June 2010 - dovecot - dovecot.org

[Dovecot] userdb prefetch not compatible with ssl_require_client_cert
by zhong ming wu 04 Jun '10

04 Jun '10

Dear List I looked into docs but couldn't see any where that says of this incompatibility. Anywhere this is confirmed in the doc? Thanks mr.wu

2 3

[Dovecot] 'doveadm who' enhancement request
by Brad Davidson 04 Jun '10

04 Jun '10

When Dovecot is in proxy mode, the client sends along the original connection endpoints in an ID command. Is there any chance 'doveadm who' could use this to display the original connection source? As it currently stands, all I see is a bunch of connections from the proxy. Thanks! --- Brandon 'Brad' Davidson Virtualization Systems Administrator University of Oregon Information Services (541) 346-8098 brandond(a)uoregon.edu

3 7

[Dovecot] v2.0.beta4: conversion of v1.2 configuration
by Pascal Volk 04 Jun '10

04 Jun '10

Hi Timo, I've just tried to convert my v1.2 configuration to a v2.0 configuration. Below a few obsolete warnings, among others "mail_executable has been replaced by service { executable }", was an interesting error: "doveconf: Error: duplicate listener: 198:" The broken parts of the converted configuration: # 2.0.beta4 (84ffb38839b9): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-trunk-amd64 x86_64 Debian squeeze/sid listen = 192.168.111.222 [2a01 service imap-login { inet_listener imap { port = 198 } } service managesieve-login { inet_listener managesieve { port = 198 } } service managesieve { executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/managesieve } service pop3-login { inet_listener pop3 { port = 198 } } # missing section: #protocol lda { # … #} # missing setting #postmaster_address The corresponding parts from v1.2 configuration: protocols = imap imaps managesieve pop3 pop3s listen = 192.168.111.222 [2a01:198:37a:1::1] protocol managesieve { mail_executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/managesieve } protocol lda { postmaster_address = f007ba11.1008605(a)localdomain.org mail_plugins = sieve } Why is the lda section missing? Because it is not listed in v1.2's protocols setting? (only an idea/wild guess) Regards, Pascal -- The trapper recommends today: deadbeef.1008606(a)localdomain.org

3 3

[Dovecot] Panic with mail_log activated
by Xavier Pons 04 Jun '10

04 Jun '10

Hi, We get intermitend deliver-errors when we have activated the mail_log plugin. The installed version is dovecot-2.0-beta5. Below, the error we get: Jun 02 21:58:11 lda(xxx(a)uib.es): Panic: file mail-log-plugin.c: line 364 (mail_log_mail_transaction_commit): assertion failed: (ret) Jun 02 21:58:11 lda(xxx(a)uib.es): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x31c4a35dd0] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x37) [0x31c4a35eb7] -> /usr/lib/dovecot/libdovecot.so.0 [0x31c4a352f8] -> /usr/lib/dovecot/lib20_mail_log_plugin.so [0x2ba85f9a6369] -> /usr/lib/dovecot/lib15_notify_plugin.so(notify_contexts_mail_transaction_commit+0x76) [0x2ba85f7a3716] -> /usr/lib/dovecot/lib15_notify_plugin.so [0x2ba85f7a3b49] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x3d) [0x31c4e2d5bd] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x255) [0x31c5205585] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0xd3) [0x31c5205903] -> /usr/libexec/dovecot/deliver(main+0x63a) [0x402c0a] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x324d01d994] -> /usr/libexec/dovecot/deliver [0x402509] it's a bug or a misconfiguration? thanks Xavier

3 5

[Dovecot] SORT with unknown charset bug?
by A.L.E.C 04 Jun '10

04 Jun '10

I'm not sure this is a known bug. I'm using dovecot 1.1.19. C: s SORT (DATE) blah ALL UNDELETED OR HEADER SUBJECT {4} S: + OK C: asdf HEADER FROM {4} S: + OK C: asdf S: * SORT 1 2 4 5 3 6 7 (... all messages in folder) S: s NO [BADCHARSET] Unknown charset I think there shouldn't be "* SORT... " response. -- Aleksander 'A.L.E.C' Machniak http://alec.pl gg:2275252 LAN Management System Developer http://lms.org.pl Roundcube Webmail Developer http://roundcube.net

