- dovecot - dovecot.org

[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