August 2008 - dovecot

[Dovecot] Dovecot crashing
by Erinn Looney-Triggs 12 Aug '08

12 Aug '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sent an e-mail off as was detailed here: http://wiki.dovecot.org/MboxProblems for crashes but I also wanted to see if any of you folks had insight into the issue. Dovecot is crashing on a certain user inbox which is in mbox format as well as one of the users other mbox files. The crash doesn't exactly match what is listed in the aforementioned wiki page, so I thought their might be some other insight into this process or how to fix it. Here is the error in the log files: Aug 8 09:26:07 localhost dovecot: IMAP(user): UIDVALIDITY changed (1216167307 -> 1218134720) in mbox file /var/mail/user Aug 8 09:26:07 localhost dovecot: Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Aug 8 09:26:07 localhost dovecot: IMAP(user): Raw backtrace: imap [0x80f5257] -> imap [0x80f5aa4] -> imap(i_fatal+0) [0x80f53b3] -> imap(index_mailbox_set_recent_uid+0x62) [0x80b1af9] -> imap(index_mailbox_set_recent_seq+0x33) [0x80b1b6f] -> imap [0x808ef93] - -> imap [0x808f502] -> imap [0x808fe73] -> imap(mbox_sync+0x2b) [0x8090120] -> imap(mbox_storage_sync_init+0x8b) [0x80901ee] -> imap(mailbox_sync_init+0x1b) [0x80b61df] -> imap(mailbox_sync+0x1c) [0x80b6256] -> imap(cmd_select_full+0x13b) [0x805fad7] -> imap(cmd_select+0x19) [0x805fc63] -> imap [0x8062444] -> imap [0x8062679] -> imap [0x8062777] -> imap [0x80627b3] -> imap(client_input+0xb7) [0x8062941] -> imap(io_loop_handler_run+0x17d) [0x80ff704] -> imap(io_loop_run+0x35) [0x80fea32] -> imap(main+0xb0) [0x806dd99] -> /lib/libc.so.6(__libc_start_main+0xdc) [0xc31dec] -> imap [0x805a151] Aug 8 09:26:07 localhost dovecot: child 4740 (imap) killed with signal 6 Any ideas or thoughts? Thanks, - -Erinn Here are the pertinents: ./dovecot --version 1.1.2 ./dovecot -n # 1.1.2: /usr/local/dovecot/etc/dovecot.conf protocols: pop3s imaps ssl_cert_file: /usr/local/adm/config/openssl/certs/imapd.pem ssl_key_file: /usr/local/adm/config/openssl/certs/imapd.pem login_dir: /usr/local/dovecot/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 max_mail_processes: 128 mail_location: mbox:~/mail:INBOX=/var/mail/%u 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_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 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: passdb: driver: pam userdb: driver: passwd -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFInHWxJqsQ+sq8O4ERAoklAJ4i1Ja3D8OcBjpyPZ6NJ/1A+l/rvQCgiu7B b/dk0dCGNd5zNBgHGXULHyc= =F0sY -----END PGP SIGNATURE-----

2 1

[Dovecot] Possible bug in v1.1.1
by John Wood 12 Aug '08

12 Aug '08

Greetings, I recently upgraded our server from Dovecot 1.0.14 to 1.1.1. I am building using the FreeBSD ports system, so nothing is custom aside from the flags set there. dovecot fell down a few days after the update with: pid 1823 (imap), uid 1000: exited on signal 11 the mail log shows: Jul 4 14:36:07 hostname dovecot: IMAP(username): Corrupted index cache file /home/username/mail/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 10462 Jul 4 14:36:07 hostname dovecot: child 1823 (imap) killed with signal 11 unfortunately I do not have a core. The closest thing I could find in the Changelog is: v1.1.rc13 2008-06-20 Timo Sirainen <tss(a)iki.fi> - Message parser: Fixed assert-crash if cached MIME structure was broken. but, it does not appear to be the same issue. The upgrade file mentions issues with cache/index files, but they are related to downgrades. The rest of the relative information: Dovecot version: v1.1.1 Operating system: FreeBSD 6.2 p11 CPU architecture: x86 Filesystem you used: FreeBSD UFS Message that caused the crash: attached Dovecot configuration: 1.1.1: /usr/local/etc/dovecot.conf Warning: mail_extra_groups setting was often used insecurely so it is now deprecated, use mail_access_groups or mail_privileged_group instead protocols: imap imaps pop3 pop3s listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(pop3): 127.0.0.1:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_ca_file: /etc/ssl/godaddy_cert/gd_intermediate.crt ssl_cert_file: /etc/ssl/godaddy_cert/hostname.cert ssl_key_file: /etc/ssl/godaddy_cert/hostname.key ssl_parameters_regenerate: 400 login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: Hostname ready. login_process_per_connection: no login_process_size: 128 verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_extra_groups: mail mail_access_groups: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u mbox_read_locks: fcntl dotlock mbox_write_locks: fcntl dotlock mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix I have not been able to repeat this so far. Thanks, John

2 3

[Dovecot] Auth message
by Pavel Shirov 12 Aug '08

12 Aug '08

