- dovecot - dovecot.org

[Dovecot] singe system user for all virtual users
by Wojtek Bogusz 25 May '08

25 May '08

hi, i would like to have all the emails stored under one system user and system group. i keep user passwords in LDAP. for userdb i wanted to use static. but i keep getting this error: Error: Error in configuration file /usr/local/etc/dovecot.conf line 909: Unknown setting: userdb Fatal: Invalid configuration in /usr/local/etc/dovecot.conf i am using version 1.0.13 my /usr/local/etc/dovecot.conf without comments is: base_dir = /var/run/dovecot/ protocols = imaps imap listen = * disable_plaintext_auth = no shutdown_clients = yes log_timestamp = "%Y-%m-%d %H:%M:%S " ssl_disable = no ssl_cert_file = /etc/apache2/ssl/server.pem ssl_key_file = /etc/apache2/ssl/server.key mail_location = maildir:/home/MAIL/%n mail_privileged_group = mail protocol imap { login_greeting_capability = yes imap_client_workarounds = tb-extra-mailbox-sep } protocol lda { postmaster_address = postmaster(a)frontlinedefenders.org hostname = base auth_socket_path = /var/run/dovecot/auth-master } auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb static { args = uid=mail gid=mail home=/home/MAIL/%n } auth_userdb = user = mail socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = mail # User running Dovecot LDA group = mail # Or alternatively mode 0660 + LDA user in this group } } } dict { } plugin { } what do i do wrong? best regards, Wojtek

3 4

[Dovecot] Error while set mailQuota=0 with mbox and LDAP backend
by Zhang Huangbin 25 May '08

25 May '08

Hi, all. I have OpenLDAP(+qmail.schema), Dovecot, Postfix installed on RHEL 5.1 (x86_64), and they works fine with mbox format. The problem is if i set 'mailQuota=0' in LDAP, postfix can't send mail to recipient user. But it works fine with 'mailQuota != 0', such as '10240'(10M). What's wrong with my mail server setting? How can i solved this issue? Thanks very much. Bellow is the mail log from /var/log/maillog: ---------------- /var/log/maillog ------------- # mail -s "h" postmaster(a)a.cn < /etc/hosts && tail -0f /var/log/maillog May 23 20:29:35 rh6 postfix/pickup[1608]: 8E8B884949: uid=0 from=<root> May 23 20:29:35 rh6 postfix/cleanup[1896]: 8E8B884949: message-id=<20080524002935.8E8B884949(a)rh6.bibby.org> May 23 20:29:35 rh6 postfix/qmgr[1616]: 8E8B884949: from=<root(a)rh6.bibby.org>, size=467, nrcpt=1 (queue active) May 24 00:29:35 rh6 postfix/smtpd[1901]: connect from localhost.localdomain[127.0.0.1] May 24 00:29:35 rh6 postfix/smtpd[1901]: CFE838494A: client=localhost.localdomain[127.0.0.1] May 23 20:29:35 rh6 postfix/cleanup[1896]: CFE838494A: message-id=<20080524002935.8E8B884949(a)rh6.bibby.org> May 23 20:29:35 rh6 postfix/qmgr[1616]: CFE838494A: from=<root(a)rh6.bibby.org>, size=1076, nrcpt=1 (queue active) May 24 00:29:35 rh6 postfix/smtpd[1901]: disconnect from localhost.localdomain[127.0.0.1] May 24 00:29:35 rh6 postfix/smtp[1898]: 8E8B884949: to=<postmaster(a)a.cn>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.35, delays=0.07/0/0.01/0.27, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as CFE838494A) May 23 20:29:35 rh6 postfix/qmgr[1616]: 8E8B884949: removed May 23 20:29:35 rh6 postfix/pickup[1608]: E47BA84949: uid=2000 from=<> May 23 20:29:35 rh6 postfix/cleanup[1896]: E47BA84949: message-id=<dovecot-1211588975-866451-0(a)rh6.bibby.org> May 23 20:29:35 rh6 postfix/qmgr[1616]: E47BA84949: from=<>, size=2085, nrcpt=1 (queue active) May 23 20:29:35 rh6 postfix/pipe[1902]: CFE838494A: to=<postmaster(a)a.cn>, relay=dovecot, delay=0.12, delays=0.01/0/0/0.11, dsn=2.0.0, status=sent (delivered via dovecot service) May 23 20:29:35 rh6 postfix/qmgr[1616]: CFE838494A: removed May 24 00:29:36 rh6 postfix/smtpd[1901]: connect from localhost.localdomain[127.0.0.1] May 24 00:29:36 rh6 postfix/smtpd[1901]: 390468494F: client=localhost.localdomain[127.0.0.1] May 23 20:29:36 rh6 postfix/cleanup[1896]: 390468494F: message-id=<dovecot-1211588975-866451-0(a)rh6.bibby.org> May 23 20:29:36 rh6 postfix/qmgr[1616]: 390468494F: from=<>, size=2522, nrcpt=1 (queue active) May 24 00:29:36 rh6 postfix/smtpd[1901]: disconnect from localhost.localdomain[127.0.0.1] May 24 00:29:36 rh6 postfix/smtp[1898]: E47BA84949: to=<root(a)rh6.bibby.org>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.34, delays=0.02/0/0.01/0.31, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 390468494F) May 23 20:29:36 rh6 postfix/qmgr[1616]: E47BA84949: removed May 23 20:29:36 rh6 postfix/local[1951]: 390468494F: to=<root(a)rh6.bibby.org>, relay=local, delay=0.04, delays=0.01/0/0/0.03, dsn=4.3.0, status=deferred (temporary failure. Command output: Can't open log file /var/log/sieve.log: Permission denied ) ------------ End maillog --------------- Bellow is my dovecot setting(dovecot -n): ----------- dovecot -n -------------- # 1.0.13: /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/pki/dovecot/certs/dovecotCert.pem ssl_key_file: /etc/pki/dovecot/private/dovecotKey.pem 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_location: mbox:/%Lh/%Ld/%Ln:INBOX=/%Lh/%Ld/%Ln/inbox:INDEX=MEMORY mbox_write_locks: dotlock fcntl mbox_min_index_size: 10240 mbox_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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login user: vmail passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail ----------- End dovecot -n -------------- Bellow is /etc/dovecot-ldap.conf: -------------- /etc/dovecot-ldap.conf --------------- hosts = 127.0.0.1:389 ldap_version = 3 auth_bind = yes dn = cn=vmail,dc=osspinc,dc=com dnpass = passwd base = o=%d,o=domains,dc=osspinc,dc=com scope = subtree deref = never user_filter = (&(mail=%u)(objectClass=qmailUser)(accountStatus=active)) pass_filter = (mail=%u) pass_attrs = userPassword=password user_global_uid = 2000 user_global_gid = 2000 default_pass_scheme = CRYPT user_attrs = homeDirectory=home,mailMessageStore=dirsize:mail,mailQuota=quota=dirsize:storage -------------- End /etc/dovecot-ldap.conf --------------- transport entry in Postfix master.cf: ----------- /etc/postfix/master.cf ---------------- dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -d ${recipient} -f ${sender} ----------- End /etc/postfix/master.cf ---------------- -- Best Regards. Zhang Huangbin - Mail Server Solution for Red Hat(R) Enterprise Linux & CentOS 5.x: http://rhms.googlecode.com/

