September 2010 - dovecot

[Dovecot] "Documentation" link from http://www.dovecot.org/
by William Blunn 22 Sep '10

22 Sep '10

On the Dovecot home page http://www.dovecot.org/ we have a link "Documentation" which links to the Dovecot 1.x wiki ( http://wiki.dovecot.org/ ). There is a question mark in my mind as to whether that is a good idea considering as how the current stable version of Dovecot appears to be 2.0.x. In the Dovecot 1.x wiki, there is a pink stripe across the top of the page which says that the documentation is for Dovecot 1.x. It looks as though the intention was to make that prominent so as to guide visitors to the right documentation, and I think to a certain extent it may work. But I am wondering if perhaps the stripe could be too easily missed. People might start browsing around in the Dovecot 1.x wiki without it even occurring to them that there was a whole another wiki for 2.x. I have an idea: Perhaps the "Documentation" link on the home page could be re-worked to something like Documentation v2.x v1.x where "v2.x" and "v1.x" are links to the two wikis. This would make it obvious that there was different documentation available for v2.x and v1.x, and encourage visitors to choose the appropriate set. Bill

3 8

[Dovecot] service(imap-login): chiled ... killed with signal 11
by Burckhard Schmidt 22 Sep '10

22 Sep '10

Hi, dovecot 2.0.3 After closing the imap(s) connection dovecot crashes: imap-login: Info: Aborted login (no auth attempts): rip=... lip=... mpid=0 master: Error: service(imap-login): child 18636 killed with signal 11 (core not dumped - set service imap-login { drop_priv_before_exec=yes }) master: Warning: Killed with signal 15 (by pid=18643 uid=0 code=kill) It also happens if I only telnet to the imap(s) port and give the only command "1 logout". How can I get a dump for backtracing? With drop_priv_before_exec=yes I get a config error: doveconf: Fatal: Error in configuration file /usr/dovecot/etc/dovecot/dovecot.conf: service(imap-login): drop_priv_before_exec=yes can't be used with chroot As user I can login and work normaly but I have to reconnect after a differnet connection will be closed causing a dovecot crash. Additional information: Solaris 10, packages openssl, openldap by opencsw I had seen a similar error during login process already with an rc-version. Because opencsw offers only an older version of openssl I installed current versions of openssl and openldap, So it works again. Now both packaged are up to date at opencsw. So I would like using these packages again when I install dovecot. Any hints? -- Mit freundlichen Gruessen --- Burckhard Schmidt

2 1

[Dovecot] Sieve autoreply woes on test setup
by Mohit Chawla 22 Sep '10

22 Sep '10

