On Thu, 2008-08-21 at 09:14 +0200, Roberto Tagliaferri - Tosnet srl wrote:
All of these look like normal client QUITs, so I've no idea why the client wouldn't see the new mails. If there's nothing in error logs either (may be different from where the above messages are logged, http://wiki.dovecot.org/Logging), the only possibility to debug this is to look at what the client and Dovecot actually talk to each others and how it differs from v1.0. Rawlog for example could be used for that: http://wiki.dovecot.org/Debugging/Rawlog
Ok.. i've tested only one account because this server is a production server.. I've recreated this: dovecot: Aug 21 08:38:54 Info: pop3-login: Login: user=<agenzia>, method=PLAIN, rip=213.203.182.90, lip=91.102.48.12 dovecot: Aug 21 08:38:54 Info: POP3(agenzia): Disconnected: Logged out top=0/0, retr=0/0, del=0/21, size=217625 in this check the client have not download the message
dovecot: Aug 21 08:40:20 Info: pop3-login: Login: user=<agenzia>, method=PLAIN, rip=213.203.182.90, lip=91.102.48.12 dovecot: Aug 21 08:40:20 Info: POP3(agenzia): Disconnected: Logged out top=0/0, retr=1/2962, del=0/21, size=217625 In this check yes... (thunderbird 2.0.16)
Were both of these using the same Dovecot version or was the second one different?
For first check, in log: STAT LIST UIDL
In both of the cases Dovecot's replies to these 3 commands were identical. So why did the client decide to do RETR only in the second session?.. I don't really have any ideas what could be the problem.
If you can easily test this, I guess the best way would be to find one which Dovecot v1.0.x version exactly broke this for you (and after that which hg commit change broke it).