3 6

[Dovecot] Auto-subscribe to folders
by Juan Asensio Sánchez 25 May '08

25 May '08

Hi I will use autocreate plugin in a new installation, and client has asked me if the users can be auto-subscribed to certain folders. Example: the users will have an autocreated Junk folder (for SPAM) and we want the users not to be un-subscribed for this folder; so if the user wants to be unsubscribed (from outlook, webmail, etc), there are two options: a) the action is rejected or denied; b) the next time he/she logins, then the folder is autosubscribed again. Could this be done? How? Thanks in advance.

2 1

[Dovecot] Domain variable in checkpassword
by sawyer x 25 May '08

25 May '08

Hello everyone I'm using the checkpassword method but I don't get the domain a user inputs. I can't cross check per virtual domains if I'm not getting one, which means it renders all my efforts useless. I've tried sending %d as a variable to my checkpassword script, but I'm just getting %d instead. This is a dump of my information: %ENV = { 'USERNAME_TRANSLATION' => '', 'SYSLOG_FACILITY' => '16', 'CACHE_SIZE' => '0', 'RESTRICT_GID_LAST' => '', 'TCPREMOTEIP' => '213.31.43.3', 'RESTRICT_GID_FIRST' => '', 'AUTH_NAME' => 'default', 'CACHE_TTL' => '3600', 'SERVICE' => 'IMAP', 'USERDB_1_DRIVER' => 'prefetch', 'USERNAME_CHARS' => 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@', 'DOVECOT_MASTER' => '1', 'RESTRICT_SETGID' => '', 'AUTH_WORKER_MAX_COUNT' => '30', 'AUTH_WORKER_PATH' => '/var/run/dovecot/auth-worker.25291', 'PASSDB_2_ARGS' => '/etc/exim/checkp %d', 'USERNAME_FORMAT' => '', 'LOCAL_IP' => '128.177.27.100', 'PASSDB_2_DRIVER' => 'checkpassword', 'PASSDB_1_DRIVER' => 'pam', 'REALMS' => '', 'PROTO' => 'TCP', 'ANONYMOUS_USERNAME' => 'anonymous', 'RESTRICT_SETEXTRAGROUPS' => '', 'TCPLOCALIP' => '128.177.27.100', 'LOG_TO_MASTER' => '1', 'MASTER_USER_SEPARATOR' => '', 'RESTRICT_SETUID' => '', 'REMOTE_IP' => '213.31.43.3', 'RESTRICT_USER' => '', 'DOVECOT_VERSION' => '1.0.rc15', 'MECHANISMS' => 'plain', 'RESTRICT_CHROOT' => '', 'DEFAULT_REALM' => '' }; ARGS: @ARGV = [ '%d', '/usr/libexec/dovecot/checkpassword-reply' ]; Thanks, Sawyer.

2 1

[Dovecot] imap-login processes
by Bryan Polk 25 May '08

25 May '08

First, thanks for this great product. We migrated from Courier last week with only small bumps along the way. We have a few hundred active users with a mix of pop3 and imap clients. The server is running on sparc Solaris 9. We're seeing a problem now with the number of "imap-login" processes rising slowly to it's limit and then (understandably) not letting any more logins happen. Legitimate users seem to have no problem logging in until the limit is hit. Another odd thing is that this is not a problem for pop3-login processes, just imap... I've tried changing some obvious things including the passdb from pam to passwd and back again, but here's the current dovecot -n output: # 1.0.13: /opt/dovecot/etc/dovecot.conf protocols: imap imaps pop3 pop3s ssl_cert_file: /opt/dovecot/etc/ssl/certs/dovecot.pem ssl_key_file: /opt/dovecot/etc/ssl/certs/key.pem disable_plaintext_auth: no login_dir: /opt/dovecot/var/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login login_processes_count: 12 login_max_processes_count: 512 verbose_proctitle: yes mail_location: maildir:~/Maildir mmap_disable: yes mail_executable(default): /opt/dovecot/libexec/dovecot/imap mail_executable(imap): /opt/dovecot/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private prefix: INBOX. inbox: yes auth default: verbose: yes passdb: driver: pam userdb: driver: passwd Any ideas or advice? Thanks, Bryan Polk Unix Systems Administrator Communication and Multimedia Services FAMU-FSU College of Engineering bpolk(a)eng.fsu.edu

5 14

[Dovecot] Problems with apple'mail client
by Osvaldo Alvarez Pozo 25 May '08

25 May '08

hi all I use dovecot for smtp authentication this works ok for thunderbird and for outlook express but not for apple'mail client. my config is as follow postfx main.cf . . #authentication smtpd_sasl_auth_enable = yes #smtpd_sasl_local_domain = $myhostname smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth # TLS parameters . . Dovecot dovecot.conf ssl_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key_file = /etc/ssl/private/ssl-cert-snakeoil.key mail_location = maildir:/var/vmail/%d/%u/Maildir mail_extra_groups = mail first_valid_uid = 5000 last_valid_uid = 5000 maildir_copy_with_hardlinks = yes disable_plaintext_auth = no mail_debug = no dotlock_use_excl=yes protocols = imap pop3 protocol imap { mail_plugins = quota imap_quota imap_client_workarounds = outlook-idle delay-newmail } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { postmaster_address = support(a)oc3.fr mail_plugins = quota log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log } auth default { mechanisms = plain login passdb sql { args = /usr/dovecot/etc/sql.conf } # userdb prefetch { # } userdb sql { args = /usr/dovecot/etc/sql.conf } user = nobody socket listen { master { path = /usr/dovecot/var/run/dovecot/auth-master mode = 0660 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = mail } } } dict { } plugin { } Thanks

3 3

[Dovecot] Bug [1.1rc5]: Crash during "CPU architecture changed" index upgrade
by Cabel Sasser 25 May '08

25 May '08

Hello List, We just migrated from a PPC Xserve to an Intel Xserve. I used "rsync" to bring everyone's home directories over, and in the back of my mind wondered about how it would handle the binary index files... only one way to find out! :) Once I tried to login to IMAP, I got the following results: May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Rebuilding index file /Users/cabel/mail/.imap/INBOX/dovecot.index: CPU architecture changed May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): fscking index file / Users/cabel/mail/.imap/INBOX/dovecot.index May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Fixed index file / Users/cabel/mail/.imap/INBOX/dovecot.index: log_file_seq 1 -> 637534208 May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): /Users/cabel/ mail/.imap/INBOX/dovecot.index: log_file_head_offset too small May 6 19:46:48 posh dovecot[1169]: Panic: IMAP(cabel): file mail- transaction-log-view.c: line 215 (mail_transaction_log_view_set): assertion failed: (min_file_offset >= view->tail->hdr.hdr_size) May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Raw backtrace: 2 imap 0x000839d8 i_set_failure_file + 392 -> 3 imap 0x00083283 i_panic + 51 -> 4 imap 0x0006f512 mail_transaction_log_view_set + 1170 -> 5 imap 0x000669c9 mail_index_sync_map + 297 -> 6 imap 0x0005d35c mail_index_map + 1580 -> 7 imap 0x00061f5e mail_index_transaction_open_updated_view + 958 -> 8 imap 0x00062ba6 mail_index_sync_begin_to + 102 -> 9 imap 0x0006352d mail_index_sync_begin + 77 -> 10 imap 0x00030b50 mbox_sync + 1120 -> 11 imap 0x0003203d mbox_storage_sync_init + 77 -> 12 imap 0x0004f21f mailbox_sync + 31 -> 13 imap 0x00006167 cmd_select_full + 231 - > 14 imap 0x0000 May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): 6329 cmd_select + 25 - > 15 imap 0x00008409 client_handle_unfinished_cmd + 201 -> 16 imap 0x000084ab client_handle_unfinished_cmd + 363 -> 17 imap 0x00008705 client_handle_unfinished_cmd + 965 -> 18 imap 0x00008962 client_input + 114 -> 19 imap 0x0008c2e9 io_loop_handler_run + 313 -> 20 imap 0x0008b606 io_loop_run + 70 -> 21 imap 0x000119f7 main + 1207 -> 22 imap 0x000016c6 start + 54 May 6 19:46:49 posh ReportCrash[1222]: Formulating crash report for process imap[1202] May 6 19:46:49 posh dovecot[1169]: child 1202 (imap) killed with signal 6 May 6 19:46:49 posh ReportCrash[1222]: Saved crashreport to /Library/ Logs/CrashReporter/imap_2008-05-06-194648_posh.crash using uid: 0 gid: 0, euid: 0 egid: 0 Naturally, deleting everyone's ".imap" folders fixed the problem. I'll attach the crash report to this e-mail. Hope this is useful to someone on this list! Best, Cabel Panic Process: imap [1202] Path: /usr/local/libexec/dovecot/imap Identifier: imap Version: ??? (???) Code Type: X86 (Native) Parent Process: dovecot [1169] Date/Time: 2008-05-06 19:46:48.366 -0700 OS Version: Mac OS X Server 10.5.2 (9C31) Report Version: 6 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Crashed Thread: 0 Thread 0 Crashed: 0 libSystem.B.dylib 0x96d540ea __kill + 10 1 libSystem.B.dylib 0x96dcb3f2 raise + 26 2 libSystem.B.dylib 0x96dda9af abort + 73 3 imap 0x00083a0a i_internal_fatal_handler + 106 4 imap 0x00083283 i_panic + 51 5 imap 0x0006f512 mail_transaction_log_view_set + 1170 (mail-transaction-log-view.c:143) 6 imap 0x000669c9 mail_index_sync_map + 297 (mail-index-sync-update.c:753) 7 imap 0x0005d35c mail_index_map + 1580 (mail-index-map.c:926) 8 imap 0x00061f5e mail_index_sync_begin_init + 78 (mail-index-sync.c:355) 9 imap 0x00062ba6 mail_index_sync_begin_to + 102 (mail-index-sync.c:418) 10 imap 0x0006352d mail_index_sync_begin + 77 (mail-index-sync.c:323) 11 imap 0x00030b50 mbox_sync + 1120 (mbox- sync.c:1684) 12 imap 0x0003203d mbox_storage_sync_init + 77 (mbox-sync.c:1880) 13 imap 0x0004f21f mailbox_sync + 31 (mail- storage.c:539) 14 imap 0x00006167 cmd_select_full + 231 (cmd-select.c:39) 15 imap 0x00006329 cmd_select + 25 (cmd- select.c:88) 16 imap 0x00008409 client_command_input + 41 (client.c:553) 17 imap 0x000084ab client_command_input + 203 (client.c:604) 18 imap 0x00008705 client_handle_input + 277 (client.c:643) 19 imap 0x00008962 client_input + 114 (client.c:698) 20 imap 0x0008c2e9 io_loop_handler_run + 313 (ioloop-kqueue.c:150) 21 imap 0x0008b606 io_loop_run + 70 (ioloop.c:300) 22 imap 0x000119f7 main + 1207 (main.c:254) 23 imap 0x000016c6 start + 54 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0x96dda96f ecx: 0xbfffdcdc edx: 0x96d540ea edi: 0x00201720 esi: 0x00000004 ebp: 0xbfffdcf8 esp: 0xbfffdcdc ss: 0x0000001f efl: 0x00000282 eip: 0x96d540ea cs: 0x00000007 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x00107000 Binary Images: 0x1000 - 0xa9fe0 +imap ??? (???) <10c13baf127aaaae5e5c68a2929781d2> /usr/local/libexec/dovecot/imap 0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <7af47d3b00b2268947563c7fa8c59a07> /usr/lib/dyld 0x9024c000 - 0x90340ff4 libiconv.2.dylib ??? (???) <c508c60fafca17824c0017b2e4369802> /usr/lib/libiconv.2.dylib 0x935d3000 - 0x935d7fff libmathCommon.A.dylib ??? (???) /usr/lib/ system/libmathCommon.A.dylib 0x93768000 - 0x9376ffe9 libgcc_s.1.dylib ??? (???) <a9ab135a5f81f6e345527df87f51bfc9> /usr/lib/libgcc_s.1.dylib 0x96ce5000 - 0x96e44ff3 libSystem.B.dylib ??? (???) <4899376234e55593b22fc370935f8cdf> /usr/lib/libSystem.B.dylib 0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/ libSystem.B.dylib

2 1

[Dovecot] Maildir locking by LDA of dovecot
by Mike Grozak 25 May '08

25 May '08

Hi all! First of all, I want ti thank the whole Dovecot community (developers for developing and fast responses, users for populating and responses too). Dovecot is a really good and fast IMAP server - it serves near 3000 in our installation. Now I have a problem and request community's help its resolving;) Dovecot version: 1.0.13, compiled with vpopmail support. I have an account spam(a)domain.com (:-), in which we put all our spam (we gather statistic later). There can be 10 and more delivery attempts in a second to maildir of this account during the spam attacks on our server. The queue of our server can grow up to 20k messages, and all of these messages are sent to spam(a)domain.com. I found a lot of such strings in dovecot.log file during such DoS attack: dovecot.log:deliver(spam@domain.com): May 16 04:18:48 Info: msgid=<01c8b6da$a8bacf80$b7af2abe@sale>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:18:59 Info: msgid=<6611811842.20080516012444(a)poiusadfhnvxzmdiasdasgkhlsdkfg.com>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:06 Info: msgid=<01c8b6a8$7b552e00$a0a4034c@sale>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:14 Info: msgid=<360825920.32055246029506(a)mirgames.ru>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:50 Info: msgid=<01c8b6b1$0df9cb00$cc36dfc9@tek2>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:21:00 Info: msgid=<087901c7ca2d$ef272640$1e01a8c0(a)telefonia.InterCable.net>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:21:01 Info: msgid=<000701c8b6d2$01ff999f$c491aca7@snoueiij>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:32 Info: msgid=<000801c8b69b$060c0230$3cd8a4b7@cpbvlrx>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:45 Info: msgid=<000801c8b6a5$04ba6412$9910848d@aldldr>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:45 Info: msgid=<031401c772e2$adc5be40$1e01a8c0(a)mtu-net.ru>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:23:08 Info: msgid=<01c8b6db$0222fe80$b7af2abe@info>: save failed to INBOX: Timeout while waiting for lock What can I do for resolving this locks? The queue of my server becomes really big! May be, while looking into uidlist file, can dovecot LDA lock it? And other deliver processes can't open it and wait for him? $ dovecot --version 1.0.13 # dovecot -n # 1.0.13: /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap pop3 ssl_disable: yes 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_greeting: Server is ready. login_process_per_connection: no login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_max_connections: 1024 first_valid_uid: 39 last_valid_uid: 39 first_valid_gid: 39 last_valid_gid: 39 fsync_disable: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain login cram-md5 default_realm: tversu.ru cache_size: 10240 user: vpopmail username_format: %Lu passdb: driver: vpopmail args: cache_key=%u dovecot userdb: driver: vpopmail socket: type: listen client: path: /var/spool/postfix/private/auth mode: 438 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 438 plugin: quota: maildir:ignore=Trash --------------------------- WBR, Mike Grozak, TvSU IC

3 4

[Dovecot] Multiple private namespace question
by Troy Engel 24 May '08

24 May '08

(apologies if this has been covered, can't find it on the Wiki/FAQ, etc.) We have a stellar, fantastic, hard working Dovecot 1.0.5 (yes, I need to upgrade) installation running in Courier-IMAP compatibility mode: mail_location = maildir:~/Maildir:INDEX=/var/spool/dovecot/indexes/%1u/%u namespace private { separator = . prefix = INBOX. inbox = yes } A user purchased a Windows Mobile 6 device which is ignoring the namespace (it's the device's bug for sure, other people report it on forums around the 'net) and there's no way on this device to manually set the Prefix; so, his Sent mails are never making it back to the server when replying from the device because of the missing INBOX. issue. Can I add a second hidden namespace with no prefix: namespace private { separator = . prefix = hidden = yes } ...to fix his problem, but without adversely affecting anyone else? The issue that has given me pause is this comment in the config file: "Default namespace is simply done by having a namespace with empty prefix." ..but then there's also: "If namespace is hidden, it's not advertised to clients via NAMESPACE extension or shown in LIST replies." I'm not sure what exactly will happen by adding a hidden namespace with no prefix after an advertised namespace with a prefix; this is a live server, so mucking up the works with a bad config is not an option. :) Anyone have a clue if this is valid/good/correct and Dovecot will play nicely? Many thanks, -te -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com

3 8

[Dovecot] Problem compiling antispam plugin with Dovecot 1.1
by Juan Asensio Sánchez 24 May '08

24 May '08

Hi I am trying to compile antispam plugin with Dovecot 1.1, but i get an error when running make install: pdc-server:~/tmp/dovecot-antispam# make cc -c -DHAVE_CONFIG_H -Wall -I/root/tmp/dovecot-1.1.rc5/ -I/root/tmp/dovecot-1.1.rc5/src/ -I/root/tmp/dovecot-1.1.rc5/src/lib/ -I/root/tmp/dovecot-1.1.rc5/src/lib-storage/ -I/root/tmp/dovecot-1.1.rc5/src/lib-mail/ -I/root/tmp/dovecot-1.1.rc5/src/lib-imap/ -I/root/tmp/dovecot-1.1.rc5/src/lib-dict/ -I/root/tmp/dovecot-1.1.rc5/src/lib-index/ -I/root/tmp/dovecot-1.1.rc5/src/imap/ -DCONFIG_DEBUG -DDEBUG_SYSLOG -DCONFIG_DEBUG_VERBOSE -DCONFIG_DOVECOT_11 "-Dmempool_unref(x)=pool_unref(x)" -fPIC -shared -Wall -Wextra -DPLUGINNAME=antispam -o debug.o.o debug.c cc -DHAVE_CONFIG_H -Wall -I/root/tmp/dovecot-1.1.rc5/ -I/root/tmp/dovecot-1.1.rc5/src/ -I/root/tmp/dovecot-1.1.rc5/src/lib/ -I/root/tmp/dovecot-1.1.rc5/src/lib-storage/ -I/root/tmp/dovecot-1.1.rc5/src/lib-mail/ -I/root/tmp/dovecot-1.1.rc5/src/lib-imap/ -I/root/tmp/dovecot-1.1.rc5/src/lib-dict/ -I/root/tmp/dovecot-1.1.rc5/src/lib-index/ -I/root/tmp/dovecot-1.1.rc5/src/imap/ -DCONFIG_DEBUG -DDEBUG_SYSLOG -DCONFIG_DEBUG_VERBOSE -DCONFIG_DOVECOT_11 "-Dmempool_unref(x)=pool_unref(x)" -fPIC -shared -Wall -Wextra -DPLUGINNAME=antispam antispam-storage-1.1.c -o antispam-storage-1.1 cc -o .o cc: no input files make: *** [.o] Error 1 When running make clean to try to compile again, a file called "antispam-storage-1.1.c" (without any extension) is not deleted, and this file was not before running make install. If I run again make install with that file present (after running make clean), i get this output: cc -c -DHAVE_CONFIG_H -Wall -I/root/tmp/dovecot-1.1.rc5/ -I/root/tmp/dovecot-1.1.rc5/src/ -I/root/tmp/dovecot-1.1.rc5/src/lib/ -I/root/tmp/dovecot-1.1.rc5/src/lib-storage/ -I/root/tmp/dovecot-1.1.rc5/src/lib-mail/ -I/root/tmp/dovecot-1.1.rc5/src/lib-imap/ -I/root/tmp/dovecot-1.1.rc5/src/lib-dict/ -I/root/tmp/dovecot-1.1.rc5/src/lib-index/ -I/root/tmp/dovecot-1.1.rc5/src/imap/ -DCONFIG_DEBUG -DDEBUG_SYSLOG -DCONFIG_DEBUG_VERBOSE -DCONFIG_DOVECOT_11 "-Dmempool_unref(x)=pool_unref(x)" -fPIC -shared -Wall -Wextra -DPLUGINNAME=antispam -o debug.o debug.c cc -o .o cc: no input files make: *** [.o] Error 1 If I run make clean and manually deleted that file before running make install, i get again the first output. Why am i getting this error? Regards.

1 0

[Dovecot] I've moved
by Timo Sirainen 24 May '08

24 May '08

I've moved again. If you need to know my new address, whois imapwiki.org (dovecot.org address is still lagging behind). My living costs also increased some because of this, but hopefully I'll get enough money from Dovecot coding to pay for it. :) I'll try to get back to replying mails within the next few days.