Hi, I have been testing sieve in my setup with qmail-ldap and deliver on a LAN with an artificial domain name. Everything seems to be working as expected, except in cases when autoreplies (vacation, reject messages) need to be tested. The domain name is vmint, and dawnone is the hostname on which mail server is setup, so a users have address like cot@vmint, cute@vmint and dove@vmint * LDA Log* *cot is the user with the sieve vacation filter enabled* 2010-09-22 16:47:55 deliver(cot): Info: Loading modules from directory: /usr/lib/dovecot/modules/lda 2010-09-22 16:47:55 deliver(cot): Info: Module loaded: /usr/lib/dovecot/modules/lda/lib10_quota_plugin.so 2010-09-22 16:47:55 deliver(cot): Info: Module loaded: /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so 2010-09-22 16:47:55 deliver(cot): Info: auth input: uid=1011 2010-09-22 16:47:55 deliver(cot): Info: auth input: gid=1011 2010-09-22 16:47:55 deliver(cot): Info: auth input: home=/home/cot 2010-09-22 16:47:55 deliver(cot): Info: auth input: quota_rule=*:bytes=1000000 2010-09-22 16:47:55 deliver(cot): Info: Quota root: name= backend=maildir args= 2010-09-22 16:47:55 deliver(cot): Info: Quota rule: root= mailbox=* bytes=1000000 messages=0 2010-09-22 16:47:55 deliver(cot): Info: maildir: data=/home/cot/Maildir 2010-09-22 16:47:55 deliver(cot): Info: maildir++: root=/home/cot/Maildir, index=, control=, inbox=/home/cot/Maildir 2010-09-22 16:47:55 deliver(cot): Info: sieve: using sieve path for user's script: /home/cot/.dovecot.sieve 2010-09-22 16:47:55 deliver(cot): Info: sieve: opening script /home/cot/.dovecot.sieve 2010-09-22 16:47:55 deliver(cot): Info: sieve: executing compiled script /home/cot/.dovecot.sieve 2010-09-22 16:47:55 deliver(cot): Info: sieve: msgid=< e93c61e349a52559d3060b6530f6dd69.squirrel(a)192.168.1.137>: sent vacation response to <cute@vmint> 2010-09-22 16:47:55 deliver(cot): Info: Namespace : Using permissions from /home/cot/Maildir: mode=0700 gid=-1 2010-09-22 16:47:55 deliver(cot): Info: sieve: msgid=< e93c61e349a52559d3060b6530f6dd69.squirrel(a)192.168.1.137>: stored mail into mailbox 'INBOX' *failure notice message/bounce sent to the postmaster* Return-Path: <> Received: (qmail 5346 invoked for bounce); 22 Sep 2010 11:17:55 -0000 Date: 22 Sep 2010 11:17:55 -0000 From: MAILER-DAEMON@vmint To: "<>"@dawnone.vmint Subject: failure notice Hi. This is the qmail-send program at vmint. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <cute(a)vmint.vmint <http://192.168.1.137/squirrelmail/src/compose.php?send_to=cute%40vmint.vmint>>: Sorry, I couldn't find any host named vmint.vmint. (#5.1.2) --- Below this line is a copy of the message. Return-Path: <"<>"@dawnone.vmint> Received: (qmail 5344 invoked by uid 1011); 22 Sep 2010 11:17:55 -0000 X-Sieve: Dovecot Sieve 0.1.17 Message-ID: <dovecot-sieve-1285154275-554846-0@dawnone> Date: Wed, 22 Sep 2010 16:47:55 +0530 From: <cot(a)vmint.vmint <http://192.168.1.137/squirrelmail/src/compose.php?send_to=cot%40vmint.vmint>> To: <cute(a)vmint.vmint <http://192.168.1.137/squirrelmail/src/compose.php?send_to=cute%40vmint.vmint>> Subject: Not here In-Reply-To: <e93c61e349a52559d3060b6530f6dd69.squirrel(a)192.168.1.137 <http://192.168.1.137/squirrelmail/src/compose.php?send_to=e93c61e349a52559d…>> References: <e93c61e349a52559d3060b6530f6dd69.squirrel(a)192.168.1.137 <http://192.168.1.137/squirrelmail/src/compose.php?send_to=e93c61e349a52559d…>> Auto-Submitted: auto-replied (vacation) Precedence: bulk MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit This is an automated reply; I am away and will not be able to reply to you immediately.I will get back to you as soon as I return. *deliver is being called like this*: deliver -f $SENDER -d $USER where SENDER and USER are provided by qmail-ldap. So, am not sure what component in the chain is appending a .vmint to the existing domain name. Any input appreciated, thanks.

1 2

[Dovecot] Support for spaces in plaintext passwords?
by Simon 22 Sep '10

22 Sep '10

Hi! I have problems with my cellphone. It does not seem to quote the strings to the login command. I can logon using ie SquirrelMail but if i try to login using AndroidMail it just says "autentication failed". If i try maualy i get similar results. Changing password for test to "password-" a login test password- a OK Logged in. Changing password for test to "password " * OK Dovecot ready. a login test password #here i type "password ", but without "" a NO Authentication failed. Uppon examining squirrelmails comunication it sends login "test" "password " I will of cause file a bugreport that Android Mail should use quoted strings when using 'login' autentication as per rfc2060 (which seems to allow it but not demand it). But i wonder if it is possible to work around this issue in Dovecot somehow?

3 4

[Dovecot] Dovecot needs to be built with SSL support?
by ksrini9＠yahoo.com 22 Sep '10

22 Sep '10

I intend to use Dovecot without SSL. Hence, I built it without SSL support. When I am trying start Dovecot, I am getting the following error message. I have set ssl=no in 10-ssl.conf. Can anyone please let me know if it is possible to build and run Dovecot without SSL support? If it is, how can I overcome the following error message? Thanks a lot. Srini Sep 21 11:18:11 master: Info: Dovecot v2.0.3 starting up (core dumps disabled) Sep 21 11:18:11 ssl-params: Fatal: Dovecot built without SSL support Sep 21 11:18:11 master: Error: service(ssl-params): command startup failed, throttling

3 2

[Dovecot] Quota value *not* getting over written by ldap attr value, help ?
by Mohit Chawla 22 Sep '10

22 Sep '10

Hi, I am having trouble with the quota plugin with deliver. In the auth logs, I see that dovecot is able to get the attribute value just fine: *** Sep 21 17:49:30 dawnone dovecot: auth(default): ldap(cot,127.0.0.1): result: uid(user)=cot uidNumber(userdb_uid)=1011 gidNumber(userdb_gid)=1011 homeDirectory(userdb_home)=/home/cot mailQuotaSize(userdb_quota_rule=*:bytes=%$)=*:bytes=1000000 *** But the value defined in dovecot.conf does *not* get over written with the above value: *** 2010-09-21 17:49:37 deliver(cot): Info: Loading modules from directory: /usr/lib/dovecot/modules/lda 2010-09-21 17:49:37 deliver(cot): Info: Module loaded: /usr/lib/dovecot/modules/lda/lib10_quota_plugin.so 2010-09-21 17:49:37 deliver(cot): Info: Quota root: name=User quota backend=maildir args= 2010-09-21 17:49:37 deliver(cot): Info: Quota rule: root=User quota mailbox=* bytes=2500 messages=0 2010-09-21 17:49:37 deliver(cot): Info: maildir: data=/home/cot/Maildir 2010-09-21 17:49:37 deliver(cot): Info: maildir++: root=/home/cot/Maildir, index=, control=, inbox=/home/cot/Maildir 2010-09-21 17:49:37 deliver(cot): Info: Namespace : Using permissions from /home/cot/Maildir: mode=0700 gid=-1 2010-09-21 17:49:37 deliver(cot): Info: msgid=<2092295c098690fc157fca938d28b879.squirrel@dawnone>: save failed to INBOX: Quota exceeded (mailbox for user is full) 2010-09-21 17:49:37 deliver(cot): Info: msgid=<2092295c098690fc157fca938d28b879.squirrel@dawnone>: rejected: Quota exceeded (mailbox for user is full) 2010-09-21 17:49:37 deliver(cot): Info: msgid=<2092295c098690fc157fca938d28b879.squirrel@dawnone>: Return-Path missing, rejection reason: Quota exceeded (mailbox for user is full) *** My configuration files are as follows: **dovecot.conf** root@dawnone:~# dovecot -n # 1.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-3-686 i686 Debian squeeze/sid log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_location: maildir:~/Maildir mbox_write_locks: fcntl dotlock lda: postmaster_address: dove@vmint mail_plugins: quota deliver_log_format: msgid=%m: %$ sendmail_path: /usr/lib/sendmail log_path: /var/log/ldaone info_log_path: /var/log/ldatwo debug: yes auth default: debug: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: prefetch userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf plugin: quota: maildir:User quota quota_rule: *:bytes=2500 **dovecot-ldap.conf** hosts = dawnone.vmint uris = ldap://dawnone.vmint dn = cn=admin,dc=vmint dnpass = debian auth_bind = yes ldap_version = 3 base = ou=People,dc=vmint scope = subtree user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,userPassword=password,\ homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid,mailQuotaSize=userdb_quota_rule=*:bytes=%$ user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailQuotaSize=quota_rule=*:bytes=%$ Any help in this regard, appreciated. Thanks.

2 2

[Dovecot] expire_tool trouble + howto part sasl from 1.1.7 -> 2.0.1?
by Igor Kowalski 21 Sep '10

21 Sep '10

Hello! Let me smuggle 2 questions in 1 email: 1) I upgraded from 1.1.7 to 2.0.1, but couldn't get it to work, because the 'dovecot + postfix sasl howto' doesn't seem to be updated and the old sasl settings are incompatible with new version. How do I set up sasl with dovecot2 ? Is there any updated howto available? 2) In dovecot 1.1.7: my expire_plugin seems to work fine, new entries are correctly added to the dictionary, but the messages don't actually get expunged. expire_tool says: dovecot --exec-mail ext /usr/lib/dovecot/expire-tool --test Info: maildir: data=~/Maildir Info: maildir++: root=/home/virtual/<domain>/<user>/Maildir, index=, control=, inbox=/home/virtual/<domain>/<user>/Maildir Info: <user>@<domain>/Trash: timestamp 1285005106 (Mon Sep 20 18:51:46 2010 ) -> 1290102903 (Mon Sep 20 18:51:46 2010 ) Info: <user2>@<domain>/Trash: stop, expire time in future: Sat Nov 6 18:33:12 2010 Messages are only updated in the dictionary, but nothing is ever expunged. Any idea why? Output of dovecot -n: # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.7-9-pae i686 openSUSE 11.1 (i586) protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/ssl/certs/startssl.pem ssl_key_file: /etc/ssl/private/startssl.pem verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_location: maildir:~/Maildir mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota expire autocreate mail_plugins(imap): quota imap_quota expire autocreate mail_plugins(pop3): quota expire mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 auth default: mechanisms: plain login debug_passwords: yes passdb: driver: pam args: dovecot2 passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: quota: maildir quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning: storage=80%% /usr/local/bin/quota-warning.sh 80 expire: Trash 60 Trash.* 60 Spam 365 expire_dict: proxy::expire autocreate: Trash autocreate2: Spam autosubscribe: Trash autosubscribe2: Spam dict: expire: mysql:/etc/dovecot/dovecot-dict-expire.conf Create dict. table query: CREATE TABLE `expires` ( `mailbox` varchar(255) NOT NULL, `expire_stamp` int(11) NOT NULL, PRIMARY KEY (`mailbox`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 expire dict. conf: table = expires select_field = expire_stamp where_field = mailbox username_field = not_used And is there a point in using expire plugin without autocreate plugin? Because trash can be called wastebasket for example, and then it doesn't work. Spam can be called Junk, and again, it doesn't work. Any response to these queries would be greatly appreciated. Tadeusz Stelmach

