- dovecot - dovecot.org

[Dovecot] SSL problems on dovecot 2.1.7
by Steinar Bang 09 May '13

09 May '13

When I upgraded my debian-based imap server from squeeze to wheezy yesterday, SSL stopped working. I am using a http://cacert.org signed server sertificate, and I am reusing the certificates that were used on the 1.x dovecot of debian squeeze. My three MUAs that worked against the previous 1.x dovecot with the same certificate, now fails in various ways. Any hints and guesses as to how to debug this further will be highly appreciated. Even more appreciated will be a pin point of the issue. :-) Here are the error messages from the MUAs: - Opera 12.15 on Windows 7 just reports: "The connection with the IMAP server was unexpectedly interrupted." - Emacs24(w/linked-in gnutls)/Ma Gnus 0.8 (Gnus git HEAD) on Windows 7 says "imap.mydomain.com certificate could not be verified." - Emacs23/Ma Gnus 0.8 (also Gnus git HEAD) on debian testing (with Emacs23 gnutls-cli is run in a subprocess), says: "Opening connection to imap.mydomain.com via tls... Opening TLS connection to `imap.mydomain.com'... Opening TLS connection with `gnutls-cli --insecure -p 993 imap.mydomain.com'...done Opening TLS connection to `imap.mydomain.com'...done Unable to open server nnimap+privat due to: Process *nnimap* not running" When I try running gnutls-cli from the command line of the debian testing machine (the same gnutls-cli that is used by the emacs23/gnus combo), it seems to connect ok (the transcript of that session is below). The config for the SSL, from /etc/dovecot/conf.d/10-ssl.conf, is: # SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt> ssl = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf ssl_cert = </etc/ssl/certs/imap_mydomain_com.pem ssl_key = </etc/ssl/private/imap_mydomain_com.key The access privileges of the files, are: -rw-r--r-- 1 root root 2077 Mar 27 12:45 /etc/ssl/certs/imap_mydomain_com.pem -rw------- 1 root root 3243 Jul 12 2011 /etc/ssl/private/imap_mydomain_com.key What follows, is the transcript from the gnutls-cli session from a debian testing machine to the server (which seems to be working as far as I can tell...): sb@edwards:~$ gnutls-cli -p 993 rainey.mydomain.com WARNING: gnome-keyring:: couldn't connect to: /home/sb/.cache/keyring-yeEdM3/pkcs11: No such file or directory Resolving 'rainey.mydomain.com'... Connecting to '212.110.185.190:993'... - Ephemeral Diffie-Hellman parameters - Using prime: 1024 bits - Secret key: 1023 bits - Peer's public key: 1023 bits - Certificate type: X.509 - Got a certificate list of 1 certificates. - Certificate[0] info: - subject `CN=imap.mydomain.com', issuer `O=Root CA,OU=http://www.cacert.org,CN=CA Cert Signing Authority,EMAIL=support(a)cacert.org', RSA key 4096 bits, signed using RSA-SHA1, activated `2013-03-27 12:43:30 UTC', expires `2013-09-23 12:43:30 UTC', SHA-1 fingerprint `86f8a501bca1e2b0eadc677bf05b103d298ce247' - The hostname in the certificate does NOT match 'rainey.mydomain.com' sb@edwards:~$ gnutls-cli -p 993 imap.mydomain.com WARNING: gnome-keyring:: couldn't connect to: /home/sb/.cache/keyring-yeEdM3/pkcs11: No such file or directory Resolving 'imap.mydomain.com'... Connecting to '212.110.185.190:993'... - Ephemeral Diffie-Hellman parameters - Using prime: 1024 bits - Secret key: 1022 bits - Peer's public key: 1021 bits - Certificate type: X.509 - Got a certificate list of 1 certificates. - Certificate[0] info: - subject `CN=imap.mydomain.com', issuer `O=Root CA,OU=http://www.cacert.org,CN=CA Cert Signing Authority,EMAIL=support(a)cacert.org', RSA key 4096 bits, signed using RSA-SHA1, activated `2013-03-27 12:43:30 UTC', expires `2013-09-23 12:43:30 UTC', SHA-1 fingerprint `86f8a501bca1e2b0eadc677bf05b103d298ce247' - The hostname in the certificate matches 'imap.mydomain.com'. - Peer's certificate issuer is unknown - Peer's certificate is NOT trusted - Version: TLS1.2 - Key Exchange: DHE-RSA - Cipher: AES-128-CBC - MAC: SHA1 - Compression: NULL - Handshake was completed - Simple Client Mode: * OK Waiting for authentication process to respond.. - Peer has closed the GnuTLS connection

1 0

[Dovecot] dovecot stats
by Jan-Frode Myklebust 09 May '13

09 May '13

I just upgraded one of our servers to dovecot v2.1.16 (ee), and am looking into the stats feature. Am I interpreting the wiki correct in reading that the "doveadm stats dump command" only returns statistics about IMAP commands? Is it possible to collect info about POP3 and LMTP commands also ? Also, is "doveadm stats dump command" telling me the results of all commands that has finished the last stats_command_min_time, or will it maybe contain much more than 1 minute of activity ? -jf

3 5

[Dovecot] AuthenticationFailedException: [IN-USE] Couldn't open INBOX: Permission denied
by Earles, Jill 09 May '13