2 2

[Dovecot] Disallow folder delete
by Kenneth Porter 24 May '08

24 May '08

Is there a straightforward way to disallow the deletion of all IMAP mailboxes? I have a user who's deleted an important IMAP mailbox and I'm now recovering a recent copy from the backup. But I'd rather just blanket disallow all folder deletions. The user is using Thunderbird and this has happened more than once so I suspect Tbird is willing to let a folder get deleted too easily. Perhaps there was a delay in the confirmation dialog and the user clicked ahead and confirmed something he shouldn't have. I'm looking at <http://wiki.dovecot.org/ACL> and it looks like I should be able to use a group override to disallow "x" (mailbox delete) but the page says that groups aren't implemented, so I don't know how one says that nobody can do this for any mailbox. I'm using 1.2.rc15 from CentOS 5 (RHEL5 equivalent).

7 16

[Dovecot] Don't Understand Error Entry
by Carlos Williams 24 May '08

24 May '08

I am using dovecot-0.99.11-8.EL4 on my system and decided to check the logs since I just took over as the administrator on this system and I noticed the same error entry over and over in the logs. I went to /var/log/dovecot.err and see: imap(rangry): May 22 13:33:31 Error: Error parsing IMAP envelope: "Thu, 20 Apr 2006 10:10:01 -0400" "Re: Hi there I have a question" (("Rodney Angry" NIL "rodney.s.angry" "example.com")) (("Rodney Angry" NIL "rodney.s.angry" " example.com")) ((NIL NIL "rodney.s.angry" "example.com")) (("Gryder, Connie" NIL "CONSTANCE.L.GRYDER" "example.com")) NIL NIL "< DD3761B99DC88F4284EDE00D608383C65DF16C(a)0088-its-exmp01.us.example.com>" NIL I don't understand what this error message means and why its flooding my logs. I do know the that the name in parenthesis on line one is a user on my email server. <rangry> is a user on my domain with a valid email account but I can't tell if the problem is coming from example.com or originating from <rangry>. Anyone happen to know what is causing this? I don't know if you guys need my config here so I don't want to flood this message. If this makes sense to anyone, please let me know what I can do to resolve this or keep this from flooding my email server. Thanks!

