- dovecot - dovecot.org

[Dovecot] 1.0.15 --> 1.2.11 --> got too little data
by Andre Hübner 30 Apr '10

30 Apr '10

Hello, did updates from 1.0.15 to 1.2.11 and is in most cases succesful. Sometimes dovecot leaves errormessage in Log: IMAP(username): FETCH [HEADER] for mailbox INBOX UID 5106 got too little data (copying): 516 vs 528 Until now only Inbox was effected and no other folders. I delete cachesfiles in ~mail/.imap to solve this but is there a way to do this automatical (self healing)? Dovecot could recreate complete caches if there was a difference in calculation. Thanks, Andre

2 6

[Dovecot] convert old configuration file with doveconf : Unknown setting
by de Lafond Guillaume 30 Apr '10

30 Apr '10

Hi, It happens when I try to convert this config (with the dovecot 2.0 beta4 release) : test-mail:/tmp# dovecot -n -c ./dovecot.old.conf # 1.2.11: ./dovecot.old.conf # OS: Linux 2.6.26-2-686-bigmem i686 Debian 5.0.4 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot_info.log protocols: imap listen: 127.0.0.1:30143 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_user: aquaray login_greeting: Mail - test v2 login_process_per_connection: no login_process_size: 96 login_processes_count: 20 login_max_processes_count: 196 max_mail_processes: 10024 mail_max_userip_connections: 10000 verbose_proctitle: yes first_valid_uid: 89 mail_location: maildir:~/:INDEX=/var/mail/dovecot_indexes/%1d/%d/%n fsync_disable: yes maildir_very_dirty_syncs: yes mbox_write_locks: fcntl dotlock mail_drop_priv_before_exec: yes mail_plugins: quota imap_quota imap_client_workarounds: outlook-idle delay-newmail namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: INBOX/ hidden: yes list: no subscriptions: yes lda: postmaster_address: postmaster(a)test-dovecotv2.aquaray.com hostname: test-dovecotv2.aquaray.com log_path: /var/log/dovecot-deliver.log info_log_path: /var/log/dovecot-deliver.log auth_socket_path: /var/run/dovecot-socket-auth/auth-master auth default-auth-master: mechanisms: plain login apop cram-md5 master_user_separator: * passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot-socket-auth/auth-master mode: 384 user: aquaray auth default: mechanisms: plain login apop cram-md5 cache_size: 2048 cache_ttl: 2000 master_user_separator: * count: 10 passdb: driver: sql args: /etc/dovecot/dovecot-sql-master.conf pass: yes master: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf plugin: quota: maildir:User quota test-mail:/tmp# /usr/local/dovecot2/bin/doveconf -n -c ./ dovecot.old.conf # 2.0.beta4 (6891d20929ca): ./dovecot.old.conf doveconf: Warning: Obsolete setting in ./dovecot.old.conf:26: login_dir has been removed doveconf: Warning: Obsolete setting in ./dovecot.old.conf:29: login_chroot has been replaced by service { chroot } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 29: Unknown setting: chroot doveconf: Warning: Obsolete setting in ./dovecot.old.conf:32: login_user has been replaced by service { user } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 32: Unknown setting: user doveconf: Warning: Obsolete setting in ./dovecot.old.conf:36: login_process_size has been replaced by service { vsz_limit } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 36: Unknown setting: vsz_limit doveconf: Warning: Obsolete setting in ./dovecot.old.conf:39: login_process_per_connection has been replaced by service { service_count } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 39: Unknown setting: service_count doveconf: Warning: Obsolete setting in ./dovecot.old.conf:42: login_processes_count has been replaced by service { process_min_avail } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 42: Unknown setting: process_min_avail doveconf: Warning: Obsolete setting in ./dovecot.old.conf:45: login_max_processes_count has been replaced by service { process_limit } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 45: Unknown setting: process_limit doveconf: Warning: Obsolete setting in ./dovecot.old.conf:48: login_max_connections has been replaced by service { client_limit } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 48: Unknown setting: client_limit doveconf: Warning: Obsolete setting in ./dovecot.old.conf:75: mail_drop_priv_before_exec has been replaced by service { drop_priv_before_exec } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 75: Unknown setting: drop_priv_before_exec doveconf: Warning: Obsolete setting in ./dovecot.old.conf:88: max_mail_processes has been replaced by service { process_limit } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 88: Unknown setting: process_limit doveconf: Warning: Obsolete setting in ./dovecot.old.conf:91: mail_process_size has been replaced by service { vsz_limit } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 91: Unknown setting: vsz_limit It does not understand the old 1.1 setting "ssl_disable". test-mail:/tmp# /usr/local/dovecot2/bin/doveconf -n -c ./ dovecot.old.conf # 2.0.beta4 (6891d20929ca): ./dovecot.old.conf doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 21: Unknown setting: ssl_disable ----------------------------------------------------------- After removing all fatal error (comment all settings that are not understood), it works. If needed, I could test against the another other version (latest hg ?). Regards, -- Guillaume de Lafond Aqua Ray SARL