09 May '13

I've been pouring over the documentation for dovecot, but can't find a solution to this problem. I recently took over administration of the dovecot email service at the University where I work, and things were going smoothly. We've been creating email accounts for use with JIRA, a bug reporting/tracking system, and one day recently, when I tried to add a new account to JIRA, I got this error returned from dovecot: "AuthenticationFailedException: [IN-USE] Couldn't open INBOX: Permission denied" I got help from Atlassian, the creators of JIRA, and they sent me links to some forum posts that said that changing the permissions of that user's /var/mail/ directory to 0600 would solve the problem. I changed that and no longer got the error. Being satisfied that this was a solution, I created a bunch of new email accounts today to replace exchange accounts, and then changed the permissions on all the /var/mail/ directories to 0600. Now I'm getting that error again, even for pre-existing email addresses, including the one that I had previously fixed by changing the permissions the same way. I tried changing some of the older accounts back to 0660, which is what they had before, and I still get the error even after restarting dovecot. JIRA uses POP, port 110, to connect to the dovecot mail server. I've also had the same problem trying to connect from Mac Mail. Our JIRA application is used for tracking issues for the UBC Libraries, and those email addresses are critical for the creation of tickets and adding comments to tickets. I am at a loss for what to do. Can anyone help? Thank you very much for your time. # dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-131.0.15.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.4 (Santiago) auth_debug = yes auth_debug_passwords = yes disable_plaintext_auth = no mail_access_groups = mail mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl passdb { driver = pam } ssl_cert = </etc/pki/dovecot/certs/server.crt ssl_key = </etc/pki/dovecot/private/server.key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } Here's an except of the maillog from a recent attempt: May 8 17:46:49 moose dovecot: auth: Debug: pam(lib.sysadmin,{ip removed}): lookup service=dovecot May 8 17:46:49 moose dovecot: auth: Debug: pam(lib.sysadmin,{ip removed}): #1/1 style=1 msg=Password: May 8 17:46:49 moose dovecot: auth: Debug: client out: OK#0111#011user=lib.sysadmin May 8 17:46:49 moose dovecot: auth: Debug: master in: REQUEST#0111028653057#01128298#0111#011a60ed90501af39d7e353a14e027255cd May 8 17:46:49 moose dovecot: auth: Debug: passwd(lib.sysadmin,{ip removed}): lookup May 8 17:46:49 moose dovecot: auth: Debug: master out: USER#0111028653057#011lib.sysadmin#011system_groups_user=lib.sysadmin#011uid=523#011gid=524#011home=/home/lib.sysadmin May 8 17:46:49 moose dovecot: pop3-login: Login: user=<lib.sysadmin>, method=PLAIN, rip={ip removed}, lip={ip removed}, mpid=28302 May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Error: stat(/var/spool/mail/lib.sysadmin) failed: Permission denied May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Error: stat(/var/spool/mail/lib.sysadmin) failed: Permission denied May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Error: Couldn't open INBOX: Permission denied May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 May 8 17:46:50 moose dovecot: auth: Debug: auth client connected (pid=28303) May 8 17:46:50 moose dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=pop3#011lip={ip removed}#011rip={ip removed}#011lport=110#011rport=64420#011resp=AGJ2YXV3LnJlbGFpcwByM2xAaXMuYnZAdXc=

2 8

[Dovecot] change inbox dotlock name
by Chris Saldanha 08 May '13

08 May '13

Hi, Is there a configuration element that would allow me to change the dot-lock name for the user's /var/mail inbox when it is locked? dovecot (correctly) acquires <username>.lock, but I'm having a problem with procmail where some obscure code path is preventing procmail's acquisition of a lock when it's that default name in /var/mail. The issue is not permissions (using a world-writeable and sticky-bit config for /var/mail). I'll dig into the procmail code if needed, but if dovecot could use a different filename for such locks, then that would solve my issue. procmail has such an option, and I only need to do this for inboxes. Thanks, Chris -- Chris Saldanha Parliant Corporation

2 1

[Dovecot] sieve redirect envelope address problem
by Костырев Александр Алексеевич 08 May '13

08 May '13

Good day! I have a problem with mail redirection through sieve rules. I've configured sieve rule that redirects any mail coming to user to gmail mailbox (or whatever external mail system there is). But when sieve redirects any mail it puts vmail@%dovecot_hostname% into envelope address, gives it to my exim for delivery and gmail rejects my mail because user vmail@%dovecot_hostname% do not exist. Please, advice for what can be done about this behavior. my `doveconf -n` http://pastebin.com/0dyL9Jgs Thanks in advance! -- С уважением, Костырев Александр администратор Linux-систем

4 4

[Dovecot] CATENATE mis-reads literal after bad URL
by Mike Abbott 08 May '13

08 May '13