Recently my network was scanned. Various services was scanned, and checking the logs of mail server the following string draw my attention: mail dovecot: pop3-login: Disconnected: user=<ttejmgpfip>, method=PLAIN, rip=87.228.15.180, lip=x.x.x.x This looks weird to me, because pop3-login: Disconnected looks like succesful login attempt to me. I have no such user named ttejmgpfip exits ofc. I've check what dovecot writes to log if try PLAIN login method with random login/password, and it's "Aborted login". As I'm using SQL backend for user/pass database, I'm afraid that I might have something misconfigured and a possible sql-injection or something else allowed attacker to "login" with random password. Or my worries are groundless and I can get such message in some case of unsuccessful login? Running dovecot 1.0.rc15 (CentOS 5). Here is how my sql auth done: default_pass_scheme = MD5 password_query = SELECT password FROM mailbox WHERE active = '1' AND (LEFT(username, INSTR(username, '@')-1) = '%u' OR username = '%u') user_query = SELECT maildir as home, 6000 AS uid, 6000 AS gid, domain FROM mailbox WHERE LEFT(username, INSTR(username, '@')-1) = '%u' OR username = '%u' I have such query so it is possible for a user to login either as user@domain or just as user (I have single domain).

3 2

[Dovecot] About domains in antispam plugin
by Eduardo Morales Chavez 12 Aug '08

12 Aug '08

Hi there, I have the problem that the antispam filter is looking in a different subdirectory (I think is the domain subfolder) than the actuallly used i.e., The following error message is constant: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Aug 12 12:07:58 mail dspam[4540]: Unable to open file for reading: /var/spool/dspam/data/local/itadmin/itadmin.sig/48a1c36c24 9461173910573.sig: No such file or directory Aug 12 12:07:58 mail dspam[4541]: Unable to open file for reading: /var/spool/dspam/data/local/itadmin/itadmin.sig/48a1c36c24 9461173910573.sig: No such file or directory ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The file in the error exists but in a different subdirectory than the one AntiSpam Plugin is looking: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ls -l /var/spool/dspam/data/local/itadmin/itadmin.sig/48a1c36c249461173910573.sig ls: cannot access /var/spool/dspam/data/local/itadmin/itadmin.sig/48a1c36c249461173910573.sig: No such file or directory ls -l /var/spool/dspam/data/mydomain.com/itadmin/itadmin.sig/48a1c36c249461173910573.sig -rw-rw---- 1 root dspam 968 Aug 12 12:07 /var/spool/dspam/data/mydomain.com/itadmin/itadmin.sig/48a1c36c249461173910573.sig ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I looked at the /etc/dovecot/dovecot.conf for a line containing a local doman vs mydomain.com but there's nothing even in the comments. So If there's something I'm missing I'd be glad you to enlight me. Thanks a lot in advance for you help. Rgds, Eduardo

1 0

[Dovecot] NFS vs CIFS - and Dovecot
by Daniel L. Miller 12 Aug '08

12 Aug '08

I've seen a number of posts discussing NFS based storage and issues with Dovecot. When the term "NFS" is used - does this exclusively refer to the Linux NFS network file system, or is it a generic reference to any network file system? I don't recall seeing any posts referencing issues with CIFS or SMBFS - is this because no one is using it, or because it just works instead of fiddling with NFS? -- Daniel

2 1

[Dovecot] Install from source of dovecot 1.1.2
by Guy 12 Aug '08

12 Aug '08

Hi guys, I have what I'm sure is a stupid question. I'm trying to install Dovecot 1.1.2 from source and my command sequence is this: cd dovecot-1.1.2 ./configure --prefix=/usr --exec-prefix=/usr --with-mysql --with-storagesmaildir --sysconfdir=/etc/dovecot make make install cd ../dovecot-sieve-1.1.5 ./configure --with-dovecot=../dovecot-1.1.2 make make install I don't get any errors during either install I've done the odd config on dovecot to try and keep it as close to the install dirs used by the Dovecot package included with Ubuntu. Once it's done, dovecot -n still looks in /usr/local/etc and when I try and start dovecot it looks for the libexec dir in /usr/local instead of /usr. Is there something I'm missing on the configure? I've very, very little experience (rather obviously) installing directly from source so any advice would be greatly appreciated. Thanks Guy -- Don't just do something...sit there!

5 5

[Dovecot] Cyrus vs Dovecot
by Mathieu Kretchner 12 Aug '08

12 Aug '08

First of all : forgive me for my poor English Hello all, I've to compare cyrus with dovecot for my work. Because these are the only solutions that could fit our needs. Unfortunately I really don't know a lot about dovecot and I would like to have some of its assets. Here are the properties of the versus table I've done : dovecot cyrus Installation: Update: Migration from cyrus : Migration from dovecot : functionalities : Management : Local Delivery : availability : Security : Indexes management : NFS compatibility : Scalability : Configuration : interoperability : Sieve filter : Documentation : Quota capability : Performance : IMAP capability : So I know this can scared you, but If you have some asset for dovecot, It could be great and a lot more FAIR !! Thank you in advance for your advice.

7 14

[Dovecot] GlusterFS
by Jeroen Koekkoek 12 Aug '08

12 Aug '08

