- dovecot - dovecot.org

[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

[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

[Dovecot] Help needed: Index filesystem permissions problem after switch to V1.2 and back to V1.1
by Stewart Dean 05 Nov '09

05 Nov '09

After V1.2 had been up for a while, I started seeing tons of syslog error messages like this: Nov 5 09:11:52 mercury mail:err|error dovecot: IMAP(sdean): stat(/var/dcindx/sdean/.imap/DadEstate) failed: Permission denied (euid=202(sdean) egid=200(hcrc) missing +x perm: /var/dcindx) Ownernship and Permissions are: The index filesystem 2726 root@mercury:/var/dcindx ## ls -ald drwx--S--- 3946 dovecot system 192512 Nov 05 08:59 ./ A user's directory is: 2729 root@mercury:/var/dcindx ## ls -al sdean total 400 drwx--S--- 7 sdean sys 256 Sep 29 04:43 ./ drwx--S--- 3946 dovecot system 192512 Nov 05 08:59 ../ drwx--S--- 139 sdean sys 8192 Sep 29 04:43 .imap/ and for the directory with the problem: 2731 root@mercury:/var/dcindx ## ls -al sdean/.imap/DadEstate total 48 drwx--S--- 2 sdean sys 256 Sep 29 04:43 ./ drwx--S--- 139 sdean sys 8192 Sep 29 04:43 ../ -rw------- 1 sdean sys 408 Jan 14 2009 dovecot.index -rw------- 1 sdean sys 18432 May 05 2009 dovecot.index.cache -rw------- 1 sdean sys 828 Jan 14 2009 dovecot.index.log I switched back to V1.1, but the situation persists dovecot -n: # 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 -- ==== 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

3 3

[Dovecot] Quota email
by Peter Fraser 05 Nov '09

05 Nov '09

Hi All Just a quick question. Is it possible for the postmaster to get an email when a user goes over quota or is close to it? That is, aside for using the same script used to alert the user?

2 1

[Dovecot] defunct in 1.24 on FreeBSD Alphaserver
by Paweł Kaczor 05 Nov '09

05 Nov '09

Hello, I've recently upgraded Dovecot from 1.1.16 to 1.2.4 on FreeSBD 6.3- RELEASE running on old Alphaserver 1200. Some time after this upgrade all user's MUAs showed error that user password was not accepted. I've noticed many zombies of imap and pop3 processes on my server (all in defunct state). Looks like when "login_max_processes_count" was reached, Dovecot canceled all new connections. I've setup completely new configuration based on http://wiki.dovecot.org/TestInstallation and no error was produced but every time I closed telnet the imap process became defunct. So, I tried to trace what was happening with ktrace: ktrace -d -f log -p pid_of_imap_process In attached file is a part of ktrace output at the moment when I close telnet connection. What is interesting (at last for me, but I'm lamer) is an error: 1576 imap 1256902587.568406 CALL close(0xffffffffffffffff) 1576 imap 1256902587.568448 RET close -1 errno 9 Bad file descriptor AFAIK, such error could be produced by inconsistent file system so I double checked OS and I'm 100% sure it's OK. At the very end of this history I had to switch back to 1.1.16 version of Dovecot which works OK now. I'll be very thankful if somebody could point me to explanation what can cause such strange behavior. Regards, Pawel Kaczor -- "A z kwiatków, jakie pan lubi najbardziej? Sztukamięs z kwiatkiem" Paweł Kaczor <paczor(a)gmail.com>

2 1

[Dovecot] IMAP goes down from time to time
by Juan Felipe Estrada 05 Nov '09

05 Nov '09

Good Morning I´m writing back cause the IMAP going down issue has changed a little, i still have the dovecot-1.0.7-7.el5 but with 2 changes; I added to the dovecot.conf the outlook-idle workaround, and the three login_processes parameters login_process_per_connection = yes login_processes_count = 3 login_max_processes_count = 128 Since I added this parameters the IMAP process has gone down just 1 time in 2 weeks, before this, the proccess was going down about 4 times a day so I think this is suitable, the next step i´ll take is to update the Dovecot. Thanks for your help Juan Felipe Estrada dovecot-request(a)dovecot.org escribió: > Send dovecot mailing list submissions to > dovecot(a)dovecot.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > or, via email, send a message with subject or body 'help' to > dovecot-request(a)dovecot.org > > You can reach the person managing the list at > dovecot-owner(a)dovecot.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dovecot digest..." > > > Today's Topics: > > 1. Re: Panic when using QRESYNC (Michael M. Slusarz) > 2. Re: Capability info in hello message not complete? (Timo Sirainen) > 3. Re: Expire plugin per domain (Timo Sirainen) > 4. Re: Expire plugin per domain (Jose Luis Marin Perez) > 5. Re: Expire plugin per domain (Timo Sirainen) > 6. Re: Expire plugin per domain (Jose Luis Marin Perez) > 7. Re: IMAP goes down from time to time (Juan Felipe Estrada) > 8. Re: deliver+sieve: Destination address (-a) parsing changes > (Timo Sirainen) > 9. Re: deliver+sieve: Destination address (-a) parsing changes > (Frank Behrens) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 20 Oct 2009 13:48:32 -0600 > From: "Michael M. Slusarz" <slusarz(a)curecanti.org> > Subject: Re: [Dovecot] Panic when using QRESYNC > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <20091020134832.Horde.gkck4wsoc00o(a)bigworm.curecanti.org> > Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes > > Quoting Timo Sirainen <tss(a)iki.fi>: > > >> On Tue, 2009-10-20 at 15:38 -0400, Timo Sirainen wrote: >> >>> On Tue, 2009-10-20 at 13:34 -0600, Michael M. Slusarz wrote: >>> >>>> Hmmm... Rebuilt with the latest 1.2.7-pre code yesterday, and I am >>>> still seeing this (on at least 2 different mailboxes in the last day): >>>> >>>> Oct 20 13:23:32 bigworm dovecot: IMAP(slusarz): Panic: file >>>> imap-fetch.c: line 2 >>>> 27 (get_expunges_fallback): assertion failed: (mail->uid > next_uid) >>>> >>> Is it logging any other errors anymore? I can't really see how the code >>> is broken to cause this. >>> >> Oh, this actually should fix it: >> http://hg.dovecot.org/dovecot-1.2/rev/36b8d97d0f58 >> > > OK - I'm building with the latest source and will keep my eye out for > any issues. > > michael > > > > ------------------------------ > > Message: 2 > Date: Tue, 20 Oct 2009 15:49:45 -0400 > From: Timo Sirainen <tss(a)iki.fi> > Subject: Re: [Dovecot] Capability info in hello message not complete? > To: Michal Hlavinka <mhlavink(a)redhat.com> > Cc: dovecot(a)dovecot.org > Message-ID: <1256068185.4605.834.camel@timo-desktop> > Content-Type: text/plain; charset="us-ascii" > > On Tue, 2009-10-20 at 17:10 +0200, Michal Hlavinka wrote: > >> On Tuesday 13 October 2009 19:10:15 Timo Sirainen wrote: >> >>> On Tue, 2009-10-13 at 17:26 +0200, Michal Hlavinka wrote: >>> >>>> would it be possible to: >>>> a) send content of imap_capability in greeting message? It should be >>>> user's responsibility if it's set to something "weird" >>>> >>> I guess I could do this. >>> >> "could" - does it mean you are waiting for my response? If yes this option is >> fine for me, since it should fix the issue. >> > > It meant I added it to my TODO list, but hadn't yet got around to doing > it. Anyway, done now: http://hg.dovecot.org/dovecot-1.2/rev/ab32d7e2c0d6 > >

1 0

[Dovecot] dovecot + dns srv registers
by maximatt 05 Nov '09

05 Nov '09

hi... Dovecot support dns srv registers... for ldap service? thanks in advance :) -- Salu2 ;)

