- dovecot - dovecot.org

[Dovecot] dovecot-2.0.alpha2 doesn't compile on Mac OS X
by Mike Abbott 12 Nov '09

12 Nov '09

Howdy, dovecot-2.0.alpha2 doesn't compile on Mac OS X. First, trivially, there's a typo in array.h: --- a/src/lib/array.h 2009-10-08 10:04:35.000000000 -0500 +++ b/src/lib/array.h 2009-10-27 10:35:58.000000000 -0500 @@ -72,7 +72,7 @@ (elem)++) # define array_foreach_modifiable(array, elem) \ for (elem = ARRAY_TYPE_CAST_MODIFIABLE(array) \ - buffer_get_modifiable_data((array)- >arr.buffer, NULL)) + \ + buffer_get_modifiable_data((array)->arr.buffer, NULL) + \ (array)->arr.buffer->used; \ elem != CONST_PTR_OFFSET(*(array)->v, (array)->arr.buffer- >used); \ (elem)++) Second, Mac OS X can't link loadable modules against other loadable modules (http://www.finkproject.org/doc/porting/porting.en.html#shared.lib-and-mod ): --- a/src/plugins/fts-squat/Makefile.am 2009-10-18 16:28:45.000000000 -0500 +++ b/src/plugins/fts-squat/Makefile.am 2009-10-27 10:35:58.000000000 -0500 @@ -10,8 +10,9 @@ module_LTLIBRARIES = \ lib21_fts_squat_plugin.la -lib21_fts_squat_plugin_la_LIBADD = \ - ../fts/lib20_fts_plugin.la +# Apple can't link loadable modules against other loadable modules +#lib21_fts_squat_plugin_la_LIBADD = \ +# ../fts/lib20_fts_plugin.la lib21_fts_squat_plugin_la_SOURCES = \ fts-squat-plugin.c \ --- a/src/plugins/imap-acl/Makefile.am 2009-10-09 13:02:15.000000000 -0500 +++ b/src/plugins/imap-acl/Makefile.am 2009-10-27 10:35:58.000000000 -0500 @@ -14,8 +14,9 @@ imap_module_LTLIBRARIES = \ lib02_imap_acl_plugin.la -lib02_imap_acl_plugin_la_LIBADD = \ - ../acl/lib01_acl_plugin.la +# Apple can't link loadable modules against other loadable modules +#lib02_imap_acl_plugin_la_LIBADD = \ +# ../acl/lib01_acl_plugin.la lib02_imap_acl_plugin_la_SOURCES = \ imap-acl-plugin.c --- a/src/plugins/imap-quota/Makefile.am 2009-10-09 13:02:15.000000000 -0500 +++ b/src/plugins/imap-quota/Makefile.am 2009-10-27 10:35:58.000000000 -0500 @@ -13,8 +13,9 @@ imap_module_LTLIBRARIES = \ lib11_imap_quota_plugin.la -lib11_imap_quota_plugin_la_LIBADD = \ - ../quota/lib10_quota_plugin.la +# Apple can't link loadable modules against other loadable modules +#lib11_imap_quota_plugin_la_LIBADD = \ +# ../quota/lib10_quota_plugin.la lib11_imap_quota_plugin_la_SOURCES = \ imap-quota-plugin.c --- a/src/plugins/mail-log/Makefile.am 2009-10-09 13:02:15.000000000 -0500 +++ b/src/plugins/mail-log/Makefile.am 2009-10-27 10:35:58.000000000 -0500 @@ -13,8 +13,9 @@ module_LTLIBRARIES = \ lib20_mail_log_plugin.la -lib20_mail_log_plugin_la_LIBADD = \ - ../notify/lib15_notify_plugin.la +# Apple can't link loadable modules against other loadable modules +#lib20_mail_log_plugin_la_LIBADD = \ +# ../notify/lib15_notify_plugin.la lib20_mail_log_plugin_la_SOURCES = \ mail-log-plugin.c --- a/src/plugins/trash/Makefile.am 2009-10-09 13:02:15.000000000 -0500 +++ b/src/plugins/trash/Makefile.am 2009-10-27 10:35:58.000000000 -0500 @@ -10,8 +10,9 @@ module_LTLIBRARIES = \ lib11_trash_plugin.la -lib11_trash_plugin_la_LIBADD = \ - ../quota/lib10_quota_plugin.la +# Apple can't link loadable modules against other loadable modules +#lib11_trash_plugin_la_LIBADD = \ +# ../quota/lib10_quota_plugin.la lib11_trash_plugin_la_SOURCES = \ trash-plugin.c Third, for cross-compiling the value of WORDS_BIGENDIAN needs to be tested, not its presence: --- a/src/lib-index/mail-transaction-log-file.c 2009-10-15 21:26:13.000000000 -0500 +++ b/src/lib-index/mail-transaction-log-file.c 2009-10-27 10:35:58.000000000 -0500 @@ -189,7 +189,7 @@ hdr->hdr_size = sizeof(struct mail_transaction_log_header); hdr->indexid = log->index->indexid; hdr->create_stamp = ioloop_time; -#ifndef WORDS_BIGENDIAN +#if !WORDS_BIGENDIAN hdr->compat_flags |= MAIL_INDEX_COMPAT_LITTLE_ENDIAN; #endif @@ -404,7 +404,7 @@ /* we have compatibility flags */ enum mail_index_header_compat_flags compat_flags = 0; -#ifndef WORDS_BIGENDIAN +#if !WORDS_BIGENDIAN compat_flags |= MAIL_INDEX_COMPAT_LITTLE_ENDIAN; #endif if (file->hdr.compat_flags != compat_flags) {