Dovecot-2.2.1 plus Timo's recent CATENATE and URLAUTH fixes mishandles literals after bad URLs. (As before remember that the "foobar" text below is really "foobarCRLF" hence the length of 8. Also, last time some MTA discarded an important single leading space character in the snippet I quoted so this time I'm prefixing all the lines to avoid that. In case it's lost again, there's a space before the word "url" below.) | b append inbox catenate (text {8} | + OK | foobar | url /a-bad-url text {8} | b NO [BADURL /a-bad-url] Invalid messagepart IMAP URL. | c noop | d noop | d OK NOOP completed. | e logout | * BYE Logging out | e OK Logout completed. Note that the command with tag "c" is lost. I think it shouldn't be, because the NO was reported to the client without sending a continuation (+ OK) so the client knows not to send the literal. Plus it appears only one line is discarded regardless of the size of the literal.

2 2

[Dovecot] URLAUTH assertion failures in 2.2.1
by Mike Abbott 07 May '13

07 May '13

Testing URLAUTH in dovecot-2.2.1 plus Timo's recent CATENATE and URLAUTH fixes eventually trips some assertions. No simple sequence of commands always hits these; they appear to be timing-dependent. The first one is: May 02 17:47:17 imap(pid 50490 user submit): Panic: file imap-client.c: line 643 (client_command_free): assertion failed: (client->output_cmd_lock == NULL) The line number doesn't match dovecot-2.2.1 due to Apple's unrelated modifications. 0 libsystem_kernel.dylib 0x00007fff8a9f7d4a __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff8f728705 pthread_kill + 92 2 libsystem_c.dylib 0x00007fff8f48b17b abort + 125 3 libdovecot.0.dylib 0x000000010db8d2bb default_fatal_finish + 68 4 libdovecot.0.dylib 0x000000010db8df66 i_internal_error_handler + 0 5 libdovecot.0.dylib 0x000000010db8d53d i_panic + 158 6 imap 0x000000010da468fe client_command_free + 446 7 imap 0x000000010da47a33 client_output_cmd + 37 8 imap 0x000000010da46497 client_output + 143 9 libdovecot.0.dylib 0x000000010dba5610 stream_send_io + 53 10 libdovecot.0.dylib 0x000000010db9bc74 io_loop_call_io + 46 11 libdovecot.0.dylib 0x000000010db9cc85 io_loop_handler_run + 214 12 libdovecot.0.dylib 0x000000010db9be1f io_loop_run + 77 13 libdovecot.0.dylib 0x000000010db5b0c6 master_service_run + 24 14 imap 0x000000010da4fa66 main + 1010 15 libdyld.dylib 0x00007fff8f7887bd start + 1 The second one is: May 02 19:23:29 imap(pid 60229 user mja): Panic: file index-mail.c: line 1274 (index_mail_close_streams_full): assertion failed: (!mail->data.destroying_stream) 0 libsystem_kernel.dylib 0x00007fff8a9f7d4a __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff8f728705 pthread_kill + 92 2 libsystem_c.dylib 0x00007fff8f48b17b abort + 125 3 libdovecot.0.dylib 0x00000001054c42bb default_fatal_finish + 68 4 libdovecot.0.dylib 0x00000001054c4f66 i_internal_error_handler + 0 5 libdovecot.0.dylib 0x00000001054c453d i_panic + 158 6 libdovecot-storage.0.dylib 0x00000001053aaebb index_mail_close_streams_full + 199 7 libdovecot-storage.0.dylib 0x00000001053aaf29 index_mail_close + 44 8 libdovecot-storage.0.dylib 0x00000001053ab6bd index_mail_free + 48 9 libdovecot-storage.0.dylib 0x000000010538a19a mail_free + 15 10 libdovecot-storage.0.dylib 0x00000001053dd3b3 imap_msgpart_url_free + 65 11 imap 0x000000010532d563 imap_urlauth_fetch_abort_local + 30 12 imap 0x000000010532cb96 imap_urlauth_fetch_abort + 38 13 imap 0x000000010532cb54 imap_urlauth_fetch_deinit + 24 14 imap 0x00000001053218bd cmd_urlfetch_finish + 45 15 imap 0x0000000105321aa3 cmd_urlfetch_continue + 167 16 imap 0x0000000105323ef8 command_exec + 55 17 imap 0x0000000105323a20 client_output_cmd + 18 18 imap 0x0000000105322497 client_output + 143 19 libdovecot.0.dylib 0x00000001054dc610 stream_send_io + 53 20 libdovecot.0.dylib 0x00000001054d2c74 io_loop_call_io + 46 21 libdovecot.0.dylib 0x00000001054d3c85 io_loop_handler_run + 214 22 libdovecot.0.dylib 0x00000001054d2e1f io_loop_run + 77 23 libdovecot.0.dylib 0x00000001054920c6 master_service_run + 24 24 imap 0x000000010532ba66 main + 1010 25 libdyld.dylib 0x00007fff8f7887bd start + 1

2 2

[Dovecot] Dovecot Postfix Quota Policy Service
by Daniel Luttermann 07 May '13

07 May '13

Hallo zusammen, über den Policy Service von Dovecot zum Abfragen der User Quotas wurde ja schon diskutiert - auch gibt es eine gute Anleitung zum Einrichten, nur leider bekomme ich den Policy Server nicht korrekt konfiguriert. Folgende Fehler werden protokolliert: May 3 22:00:13 mail postfix/smtpd[17463]: warning: access table unix:private/quota-status entry has empty value May 3 22:00:42 mail dovecot: quota-status(daniel(a)dlutt.de): Error: user daniel(a)dlutt.de: Error reading configuration: net_connect_unix(/usr/var/run/dovecot/config) failed: Permission denied Es ist dabei so, dass nach einem Reload der Dienste die erste Mail noch zugestellt wird, die folgende, eingehende Mail dann jedoch abgelehnt wird. Nachfolgend die kompletten Logeinträge: May 3 22:00:12 mail postfix/smtpd[17463]: connect from mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:13 mail postfix/smtpd[17463]: warning: access table unix:private/quota-status entry has empty value May 3 22:00:13 mail postfix/smtpd[17463]: 0EB81172391A: client=mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:13 mail postfix/cleanup[17475]: 0EB81172391A: message-id=<CAKrzS114MaJGND9BxYUiixMMtORmXJqTA3W13B=QAr0YW_nkUg(a)mail.gmail.com> May 3 22:00:13 mail postfix/qmgr[17429]: 0EB81172391A: from=<sender(a)googlemail.com>, size=5409, nrcpt=1 (queue active) May 3 22:00:13 mail postfix/smtpd[17463]: disconnect from mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:13 mail klms-smtp_proxy: Message from sender(a)googlemail.com to daniel(a)dlutt.de passed May 3 22:00:14 mail postfix/smtpd[17482]: connect from localhost[127.0.0.1] May 3 22:00:14 mail postfix/smtpd[17482]: 00776172391C: client=localhost[127.0.0.1], orig_client=mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:14 mail postfix/cleanup[17475]: 00776172391C: message-id=<CAKrzS114MaJGND9BxYUiixMMtORmXJqTA3W13B=QAr0YW_nkUg(a)mail.gmail.com> May 3 22:00:14 mail postfix/qmgr[17429]: 00776172391C: from=<sender(a)googlemail.com>, size=6195, nrcpt=1 (queue active) May 3 22:00:14 mail postfix/smtpd[17482]: disconnect from localhost[127.0.0.1] May 3 22:00:14 mail postfix/smtp[17476]: 0EB81172391A: to=<daniel(a)dlutt.de>, relay=127.0.0.1[127.0.0.1]:10025, delay=1.2, delays=0.54/0.02/0/0.65, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 00776172391C) May 3 22:00:14 mail postfix/qmgr[17429]: 0EB81172391A: removed May 3 22:00:14 mail dovecot: lmtp(17484): Connect from local May 3 22:00:14 mail dovecot: lmtp(17484, daniel(a)dlutt.de) dEa8BE4XhFFMRAAAG4AjPw: sieve: msgid=<CAKrzS114MaJGND9BxYUiixMMtORmXJqTA3W13B=QAr0YW_nkUg(a)mail.gmail.com>: stored mail into mailbox 'INBOX' May 3 22:00:14 mail dovecot: lmtp(17484): Disconnect from local: Successful quit May 3 22:00:14 mail postfix/lmtp[17483]: 00776172391C: to=<daniel(a)dlutt.de>, relay=mail.dlutt.de[private/dovecot-lmtp], delay=0.11, delays=0.05/0.02/0.01/0.03, dsn=2.0.0, status=sent (250 2.0.0 <daniel(a)dlutt.de> dEa8BE4XhFFMRAAAG4AjPw Saved) May 3 22:00:14 mail postfix/qmgr[17429]: 00776172391C: removed May 3 22:00:36 mail postfix/postscreen[17433]: CONNECT from [2607:f8b0:4001:c03::230]:43653 to [2a00:1828:2000:206::2]:25 May 3 22:00:42 mail postfix/postscreen[17433]: PASS NEW [2607:f8b0:4001:c03::230]:43653 May 3 22:00:42 mail postfix/smtpd[17463]: connect from mail-ie0-x230.google.com[2607:f8b0:4001:c03::230] May 3 22:00:42 mail dovecot: quota-status(daniel(a)dlutt.de): Error: user daniel(a)dlutt.de: Error reading configuration: net_connect_unix(/usr/var/run/dovecot/config) failed: Permission denied May 3 22:00:42 mail postfix/smtpd[17463]: NOQUEUE: reject: RCPT from mail-ie0-x230.google.com[2607:f8b0:4001:c03::230]: 450 4.7.1 <daniel(a)dlutt.de>: Recipient address rejected: Internal error occurred. Refer to server log for more information.; from=<absender(a)googlemail.com> to=<daniel(a)dlutt.de> proto=ESMTP helo=<mail-ie0-x230.google.com> May 3 22:00:42 mail postfix/smtpd[17463]: disconnect from mail-ie0-x230.google.com[2607:f8b0:4001:c03::230] May 3 22:00:53 mail postfix/postfix-script[17560]: stopping the Postfix mail system May 3 22:00:53 mail postfix/master[17425]: terminating on signal 15 May 3 22:02:51 mail dovecot: master: Warning: Killed with signal 15 (by pid=17681 uid=0 code=kill) Das Problem tritt mit dem unix_listener, aber auch mit dem inet_listener auf - beide Male beschwert sich Dovecot über den Zugriff auf den Service "config". Ich habe auch mal versucht, die Berechtigungen für den Service "config" auf World-Readable zu setzen, leider hat dies auch nicht geklappt, wobei ich nicht weiß, ob dieser unbedingt mit dem Problem etwas zu tun hat. Auch beim Debug-Logging sind leider nicht mehr Infos zum Fehler zu finden. Zum Einsatz kommt aktuell Postfix 2.10.0 und Dovecot 2.2.1. Die Dovecot Quota Konfiguration sieht so aus, wie bei sys4 beschrieben: service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } client_limit = 1 } Mittlerweile habe ich schon einige Optionen und Berechtigungen ausprobiert, aber der Fehler bleibt leider der gleiche. Hat vielleicht jemand noch einen Tip? Danke schon mal. -- Daniel