5 6

[Dovecot] Post login script issue with pop3 protocol
by Zhang Huangbin 05 Nov '09

05 Nov '09

Hi, all. I want to track user last login data (ip address, login date, etc) with dovecot, followed dovecot tutorial[1], and it now works with IMAP, but failed with POP3. i don't know why. My script: ---- LDAP_URI='ldap://127.0.0.1:389' LDAP_BASEDN='o=domains,dc=iredmail,dc=org' BIND_DN='cn=vmailadmin,dc=iredmail,dc=org' BIND_PW='plain_passwd' if [ X"${USER}" != X"dump-capability" ]; then ldapmodify -c -x \ -H "${LDAP_URI}" \ -D "${BIND_DN}" \ -w "${BIND_PW}" <<EOF dn: mail=${USER},ou=Users,domainName=$(echo ${USER} | awk -F'@' '{print $2}'),${LDAP_BASEDN} changetype: modify replace: lastLoginDate lastLoginDate: $(date +%Y%m%d%H%M%SZ) - replace: lastLoginIP lastLoginIP: ${IP} - replace: lastLoginProtocol lastLoginProtocol: pop3 EOF fi ---- It works with IMAP protocol, but failed with POP3 protocol. Error msg in Thunderbird: ---- The STAT command did not succeed. Error getting message number and sizes. Mail server r6.iredmail.org responsed: ying entry "mail=www(a)a.cn,ou=Users,domainName=a.cn,o=domains,dc=iredmail,dc=org" ---- [1] Post-login scripting: http://wiki.dovecot.org/PostLoginScripting -- Best Regards. Zhang Huangbin - Open Source Mail Server Solution for Red Hat(R) Enterprise Linux, CentOS, Debian, Ubuntu: http://www.iredmail.org/

