September 2008 - dovecot

[Dovecot] imap-quota not working
by arvids 16 Oct '08

16 Oct '08

Hello, imap-quota plugin always returns empty quota: a1 GETQUOTA "" * QUOTA "" () a1 OK Getquota completed. a2 GETQUOTAROOT INBOX * QUOTAROOT "INBOX" a2 OK Getquotaroot completed. quota_rule and quota_rule2 for this user are defined in db as following: '*:storage=5000000' '*:messages=50000' Quota for LDA is working OK. I am using dovecot-1.1.3 with quotadict. Here is my dovecot -n output: # 1.1.3: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ syslog_facility: local7 protocols: pop3 imap ssl_cert_file: /etc/postfix/host-cert.pem ssl_key_file: /etc/postfix/host-key.pem disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_greeting: Server. login_process_per_connection: no login_processes_count: 5 login_max_processes_count: 32 verbose_proctitle: yes first_valid_uid: 95 first_valid_gid: 95 mail_uid: 95 mail_gid: 95 mail_location: maildir:~/Maildir fsync_disable: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail imap_client_workarounds(pop3): pop3_enable_last(default): no pop3_enable_last(imap): no pop3_enable_last(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: . inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login digest-md5 cram-md5 apop cache_size: 1024 cache_ttl: 600 cache_negative_ttl: 60 user: doveauth verbose: yes passdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: dict:::proxy:/var/run/dovecot/dict-server:quotadict dict: quotadict: mysql:/usr/local/dovecot/etc/dovecot-sql-dict-quota.conf Regards, Arvids

2 8

[Dovecot] assertion failure in current hg, file istream.c: line 303 (i_stream_read_data): assertion failed: (stream->stream_errno != 0) (1.1.3 was working fine)
by Diego Liziero 16 Oct '08

16 Oct '08

Today I updated to current dovecot-1.1 hg tree and I got many of these assertion failures: file istream.c: line 303 (i_stream_read_data): assertion failed: (stream->stream_errno != 0) (gdb) bt full #0 0x00352402 in __kernel_vsyscall () No symbol table info available. #1 0x0043ed20 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x00440631 in abort () from /lib/libc.so.6 No symbol table info available. #3 0x080f6968 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:150 backtrace = 0x906d950 "/usr/libexec/dovecot/imap [0x80f6946] -> /usr/libexec/dovecot/imap [0x80f7207] -> /usr/libexec/dovecot/imap(i_fatal+0) [0x80f6ac0] -> /usr/libexec/dovecot/imap(i_stream_read_data+0. #4 0x080f7207 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x8124778 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfe643a4 "mG\022\b/\001") at failures.c:430 No locals. #5 0x080f6ac0 in i_panic (format=0x8124778 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:197 args = 0xbfe643a4 "mG\022\b/\001" #6 0x080fcb64 in i_stream_read_data (stream=0x9094a08, data_r=0xbfe64444, size_r=0xbfe64440, threshold=0) at istream.c:303 ret = -1 read_more = false __PRETTY_FUNCTION__ = "i_stream_read_data" #7 0x08065ba1 in imap_fetch_send (ctx=0x90716e0, output=0x90714ec, input=0x9094a08, cr_skipped=false, virtual_size=169, add_missing_eoh=false, last_cr=0x9071734) at imap-fetch-body.c:132 msg = (const unsigned char *) 0x0 i = 3219539032 size = 0 vsize_left = 169 sent = 0 ret = 581237648214344776 add = 16 '\020' blocks = false #8 0x08065d7f in fetch_stream_send (ctx=0x90716e0) at imap-fetch-body.c:217 ret = 151603720 #9 0x080660e8 in fetch_stream (ctx=0x90716e0, size=0x908efc4) at imap-fetch-body.c:293 input = (struct istream *) 0x10b8df #10 0x08066225 in fetch_data (ctx=0x90716e0, body=0x9071cd8, size=0x908efc4) at imap-fetch-body.c:318 str = (string_t *) 0x906cc18 #11 0x08066ac7 in fetch_body_mime (ctx=0x90716e0, mail=0x908e9e8, body=0x9071cd8) at imap-fetch-body.c:555 part = (const struct message_part *) 0x908efb0 section = 0x9071d12 "MIME" __PRETTY_FUNCTION__ = "fetch_body_mime" #12 0x08064bad in imap_fetch_more (ctx=0x90716e0) at imap-fetch.c:309 h = (const struct imap_fetch_context_handler *) 0x90718c8 _data_stack_cur_id = 4 client = (struct client *) 0x9071368 handlers = (const struct imap_fetch_context_handler *) 0x9071850 count = 7 ret = 1 __PRETTY_FUNCTION__ = "imap_fetch_more" #13 0x08064dd4 in imap_fetch (ctx=0x90716e0) at imap-fetch.c:361 ret = 0 __PRETTY_FUNCTION__ = "imap_fetch" #14 0x0805c792 in cmd_fetch (cmd=0x9071600) at cmd-fetch.c:152 ctx = (struct imap_fetch_context *) 0x90716e0 args = (const struct imap_arg *) 0x9075688 search_arg = (struct mail_search_arg *) 0x9071678 messageset = 0x9075750 "4068" ret = 151455048 #15 0x08061173 in cmd_uid (cmd=0x9071600) at cmd-uid.c:26 command = (struct command *) 0x907068c cmd_name = 0x9075738 "fetch" #16 0x08062534 in client_command_input (cmd=0x9071600) at client.c:580 client = (struct client *) 0x9071368 command = (struct command *) 0x23 __PRETTY_FUNCTION__ = "client_command_input" #17 0x08062769 in client_command_input (cmd=0x9071600) at client.c:629 client = (struct client *) 0x9071368 command = (struct command *) 0x9070668 __PRETTY_FUNCTION__ = "client_command_input" #18 0x08062867 in client_handle_next_command (client=0x9071368, remove_io_r=0xbfe64765) at client.c:670 size = 132 #19 0x080628a3 in client_handle_input (client=0x9071368) at client.c:680 _data_stack_cur_id = 3 ret = 7 remove_io = false handled_commands = false #20 0x08062a31 in client_input (client=0x9071368) at client.c:725 cmd = (struct client_command_context *) 0x4e7408 output = (struct ostream *) 0x90714ec bytes = 132 __PRETTY_FUNCTION__ = "client_input" #21 0x08101115 in io_loop_handler_run (ioloop=0x906f9b0) at ioloop-epoll.c:203 ctx = (struct ioloop_handler_context *) 0x906faa8 events = (struct epoll_event *) 0x906fae8 event = (const struct epoll_event *) 0x906fae8 list = (struct io_list *) 0x9071568 io = (struct io_file *) 0x9071548 tv = {tv_sec = 1799, tv_usec = 999874} events_count = 3 t_id = 2 msecs = 1800000 ret = 1 i = 0 j = 0 call = true #22 0x081003ac in io_loop_run (ioloop=0x906f9b0) at ioloop.c:320 No locals. #23 0x0806debd in main (argc=1, argv=0xbfe648c4, envp=0xbfe648cc) at main.c:293 No locals.