4 5

[Dovecot] log contents questions?
by Knute Johnson 24 May '08

24 May '08

I switched from using Pegasus and POP3 to Thunderbird and IMAP for my email. Now I get a lot of "Corrupted index cache file" errors in my log. Dovecot is running under Fedora 8 and is version 1.0.13-6.fc8. The Thunderbird is version 2.0.0.14 running under Windows XP. My wife's Blackberry is also using IMAP and not reporting any errors. Any ideas what the problem is or how to fix it? Thanks, knute... --------------------- Dovecot Begin ------------------------ Dovecot disconnects: Inactivity: 2 Time(s) Logged out: 2606 Time(s) in IDLE: 27 Time(s) **Unmatched Entries** dovecot: IMAP(knute): Connection closed: 5 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/CR-FFL/dovecot.index.cache: invalid record size: 3 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/INBOX/dovecot.index.cache: invalid record size: 2 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/frazmtn.com/dovecot.index.cache: invalid record size: 4 Time(s) dovecot: IMAP(linux): Connection closed: 4 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Dovecot/dovecot.index.cache: invalid record size: 2 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora List/dovecot.index.cache: invalid record size: 4 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora Selinux List/dovecot.index.cache: invalid record size: 1 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora Test List/dovecot.index.cache: invalid record size: 2 Time(s) ---------------------- Dovecot End ------------------------- -- Knute Johnson linux(a)www.knutejohnson.com

