- dovecot - dovecot.org

[Dovecot] Multiple instances of dovecot in the same machine.
by Rodolfo Gonzalez Gonzalez 10 Nov '09

10 Nov '09

Hello all, I'm trying to run several instances of dovecot, with a different config each one, following the instructions from here: http://wiki.dovecot.org/RunningDovecot I try the command dovecot -c /etc/dovecot/installN/dovecot.conf and get: --- Error: ssl_cert_file: Can't use /etc/ssl/certs/dovecot.pem: No such file or directory Fatal: Invalid configuration in /etc/dovecot/installN --- but in my /etc/dovecot/installN/dovecot.conf file I have these lines: ssl_cert_file = /etc/dovecot/installN/ssl/certs/dovecot.pem ssl_key_file = /etc/dovecot/installN/ssl/private/dovecot.pem where both files exist and are valid. Any help is appreciated. Thanks, Rodolfo.

1 1

[Dovecot] [Fwd: Re: Bug in BODYSTRUCTURE]
by Charles Marcus 10 Nov '09

10 Nov '09

Fyi... Sam Varshavik (courier-imap developer) claims (on the courier-imap list, see attached) dovecot is incorrectly parsing messages with missing/invalid "MIME-Version:" header... I have no clue if he is correct... if so, maybe this has already been fixed?

3 3

[Dovecot] homedir auto-creat
by Frank Bonnet 10 Nov '09

10 Nov '09

Hello Is it possible to activate home directories auto creation when using real UNIX users ( NIS ) on the dovecot server ? Thank you

3 2

[Dovecot] Missing 'mailbox' variable ?
by David Goncalves 10 Nov '09

10 Nov '09

Hi, I'm using Dovecot with LDAP. My users have an home directory and a field named 'mailMessageStore'. Then the full mailbox path is 'homeDirectory/mailMessageStore' In dovecot-ldap.conf i configured as follows : user_filter = (&(objectClass=qmailUser)(cn=%u)) user_attrs = qmailUID=uid,qmailGID=gid,homeDirectory=home,mailMessageStore=mail=maildir:~/%$ Everything is working as expected but... I'm using sieve and in the 'dovecot.conf' there is no way to get a variable containing the mailbox path... As the mailMessageStore field can contain something different than the login or uid, how can i get the mailbox path in the conf ? Regards. -- David Goncalves - http://www.lestat.st

2 8

[Dovecot] Auth failure delays
by Timo Sirainen 09 Nov '09

09 Nov '09

Currently Dovecot works like this when authentication fails: - the delay is always at least auth_failure_delay seconds (default: 2s) - each failed attempt doubles the delay for that specific imap/pop3 connection (no such delays for e.g. smtp) - the delay's upper limit is 3 minutes For v2.0 I was planning on making dovecot-auth process do these checks and keeping the state in anvil process: - the delay is always at least auth_failure_delay seconds (default: 2s) - for each remote IP address the delay is doubled, regardless of how the request comes (imap, pop3, smtp, etc). - the delay's upper limit is .. hardcoded to 15 secs? i kind of hate the thought of making this configurable. - each successful authentication from the IP resets the IP's delay - the delay happens before authentication is even attempted, so even successful auth attempts will have the delay (unless of course there haven't been auth failures from that IP) If the upper limit is 15 secs, that means max. 240 auth attempts per hour per IP. The reason I was thinking 15 secs is because I have some vague memories about Thunderbird dropping connection after 15 or maybe 30 seconds of idling. If user has one successful login, it's of course possible to get around the delay doubling by just doing failed attempt -> successful attempt -> failed -> success -> etc. But probably no one is really going to try to do that, and even if they did it's still not that bad. The second successful login will still have that 2 second delay before it resets the delay. So that's still max one auth/2 seconds or max. 1800 auth attempts/hour. Any thoughts?

2 3

[Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
by Mark Sapiro 09 Nov '09

09 Nov '09

I have been running Dovecot 1.2.5 since Sept 14. Beginning at about 03:28 on Sept 21 for no apparent (to me) reason and continuing through the present, I am seeing log messages like the following and am experiencing delays logging in. Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 22 19:07:48 sbh16 dovecot: pop3-login: Login: user=<mark>, method=APOP, rip=68.183.193.239, lip=72.52.113.16, TLS Sep 22 19:07:48 sbh16 dovecot: POP3(mark): Disconnected: Logged out top=0/0, retr=0/0, del=0/218, size=2550090 Sep 22 19:08:15 sbh16 dovecot: dovecot: Created login processes successfully, unstalling Sep 22 19:08:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:08:15 sbh16 dovecot: dovecot: child 21735 (login) returned error 89 (Fatal failure) Sep 22 19:08:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Sep 22 19:08:21 sbh16 dovecot: pop3-login: Login: user=<mark>, method=APOP, rip=68.183.193.239, lip=72.52.113.16, TLS Sep 22 19:08:22 sbh16 dovecot: POP3(mark): Disconnected: Logged out top=0/0, retr=1/57566, del=0/218, size=2550090 Sep 22 19:09:15 sbh16 dovecot: dovecot: Created login processes successfully, unstalling Is this a dovecot issue, some other issue or perhaps some kind of denial of service attack? Here's my dovecot -n # 1.2.5: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/postfix/sbh16-cert.pem ssl_key_file: /etc/postfix/sbh16-key.pem login_dir: /usr/local/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 mail_privileged_group: mail mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u mbox_write_locks: fcntl dotlock 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_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 lda: postmaster_address: postmaster(a)example.com auth default: mechanisms: plain apop login worker_max_count: 5 passdb: driver: passwd-file args: /usr/local/etc/dovecot.passwd passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix [root@sbh16 ~]# -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 35

[Dovecot] deliver_log_format ignored
by Lampa 08 Nov '09

08 Nov '09

Hello, seems that LDA ignores deliver_log_format (still log with format: "msgid=%m: %$") # 1.2.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31 x86_64 Debian squeeze/sid xfs log_path: /var/log/dovecot/error.log info_log_path: /var/log/dovecot/info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: none listen: none disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:/home/mail/%d/%n/Maildir mbox_write_locks: fcntl dotlock lda: postmaster_address: postmaster(a)domain.tld mail_plugins: sieve quota deliver_log_format: from=%f msgid=%m: %$ auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=500 gid=500 home=/home/mail/%d/%n allow_all_users=yes 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: dict:user::file:/home/mail/%d/%n/Maildir/dovecot-quota quota_rule: *:storage=500M:messages=10000 quota_warning: storage=95%% /etc/dovecot/quota-warning.sh quota_warning2: storage=80%% /etc/dovecot/quota-warning.sh global_script_path: /home/mail/globalsieverc Is there some change from this http://www.dovecot.org/list/dovecot/2009-April/039013.html or http://www.dovecot.org/list/dovecot/2009-May/039269.html ? -- Lampa

4 9

[Dovecot] Question regarding performance of dovecot-1.0.15
by Hanno Wagner 07 Nov '09

07 Nov '09

Hi, I have a dovect 1.0.15 on my mailserver and as a Client I use offlineimap. Since some time now my mailsynchronisation got slow - I don't know exactly where the problem is, but I tried to track it down. Usually the UID-Searches are fast (according to the offlineimap-debugging) but as soon as it comes to big folders it takes a long time: [..] DEBUG[imap]: 37:15.22 < * 1 RECENT DEBUG[imap]: 37:15.22 matched r'\* (?P<data>\d+) (?P<type>[A- Z-]+)( (?P<data2>.*))?' => ('1', 'RECENT', None, None) DEBUG[imap]: 37:15.22 untagged_responses[RECENT] 1 += ["1"] DEBUG[imap]: 37:15.22 < HAMH49 OK Append completed. DEBUG[imap]: 37:15.22 matched r'(?P<tag>HAMH\d+) (?P<type>[A- Z]+) (?P<data>.*)' => ('HAMH49', 'OK', 'Append completed.') DEBUG[imap]: 37:15.22 > HAMH50 CHECK DEBUG[imap]: 37:15.49 < HAMH50 OK Check completed. DEBUG[imap]: 37:15.49 matched r'(?P<tag>HAMH\d+) (?P<type>[A- Z]+) (?P<data>.*)' => ('HAMH50', 'OK', 'Check completed.') DEBUG[imap]: savemessage: first attempt to get new UID DEBUG[imap]: savemessage_searchforheader called for X-OfflineIMAP- x601334136 -52656d6f7465496d61704976616e6f7661 -446174656e73636875747a2e4343432e646562617465: 1257496634-0840104922121-v5.99.4 DEBUG[imap]: 37:15.49 > HAMH51 UID SEARCH HEADER X-OfflineIMAP- x601334136 -52656d6f7465496d61704976616e6f7661 -446174656e73636875747a2e4343432e646562617465 "1257496634-0840104922121-v5.99.4" DEBUG[imap]: 42:46.80 < * SEARCH 24578 DEBUG[imap]: 42:46.80 matched r'\* (?P<type>[A-Z-]+)( (? P<data>.*))?' => ('SEARCH', ' 24578', '24578') DEBUG[imap]: 42:46.80 untagged_responses[SEARCH] 0 += ["24578"] DEBUG[imap]: 42:46.80 < HAMH51 OK Search completed. DEBUG[imap]: 42:46.80 matched r'(?P<tag>HAMH\d+) (?P<type>[A- Z]+) (?P<data>.*)' => ('HAMH51', 'OK', 'Search completed.') DEBUG[imap]: 42:46.80 untagged_responses[SEARCH] => ['24578'] DEBUG[imap]: savemessage_searchforheader got initial matchinguids: '24578' DEBUG[imap]: savemessage_searchforheader: matchinguids now ['24578'] DEBUG[imap]: savemessage: returning 24578 Copy message 9480 Maildir[.Datenschutz.CCC.debate] -> IMAP[Datenschutz.CCC.debate], LocalStatus[.Datenschutz.CCC.debate] DEBUG[imap]: savemessage: called DEBUG[imap]: savemessage: using date "15-Mar-2009 18:04:01 +0100" DEBUG[imap]: savemessage: initial content is: 'Return-path: [..] (here is the mail) DEBUG[imap]: savemessage: new headers are: X-OfflineIMAP- x1331546026 -52656d6f7465496d61704976616e6f7661 -446174656e73636875747a2e4343432e646562617465: 1257496966-0335241954714-v5.99.4 DEBUG[imap]: savemessage_addheader: called to add X-OfflineIMAP- x1331546026 -52656d6f7465496d61704976616e6f7661 -446174656e73636875747a2e4343432e646562617465: 1257496966-0335241954714-v5.99.4 DEBUG[imap]: savemessage_addheader: insertionpoint = 63 DEBUG[imap]: savemessage_addheader: leader = 'Return-path: <debate-return-45711-wagner=fitug.de(a)lists.ccc.de >' DEBUG[imap]: savemessage_addheader: newline = '\r\nX-OfflineIMAP- x1331546026 -52656d6f7465496d61704976616e6f7661 -446174656e73636875747a2e4343432e646562617465: 1257496966-0335241954714-v5.99.4' DEBUG[imap]: savemessage_addheader: trailer = '\r\nEnvelope-to:[..] the mail.. As you can see at the timestamp, it took roundabout 5 minutes to find the next mail. Is this normal? In this mailbox there are right now around 20.000 mails, which shouldn't be too hard then... or am I missing something there? Is there a way to see why dovecot needs so long to find the next mail to synchronise? my configuration: # 1.0.15: /etc/dovecot/dovecot.conf log_path: /home/rince/dovecot-debug.log info_log_path: /home/rince/dovecot-debug.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s imap listen(default): 10.11.12.1 listen(imap): 10.11.12.1 listen(pop3): * ssl_cert_file: /etc/ssl/certs/ivanova.crt ssl_key_file: /etc/ssl/private/ivanova.key 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_user: dovecot-login mail_privileged_group: mail 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_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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: user: dovecot-auth passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd userdb: driver: passwd-file args: /etc/dovecot/passwd Unfortunately, except the starting-up message, there comes nothing in the debug-logfiles. Ciao, Hanno -- Let me get this straight: You think that your client, one of the wealthiest, most powerful men in the world, is secretly a vigilante who spends his nights beating criminals to a pulp with his bare hands. And your plan is to blackmail this person? Good luck. (Lucius Fox, Morgan Freeman, The Dark Knight)

2 6

[Dovecot] scenario with one lda and 4 imapds/pop3ds
by Lampa 07 Nov '09

07 Nov '09

Hello, i want to create following scenario: one dovecot using ONLY LDA (using sql ) # 1.2.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31 x86_64 Debian squeeze/sid xfs log_path: /var/log/dovecot/error.log info_log_path: /var/log/dovecot/info.log log_timestamp: %FT%T%z protocols: none listen: none disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:/home/mail/%d/%n/Maildir mbox_write_locks: fcntl dotlock lda: postmaster_address: postmaster(a)domain.com mail_plugins: quota sieve deliver_log_format: from=%f msgid=%m: %$ auth_socket_path: /var/run/dovecot/auth-master info_log_path: /var/log/dovecot/info2.log auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=500 gid=500 home=/home/mail/%d/%n allow_all_users=yes 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: dict:user::file:/home/mail/%d/%n/Maildir/dovecot-quota quota_rule: *:storage=500M:messages=10000 quota_warning: storage=95%% /etc/dovecot/quota-warning.sh quota_warning2: storage=80%% /etc/dovecot/quota-warning.sh global_script_path: /home/mail/globalsieverc other 4 dovecots for serving imaps pop3s (each will have own ssl certificate and using own ip address) my idea is using only one auth mechanism provided by dovecot LDA (above) - eg using one SQL connection question is, how to force other 4 dovecots use auth from LDA dovecot ? is possible to do this ? is enough to use: auth external { socket connect { master { path = /var/run/dovecot/auth-master } } } Thank you for advices and help. -- Lampa

2 1

Re: [Dovecot] Help needed: Index filesystem permissions problem after switch to V1.2 and back to V1.1
by Steffen Kaiser 06 Nov '09

06 Nov '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 5 Nov 2009, Stewart Dean wrote: > So you say that the /var/dcindx permissions should be 1777? Not 2777? What No, not 2777, your "/tmp" is not 2777 either, I guess. > userid/group should own the directory? I use root:root. In fact, because multiple uids (and gids) have to create a directory there, you have to use a tmp-like directory. "1xxx" means the sticky-bit, so users may not remove an entry owned by another user. Because root is owner of /var/dvindex, you have just those two users able to remove: root and the owning user of the subdir. The user-specific subdirectories should be 0700 or something like that, so the security is OK. DoS is possible by filling the partition completely, but this ability is available in other scenarios as well. > > #2: Under both V1.1 and V1.2, the vast majority of users *can* and have > created their index directories, but others can't. How can this be? This > shows up as errmsgs like > Nov 5 09:36:06 mercury mail:err|error dovecot: IMAP(ahinds): > mkdir(/var/dcindx/ahinds/.imap/Apple M > ail To Do) failed: Permission denied All I can think of is that: a) the existing subdirs had be created earlier e.g. by root or migration, b) those few users use a different group. IMHO, as soon as you have system users the /var/dcindex must be 1777, the few exceptions, when all users share a single group, or you can pre-create the directories are the special cases. BTW: _If_ you use system users and your account name <-> uid relationship can change, you should use an template different than /var/dcindex/%u, e.g. /var/dcindex/%i, because if a new user with an name already used in past, but with another uid logs on the server, the uid cannot access the old /var/dcindex/ahinds tree. The leftover files should not make much worries, except the subscription perhaps. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSvQCuXWSIuGy1ktrAQIXFQgAwtHVLIpt9Kr+QCulz0NunTdAbtamiMrb 9i2ZVG9Sb5swAYmeRKOHYAWnVIcGA8gPnKDadVuG/+6+ZjDhcapk4MTlb8NzaKNV 6Rwr9I+JYdQI/HnLzHHj+WJxn6bgr5fe21LN1WXgwtIccAbOPSj7mzUih+p0V/RX ZXpzLHgu6+BrdWdFgmnDUA1nidXCtV8/V9b1b6P4j591yeOnnXs3sJlhoucD3Pyt Pt/8toXeJJMmxdbTSJME9ov5ZxfQHg8lBxVgB04RvhSP3CN4c3ijLI93heRUub0k zeG79mS9xfHbXlxDHM4qUsxkOUgZyk7RU6q27arB5HFT3v/J/uVyFQ== =YhYT -----END PGP SIGNATURE-----

1 0