- dovecot - dovecot.org

[Dovecot] IDLE with inotify problem
by Michael Guntsche 22 Sep '07

22 Sep '07

Hi, I recently switched from courier imap to dovecot. With courier I had a working IDLE setup that informed me immediately when new mail arrived. With Dovecot it is different, sometimes i get an immediate result but most of the time it takes a rather long time for the notification to return to the client. For testing purposes I set mailbox_idle_check_interval = 1 and i now get the same behaviour as with couier (a new mail immediately causes a notification) but i am not sure that this is the right solution. Reading the comments in the config files I was under the impression that this is not needed if dovecot uses inotify. Setup: Kernel 2.6.22.1 with inotify dovecot 1.0.3 from debian unstable Build options: ioloop=epoll notify=inotify ipv6 openssl So my question is can I check that dovecot is actually using inotify? Kind regards, Michael

4 10

[Dovecot] Problems with quota dict in 1.1.alpha4
by arvids 22 Sep '07

22 Sep '07

Hello, there are problems with quota dict when multiple dovecot deliver processes are launched in parallel. It can be reproduced by sending a mail with multiple different recipients - the mail is delivered OK to all recipients, but the quota are not updated correctly in sql. I looked at the code and it seems that the problem is somewhere in dict cache. If I configure in Postfix max number of deliver processes to 1, dict quota is updated correctly. postconf -n output: # 1.1.alpha4: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ syslog_facility: local0 protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/pop3-login login_greeting: Server. login_process_per_connection: no login_process_size: 64 verbose_proctitle: yes first_valid_uid: 95 first_valid_gid: 95 mail_uid: 95 mail_gid: 95 mail_location: maildir:~/Maildir mail_debug: yes fsync_disable: yes mail_executable: /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins: quota mail_plugin_dir: /usr/local/dovecot/lib/dovecot/pop3 pop3_enable_last: yes pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 cram-md5 apop cache_size: 2048 cache_ttl: 28800 cache_negative_ttl: 60 user: doveauth verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: dict:::proxy:/var/run/dovecot/dict-server:quotadict dict: quotadict: mysql:/usr/local/dovecot/etc/dovecot-sql-dict-quota.conf Regards, Arvids

2 4

[Dovecot] Feature Request for Proxy
by Ed W 22 Sep '07

22 Sep '07

Hi, Quick feature request for the proxy function: I have a couple of machines which are all customer facing and customer mailbox lives on any one of them. Customer can login to any machine and the proxy feature then forwards them to the correct machine (often the machine they are already connected to). However, right now if the SQL query simply returns the IP of the correct machine, and this happens to be the same machine that the connection is already on, then we get the auth process stuck in an infinite loop (and generating a lot of log files...) The quick fix is to customise each installation and add some kind of WHERE clause to change the results IF result is already the same as the machine we are on. However, this is error prone when setting up new machines and it's easy to forget or make a typo adjusting the config files. In my case I am using vservers and it's quite neat to be able to simply copy the whole image and fire it up on a new IP to test an upgrade, etc, hence easy to mess up adjusting the conf files when creating a new image. Any suggestions on how this could be done more dynamically, or else could I raise a feature request that the auth process somehow realises when it's being forwarded to an IP address that it's actually listening on already already (ie it's a request which loops back to itself), thus simplifying the config files? I haven't cracked open the code, but it sounds somewhat possible to check the list of IP addresses we are currently listening on and check that the proxy dest isn't among them? Cheers Ed W

2 1

[Dovecot] maildir rename_subfolders() and listescape interaction
by pod 22 Sep '07

22 Sep '07

I'd like to flag a problem we are observing that looks like it is caused by the listescape-plugin.c. I realize that this plugin is not part of the standard Dovecot 1.0 distribution but I would appreciate any insights or suggestions for fixes that anyone is kind enough to offer. The problem concerns subfolder renames when used in conjunction with Maildir folders (I've not tested this against any other folder type). Without listescape plugin: mail_location: maildir:%h/Maildir:INDEX=%h/index:CONTROL=%h/control mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota namespace: type: private separator: / inbox: yes 01 LIST "" * * LIST (\HasNoChildren) "/" "INBOX" 01 OK List completed. 02 CREATE a 02 OK Create completed. 03 CREATE a/b 03 OK Create completed. 04 LIST "" * * LIST (\HasChildren) "/" "a" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "a/b" 04 OK List completed. 05 RENAME a c 05 OK Rename completed. 06 LIST "" * * LIST (\HasChildren) "/" "c" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "c/b" 06 OK List completed. 07 LOGOUT * BYE Logging out 07 OK Logout completed. With listescape plugin: mail_location: maildir:%h/Maildir:INDEX=%h/index:CONTROL=%h/control mail_plugins(default): quota imap_quota listescape mail_plugins(imap): quota imap_quota listescape namespace: type: private separator: / inbox: yes 01 LIST "" * * LIST (\HasNoChildren) "/" "INBOX" 01 OK List completed. 02 CREATE a 02 OK Create completed. 03 CREATE a/b 03 OK Create completed. 04 LIST "" * * LIST (\HasChildren) "/" "a" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "a/b" 04 OK List completed. 05 RENAME a c 05 NO Internal error occurred. Refer to server log for more information. [2007-08-30 19:33:41] 06 LIST "" * * LIST (\HasNoChildren) "/" "a/b" * LIST (\HasNoChildren) "/" "c" * LIST (\HasNoChildren) "/" "INBOX" 06 OK List completed. 07 LOGOUT * BYE Logging out 07 OK Logout completed. Seemingly the only relevant log entry is @4000000046d70d8f1f72b66c dovecot: Error: IMAP(pod): rename(/srv/mail/home/test0/pod/Maildir/.a/b, /srv/mail/home/test0/pod/Maildir/.c/b) failed: No such file or directory Note the response to tag 05 in each case. The 06 list response in the listescape case is not unexpected given the nature of the failure. My initial reading of rename_subfolders() from maildir-storage.c suggests that the calls through maildir_mailbox_list_init() and maildir_mailbox_list_next() are returning "external" style names (i.e. ones that present "/" as the hierarchy separator) to rename_subfolders(), which is an "internal" helper function. This is supported by the logged error message. I am afraid I am yet to get my head around the actual code path and the escaping and unescaping that is going on so am not able to suggest a fix as yet.

