Troubles with MagicMail (pop checker)

Hi!

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.

KickIn

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?

THIS THREAD looks simulair to your problem.

In fact I’m using Magic Mail Monitor 3, which is an e-mail checker, not magicmail, which is as you already said a mail daemon. Sorry for the confusion

You can look to log file Avast4\DATA\log\aswMaiSv.log. For detailed logging insert line ‘Log=20’ to file Avast4\DATA\avast4.ini under [MailScanner].

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:

MMM3:
08/26/04 09:53:27: --POP ReadFromPop …
08/26/04 09:53:27: <-POP +OK
08/26/04 09:53:27: --XXX testing second-side connection
08/26/04 09:53:27: --XXX sleep

08/26/04 09:53:27: --POP Finishing connection handler

OE:
08/26/04 09:54:00: --POP ReadFromPop …
08/26/04 09:54:00: <-POP +OK maildrop ready, 0 messages (0 octets) (433059 104857600)
08/26/04 09:54:00: ->POP STAT
08/26/04 09:54:00: --POP Before ReadFromPop
08/26/04 09:54:00: --XXX sleep

08/26/04 09:54:00: --POP ReadFromPop …
08/26/04 09:54:00: <-POP +OK 0 0
08/26/04 09:54:00: ->POP QUIT
08/26/04 09:54:00: --POP Before ReadFromPop
08/26/04 09:54:01: --XXX sleep

08/26/04 09:54:01: --POP ReadFromPop …
08/26/04 09:54:01: <-POP +OK server signing off.
08/26/04 09:54:01: --POP Finishing connection handler

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).

kick

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…

Did you test the direct connection?
username
pop.mail.yahoo.fr
110

Direct connection works, so I left mmm3 runnning with direct parameters, and after I use the avast’s parameters for OE…

thanks anyway…
Kick

Could you post a log of the whole session of MMM ? I cannot see the problem without the beginning.

Hi, Thnks for your interrest; there is the whole log:

08/30/04 09:17:50: POP accept connection from: 127.0.0.1
08/30/04 09:17:50: ->POP USER XXXXXX#pop.mail.yahoo.fr
08/30/04 09:17:50: Connected to POP server pop.mail.yahoo.fr 110
08/30/04 09:17:50: --XXX sleep
08/30/04 09:17:50: --XXX sleep
08/30/04 09:17:50: --XXX sleep
08/30/04 09:17:50: --XXX sleep
08/30/04 09:17:50: --XXX sleep
08/30/04 09:17:51: <-POP +OK hello from popgate(2.27.5)
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: <-POP +OK password required.
08/30/04 09:17:51: ->POP pass …
08/30/04 09:17:51: --POP Before ReadFromPop
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --POP ReadFromPop …
08/30/04 09:17:51: <-POP +OK maildrop ready, 0 messages (0 octets) (433059 104857600)
08/30/04 09:17:51: ->POP NOOP
NOOP
08/30/04 09:17:51: --POP Before ReadFromPop
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:51: --XXX sleep
08/30/04 09:17:52: --XXX sleep
08/30/04 09:17:52: --XXX sleep
08/30/04 09:17:52: --XXX sleep
08/30/04 09:17:52: --POP ReadFromPop …
08/30/04 09:17:52: <-POP +OK
08/30/04 09:17:52: --XXX testing second-side connection
08/30/04 09:17:52: --XXX sleep
08/30/04 09:17:52: --XXX testing second-side connection
08/30/04 09:17:52: --XXX sleep
08/30/04 09:17:52: --XXX testing second-side connection
08/30/04 09:17:52: --XXX sleep
08/30/04 09:17:52: --XXX testing second-side connection
08/30/04 09:17:52: --XXX sleep
08/30/04 09:17:52: --XXX testing second-side connection
08/30/04 09:17:52: --XXX sleep
08/30/04 09:17:52: --XXX testing second-side connection
08/30/04 09:17:52: --XXX sleep
08/30/04 09:17:52: --XXX testing second-side connection
08/30/04 09:17:52: --XXX sleep
08/30/04 09:17:52: --XXX testing second-side connection
08/30/04 09:17:52: --POP Finishing connection handler

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…

Kick

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 :wink: )

Kick

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.