[Dovecot] 0 mails available even if mails in mailbox
Hello
We are currently facing the problem, that dovecot doesn't return any messages (Pop3: +OK 0 messages) even if there are messages in the cur and new directory (maildir format). The logfile does not contain any information other than login/logout.
After I deleted the dovecot.index file, all messages are available and everything works as expected. According to the wiki page [1] the main index file should be synchronized when the cur and new timestamps changed. I suppose this synchronization doesn't work correctly because the problem still existed after I changed the timestamps manually.
Dovecot version: 10.0.14 Operating System: FreeBSD 7.0-RELEASE-p1 CPU Arch: amd64 Filesystem: NFS Clients: The problem exists on Pop3 and IMAP. It doesn't matter which client. I could reproduce the problem on outlook, thunderbird and even on telnet.
Reproduced:
+OK Dovecot ready. user user@domain.com +OK pass password +OK Logged in. list +OK 0 messages:
After deleting dovecot.index:
+OK Dovecot ready. user user@domain.com +OK pass password +OK Logged in. list +OK 20 messages:
It seems to be a problem with the index-file from dovecot which doesn't seem to be synchronized.
What could be the reason for this behaviour? How can we fix this issue for all customers?
Kind regards Raphael Thoma
On Apr 17, 2009, at 9:27 AM, Raphael Thoma wrote:
We are currently facing the problem, that dovecot doesn't return any
messages (Pop3: +OK 0 messages) even if there are messages in the
cur and new directory (maildir format). The logfile does not contain
any information other than login/logout.After I deleted the dovecot.index file, all messages are available
and everything works as expected. According to the wiki page [1] the
main index file should be synchronized when the cur and new
timestamps changed. I suppose this synchronization doesn't work
correctly because the problem still existed after I changed the
timestamps manually.
Did you check that the timestamp also really changes in the server
Dovecot was running on? Could be a NFS caching problem.
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
On Mon, 2009-04-20 at 15:17 +0200, Raphael Thoma wrote:
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...
Well, that is weird. If timestamp changes, Dovecot makes sure that it has all the changes in the index file. The only possibility that I can think of for it not noticing new mails is because it doesn't see that the timestamp changes..
You could check with idxview what the index files contain. idxview is in included in Dovecot's libexec directory (where imap etc. binaries are). For example:
/usr/local/libexec/dovecot/idxview ~/Maildir
What does it show in "sync stamp" line?
Also you mentioned you're using Dovecot v10.0.14, which I guess means v1.0.14. You could see if v1.1 happens to work better. It also uses different/better timestamping in index files than v1.0.
participants (3)
-
Raphael Thoma
-
stefan novak
-
Timo Sirainen