2 4

[Dovecot] procmail --> deliver question
by Ben Budts 23 May '08

23 May '08

Hi there, I use dovecot-1.1-rc4, got imap, imaps, pop3 & pop3s working fine with the mbox format. I use sendmail-8.14.2 as an MTA, sendmail uses procmail as an LDA. I migrated to maildir format now, and pipe all my mail to deliver right now to be able to make use of the indexing etc... Problem is I run into some errors : #My .procmailrc PATH=/usr/bin:/usr/local/bin:/usr/sbin SHELL="/bin/bash" SENDMAIL="sendmail -oi -t" DELIVER="/opt/dovecot/libexec/dovecot/deliver" LOGFILE="$HOME/procmail.log" #/dev/null VERBOSE=on LOGABSTRACT = "all" #DEFAULT="$HOME/Maildir/" #MAILDIR="$HOME/Maildir/" :0 w | $DELIVER ##### My procmail.log : procmail: [12743] Wed May 21 13:43:38 2008 procmail: Assigning "LOGABSTRACT=all" procmail: Executing "/opt/dovecot/libexec/dovecot/deliver" Fatal: destination user parameter (-d user) not given procmail: Error while writing to "/opt/dovecot/libexec/dovecot/deliver" procmail: Program failure (64) of "/opt/dovecot/libexec/dovecot/deliver" procmail: Assigning "LASTFOLDER=/opt/dovecot/libexec/dovecot/deliver" procmail: Locking "/var/spool/mail/kris.lock" procmail: Assigning "LASTFOLDER=/var/spool/mail/kris" procmail: Opening "/var/spool/mail/kris" ####" It's not working out and he falls back to delivering his mail to /var/spool/mail/%u Could you guys point me out in the right direction please ? Another question about the logging with deliver... I've put the following in my deliver.conf : deliver.conf in the lda section : log_path = /var/log/dovecot/deliver.log info_log_path = /var/log/dovecot-deliver.log root@blaat:/home/kris# ls -la /var/log/dovecot/ total 232 drwxrwxrwx 2 root root 4096 2008-05-20 10:44 . drwxr-xr-x 11 root root 4096 2008-05-19 10:08 .. -rw-rw-rw- 1 root root 0 2008-05-20 10:44 deliver.log But it's not logging at all... Also tried the syslog alternative, no logging either. Also put set user or group ID on execution (s) on the deliver binary : -rwsr-sr-x 1 root root 693300 2008-05-19 09:38 /opt/dovecot/libexec/dovecot/deliver thx a lot Benjamin