2 9

[Dovecot] client certs with godaddy ssl cert
by Harondel J. Sibble 13 Oct '08

13 Oct '08

I've read the client ssl cert section in the wiki and it talks about using a self signed cert, if I am using a commercial cert, in this case godaddy, how do I implement a self signed cert for the client side and have dovecot make use of this? I know the mechanics of setting up the self signed ca, the question is more what configuration changes do I need to make in dovecot to handle both godaddy and the self signed ca functionality? Thanks -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help(a)pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager)

6 18

[Dovecot] Test environment question
by Stewart Dean 09 Oct '08

09 Oct '08

My production DC machine owns the mail filesystems and is running DC V1.0.15 and mbox folder format. I am looking to test V1.1.3 on another machine, which NFS mounts the mail filesystems, but has its own local index FS. I have made this test environment my default connection in TBird, and it seems to work just fine. Also, I have made sure that my TBird client isn't connecting to the production server (it has multiple accounts but I have turned off the cehck for mail when starting and check for new mail every N minutes functions, and then check the ps table to make sure there are no imap connections) However, I'm seeing two errmsgs in the maillog on the test machine: > Sep 22 11:54:13 egg mail:err|error dovecot: IMAP(sdean): posix_fallocate() faile > d: Protocol not available > Sep 22 11:54:13 egg mail:err|error dovecot: IMAP(sdean): file_set_size() failed > with mbox file /var/spool/mail/sdean: Protocol not available which appear to happen AFTER mail arrives at the production server....it seems to happen on my test server the next time my client goes to access mail AFTER mail has arrived at the production server. Subsequent client requests of the test server execute without error until AFTER the next time mail arrives at and my inbox is updated with it. Again, if I hadn't looked at the logs, I wouldn't know there was a problem...I can see my new mail just fine from the test server. The questions: Is this anything I should be concerned about? Is this a bug or a legit problem coming from my improper use of two servers against the same data. FWIW, I am using fcntl for both mbox read and write locks. procmail in the MDA on the production server, and its locking hierarchy <dotlock,fcntl>, which Timo previously approved. Thanks! Production dovecot -n output: > # 1.0.15: /usr/local/etc/dovecot.conf > listen: *:143 > ssl_listen: *:993 > disable_plaintext_auth: no > verbose_ssl: yes > login_dir: /var/run/dovecot/login > login_executable: /usr/local/libexec/dovecot/imap-login > login_processes_count: 12 > login_max_processes_count: 774 > verbose_proctitle: yes > first_valid_uid: 200 > mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u > mbox_write_locks: fcntl > mbox_dirty_syncs: no > auth default: > passdb: > driver: pam > userdb: > driver: passwd Test dovecot -n output: > # 1.1.3: /usr/local/etc/dovecot.conf > listen: *:143 > ssl_listen: *:993 > disable_plaintext_auth: no > verbose_ssl: yes > login_dir: /var/run/dovecot/login > login_executable: /usr/local/libexec/dovecot/imap-login > login_processes_count: 12 > login_max_processes_count: 774 > max_mail_processes: 1024 > verbose_proctitle: yes > first_valid_uid: 200 > mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u > mbox_write_locks: fcntl > mbox_dirty_syncs: no > auth default: > passdb: > driver: pam > userdb: > driver: passwd

