December 2024 - dovecot

Trying to track down the source of a corrupted cache error
by Grant Keller 10 Dec '24

10 Dec '24

Recently we have been seeing a steady increase (nothing too crazy, just more than usual) in "Deleting corrupted cache record" log errors. What struck me as weird was that it would be for the same message over and over, indicating that the deleted record was making it back into the cache. Digging into one, I realized that the first error was actually this: Dec 4 19:08:59 b.imapd.sonic.net dovecot[2696]: imap(xxx): session=wnZqMH0oHOViI3NN Error: Mailbox INBOX: Maildir filename has wrong W value, renamed the file from /var/spool/mail/17/62/xxx/cur/1733363505.M428026P1491073.b.imapd.sonic.net,S=8966052,W=12155730:2, to /var/spool/mail/17/62/xxx/cur/1733363505.M428026P1491073.b.imapd.sonic.net,S=8966052:2, Dec 4 19:08:59 b.imapd.sonic.net dovecot[2696]: imap(xxx): session=wnZqMH0oHOViI3NN Error: Mailbox INBOX: Deleting corrupted cache record uid=6430670: UID 6430670: Broken virtual size in mailbox INBOX: read(/var/spool/mail/17/62/xxx/cur/1733363505.M428026P1491073.b.imapd.sonic.net,S=8966052,W=12155730:2,): FETCH BODY[]<11796480.393216> got too little data: 359249 vs 359250 Also worth noting that the emails themselves do have a highly unusual number of carriage returns. What causes this and is there a way to fix it besides deleting the offending message?

1 0

Info on 'sieve_pipe_bin_dir' needed
by leo1subscr＠zudiewiener.com 06 Dec '24

06 Dec '24

I'm trying to follow the instruction https://doc.dovecot.org/2.3/configuration_manual/howto/antispam_with_sieve/ to setup IMAPSieve I cannot find any info on what sieve_pipe_bin_dir should point to. Any references I have found to this point to the old wiki. My current spam learning sieve scripts are in file:/home/vmail/sieve/global/ Should sieve_pipe_bin_dir point to this? Thanks, Leo

2 1

Dovecot IMAP Mail latency
by tamilarasan_ext＠iomd.info 05 Dec '24

05 Dec '24

We are working on importing emails from Gmail to Dovecot. During the process, all emails are written to a new directory within the mail folder. For fetching the emails, we are using the IMAP protocol with the imap_tools Python library. After importing, we run the IMAP fetch at 5-second intervals. However, the newly imported emails do not appear immediately. They only become available after 30 to 40 seconds. How can we resolve this issue? What steps can we take to debug and identify the source of the delay?

2 1