2 1

[Dovecot] dovecot-sieve on freebsd
by Lazar Szilard 22 May '08

22 May '08

Hi,I need some help. I use dovecot and dovecot-sieve on a freebsd 7.0-release. everything worked fine without dovecot sieve. I want to deliver amavisd spam marked messages to the 'spam' folder of the user. the system uses virtual environment with multiple domains (and users).all want is a global sieve, to all users, all domains.I googled, but I cannot find the problem,my protocol lda section:protocol lda {    log_path = /usr/local/vmail/dovecot-deliver.log    sieve_global_dir = /usr/local/vmail/globalsieverc    mail_plugins = cmusieve    mail_debug = yes    log_path = /var/log/dovecot-deliver    info_log_path = /var/log/dovecot-deliver     postmaster_address = postmaster(a)tamann.hu    mail_plugin_dir = /usr/local/lib/dovecot/lda    sendmail_path = /usr/sbin/sendmail}globalsieverc:require "fileinto";if header :contains "X-Spam-Flag" "YES" {        fileinto "Spam";        stop;}thank you for your help,and sorry for my bad english.t

1 0

[Dovecot] auth_socket_path permissiones
by Adrián Ribao Martínez 22 May '08

22 May '08

Hello, I'm using dovecot 1.0 under debian etch. The lda socket path is set to: auth_socket_path = /var/spool/postfix/private/auth But this gives me the error: net_connect(/var/spool/postfix/private/auth) failed: Permission denied I suppose deliver is run as dovecot user. I read about running deliver as root with the suid bit set. I'm not quite sure if this is a good solution. Is there any other way. In the wiki says: "Most MTAs won't let you run deliver as root, so for now you'll need to make it setuid root. However deliver isn't designed to be run as setuid-root" My MTA is postfix, does someone know if postfix let me run deliver as root? If not, should I go to the setuid option? Thank you. -- Adrián Ribao Martínez

3 3

[Dovecot] Clients hang because imap-login discards post-login commands
by Mike Abbott 22 May '08

22 May '08