3 6

[Dovecot] multiple connections per imap/pop3 process in 2.0
by Mike Abbott 12 Nov '09

12 Nov '09

When I set this in master.conf: service imap { service_count = 5 } I see this error when two imap users log in: Nov 11 16:54:16 server dovecot[5432]: imap-login: Login: user=<user1>, method=PLAIN, rip=10.100.0.84, lip=10.80.0.163, pid=5573 Nov 11 16:54:31 server dovecot[5432]: imap-login: Login: user=<user2>, method=PLAIN, rip=::1, lip=::1, secured, pid=5573 Nov 11 16:54:31 server dovecot[5432]: imap(pid 5573 user user2): Fatal: setgid(2002) failed with euid=2001(user1), gid=2001, egid=2001: Operation not permitted Then both users are logged out. Is there another setting I have to change to enable multiple connections per imap/pop3 process in dovecot-2.0, or does it just not work yet? I tried changing client_limit=5 but that had no effect. (I suggest that master.conf needs more documentation.) Thanks.

2 1

[Dovecot] Sluggish log process
by Pascal Volk 12 Nov '09

12 Nov '09

After the first `dovecot reload` the initial log process will not terminate immediately. The master logs: Nov 11 23:30:04 master: Warning: SIGHUP received - reloading configuration Nov 11 23:31:04 master: Warning: Processes aren't dying after reload, sending SIGTERM. Nov 11 23:32:04 master: Warning: Processes aren't dying after reload, sending SIGTERM. Nov 11 23:32:04 log: Warning: Killed with signal 15 (by pid=21639 uid=0 code=kill) With succeeding `dovecot reload`s the current log process terminates immediately Regards, Pascal -- The trapper recommends today: 5e1f1e55.0931602(a)localdomain.org

1 0

[Dovecot] patch for 2.0.alpha3 crash
by Mike Abbott 11 Nov '09

11 Nov '09

Dovecot-2.0.alpha3 crashes on startup for me on Mac OS X. It hits a segmentation fault at: 0 libdovecot.0.dylib 0x0000000100025e9f master_service_set_die_with_master + 10 1 libdovecot.0.dylib 0x0000000100025d93 master_service_settings_read + 1818 2 libdovecot.0.dylib 0x0000000100025e63 master_service_settings_read_simple + 110 3 dovecot 0x00000001000021d3 main + 846 4 dovecot 0x0000000100001650 start + 52 This appears to be because lib-master's master_service global (in the libdovecot shared library) is different from master's master_service global (in the dovecot binary). Here's a patch to fix it: --- a/src/master/main.c 2009-11-09 19:53:11.000000000 -0600 +++ b/src/master/main.c 2009-11-11 14:12:55.000000000 -0600 @@ -35,7 +35,6 @@ #define MASTER_PID_FILE_NAME "master.pid" #define SERVICE_TIME_MOVED_BACKWARDS_MAX_THROTTLE_SECS (60*3) -struct master_service *master_service; uid_t master_uid; gid_t master_gid; bool core_dumps_disabled;

1 0

[Dovecot] v2.0.tip master: service(auth): kill(pid, SIGINT) failed: Operation not permitted
by Pascal Volk 11 Nov '09