6 18

[Dovecot] pop3 login ok then disconnects right away..outlook
by markh 07 May '13

07 May '13

I have dovecot with postfix on ubuntu server 12 I cannot log into outgoing server with outlook. It logs into incoming server ok with outlook. I can telnet pop3 and imap ok. Looking at mail log it looks like dovecot auths: ok then shows pop3-login: Login: user=<user> USER#etc ok ... then next line shows..same second pop3(user): disconnected: Logged out top/0/0 etc. I have tried a lot of combinations with ssl ,tls none Any suggestions...thanks -- View this message in context: http://dovecot.2317879.n4.nabble.com/pop3-login-ok-then-disconnects-right-a… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] v2.2.1 released
by Timo Sirainen 07 May '13

07 May '13

http://dovecot.org/releases/2.2/dovecot-2.2.1.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.1.tar.gz.sig - mailbox_list_index=yes was broken. - LAYOUT=index didn't list subscriptions. - auth: Multiple master passdbs didn't work. - Message parsing (e.g. during search) crashed when multipart message didn't actually contain any parts.

15 25

[Dovecot] Upgrading from 2.0 to 2.2
by Asai 06 May '13

06 May '13

Greetings, Is this possible to upgrade directly from 2.0 to 2.2? If so, is there a guide for doing this? Thank you. -- --Asai