Some of my IMAP clients hang when connecting to Dovecot 1.1.rc5. I believe the problem is that imap-login reads eagerly rather than sparingly. If a client sends a login user password b select Inbox all at once, without waiting for the login reply before sending the select, imap-login eats the second command (reads it from the socket and does nothing with it; system call tracing confirms this) and the client hangs waiting for a reply to the select command. I can reproduce this simply using telnet to the dovecot on localhost, as long as I send both lines at once (I paste them in together). $ telnet localhost 143 * OK Dovecot ready. a login user password b select Inbox a OK Logged in. <dovecot never replies to select> This may also be true with pop3-login, I have not checked. It does happen (with IMAP) when authentication is delayed and Dovecot responds with "* OK Waiting for authentication process to respond.." but I believe that shares the same underlying cause as the simpler case above. I believe the login processes should read only as much as they need to satisfy the login request and leave subsequent commands in the socket for post-login processing. Or, the login processes should pass the remainder of their input buffers to the mail processes so no commands are dropped. This section of RFC 2060 explains why I think this: 5.5. Multiple Commands in Progress The client MAY send another command without waiting for the completion result response of a command, subject to ambiguity rules (see below) and flow control constraints on the underlying data stream. Similarly, a server MAY begin processing another command before processing the current command to completion, subject to ambiguity rules. [...] The exception is if an ambiguity would result because of a command that would affect the results of other commands. Clients MUST NOT send multiple commands without waiting if an ambiguity would result. If the server detects a possible ambiguity, it MUST execute commands to completion in the order given by the client. So it appears that both the client and Dovecot may be in violation, depending on how you define "ambiguity." The RFC does not explicitly define whether login causes an ambiguity, but I personally believe that login does "affect the results of other commands" (the login may fail, for instance). So the client should not issue commands before receiving the login reply, and Dovecot should not drop commands during login. I have reported the client issue to the developers of the IMAP client, as I am reporting the server issue to you. Fortunately for me, only one or the other needs to change to erase the symptom (hung clients), but fixing both would be best. Thanks for your attention.

3 2

[Dovecot] Dovecot or postfix Quota
by Adrián Ribao Martínez 22 May '08

22 May '08

Hello, I'm a bit confused with the dovecot quota support. What is it for? I thought postfix should be the one managing the quota. If I set up a quota in dovecot, does dovecot keep the messages size under certain limit? What happen when you reach the quota limit? What's the difference between postfix quotas and dovecot quota? I'm confused about this. Thank you! -- Adrián Ribao Martínez

3 4

[Dovecot] VMware and Time moved backwards
by Robert Henjes 22 May '08

22 May '08

Hi, I followed the discussions regarding the "time moved backward" problem and the use of ntp in such cases. At our department we are running two dovecot servers within an vmware server environment, and unfortunately the timedrift (with ntpd active) exceeds sometimes up to 30 minutes virtual drift within 10 minutes realtime (mostly into future). This is due to some overcorrections within the TSC algorithms of the vmware virtual machine. More information and some hints to workaround are documented here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=di… Nevertheless we are currently working on evaluating a stable solution by doing some system measurements, which would be the best option to cope with this problem, since the XEN environment seems to have a similar issue. Running "ntpdate -u" as a cronjob is not an option due to two facts: a) Time is moving quickly and may cause "major problems" ;) b) It is not recommended by the vmware team itself as well We are currently considering two options: a) Using the "clock=pit" kernel option, which may cause the system to be to slow b) using vmware tools and use only the ntp synchronisation of the host (we have currently only little experience with this). Also vmware tools are somewhat critical in case of updates. So our intention was to use as less vmware specific things as possible within the virtual machine, so only our host itself depends on vmware specific software. The question is, which option would you prefer? Is there another solution beside the mentioned ones? According to Timo's postings, workarounds within the dovecot itself to cope with "time moved backward" problems are not planned yet to be impelented. So best regards, Robert

5 5

Re: [Dovecot] VMware and Time moved backwards
by Robert Henjes 21 May '08

21 May '08

Thank you for the prompt answers @Luuk Vosslamber >finding correct values for the following entrys in your vmware(host) >config file might solve some things: >host.cpukHz = 1596000 <== depends on processor speed ;-) >host.noTSC = TRUE >ptsc.noTSC = TRUE >hostinfo.noTSC = TRUE >tools.syntime = TRUE > >Above values go with the presumption that the host CPU is running at a >fixed frequency. The variable frequency seems to be the origin of this >problem.. We tried your parameters already, but they are not an option, unless you have the following a) machine smp disabled (enabled in our case) b) other machines on the host system have really low load c) vmware tools should not be missing on guest @Peter Hessler >never ever ever run ntp on virtual hardware. > >instead, run ntp on the host hardware, and tell the client to always obey the bios clock. I add "* * * * * /sbin/hwclock --localtime -->hctosys" >to my crontab for that. Thank you very much Peter, this hint opens up a bunch of new possibilities only mentioning "adjtimex" ... BUT: And this brings me back to, why I posted this issue to the dovecot mailinglist and not elsewhere: All these guest based solutions lead to a fixed time movement (we used previously ntpdate -u every 7 minutes, ntp itself synchronizes every 11 minutes with the hardware clock for calculating drifts), which happens about once per week, that the time movement backward is larger than 11 seconds between two dovecot imap operations, which leads to an immediate shutdown of the dovecot process. All other services on these machine can cope with this. So the question is how to get these adjustments smooth or close to realtime. Best regards, Robert Btw.: We are running Dovecot 1.0.13 from Debian etch-backports (which is an important information since debian seems to have its own rules ;) )

1 0

[Dovecot] Maildir locking by LDA of dovecot
by Mike Grozak 21 May '08

21 May '08