2 1

[Dovecot] MD5 to CRAM-MD5 password conversion?
by David Jonas 21 Sep '10

21 Sep '10

We have a plethora of accounts for which we would like to enable CRAM-MD5 but their passwords are stored as MD5 hashes. Is there anything we can do? Can we take a linux MD5 hashed password (e.g. $1$fac330ee$wd6Tll...) and convert it to dovecot's CRAM-MD5 format (e.g. {CRAM-MD5}b3f297...)? Thanks!

2 1

[Dovecot] understand the struct message_header_line
by Alex Baule 21 Sep '10

21 Sep '10

Timo... Using the src/lib-mail/test-istream-header-filter.c as example, and following your tips to jump my desired header value, but i need to store the value from the Header filtered. In the Exemple, the callback is this: static void filter_callback(struct message_header_line *hdr, bool *matched, void *context ATTR_UNUSED) { if (hdr != NULL && hdr->name_offset == 0) { /* drop first header */ *matched = TRUE; } } What i try to understand is how the structs work, it's save the entire header or every line from header call the callback function ? hdr->name_offset is the size of elements in the struct ? (like a array of message_header_line) The void *context ATTR_UNUSED i can pass what i want to change ? like a pointer to a variable ?

2 1

[Dovecot] 2.0.3 doesn't start without SSL
by Attila Nagy 21 Sep '10

21 Sep '10

Hi, I've upgraded from 2.0.1 to 2.0.3 and while the former starts, the latter doesn't (the config is the same). It bails with: Sep 21 17:15:32 locsocs dovecot: ssl-params: Fatal: Dovecot built without SSL support Sep 21 17:15:32 locsocs dovecot: master: Error: service(ssl-params): command startup failed, throttling I have ssl=off.

2 2