11 Nov '09

Hi Timo, I've configured the user nobody for the the service auth. doveconf -n # 2.0.alpha3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.30-1-amd64 x86_64 Debian squeeze/sid … service auth { user = nobody } … The other processes are executed by root (or logged in user): root 8758 0.0 0.0 2604 1052 ? Ss 07:21 0:00 /usr/local/sbin/dovecot root 8759 0.0 0.0 2308 808 ? S 07:21 0:00 \_ dovecot/anvil root 10869 0.0 0.0 2308 996 ? S 08:18 0:00 \_ dovecot/log nobody 10884 0.0 0.0 7292 2176 ? S 08:18 0:00 \_ dovecot/auth Logins are not a problem. But since the last logout, Dovceot logs once a minute: Nov 11 hh:mm:23 el-negro dovecot: master: service(auth): kill(10884, SIGINT) failed: Operation not permitted Regards, Pascal -- The trapper recommends today: cafefeed.0931509(a)localdomain.org

3 3

[Dovecot] selective disable_plaintext_auth
by Mariano Absatz 11 Nov '09

11 Nov '09

Hi, I've been using dovecot for some time now, always with the setting: disable_plaintext_auth = yes so that no user can accidentally expose their username/password in the open. However, I'm now trying to configure a webmail client in a nearby server which doesn't support TLS or SSL IMAP connections :-( Is there any way to allow plaintext_auth only for a small set of IP addresses (for what I see in the comment, this is automatic for local addresses, alas, the webmail client is on another host). TIA -- Mariano Absatz - "El Baby" el.baby(a)gmail.com www.clueless.com.ar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - Theory is when you know something but it doesn't work. - Practice is when something works but you don't know why. - Usually we combine theory and practice: Nothing works and we don't know why. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * TagZilla 0.066 * http://tagzilla.mozdev.org

2 3

[Dovecot] panic 1.2.7
by Cor Bosman 11 Nov '09

11 Nov '09

Im getting a panic from a specific user: Nov 11 13:53:29 userimap24.xs4all.nl dovecot: IMAP(xxxxxx): Panic: file maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): assertion failed: (recs[i]- >uid < rec->uid) Nov 11 13:53:29 userimap24.xs4all.nl dovecot: IMAP(xxxxxx): Raw backtrace: imap [0x4a6c02] -> imap [0x4a6c83] -> imap [0x4a6346] -> imap [0x444d6d] -> imap(maildir_uidlist_sync_finish+0x2d3) [0x445d83] - > imap [0x440d7e] -> imap(maildir_storage_sync_init+0x148) [0x441338] -> imap(mailbox_sync+0x30) [0x46d3b0] -> imap(imap_status_get+0x88) [0x42a9d8] -> imap(cmd_status+0x12f) [0x421e0f] -> imap [0x423b7c] -> imap [0x423c2d] -> imap(client_handle_input+0x45) [0x423da5] -> imap(client_input+0x5f) [0x42473f] -> imap(io_loop_handler_run+0xcb) [0x4aedab] -> imap(io_loop_run+0x18) [0x4ae228] -> imap(main+0x537) [0x42c707] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x7f0cef0471a6] - > imap [0x41c859] Nov 11 13:53:30 userimap24.xs4all.nl dovecot: dovecot: child 3594 (imap) killed with signal 6 (core dumps disabled) 1.2.7, Linux/Debian Lenny, amd64, NFS spool and index. Seems to be happing every few minutes, probably every time they check mail. The command they're sending: A002 STATUS "INBOX" (MESSAGES UNSEEN RECENT) Output doesnt show any result, only their login: A001 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH STARTTLS AUTH=PLAIN QUOTA] Logged in Regards, Cor

1 1

[Dovecot] System Users with IMAP
by Shane Arnold 11 Nov '09

11 Nov '09

Hi All, Sorry if this is a dumb questions, but what methods are available for retrieving mail for a system user i.e www-data. Basically my setup is just a normal Dovecot-IMAP which is working fine for shell users, but I want to be able to read mail for system users via IMAP. Is this doable? Cheers

3 2

[Dovecot] log pop3/imap logins
by Chantal Rosmuller 11 Nov '09

11 Nov '09