2 3

[Dovecot] Quota maildirsize and dbox
by luben karavelov 30 Apr '10

30 Apr '10

Hello, Is there any reason that maildirsize Quota store should not work in dbox folders or any other folder based mailbox stores? I have patched a test version here and it seems to work (added "dbox" check in src/plugins/quota/quota-maildir.c line 785). If there could be any complications or unexpected consequences of this setup? Thanks in advance luben

3 2

[Dovecot] Expire plugin / expire-tool redesign for doveadm
by Timo Sirainen 30 Apr '10

30 Apr '10

Expire plugin / expire-tool seems annoyingly inflexible currently, so I was thinking about a more generic redesign: The expire plugin keeps track of the oldest message in configured mailboxes. Its only configuration is the list of tracked mailboxes. There's no configuration like what the expire timeouts are or anything. There will be a new doveadm command: doveadm expunge [-u user | -A] <mailbox> <search query> So when you want to expunge all mails from Trash older than 1 week for all users, you say: doveadm expunge -A Trash savedbefore 1w This command works even without expire plugin. To optimize it to avoid looking into all users' Trash mailbox, there's a new expire doveadm plugin, which can use the expire dict to filter out users who don't have anything to expunge. This also supports another feature that the plugin can optimize: doveadm move -A INBOX Archive/2009/INBOX since 2009-01-01 before 2010-01-01 And since people have had problems waiting for expire dict to fill, there could be also a new parameter that does the filling immediately. TODO: - dbox altmove feature will be removed from expire plugin. it may need another plugin, or some other way to configure expire plugin for it. it's anyway a special case. - When using multiple mailboxes it would be more optimal to handle all mailboxes for a user at once, rather than using separate doveadm commands. Maybe the command syntax needs some more thinking to support this. Different mailboxes could have different rules though..

3 6

[Dovecot] Released Pigeonhole Sieve v0.1.16 for Dovecot v1.2.11
by Stephan Bosch 30 Apr '10

30 Apr '10

Hello Dovecot users, Pigeonhole development has slowed down significantly in the last few months due to the fact that I got swamped in work. The plan is now to move active development of Pigeonhole to Dovecot v2.0, meaning that this will be the last release for v1.2 that contains significant development changes and new features. However, if a certain new feature is simple enough and there is a demand for it, I may backport it from v2.0 and release it along with any bugfixes that may still arise. The main thing that this new release adds is full support for the spamtest, spamtestplus and virustest extensions. These extensions implement a uniform means of testing the content spam/virus status headers in mail messages: http://ietfreport.isoc.org/idref/rfc5235/ Not many people have tested these new features yet and therefore these are currently considered experimental. Test these thoroughly before you start using them! Documentation is available in doc/spamtest-virustest.txt Changelog Sieve v0.1.16: * Finished implementation of spamtest, spamtestplus and virustest extensions. These are not enabled by default and need to be activated with the sieve_extensions setting. Documentation available in doc/spamtest-virustest.txt + Vacation extension: the from address of the generated reply is now by default equal to whatever known recipient alias matched the headers of the message. If it is one of the aliases specified with :addresses, it is used in stead of the envelope recipient address that was used before. + Restructured and optimized the lexical scanner. + Added --with-docs configure option to allow disabling installation of documentation. - Accidentally omitted 'extern' in two declarations of global variables in header files, causing compile failures on certain systems. - Deprecated imapflags extension: fixed implicit assignment of flags. Turns out this never really worked, but the effect of this bug was obscured by the removeflag bug fixed in the previous release. - Fixed various memset argument mixups in enotify extension. This caused warnings on certain systems, but luckily no adverse effects at runtime. The releases are available as follows: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.16.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.16.tar.gz.sig Refer to http://pigeonhole.dovecot.org for more information. Have fun testing the new releases and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 6

[Dovecot] Again: Occasional problem with POP3-Download
by Andre Tann 30 Apr '10

30 Apr '10