2 3

[Dovecot] Auto forward virtual users mail using Sieve
by Julian Baker 04 Jun '10

04 Jun '10

Hi All I'm trying to configure Dovecot to automatically forward mail to another account without the virtual user having to log-in first to Roundcube web mail. These are virtual users with no log-in to the server only Roundcube's web interface The situation is that I have two domains only who want to receive email at their domains, get a forwarded copy at their hotmail account, then log-in to Roundcube to reply. A Sieve script running in Dovecot seems the way to go, but the finer points of configuration have failed me. I got as far as 1) /etc/dovecot/dovecot.conf Adding: protocol lda { mail_plugins = cmusieve mail_plugin_dir = /usr/lib/dovecot/modules/lda } 2) /var/vmail/___domain___/___user___/.dovecot.sieve Created the .dovecot.sieve file in the domain/user directory and added: require ["fileinto ","reject","vacation","imapflags","relational","regex","notify"]; # Resend a copy of the message to another address # if true { redirect "julian(a)flatearth.co.uk"; } Which doesn't seem to have broken anything. Or worked. I'm assuming that as /var/vmail/___domain___/___user___/ is their virtual user home/mail spool the '.dovecot.sieve' file will get picked up. It seems that Dovecot isn't configured to use send via Deliver ? My conf is pasted before (Exim handles regular domain email forwarding mail for a bunch of virtual domains to pop accounts.) TIA Julian dovecot --version 1.0.rc15 ovecot -n # /etc/dovecot/dovecot.conf protocols: imap imaps pop3 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 login_process_size: 64 verbose_proctitle: yes first_valid_uid: 102 first_valid_gid: 104 mail_privileged_group: Debian-exim mail_location: maildir:/var/vmail/%d/%n/ mbox_write_locks: fcntl mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 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 imap_client_workarounds(default): delay-newmail outlook-idle netscape- eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle namespace: type: private separator: . prefix: INBOX. inbox: yes namespace: type: private separator: . inbox: yes hidden: yes auth default: verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch args: /etc/dovecot/dovecot-sql.conf Roundcube v0.3.0 _______________________________________________ F L A T E A R T H I N D U S T R I E S L T D Julian Baker - Email: julian(a)flatearth.co.uk - AIM: juliobesq Phone: +44 (0)20 7916 4801 - Mobile: +44 (0)7961 307879 124 Agar Grove, London NW1 9TY, UK - www.flatearth.co.uk · DESIGN FOR PIXELS · PRINTING BY HAND · Privileged/Confidential information may be contained in this message. If you are not the intended addressee you should destroy this message & kindly notify the sender by reply email. Opinions, conclusions & other information in this message that do not relate to the official business of Flat Earth shall be understood as neither given nor endorsed by it.

3 4

Re: [Dovecot] auth socket goes away on reload
by David Jonas 03 Jun '10

03 Jun '10

On 6/3/10 , Jun 3, 9:45 AM, Jerrale Gayle wrote: > On 6/3/2010 12:35 PM, David Jonas wrote: >> We're using the SQLite backend for authentication of Postfix SASL. When >> the db is replaced we HUP dovecot to close and reopen its connection. >> During this time it appears the socket file is removed and Postfix >> rejects the authentication attempt. From the logs: >> >> Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading >> configuration >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to >> private/auth failed: Connection refused >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: >> SASL LOGIN authentication failed: >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from >> unknown[dd.dd.dd.dd]: 554 5.7.1<user(a)example.com>: Relay access denied; >> from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP >> helo=<localhost.localdomain> >> >> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: >> SASL LOGIN authentication failed: Connection lost to authentication >> server >> Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH >> from unknown[dd.dd.dd.dd] >> >> Is there an obvious way around this? I know I could somehow merge the >> changes into the running sqlite db but that undermines the simplicity of >> the design I have. Maybe a patch to reopen the db if it's replaced? Or >> perhaps I should just switch to a different db format -- that's probably >> the quickest/easiest solution. Any other ideas? There are about 20k >> entries to deal with. >> >> Thanks, >> >> David >> >> > the HUP reload method is only available on dovecot 2.0. Make sure > you're using that version to do that; otherwise, killall dovecot and > then dovecot. I should have specified that this is dovecot 1.2.7. The sighup seems to work just fine except for the effect I've outlined.

