- dovecot - dovecot.org

[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