January 2012 - dovecot

[Dovecot] Dovecot crashes totally
by Gordon Grubert 18 Jan '12

18 Jan '12

Hello, our dovecot server crashes totally without any really useful log messages. The error log can be found in the attachment. The only way to get dovecot running again is a complete system restart. Dovecot version: 2:2.0.15-0~auto+5 (2.0.15 (6b7242ead6ed)) Configuration : see attachment OS : Debian Squeeze amd64 Dovecot source : http://xi.rename-it.nl/debian/ \ stable-auto/dovecot-2.0 main This problem has already occurred with the version 2.0.13 where the log says as few as the current logs :-( Best regards, Gordon -- Leiter AG Technische Infrastruktur und Basisdienste Universitaetsrechenzentrum (URZ) E.-M.-Arndt-Universitaet Greifswald Felix-Hausdorff-Str. 12 17489 Greifswald Germany Tel. +49 3834 86-1456 Fax. +49 3834 86-1401

3 3

[Dovecot] [Dovecot 2.1] ACL plugin makes imap service crash when using some clients
by interfaSys sàrl 18 Jan '12

18 Jan '12

Hello, I've just noticed that when Horde is connecting to Dovecot 2.1, it crashes the imap service if Dovecot is configured to use the ACL plugin. I'm not sure what's so special about the command Horde sends, but it shouldn't make Dovecot crash. Everything is fine when using Thunderbird. Here is the message in Dovecot's logs "Fatal: master: service(imap): child 89974 killed with signal 11 (core not dumped)" The message says that the core is not dumped, even though I did add drop_priv_before_exec=yes to my config file. I've tried connecting to the pid using gdb, but the process just hangs as soon as I'm connected. Cheers, Olivier

2 1

[Dovecot] resolve mail_home ?
by Jan-Frode Myklebust 17 Jan '12

17 Jan '12

I now have "mail_home = /srv/mailstore/%256RHu/%d/%n". Is there any way of asking dovecot where a user's home directory is? It's not in "doveadm user": $ doveadm user -f home janfrode(a)lyse.net $ doveadm user janfrode(a)tanso.net userdb: janfrode(a)tanso.net mail : mdbox:~/mdbox quota_rule: *:storage=1048576 Alternatively, is there an easy way to calculate the %256RHu hash ? -jf

3 2

[Dovecot] little bug with Director in 2.1?
by Luca Di Vizio 17 Jan '12

17 Jan '12

Hi, in 2.1rc3 the "director_servers" setting does not accept hostnames as documented (with ip no problems). It works correctly in 2.0.17. Greetings, Luca

2 1

[Dovecot] Using Dovecot-auth to return error code 450 (or other 4xx) to Postfix when user is on vacation
by IVO GELOV (CRM) 17 Jan '12

17 Jan '12

Hello to all members. I am using Dovecot for 5 years, but this is my first post here. I am aware of the various autoresponder scripts for vacation autoreplies (I am using Virtual Vacation 3.1 by Mischa Peters). I have an issue with auto-replies - it is vulnerable to spamming with forged email address. Forging can be prevented with several Postfix settings, which I did in the past - but was forced to remove, because our company occasionaly has clients with improper configurations and those settings prevent us to receive their legitimate mail (and this of course is not good for the business). So I have though about another idea. Since I use Dovecot-auth to verify mailbox existence - I just wonder is it possible to somehow indicate specific error code (and hopefully descriptive text also) to Postfix (e.g. 450 or some other temporary failure) when the owner of the mailbox is currently on vacation ? Best wishes, IVO GELOV

5 16

[Dovecot] IMAP maillog error: file lib.c: line 37 (nearest_power): assertion failed: (num <= ((size_t)1 << (BITS_IN_SIZE_T-1)))
by Charles Thompson 15 Jan '12

15 Jan '12

Dear Mailing List, What does this error mean and how do I fix it? I am on a Centos 4.9 >From /var/log/maillog : Jan 14 11:54:51 hostname imap(username): file lib.c: line 37 (nearest_power): assertion failed: (num <= ((size_t)1 << (BITS_IN_SIZE_T-1))) Version information : root(a)hostname[/etc/rc.d/rc3.d]# dovecot --version ; dovecot -n ; cat /etc/*release* 0.99.11 Usage: dovecot [-F] [-c <config file>] Fatal: Unknown argument: -n CentOS release 4.9 (Final) root(a)hostname[/etc/rc.d/rc3.d]# Thank you. -- Sincerely, Charles Thompson *UNIX & Linux Administrator* Tel* : *(650) 906-9156 Web : www.kinesis.me Mail: mail(a)kinesis.me