4 6

Re: [Dovecot] Dovecot lock problem
by Simon Gao 04 Nov '09

04 Nov '09

> >What is the process doing? Check with "strace -p <imap process pid>"? > >How large is the user's mailbox? We just have another user reporting problem. There is no lock on /var/spool/mail/<user> file. The strace has following: # strace -p 8117 Process 8117 attached - interrupt to quit fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362101 alarm(5) = 0 time(NULL) = 1257362101 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362106 alarm(5) = 0 time(NULL) = 1257362106 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362111 alarm(5) = 0 time(NULL) = 1257362111 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362116 alarm(5) = 0 time(NULL) = 1257362116 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362121 alarm(5) = 0 time(NULL) = 1257362121 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362126 alarm(5) = 0 time(NULL) = 1257362126 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362131 alarm(5) = 0 time(NULL) = 1257362131 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362136 alarm(5) = 0 time(NULL) = 1257362136 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362141 alarm(5) = 0 time(NULL) = 1257362141 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362146 alarm(5) = 0 time(NULL) = 1257362146 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0} # strace -p 8117 Process 8117 attached - interrupt to quit fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362101 alarm(5) = 0 time(NULL) = 1257362101 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362106 alarm(5) = 0 time(NULL) = 1257362106 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362111 alarm(5) = 0 time(NULL) = 1257362111 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362116 alarm(5) = 0 time(NULL) = 1257362116 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362121 alarm(5) = 0 time(NULL) = 1257362121 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362126 alarm(5) = 0 time(NULL) = 1257362126 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362131 alarm(5) = 0 time(NULL) = 1257362131 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362136 alarm(5) = 0 time(NULL) = 1257362136 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362141 alarm(5) = 0 time(NULL) = 1257362141 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362146 alarm(5) = 0 time(NULL) = 1257362146 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362151 alarm(5) = 0 time(NULL) = 1257362151 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362156 alarm(5) = 0 time(NULL) = 1257362156 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362161 alarm(5) = 0 time(NULL) = 1257362161 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362166 alarm(5) = 0 time(NULL) = 1257362166 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362171 alarm(5) = 0 time(NULL) = 1257362171 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362176 alarm(5) = 0 time(NULL) = 1257362176 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}, 0xff9f4db4) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) time(NULL) = 1257362181 alarm(5) = 0 time(NULL) = 1257362181 fcntl64(8, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0} I did see somewhere log says "no lock file found, abort, etc". Simon