2 1

[Dovecot] imap crash during URLFETCH
by Mike Abbott 06 May '13

06 May '13

Dovecot-2.2.1's imap processes crash reliably when they use an IMAP URL with an invalid access specifier. A backtrace and some debug output follows. The crash is likely caused by imap_urlauth_fetch_parsed() returning 0 without having set *mpurl_r to NULL, and then imap_urlauth_fetch_local() freeing an uninitialized pointer. Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001059 0 libdovecot-storage.0.dylib 0x000000010b06a383 imap_msgpart_url_free + 17 1 imap 0x000000010afc71cc imap_urlauth_fetch_local + 770 2 imap 0x000000010afc6dcf imap_urlauth_fetch_url + 439 3 imap 0x000000010afbb489 cmd_urlfetch + 580 4 imap 0x000000010afbdf4d command_exec + 55 5 imap 0x000000010afbdabb client_command_input + 34 6 imap 0x000000010afbdc7c client_command_input + 483 7 imap 0x000000010afbd351 client_handle_input + 239 8 imap 0x000000010afbc613 client_input + 119 9 libdovecot.0.dylib 0x000000010b111c74 io_loop_call_io + 46 10 libdovecot.0.dylib 0x000000010b112c85 io_loop_handler_run + 214 11 libdovecot.0.dylib 0x000000010b111e1f io_loop_run + 77 12 libdovecot.0.dylib 0x000000010b0d10c6 master_service_run + 24 13 imap 0x000000010afc5aba main + 1010 14 libdyld.dylib 0x00007fff89e5f7bd start + 1 Apr 29 20:00:31 imap(pid 82429 user mja): Debug: Fetching local URLAUTH imap://mja@duck.example.com/INBOX;uidvalidity=1366726248/;uid=19;urlauth=submit+mja:internal:012c9c6a3d74db6509e4a3802a0f5edf64546608b8 Apr 29 20:00:31 imap(pid 82429 user mja): Debug: Failed to fetch URLAUTH "imap://mja@duck.example.com/INBOX;uidvalidity=1366726248/;uid=19;urlauth=submit+mja:internal:012c9c6a3d74db6509e4a3802a0f5edf64546608b8": No 'submit+mja' access allowed for user mja Apr 29 20:00:31 imap(pid 82429 user mja): Fatal: master: service(imap): child 82429 killed with signal 11 (core dumps disabled)

2 3

[Dovecot] doveadm search causes replication error message
by Oli Schacher 06 May '13

06 May '13

Hi # 2.2.1 (83d83f55e5c2+) / dsync replicated setup I just noticed that 'doveadm search' apparently tries to replicate mailboxes and spits out errors if a mailbox in the search query is not found: #doveadm search -u user(a)example.com mailbox Spamreport doveadm(user(a)example.com): Error: Syncing mailbox Spamreport failed: Mailbox doesn't exist: Spamreport this is especially problematic with -A searches as this causes a error message for every user which doesn't have that folder. Is this a bug or intended behaviour? Should I just 2>/dev/null these errors in doveadm scripts? Thanks Oli -- message transmitted on 100% recycled electrons

2 2

[Dovecot] SELECT/EXAMINE don't report URLMECH
by Mike Abbott 06 May '13

06 May '13