2 2

[Dovecot] Dovecot as LDA issues - please help
by Placid Publishing, LLC 22 Sep '07

22 Sep '07

I'm trying to get dovecot to work as an LDA with dspam; so I can run the dspam dovecot plugin for drag and drop spam/ham learning. Here is my config info: Version 1.0.5 base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cipher_list: ALL:!LOW login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: Welcome Mail. login_processes_count: 1 login_max_processes_count: 10 max_mail_processes: 20 verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_extra_groups: mail mail_location: maildir:/usr/local/virtual/%d/%n mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): dspam mail_plugins(imap): dspam mail_plugins(pop3): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/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 pop3_no_flag_updates(default): no pop3_no_flag_updates(imap): no pop3_no_flag_updates(pop3): yes pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /usr/local/etc/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 dovecot-sql config: driver = mysql password_query = SELECT password, 1011 AS uid, 1011 AS gid FROM users WHERE userid = '%u' user_query = SELECT 1011 AS uid, 1011 AS gid FROM users WHERE userid = '%u' dspam.conf (for delivery): TrustedDeliveryAgent "/usr/local/libexec/dovecot/deliver -d %u" UntrustedDeliveryAgent "/usr/local/libexec/dovecot/deliver -d %u" QuarantineAgent "/usr/local/libexec/dovecot/deliver -d %u -m Junk The error I get when running /usr/local/libexec/dovecot/deliver -c dovecot.conf -d username Sep 19 22:55:57 pelorus dovecot: auth-worker(default): mysql: Connected to localhost (db) Sep 19 22:55:57 pelorus deliver(support): auth input: support Sep 19 22:55:57 pelorus deliver(support): auth input: uid=1011 Sep 19 22:55:57 pelorus deliver(support): auth input: gid=1011 Sep 19 22:55:57 pelorus deliver(support): chdir(/root) failed: Permission denied Sep 19 22:55:57 pelorus deliver(support): maildir: data=/usr/local/virtual//support Sep 19 22:55:57 pelorus deliver(support): maildir: root=/usr/local/virtual//support, index=/usr/local/virtual//support, control=, inbox= maillog output when trying to deliver mail: Sep 19 22:57:13 pelorus postfix/smtpd[38846]: connect from py-out-1112.google.com[64.233.166.179] Sep 19 22:57:14 pelorus postfix/smtpd[38846]: NOQUEUE: filter: RCPT from py-out-1112.google.com[64.233.166.179]: <user(a)domain.com>: Recipient address triggers FILTER dspam:unix:/var/run/dspam/dspam.sock; from=<user(a)gmail.com> to=<support(a)exotixboard.com> proto=ESMTP helo=<py-out-1112.google.com> Sep 19 22:57:14 pelorus postfix/smtpd[38846]: B868B6CF83: client=py-out-1112.google.com[64.233.166.179] Sep 19 22:57:14 pelorus postfix/cleanup[38853]: B868B6CF83: message-id=<436c6f2f0709192057w17904ae5m83655736dc01929a(a)mail.gmail.com> Sep 19 22:57:14 pelorus postfix/qmgr[33660]: B868B6CF83: from=<user(a)gmail.com>, size=2040, nrcpt=1 (queue active) *Sep 19 22:57:14 pelorus dspam[33675]: Delivery agent returned exit code 67: /usr/local/libexec/dovecot/deliver -d user(a)domain.com* Sep 19 22:57:14 pelorus postfix/lmtp[38854]: B868B6CF83: to=<user(a)domain.com>, relay=mail2.domain.com[/var/run/dspam/dspam.sock], delay=1, delays=1/0/0/0.02, dsn=4.3.0, status=deferred (host mail2.exotixboard.com[/var/run/dspam/dspam.sock] said: 421 4.3.0 <user(a)domain.com> Auto-Whitelisted (in reply to end of DATA command)) My virtual users directory (/usr/local/virtual) is chowned vmail:vmail is chmodded 0777 for testing purposes. My question is, how can I get this to work? What is the "Sep 19 22:55:57 pelorus deliver(support): chdir(/root) failed: Permission denied"error from? Why doesn't the deliver work? Any help, input, or suggestions would be greatly appreciated.

