- dovecot - dovecot.org

[Dovecot] NFS quota: hard or soft
by Edgar Fuß 20 Oct '08

20 Oct '08

Yes. I could spend more time testing this myself or examining the code. It looks to me that, with fs quota, dovecot refuses to store a mail (e.g. when the client moves a mail from one IMAP folder to another) if the user is beyond his soft limit. Is this correct/intended? Knowing nothing about the IMAP Quota extension, I would have expected that being in grace was OK. At least, this is what would happen if dovecot wasn't quota aware and the file system would enforce the limits.

2 5

[Dovecot] Sendmail and deliver LDA exits with EX_TEMPFAIL on overquota
by Sotiris Tsimbonis 20 Oct '08

20 Oct '08

Hi all, I have setup dovecot 1.1.4 and sendmail 8.14.3 with dovecot LDA on linux (RHEL5 on x86_64). I have deliberately set a very low quota (4MB) on a test account, while the actual disk usage is 5MB at the moment, in order to test overquota behaviour.. When I send an email to this account, sendmail accepts the email and tries to deliver it. Deliver fails to save in INBOX and returns an error, but the email stays in sendmail's queue.. Any suggestions on how to avoid this and produce a 5xx error for overquota users before accepting the email would be greatly appreciated.. TIA, Sotiris. ==> /var/log/maillog <== Oct 17 14:25:19 mx-mstr-07 sendmail[17289]: m9HBPJ99017288: to=<stsimb(a)t157.forthnet.gr>, ctladdr=<root(a)mx-mstr-07.forthnet.prv> (0/0), delay=00:00:00, xdelay=00:00:00, mailer=local, pri=30603, dsn=4.0.0, stat=Deferred: local mailer (/usr/libexec/dovecot/deliver) exited with EX_TEMPFAIL ==> /var/log/dovecot.log <== deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: Loading modules from directory: /usr/lib64/dovecot/lda deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: Module loaded: /usr/lib64/dovecot/lda/lib10_quota_plugin.so dovecot: Oct 17 14:25:19 Info: auth(default): master in: USER 1 stsimb.t157.forthnet.gr service=deliver dovecot: Oct 17 14:25:19 Info: auth(default): master out: USER 1 stsimb.t157.forthnet.gr uid=2082264764 home=/home/mailusers/stsimb.t157.forthnet.gr gid=126 quota_rule=*:storage=4M deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: auth input: stsimb.t157.forthnet.gr deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: auth input: uid=2082264764 deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: auth input: home=/home/mailusers/stsimb.t157.forthnet.gr deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: auth input: gid=126 deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: auth input: quota_rule=*:storage=4M deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: Quota root: name= backend=maildir args= deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: Quota rule: root= mailbox=* bytes=4194304 (0%) messages=0 (0%) deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: Quota warning: bytes=3774873 (90%) messages=0 (0%) command=/local/dovecot/sbin/quota-warning.sh 90 deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: Quota warning: bytes=2516582 (60%) messages=0 (0%) command=/local/dovecot/sbin/quota-warning.sh 60 deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: maildir: data=/var/mail/stsimb.t157.forthnet.gr/Maildir deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: maildir++: root=/var/mail/stsimb.t157.forthnet.gr/Maildir, index=, control=, inbox=/var/mail/stsimb.t157.forthnet.gr/Maildir deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: msgid=<200810171125.m9HBPJFT017287(a)mx-mstr-07.forthnet.prv>: save failed to INBOX: Quota exceeded (mailbox for user is full) ==> sendmail.cf dovecot mailer <== Mlocal, P=/usr/libexec/dovecot/deliver, F=lsDFMAw5:/|@qSPhn9, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, T=DNS/RFC822/X-Unix, A=deliver -d $u [root@mx-mstr-07 ~]# dovecot -n # 1.1.4: /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap pop3 ssl_disable: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Dovecot ready mx-mstr-07 login_process_per_connection: no login_process_size: 1024 max_mail_processes: 2048 verbose_proctitle: yes mail_location: maildir:/var/mail/%u/Maildir mail_cache_min_mail_count: 100 mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 pop3_no_flag_updates(default): no pop3_no_flag_updates(imap): no pop3_no_flag_updates(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: cache_size: 131072 cache_ttl: 315 cache_negative_ttl: 285 verbose: yes debug: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: prefetch socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota_warning: storage=90%% /local/dovecot/sbin/quota-warning.sh 90 quota_warning2: storage=60%% /local/dovecot/sbin/quota-warning.sh 60