In dovecot-2.2.1 neither the SELECT nor the EXAMINE commands include an untagged URLMECH reply. (Note, this is not the one mandated by the RESETKEY command.) AFAICT RFC 4467 does not require an URLMECH reply to SELECT or EXAMINE but without it clients have no way of knowing about authorization mechanisms other than INTERNAL. Now I know dovecot-2.2 supports only the INTERNAL mechanism at present so this is probably harmless, but still I think it's worthwhile to ask: Is the absence of the URLMECH reply intentional or an oversight? For comparison Apple's enhanced dovecot replies: c1 select inbox [...] * OK [URLMECH INTERNAL] Mechanisms supported c1 OK [READ-WRITE] Select completed.

2 1

[Dovecot] many SSH connexions with dsynx/SSH replication
by Emmanuel Dreyfus 06 May '13

06 May '13

Hi I am trying replication over dsync/ssh, as explained there: http://wiki2.dovecot.org/Replication I added the options below to dovecot.conf. It works, but it seems there is a new SSH connexion for each user, which is a bit overkill performance-wise. Since I sync as root, I guess there is a way of haing everything on the same SSH connexion? --- cut here --- mail_plugins = $mail_plugins notify replication service replicator { process_min_avail = 1 } dsync_remote_cmd = ssh -lroot %{host} doveadm dsync-server -u%u plugin { mail_replica = remote:root@mail1.example.net } service aggregator { fifo_listener replication-notify-fifo { user = dovecot } unix_listener replication-notify { user = dovecot } } service replicator { unix_listener replicator-doveadm { mode = 0600 } } service doveadm { inet_listener { port = 12345 ssl = yes } } doveadm_port = 12345 ssl_client_ca_file = /etc/openssl/certs/ca.crt doveadm_proxy_port = 0 --- cut here --- -- Emmanuel Dreyfus manu(a)netbsd.org

2 1

[Dovecot] dsyncing lazy_expunge namespace
by Angel L. Mateo 06 May '13

06 May '13

Hello, I'm in the process of migrating mailbox from one dovecot server running dovecot 2.1.9 with mailboxes stored in maildir format to a newer one running 2.1.16 with mailboxes stored in mdbox format. To migrate mailboxes I'm using dsync as explained at http://wiki2.dovecot.org/Tools/Dsync. The command I'm running in the newer server is: sudo dsync -o mailbox_list_index=no mirror -R -u <user> imapc: The mailbox of the user is correctly synced to the newer server, except the lazy_expunge namespace, which is not synced at all. The config in my old server is: namespace { # hidden = yes # list = no # Temporally, only for migration hidden = no list = yes location = maildir:~/Maildir/expunged prefix = BORRADOS. separator = . } and in the newer one is: namespace { hidden = yes list = no location = mdbox:%h/expunged:INDEX=/mail/indexes/%2Ln/%Ln/expunged prefix = BORRADOS/ separator = / } With a tcpdump I have checked that old servers list the namefolder, this is the IMAP dialog for an example user: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. 2 AUTHENTICATE PLAIN YW5nZWwubHVpcwBtYXN0ZXIAVkFzR293ZW0= 2 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE QUOTA ACL RIGHTS=texk] Logged in 1 LIST "" "" * LIST (\Noselect) "." "" 1 OK List completed. 3 LIST "" "*" * LIST (\HasNoChildren) "." "SPAM" * LIST (\HasNoChildren) "." "Trash" * LIST (\HasNoChildren) "." "Drafts" * LIST (\HasNoChildren) "." "INBOX" * LIST (\Noselect \HasNoChildren) "." "BORRADOS" 3 OK List completed. 4 STATUS "SPAM" (UIDNEXT UIDVALIDITY) * STATUS "SPAM" (UIDNEXT 3 UIDVALIDITY 1316372649) 4 OK Status completed. 5 EXAMINE "SPAM" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) ... But "BORRADOS" is never selected in the rest of the dialog. Any idea? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

2 1

[Dovecot] XFS vs EXT4 for mail storage
by Charles Marcus 05 May '13

05 May '13

Hello, I'm in the process of finalizing the spec for my new dovecot VM, and this is the last question I need to address... I've read until I'm just about decided on XFS, but I have no experience with it (been using reiserfs on my old box (@ 8 yrs old now), and never had a problem (knock on wood), but considering its current situation (little to no development support for reasons everyone is aware of), I've decided now is the time to switch. It came down to XFS or EXT4, and I like what I've read about XFS, but am unsure how to tune it (or even if I should). I've decided to use mdbox for storage (been using maildir), and will enable SIS for attachments. So, anyone (Stan?) have any suggestions? Should I go with EXT4? Or XFS with just the defaults? Or XFS with one or more tuned parameters? Appreciate any suggestions (including links to docs dealing with tuning XFS for my mail storage conditions that are written more at the layman level) or comments from anyone experienced using both... Thanks, -- Best regards, Charles

11 37

Re: [Dovecot] qmail-ldap LDA Delivery and sieve
by Deepak 04 May '13

04 May '13

Hi I used the below filter in my dovecot-ldap-userdb.conf file, user_attrs = homeDirectory=home, uidNumber=uid, gidNumber=gid user_filter = (&(objectClass=posixAccount)(|(mail=%u)(mailAlternateAddress=%u) (uid=%u))) This above filter was working fine for me, and it's delivering fine for all the domains. seive is also working fine. The "-d" in dovecot-lda will do userdb lookup with ldap.