Hi everybody, We use a Dovecot setup with GlusterFS. Dovecot 1.1.2 and GlusterFS 1.3.9. I enabled the following options (I don't have posix-locks translators): lock_method = dotlock dotlock_use_excl = no mmap_disable = yes mail_nfs_index = yes mail_nfs_storage = yes I receive the following error message. Aug 7 09:38:51 mta2 dovecot: POP3(somebody(a)domain.tld): nfs_flush_fcntl: fcntl(/var/vmail/domain.tld/somebody/Maildir/dovecot.index, F_RDLCK) failed: Function not implemented I think that I can disable mail_nfs_index to fix these messages. Has anybody had the same problem, if so, how did you solve it? Kind regards, Jeroen Koekkoek

5 6

[Dovecot] proxy_maybe and IPv6
by Matthieu Herrb 12 Aug '08

12 Aug '08

Hi, Using dovecot 1.1.2 on a dual-stack server, with the 'proxy_maybe' attribute to forward some clients to another server, it seems that only clients connecting with the same protocol version as the one used by address in the 'host' attribute in the password db are recognized as local. If an IPv4 address is specified as 'host', a dovecot proxy is created for clients connecting using IPv6 to this server, and symmetrically if the proxy is specified as an IPv6 address, clients connecting through IPv4 will get forwarded to the v6 address. Is there a way to avoid that? -- Matthieu Herrb

2 3

[Dovecot] Good news for CPanel users
by Marshal Newrock 11 Aug '08

11 Aug '08

In response to a feature request for cpanel to have native support for dovecot: Rudimentary support was added in 11.23. Full support for Dovecot will be available in 11.24. -- Marshal Newrock 517-679-0699 x223 FreedomBI, LLC - http://www.freedombi.com

1 0

[Dovecot] nombre de compte imap/ rapide rapide
by Mathieu Kretchner 11 Aug '08

11 Aug '08

find . -type d -mindepth 2 -maxdepth 3 -print | sort | uniq | grep -vE "user$" | wc -l

1 0

[Dovecot] optionnal arguments to ntlm_auth helper
by François LEGAL 10 Aug '08

10 Aug '08

Hello, I'm setting up (at least I try) to set up network services with single sign on. I could build and configure dovecat to use samba's ntlm_auth helper to achieve ntlm authentication of imap users. The point is, I wanted to restrict which users could actually authenticate through ntlm. The ntlm_auth helper has this ability with the --require-membership-of=... command line parameter. I first tried (unsuccessfully) to add this parameter to the auth_winbind_helper_path token in dovecot.conf, and figured out by checking the source that this was not possible. I then decided to patch the source so that one can pass any argument to the ntlm_auth helper by specifying at new line in dovecot.conf with the token "auth_winbind_helper_args" (for instance, what I wanted to do is "auth_winbind_helper_args = --require-membership-of=... ") Well, here comes the patch. It is to be used with recent 1.1.2 release. Best regards François

3 2

[Dovecot] tcp-wrappers.patch
by Edgar Fuß 09 Aug '08

09 Aug '08

I'd like to see tcp-wrappers.patch getting integrated into dovecot. I ported the original 1.0 patch to 1.1, but would prefer not to have to maintain another local patch. As the name suggests, the patch adds libwrap support to dovecot. We use is to limit access from outside our network to secure (imaps/pop3s) protocols only and to exclude certain internal addresses from accessing dovecot in general. I fully understand Timo's concern of people not reading documentation and then whining that librwapping doesn't work whereas they simply forgot to put hosts.{allow,deny} into the login chroot. Would it be acceptable if either dovecot itself or the init script copies /etc/hosts.{allow,deny} into the chroot (unless it's already there)? Also, dovecot could probably complain/abort/turn off libwrap if these files are missing in the login chroot. The problem mainly occurs with the default (Linux) setting of login_dir = /var/run/dovecot/login; on NetBSD, I use /var/chroot/dovecot-login instead, which doesn't get wiped out at boot. Comments? Suggestions? Oh, yes, managesieve (which uses src/login-common) would need a slight update, too.

3 5

[Dovecot] Dovecot 1.1.1 killed with SIGABRT
by Andreas M. Kirchwitz 08 Aug '08

08 Aug '08