6 15

[Dovecot] workaround for shared maildirs
by Giuliano Gavazzi 19 Oct '08

19 Oct '08

Hello, this is my first post to the list. I have several mailservers running courier-imap, but am planning to convert one (and maybe more) to dovecot 1.1.4. In the process I am also looking to finally implement shared maildirs. As it is well known some clients (notable Apple's Mail) have problems in showing shared folders if the correct private namespace (INBOX) is set in the client, as only folders beneath the INBOX root are displayed. I have seen some solutions proposed, but none satisfactory. As the problem stems in the invisibility of secondary namespaces from Mail.app, I though that tricking the namespace prefix to push the shared mailboxes inside the private INBOX namespace could be a solution and tried the following: namespace public { separator = . prefix = INBOX.Public. inbox = no location = maildir:/SharedMaildirs/Public:CONTROL=~/Maildir/ control/Public:INDEX=~/Maildir/index/Public hidden = yes list = yes subscriptions = yes } note the bogus INBOX.Public prefix. Note also that CONTROL might be better not set as this is a Maildir (see Keyword sharing in http://wiki.dovecot.org/SharedMailboxes) Initially I had defined an additional public namespace with the same maildir and a normal prefix, but this seems not necessary. Well, after some tests from Thunderbird, Mail and cone (yes, the courier UA) I can say it works . Still have to check Outlook and Opera, but this is encouraging. As the public namespace Public is actually contained inside the private (INBOX), as if it was a private mailbox (with no messages) called Public, it is actually possible to create such a mailbox inside INBOX and end up with a private mailbox called Public containing private messages AND public mailboxes... Any mailbox that a user creats inside Public instead, will end up being a public mailbox as expected. Thanks or any comments. Giuliano

2 2

Re: [Dovecot] Corrupted transaction log file / record size too small
by Steven Winikoff 19 Oct '08

19 Oct '08

>This and some other bugs are now fixed by this: >http://hg.dovecot.org/dovecot-1.1/rev/262c52055f2a Thank you! Both for this and for http://hg.dovecot.org/dovecot-1.1/rev/a0693aec0245 - Steven ________________________________________________________________________ Steven Winikoff | Concordia University | "It's a control freak thing -- I Montreal, QC, Canada | wouldn't let you understand." smw(a)alcor.concordia.ca | http://alcor.concordia.ca/~smw | - Stephen H. Underwood

1 0

[Dovecot] regarding dovecot.index.cache
by Dhaval Thakar 19 Oct '08

19 Oct '08

Hi, This is regarding updating dovecot.index.cache. I have few backup ids configured. these are used only when old mail needs to be retrieved. usually these mailboxes contains more then 9,000 mails. while login to webmail, imap consumption is high, which creates performance related issues for regular mailboxes. to resolve this i have to move heavy mailbox to dedicated server. before doing that, I wanted to confirm if there any way to update dovecot.index.cache even if user is not checking his / her mails. kindly confirm, & provide direction to implement same. Following is the mailserver related details Qmail with Vpopmail 5.4.24 Dovecot-1.1.4 dovecot -n # 1.1.4: /etc/dovecot/dovecot.conf protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_plugins: quota imap_quota trash imap_client_workarounds: delay-newmail outlook-idle namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: checkpassword args: /home/vpopmail/bin/vchkpw userdb: driver: vpopmail userdb: driver: prefetch plugin: quota: maildir quota_rule: Trash:ignore thanks & regards dhaval

2 3

[Dovecot] Dovecot 1.1.4 / Maildir++ quota and move to trash
by Xavier Beaudouin 18 Oct '08

18 Oct '08

Hello, Seems there is some nasty problems with Dovecot 1.1.4... We use Maildir++ quota, and when moving mail to Trash, Dovecot just drop the connection... when the maildir is overquota. Is there any way to avoid that and just move the mail to the trash allowing user to expunge their mail easily without calling support to do rm -rf Maildir/cur ? Thanks, /Xavier

4 8

[Dovecot] Pop3 on dovecot
by Rajiv Gore 18 Oct '08

18 Oct '08

Hi When I telnet localhost 110 I get a response as +OK POP3 localhost 2006c.94 server ready I expect to get +OK Dovecot ready. Is there any other pop3 server running on port 110? If so how to assign port 110 to Dovecot? Thanks for advice -- Rajiv Gore 102 Sahakarnagar Ahmednagar 414 003 MS, India

2 1

Re: [Dovecot] Corrupted transaction log file / record size too small
by Steven Winikoff 18 Oct '08

18 Oct '08

>> 2) recompiled dovecot without optimization (ie, gcc -O0 instead of -O2) >> (as per http://www.mail-archive.com/dovecot@dovecot.org/msg12936.html) > >The problem here turned out to be a bug in Sun CC (and gcc -O2 >apparently worked after all, so maybe a problem with testing). Thanks. I'll revert to the default -O2 the next time we recompile (which will probably be version 1.1.4 sometime early next week). >> 3) reverted to using flock for file locking instead of fcntl (we'd been >> using flock with dovecot 1.0.10; 1.1.3 used fcntl by default in a >> couple of places, so I changed it back to see what would happen) > >This shouldn't really make a difference. That's good, because in hindsight I haven't noticed any difference. :-) >> - we still see the occasional assertion failure at line 1091 of >> index-mail.c; this is the one that I'd hoped to solve by >> recompiling without optimization, but at least it seems to be >> happening less frequently than before > >I had hoped v1.1.3 would have fixed this. But perhaps this is also >related to the disk quota issues. Are there any other errors that are >logged before the assert? Nothing obvious, I'm afraid. For example, this occurence is typical of the 24 which we've logged since Sept. 26 (which is as far back as we keep dovecot log data online; for the record, we upgraded from 1.0.10 to 1.1.3 on Sept. 23): Oct 8 13:56:39 alcor dovecot: pop3[15127] USER1, NNN.NNN.NNN.NNN: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0, xfer=12/27 Oct 8 13:56:39 alcor dovecot: pop3-login: Login: [15118], USER2, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: wrapper[15139]: pop3, USER2, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: pop3-login: Login: [15058], USER3, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: wrapper[15141]: pop3, USER3, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: pop3[15141] USER3, NNN.NNN.NNN.NNN: mkdir(/home/USER3/.imap/INBOX) failed: Disk quota exceeded Oct 8 13:56:39 alcor dovecot: imap-login: Login: [15121], USER4, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: wrapper[15143]: imap, USER4, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: pop3[15139] USER2, NNN.NNN.NNN.NNN: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0, xfer=12/27 Oct 8 13:56:39 alcor dovecot: imap-login: Login: [15001], USER5, NNN.NNN.NNN.NNN Oct 8 13:56:40 alcor dovecot: wrapper[15159]: imap, USER5, NNN.NNN.NNN.NNN Oct 8 13:56:40 alcor dovecot: imap-login: Login: [15158], USER6, NNN.NNN.NNN.NNN Oct 8 13:56:40 alcor dovecot: wrapper[15162]: imap, USER6, NNN.NNN.NNN.NNN Oct 8 13:56:40 alcor dovecot: imap[15159] USER5, NNN.NNN.NNN.NNN: Disconnected: Logged out bytes=305/13377 Oct 8 13:56:40 alcor dovecot: imap[15162] USER6, NNN.NNN.NNN.NNN: Disconnected: Logged out bytes=110/356 Oct 8 13:56:40 alcor dovecot: Panic: imap[15143] USER4, NNN.NNN.NNN.NNN: file index-mail.c: line 1091 (index_mail_close): assertion failed: (!mail->data.destroying_stream) Oct 8 13:56:40 alcor dovecot: imap[15143] USER4, NNN.NNN.NNN.NNN: Raw backtrace: dovecot-imap [0x4a3ddd] -> dovecot-imap [0x4a4b9d] -> dovecot-imap(i_fatal+0) [0x4a40d1] -> dovecot-imap(index_mail_close+0xfa) [0x4538d4] -> dovecot-imap [0x4538fe] -> dovecot-imap(index_mail_set_seq+0x6a) [0x453ac6] -> dovecot-imap [0x445e6e] -> dovecot-imap(mail_set_seq+0x28) [0x45f6a5] -> dovecot-imap(index_storage_search_next_nonblock+0xe9) [0x458ff0] -> dovecot-imap(mailbox_search_next_nonblock+0x33) [0x462de3] -> dovecot-imap(mailbox_search_next+0x2e) [0x462da2] -> dovecot-imap [0x415e99] -> dovecot-imap(cmd_copy+0x19c) [0x4160ac] -> dovecot-imap [0x41d0ac] -> dovecot-imap [0x41d2e9] -> dovecot-imap [0x41d41c] -> dovecot-imap [0x41d460] -> dovecot-imap(client_input+0xb4) [0x41d5ed] -> dovecot-imap(io_loop_handler_run+0x17d) [0x4aea11] -> dovecot-imap(io_loop_run+0x3b) [0x4adc6a] -> dovecot-imap(main+0x99) [0x42908b] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b306fee78c4] -> dovec! ot-imap [0x414939] Oct 8 13:56:40 alcor dovecot: child 15143 (imap) killed with signal 6 Oct 8 13:56:40 alcor dovecot: pop3[15141] USER3, NNN.NNN.NNN.NNN: Disconnected: Logged out top=0/0, retr=1/12816, del=1/1, size=12798, xfer=40/12944 Oct 8 13:56:40 alcor dovecot: imap-login: Login: [15003], USER7, NNN.NNN.NNN.NNN Although the usernames and IP addresses have been elided, each USERn token always represents the same specific account wherever it appears. >> - this doesn't happen often, but once in a while we see assertion >> failures at line 163 of src/pop3-login/client-authenticate.c or >> line 200 of src/imap-login/client-authenticate.c > >I think I've managed to get this also sometimes when killing dovecot- >auth or doing something else "wrong" (I don't remember exactly), but >not during normal operation. I should have noted down how to reproduce >this when I still knew how to reproduce it.. For us this appears to happen during normal operations. That's not to say I've never killed a dovecot-auth process :-), but it's not something I do often (in fact the last time I did was when I recompiled 1.1.3 as described previously, which by now was ten days ago). For what it may be worth, this particular symptom appears to happen in clusters. The most recent spate that we saw were as follows (in context, in case any of the other log messages may be relevant): Oct 10 04:48:45 alcor dovecot: pop3-login: Disconnected (no auth attempts): [9703], NNN.NNN.NNN.NNN Oct 10 04:48:45 alcor dovecot: pop3-login: Disconnected (no auth attempts): [9705], NNN.NNN.NNN.NNN Oct 10 04:48:45 alcor dovecot: pop3-login: Disconnected (no auth attempts): [9702], NNN.NNN.NNN.NNN Oct 10 04:48:46 alcor dovecot: pop3-login: Disconnected (no auth attempts): [9704], NNN.NNN.NNN.NNN Oct 10 04:48:46 alcor dovecot: pop3-login: Disconnected: Inactivity (auth failed, 1 attempts): [9500], USER10, NNN.NNN.NNN.NNN Oct 10 04:48:46 alcor dovecot: Panic: pop3-login: file client-authenticate.c: line 163 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:46 alcor dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): [9502], USER11, NNN.NNN.NNN.NNN, TLS Oct 10 04:48:46 alcor dovecot: Panic: imap-login: file client-authenticate.c: line 200 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:46 alcor dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): [9503], USER12, NNN.NNN.NNN.NNN, TLS Oct 10 04:48:46 alcor dovecot: Panic: imap-login: file client-authenticate.c: line 200 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:46 alcor dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): [8777], USER9, NNN.NNN.NNN.NNN Oct 10 04:48:46 alcor dovecot: Panic: imap-login: file client-authenticate.c: line 200 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:47 alcor dovecot: imap[4258] USER8, 67.223.74.40: Disconnected: Logged out bytes=7407/20930 Oct 10 04:48:47 alcor dovecot: pop3-login: Disconnected: Inactivity (auth failed, 1 attempts): [9575], USER13, NNN.NNN.NNN.NNN Oct 10 04:48:47 alcor dovecot: Panic: pop3-login: file client-authenticate.c: line 163 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:47 alcor dovecot: pop3-login: Disconnected: Inactivity (auth failed, 1 attempts): [9576], USER14, NNN.NNN.NNN.NNN Oct 10 04:48:47 alcor dovecot: Panic: pop3-login: file client-authenticate.c: line 163 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9498 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9500 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9499 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9502 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9503 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9575 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9576 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9174 Oct 10 04:48:47 alcor dovecot: imap[9809] USER9, 132.205.7.20: Connection closed bytes=0/0 Oct 10 04:48:47 alcor dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): [9174], USER8, NNN.NNN.NNN.NNN, TLS Oct 10 04:48:47 alcor dovecot: Panic: imap-login: file client-authenticate.c: line 200 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:48 alcor dovecot: imap-login: Disconnected (no auth attempts): [9896], NNN.NNN.NNN.NNN Oct 10 04:48:48 alcor dovecot: imap-login: Disconnected (no auth attempts): [9895], NNN.NNN.NNN.NNN Oct 10 04:48:48 alcor dovecot: pop3-login: Disconnected (no auth attempts): [9893], NNN.NNN.NNN.NNN >> I missed this originally, but on reflection I notice in the logs that >> every time the "record size too small" error appears, inevitably the >> user involved is over disk quota and out of grace period. For >> example, > >Yes, this is most likely what's the problem. I remember testing v1.0 >quite a lot in "out of disk space" conditions, but I haven't really >done any such testing with v1.1. I'll try that and see if I can get >these problems reproduced and fixed. Thank you! :-) Please let me know if there's anything I can do to help. - Steven ________________________________________________________________________ Steven Winikoff | Concordia University | "Hanging is too good for a man who Montreal, QC, Canada | makes puns; he should be drawn and smw(a)alcor.concordia.ca | quoted." http://alcor.concordia.ca/~smw | - Fred Allen

2 2

Re: [Dovecot] Corrupted transaction log file / record size too small
by Steven Winikoff 18 Oct '08

18 Oct '08

>> I've been working around the problem by deleting the contents of >> ~user/.imap for affected users, but I'd really prefer to fix it >> properly. :-) Any suggestions would be gratefully received. > >I think this should get fixed by itself? Although the first login fails, >the next one should succeed. Yes, that's right. I didn't realize it at first, because we were also seeing other problems (eg assertion failure at line 39 of index-sync.c) which did require the index to be deleted. I've since made the following changes: 1) commented out the assertion at line 39 of index-sync.c (as per http://www.nabble.com/dovecot-panic-after-upgrade-1.0.15-to-1.1.2-td1909850…) 2) recompiled dovecot without optimization (ie, gcc -O0 instead of -O2) (as per http://www.mail-archive.com/dovecot@dovecot.org/msg12936.html) 3) reverted to using flock for file locking instead of fcntl (we'd been using flock with dovecot 1.0.10; 1.1.3 used fcntl by default in a couple of places, so I changed it back to see what would happen) After this, we've seen fewer problems, but there are still the occasional ones: - the original corrupted transaction log error which prompted this thread - we still see the occasional assertion failure at line 1091 of index-mail.c; this is the one that I'd hoped to solve by recompiling without optimization, but at least it seems to be happening less frequently than before - this doesn't happen often, but once in a while we see assertion failures at line 163 of src/pop3-login/client-authenticate.c or line 200 of src/imap-login/client-authenticate.c >Can you reproduce this by running imaptest (on a test account)? >http://imapwiki.org/ImapTest Actually this and your other suggestions may not be necessary; I think I just realized what's been going on. I missed this originally, but on reflection I notice in the logs that every time the "record size too small" error appears, inevitably the user involved is over disk quota and out of grace period. For example, Oct 3 17:52:21 alcor dovecot: imap[14973] XXXX, NNN.NNN.NN.NNN: Corrupted transaction log file /home/XXXX/mail/.imap/sent-mail/dovecot.index.log: record size too small (type=0xcd91, offset=8180, size=0) Oct 3 17:52:21 alcor dovecot: imap[14973] XXXX, NNN.NNN.NN.NNN: fscking index file (in-memory index) Oct 3 17:52:21 alcor dovecot: imap[14973] XXXX, NNN.NNN.NN.NNN: Transaction log got desynced for index (in-memory index) Oct 3 17:52:21 alcor dovecot: imap[14973] XXXX, NNN.NNN.NN.NNN: Disconnected: IMAP session state is inconsistent, please relogin. bytes=169/1848 Oct 3 17:52:22 alcor dovecot: imap-login: Login: [14998], XXXX, NNN.NNN.NN.NNN Oct 3 17:52:22 alcor dovecot: wrapper[15023]: imap, XXXX, NNN.NNN.NN.NNN Oct 3 17:52:22 alcor dovecot: imap[15023] XXXX, NNN.NNN.NN.NNN: open(/home/XXXX/mail/.imap/CFI-Howe/.temp.alcor.15023.e786c194b1dcc08c) failed: Disk quota exceeded Having seen this, I went back to the saved log for September 30th (the one containing the excerpt I pasted into my original message in this thread) -- and interestingly, I found that the quota failure wasn't recorded there. I don't know what was different about that occurrence, but everything I've seen recently suggests that "record size too small" is due to interaction with the quota system. ...so this is where I admit that I have indeed read http://wiki.dovecot.org/Quota/FS; unfortunately, the only user-writable file system on this machine that doesn't have (or need to have!) disk quotas enabled is /var/tmp, which doesn't seem to be a suitable place for dovecot indexes. Under the circumstances, are you still interested in seeing ImapTest results and a backtrace? If so, should I do that before or after upgrading to 1.1.4? Thanks, - Steven ________________________________________________________________________ Steven Winikoff | Concordia University | "The end of the world will occur at Montreal, QC, Canada | 3:00 p.m., this Friday, with symposium smw(a)alcor.concordia.ca | to follow." http://alcor.concordia.ca/~smw | - fortune(6)