3 2

[Dovecot] [PATCH] support master user to login as other users by DIGEST-MD5 SASL proxy authorization
by Yubao Liu 14 Jan '12

14 Jan '12

Hi Timo, As http://wiki2.dovecot.org/Authentication/MasterUsers states, currently the first way for master users to log in as other users only supports PLAIN SASL mechanism, and because DIGEST-MD5 uses user name to calculate MD5 digest, the second way can't support DIGEST-MD5. I enhance the code to support DIGEST-MD5 too for the first way, please review the attached patch against dovecot-2.0 HG tip. The patch also contains a little fix to "nonce-count" string, RFC 2831 shows it should be "nc". I tested it on Debian Wheezy, it seems OK. Below are my verification steps. (Debian packaged 2.0.15 + http://hg.dovecot.org/dovecot-2.0/rev/bed15faedfd4 + attached patch) $ doveconf -n # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 3.1.0-1-686-pae i686 Debian wheezy/sid auth_default_realm = corp.example.com auth_krb5_keytab = /etc/dovecot.keytab auth_master_user_separator = * auth_mechanisms = gssapi digest-md5 cram-md5 auth_realms = corp.example.com auth_username_format = %n first_valid_gid = 1000 first_valid_uid = 1000 mail_location = mdbox:/srv/mail/%u/Mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { driver = pam } plugin { sieve = /srv/mail/%u/.dovecot.sieve sieve_dir = /srv/mail/%u/sieve } protocols = " imap lmtp sieve" service auth { unix_listener auth-client { group = Debian-exim mode = 0660 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = home=/srv/mail/%u driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } $ grep webmail2 /etc/dovecot/master-users webmail2:{DIGEST-MD5}458af98b24dce5db79f852d146d5a5ca $ gsasl -m DIGEST-MD5 --imap imap.corp.example.com -z dieken -a webmail2 -p 123456 -r corp.example.com Trying `gold.corp.example.com'... * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED AUTH=GSSAPI AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. . CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED AUTH=GSSAPI AUTH=DIGEST-MD5 AUTH=CRAM-MD5 . OK Pre-login capabilities listed, post-login capabilities have more. . STARTTLS . OK Begin TLS negotiation now. . CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=GSSAPI AUTH=DIGEST-MD5 AUTH=CRAM-MD5 . OK Pre-login capabilities listed, post-login capabilities have more. . AUTHENTICATE DIGEST-MD5 + cmVhbG09ImNvcnAuZXhhbXBsZS5jb20iLG5vbmNlPSI2Y0tvRWpoRkREQVpsRHM4Q05QTUx3PT0iLHFvcD0iYXV0aCIsY2hhcnNldD0idXRmLTgiLGFsZ29yaXRobT0ibWQ1LXNlc3Mi Enter quality of protection (optional, e.g. 'qop-int'): dXNlcm5hbWU9IndlYm1haWwyIiwgcmVhbG09ImNvcnAuZXhhbXBsZS5jb20iLCBub25jZT0iNmNLb0VqaEZEREFabERzOENOUE1Mdz09IiwgY25vbmNlPSJIUUZKQy9VbnFSb3lGb3orTWpOY2hnPT0iLCBuYz0wMDAwMDAwMSwgcW9wPWF1dGgsIGRpZ2VzdC11cmk9ImltYXAvaW1hcC5jb3JwLmV4YW1wbGUuY29tIiwgcmVzcG9uc2U9NjU0MTQ0NzM5MTFhNjNlMjE4ZDJmZjc0NmNjZjk0MjUsIGNoYXJzZXQ9dXRmLTgsIGF1dGh6aWQ9ImRpZWtlbiI= + cnNwYXV0aD04ZTNiZmZhMmNhOWM4YzczODU3Zjc2OWZiOGRlMTU3MQ== * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS Client authentication finished (server trusted)... Enter application data (EOF to finish): Session finished... . LOGOUT . OK Logged in * BYE Logging out $ sudo tail -f 30 /var/log/mail.log .... Jan 14 20:35:30 gold dovecot: auth: Debug: client in: AUTH#0111#011DIGEST-MD5#011service=imap#011secured#011lip=127.0.1.1#011rip=127.0.0.1#011lport=143#011rport=54455 Jan 14 20:35:30 gold dovecot: auth: Debug: client out: CONT#0111#011cmVhbG09ImNvcnAuZXhhbXBsZS5jb20iLG5vbmNlPSJsQzM0dlQ3QkxUOHdlc2VOOWIybzhnPT0iLHFvcD0iYXV0aCIsY2hhcnNldD0idXRmLTgiLGFsZ29yaXRobT0ibWQ1LXNlc3Mi Jan 14 20:35:32 gold dovecot: auth: Debug: client in: CONT#0111#011dXNlcm5hbWU9IndlYm1haWwyIiwgcmVhbG09ImNvcnAuZXhhbXBsZS5jb20iLCBub25jZT0ibEMzNHZUN0JMVDh3ZXNlTjliMm84Zz09IiwgY25vbmNlPSJQOTFta2VHZjFFS2kzQVgxMWVVT3FnPT0iLCBuYz0wMDAwMDAwMSwgcW9wPWF1dGgsIGRpZ2VzdC11cmk9ImltYXAvaW1hcC5jb3JwLmV4YW1wbGUuY29tIiwgcmVzcG9uc2U9OTllNzM2MDc0ZWE3YjE2NTE4NGQ3ZGVjY2E5ZGExNTgsIGNoYXJzZXQ9dXRmLTgsIGF1dGh6aWQ9ImRpZWtlbiI= Jan 14 20:35:32 gold dovecot: auth: Debug: auth(webmail2,127.0.0.1,master): Master user lookup for login: dieken Jan 14 20:35:32 gold dovecot: auth: Debug: passwd-file(webmail2,127.0.0.1,master): lookup: user=webmail2 file=/etc/dovecot/master-users Jan 14 20:35:32 gold dovecot: auth: passdb(webmail2,127.0.0.1,master): Master user logging in as dieken Jan 14 20:35:32 gold dovecot: auth: Debug: password(dieken,127.0.0.1): Credentials: 458af98b24dce5db79f852d146d5a5ca Jan 14 20:35:32 gold dovecot: auth: Debug: client out: CONT#0111#011cnNwYXV0aD04YmU5ZjFmN2UyMTRlMjI3MmY2YjEwMDU0YmYwNmMwZg== Jan 14 20:35:32 gold dovecot: auth: Debug: client in: CONT#0111#011 Jan 14 20:35:32 gold dovecot: auth: Debug: client out: OK#0111#011user=dieken Jan 14 20:35:32 gold dovecot: auth: Debug: master in: REQUEST#0112451832833#01115973#0111#011b7ff18971fd6967b00e2ea0ed2ef6278 Jan 14 20:35:32 gold dovecot: auth: Debug: passwd(dieken,127.0.0.1): lookup Jan 14 20:35:32 gold dovecot: auth: Debug: master out: USER#0112451832833#011dieken#011home=/srv/mail/dieken#011system_groups_user=dieken#011uid=1000#011gid=1000#011master_user=webmail2 Jan 14 20:35:32 gold dovecot: imap-login: Login: user=<dieken>, method=DIGEST-MD5, rip=127.0.0.1, lip=127.0.1.1, mpid=15974, TLS Jan 14 20:35:32 gold dovecot: imap: Debug: Added userdb setting: plugin/master_user=webmail2 Jan 14 20:35:32 gold dovecot: imap(dieken): Debug: Effective uid=1000, gid=1000, home=/srv/mail/dieken Jan 14 20:35:32 gold dovecot: imap(dieken): Debug: fs: root=/srv/mail/dieken/Mail, index=, control=, inbox=, alt= Jan 14 20:35:32 gold dovecot: imap(dieken): Debug: Namespace : Using permissions from /srv/mail/dieken/Mail: mode=0700 gid=-1 Jan 14 20:35:34 gold dovecot: imap(dieken): Disconnected: Logged out bytes=8/329 Jan 14 20:35:34 gold dovecot: imap-login: Warning: SSL alert: where=0x4008, ret=256: warning close notify [127.0.0.1] Jan 14 21:04:50 gold dovecot: imap(dieken): Disconnected: Logged out bytes=131/533 Jan 14 21:33:59 gold dovecot: imap-login: Login: user=<dieken>, method=DIGEST-MD5, rip=127.0.0.1, lip=127.0.1.1, mpid=16114, TLS Jan 14 21:34:03 gold dovecot: imap(dieken): Disconnected: Logged out bytes=8/329 Jan 14 21:36:56 gold dovecot: imap-login: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.1.1 Jan 14 21:36:56 gold dovecot: imap-login: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.1.1 Jan 14 21:36:58 gold dovecot: imap-login: Login: user=<dieken>, method=DIGEST-MD5, rip=127.0.0.1, lip=127.0.1.1, mpid=16135, TLS Jan 14 21:37:00 gold dovecot: imap(dieken): Disconnected: Logged out bytes=10/377 Regards, Yubao Liu

