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
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
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,
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
On Apr 17, 2009, at 6:51 PM, stefan novak wrote:
maybe you have mounted your nfs share with nodiratime?
Dovecot doesn't care about atimes in mailbox syncing, only mtimes.
