search for: mail8

...mailserver today, and when I started the server again, the logs filled up with "Fixed a duplicate" warnings. This in itself it not a problem, the problem is that it appears the fix is not done correct. Consider this: Warning: Fixed a duplicate: [X]/cur/1305907573.V807I37682f3M146183.mail8.xxx.com:2,S -> 1306601066.M382668P27710.mail8.xxx.com The problem appears to be the timestamp of this new file isn't updated correctly. Now I got hundreds of mailboxes filled with mails named 1305907573.* with random (in the past) timestamps, leading to mangled miss-sorted inboxes for...

Hi, we're running dovecot 1.1.2 (centos5 32-bit rpm from atrpms) havn't had any real issues with it, but today it looks like an index has become badly corrupted. We're seeing this in the logs every time we log in to a particular account: 2008-09-10T11:56:07+01:00 mail8 dovecot: Panic: IMAP(xxx): Trying to allocate 2273345672 bytes 2008-09-10T11:56:07+01:00 mail8 dovecot: IMAP(xxx): Raw backtrace: /usr/libexec/dovecot/imap [0x80d0310] -> /usr/libexec/dovecot/imap [0x80d036a] -> /usr/libexec/dovecot/imap [0x80cfc2c] -> /usr/libexec/dovecot/imap [0x80d966c]...

Hi there, I've been seeing this error in our logs quite frequently on our nfs storage (v3): 2008-11-10T13:24:26+00:00 mail8 dovecot: IMAP(XXX at YYY.com): nfs_flush_fcntl: fcntl(/var/spool/mail/XXX/Maildir/dovecot.index.cache, F_RDLCK) failed: No locks available Which is because we don't run lockd on our servers. Why is dovecot trying to use fcntl() ? I explicitly set it to use dotlocks in the dovecot config: # 1....