2 3

[Dovecot] Multiple SSL certs
by Noah Kantrowitz 22 Sep '07

22 Sep '07

I am trying to find a way to have the SSL cert used by Dovecot be dependent on the local IP address. So far the only ways I have found is to either have two different instances running (annoying because I would need to argue with the init scripts a lot) or use the old, undocumented server{} sections. Is the latter an acceptable way to do this, or is there something better? --Noah Kantrowitz

2 1

[Dovecot] deliver assertion failure
by Jasper Bryant-Greene 22 Sep '07

22 Sep '07

Deliver from latest 1.1 HG with sieve also from latest 1.1 HG is dying with an assertion failure when it delivers to my mailbox. Other mailboxes on the same system are unaffected, but I can read my mailbox fine through IMAP. Dovecot and sieve were compiled with -march=nocona -pipe -ggdb I've commented out my entire sieve script and the problem still occurs. file index-mail-headers.c: line 590 (index_mail_get_raw_headers): assertion failed: (ret != -1) - Last output repeated twice - Raw backtrace: /usr/libexec/dovecot/deliver(i_syslog_panic_handler+0x2b) [0x493125] -> /usr/libexec/dovecot/deliver(i_fatal+0) [0x492b17] -> /usr/libexec/dovecot/deliver [0x44f7cf] -> /usr/libexec/dovecot/deliver(index_mail_get_first_header+0x30) [0x44fb9b] -> /usr/libexec/dovecot/deliver(mail_get_first_header+0x3a) [0x47ca3d] -> /usr/libexec/dovecot/deliver(deliver_get_return_address+0x21) [0x41453b] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x14b) [0x2b3687f194a1] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x2b3687f169ba] -> /usr/libexec/dovecot/deliver(main+0x8dc) [0x415c4d] -> /lib/libc.so.6(__libc_start_main+0xe3) [0x2b3687cf6533] -> /usr/libexec/dovecot/deliver [0x4137a9] Jasper

2 1

[Dovecot] v1.1.alpha4 released / about dbox
by Timo Sirainen 22 Sep '07

22 Sep '07

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha4.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha4.tar.gz.sig Lots of fixes since alpha3. Also includes the dbox rewrite. Currently dbox works properly only in one-message-per-file mode. I'm not actually even sure how good idea it would be to use it with multiple-messages-per-file mode. But I guess it won't hurt to finish its implementation and see. :) As you can see I haven't been replying much to the mailing list lately. My school started again, which meant that I had to start sleeping again at night instead of at day :) Doing that always takes a few weeks of feeling too tired to get much of anything done. Hopefully that goes away soon. A bit more about dbox: Originally I had thought that it'd be good to have multiple messages per file. The bad thing about that is that it works badly without fcntl locks, which don't work all that great with NFS. So I changed my plans a bit so that dbox also supports one-message-per-file behavior where it doesn't need locking much. (Multiple-messages-per-file is still supported by the format, but currently the code is not fully working.) dbox files begin with a header, then they have the message data and at the end of file there's a metadata block. Metadata contains things like message flags, keywords, received date and so on. When a flag/keyword is updated, the change is normally done only to index files. This is why dovecot.index and dovecot.index.log files are important with dbox format, they contain flag changes that haven't been written anywhere else. But since there's still a chance that index files could break (although v1.1 tries harder than v1.0 to fix problems), it would be nice if the flags/keywords were written to metadata block once in a while. So if the index files are lost, flag changes wouldn't be completely lost. Metadata updates of course use disk I/O so they shouldn't be done too often. I was thinking that the metadata could be updated: - if IMAP connection has been idling for 4 hours (not changing flags) - when closing mailbox and there are changes older than 4h - immediately if there are changes older than 24h (whenever mailbox is being synced, e.g. SELECT/NOOP/STATUS) Or something like that. Those rules can of course be changed, but I'm not sure if I should bother making them configurable from dovecot.conf. There are already too many settings.