Hi List, I would like to log pop3/imap login events but I don't see them in the logfiles. What am I doing wrong? dovecot version: 1.1.11 dovecot -n: # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28-13-server i686 Ubuntu 9.04 nfs base_dir: /var/run/dovecot/ log_path: /var/log/mail.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 imaps pop3s ssl_cert_file: /etc/ssl/certs/dovecot-cert.pem ssl_key_file: /etc/ssl/private/dovecot.pem disable_plaintext_auth: no 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 first_valid_uid: 150 last_valid_uid: 150 mail_privileged_group: mail mail_location: mbox:/var/vmail/%2d/%d/%n mmap_disable: yes dotlock_use_excl: no mail_nfs_storage: yes mail_nfs_index: 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 auth pysieved: user: vmail passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen client: path: /var/run/pysieved/auth mode: 432 user: vmail group: mail master: path: /var/run/pysieved/auth-master mode: 432 user: vmail group: mail auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.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: 384 user: vmail

1 1

[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 09 Nov '09

09 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

[Dovecot] unsubscribe
by Jon Essen-Moller 06 Nov '09

06 Nov '09

On Thu, Nov 5, 2009 at 22:42, Lampa <lampacz(a)gmail.com> wrote: > 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 >

1 0

[Dovecot] config typo in 2.0.alpha2
by Mike Abbott 06 Nov '09

06 Nov '09

The mdbox_rotate_size and mdbox_rotate_min_size parameters are specified in bytes not kilobytes. doc/example-config/conf.d/mail.conf: # Maximum dbox file size in kilobytes until it's rotated. #mdbox_rotate_size = 2048 # Minimum dbox file size in kilobytes before it's rotated # (overrides mdbox_rotate_days) #mdbox_rotate_min_size = 16 src/lib-storage/index/dbox-multi/mdbox-settings.c: MEMBER(mdbox_rotate_size) 2048*1024, MEMBER(mdbox_rotate_min_size) 16*1024,

2 1

[Dovecot] v2.0 lmtp logging
by Pascal Volk 05 Nov '09

05 Nov '09

Hi, I am not yet completely happy with the logging behavior of the lmtp. It logs informative messages like 'lmtp: Info: Connection closed' or 'lmtp: Info: Disconnected for inactivity'. Hm, which server was connected to the lmtp? Who was disconnected for inactivity? I think it would be useful if the lmtp would also log new connections. For example: a) TCP connections: lmtp: Info: Connection: rip=10.1.2.3, lip=10.1.2.5, cid=1255555555.12345 b) Socket connections: lmtp: Info: Connection: via socket, cid=1255555777.10452 rip: There may be multiple SMTP servers in front the IMAP server(s) lip: The lmpt may listen to more than one address cid: The 'connection ID', consists of the current unix time and the pid of the lmtp process. (Or some other values in some other format) The cid should be used in the 'saved' messages. So the delivering MTA would see something like '250 2.0.0 OK: 1255555555.12345 Saved', instead of a message like '250 2.0.0 <jdoe(a)example.com> Saved'. The lmtp should also write the cid to the log. For example: 'lmtp(jdoe): Info: msgid=123, cid=1255555555.12345: saved mail to INBOX' (or discarded because of a matching sieve rule). With this connection ID it would be possible to trace the route which the e-mail has taken. Regards, Pascal -- The trapper recommends today: c01dcafe.0929623(a)localdomain.org

2 5

[Dovecot] Worker-server timeout
by Jeffrey Nikoletich 05 Nov '09

05 Nov '09