1 0

[Dovecot] dovecot antispam plugin is not woking
by Ravi Kanchan 04 May '13

04 May '13

Hi All, I am using dovecot version 2.0.9 DSPAM Anti-Spam Suite 3.10.2 (agent/library) ClamAV 0.97.7/17102 and dspam antispam plugin dovecot-antispam-plugin-43880985e3dd and plugin configuration is given below: protocol imap { mail_plugins = " antispam autocreate" } protocol pop3 { mail_plugins = antispam autocreate } plugin { antispam_allow_append_to_spam = YES antispam_backend = dspam antispam_crm_args = --config=/home/vmail antispam_dspam_args = --client;--user vmail antispam_dspam_binary = /usr/bin/dspam antispam_dspam_notspam = --class=innocent antispam_dspam_result_header = X-DSPAM-Result antispam_dspam_spam = --class=spam antispam_mail_tmpdir = /tmp antispam_signature = X-DSPAM-Signature antispam_signature_missing = error antispam_spam = Spam } dspam bin path: [root@sogo ~]# which dspam /usr/bin/dspam but my dspam plugin configuration is not working. and I am not getting any log from dspam. My dspam server is working prefect. cna anyone help me Regard's Ravi Kanchan Sharma

4 8

[Dovecot] Dovecot has no understandable configuration any more
by forum 04 May '13

04 May '13

Hello, for many years i used an mailserver with dovecot V1 very satisfied! http://mailserver.decotrain.de/ One of the reasons to use dovecot was a simply configuration. Dovecot was the best choice for IMAP for me! Now i updated the server to Debian testing with dovecot 2.1.7. It's not possible for me to get a running authentication for virtual mail users! I recently found this mailing and have the same problem: http://www.dovecot.org/list/dovecot/2012-March/064181.html The documentation says *nothing* about my problem how to authenticate with mysql! http://wiki2.dovecot.org/VirtualUsers I can solve the problem only with try and error without a chance in this complex system. It's nice to have all this possibilites but they are not useful if not documented. There should be some clear examples for different scenarios to be found in your wiki. My problem at this time: I don't know how to configure the userdb to work with mysql authentification? All mail is running under the special user mail. dovecot.conf ============ disable_plaintext_auth = yes passdb { driver = sql # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext args = /etc/dovecot/dovecot-sql.conf } userdb { driver = prefetch } first_valid_uid = 8 last_valid_uid = 8 first_valid_gid = 8 last_valid_gid = 8 mail_location = maildir:/srv/mail/%d/%n dovecot-sql.conf ================ driver = mysql connect = host=/var/run/mysqld/mysqld.sock dbname=... => WORKS! default_pass_scheme = SHA1 password_query = SELECT password, '/srv/mail/%d/%n' AS home, 'mail' AS uid, 'mail' AS gid FROM user WHERE username = '%n' AND domain = '%d' AND IMAP_allowed = 'YES' Errors ====== Apr 30 10:28:22 auth: Debug: client out: OK 1 user=xxxx@yyyy home=/srv/mail/yyyy/xxxx uid=mail gid=mail Apr 30 10:28:22 auth: Debug: master in: REQUEST 3163291649 5347 1 87066c907eef8f4e5ed71319b560dd2a Apr 30 10:28:22 auth: Error: prefetch(xxxx@yyyy,::1,<doTKyI/brgAAAAAAAAAAAAAAAAAAAAAB>): userdb lookup not possible with only userdb prefetch Apr 30 10:28:22 auth: Error: userdb(xxxx@yyyy,::1,<doTKyI/brgAAAAAAAAAAAAAAAAAAAAAB>): user not found from userdb prefetch Apr 30 10:28:22 auth: Debug: master out: NOTFOUND 3163291649 Apr 30 10:28:22 imap: Error: Authenticated user not found from userdb, auth lookup id=3163291649 (client-pid=5347 client-id=1) Apr 30 10:28:22 imap-login: Info: Internal login failure (pid=5347 id=1) (internal failure, 1 succesful auths): user=<karsten(a)dct.mine.nu>, method=PLAIN, rip=::1, lip=::1, mpid=5352, secured, session=<doTKyI/brgAAAAAAAAAAAAAAAAAAAAAB> I have no idea how to solve the problem and up to know i could not find an example with google. Please help. Best regards Karsten

8 11

[Dovecot] Accessing mail files not owned by imap login user
by PaulM47 03 May '13

03 May '13

Hi, I have managed to set up a 'maildir' based mail system using fetchmail and procmail that delivers sorted mail to folders /var/spool/mail/user1, ../user2 etc. 'user1', 'user2' etc. are real users but the mail system is run under logged in user 'mailserver'. The mail folders are owned by 'user1', 'user2' etc. but mail files, when delivered, are owned by 'mailserver'. I've been unable to find a way to change this behaviour :-( Dovecot is configured by adding the single line 'mail_location = maildir:/var/spool/mail/%u' to 'dovecot.conf', everything else is as installed. When I make an imap connection as 'user1' the logon is successful, the mail files are moved from ../new/ to ../cur/ but are invisible to the imap client. If I 'chown' the mail files to 'user1' they instantly become visible to the imap client. I gather from googling info on dovecot I can configure dovecot to allow 'user1', when logged in, to access the mail files owned by 'mailserver'. Is this simple to do, and if so how do I do it please ? Thanks PaulM -- View this message in context: http://dovecot.2317879.n4.nabble.com/Accessing-mail-files-not-owned-by-imap… Sent from the Dovecot mailing list archive at Nabble.com.