1 0

[Dovecot] quota ignore sent folder
by juan carlos 04 Nov '09

04 Nov '09

I have configured postfix and dovecot and I want to know hot to configure quota in order to ignore sent folder. Now it does work ignoring trash folder but I want to ignore sent.

2 7

[Dovecot] login BAD Error in IMAP command received by server.
by Yaron B 04 Nov '09

04 Nov '09

hi, i can open telnet on port 143 but failing on login user/pass and getting - "login BAD Error in IMAP command received by server." i assume that i didnt setup properly the authentication method and user/pass does Dovecot can use postfix user/pass ? less /var/mail/maillog Nov 3 11:21:45 localhost dovecot: imap-login: Login: user=<info>, method=PLAIN, rip=::1, lip=::1, secured Nov 3 11:21:45 localhost dovecot: IMAP(info): Connection closed bytes=41/347 [root@fedora ~]# dovecot --version 1.2.6 [root@fedora ~]# dovecot -n # 1.2.6: /etc/dovecot.conf # OS: Linux 2.6.30.9-90.fc11.i586 i686 Fedora release 11 (Leonidas) ext4 protocols: imap pop3 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 mail_privileged_group: mail mail_location: mbox:/var/mail/%u maildir_very_dirty_syncs: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): imap_client_workarounds(imap): imap_client_workarounds(pop3): delay-newmail outlook-idle netscape-eoh pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh lda: postmaster_address: postmaster(a)example.com auth default: passdb: driver: pam userdb: driver: passwd

3 3

[Dovecot] Why : dovecot_destination_recipient_limit = 1 ?
by Koenraad Lelong 03 Nov '09

03 Nov '09

Hi all, I'm trying to activate sieve. In all tutorials I have seen I need to set dovecot_destination_recipient_limit = 1 in Postfix's main.cf. Can anyone explain why ? I like to know because when I set this and the dovecot transport in Postfix, I'm having problems when aliasses are used that map to different recipients, i.e. info@... results in user1@..., user2@..., etc. The problems are an error from Postfix : Oct 30 09:25:19 lace3 postfix/pipe[19729]: 8A77E2D5B5B: to=<some.body(a)some.where.org>, relay=dovecot, delay=2390, delays=2390/0.04/0/0.01, dsn=4.3.5, status=deferred (mail system configuration error) Oct 30 09:25:19 lace3 postfix/pipe[19729]: warning: pipe flag `D' requires dovecot_destination_recipient_limit = 1 Thanks for any info. Regards, Koenraad Lelong.

5 6

[Dovecot] X.509 certificate based IMAP login
by dovecotlist＠encambio.com 03 Nov '09

03 Nov '09

Hello list, The dovecot version is 1.2.6 running on Solaris x86 11 (nv-b91). The relevant configuration lines are: passdb ldap { # LDAP database (doc/wiki/AuthDatabase.LDAP.txt.) args = /pfx/etc/dovecot/dovecot-ldap.conf } The file dovecot-ldap.conf is correct and LDAP authentication is working well. We would like to make it possible for users with a X.509 client certificate to log in without providing LDAP or any other credentials. Is there something like: passdb x509 { args = /pfx/etc/dovecot/dovecot-caroots.pem nopwd = yes } ...avaibable, or is there another solution? Thanks, Brian

2 2

[Dovecot] something similar to last login but for aliases
by Bradley Giesbrecht 03 Nov '09

03 Nov '09

I'm using dovecot deliver with postfix. Is there a place to hook in a db update when an alias is hit? I'm wanting to delete aliases that haven't been used in x time. Thank you, Brad

2 1