1 0

[Dovecot] Server Time 45min ahead
by maximus12 13 Jan '12

13 Jan '12

Hi, I have the issue that my server clock is 45min fast. Therefore I would like to install ntp. I read a lot on the internet about dovecot and ntp. My issue is that 45 min are a lot an I would like to minimize mail server downtimes as much as possible. I don't care if the time corrections with ntp takes more than a few month. Does anyone know how I should proceed (e.g. how I have to setup ntp -> no time jump during installation and afterwards). Thanks a lot for your help! -- View this message in context: http://old.nabble.com/Server-Time-45min-ahead-tp33126760p33126760.html Sent from the Dovecot mailing list archive at Nabble.com.

4 6

[Dovecot] Dsync and compressed mailboxes
by Joseba Torre 13 Jan '12

13 Jan '12

Hi, I will begin two migrations next week, and in both cases I plan to use compressed mailboxes with mdbox format. But in the last minute one doubt has appeared: is dsync aware of compressed mailboxes? I'm not sure if dsync -u $USER mirror mdbox:compressed_mdbox_path works, or if I have to use something else (I guess that with a running dovecot dsync backup should work). Thanks.

2 1

[Dovecot] (no subject)
by Geoffrey Broadwell 13 Jan '12

13 Jan '12

I'm working on a Dovecot plugin, but I'm pretty new to Dovecot, so there's a LOT to learn about the code base and it's pretty slow going. I've got a few things coded so far, but I want to make sure I'm headed down the right path and get some advice before I go too much further. A couple years ago, I wrote some code for our Courier implementation that sent a magic UDP packet to a small server each time a user modified their voicemail IMAP folder. That UDP server would then connect back to Courier via IMAP again and check whether the folder had any unread messages left in it. Finally, it would contact our phone switches to modify the state of the message waiting indicator (MWI) on that user's phone line appropriately. Fast forward to now, and we want to migrate wholesale to Dovecot 2.x. The servers are all in place, they've been well tested and burned in (with Dovecot 2.0.15 I believe), and the final migration is pretty much waiting on a port to Dovecot of the MWI update functionality. The good news is that I originally spent some effort to isolate the UDP packet generation and delivery, and I used purely standard portable code as per APUE2, so I think that chunk of code should be reusable with only minor modifications. I'm aware that internally Dovecot has its own memory, buffer, and string management functions, but it doesn't feel like a win to try to convert the existing code. It's small, completely isolated, and well reviewed -- I'd be more afraid of using the new (to me) Dovecot API incorrectly than I am that the existing code has bugs in buffer handling. By cribbing from other plugins and editing appropriately, I've also created the skeleton for my plugin: Makefile, docs, conf snippet, .spec (I'll be deploying the plugin as an RPM), and so on. I've got the beginnings of the .h and .c written, just enough to init and deinit the plugin by calling mail_storage_hooks_{add,remove}() with some stub hook functions. This all seems good so far; test builds are error-free and seem sane. So now the hard part is writing the piece that I can't just crib from elsewhere -- making sure that I hook every place in Dovecot that the user's voicemail folder can be changed in a way that would change it between having one or more unread messages, and not having any unread messages at all (or vice-versa, of course). At the same time, I want to minimize the performance impact to Dovecot (and the load on the UDP server) by only hooking the places I need to, filtering out as many false positives as I can without introducing massive complexity, and only pinging the UDP server when it's most likely to notice a change in the state of that user's voicemail server. It seems to me that I need to at least capture mailbox_allocated from the mail_storage hooks, for a couple reasons: 1. The state of the voicemail folder could be changed because the entire folder is created, destroyed, or renamed. 2. I want to only do further checks when I'm sure I'm looking at the voicemail folder. There's no reason to do work when the user is working with any other folder. So now the questions: Does all of the above seem sane so far? Do I need to hook mail_allocated as well, or will I be able to see any change I need to monitor just from the mailbox? Finally, I'm lost about what operations on the mailbox and the mails within it I need to check. Can anyone offer some advice (or doc pointers) on this? Thank you! -'f

4 5