2 6

[Dovecot] Lots of assertion PANICs in error log
by Yates Ian Mr (ITCS) 08 Oct '08

08 Oct '08

I have just upgraded to dovecot 1.1.2 and am seeing lots of the following panic messages filling up the error logs: dovecot: Aug 29 09:34:32 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Aug 29 09:34:32 Error: IMAP(user): Raw backtrace: imap [0x483888] -> imap [0x484293] -> imap [0x483a46] -> imap(index_mailbox_set_recent_seq+0) [0x453f80] -> imap(index_mailbox_set_recent_seq+0x43) [0x453fc3] -> imap [0x43b3e8] -> imap(mbox_sync+0x380) [0x43bdd0] -> imap [0x434bcd] -> imap(index_transaction_commit+0x3c) [0x454f3c] -> imap(cmd_copy+0x344) [0x4167d4] -> imap(cmd_uid+0x52) [0x41a6c2] -> imap [0x41b723] -> imap [0x41b6e8] -> imap [0x41b9ba] -> imap(client_input+0x63) [0x41bb93] -> imap(io_loop_handler_run+0x109) [0x48b029] -> imap(io_loop_run+0x28) [0x48a3f8] -> imap(main+0x3f2) [0x423272] -> /lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x337911c40b] -> imap [0x41578a] dovecot: Aug 29 09:34:32 Error: child 25658 (imap) killed with signal 6 This is just the latest example from this morning, there are plenty to choose from! My system setup is a RHEL4.6 64bit install. I have tried clearing out the old cache files (dovecot.index, dovecot.cache etc) for all the users but I'm still seeing these crash dumps filling my logs. Help! If you require any further information please let me know. I.

4 10

[Dovecot] Expire Plugin
by e-frog 06 Oct '08

06 Oct '08

I was struggling for a while to get the expire plugin to expunge mail. I was using (and still would like to use) PAM as passdb and passwd as userdb but with this I could not get the expire-tool to delete any mails. For debugging purpose I switch to passwd-file as userdb/passdb and enabled mail_debug=yes. 1. passwd-file contains home directory and userdb_mail (->working!) /etc/dovecot/dovecot.users: foo:{plain}xxxx:2004:100::/home/foo::userdb_mail=maildir:~/Maildir root@mail:# dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test Info: maildir: data=~/Maildir Info: maildir++: root=/home/foo/Maildir, index=, control=, inbox=/home/foo/Maildir Info: Trash: seq=1 uid=2586: Expunge Info: Trash: timestamp 1220392046 -> 1220451447 2. passwd-file contains home directory only (->not working!) /etc/dovecot/dovecot.users: foo:{plain}xxxx:2004:100::/home/foo root@mail:# dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test Info: maildir: data=/root/Maildir Info: maildir++: root=/root/Maildir, index=, control=, inbox=/root/Maildir Error: stat(/root/Maildir/.Trash/tmp) failed: Permission denied (euid=2005 egid=100) The expire-tool doesn't find foo's mailbox even if mail_location is set global in the configuration file (please see below). This is exactly the same result as when using PAM and passwd. So I guess there is something wrong with user lookup or setting/expanding HOME and MAIL in the expire-tool. root@mail:# dovecot -n # 1.1.3: /etc/dovecot/dovecot.conf log_path: /var/log/mail/dovecot.log info_log_path: /var/log/mail/dovecot.log ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_process_size: 16 max_mail_processes: 16 mail_location: maildir:~/Maildir mail_debug: yes mail_process_size: 64 mail_plugins: quota imap_quota expire auth default: passdb: driver: passwd-file args: scheme=plain /etc/dovecot/dovecot.users userdb: driver: passwd-file args: /etc/dovecot/dovecot.users socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: dovecot group: mail master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota_rule: *:storage=1GB quota_rule2: Trash:storage=10%% expire: Trash 1 Junk 1 expire_dict: proxy::expiredict dict: expiredict: db:/var/lib/dovecot/expire.db