2 2

[Dovecot] Request for help with new plugin
by John Lightsey 18 Oct '08

18 Oct '08

Hi there, I was having lots of trouble with the normal expire plugin so I decided to try and come up with a plugin that handles the trash directory in the same way as Courier (when the user logs out it should clean messages from the trash that have been there for more than X days.) I used the expire and trash plugins as a guide but there are probably a number of things done wrong here and I have plenty of questions. To use this you'd need to run autoreconf for the autotools scripts, compile, make, make install, then add "autoexpire" to the imap/pop3 mail_plugins lists and "autoexpire = Trash 7" to the plugin section. 1. Is there any documentation of how the hook system and virtual mailboxes work outside of the source code? 2. I'd like the Trash cleanup to occur at logout, but the closest I could find was mailbox close. This makes the behavior a little quirky. It seems like Dovecot closes the mailbox each time it performs an operation on it, so when the client gets a list of mail in the box it does a close and the oldest items in the returned list will actually be expunged. 3. Is SAVE_DATE the correct field to be looking for here? I want the expiration to be based on the amount of time the letter has spent in the trash folder. 4. For searching through the Trash folder, SEARCH_BEFORE doesn't seem to match up with SAVE_DATE. Is there some other way to limit the search results to the dates that will fall before a certain SAVE_DATE value? J.D.

3 4