Hello Everyone, First wanted to say thanks for any help in advance. I have a clustered mail system each running on centos 5.2. I have a test box that I am running the newest version on dovecot on and I am getting some random authnication failed errors. Here is the error below: Nov 04 17:31:22 auth(default): Error: worker-server(xxx(a)xxxx.com): Aborted: Lookup timed out Nov 04 17:31:23 auth(default): Info: client out: FAIL 2 user=xxx(a)xxxx.com temp The thing is, the errors only show when the user is attempting to send a message. Here is my dovecot -n # 1.2.5: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5 x86_64 CentOS release 5.2 (Final) nfs log_path: /var/log/dovecot login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_process_size: 512 login_processes_count: 500 login_max_processes_count: 5000 login_max_connections: 1000 max_mail_processes: 5000 mail_max_userip_connections: 2000 verbose_proctitle: yes first_valid_uid: 5000 first_valid_gid: 5000 mail_location: maildir:/export/monster/mail/%d/%n:INDEX=/export/ monster/mail/%d/%n mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes maildir_stat_dirs: yes mbox_read_locks: dotlock mbox_write_locks: dotlock mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_process_size: 512 mail_plugins(default): mail_log mail_plugins(imap): mail_log mail_plugins(pop3): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 pop3_save_uidl(default): no pop3_save_uidl(imap): no pop3_save_uidl(pop3): yes pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu lda: postmaster_address: xxx(a)xxxx.net mail_plugins: sieve log_path: /var/log/dovecot-deliver.log info_log_path: /var/log/dovecot-deliver.log auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login failure_delay: 1 verbose: yes debug: yes debug_passwords: yes worker_max_count: 500 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/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: mailowner group: mailowner plugin: mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename Also here is my dovecot-sql.conf user_query = SELECT '/export/monster/mail/%d/%n' as home, 'maildir:/ export/monster/mail/%d/%n:INDEX=/export/monster/mail/%d/%n' as mail, 5000 AS uid, 5000 AS gid, concat('*:bytes=', quota) AS quota_rule FROM mailbox WHERE username ='%u' AND active ='1' password_query = SELECT MB.password FROM (mailbox as MB) LEFT JOIN domain as D ON (D.id=MB.domain_id AND D.active='1') WHERE MB.username = '%u' AND MB.active = '1' AND (D.id IS NOT NULL OR (MB.domain_id=0 and MB.name='SASL')) I have disabled user prefetch because for some reason, I get this error when it is active: Nov 04 17:05:25 auth(default): Info: prefetch (xxx(a)xxxx.net,xxx.xxx.xxx.xxx) passdb didn't return userdb entries, trying the next userdb Thanks for any help you can offer. Jeffrey Nikoletich

2 2

[Dovecot] meaning of parameter imap_idle_notify_interval??
by Ingo Thierack 05 Nov '09

05 Nov '09

Hello, is my understanding of the parameter "imap_idle_notify_interval" right, if i say, it's the time between two point where dovecot tells the client he is here, and sould have nothing directly todo with the notification of new mails arrived. I played with the values around. And the courios is, in thunderbird the folloing. set to 30 seconds. Thunderbird pop up around 25 seconds after the message is deliverd to the inbox. set to 60 seconds. Thunderbird pup up around 50 seconds after the message is deliverd to the inbox. I switch over from archiveopteryx, where no such delay was. Regards, Ingo

2 13

[Dovecot] Seeing "Corrupted transaction log file" error messages.
by Stewart Dean 05 Nov '09

05 Nov '09

In V1.1.15 that I fell back to. Again: # 1.1.15: /usr/local/etc/dovecot.conf # OS: AIX 3 0001378F4C00 listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1024 verbose_proctitle: yes first_valid_uid: 200 mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u mbox_write_locks: fcntl mbox_dirty_syncs: no auth default: passdb: driver: pam userdb: driver: passwd This is happening during peak load; the error msgs I'm seeing look like: Nov 5 15:01:47 mercury mail:err|error dovecot: IMAP(olson): Corrupted transaction log file /var/dci ndx/olson/.imap/INBOX/dovecot.index.log seq 742: file_seq=742, min_file_offset (24) < hdr_size (40) (sync_offset=24) Nov 5 15:04:13 mercury mail:err|error dovecot: IMAP(herchenr): Corrupted transaction log file /var/ dcindx/herchenr/.imap/INBOX/dovecot.index.log seq 357: file_seq=357, min_file_offset (24) < hdr_size (40) (sync_offset=24) Nov 5 15:04:13 mercury mail:info dovecot: IMAP(herchenr): Disconnected: Internal error occurred. Re fer to server log for more information. [2009-11-05 15:04:13] bytes=1314/18024 Nov 5 15:04:33 mercury mail:err|error dovecot: IMAP(olson): Transaction log file /var/dcindx/olson/ .imap/INBOX/dovecot.index.log: marked corrupted Nov 5 15:06:17 mercury mail:err|error dovecot: IMAP(olson): Corrupted transaction log file /var/dci ndx/olson/.imap/INBOX/dovecot.index.log seq 742: file_seq=742, min_file_offset (24) < hdr_size (40) (sync_offset=24) Nov 5 15:06:17 mercury mail:err|error dovecot: IMAP(olson): Transaction log got desynced for index /var/dcindx/olson/.imap/INBOX/dovecot.index Is worrisome or inconsequential? About 40 such messages in 30 minutes, mostly clumped together -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 2