3 3

[Dovecot] feature request: pipe for custom quota dict queries
by Jeff Gustafson 03 May '13

03 May '13

Just a followup to my previous post. I appears that a pipe for quota queries via dict is not supported right now. Because of the way we group things we need more flexibility. I'd like to propose that dovecot should support quota queries just like userdb dict queries. My expertise is not C, but I might try to poke around and see if I can make something work. ...Jeff

1 0

[Dovecot] sieve: deleteheader sometimes fails [bug]
by Daniel Piddock 03 May '13

03 May '13

Hi, We're using Dovecot 2.1.16 with Pigeonhole 0.3.4. Mail is delivered by exim4 to the dovecot LDA. Sometimes users are unable to delete headers. I've narrowed the problem down to preceding the deleteheader command with a query against the body. A simple example: """ require ["body", "editheader", "fileinto"]; if body :contains "!TEST!" { fileinto "INBOX.Trash"; stop; } deleteheader "Subject"; addheader "Subject" "Testing"; """ Putting the "deleteheader" above the "if body" causes it to be deleted correctly. Although I've used Subject in this example it happens for other headers. Cheers, Dan

2 5

[Dovecot] dovecot 1.2.5 Fatal: setgid(5000(vmail)) Operation not permitted
by Mosh Mage 03 May '13

03 May '13

This is the error I'm getting (whenever i recieve and email): *deliver() : Fatal: setgid(5000(vmail)) failed with euid=5000(vmail), gid=8(mail), egid=8(mail): Operation not permitted (This binary should probably be called with process group set to 5000(vmail) instead of 8(mail)) * I am at loss. I have tried "everything" i could think of (besides purging the machine and do it all over again, which is not an option -- unless it is). Can anyone help me fix this? # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 3.2.13-grsec-xxxx-grs-ipv6-64-vps x86_64 Debian 6.0.6 ext3 log_timestamp: %Y-%m-%d %H:%M:%S disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login verbose_proctitle: yes mail_uid: vmail mail_gid: vmail mail_location: maildir:/var/zpanel/vmail/%d/%n mail_debug: yes mbox_write_locks: fcntl dotlock auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf 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: 432 user: vmail group: vmail plugin: trash: /etc/dovecot/dovecot-trash.conf # /etc/dovecot/dovecot-sql.conf driver = mysql connect = host=localhost dbname=zpanel_postfix user=USERNAME password=AWESOMEPASSWORD default_pass_scheme = PLAIN password_query = \ SELECT name, domain, password \ FROM mailbox WHERE name = '%n' AND domain = '%d' user_query = \ SELECT maildir \ FROM mailbox WHERE name = '%n' AND active = '1' AND domain = '%d' #This is my ls -la drwxrwsrwx 5 vmail vmail 4096 May 2 18:39 vmail #and this is inside vmail/ drwx--S--- 3 vmail vmail 4096 May 2 18:39 asfaltotejo.com drwx--S--- 3 vmail vmail 4096 May 2 12:35 gestaoconteudos.pt drwx--S--- 17 vmail vmail 4096 May 2 15:34 tribanet.com #/var/run/dovecot srw-rw---- 1 vmail vmail 0 May 2 19:46 auth-master srw------- 1 root root 0 May 2 19:46 auth-worker.6564 srwxrwxrwx 1 root root 0 May 2 19:46 dict-server lrwxrwxrwx 1 root root 25 May 2 19:46 dovecot.conf -> /etc/dovecot/dovecot.conf drwxr-x--- 2 root dovecot 4096 May 2 19:46 login

1 0

[Dovecot] CATENATE allows zero parts
by Mike Abbott 03 May '13

03 May '13

I'm pleased to see that dovecot-2.2 includes support for RFCs 4467 and 4469 (URLAUTH and CATENATE). I have begun testing these features (in dovecot-2.2.1) and comparing their functionality against Apple's implementation. So far I have discovered a few inconsistencies. I will report each of these, and any more that I may find, in separate threads. The first issue is that using CATENATE with no message parts works but, IMO, shouldn't: a2 append inbox catenate () a2 OK [APPENDUID 1366726248 9] Append completed. For comparison this is how Apple's enhanced dovecot in OS X Server handles this request: a2 append inbox catenate () a2 BAD Invalid arguments. According to RFC 4469 section 3 CATENATE requires "one or more message parts." This is formalized in section 5: append-data =/ "CATENATE" SP "(" cat-part *(SP cat-part) ")" and in RFC 3501 section 9 which states that "[ABNF] rules MUST be followed strictly." I believe that permitting zero cat-parts is contrary to the RFC, although I can understand permitting it under the general doctrine of "servers should be liberal in what they accept, and clients strict in what they send." Is accepting zero cat-parts an intentional exception to the RFC or an oversight?

2 2