I have a little problem with magic mail, as when it is configured to lok to my accounts directly, all is going well, but when I’m trying to pass through avast! it retruns me the following error:
Connection was lost.
Parameters where the following:
username#pop.mail.yahoo.fr
127.0.0.1
110
When using those parameters with outlook express it works too.
Acording to the MagicMail website this mail server application is for *.nix. Why posting in Home/Pro and not in the Linux forum?
I think the problem lies in the fact that MailMagic is a server and not a email client. You need to find a way to get the email through Avast before it reaches the mail server. If that can be done is something I doubt. Perhaps with a little programing?
Thanks for the infos, I have done what you said, but I don’t know a lot of pop3 protocols, so…
Nevertheless, it seems that the following command seems to block my client:
<-POP +Ok
With OE I have no pb, here part of log for both clients:
don’t know if you can do something with it… Even if this is a client problem, could you explain why to me? (as the client is opensource, i’ll read a little about pop3 specs, and will try to achieve making it work with avast).
I use exactly the same parameters with POP3Notifier (a Spamihilator plugin). It works there :-
I used Magic Mail before I started Spami (and its plugin), sorry, I can’t imagine what is happening…
So I think there is a problem with noop sending, seems like mmm3 is sending it 2 times instead of 1 time; but i’m not sure it can cause problem to a pop3 server, as I have done a telnet on my work’s pop3 server, and it just return me error message when commands where wrong, sending them again doesn’t perturb it. Need to try with avast pop3 server…
In fact it seems that it’s not the double NOOP that is causing troubles…Seems to have an unanswered response from the client or from the server ( testing second-side connection).
but from which is this string emmitted (the server logs both client and server side ;masking password, thanx )
I think the double NOOP is the problem. The mail scanner expects to receive subsequent command from client only after the previous one was answered by server.