Hello everyone, in february I posted the mail below[1]. I can now reproduce the problem. When filling up a mailbox with postfix' smtp-source with dozens of identical mails, then it is never possible for me to fetch one single mail out of the mailbox. The process of fetching mail via POP3 always fails. It makes no difference which mail client I use. I have tested KMail, Outlook and Thunderbird. Can anyone confirm this? Is dovecot for some reason unable to deliver such identical mails? Can it be the case that this is a problem with too similar message ids? ~/Maildir/cur$ cat * | grep -i message-id Message-Id: <1024.0003.0008@alphamobil> Message-Id: <1024.0003.0009@alphamobil> Message-Id: <1024.0003.0006@alphamobil> Message-Id: <1024.0003.0007@alphamobil> Message-Id: <1024.0003.0005@alphamobil> Message-Id: <1024.0003.0004@alphamobil> Message-Id: <1024.0003.0003@alphamobil> Message-Id: <1024.0003.0002@alphamobil> Message-Id: <1024.0003.0001@alphamobil> Message-Id: <1024.0003.0000@alphamobil> Thanks and greetings from Munich! AT [1] Hello everyone, I have two mailservers [1] running dovecot. Mail store format is maildir. Every once in a while I have the following problem: When a User downloads his mail via POP3, the client says something like "the server has closed the connection unexpectedly, and gives this reason: [...blahblah...]". One can now cancel the download, and restart it, and the problem shows up again and again. The first few mails get downloaded, and then the process stops. Strange to say the "blahblah"-portion is a piece of text out of the email that doesn't want to get downloaded. Then I remove this single message out of the Maildir/cur-directory, and everything is fine again. It is easy to figure out which mail to delete because it's the first one that is not market as seen [...] filename...:2,S otherfilename...;2, <= this file must be deleted [...] For me it looks as if dovecot had a problem with some byte sequence in this mail, and for some reason it gives an error message to the client which is taken out of the mail. On the SuSE-Machine, before dovecot there was a courier-imapd running, which never showed this kind of problem, so it should not be a client problem. Hopefully my description is clear enough. Does anyone have an idea what's going on here? Thanks. Andre [1] One machine is a openSuSE 11.2 with # rpm -qa | grep dovecot dovecot12-backend-sqlite-1.2.9-0.1.1.i586 dovecot12-backend-mysql-1.2.9-0.1.1.i586 dovecot12-backend-pgsql-1.2.9-0.1.1.i586 dovecot12-1.2.9-0.1.1.i586 The other machine is a Debian Lenny with # dpkg -l | grep dovecot dovecot-common 1:1.0.15-2.3+lenny1 dovecot-imapd 1:1.0.15-2.3+lenny1 dovecot-pop3d 1:1.0.15-2.3+lenny1 -- Andre Tann

3 3

[Dovecot] Right way to Dovecot Load Balance
by Proskurin Kirill 30 Apr '10

30 Apr '10

Hello. I building LB&HA Email cluster based on Exim+Dovecot+LDAP. Now I thinking what the most right way to LB Dovecot(2 nodes with shared storage). HA-Proxy? Dovecot Proxy? Nginx? Else? -- Best regards, Proskurin Kirill

2 1

[Dovecot] Question about auth multiple configuration
by Fabrice MATHIEU 30 Apr '10

30 Apr '10

Hello, My mail system is build with postfix, dovecot and roundcube. In first time users can view and "manage" their mail only on the webmail. So this one (webmail) use IMAP (no tls/ssl at all) authentication to give access to users maildir. This connection is made on the 'loopback' interface and use PLAIN method. This works fine (configuration below without ssl parameters). Now I want to see and send my mail with a MUA (thunderbird). As my system is on an Internet provider I want to add more security "solutions". I use smtps with postfix and SASL/auth by dovecot socket mechanism to send mail. I use imaps with dovecot for managing my maildir. I have added ssl parameters to the configuration file (see below) and I required certificate from the client (to avoid man in the middle attack and to get access only for client with user certificate). To get this "ssl_require_client_cert" is set to yes. Ok, now imaps works perfectly. But since a certificate is required webmail authentication (localhost) and SASL (postfix auth trough dovecot socket mechanism) don't work. Webmail => dovecot: imap-login: Disconnected (cert required, client didn't start TLS): method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Postfix => postfix/smtpd[71640]: warning: TOTO[X.A.B.C]: SASL PLAIN authentication failed: Client didn't present valid SSL certificate That's normal. But 127.0.0.1 client(network) is considered by dovecot as secure, so won't the auth possible without certificate ? Can't we make two auth policy to make secure (client crt require) for public IP/client and less "secure" (without crt client) for local process (postfix) and local newtwork(127.0.0.1) for roundcube ? I see section "auth default { ... }" and is used by ... default ! But can we make an other one to make this two particular authentication on the same "instance" ? Thank you. And then my configuration : operating system => FreeBSD 7.1 dovecot --version => 1.2.8 dovecot -n => # 1.2.8: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE i386 ufs protocols: imap listen: 127.0.0.1 ssl_listen: X.Y.Z.T ssl: yes ssl_ca_file: /usr/local/etc/dovecot/CAclient.pem ssl_cert_file: /usr/local/etc/dovecot/imaps.pem ssl_key_file: /usr/local/etc/dovecot/imaps.key ssl_verify_client_cert: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/jails/mails/%d/%n imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep lda: postmaster_address: postmaster@SOMETHING hostname: SOMETHING_ELSE sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login username_format: %Lu passdb: driver: passwd-file args: username_format=%n /jails/mails/dov_pass/%d/usr_pas userdb: driver: passwd-file args: username_format=%n /jails/mails/dov_pass/%d/usr_pas ssl_require_client_cert = yes ssl_username_from_cert = no socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: wheel master: path: /var/run/dovecot/auth-master mode: 384 Best regards, _________________________________________________________________ Consultez gratuitement vos emails Orange, Gmail, Free, ... directement dans HOTMAIL ! http://www.windowslive.fr/hotmail/agregation/

