Hey > Did you check that the timestamp also really changes in the server > Dovecot was running on? Could be a NFS caching problem.
It took a few seconds until the new timestamp came up on the dovecot-server, but it still didn't work after the new timestamp was available. I still got the message that there are 0 messages available even there are some mails in the cur/new dir... The timestamp on the dovecot.index and dovecot.index.log file has changed after I attempted to log in. The only solution at the moment is, to destroy the dovecot.index file. Unfortunately this is not a long-term solution for us, because it happens periodically and we don't know exactly which users are affected by this problem. Any other ideas? Is there a possibility to check end rebuild the dovecot.index file manually? -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a