2 1

[Dovecot] Sieve GUI
by Gerhard Waldemair 03 Jun '10

03 Jun '10

> Is there à GUI for sieve. > > I don't have installed Squrielmail, but won't like to manage the > Rules per ssh

13 19

[Dovecot] auth socket goes away on reload
by David Jonas 03 Jun '10

03 Jun '10

We're using the SQLite backend for authentication of Postfix SASL. When the db is replaced we HUP dovecot to close and reopen its connection. During this time it appears the socket file is removed and Postfix rejects the authentication attempt. From the logs: Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading configuration Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to private/auth failed: Connection refused Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: SASL LOGIN authentication failed: Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from unknown[dd.dd.dd.dd]: 554 5.7.1 <user(a)example.com>: Relay access denied; from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP helo=<localhost.localdomain> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: SASL LOGIN authentication failed: Connection lost to authentication server Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH from unknown[dd.dd.dd.dd] Is there an obvious way around this? I know I could somehow merge the changes into the running sqlite db but that undermines the simplicity of the design I have. Maybe a patch to reopen the db if it's replaced? Or perhaps I should just switch to a different db format -- that's probably the quickest/easiest solution. Any other ideas? There are about 20k entries to deal with. Thanks, David

2 1

Re: [Dovecot] auth socket goes away on reload
by William Blunn 03 Jun '10

03 Jun '10

On 03/06/2010 19:08, David Jonas wrote: > On 6/3/10 , Jun 3, 10:16 AM, William Blunn wrote: > >> On 03/06/2010 17:35, David Jonas wrote: >> >>> We're using the SQLite backend for authentication of Postfix SASL. When >>> the db is replaced we HUP dovecot to close and reopen its connection. >>> During this time it appears the socket file is removed and Postfix >>> rejects the authentication attempt. From the logs: >>> >>> Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading >>> configuration >>> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to >>> private/auth failed: Connection refused >>> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: >>> SASL LOGIN authentication failed: >>> Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from >>> unknown[dd.dd.dd.dd]: 554 5.7.1<user(a)example.com>: Relay access denied; >>> from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP >>> helo=<localhost.localdomain> >>> >>> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: >>> SASL LOGIN authentication failed: Connection lost to authentication >>> server >>> Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH >>> from unknown[dd.dd.dd.dd] >>> >>> Is there an obvious way around this? I know I could somehow merge the >>> changes into the running sqlite db but that undermines the simplicity of >>> the design I have. Maybe a patch to reopen the db if it's replaced? Or >>> perhaps I should just switch to a different db format -- that's probably >>> the quickest/easiest solution. Any other ideas? There are about 20k >>> entries to deal with. >>> >> It sounds like your updates arrive in the shape of entire-table updates. >> >> That is no problem. You can easily apply entire-table updates to the >> database without having to re-create the SQLite database file, and >> without having to tell Dovecot. >> >> Just create a new table (with a different name) inside the SQLite >> database file, with the new content, then snap it into place using a >> pair of table renames inside a transaction; then delete the old table. >> >> That way you don't need to re-create the database file or HUP Dovecot, >> and Dovecot will only ever see the old data or the new data. >> > That sounds reasonable, not sure why I didn't think of it! Thanks. > If you are going to keep the SQLite database around, you might want to look at vacuuming it periodically using either VACUUM or the auto_vacuum PRAGMA depending on what fits your context best. http://sqlite.org/lang_vacuum.html http://sqlite.org/pragma.html#pragma_auto_vacuum Bill

2 2