3 8

[Dovecot] Question about dovecot imap proxy
by Monika Janek 29 Apr '10

29 Apr '10

Hi everyone! I have dovecot (1.2.11) on one our external mail servers acting as a proxy. The client (ifor now, my iphone) connects fine via ssl to the external mailserver but I can't seem to get a secure connection now to the internal destination imap server (between external mail server and internal imap server, it's going through port 143). Running tcpdump, I can clearly see my password being transmitted on our internal network. I read the addition to the documentation about dovecot proxy but I'm not sure where to add these variables: In v1.2.rc4+ the connections to destination server can be TLS/SSL encrypted by returning: * ssl=yes: Use SSL and require a valid verified remote certificate. *WARNING: Unless used carefully, this is an insecure setting!* Currently host must be an IP address, so this setting accepts any certificate signed by a trusted CA. The host name isn't checked in any way against the certificate's CN. The only way to use this securely is to only use and allow your own private CA's certs, anything else is exploitable by a man-in-the-middle attack. * ssl=any-cert: Use SSL, but don't require a valid remote certificate. * starttls: Use STARTTLS command instead of doing SSL handshake immediately after connected. Can anyone point me in the right direction? Thanks so much! :) -- Monika Janek Systems Administrator, Side Effects Software Toronto, Ontario Canada 416-504-9876 x207 www.sidefx.com

2 8

[Dovecot] Assertion failed in mail-search-build.c
by Mark Moseley 29 Apr '10

29 Apr '10

With Friday's and today's mercurial repo, I'm getting this: Apr 26 12:55:31 master: Info: Dovecot v2.0.beta4 starting up (core dumps disabled) Apr 26 12:58:34 imap-login: Info: Login: user=<mail@box>, method=PLAIN, rip=10.1.1.206, lip=192.168.152.1 Apr 26 12:58:34 imap(mail@box): Panic: file mail-search-build.c: line 59 (mail_search_build_key_int): assertion failed: (sarg->value.subargs != NULL) Apr 26 12:58:34 imap(mail@box): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb76a3ad1] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a3b4f] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0xb76a3e08] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb76f859e] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb76f860f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_build+0x82) [0xb76f86f2] -> dovecot/imap [mail@box 10.1.1.206 SEARCH](imap_search_args_build+0x48) [0x805d8a8] -> dovecot/imap [mail@box 10.1.1.206 SEARCH](cmd_search+0xbb) [0x805342b] -> dovecot/imap [mail@box 10.1.1.206 SEARCH] [0x80564dc] -> dovecot/imap [mail@box 10.1.1.206 SEARCH] [0x8056579] -> dovecot/imap [mail@box 10.1.1.206 SEARCH](client_handle_input+0x2d) [0x80566ed] -> dovecot/imap [mail@box 10.1.1.206 SEARCH](client_input+0x5f) [0x805710f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xf5) [0xb76b0115] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x30) [0xb76af160] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2a) [0xb769ca5a] -> dovecot/imap [mail@box 10.1.1.206 SEARCH](main+0x2b5) [0x805fb95] -> /lib/libc.so.6(__libc_start_main+0xe5) [0xb752e455] -> dovecot/imap [mail@box 10.1.1.206 SEARCH] [0x804e951] Apr 26 12:58:34 master: Error: service(imap): child 13220 killed with signal 6 (core dumps disabled) Login is working fine, just blowing up on that assert by doing a search. The search is pretty basic, in python: server.search( None, "(ALL)" ) Testing with a previous version (from a couple of days earlier -- I don't have the intervening), I don't hit that assertion. The last changeset on mail-search-build.c in the working copy is 11146:3649ad8c9f9a. Let me know if there's anything you'd like me to try.

2 1