Hi folks, with Dovecot 1.1.1, I've had two "crashes" (SIGABRT) recently. Dovecot 1.1.1 has been compiled from source and is running on Fedora 8 Linux 32 Bit (all patches) with custom OpenSSL 0.9.8h. [ output of "dovecot -n" ] # 1.1.1: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u auth default: mechanisms: plain login digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd userdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd First, the "small" problem with Pine 4.64: Jul 20 03:17:04 linux dovecot: imap-login: Login: user=<user1>, method=CRAM-MD5, rip=138.201.2.8, lip=138.201.2.2, TLS Jul 20 03:17:53 linux dovecot: IMAP(user1): UIDVALIDITY changed (1215137127 -> 1216072777) in mbox file /home/user1/Mail/Trash Jul 20 03:17:53 linux dovecot: Panic: IMAP(user1): file mail-index-transaction.c: line 548 (mail_index_transaction_get_next_uid): assertion failed: (recs[count-1].uid >= next_uid) Jul 20 03:17:53 linux dovecot: IMAP(user1): Raw backtrace: imap [0x80cf2f0] -> imap [0x80cf34a] -> imap [0x80cec5c] -> imap [0x80ad621] -> imap [0x80ae56b] -> imap(mail_cache_get_first_new_seq+0x12) [0x80a1d82] -> imap(mail_cache_field_want_add+0x8d) [0x80a555d] -> imap(index_mail_parse_header_init+0x1cc) [0x80964ac] -> imap(index_mail_cache_parse_init+0x4e) [0x809696e] -> imap(mbox_save_init+0x457) [0x807d4a7] -> imap(mailbox_save_init+0x51) [0x809fd71] -> imap(mail_storage_copy+0xc1) [0x809df31] -> imap(cmd_copy+0x1d2) [0x805b1f2] -> imap(cmd_uid+0x59) [0x805f489] -> imap [0x805fe2c] -> imap [0x805fed5] -> imap [0x8060695] -> imap(client_input+0x5e) [0x80608ae] -> imap(io_loop_handler_run+0x100) [0x80d6c30] -> imap(io_loop_run+0x28) [0x80d5dc8] -> imap(main+0x4a1) [0x80683d1] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] -> imap [0x805a211] Jul 20 03:17:53 linux dovecot: child 19853 (imap) killed with signal 6 The user didn't configure his Pine properly. He used IMAP to access his INBOX, but he forgot to configure this for all other folders as well. Now, Pine modified /home/user1/Mail/Trash directly, and when Dovecot stumbled upon this file it killed itself with signal 6. The problem is not reproducible. After this single failure, Dovecot doesn't seem to have any problems with the folder. However, instead of this panic operation, Dovecot maybe could issue a warning or error response to the client so that the user (hopefully) gets a clue about what's going wrong. Second, the "big" problem with Thunderbird 2.0.0.14: Jul 12 01:04:06 linux dovecot: imap-login: Login: user=<user2>, method=CRAM-MD5, rip=138.201.2.4, lip=138.201.2.2, TLS Jul 12 01:04:45 linux dovecot: Panic: IMAP(user2): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Jul 12 01:04:45 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf2f0] -> imap [0x80cf34a] -> imap [0x80cec5c] -> imap [0x809ccba] -> imap [0x8080d10] -> imap(mbox_sync+0x522) [0x80817d2] -> imap [0x807a334] -> imap(index_transaction_commit+0x4e) [0x809d99e] -> imap(cmd_copy+0x35f) [0x805b37f] -> imap(cmd_uid+0x59) [0x805f489] -> imap [0x805fe2c] -> imap [0x805fed5] -> imap [0x8060695] -> imap(client_input+0x5e) [0x80608ae] -> imap(io_loop_handler_run+0x100) [0x80d6c30] -> imap(io_loop_run+0x28) [0x80d5dc8] -> imap(main+0x4a1) [0x80683d1] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] -> imap [0x805a211] Jul 12 01:04:45 linux dovecot: child 25672 (imap) killed with signal 6 [happens over and over in an endless loop until Thunderbird is killed] This has been a nasty one. Different user, different mail client. INBOX with 350 messages in total, 3 of them new. Started Thunderbird, index page is displayed fine, then clicked on one of the 3 new messages to read it. For no apparent reason, Dovecot dies with signal 6. Thunderbird reconnected automatically, and then Dovecot dies again. Nice endless loop ... Stopping and restarting the complete Dovecot subsystem with the help of the init.d script didn't help. Finally the crashes stopped after removing the cache files in /home/fubar/Mail/.imap/INBOX. It's obvious that the cache files got corrupted somehow. There was plenty of disk space free. And the cache files have been freshly created from scratch with Dovecot 1.1.0. Other folders were not affected. Except Dovecot, nobody ever touches these cache files. Well, the good news is, it stopped crashing after removing the cache files. The bad news is, without the cache files (which I removed) the problem cannot be reproduced. So, there's nothing more to offer than these two backtraces. Both crashes are not related to each other and happened to different users with different clients. Maybe the backtraces and my descriptions help to find what's going wrong or how to make Dovecot behave more robustly. If there's any additional information needed, please let me know. Sorry that I didn't save the corrupted cache files. Greetings, Andreas

3 6

Re: [Dovecot] Auth message
by Pavel Shirov 08 Aug '08

08 Aug '08

Further testing show that such message could occur simply by providing random username/password and termination session afterwards (not sending QUIT).

1 0

[Dovecot] Dovecot auto vacation with sieve doesn't work
by CJ Keist 08 Aug '08