4 6

[Dovecot] Unexpected input from auth master: CUID
by Branislav Baca 22 Sep '07

22 Sep '07

Hello, I'm using postfix(2.4.5) and dovecot(1.0.5), and till now I have been using postfix deliver agent. Now I have tried to reconfigure postfix to use the dovecot LDA, but I'm getting some strange error: Sep 9 18:07:57 hostname deliver(username(a)domain.tld): BUG: Unexpected input from auth master: CUID^I5 For IMAP and POP3 my configuration works fine. I have tried it also with dovecot versions 1.0.4 and 1.0.1, but the behaviour is the same. What can be the reason of this? What should I look for to get more details what can causing this? I have this line in postfix master file: dovecot unix - n n - - pipe flags=DRhu user=mails:mails argv=/opt/dovecot-1.0.5-1/libexec/dovecot/deliver -f ${sender} -d ${recipient} In main.cf: dovecot_destination_recipient_limit = 1 virtual_transport = dovecot Relevant parts of dovecot.conf: auth default { passdb sql { args = /path/to/dovecot-sql.conf } userdb sql { args = /path/to/dovecot-sql.conf } socket listen { client { path = /var/run/dovecot/auth-master mode = 0600 user = mails group = mails } } } protocol lda { postmaster_address = postmaster(a)domain.tld auth_socket_path = /var/run/dovecot/auth-master } And relevant parts of dovecot-sql.conf: driver = mysql password_query = SELECT address as user, passwd as password FROM mail_users WHERE address='%u' user_query = SELECT CONCAT('/home/',maildir) as home, 999 as uid, 999 as gid FROM mail_users WHERE address='%u' Thanks, BB

2 2

[Dovecot] Dovecot "authentication failed" interaction with Postfix
by Julian Cowley 22 Sep '07

22 Sep '07

Hi, I'm not sure if I should be posting this question here or on the Postfix mailing list, but I'll start here. When using Dovecot SASL with Postfix, is there a way to return a login-failed reason in the SMTP AUTH dialog using "nologin", similar to the way it can be done with Dovecot IMAP and POP? Details: I have a Dovecot authentication-only daemon working with a Postfix server doing SMTP AUTH. The Dovecot configuration uses a MySQL driver to get the password information, and one of the fields in the database is "access". In my SQL query, I return a row only if "access" is non-zero. This all works -- I can shut down an account from accessing mail while retaining the user's original password. password_query = SELECT username AS user, password FROM mailbox WHERE username = '%u' AND access != 0 Now, in my Dovecot IMAP and POP server configuration, I'm using "access" in a similar way, except that instead of not returning a row when "access" is zero, I return the "nologin" extra field (along with a "reason" field). The MySQL query for this is slightly tricky, but it works: password_query = SELECT username AS user, password, NULLIF(access != 0, 1) AS nologin, 'Access not allowed for this account' AS reason FROM mailbox WHERE username = '%u' While this second query works correctly with IMAP and POP authentication, it does not work with Postfix SMTP AUTH. Assuming the password is correct, the user is authenticated even when "access" is zero. It seems that either Postfix and/or dovecot-auth (I'm not sure which) is ignoring the "nologin" field in this case. In addition, when using the first SQL query, nothing is returned as a reason following Postfix's message. For example: AUTH PLAIN (correct password) 535 5.7.0 Error: authentication failed: <-- no reason returned here I'd like to return a reason here in the (optimistic :) hope that this will be shown to the user by the email client when an account is shut off. Here's an example of it working correctly with IMAP with an account that is shut off: 001 LOGIN user (correct password) 001 NO Access not allowed for this account

2 1