Hi all! First of all, I want ti thank the whole Dovecot community (developers for developing and fast responses, users for populating and responses too). Dovecot is a really good and fast IMAP server - it serves near 3000 in our installation. Now I have a problem and request community's help its resolving;) Dovecot version: 1.0.13, compiled with vpopmail support. I have an account spam(a)domain.com (:-), in which we put all our spam (we gather statistic later). There can be 10 and more delivery attempts in a second to maildir of this account during the spam attacks on our server. The queue of our server can grow up to 20k messages, and all of these messages are sent to spam(a)domain.com. I found a lot of such strings in dovecot.log file during the such DoS attack: dovecot.log:deliver(spam@domain.com): May 16 04:18:48 Info: msgid=<01c8b6da$a8bacf80$b7af2abe@sale>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:18:59 Info: msgid=<6611811842.20080516012444(a)poiusadfhnvxzmdiasdasgkhlsdkfg.com>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:06 Info: msgid=<01c8b6a8$7b552e00$a0a4034c@sale>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:14 Info: msgid=<360825920.32055246029506(a)mirgames.ru>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:20:50 Info: msgid=<01c8b6b1$0df9cb00$cc36dfc9@tek2>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:21:00 Info: msgid=<087901c7ca2d$ef272640$1e01a8c0(a)telefonia.InterCable.net>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:21:01 Info: msgid=<000701c8b6d2$01ff999f$c491aca7@snoueiij>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:32 Info: msgid=<000801c8b69b$060c0230$3cd8a4b7@cpbvlrx>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:45 Info: msgid=<000801c8b6a5$04ba6412$9910848d@aldldr>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:22:45 Info: msgid=<031401c772e2$adc5be40$1e01a8c0(a)mtu-net.ru>: save failed to INBOX: Timeout while waiting for lock dovecot.log:deliver(spam@domain.com): May 16 04:23:08 Info: msgid=<01c8b6db$0222fe80$b7af2abe@info>: save failed to INBOX: Timeout while waiting for lock My dovecot.conf: $ cat /etc/dovecot.conf | grep -v \# | grep -v ^\n protocols = imap pop3 log_path = /var/log/dovecot.log ssl_disable = yes login_user = dovecot login_process_per_connection = no login_max_connections = 1024 login_greeting = Server is ready. >>dotlock_use_excl = yes - can it be the reason? fsync_disable = yes first_valid_uid = 39 last_valid_uid = 39 first_valid_gid = 39 last_valid_gid = 39 max_mail_processes = 1024 maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = yes protocol imap { mail_plugins = quota imap_quota login_greeting_capability = yes imap_client_workarounds = outlook-idle } protocol pop3 { pop3_lock_session = no pop3_uidl_format = %08Xu%08Xv mail_plugins = quota } protocol lda { postmaster_address = postmaster(a)tversu.ru mail_plugins = quota cmusieve sendmail_path = /usr/lib/sendmail fsync_disable = no } auth_cache_size = 10240 auth_username_format = %Lu auth default { mechanisms = plain login cram-md5 socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } client { path = /var/spool/postfix/private/auth mode = 0666 user = postfix group = postfix } } passdb vpopmail { args = cache_key=%u dovecot } userdb vpopmail { } user = vpopmail ssl_require_client_cert = no } dict { } plugin { quota = maildir:ignore=Trash } What can I do for resolving this locks? May be, while looking into uidlist file, can dovecot LDA lock it? And other deliver processes can't open it and wait for him? --------------------------- WBR, Mike Grozak, TvSU IC

1 0

[Dovecot] Running sieve filters on already delivered mails
by Axel Gembe 20 May '08

20 May '08

I want to know what the best way to run sieve filters on already delivered mail is. Problem is that I have a rather large unfiltered mailbox and filtering it by hand would be a PITA. I don't mind coding something up to do this, but I just don't think that I'm the first one with this problem. Thanks - Axel

2 2

[Dovecot] Cannot compile current version of antispam
by Steffen Kaiser 20 May '08

20 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, with the current (2008-05-20) repository releases of Dovecot-1.0 and antispam the plugin no longer compiles: antispam-storage-1.0.c: In function âantispam_mail_update_keywordsâ: antispam-storage-1.0.c:285: error: âidxkwd__typeâ undeclared (first use in this function) antispam-storage-1.0.c:285: error: (Each undeclared identifier is reported only once antispam-storage-1.0.c:285: error: for each function it appears in.) antispam-storage-1.0.c:285: warning: type defaults to âintâ in declaration of âtype nameâ antispam-storage-1.0.c:285: warning: initialization from incompatible pointer type Version of antispam: (first entry of git log) commit c3a343290773d6e22a08946cb2ef80b1b8fe8a06 Author: Johannes Berg <johannes(a)sipsolutions.net> Date: Sat Apr 26 20:34:06 2008 +0200 add 1.1 storage. probably doesn't work Base version of Dovecot: changeset: 5551:71c02fdf1b59 branch: branch_1_0 tag: tip Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIMtunVJMDrex4hCIRAjXgAJ9j0oNUa0wGaLMshw6F/kjQoQxvygCdHLE9 Vb7rUcHxSr1kcgN+MHCsI1U= =dBuy -----END PGP SIGNATURE-----

2 2

[Dovecot] New ManageSieve releases: v0.10.2 for Dovecot 1.1.rc4 and v9.3 for Dovecot 1.0.13
by Stephan Bosch 20 May '08

20 May '08

Hello Dovecot users, Recently, I was pointed towards a problem in the managesieve SASL implementation. As it turns out there was a bug in handling mechanisms that expect more than a single client response. That is why the PLAIN mechanism works and the (obsolete) LOGIN mechanism fails (along with probably many others). This problem was present in both v9.2 and v0.10.1 for Dovecot 1.0 and 1.1 respectively. This issue is fixed in the new releases: Change Log v9.3/v0.10.2 ------------------------ * Fixed bug that caused SASL mechanisms that require more than a single client response to fail. Reported by Steffen Kaiser and occured when he tried using the (obsolete) LOGIN mechanism. * Updated installation and configuration documentation to match the information provided in the wiki Installation ------------ The full installation procedure and other relevant information regarding ManageSieve is finally available on the Dovecot wiki at: http://wiki.dovecot.org/ManageSieve New releases: 1.0: (patch) http://www.rename-it.nl/dovecot/1.0/dovecot-1.0.13-MANAGESIEVE-v9.3.diff.gz http://www.rename-it.nl/dovecot/1.0/dovecot-1.0.13-MANAGESIEVE-v9.3.diff.gz… 1.1: (package + patch) http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.2.tar.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.2.tar.gz.s… http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.rc4-managesieve-0.10.2.diff… http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.rc4-managesieve-0.10.2.diff… (my public key (id: 3DFBB4F4) can be found at wwwkeys.pgp.net) Have fun testing the Dovecot ManageSieve service. Don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

2 1