2 4

[Dovecot] FETCH for mailbox mailboxname UID #1 got too little data: #2 vs #3
by Diego Liziero 05 Oct '08

05 Oct '08

I got it with multiple imaptest instances even with current dovecot-1.1 hg tree. I checked the emails with that UIDs and they are actually truncated. Some things I noted on these mails: - they are all with MIME multipart attachments. - the last multipart attachment is truncated - the truncated last line is not complete - the following line is the beginning of a new mail (From line) without any empty line after the truncated attachment. - in "got too little data: #2 vs #3" 0 <= #2 < #3 (zero included) - Content-Length: #4 is sometimes bigger than both #2 and #3, sometimes smaller. Regards, Diego.

2 4

Re: [Dovecot] GETQUOTAROOT (part 2)
by Patrick Medina 05 Oct '08

05 Oct '08

--- On Mon, 9/1/08, Timo Sirainen <tss(a)iki.fi> wrote: > From: Timo Sirainen <tss(a)iki.fi> > Subject: Re: [Dovecot] GETQUOTAROOT (part 2) > To: cpjmedina(a)yahoo.com > Cc: dovecot(a)dovecot.org > Date: Monday, September 1, 2008, 1:55 AM > On Aug 31, 2008, at 8:34 PM, Patrick Medina wrote: > > > Did some further testing: > > 1. maildirsize was initially = 5119 bytes > > 2. login via imap command line, verified GETQUOTAROOT > > returns correct quota, then logged out > > 3. sent test email and is delivered by deliver > > 4. maildirsize is updated but now = 5126 bytes > > (i.e. it is _not_ recreated) > > 5. log in again and GETQUOTAROOT now returns empty > > 6. quota thereafter no longer works > > OK, that's clearly a bug. If it's not gone in v1.1 > I'll look at it again. And in any case it would be more > reliable if you could have your userdb return the quota Upgraded to 1.1.2 from atrpms.net but I'm still getting the same behavior. I am trying to look at the quota plugin source (e.g. quota-maildir.c), but I'm very rusty in that aspect already. Thank you.

2 1

[Dovecot] Quota exceeded message
by Timo Sirainen 05 Oct '08

05 Oct '08

I just realized that "quota" word probably doesn't mean much to many non-native english speakers. Do even non-technical native speakers understand what "Quota exceeded" really means? It's sent by quota plugin, currently in two different situations: 1) To the user doing the operation via IMAP COPY/APPEND. 2) More importantly: If deliver rejects the mail, it's sent to the sender. Here are some ideas for improvements: "Mail storage disk quota exceeded" "User's mail storage disk quota exceeded" "Quota exceeded - not enough disk storage capasity for the user" Any better ideas? I think it should mention "quota" word in any case so that people who understand it would know immediately what the error message is about. The current code doesn't allow cleanly using separate messages for 1) and 2), so I'd prefer to use the same one. But if you've a great suggestion for them separately I could do it.

5 9

[Dovecot] Stupid question: Need to increase some connection limits
by Jon Callas 05 Oct '08

05 Oct '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I switch from one network to another, I sometimes get dovecot rejecting my connections. The error I get in the log is similar to: Sep 22 15:23:22 hostname dovecot: imap-login: Maximum number of connections from user+IP exceeded: user=<user>, method=METHOD, rip=1.2.3.4, lip=5.6.7.8 So the question is what parameter increases that? My five minutes of looking has failed me. Jon -----BEGIN PGP SIGNATURE----- Version: PGP Universal 2.6.3 Charset: US-ASCII wj8DBQFI2BtFsTedWZOD3gYRAs18AJ4wcFwyUl7JyVg5EO6jiZCWwt8URACdElWW 4pYB51ubkC1I+wf8RLuivYY= =yjuT -----END PGP SIGNATURE-----

2 1