POP3 collection stops after few weeks

[thornthunder]

Hello.

I have a wingate mail server, version 6.1.2, that works fine, until one day, the pop3 collection ceases.

I've found by now that the only way to make this work is to inflate a ghost image of the installation when it was still working.

I've tried to make backups of the wingate folder, as wel as the registry, but no succes. The only fix, is ghost restoring.

This is the mesage I get in the logging file when I try to retreve mail on a non functional server:
07/21/07 23:48:12 127.0.0.2 <system> 0000000062 Debug: Administrator@172.16.1.3 <=S: +OK Administrator has 218 messages in mailbox
07/21/07 23:48:12 127.0.0.2 <system> 0000000062 Debug: Administrator@172.16.1.3 C=>: STAT
07/21/07 23:48:12 127.0.0.2 <system> 0000000063 Debug: mailsort@172.16.1.3 <=S: +OK 0 0
+OK POP3 Server signing off
07/21/07 23:48:12 127.0.0.2 <system> 0000000063 Traffic 91 266 0 0 0s
07/21/07 23:48:12 127.0.0.2 <system> 0000000063 Terminated exit code 0
07/21/07 23:48:12 127.0.0.2 <system> 0000000062 Debug: Administrator@172.16.1.3 <=S: +OK 218 18539030
07/21/07 23:48:12 127.0.0.2 <system> 0000000062 Debug: Administrator@172.16.1.3 C=>: UIDL 1
07/21/07 23:48:12 127.0.0.2 <system> 0000000062 Debug: Administrator@172.16.1.3 <=S: +OK 1 0000209236.msg
07/21/07 23:48:12 127.0.0.2 <system> 0000000062 Debug: Administrator@172.16.1.3 C=>: RETR 1
07/21/07 23:48:12 127.0.0.2 <system> 0000000062 Debug: Administrator@172.16.1.3 <=S: +OK 2522 octets
07/21/07 23:48:12 127.0.0.2 <system> 0000000062 Debug: Administrator@172.16.1.3 C=>: QUIT
07/21/07 23:48:12 127.0.0.2 <system> 0000000062 Debug: Administrator@172.16.1.3 <=S: Received: From 196.25.240.94 (unverified [127.0.0.1]) by SMTP Server [127.0.0.1]

Ignore the "mailsort" collections, that is part of a loop i had to put in, to compensate for the shortcommings in wingate mail parsing by use of a pearl script, and some "mail juggeling"

Funny thing is, when this stops to function, both mail collections stop as well...

Thanks, and looking forward to the solution !

[adrien]

that line back from the server after the QUIT command is very odd.

It's part of some message headers.

Also, it's odd that the retrieval sends QUIT after retrieving only one message (and possibly not even all of it).

in any case, I'd recommend updating to 6.2.2. we fixed quite a few POP3 collection issues since 6.1.2.

http://www.wingate.com/showfaq.php?faqid=2

Regards

Adrien