08 Aug '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry if this comes in twice, I sent this first from my test account. - --------- Guys, I'm running out of hair to pull out ;). Can anyone out there say that this does work?? To me this is looking like a bug and I'm not sure whether it's the sieve plugin or the dovecot deliver program. I have also had no luck the the "reject" sending any reply back to the sender. My setup: OS: Solaris 10 sparc platform postfix: 2.5.2 dovecot: 1.1.2 sieve plugin: 1.1.5 I'm going back forth between procmail and sieve and having no luck. procmail will send the reply to the sender but doesn't deliver the message to the recipient. Sieve will deliver the message to the recipient but doesn't send the reply to the sender. Now if I can just combine the two, I'll be in business. Postfix mail command: mailbox_command = /userM/mail-services/dovecot/libexec/dovecot/deliver - -d $USER* * Dovecot -n (I've made some changes from my previous posting namely with the master_auth settings) # 1.1.2: /userM/mail-services/dovecot/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 3072). Either grow the limit or change login_max_processes_count and max_mail_processes settings base_dir: /userM/mail-services/dovecot/var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /userM/mail-services/dovecot/etc/ssl/dovecot.pem ssl_key_file: /userM/mail-services/dovecot/etc/ssl/privkey.pem ssl_parameters_regenerate: 0 ssl_cipher_list: MEDIUM:!LOW disable_plaintext_auth: no login_dir: /userM/mail-services/dovecot/var/run/dovecot/login login_executable(default): /userM/mail-services/dovecot/libexec/dovecot/imap-login login_executable(imap): /userM/mail-services/dovecot/libexec/dovecot/imap-login login_executable(pop3): /userM/mail-services/dovecot/libexec/dovecot/pop3-login login_greeting: Cyrus ready. login_max_processes_count: 1024 max_mail_processes: 1024 mail_location: mbox:~/:INBOX=/userM/mail/%u mail_debug: yes mmap_disable: yes mail_nfs_index: yes mail_executable(default): /userM/mail-services/dovecot/libexec/dovecot/imap mail_executable(imap): /userM/mail-services/dovecot/libexec/dovecot/imap mail_executable(pop3): /userM/mail-services/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /userM/mail-services/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /userM/mail-services/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /userM/mail-services/dovecot/lib/dovecot/pop3 auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: pam passdb: driver: passwd args: blocking=yes userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /userM/mail-services/postfix/var/private/auth mode: 432 user: postfix group: postfix master: path: /userM/mail-services/dovecot/var/run/dovecot/auth-master mode: 384 user: postfix group: postfix My .dovecot.sieve file: require ["vacation"]; if header :matches "subject" "*" { vacation :days 30 :addresses "cj.keist(a)colostate.edu" :subject "Automatic response to: ${1}" "I'm away -- send mail to foo in my absence"; } I made some modifications to the vacation reply base on the following URL: http://ietfreport.isoc.org/idref/draft-ietf-sieve-vacation/ In my testing I know the sieve plugin is reading my .dovecot.sieve script and creating the .dovecot.sievec, but that is as for as it goes. The .dovecot.lda-dupes file is not being created (or any .dovecot.sieve.err file) and no reply is even being attempted from the logs: Aug 6 11:30:51 mail2.engr.colostate.edu dovecot: [ID 107833 mail.info] auth(def ault): new auth connection: pid=27187 Aug 6 11:30:51 mail2.engr.colostate.edu postfix/smtpd[27187]: [ID 197553 mail.i nfo] connect from akron.colostate.edu[129.82.103.160] Aug 6 11:30:51 mail2.engr.colostate.edu postfix/smtpd[27187]: [ID 197553 mail.i nfo] setting up TLS connection from akron.colostate.edu[129.82.103.160] Aug 6 11:30:51 mail2.engr.colostate.edu postfix/smtpd[27187]: [ID 197553 mail.i nfo] Anonymous TLS connection established from akron.colostate.edu[129.82.103.16 0]: TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits) Aug 6 11:30:52 mail2.engr.colostate.edu postfix/smtpd[27187]: [ID 197553 mail.i nfo] 16E2059984: client=akron.colostate.edu[129.82.103.160] Aug 6 11:30:52 mail2.engr.colostate.edu postfix/cleanup[27192]: [ID 197553 mail .info] 16E2059984: message-id=<3b676ae5f90fadad863930dcc61db3f8.squirrel@webmail .engr.colostate.edu> Aug 6 11:30:52 mail2.engr.colostate.edu postfix/smtpd[27187]: [ID 197553 mail.i nfo] disconnect from akron.colostate.edu[129.82.103.160] Aug 6 11:30:52 mail2.engr.colostate.edu postfix/qmgr[18021]: [ID 197553 mail.in fo] 16E2059984: from=<joeblow(a)engr.colostate.edu>, size=1877, nrcpt=1 (queue act ive) Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 315030 mail.info] Lo ading modules from directory: /userM/mail-services/dovecot/lib/dovecot/lda Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 619685 mail.info] Mo dule loaded: /userM/mail-services/dovecot/lib/dovecot/lda/lib90_cmusieve_plugin. so Aug 6 11:30:52 mail2.engr.colostate.edu dovecot: [ID 107833 mail.info] auth(def ault): master in: USER 1 cjay service=deliver Aug 6 11:30:52 mail2.engr.colostate.edu dovecot: [ID 107833 mail.info] auth-wor ker(default): passwd(cjay): lookup Aug 6 11:30:52 mail2.engr.colostate.edu dovecot: [ID 107833 mail.info] auth(def ault): master out: USER 1 cjay system_user=cjay uid=10946 gid=32 home=/top/admin/ENS/people/cjay/home Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 868608 mail.info] au th input: cjay Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 868608 mail.info] au th input: system_user=cjay Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 868608 mail.info] au th input: uid=10946 Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 868608 mail.info] au th input: gid=32 Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 868608 mail.info] au th input: home=/top/admin/ENS/people/cjay/home Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 848615 mail.info] mb ox: data=/top/admin/ENS/people/cjay/home/:INBOX=/userM/mail/cjay Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 885103 mail.info] fs : root=/top/admin/ENS/people/cjay/home, index=, control=, inbox=/userM/mail/cjay Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 223526 mail.info] cm usieve: Using sieve path: /top/admin/ENS/people/cjay/home/.dovecot.sieve Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 507699 mail.info] cm usieve: Executing script /top/admin/ENS/people/cjay/home/.dovecot.sievec Aug 6 11:30:53 mail2.engr.colostate.edu deliver(cjay): [ID 702911 mail.info] ms gid=<3b676ae5f90fadad863930dcc61db3f8.squirrel(a)webmail.engr.colostate.edu>: save d mail to INBOX Aug 6 11:30:53 mail2.engr.colostate.edu postfix/local[27193]: [ID 197553 mail.i nfo] 16E2059984: to=<cjay(a)engr2.colostate.edu>, relay=local, delay=1.2, delays=0 .32/0.08/0/0.82, dsn=2.0.0, status=sent (delivered to command: /userM/mail-servi ces/dovecot/libexec/dovecot/deliver -d $USER) Aug 6 11:30:53 mail2.engr.colostate.edu postfix/qmgr[18021]: [ID 197553 mail.in fo] 16E2059984: removed Aug 6 11:34:12 mail2.engr.colostate.edu postfix/anvil[27190]: [ID 197553 mail.i nfo] statistics: max connection rate 1/60s for (smtp:129.82.103.160) at Aug 6 1 1:30:51 Aug 6 11:34:12 mail2.engr.colostate.edu postfix/anvil[27190]: [ID 197553 mail.i nfo] statistics: max connection count 1 for (smtp:129.82.103.160) at Aug 6 11:3 0:51 Aug 6 11:34:12 mail2.engr.colostate.edu postfix/anvil[27190]: [ID 197553 mail.i nfo] statistics: max cache size 1 at Aug 6 11:30:51 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFImeYWA29OFr7C6jcRAkj+AJ0eKINCZmRDWh8gSjbW86Ga6DPWlgCeL/1M rVvbvn6al/3fLep60h2Lxg4= =veQm -----END PGP SIGNATURE-----

3 5

[Dovecot] Expire Plugin - LDA with Vpopmail errors
by Ron Culler 08 Aug '08

08 Aug '08

I am trying to setup Dovecot to use the expire plugin and wanted to use the LDA so I can ensure the messages are indexed as they are delivered to the mailboxes. This system is only accessed via a webmail interface Using dovecot-1.1.2 and Vpopmail with Qmail Dovecot.conf file base_dir = /usr/local/var/run/dovecot/ protocols = imap disable_plaintext_auth = no shutdown_clients = yes log_path = /var/log/dovecott info_log_path = /var/log/dovecott log_timestamp = "" ssl_disable = yes login_dir = /usr/local/var/run/dovecot/login login_user = dovecot login_process_per_connection = yes login_processes_count = 3 login_max_processes_count = 128 mail_location = maildir:~/Maildir namespace private { separator = . prefix = INBOX. inbox = yes } verbose_proctitle = yes first_valid_uid = 89 #last_valid_uid = 0 maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = no protocol imap { listen = 127.0.0.1:4143 imap_max_line_length = 65536 login_greeting_capability = yes mail_plugins = expire } protocol lda { mail_plugins = expire log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log } plugin { # Trash and its children 7d, Spam 30d expire = Trash 7 expire_dict = proxy::expire } auth default { mechanisms = plain passdb vpopmail { args = } userdb vpopmail { } user = vpopmail count = 1 ssl_require_client_cert = no } I see errors in the /var/log/dovecot-deliver.log deliver (email@addrss) Error: Can't connect to auth server at /usr/local/var/run/dovecot//auth-master: no such file or directory. What do I need to do to create this? Ron Culler

2 1

[Dovecot] virtual domains and SSL certificates
by Kacper Wysocki 07 Aug '08

07 Aug '08

Hi all, I have dovecot 1.1.0 setup to access vpopmail accounts for several virtual domains. Dovecot IMAP is accessed through several virtual domains as well, ie mail.foo.com an d mail.bar.com The problem is that the configuration file specifies only one certificate file for dovecot, which means only one Common Name, which means one cannot provide one server cert that will match mail.foo.com AND mail.bar.com, and either mary(a)foo.com or bob(a)bar.com will get a "Security Error: Domain Name Mismatch" in their mail client when connecting through IMAPS. How can I avoid this domain name mismatch error? Regards, Kacper Wysocki

4 4

[Dovecot] RESOLVED: dovecot-imap displays empty domainalias mailboxen
by Kacper Wysocki 07 Aug '08

07 Aug '08

On Thu, Jul 31, 2008 at 5:21 PM, Kacper Wysocki <kacperw(a)online.no> wrote: > I'm using dovecot 1.0.13 as the IMAPS frontend for a vpopmail/qmail > virtual domain setup. Dovecot is set up as follows: > passdb vpopmail{ > } > userdb vpopmail{ > } > > I've added a domain alias for the main domain with vaddaliasdomain and > email to post@aliasdomain is delivered to post@maindomain and can be > checked with pop. > > However, when I try to check IMAP through the account post@aliasdomain > I am confronted with an empty mailbox. If I log in using > post@maindomain I get the expected contents. > > Why can't my users log in using user@aliasdomain to check their emails? Update: dovecot can't find the mail directory because of mail_location = maildir:/var/vpopmail/domains/%d/%n/Maildir and dovecot doesn't know anything about domain aliases. ln -s ~vpopmail/domains/maindomain ~vpopmail/domains/aliasdomain fixes the problem for dovecot. -K

1 0

Re: [Dovecot] Dovecot 1.1 Quota Plugin Configuration?
by David Reid 07 Aug '08

07 Aug '08

Charles Marcus wrote: > On 8/7/2008 8:39 AM, David Reid wrote: >> With 1.0 I had the quota plugin set to allow some accounts to have no >> quota by setting their size (in bytes) to 0 (via mysql). Following the >> upgrade to 1.1 this no longer seems to work and has resulted in a lot of >> annoyed people having messages bumped :-( >> >> The config I have is as follows... >> >> quota = maildir >> quota_rule = *:storage=15M >> quota_rule2 = Trash:ignore >> quota_rule3 = INBOX.Trash:ignore >> quota_rule4 = INBOX.SpamTrain:ignore >> quota_rule5 = SpamTrain:ignore >> >> In the sql.conf I get the quota for each mailbox using this line >> >> user_query = SELECT '/var/vmail/%d/%n' as home, >> 'maildir:/var/vmail/%d/%n' as mail, xxx AS uid, xxx AS gid, >> concat('maildir:storage=', mb_quota) AS quota FROM >> mailboxes WHERE mb_mbname = '%u' AND mb_active = '1' >> >> With this setup when I have a mb_quota set to 0 it simply bounces all >> messages for the mailboxes that should have no quota. >> >> Any ideas how I need to fix this? > > You could start by not posting the same question twice in a 24 hour > period, especially when your question has already been answered. Apologies, but as the problem affected the mailbox I posted from I missed the reply and hence the answer. > > You are trying to use the same mysql query from 1.0 for 1.1 and it won't > work. > > http://wiki.dovecot.org/Quota/1.1 > Knowing the sql needed to be adjusted I have made the changes. The wiki page says that the uid and guid can be set in the config file, but doesn't give any indication of the lines to use. Maybe the information could be added? Thanks for your (duplicate) reply. david

1 0

[Dovecot] Dovecot 1.1 Quota Plugin Configuration?
by David Reid 07 Aug '08

07 Aug '08

With 1.0 I had the quota plugin set to allow some accounts to have no quota by setting their size (in bytes) to 0 (via mysql). Following the upgrade to 1.1 this no longer seems to work and has resulted in a lot of annoyed people having messages bumped :-( The config I have is as follows... quota = maildir quota_rule = *:storage=15M quota_rule2 = Trash:ignore quota_rule3 = INBOX.Trash:ignore quota_rule4 = INBOX.SpamTrain:ignore quota_rule5 = SpamTrain:ignore In the sql.conf I get the quota for each mailbox using this line user_query = SELECT '/var/vmail/%d/%n' as home, 'maildir:/var/vmail/%d/%n' as mail, xxx AS uid, xxx AS gid, concat('maildir:storage=', mb_quota) AS quota FROM mailboxes WHERE mb_mbname = '%u' AND mb_active = '1' With this setup when I have a mb_quota set to 0 it simply bounces all messages for the mailboxes that should have no quota. Any ideas how I need to fix this? david

1 0

[Dovecot] Experience moving mailboxes from Dovecot 0.99.14 to Dovecot 1.07 => Improvement possible
by Benoît DESLOGES 07 Aug '08

07 Aug '08

Hi, This small mail to share my observation about a recent move of mailboxes between two servers and ask about explanation and/or improvement about UIDL in dovecot. SV1 : Dovecot 0.99.14 / Red Hat Fedore Core 4 SV2 : Dovecot 1.07 / CentOS 5.2 Mailboxes in /var/spool/mail on the twoo servers. Test will be done with outlook express with option "leave message on server" checked. Goal is simply to move users mailboxes from SV1 to SV2 without re-downloading all messages. Try 1: - Stop dovecot on SV2 - Clear all dovecot indexes on SV2 - Rsync of my mailbox - Start dovecot on SV2 - Update pop setting in outlook and send/receive Result : => starting to download 3000 mails... After some debug, I discovered that UIDL where not of the same format => put pop3_uidl_format = %v.%u in dovecot.conf of SV2. Try 2: Same operations as Try1 Result : => starting to download 3000 mails... UIDL's where of the same format but values where not corresponding... Teleting on SV1 and asking UIDL, last value is xxxxxxxxxx.85878. On SV2, xxxxxxxxxx.85879 was the FIRST value of the list. Conclusion for the moment, Dovecot has a problem with the detection of existing UID of the moved mailbox. Comparaison of first header found from the two mailboxes show ... differences ! SV1 give the following : (...) X-UID: 70570 Content-Length: 1561 X-IMAPbase: xxxxxxxxxx 85845 $MDNSent X-Keywords: (...) SV2 give the following (after first POP attempt) : (...) Content-Length: 1561 X-IMAPbase: xxxxxxxxxx 0000089204 $MDNSent X-Keywords: X-UID: 85846 (...) Observation : X-UID: 85846 is not at the same place in the header. Try 3: - Stop dovecot on SV2 - Clear all dovecot indexes on SV2 - Rsync of my mailbox - Edit mailbox and move X-UID header after the X-Keywords header - Start dovecot on SV2 - Update pop setting in outlook and send/receive Result : => OK. Is that normal that dovecot is impacted by the position of the headers ? Maybe some improvement possible ? Maybe theyre is another method to make my migration ? Any observation or comment is welcome... -- Benoît Desloges Network Engineer

7 8

[Dovecot] Fwd: Re: sasl parameters missing (in postfix)
by Daniel Black 07 Aug '08

07 Aug '08

In response to my request for postfix to support dovecot auth arguments I got the forwarded reply. If someone gets around to this before me I won't be offended. ------------ Story is I deployed a webmail with certificate based authentication that substitutes a global master password (http://wiki.dovecot.org/Authentication/MasterUsers) when the certificate matches. The webmail accesses the inbox by imap and reuses the password for smtp through postfix. I configured dovecot sasl authentication to allow a particular global password to be allowed from one IP address of the webmail server. Unfortuanately it seems as though postfix doesn't pass rip= (remote ip) or the other AUTH parameters of the protocol (http://dovecot.org/doc/auth-protocol.txt) Is adding these parameters to postfix's sasl authentication a useful feature request? ---------- Forwarded Message ---------- Subject: Re: sasl parameters missing Date: Thu, 7 Aug 2008 From: Wietse Venema <wietse(a)porcupine.org> To: Daniel Black <daniel.subs(a)internode.on.net> Daniel Black: > Thanks Wietse, > > On Tue, 5 Aug 2008 09:30:44 am Wietse Venema wrote: > > Postfix passes the information in the SMTP client's AUTH command. > > This is how I got the Dovecot extension from Timo. If someone is > > willing to monitor his docs for changes, > > it seems fairly stable. Going off the doc/auth-protocol.txt changelog > Nov 12 2006 lport/rport was added. > Aug 07 2005 changed valid-client-cert to ssl-valid-cert > Oct 22 2004 original documentation > > Current implementation of the authentication server in dovecot seems to ignore > parameters it doesn't understand. > > > then they are welcome to do so. I won't. > > On the basis of this apparent stability and compatibility would you consider > accepting a patch? Yes. No promise, though, that it will be adopted. One consideration is that Postfix does not talk directly to Dovecot, but instead talks to an abstraction layer that is used for both Cyrus SASL and for Dovecot. Obviously, that XSASL abstraction layer must not be made specific to the underlying Cyrus SASL or Dovecot implementation. The solution therefore is not to extend XSASL functions with one extra argument for each Dovecot feature. Apart from being Dovecot-specific, functions with many parameters are difficult to update correctly; compilers can't always tell that two arguments should be swapped. I solved the problem of many-parameter functions by using macros such as TLS_SERVER_START(). This gives more assurance that data is passed correctly, and it less likely to break due to human maintainer error. Wietse ------------------------------------------------------- -- Daniel Black -- Proudly a Gentoo Linux User. Gnu-PG/PGP signed and encrypted email preferred http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x76677097 GPG Signature D934 5397 A84A 6366 9687 9EB2 861A 4ABA 7667 7097

1 0

[Dovecot] Purpose of files under .imap
by Kenneth Porter 07 Aug '08

07 Aug '08

I've got a user with an unusable account. Tbird just sits in a loop endlessly logging in over and over when a particular folder is selected. What files under .imap associated with that folder can be safely deleted? What's stored in all of them? I see all of these: .customflags dovecot.index dovecot.index.cache dovecot.index.log .imap.index .imap.index.data .imap.index.log .imap.index.tree

2 2

[Dovecot] Next message unexpectedly lost
by Kenneth Porter 07 Aug '08

07 Aug '08

Using 1.1.2. I'm getting the above message over and over in the error log. Dovecot drops the connection and the client (Tbird) just keeps retrying in an endless loop. Using Wireshark to sniff the exchange, it looks like the command that fails looks like this: 5 UID fetch 1:9749,9751:9763,9765:9930,9932,9934:9942 (UID RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS (From To Cc Subject Date Message-ID Priority X-Priority References Newsgroups In-Reply-To Content-Type)]) Dovecot seems to be shutting down after receiving this. Mulberry doesn't seem to have the problem, presumably because it's sending a different command sequence that doesn't stroke this. Here's the failing code, in i_stream_raw_mbox_read : if (stream->istream.v_offset - rstream->hdr_offset + new_pos > rstream->mail_size) { /* istream_raw_mbox_set_next_offset() used invalid cached next_offset? */ i_error("Next message unexpectedly lost from %"PRIuUOFF_T, rstream->hdr_offset + rstream->mail_size); rstream->eof = TRUE; rstream->corrupted = TRUE; return -1; } I've tried deleting the associated .imap/folder contents but it must regenerate the same bad data as it happens again.

1 0