- dovecot - dovecot.org

[Dovecot] alias best practice
by Luigi Rosa 06 Jul '09

06 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Given a Linux mail server with Postfix+Dovecot using MySQL as userbase, a single Linux user for file system access, two mail domains configured (acme1.com acme2.com) and a maildir structure as follows \var\spool\mail\acme1.com- \user1 \user2 \user3 \var\spool\mail\acme2.com- \user1 \user2 \user3 I want that the mail of user1(a)acme1.com and user1(a)acme2.com goes in \var\spool\mail\acme1.com\user1 Note that there could be some users not equal between two domains. What is the best practice? 1) Alias at Postfix level 2) The same maildir path specified in MySQL record 3) ln -s between \var\spool\mail\acme1.com\user1 and \var\spool\mail\acme2.com\user1 4) Else? (Dovecot virtual mailbox) Thank you. Ciao, luigi - -- / +--[Luigi Rosa]-- \ Blessed are they who Go Around in Circles, for they Shall be Known as Wheels. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpOGf8ACgkQ3kWu7Tfl6ZTJ1ACgp52Fy7PbGpnU9pFnvVioNcFO OO8AoJRGG2UkyPXczR/bkAXqwjmVtpyL =Loje -----END PGP SIGNATURE-----

4 3

[Dovecot] Dovecot 1.2rc4 - launchd keeps trying to restart it, after Dovecot exits with exit code: 89
by James Brown 06 Jul '09

06 Jul '09

I know I should update to the release version (will do on Monday), but I keep getting this in my logs (ie All Messages shown): 4/07/09 11:50:18 PM Dovecot[742] Fatal: Dovecot is already running with PID 624 (read from /usr/local/var/run/dovecot/master.pid) 4/07/09 11:50:18 PM com.apple.launchd[1] (Dovecot[742]) Exited with exit code: 89 4/07/09 11:50:18 PM com.apple.launchd[1] (Dovecot) Throttling respawn: Will start in 10 seconds 4/07/09 11:50:18 PM com.apple.launchd[1] (Dovecot) Throttling respawn: Will start in 10 seconds 4/07/09 11:50:28 PM Dovecot[743] Fatal: Dovecot is already running with PID 624 (read from /usr/local/var/run/dovecot/master.pid) 4/07/09 11:50:28 PM com.apple.launchd[1] (Dovecot[743]) Exited with exit code: 89 4/07/09 11:50:28 PM com.apple.launchd[1] (Dovecot[743]) Exited with exit code: 89 4/07/09 11:50:28 PM com.apple.launchd[1] (Dovecot) Throttling respawn: Will start in 10 seconds 4/07/09 11:50:38 PM Dovecot[745] Fatal: Dovecot is already running with PID 624 (read from /usr/local/var/run/dovecot/master.pid) 4/07/09 11:50:38 PM com.apple.launchd[1] (Dovecot[745]) Exited with exit code: 89 4/07/09 11:50:38 PM com.apple.launchd[1] (Dovecot[745]) Exited with exit code: 89 Anywhere in particular that I should look for hints as to what is causing Dovecot to exit? System is a Mac Mini Core 2 Duo running 10.5.7 (Leopard). Thanks, James. dovecot -n: # 1.2.rc4: /usr/local/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 768). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: Darwin 9.7.0 i386 hfs protocols: imap pop3 imaps pop3s ssl_cert_file: /etc/dovecot/dovecot.pem ssl_key_file: /etc/dovecot/dovecot.pem disable_plaintext_auth: no 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 login_user: _dovecot first_valid_uid: 102 last_valid_uid: 105 mail_uid: 27 mail_gid: 27 mail_location: maildir:/usr/local/virtual/%d/%u 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 auth default: mechanisms: cram-md5 login plain user: nobody failure_delay: 4 passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf passdb: driver: sql args: /etc/dovecot/dovecot-sqlmd5.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix master: path: /var/run/dovecot-auth-master mode: 384

3 4

[Dovecot] Dovecot v1.2 ACL shared-boxes users in SQL, how to remove entries?
by Steffen Kaiser 05 Jul '09

05 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I noticed that entries added to the ACL dict are not removed, when an user no longer has explicit ACLs to another user, e.g.: [at the beginning no ACLs for "user"] 1 login testuser pwd 2 setacl INBOX user lp 3 deleteacl INBOX user Although "user" has no ACLs of mailfolders of "testuser", the user-testuser relation is still in the DB and upon login of user the ACLs in user's Maildir is consulted. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSkN+VHWSIuGy1ktrAQLR8ggAjmyUvByjz/acGoQzXahh4dr4/+FT9bx+ FU9ze1dK9ZgFWW+SkBrgmMW6ayu77rHG3Qp66ONAgJFRmBv+w6G8IJA8yueD/8z4 ZsGN1ekQxBwqAJWnGyMAVNiksRwE0SFUNAoTIKfjOLE21fQhiI6aGpdFWqP89/Vb jITOQ0+woAm2g2DvCBEMRXRZoFZGO8UCX6RCXaaqGV0c7mEkwRn/cSB/EimTTHr1 lkGXtjpJJ7u9d5apSK2TX5FFKPmKgU9G4rCzMvG9sNB808dwvtnaNBCii3btlxRT 5UBIji4PBx7zs6APctIjfsuMg5yiMg92ip9SBMYnBZ2BmmCMzDu9iA== =gAST -----END PGP SIGNATURE-----

3 5

[Dovecot] 1.1.16 and global ACLs
by Axel Luttgens 04 Jul '09

04 Jul '09

I was going to test 1.1.16 so as to see how it handles global ACLs (in the hope to have a possible comparison with 1.2.0's odd behavior), when I encountered the problem described hereafter. Note that just disabling ACLs is sufficient to get back a fully functional imap binary. So, should there be some plans for a 1.1.17 version, perhaps could the info provided here prove somewhat useful. Folowing telnet session: # telnet 127.0.0.1 imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. a1 login testuser ****** a1 OK Logged in. Connection closed by foreign host. yields this in mail.log: dovecot[18129]: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot[18129]: IMAP(testuser): Loading modules from directory: /usr/ local/dovecot-1.1.16/lib/dovecot/imap dovecot[18129]: IMAP(testuser): Module loaded: /usr/local/ dovecot-1.1.16/lib/dovecot/imap/lib01_acl_plugin.so dovecot[18129]: IMAP(testuser): Effective uid=2001, gid=2001, home=/ Volumes/ALMbpSpare/People/a/testuser dovecot[18129]: IMAP(testuser): mbox: data=~/_mailboxes:INBOX=~/ _mailboxes/inbox:CONTROL=~/_mboxesctrl dovecot[18129]: IMAP(testuser): fs: root=/Volumes/ALMbpSpare/People/a/ testuser/_mailboxes, index=, control=/Volumes/ALMbpSpare/People/a/ testuser/_mboxesctrl, inbox=/Volumes/ALMbpSpare/People/a/testuser/ _mailboxes/inbox dovecot[18129]: IMAP(testuser): acl: initializing backend with data: vfile:/usr/local/etc/dovecot-acls dovecot[18129]: IMAP(testuser): acl: acl username = testuser dovecot[18129]: IMAP(testuser): acl: owner = 1 dovecot[18129]: IMAP(testuser): acl vfile: Global ACL directory: /usr/ local/etc/dovecot-acls dovecot[18129]: child 18272 (imap) killed with signal 11 (core dumps disabled) and this crash log: Process: imap [18272] Path: /usr/local/dovecot-1.1.16/libexec/dovecot/imap Identifier: imap Version: ??? (???) Code Type: X86 (Native) Parent Process: dovecot [18129] Date/Time: 2009-07-04 18:55:46.552 +0200 OS Version: Mac OS X 10.5.7 (9J61) Report Version: 6 Anonymous UUID: EE838D90-3F91-46F8-9CDA-3611674B371F Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000d0201332 Crashed Thread: 0 Thread 0 Crashed: 0 ??? 0x000b87bf static_system_pool + 27 1 lib01_acl_plugin.so 0x0011b871 acl_cache_right_lookup + 33 (acl-cache.c:146) 2 lib01_acl_plugin.so 0x0011b9a6 acl_cache_mask_init + 182 (acl-cache.c:105) 3 lib01_acl_plugin.so 0x00118cf8 acl_backend_init + 376 (acl-backend.c:76) 4 lib01_acl_plugin.so 0x0011d269 acl_mailbox_list_created + 217 (acl-mailbox-list.c:429) 5 imap 0x00053a0a mailbox_list_init + 410 (mailbox-list.c:220) 6 imap 0x000344c5 mbox_create + 645 (mbox- storage.c:471) 7 imap 0x00052f40 mail_storage_create + 272 (mail-storage.c:224) 8 imap 0x00050978 mail_namespaces_init + 1096 (mail-namespace.c:230) 9 imap 0x00011ab9 main + 1065 (main.c:238) 10 imap 0x00001646 start + 54 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00200a00 ebx: 0x00118b8b ecx: 0x002009d0 edx: 0x002009d0 edi: 0x00200a00 esi: 0x0011da28 ebp: 0xbffff158 esp: 0xbffff13c ss: 0x0000001f efl: 0x00010282 eip: 0x000b87bf cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0xd0201332 Binary Images: 0x1000 - 0xb6fe0 +imap ??? (???) <e5ae287e992319a2faf58982a15102be> /usr/local/dovecot-1.1.16/libexec/ dovecot/imap 0x118000 - 0x11dff7 +lib01_acl_plugin.so ??? (???) <24284783dc3113906f90a37bdd1fce02> /usr/local/dovecot-1.1.16/lib/ dovecot/imap/lib01_acl_plugin.so 0x8fe00000 - 0x8fe2db43 dyld 97.1 (???) <100d362e03410f181a34e04e94189ae5> /usr/lib/dyld 0x9013c000 - 0x90143fe9 libgcc_s.1.dylib ??? (???) <f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib 0x913ba000 - 0x91521ff3 libSystem.B.dylib ??? (???) <b47c8e6e45aef620730710a732bf1930> /usr/lib/libSystem.B.dylib 0x92f5f000 - 0x92f63fff libmathCommon.A.dylib ??? (???) /usr/lib/ system/libmathCommon.A.dylib 0x97038000 - 0x9712cff4 libiconv.2.dylib ??? (???) <c508c60fafca17824c0017b2e4369802> /usr/lib/libiconv.2.dylib 0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/ libSystem.B.dylib This is the output of dovecot -n: # 1.1.16: /usr/local/etc/dovecot.conf # OS: Darwin 9.7.0 i386 protocols: pop3 imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/dovecot-1.1.16/libexec/dovecot/ imap-login login_executable(imap): /usr/local/dovecot-1.1.16/libexec/dovecot/imap- login login_executable(pop3): /usr/local/dovecot-1.1.16/libexec/dovecot/pop3- login first_valid_uid: 2001 mail_location: mbox:~/_mailboxes:INBOX=~/_mailboxes/inbox:CONTROL=~/ _mboxesctrl mail_debug: yes mbox_read_locks: flock mbox_write_locks: flock dotlock mail_executable(default): /usr/local/dovecot-1.1.16/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot-1.1.16/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot-1.1.16/libexec/dovecot/pop3 mail_plugins(default): acl mail_plugins(imap): acl mail_plugins(pop3): mail_plugin_dir(default): /usr/local/dovecot-1.1.16/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot-1.1.16/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot-1.1.16/lib/dovecot/pop3 pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: debug: yes passdb: driver: pam args: * userdb: driver: passwd plugin: acl: vfile:/usr/local/etc/dovecot-acls

1 0

Re: [Dovecot] Dovecot 1.2rc4 - launchd keeps trying to restart it, after Dovecot exits with exit code: 89
by Mark Sapiro 04 Jul '09

04 Jul '09

James Brown wrote: > I know I should update to the release version (will do on Monday), but > I keep getting this in my logs (ie All Messages shown): > > 4/07/09 11:50:18 PM Dovecot[742] Fatal: Dovecot is already running > with PID 624 (read from /usr/local/var/run/dovecot/master.pid) > 4/07/09 11:50:18 PM com.apple.launchd[1] (Dovecot[742]) Exited with > exit code: 89 > 4/07/09 11:50:18 PM com.apple.launchd[1] (Dovecot) Throttling respawn: > Will start in 10 seconds > 4/07/09 11:50:18 PM com.apple.launchd[1] (Dovecot) Throttling respawn: > Will start in 10 seconds > 4/07/09 11:50:28 PM Dovecot[743] Fatal: Dovecot is already running > with PID 624 (read from /usr/local/var/run/dovecot/master.pid) > 4/07/09 11:50:28 PM com.apple.launchd[1] (Dovecot[743]) Exited with > exit code: 89 > 4/07/09 11:50:28 PM com.apple.launchd[1] (Dovecot[743]) Exited with > exit code: 89 > 4/07/09 11:50:28 PM com.apple.launchd[1] (Dovecot) Throttling respawn: > Will start in 10 seconds > 4/07/09 11:50:38 PM Dovecot[745] Fatal: Dovecot is already running > with PID 624 (read from /usr/local/var/run/dovecot/master.pid) > 4/07/09 11:50:38 PM com.apple.launchd[1] (Dovecot[745]) Exited with > exit code: 89 > 4/07/09 11:50:38 PM com.apple.launchd[1] (Dovecot[745]) Exited with > exit code: 89 > > Anywhere in particular that I should look for hints as to what is > causing Dovecot to exit? This may or may not be relevant, but see the thread "Mailman vs OSX vs launchd" at <http://mail.python.org/pipermail/mailman-users/2009-June/066371.html> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

[Dovecot] Urgent problem with deleting emails and maildirsize
by Jose Luis Marin Perez 04 Jul '09

04 Jul '09

Dears Sirs, I hope they can help me with this problem since it is urgent. I've completed the migration from Courier to Dovecot that has been running correctly, the only problem is that maildirsize file is not updated when you delete the emails, resulting in accounts that reach to 100% faster, so I have to manually delete this file. Through Dovecot can be configured to automatically update when maildirsize delete emails? Thanks Jose Luis _________________________________________________________________ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx

6 11

[Dovecot] unsu
by pj2002＠inbox.lv 04 Jul '09

04 Jul '09

-- Tavs bezmaksas pasts Inbox.lv

2 1

[Dovecot] How to rebuild index?
by Max Ivanov 03 Jul '09

03 Jul '09

I've deleted some mails using my handmade tool, it deletes some files in "cur" subdir, but deleted messages are still appear in thunderbird. I believe that's because of stale index file. Is it safe to delete dovect.index? Or what else should I delete/modify to make TB view in sync with real state of filesystem?

3 2

[Dovecot] mbox sync failure
by Alnis Morics 03 Jul '09

03 Jul '09

Hi, Yesterday I had to reboot my server machine and I think there was an email client connected from the LAN during the reboot which I did not notice then. Now that mailbox is no longer accessible: as soon as I try to connect, it lets me wait forever while openin the folder, and cycles endlessly this message in the logs: Jul 2 19:40:37 myhostname dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=#.#.#.#, lip=#.#.#.#, TLS Jul 2 19:40:37 myhostname dovecot: IMAP(username): unlink(/var/mail/username.lock) failed: Permission denied Jul 2 19:40:48 myhostname dovecot: IMAP(username): file mbox-sync.c: line 1372 (mbox_sync_handle_eof_updates): assertion failed: (trailer_size <= 2) Jul 2 19:40:48 myhostname dovecot: IMAP(username): Raw backtrace: imap [0x80b2081] -> imap [0x80b1f99] -> imap [0x807a536] -> imap [0x807ae71] -> imap(mbox_sync+0x422) [0x807d3c2] -> imap(mbox_storage_sync_init+0x3e) [0x807d8de] -> imap(imap_sync_nonselected+0x1c) [0x806446c] -> imap(_cmd_select_full+0xc3) [0x805be83] -> imap(cmd_select+0x19) [0x805c059] -> imap [0x805d5ef] -> imap [0x805d690] -> imap(_client_input +0x74) [0x805dd64] -> imap(io_loop_handler_run+0xf0) [0x80b7e20] -> imap(io_loop_run+0x18) [0x80b7338] -> imap(main+0x478) [0x8066388] -> /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7e36455] -> imap [0x8058561] Jul 2 19:40:48 myhostname dovecot: child 2459 (imap) killed with signal 6 (I have Debian Lenny with dovecot 1.0.15.) I tried to add the user dovecot to the group mail and give the group mail write permission to the mailbox. The permission errors stopped appearing but everything else is still there, including .lock file and 3 imap-login processes that resume as soon as I try to kill them. There are also 2 unimportant mailboxes that still work. I can view the beginning of the "username" mailbox with mc inner viewer, but it hangs as I go to the end of file. Tried to copy the file so I could freely experiment with it but the copying hung up when it reached 87 % (the file is 1.1 GB). The copied part was unreadable. Tried to formail -ds < /var/mail/username >> /backup/usernameJul3 but with the same result. Is there a way to repair the synchronization of the mbox? Or at least a way to recover its content?

1 0

[Dovecot] 64 bit vs 32 Bit
by Mario Antonio Garcia 03 Jul '09

03 Jul '09

Do you think that there is a substantial performance gain by running Dovecot in a 64 bit Architecture? Regards, Mario Antonio

3 2

[Dovecot] Dovecot Support Added to OSSEC
by Michael Starks 03 Jul '09

03 Jul '09

I have added (beta) Dovecot support for the OSSEC HIDs. It will detect certain attacks and error conditions, and optionally block the attacker (similar to fail2ban). Rather than re-hash the details here, I refer you to the OSSEC mailing list for details on how to install. I would appreciate any feedback either here, there, or privately. The idea is to get a few people trying it so I thought a post here would be good, too.

1 0

[Dovecot] Problem no update maildirsize
by Jose Luis Marin Perez 02 Jul '09

02 Jul '09

Dears Sirs, I've noticed that since the Courier to Dovecot migration have had few problems with the %usage of email accounts as they do not reflect the real use, to fix this I have to manually delete the file maildirsize and run the command vuserinfo user(a)domain.com, depending on your experience may be the cause of this problem? thanks Jose Luis _________________________________________________________________ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

1 1

[Dovecot] about Update Road and no IDLE in CAPABILITY
by kfx 02 Jul '09

02 Jul '09

Hi list, I'm in the path of moving from courier-imap to dovecot and testing it since 1.2-rc3. So far it is very promising. Thank you for your amazing work. So my first question is: what is the recommended update road ? For now, I first "managesieve patch"/compile the source, go on to the old source folder and do a "make uninstall", switch back to the new source folder and do the "make install". As I am using dovecot-sieve and managesieve, the update is a little bit tricky. My second question is how to have the IDLE mode to appear in the server's CAPABILITY announce (without touching imap_capability in the conf ?) I think the IDLE mode is working because when I send me a mail from the server directly in command line like: " echo test | mail -s test my(a)address.com" The mail immediately pop-up in my thunderbird from my workstation. # !tel telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] My Message ------- No IDLE. Details: - Centos 5.3 x86_64 (Selinux in permissive mode) - /proc/sys/fs/inotify/ exist - # rpm -qa | grep gamin gamin-0.1.7-8.el5 gamin-0.1.7-8.el5 gamin-devel-0.1.7-8.el5 gamin-devel-0.1.7-8.el5 - Dovecote 1.2.0 Compilation: $ ./configure --with-ldap=yes --with-notify=inotify Install prefix . : /usr/local File offsets ... : 64bit I/O polling .... : epoll I/O notifys .... : inotify SSL ............ : yes (OpenSSL) GSSAPI ......... : no passdbs ........ : passwd passwd-file shadow checkpassword ldap : -pam -bsdauth -sia -sql -vpopmail userdbs ........ : static prefetch passwd passwd-file checkpassword ldap nss : -sql -vpopmail SQL drivers .... : : -pgsql -mysql -sqlite - # dovecot --version 1.2.0 - # dovecot -n # 1.2.0: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-128.1.10.el5 x86_64 CentOS release 5.3 (Final) ext3 log_path: /var/log/dovecot-error.log info_log_path: /var/log/dovecot-debug.log protocols: imap imaps pop3 pop3s managesieve ssl_ca_file: /etc/pki/CA/chaine.crt ssl_cert_file: /etc/pki/dovecot/certs/server.pem ssl_key_file: /etc/pki/dovecot/private/server.key 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 login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_greeting: My Message verbose_proctitle: yes mail_uid: vmail mail_gid: vmail mail_location: maildir:/var/vmail/%n mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota expire mail_plugins(imap): quota imap_quota expire mail_plugins(pop3): quota expire mail_plugins(managesieve): 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 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): imap_client_workarounds(managesieve): auth default: username_format: %Ln verbose: yes debug: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap-userdb.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: maildir:User quota quota_rule: *:storage=10GB quota_rule2: Trash:storage=10%% expire: Trash 1 Trash/* 1 expire_dict: proxy::expire sieve_dir: /var/sieve-upload/ sieve: /var/sieve-scripts/%u.sieve dict: expire: db:/var/lib/dovecot/expire.db Thank you, kfx

2 2

[Dovecot] dovecot start up messages
by Xueron Nee 02 Jul '09

02 Jul '09

Hi, Why dovecot prints these messages when start up? And how to suppress it? # /home/mail/init/dovecot.init restart Stopping Dovecot: [ OK ] ILoading modules from directory: /home/mail/lib/dovecot/imap IModule loaded: /home/mail/lib/dovecot/imap/lib01_acl_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib02_imap_acl_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib10_quota_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib11_imap_quota_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_autocreate_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_convert_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_expire_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_fts_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_mail_log_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_virtual_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib21_fts_squat_plugin.so IEffective uid=99, gid=99, home=/tmp IQuota root: name=user backend=dict args=:proxy::quota_dict Startting Dovecot: [ OK ] Thanks :) -- Xueron Nee http://www.xueron.com

2 1

[Dovecot] Directory Layout Performance
by Mario Antonio Garcia 02 Jul '09

02 Jul '09

From a performance perspective: Which Directory layout is better: 1. All mailboxes are stored in a single directory and prefixed with a dot or 2. Maildirs using physical directories, such as: Maildir/folder/subfolder/ It looks like the second option -- File Sytem Layout (LAYOUT=fs) -- could spread the load in a better way ...... I do not expect a user reaching maximum number of subfolders in linux , but what about those heavy users with a lot of sub-folders: Is there a significant performance gain by choosing a specific Directory Layout ... Any Comments? Regards, Mario Antonio

4 8

[Dovecot] keeping 2 dovcots in sync?
by joakim＠verona.se 02 Jul '09

02 Jul '09

I would like to have one master dovecot instance that gets email, and a slave dovecot on my laptop. I use maildir, and I was thinking of doing this with unison, but I suppose dovecots indexes would go out of sync whenever I used unison. There seems to be a number of imap folder synchronizers, but I have heard they are troublesome. Any hints? -- Joakim Verona

2 1

[Dovecot] dovecot lda and postfix
by Mauricio Tavares 02 Jul '09

02 Jul '09

I do not know if this is a help request to solve a problem but to understand what is going on. I am going to start with the problem description as I see it and we will go from there. I have postfix setup to use dovecot for tls/sasl in addition to its normal imap/pop3 functions. Postfix is also setup to do virtual domains, getting its information from the files valias, vmaps, and vhosts which are all located in its /etc/postfix directory: # Virtual domain stuff virtual_mailbox_domains = /etc/postfix/vhosts.txt virtual_mailbox_base = /var/spool/vmail virtual_mailbox_maps = hash:/etc/postfix/vmaps.txt # 1500:1500 is user virtual virtual_uid_maps = static:1500 virtual_gid_maps = static:1500 virtual_alias_maps = hash:/etc/postfix/valias.txt Dovecot uses its own unix passwd-like files to do authentication. In fact, as you can see, I broke them apart so I can make the actual password file readable only by root: mail_location = maildir:~/ auth default { passdb passwd-file { args = /etc/dovecot/passwd } userdb passwd-file { args = /etc/dovecot/users } } I know the norm is to use a database or at least ldap, but I had my reasons. Mailscanner is also installed. So, the whay things have been working so far was, postfix receives an email and checks if it is recipient exists here. If so, it would pass it to mailscanner and then get it back, when it would then drop it at the recipient's mailbox in /var/spool/vmail/domain.com/user. A user would then connect to dovecot to retrieve the email. And when an email was to be sent, postfix would use dovecot to do the user authentication. So far so good. Now I want to add dovecot lda so I can run the cmu sieve plugin (this is dovecot 1.0.1) primarily to move emails mailscanner (and spamassassin) thinks that are spam to each virtual user's Spam maildir directory. So, reading http://wiki.dovecot.org/LDA/Sieve/CMU, I add the following entries to dovecot.conf: protocol lda { mail_plugin_dir = /usr/lib/dovecot/modules/lda sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot/auth-master mail_plugins = cmusieve global_script_path = /etc/dovecot/scripts/dovecot.sieve mail_debug = yes log_path = /var/log/dovecot-lda info_log_path = /var/log/dovecot-lda } # I am being rather lazy in my sieve config entry. I did make sure the file # is owned by virtual:virtual plugin { sieve = /etc/dovecot/scripts/dovecot.sieve } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = virtual # User running Dovecot LDA's deliver } # Postfix is using dovecot for SMTP AUTH (SASL) client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } Then, based on http://wiki.dovecot.org/LDA/Postfix, I edit postfix's master.cf: dovecot unix - n n - - pipe flags=DRhu user=virtual:virtual argv=/usr/lib/dovecot/deliver -f ${sender} -d ${user}@${nexthop} and main.cf: dovecot_destination_recipient_limit = 1 virtual_transport = dovecot # mailbox_virtual_domains was already defined as shown above The dovecot.sieve file looks like this: require ["fileinto", "reject"]; # Spam stuff if header :contains "X-Spam-Level" "********************" { discard; stop; } elsif header :contains "X-Spam-Status" "Yes" { fileinto "Spam"; stop; } So, I restart it and try to send a message to my account, say raub(a)domain.com, in this machine. It bounces back saying the user does not exist. I check th elog files and they seem to agree: dovecot: 2009-06-30 16:31:44 Info: auth(default): passwd-file(raub(a)domain.com): lookup: user=raub(a)domain.com file=/etc/dovecot/users dovecot: 2009-06-30 16:31:44 Info: auth(default): passwd-file(raub(a)domain.com): unknown user Now this is where I am trying to understand what is going on. It seems to me that postfix *or* dovecot went to /etc/dovecot/users looking for raub(a)domain.com. Not finding it there (I had it defined there as raub simply; I have mail_location = maildir:~/ in dovecot.conf, so the username in this file does not need to be related to the user's email address), it decided user does not exist and bounced back. My testing indicated that happened after postfix passed the email to dovecot lda (I guess that virtual_transport = dovecot means it goes to master.cf and looks for the dovecot entry and then passes the message to it). That would mean postfix is not using vmaps to see if the user exists anymore. Instead, it is delegating checking if a user exists to dovecot, which is not what I want to do. I want postfix to worry about getting mail and making sure the recipient exists. Out of the blue, if I replaced the virtual_mailbox entry with local_transport = dovecot, or nothing at all, mail is delivered as it should. My gut feeling is the master.cf dovecot entry is responsible for the problem, but I am not sure because I really do not know everything that is going on there; this is the first time I venture in that file. So, could anyone shed some light on what is causing the problem? Thanks!

4 4

[Dovecot] Dovecot / Sieve
by Joan 02 Jul '09

02 Jul '09

Hi, As the "new Sieve implementation" is using a "gratefully stolen copy of deliver.c from dovecot" (i.e. a dirty code in mail-raw.c), would it be possible for the Sieve piece 1 - to be using files from dovecot directly rather than copying&changing it (which is very bad for maintenance) 2 - to be incorporated in the hg/mercurial tree of dovecot ? Thanks a lot in advance, Joan

3 10

[Dovecot] Problem with maildirsize
by Jose Luis Marin Perez 01 Jul '09

01 Jul '09

Dear Timo, I've noticed that since the Courier to Dovecot migration have had few problems with the %usage of email accounts as they do not reflect the real use, to fix this I have to manually delete the file maildirsize and run the command vuserinfo user(a)domain.com, depending on your experience may be the cause of this problem? thanks Jose Luis _________________________________________________________________ Explore the seven wonders of the world http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE

1 0

Re: [Dovecot] antispam patch #2 for Re: v1.2.rc8 released
by Steffen Kaiser 01 Jul '09

01 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 1 Jul 2009, Johannes Berg wrote: > Your patch will break 1.1 though. Er, yes. Attached patch compiles on v1.0 and v1.2. I also forgot <stdlib.h>. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSktVyHWSIuGy1ktrAQJ33Qf/QPkQuo81M1VO4r5iQ9Qa9rzfcx5o/iB3 9qI0PRALY7PP2He3PVusHRqJD7soMeTImwEMAW98XBZ8EUx/h+B3R0nuQatdJLGM /aHR3TAtVjX9zypvqWuzhy8mo/gtkhMEIa0azBYPSbW/Kiswv4bYIZP/gdCEtJ2O /eWeIN1fF7eHvPB18bYGf/edc3xZsELKGZE0oeRx9fcQIQ1pWB2ip3FrnHdSQzr2 SXwoCNw370ZzrFn1feoPpwNDbSdSdozGZgTG37quvS7NsPyDlGBfUkxbHo9ZY06+ CdCwYGJdyvf1gnzTpIzZQDYrQFqahr/GKevhbAIgjb88lYt0B71f6A== =FuX7 -----END PGP SIGNATURE-----

1 0

[Dovecot] short-cut for install prefix in conf file?
by Steffen Kaiser 01 Jul '09

01 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, is there a way to shortcut the absolute path in the dovecot.conf file for the various referenced files? Something like: Now: acl = pgsql:/usr/local/dovecot-1.2.rc8acl-hook2/etc/dovecot-dict-acl-sql.conf mail_executable = \ /usr/local/dovecot-1.2.rc8acl-hook2/libexec/dovecot/rawlog \ /usr/local/dovecot-1.2.rc8acl-hook2/libexec/dovecot/imap Short #1 - relative to dir of conf file acl = pgsql:dovecot-dict-acl-sql.conf mail_executable = ../libexec/dovecot/rawlog ../libexec/dovecot/imap Relative paths are currently evaluated relative to /tmp or '.', it looks like. Because of the different useages of the .conf file, this variant will be troublesome, I guess. Short #2 - use variables as in the shell INSTALL := /usr/local/dovecot-1.2.rc8acl-hook2 acl = pgsql:$INSTALL/etc/dovecot-dict-acl-sql.conf mail_executable = \ $INSTALL/libexec/dovecot/rawlog \ $INSTALL/libexec/dovecot/imap So you need to define the path just one time in the file. Maybe use %$INSTALL instead of $INSTALL, in order to _not_ introduce another metacharacter and break backwards compatibly. Short #3 - pseudo variable (%* here) with modifier (I == installpath) acl = pgsql:%I*/etc/dovecot-dict-acl-sql.conf The background is to support multiple parallel installations, e.g. during testing, I cannot rely on symlinks, but want that all stuff in a conf file is referenced to the same install tree. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSktUoHWSIuGy1ktrAQIMYAf/dfRvO5Q8FitDR6vlSkehjKU+LkZtDv4H 1GjmjBill9Aewuwsb4v8AqNqaoXgsIovQMPZzWGTLzT1MTp36ckOame60PiXFmbZ V7DK6LKR+oeRHVKErwu/iauzj7jmjwAUzPaKd7xavt6UdTw+4MqPFHcg42yjPJAC VF1XQC2l6Wk4rdp/1ijfpkGSYyfzgqXePzjQK8zywyAeZquB90jsfF2cDg07Bhn9 jXTDDPKB7eivEQaWKgTAwKO/vN4BNCaqdhLq20ZHAurP3aXRRbfTk/AZFebDxi5K HU5VO6xfrk8MYE0XU7M91lOi6gwwWvIBMxuEoXAQS4C7NNYFx/JtBA== =T1yk -----END PGP SIGNATURE-----

1 0

[Dovecot] IMAP bandwidth
by Martijn de Munnik 01 Jul '09

01 Jul '09

Hi, I want to calculate the bandwidth usage of the IMAP protocol. POP3 displays a message when the connection is closed about the transfered bytes. In an old mailinglist post I found this message: http://www.dovecot.org/list/dovecot/2007-March/020478.html Is this patch integrated or is there another way to calculate the bandwidth for IMAP connections? Martijn de Munnik -- YoungGuns Kasteleinenkampweg 7b 5222 AX 's-Hertogenbosch T. 073 623 56 40 F. 073 623 56 39 www.youngguns.nl KvK 18076568

3 2

Re: [Dovecot] No folders listed in felamimail
by Jonathan Knight 01 Jul '09

01 Jul '09

dovecot-request(a)dovecot.org wrote: > I thought I try and solve a long standing bug we've had with felamimail > not listing folders from our dovecot server. > Is it bad form to reply to your own postings? I've managed to find the source of the problem and apply a temporary hack to get the folders listed. I'm not sure whether it's a bug or a feature or if there is a proper fix. The issue is that our mail folder layout is still based on "elm" (hands up everyone who remembers that) and we store all the users folders in mbox format under a directory called Mail in their home directory. We've defined a namespace in dovecot called "" which knows to look there and will list all the folders. However, we have run uw-imap in the past so we have a hidden namespace that maps all the folders starting "Mail/" to the new namespace so that we didn't have to change any of the clients. Egroupware has a bunch of code that tries to guess what sort of IMAP server is on the other end based on what folders it can find. One of those checks is for "Mail" and when it finds it it assumes that's the place to go looking for folders rather than using what the Namespace command returned. I'm guessing that this was put in by someone with the same layout as we used to have with "elm" trying to overcome the lack of a configuration file in uw-imap. Our "Mail/" namespace doesn't list any folders and so felamimail can't see anything for the user. My temporary hack was to comment out all the IMAP server guessing code and that fixes the problem for us. Now I need to find out how felamimail deals with IMAP servers that can't have mail folders containing messages and subfolders (it's one or the other with dovecot using mbox) Jon.

1 0

[Dovecot] sieve vacation messages trouble
by Stéphane Cottin 30 Jun '09

30 Jun '09

Hi, sieve vacation replies are rejected by gmail with a "555 5.5.2 Syntax error". The return path is set to "<>", I think this is why this error is triggered by gmail. The rest of the vacation message seems ok. I'm using dovecot 1.1.11 (waiting for final 1.2 to upgrade) , delivering with "/usr/lib/dovecot/deliver -d email@domain" Stéphane Cottin

2 3

[Dovecot] configure dovecot to invoke pam_setcred() from the same process that accesses ~/Maildir?
by Adam Megacz 30 Jun '09

30 Jun '09

Hello. I'm wondering how one would go about configuring dovecot to invoke pam_setcred() from the same process as (or a parent process of) the process which eventually reads the user's mail off the disk. This is required for pam modules that set kernel-level credentials which are later used to access the user's mail files. In particular, I'm trying to use dovecot with pam_krb5 (which associates a ticket cache to a specific pid) and pam_afs_session (which associates tokens to a specific process authentication group -- roughly equivalent to a process and all its descendents). Thanks, - a

2 3

[Dovecot] v1.2.rc8 released
by Timo Sirainen 30 Jun '09

30 Jun '09

http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc8.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc8.tar.gz.sig Last few fixes before tomorrow's v1.2.0 release. Also this release was built in dovecot.org to make sure I can make a usable Dovecot release while not at work/home. :) - Fixed building LDAP as plugin - Fixed starting up in OS X

1 0

[Dovecot] ACLs, imap and launchd
by Axel Luttgens 30 Jun '09

30 Jun '09

I was going to experiment with ACLs when I faced a small problem. It is just sufficient to enable the acl plugin for getting the behavior described hereafter. When launching dovecot from the command line, one gets: sh-3.2# /usr/local/dovecot/sbin/dovecot -F ILoading modules from directory: /usr/local/dovecot-1.2.rc6/lib/ dovecot/imap IModule loaded: /usr/local/dovecot-1.2.rc6/lib/dovecot/imap/ lib01_acl_plugin.so IEffective uid=65534, gid=65534, home=/tmp Iacl: No acl setting - ACLs are disabled ^C In fact, a "dummy" imap process is run so as to fetch the capability (see master-settings.c); that process is run with an hardcoded uid/gid 65534. But this appears to be problematic when dovecot is started from launchd; clearly, launchd doesn't like arbitrary users, as it may be seen from system.log: org.dovecot[28382]: ^AILoading modules from directory: /usr/local/ dovecot-1.2.rc6/lib/dovecot/imap org.dovecot[28382]: ^AIModule loaded: /usr/local/dovecot-1.2.rc6/lib/ dovecot/imap/lib01_acl_plugin.so com.apple.launchd[1] (com.apple.launchd.peruser.65534[28384]): getpwuid("65534") failed com.apple.launchd[1] (com.apple.launchd.peruser.65534[28384]): PID 28383 "imap" has no account to back it! Real/effective/saved UIDs: 65534/65534/65534 com.apple.launchd[1] (com.apple.launchd.peruser.65534[28384]): Exited with exit code: 1 com.apple.launchd[1] (com.apple.launchd.peruser.65534): Throttling respawn: Will start in 10 seconds com.apple.launchd[1] (org.dovecot[28382]): Stray process with PGID equal to this dead job: PID 28383 PPID 1 imap com.apple.launchd[1] (org.dovecot[28382]): Exited abnormally: Alarm clock com.apple.launchd[1] (org.dovecot): Throttling respawn: Will start in 5 seconds com.apple.launchd[1] (com.apple.launchd.peruser.65534[28386]): getpwuid("65534") failed com.apple.launchd[1] (com.apple.launchd.peruser.65534[28386]): Exited with exit code: 1 com.apple.launchd[1] (com.apple.launchd.peruser.65534): Throttling respawn: Will start in 10 seconds ... and so on ... A workaround is to create the corresponding system user and group; launchd then doesn't complain anymore and everything seems to be working fine. But I feel somewhat uncomfortable with that... Wouldn't it be possible, for example, to consider using a system user such as "nobody" (unless I'm wrong, it should be defined on any unix flavor)? TIA, Axel sh-3.2# /usr/local/dovecot/sbin/dovecot -n # 1.2.rc6: /usr/local/etc/dovecot.conf # OS: Darwin 9.7.0 i386 protocols: pop3 imap ssl: no disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/dovecot-1.2.rc6/libexec/dovecot/ imap-login login_executable(imap): /usr/local/dovecot-1.2.rc6/libexec/dovecot/ imap-login login_executable(pop3): /usr/local/dovecot-1.2.rc6/libexec/dovecot/ pop3-login first_valid_uid: 2001 last_valid_uid: 65533 mail_location: mbox:~/_mailboxes:INBOX=~/_mailboxes/inbox mail_debug: yes mbox_read_locks: flock mbox_write_locks: flock dotlock mail_executable(default): /usr/local/dovecot-1.2.rc6/libexec/dovecot/ imap mail_executable(imap): /usr/local/dovecot-1.2.rc6/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot-1.2.rc6/libexec/dovecot/pop3 mail_plugins(default): acl mail_plugins(imap): acl mail_plugins(pop3): mail_plugin_dir(default): /usr/local/dovecot-1.2.rc6/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot-1.2.rc6/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot-1.2.rc6/lib/dovecot/pop3 pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: debug: yes passdb: driver: pam args: * userdb: driver: passwd

2 4

Re: [Dovecot] Under POP attack - now to prevent?
by James Brown 30 Jun '09

30 Jun '09

On 05/06/2009, at 4:19 PM, James Brown wrote: > > Thanks to Curtis and others who replied. > > I managed to block the IP at our Firewall (learnt a few quirky > things about Astaro Security Gateway on the way!) > > In order to automate the process, Fail2Ban has been suggested. I > know this is getting a bit off topic, but has anyone installed in > Mac OS X 10.5.7? There is a how-to for 10.4 ( HOWTO Mac OS X Server > (10.4) - Fail2ban )- does this work unchanged in 10.5? > > Anyone managed to get Fail2Ban working on Leopard with Dovecot 1.2 > RC4? I'll answer my own question! There is a OS X Installer file at: LSA Mac OS X Ported and Developed Software | LSA Information Technology | University of Michigan Any regex experts out there that can help me set up Fail2Ban to stop this? Jun 5 11:48:20 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<audrey>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:24 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<august>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:24 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<autumn>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:25 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<austin>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:27 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<audrey>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:28 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<autumn>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:30 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<august>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:31 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<autumn>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Many thanks, James.

2 1

[Dovecot] No folders listed in felamimail
by Jonathan Knight 30 Jun '09

30 Jun '09

Egroupware 1.4.004 I thought I try and solve a long standing bug we've had with felamimail not listing folders from our dovecot server. Watching dovecot's packet dumps I'm seeing dovecot do a namespace call and the a list call. Felamimail does a namespace and gets back * NAMESPACE (("" "/")) NIL NIL which is how I've configured dovecot to keep the client configuration very simple. Now Felamimail does a LIST "" "" which gets no folders returned and is obviously why it won't show anything in the felamimail display. I was expecting felamimail to do something more like: LIST "" "%" or LIST "" "*" Is there something I need to configure to make felamimail happy with our dovecot configuration? We use dovecot with outlook express, thunderbird (1,2,3), Mozilla, squirrelmail, iPod, iPhone and symbian with no issues so I'm tending towards felamimail being the source of the problem. Jon.

1 0

[Dovecot] Location of sieve_global_dir setting
by Rainer Frey 30 Jun '09

30 Jun '09

Hi, I'm a bit confused by the Wiki. Do the settings "sieve_dir" and "sieve_global_dir" belong to the lda or the plugin section (Dovecot 1.1.11)? Thanks Rainer

2 1

[Dovecot] SSL / TLS
by Carlos Williams 30 Jun '09

30 Jun '09

I am running Postfix and Dovecot on my mail server. I am required now to have SSL/TLS on my mail server. I did check and found out that I have a SSL certificate with Verisign issued to my mail servers FQDN. Now my question is when reading the Dovecot Wiki, I noticed it said that it is not common to use SSL but rather TLS on most mail servers. Even though SSL will work, which should I use on my server? We already have a purchased SSL certificate but does that really matter? Should I simply just revoke that certificate & use TLS instead? So when I read this link: http://wiki.dovecot.org/SSL/DovecotConfiguration Is it talking about a actual SSL certificate or TLS? Thanks for any clarification! - Carlos

8 12

[Dovecot] Users with large (4GB) inboxes crippling dovecot
by robforrest 30 Jun '09

30 Jun '09

Hi all, I'm new here and would very much appreciate any help you can give me. We are running a rather outdated mail server that until recently has been running beautifully. Under the pretense of "it is ain't broke, don't fix it" it hasn't been updated so is running Fedora Core 4 and dovecot v0.99.14. What is happening is that as users log in (via thunderbird), they are shown the contents of their mailboxes. However, when they try and access a given email, they get no response even if they wait upwards of 10 minutes. I believe that the problem has arisen from their huge inboxes, several users have inboxes in excess of 4GB. Do any of you know how I could split these large mbox files down in to manageable chunks of 1GB? Please be aware that I only have remote access to the server over a modest internet connection. Thanks again for any suggestions. Rob -- View this message in context: http://www.nabble.com/Users-with-large-%284GB%29-inboxes-crippling-dovecot-… Sent from the Dovecot mailing list archive at Nabble.com.

16 28

[Dovecot] Recommended Groupware?
by it-dovecot＠ml.epigenomics.com 29 Jun '09

29 Jun '09

Hi, is there a recommended groupware (email + calendar + address book + syncing with mobile devices) on top of an existing dovecot installation? Most existing commercially supported groupwares come with their own mail storage engine. I would like to keep dovecot as the email storage engine because of the maildir format which greatly helps with backup & restore. Regards -- Robert Sander

3 2

[Dovecot] Dovecot Expire doesn't work
by Stef Simoens 29 Jun '09

29 Jun '09

Hello, I'm using dovecot and I want to use the "expire" plugin. However, it doesn't work, i.e. mails do not get deleted. I ran `/usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool --test` and besides printing Info: stef/Trash: no messages left Info: stef/Spam: no messages left it doesn't do anything (especially not deleting e-mails). Obviously, in stef/Trash and stef/Spam, there are e-mails waiting to be deleted. I'm using dbox as mail storage; and use dbox:/var/mail/%u as mail_location in dovecot.conf. Furthermore, I'm running 1.1.16 on a gentoo PPC system. This is the output from `dovecot -n` # 1.1.16: /etc/dovecot/dovecot.conf # OS: Linux 2.6.29-gentoo-r2 ppc Gentoo Base System release 1.12.11.1 xfs listen: *, [::] ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login verbose_proctitle: yes mail_privileged_group: mail mail_location: dbox:/var/mail/%u mail_plugins: expire auth default: verbose: yes debug: yes passdb: driver: pam args: * userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: fs:Disk Quota expire: Trash 7 Spam 30 expire_dict: proxy::expire dict: expire: db:/var/lib/dovecot/expire.db A strace on `/usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool --test` shows the following output: mkdir("/var/mail/root", 0770) = -1 EEXIST (File exists) stat64("/var/mail/root/Trash/dbox-Mails", 0xbfda2708) = -1 ENOENT (No such file or directory) write(2, "Info: stef/Trash: no messages lef"..., 35Info: stef/Trash: no messages left ) = 35 which explains why nothing happens (stat64("/var/mail/root/Trash/dbox-Mails", which is empty, it should not even exist, but it passes by a mkdir), but why does it want to check /var/mail/root and not /var/mail/%u (i.e. why no stat64(/var/mail/stef/Trash/dbox-Mails))? Thanks for your help and kind regards, -- Stef Simoens

4 14

[Dovecot] LDAP Plugin fails to build in 1.2.rc7
by Paul Howarth 29 Jun '09

29 Jun '09

Hi, The LDAP Plugin fails to build (it doesn't attempt to build it) in 1.2.rc7 because $have_ldap_plugin is checked before it's assigned in configure.in. Patch attached. This was not a problem in 1.2.rc6 and earlier versions. Cheers, Paul.

2 1

[Dovecot] v1.2.rc7 released
by Timo Sirainen 29 Jun '09

29 Jun '09

http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc7.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc7.tar.gz.sig I'll make RC releases daily now until v1.2.0 is released, which will be either on Monday or Wednesday. Please test as much as possible. * Removed configure --with-deliver, --with-pop3d and --disable-ipv6 parameters. + Improved permission related error messages. - mbox: Don't write garbage to mbox if message doesn't have a body. - virtual: Fixed saving messages with keywords. - virtual: Fixed infinite looping bug. - zlib: Fixed error handling.

3 3

[Dovecot] Dovecot v1.2rc6 deliver to shared folder fails
by Steffen Kaiser 29 Jun '09

29 Jun '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, out of curiosity I tested to deliver into a shared folder of another owner using Sieve. (Not that I intend to do so, but well ... ) Conf is attached. == Script require ["fileinto"]; fileinto "shared.testusr.test1.test2.test3"; == Dovecot logs: Jun 22 15:36:22 ux-2s11standby dovecot: deliver(user): acl vfile: file /home/testusr/test1/test2/test3/Maildir/dovecot-acl not found Jun 22 15:36:22 ux-2s11standby dovecot: deliver(user): Namespace shared.testusr/test1/test2/test3.: Permission lookup failed from /home/testusr/test1/test2/test3/Maildir Jun 22 15:36:22 ux-2s11standby dovecot: deliver(user): Namespace shared.testusr/test1/test2/test3.: Using permissions from /home/testusr/test1/test2/test3/Maildir: mode=0700 gid=-1 Jun 22 15:36:22 ux-2s11standby dovecot: deliver(user): dovecot-acl-list creation failed: safe_mkstemp(/home/testusr/test1/test2/test3/Maildir/temp.ux-2s11standby.25681.e8eb63ed74ac1dd2) failed: No such file or directory Jun 22 15:36:22 ux-2s11standby dovecot: deliver(user): sieve: msgid=<200906221336.n5MDaMGr025671(a)ux-2s11standby.inf.fh-bonn-rhein-sieg.de>: failed to store into mailbox 'testusr/test1/test2/test3': BUG: Unknown internal error Jun 22 15:36:22 ux-2s11standby dovecot: deliver(user): sieve: execution of script /home/user/.dovecot.sieve failed, but implicit keep was successful == LIST excerpt of user: * LIST (\Noselect \HasChildren) "." "shared.testusr" * LIST (\HasNoChildren) "." "shared.testusr.test1.test2.test3" * LIST (\HasNoChildren) "." "shared.testusr.INBOX" ACL of testusr: 4 getacl test1.test2.test3 * ACL "test1.test2.test3" "user" kxeilprwtscd "testusr" lrwstipekxacd Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSj+MBHWSIuGy1ktrAQJBeggApjdThbPJwgTfDyxhSfirUfT56HmxMqFi zsLuHZvNqdY+lQ/cQh9q9gal3UwAbtdcG7f6UgT5p6FZfx87l08DOoLw8j0C3CPC EG3Dk5aAsljLwlbcI5g06hSv8qwydI9ij16nybxEcVMUwtYXALzLtpHSOh/bYr/y +GrvyGTi3wfRom4+guoXa3t6+Wjk8MBvz4aF+JdK691sivQGvhPEUwQsG3e2emSa iOyBguCTtzvYMy18j9PitqspunPPrXaypi+6HzjgYz02T0qo7TZWRyxkCwc6/S2H NEkXLgkjg1ao6uGa9svJvQkK5fl2mfjZXidjL1hGZBLeVWCcnCWVLg== =08gf -----END PGP SIGNATURE-----

2 2

[Dovecot] automated email setup and white/blacklists
by Mediawire - Alistair Campion 29 Jun '09

29 Jun '09

We are running a Red Hat Enterprise Linux environment with Dovecot IIMAP, Exim and mySQL 5.0.81, Apache 2.2.11 We are looking for several server side scripts: 1. Create a user account automatically at the completion of our registration process. i.e. username(a)ourdomain.com and existing MD5 password that is associated with his/her user account 2. Add a new user to an existing subscriber email whitelist (add buddy function) 3. Add an existing user to an existing subscriber email blacklist (block buddy function) Our preference is to receive access to a publicly available scripts. Alternatively, to come to a commercial arrangement with a party who has written or who is prepared to write the same. Regards Alistair Campion mediawirelogo_sm3 Voice : +61 411-148-400 Email: <mailto:alistair@txtbuddies.com> alistair(a)mediawire.tv Web: <http://www.buddirewards.com> www.buddirewards.com Web: <http://www.txtbuddies.com/> www.txtbuddies.com Web: <http://www.myofficebuddies.com> www.myofficebuddies.com

2 1

[Dovecot] sievec error: "fileinto require missing"
by Braden McDaniel 29 Jun '09

29 Jun '09

I'm getting this error when compiling .dovecot.sieve: $ /usr/libexec/dovecot/sievec .dovecot.sieve .dovecot.sievec Info: line 3: fileinto require missing Unable to parse script: script errors: line 3: fileinto require missing .dovecot.sieve just looks like this: $ cat .dovecot.sieve if header :contains ["List-Id"] ["dovecot.dovecot.org"] { fileinto "INBOX.dovecot"; stop; } I'm probably doing something silly; but I don't see how what I've done differs significantly from examples I've found. And googling for "fileinto require missing" just got me to the sievec source code. What might be the problem here? -- Braden McDaniel <braden(a)endoframe.com>

2 2

[Dovecot] 1.2rc5 Panic: file virtual-sync.c
by e-frog 28 Jun '09

28 Jun '09

mail.log: Jun 6 14:40:19 server dovecot: IMAP(user): Panic: file virtual-sync.c: line 502 (virtual_sync_mailbox_box_remove): assertion failed: (rec_count >= uid_count) Jun 6 14:40:19 server dovecot: IMAP(user): Raw backtrace: imap [0x80f0d21] -> imap [0x80f0da2] -> imap [0x80f06d9] -> /usr/lib/dovecot/modules/imap/lib20_virtual_plugin.so [0xb7ec36b4] -> /usr/lib/dovecot/modules/imap/lib20_virtual_plugin.so [0xb7ec4c7b] -> /usr/lib/dovecot/modules/imap/lib20_virtual_plugin.so(virtual_storage_sync_init+0x634) [0xb7ec5dc4] -> imap(imap_sync_init+0x54) [0x806fff4] -> imap(cmd_sync_delayed+0x24b) [0x807031b] -> imap(client_handle_input+0x1bc) [0x80679ac] -> imap(client_input+0x5f) [0x806817f] -> imap(io_loop_handler_run+0xe0) [0x80f99d0] -> imap(io_loop_run+0x20) [0x80f8e50] -> imap(main+0x5f5) [0x8070b85] -> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7ef8775] -> imap [0x805ff91] Jun 6 14:40:19 server dovecot: dovecot: child 13847 (imap) killed with signal 6 (core dumped) backtrace: GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... warning: Can't read pathname for load map: Input/output error. Reading symbols from /lib/tls/i686/cmov/libdl.so.2...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/libdl-2.9.so...done. done. Loaded symbols for /lib/tls/i686/cmov/libdl.so.2 Reading symbols from /lib/tls/i686/cmov/libc.so.6...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/libc-2.9.so...done. done. Loaded symbols for /lib/tls/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.9.so...done. done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so...done. Loaded symbols for /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so Reading symbols from /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so...done. Loaded symbols for /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so Reading symbols from /usr/lib/dovecot/modules/imap/lib20_expire_plugin.so...done. Loaded symbols for /usr/lib/dovecot/modules/imap/lib20_expire_plugin.so Reading symbols from /usr/lib/dovecot/modules/imap/lib20_fts_plugin.so...done. Loaded symbols for /usr/lib/dovecot/modules/imap/lib20_fts_plugin.so Reading symbols from /usr/lib/dovecot/modules/imap/lib20_virtual_plugin.so...done. Loaded symbols for /usr/lib/dovecot/modules/imap/lib20_virtual_plugin.so Reading symbols from /usr/lib/dovecot/modules/imap/lib21_fts_squat_plugin.so...done. Loaded symbols for /usr/lib/dovecot/modules/imap/lib21_fts_squat_plugin.so Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Core was generated by `imap [user 192.168.178.41]'. Program terminated with signal 6, Aborted. [New process 13847] #0 0xb8053424 in __kernel_vsyscall () (gdb) bt full #0 0xb8053424 in __kernel_vsyscall () No symbol table info available. #1 0xb7f0d6d0 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 resultvar = <value optimized out> pid = -1207693324 selftid = 13847 #2 0xb7f0f098 in *__GI_abort () at abort.c:88 act = {__sigaction_handler = {sa_handler = 0x935ee68, sa_sigaction = 0x935ee68}, sa_mask = {__val = {3215393416, 135195514, 3087272224, 0, 3215393536, 3215393524, 512, 0, 0, 3215393600, 3087472240, 134566395, 692, 0, 0, 0, 1, 135267902, 512, 1, 3215393524, 154529352, 69, 3215393652, 3215393496, 135197110, 154530076, 3215393524, 3215393528, 693, 154529384, 3086704259}}, sa_flags = 693, sa_restorer = 0x81062e9 <write_full+57>} sigs = {__val = {32, 0 <repeats 31 times>}} #3 0x080f0d35 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:160 backtrace = 0x935ea38 "imap [0x80f0d21] -> imap [0x80f0da2] -> imap [0x80f06d9] -> /usr/lib/dovecot/modules/imap/lib20_virtual_plugin.so [0xb7ec36b4] -> /usr/lib/dovecot/modules/imap/lib20_virtual_plugin.so [0xb7ec4c7b] -> "... #4 0x080f0da2 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0xb7ec6ab8 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfa703d4 "ap¦¦\001") at failures.c:440 No locals. #5 0x080f06d9 in i_panic (format=0xb7ec6ab8 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:207 No locals. #6 0xb7ec36b4 in virtual_sync_mailbox_box_remove (ctx=0x9632340, bbox=0x9374248, removed_uids=0x937427c) at virtual-sync.c:516 i = 3215393848 src = 0 dest = 135275874 uid = 154526136 vseq = 28 __PRETTY_FUNCTION__ = "virtual_sync_mailbox_box_remove" #7 0xb7ec4c7b in virtual_sync_backend_boxes (ctx=0x9632340) at virtual-sync.c:850 _data_stack_cur_id = 3 i = 10 ret = 0 #8 0xb7ec5dc4 in virtual_storage_sync_init (box=0x9373ba8, flags=MAILBOX_SYNC_FLAG_EXPUNGE) at virtual-sync.c:1445 sync_ctx = <value optimized out> ret = <value optimized out> #9 0x0806fff4 in imap_sync_init (client=0x936b188, box=0x9373ba8, imap_flags=IMAP_SYNC_FLAG_SAFE, flags=MAILBOX_SYNC_FLAG_EXPUNGE) at imap-sync.c:146 ctx = (struct imap_sync_context *) 0x958ff78 __PRETTY_FUNCTION__ = "imap_sync_init" #10 0x0807031b in cmd_sync_delayed (client=0x936b188) at imap-sync.c:579 cmd = <value optimized out> first_expunge = <value optimized out> first_nonexpunge = <value optimized out> __PRETTY_FUNCTION__ = "cmd_sync_delayed" #11 0x080679ac in client_handle_input (client=0x936b188) at client.c:724 ret = false remove_io = false handled_commands = true __PRETTY_FUNCTION__ = "client_handle_input" #12 0x0806817f in client_input (client=0x936b188) at client.c:748 ---Type <return> to continue, or q <return> to quit--- cmd = <value optimized out> output = (struct ostream *) 0x936b33c bytes = <value optimized out> __PRETTY_FUNCTION__ = "client_input" #13 0x080f99d0 in io_loop_handler_run (ioloop=0x93669b0) at ioloop-epoll.c:208 ctx = (struct ioloop_handler_context *) 0x9366ab8 event = (const struct epoll_event *) 0x9366af8 list = (struct io_list *) 0x936b3c0 io = (struct io_file *) 0x936b398 tv = {tv_sec = 4, tv_usec = 187729} t_id = 2 msecs = <value optimized out> ret = 1 i = 0 j = 0 call = <value optimized out> #14 0x080f8e50 in io_loop_run (ioloop=0x93669b0) at ioloop.c:338 No locals. #15 0x08070b85 in main (argc=Cannot access memory at address 0x3617 ) at main.c:323 No locals.

2 6

Re: [Dovecot] Lots of pop3-logins
by V S Rao 28 Jun '09

28 Jun '09

> > > Doing a "ps aux" on my Slackware box, I have approx 100 PID's of "pop3-login's going on. This is a production mail server, but it is getting VERY low traffic. In fact, only 3 people can "pop3" into it. I've check their e-mail clients, and they are not checking mail any more often than every 5 minutes. > > > > > > This is a new installation and I've had the server up and running since Sunday. If it matters, I'm using Postfix for the MTA and using the Dovecot SASL library to AUTH SMTP. > > > > > > Is this a cause for concern? Why does Dovecot need this many processes? > > > > > > > >> Because dovecot preforks the *-login processes to speed-up the login. > > > > >> No need to worry. > > > > 100 login sessions for just 3 connections? That is not right, no matter what. > > >> No, login_processes_count matters. > > How? If my understanding is correct, you have extra 3 login processes created to cater to new connections. So with only 3 POP3 users, why should so many login processes be spawned? I can understand 10-15. But 100 definitely indicates either the processes are not dying or something else happening on the system which is causing such high number of login processes. The system definitely needs to be checked for some kind of attack, a rogue process running on the system or something else. > >> My idle box has 64 imap-login processes and no, I'm not under a >> dictionary attack :) I am not sure what your load is (user base, system config etc), but I will give you my typical load here. I run mail server for about 6000 users with a mix of 70% POP3 and 30% IMAP (thro webmail). And here are the typical stats (I run a script in the background collecting this data every 5 secs): pop3-logins:12 pop3-connections:8 IMAP-logins:7 IMAP-connections:11 I have read other opinions in this thread by Timo & others. And I am interested in a few things. So if you will indulge me, maybe it will be useful for others who face these kind of issues Timo Wrote: You can also just decrease login_process_max_count Wouldn't decreasing the login_process_max_count simply create more problems. Now users will start experiencing timeouts sooner than before, because whatever is causing the login processes to increase (attack, rogue process or whatever) will *always* be trying to login and genuine users will be denied login. So without knowing the root cause of the issue simply decreasing or increasing the login_process_max_count will lead to other problems. Correct me if I am wrong. Rodman Wrote: I'll go ahead and lower that limit to something that fits my usage better. No, I think leave that value to default and try and identify the root cause and prevent it. Noel Wrote: What would be nice is, an anti brute force option Yes, that would be nice. But consider a situation where the system is not under brute force attack, but for some reason the number of login processes keep on increasing by the hour. This would ultimately lead the system to deny connections to the users. Is there a way to track what is happening? strace would be too complicated for us field guys to work with. Any suggestions? Regards --Rao

4 4

[Dovecot] Dovecot v1.2 ACL inheritance for new subfolders (aka copying ACLs)
by Steffen Kaiser 28 Jun '09

28 Jun '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, http://wiki.dovecot.org/ACL mentions: "Currently there is no ACL inheritance." However this applies to a folder inherit ACLs to existing subfolders; when you share a folder and a non-owner creates a sub-folder within, no ACLs are set, hence, the creator cannot access the new folder. Could the "create mailbox"-process copy the ACLs to the sub-folder? Actually, I would like most, if this is done regardless if owner or non-owner creates subfolders. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSj+FVnWSIuGy1ktrAQI81Af/aBOtllnFl1IP1RRMOri75cayXMWkiPkS GWKrZaK4vISUqL0yN0mSCMvP4sESwTndIn6kel3ZYqEDFrYWuhg+wAQx8XGxAfgs W1vsnlbPcQ6U02dtC7pGqhaFc8ZomLEFrO5xmDd+DEPTSqBiJzOz6C6mg7diqIuq Tmd0oGDqrP4shKt5y3oSM5tZSELnpQD2+J636JROlxvtuYgVti9M+DSPSjU3PRDs oS7eMUf9mmOt4BAUzWmq4mNda8NBFcDK3L70Lu5r1/maheEIcrDAlMmRTTtlShq8 FM2zXey5sLGMyuRhhlQmaefxuvYQosblbpGYlf6K71tKNPBzdFeR2A== =3pmt -----END PGP SIGNATURE-----

2 1

[Dovecot] bzip2 compression bug
by fernando＠dfcom.com.br 28 Jun '09

28 Jun '09

Hi, I compressed many files using bzip2, but in some cases it crashes. I believe that it is related to dovecot indexes. How to reproduce: Inside a Maildir folder without any indexes yet, compress a message with bzip2 and tryes to access it. At my server is showed the error: Jun 24 00:18:20 maildev dovecot: IMAP(xxx@xxx): FETCH for mailbox Trash UID 1 failed to read message input: No such file or directory Jun 24 00:18:20 maildev dovecot: IMAP(xxx@xxx): Disconnected: BUG: Unknown internal error bytes=329/1050 When I did the same with gzip compression it works as expected (opening the message and creating dovecot indexes). (version, 1.1.16) Best Regards, Fernando

3 2

[Dovecot] Dovecot v1.2rc6 dict-server socket path problem & pgsql crash
by Steffen Kaiser 28 Jun '09

28 Jun '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I find this in the logs: 2009-06-25 14:10:37 IMAP(dvtest) [29566]: Error: net_connect_unix(/usr/local/dovecot-1.2.rc6acl-hook2/var/run/dovecot/dict-server) failed: Permission denied 2009-06-25 14:10:37 IMAP(dvtest) [29566]: Error: acl: dict iteration failed, can't update dict although base_dir is just /var/run/dovecot/ . Dovecot v1.2 changeset: 9157:d14e8b8df025 Conf is attached. I am trying to get ACL's shared dictionary running: acl_shared_dict: proxy::acl dict: acl: pgsql:/usr/local/dovecot-1.2.rc6acl-hook2/etc/dovecot-dict-acl-sql.conf ============ I created the symlink to get map /var/run/dovecot under $install_dir, then I get a crash: 2009-06-25 14:26:53 dict: Error: pgsql: Connect failed to dovecot: could not open certificate file "/root/.postgresql/postgresql.crt": No such file or directory ==> /var/log/postgresql/postgresql-8.1-main.log <== 2009-06-25 14:26:53 CEST LOG: could not accept SSL connection: peer did not return a certificate ==> /var/log/dovecot/dovecot-1.2.log <== 2009-06-25 14:26:58 dict: Error: pgsql: Connect failed to dovecot: could not open certificate file "/root/.postgresql/postgresql.crt": No such file or directory ==> /var/log/postgresql/postgresql-8.1-main.log <== 2009-06-25 14:26:58 CEST LOG: could not accept SSL connection: peer did not return a certificate ==> /var/log/dovecot/dovecot-1.2.log <== 2009-06-25 14:27:03 dict: Error: dict sql iterate failed: Not connected to database 2009-06-25 14:27:03 IMAP(dvtest) [29801]: Error: read(/usr/local/dovecot-1.2.rc6acl-hook2/var/run/dovecot/dict-server) failed: Remote disconnected 2009-06-25 14:27:03 IMAP(dvtest) [29801]: Error: acl: dict commit failed 2009-06-25 14:27:03 dovecot: Error: child 29802 (dict) killed with signal 11 (core dumps disabled) My sql-dict.conf is: connect = host=localhost dbname=dovecot user=dovecot # password=pass [CUT samples for quota & expire] # CREATE TABLE user_shares ( # from_user varchar(100) not null, # to_user varchar(100) not null, # primary key (from_user, to_user) # ); map { pattern = shared/shared-boxes/user/$to/$from table = user_shares fields { from_user = $from to_user = $to } } ================== So I changed the connect line into: connect = dbname=dovecot user=dovecot into forcing to use the local socket, which seems to work: 2009-06-25 14:37:24 dict: Info: pgsql: Connected to dovecot but: 2009-06-25 14:37:24 dovecot: Error: child 29986 (dict) killed with signal 11 (core dumped) 2009-06-25 14:37:24 IMAP(dvtest) [29985]: Error: read(/usr/local/dovecot-1.2.rc6acl-hook2/var/run/dovecot/dict-server) failed: Remote disconnected 2009-06-25 14:37:24 IMAP(dvtest) [29985]: Error: acl: dict commit failed ==> /var/log/postgresql/postgresql-8.1-main.log <== 2009-06-25 14:37:24 CEST LOG: unexpected EOF on client connection The core's bt full of this latter crash is: Core was generated by `dict'. Program terminated with signal 11, Segmentation fault. #0 0xb7ebe463 in strlen () from /lib/tls/i686/cmov/libc.so.6 (gdb) bt full #0 0xb7ebe463 in strlen () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #1 0x08065072 in str_append (str=0x806c168, cstr=0x0) at str.c:91 No locals. #2 0x080509ef in sql_dict_set_query (build=0xbffe8c34) at dict-sql.c:536 dict = (struct sql_dict *) 0x8076e08 sql_fields = <value optimized out> extra_values = <value optimized out> i = 0 prefix = (string_t *) 0x806c168 suffix = (string_t *) 0x806c1d8 __PRETTY_FUNCTION__ = "sql_dict_set_query" #3 0x080518a4 in sql_dict_set (_ctx=0x8080028, key=0x806c032 "shared/shared-boxes/user/dvtest2/dvtest", value=0x806c05a "1") at dict-sql.c:648 build = {dict = 0x8076e08, fields = {arr = {buffer = 0x806c130, element_size = 8}, v = 0x806c130, v_modifiable = 0x806c130}, extra_values = 0xbffe8c50, key1 = 115 's', inc = false} field = {map = 0x8076ed8, value = 0x806c05a "1"} query = <value optimized out> _data_stack_cur_id = 4 ctx = <value optimized out> dict = <value optimized out> map = <value optimized out> values = {arr = {buffer = 0x806c0f0, element_size = 4}, v = 0x806c0f0, v_modifiable = 0x806c0f0} #4 0x08052460 in dict_set (ctx=0x8080028, key=0x806c032 "shared/shared-boxes/user/dvtest2/dvtest", value=0x806c05a "1") at dict.c:168 __PRETTY_FUNCTION__ = "dict_set" #5 0x0804f355 in cmd_set (conn=0x8075bc8, line=0x8075df8 "2\tshared/shared-boxes/user/dvtest2/dvtest\t1") at dict-server.c:288 trans = (struct dict_server_transaction *) 0x8080118 #6 0x0804fbf9 in dict_client_connection_input (conn=0x8075bc8) at dict-server.c:458 _data_stack_cur_id = 3 line = 0x8075df7 "S2\tshared/shared-boxes/user/dvtest2/dvtest\t1" i = 6 ret = <value optimized out> #7 0x0805e2d0 in io_loop_handler_run (ioloop=0x8074a38) at ioloop-epoll.c:208 ctx = <value optimized out> event = (const struct epoll_event *) 0x8074b80 list = (struct io_list *) 0x8075da8 io = (struct io_file *) 0x8075d80 tv = {tv_sec = 2147483, tv_usec = 0} t_id = 2 msecs = <value optimized out> ret = 1 i = 0 j = 0 call = <value optimized out> #8 0x0805d398 in io_loop_run (ioloop=0x8074a38) at ioloop.c:338 No locals. #9 0x0805002f in main () at main.c:129 No locals. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSkNxwXWSIuGy1ktrAQKuyAgAn8NU8Y59qGV75VStW2MZQH/7HWLF2z9y 2L41g+NzX5LEw9o/B2ZjlAVEsNhVbqbew2A57uuvOAgV5K8iGgx1yPUjmQT9ud6X uthcsBNQIVGu6ymCN2ufeh3XdNEkrOu1pLJaWkiVQjvc8FOczMp432Jhytc9Hpbo jtMbnFuSbZmg0GX6bqJ50kOsjwme7B7ak/ubVeOwGXHU4MQ8PRXl+TXdVTlnFwKw IUZj8xPB+Gi7nRdsJlkQItp//TgeAJ9lm+i/OWzH420qljADDs9NfrfKd/DDOo6i u6W6I+5FUsJ5N7CHDAvHeDnTHPomPC+bnYAWpRyXF/kMVPaccaFxQw== =O2WZ -----END PGP SIGNATURE-----

2 2

[Dovecot] [PATCH] allow disabling libcap support although it's installed
by Daniel Mierswa 28 Jun '09

28 Jun '09

see subject :) patch is in hg export format -- Mierswa, Daniel If you still don't like it, that's ok: that's why I'm boss. I simply know better than you do. --- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22 # HG changeset patch # User Daniel Mierswa <impulze(a)impulze.org> # Date 1245757676 -7200 # Branch HEAD # Node ID 343390a32894c654c8646650eba2cf130ca480d2 # Parent d77225a6412873528b3c94abe8268436df5dbe82 do not automagically depend on libcap if it's installed diff --git a/configure.in b/configure.in --- a/configure.in +++ b/configure.in @@ -196,6 +196,11 @@ TEST_WITH(bzlib, $withval), want_bzlib=auto) +AC_ARG_WITH(libcap, +[ --with-libcap Build with libcap support (Dropping capabilities).], + TEST_WITH(libcap, $withval), + want_libcap=auto) + AC_ARG_WITH(ssl, [ --with-ssl=gnutls|openssl Build with GNUTLS or OpenSSL (default)], if test x$withval = xno; then @@ -358,11 +363,13 @@ AC_DEFINE(HAVE_FDATASYNC,, Define if you have fdatasync()) ]) -AC_CHECK_LIB(cap, cap_init, [ - AC_DEFINE(HAVE_LIBCAP,, libcap is installed for cap_init()) - LIBCAP="-lcap" -]) -AC_SUBST(LIBCAP) +if test $want_libcap != no; then + AC_CHECK_LIB(cap, cap_init, [ + AC_DEFINE(HAVE_LIBCAP,, libcap is installed for cap_init()) + LIBCAP="-lcap" + ]) + AC_SUBST(LIBCAP) +fi AC_DEFINE(PACKAGE_WEBPAGE, "http://www.dovecot.org/", Support URL)

2 2

[Dovecot] strange quota behaviour with dovecot 1.1.7
by listacc＠gmx.de 28 Jun '09

28 Jun '09

Hello! I´m running dovecot 1.1.7 (which is the most recent binary of openSuSE 11.1 repository) with Postfix, MySQL and Postfixadmin. Now I´m trying for some days to get quota working, but I get some strange behaviour and I was not yet able to figure out where the error in my configuration is. Quota information is inserted by postfixadmin into a MySQL database. It seems that dovecot is reading this information correctly - when a mailbox is filled up and gets over-quota, further emails are rejected. But then, if I want to increase the quota for this filled-up mailbox in postfixadmin, postfixadmin correctly changes the quota information in MySQL table. After growing quota, mails to the account are accepted again. But my Thunderbird with Quota plugin continues showing the old quota setting. When more mails are sent to this account, it shows a quota > 100%. If I look into the "mailboxsize" file of this account, it still shows the old quota value before I raised it. If I delete the entry in mailboxsize, dovecot writes the old value in again. Seems that dovecot isn´t looking in the MySQL table (but it did after creating the account). But why are mails accepted again if dovecot is not recognizing the raised quota?? If I try now, as a user, to delete mails from the "overfilled" Inbox, it is denied with a "quota exceeded" message. But I´m able to send further mails to this account. The only way to get the account working properly again is to delete the messages directly on the server´s filesystem. I´m very grateful for every hint! regards, Andreas ------------- dovecot -n: # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.23-0.1-default x86_64 openSUSE 11.1 (x86_64) ext3 base_dir: /drbd/mail/var/run/dovecot/ log_path: /var/log/dovecot.err info_log_path: /var/log/dovecot.info protocols: imaps managesieve listen(default): * listen(imap): * listen(managesieve): 192.168.1.8:2000 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(managesieve): ssl_cert_file: /etc/ssl/certs/imap.domain.crt ssl_key_file: /etc/ssl/private/imap.domain.key verbose_ssl: yes login_dir: /drbd/mail/var/run/dovecot//login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login max_mail_processes: 2000 mail_max_userip_connections(default): 30 mail_max_userip_connections(imap): 30 mail_max_userip_connections(managesieve): 10 first_valid_uid: 5001 last_valid_uid: 5001 mail_location: maildir:/drbd/mail/vmail/%d/%n mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib64/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib64/dovecot/modules/managesieve managesieve_implementation_string(default): dovecot managesieve_implementation_string(imap): dovecot managesieve_implementation_string(managesieve): Cyrus timsieved v2.2.13 sieve_storage(default): sieve_storage(imap): sieve_storage(managesieve): /drbd/mail/vmail/%d/%n/sieve sieve(default): sieve(imap): sieve(managesieve): /drbd/mail/vmail/%d/%n/dovecot.sieve auth default: mechanisms: plain login cram-md5 user: nobody verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail plugin: sieve: /drbd/mail/vmail/%d/%n/dovecot.sieve quota: maildir --- dovecot-sql.conf: (...) password_query = SELECT username AS user, password, '/drbd/mail/vmail/%d/%n' AS userdb_home, 'maildir:/drbd/mail/vmail/%d/%n' AS userdb_mail, 5001 AS userdb_uid, 5001 AS userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' (...) user_query = SELECT '/drbd/mail/vmail/%d/%n' AS home, 'maildir:/drbd/mail/vmail/%d/%n' AS mail, 5001 AS uid, 5001 AS gid, concat('*:storage=', quota, 'B') AS quota_rule FROM mailbox WHERE username = '%u' AND active = '1' --- mysql> select quota from mailbox; +-----------+ | quota | +-----------+ | 512000000 | | 512000000 | | 512000000 | | 512000000 | | 512000000 | | 512000000 | | 512000000 | | 512000000 | | 512000000 | | 30720000 | | 30720000 | +-----------+ 11 rows in set (0.00 sec) -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Dovecot] POP3 flag updates
by Timo Sirainen 28 Jun '09

28 Jun '09

Why does Dovecot add \Seen flag for mails that have been RETRed? Does anyone really want to use this feature? I can't remember why I implemented it originally, perhaps it was just "because other servers do that too". I'm thinking about at least changing pop3_no_flag_updates=yes to be default. There's also of course pop3_enable_last setting to enable LAST command which was removed from POP3 specs. That requires knowing the last RETRed mail, so I guess I should add a check that it can't be enabled without pop3_no_flag_updates=no.

2 2

[Dovecot] Spliting Folders for Efficiency
by Daniel Watts 28 Jun '09

28 Jun '09

Dear Timo, Would there be any sense in giving Dovecot the option to split folders into multiple subfolders when they reached a specified size (probably message count) limit? Dovecot would monitor folders and when they reached, say, 10,000 messages, silently split the folder on the filesystem to ensure that access remains fast. I know that Dovecot scales very well but this would give practically unlimited storage capability and also keep things fast. You could even have it so that the latest 100 messages are kept in their own folder for fast access. .Folder.new .Folder.cur .Folder.tmp could become: .Folder__1.new .Folder__1.cur .Folder__1.tmp and .Folder__2.new .Folder__2.cur .Folder__2.tmp with Dovecot merging them before display as just "Folder" within the mail client. This could be further extended so that Dovecot could be configured to store 'old' message folders in a separate location. We could then have slower+cheaper+larger storage mounted so that 'old mail' does not take up the expensive local SCSI disks on the machine. Mail from 2 years ago is much less likely to be accessed than mail from the last week. This would provide very neat behind-the-scenes archiving functionality. Looking forward to hearing your thoughts. Best, Daniel -- Squirrelmail Stable 1.4.8 (and developing on 1.5.2) PHP 5.x Hardened with Eaccelerator Apache 2.x Mysql 5.0.x Imapproxy over Dovecot 1.0.rc27 with Maildir all running on Gentoo Linux for ~5,000 users.

7 11

[Dovecot] Sieve/ManageSieve integration into pkgsrc
by Edgar Fuß 28 Jun '09

28 Jun '09

I'm integrating Sieve (the new one) and ManageSieve into wip/dovecot. Currently, this works as dovecot options because dovecot must be built before sieve can be configured and sieve must be built before managesieve can be configured/built. Now, the question arose what the long-term solution (in pkgsrc) should be. To my understanding, with dovecot 2.0, ManageSieve will no longer need to patch dovecot. But what about both Sieve and ManageSieve depending on doevcot sources in order to build (or on libraries dovecot only builds internally)? The preferred way (for pkgsrc) would be if both Sieve and ManageSieve could be built as stand-alone packages and not needing a dovecot source tree to build. What's the long-term plan for Sieve/ManageSieve in this respect? The pkgsrc infrastructure (intentionally) doesn't like a package depending on anothers package working directory in order to build. So with these cross-dependencies, the only pkgsrc ways to go would be either to build it all as one package with options (that's what I currently do) or extract, patch, configure and build dovecot inside a sieve package.

3 2

[Dovecot] dovecot and vmailmgr/qmail mailboxes
by Mij 26 Jun '09

26 Jun '09

Hello folks, Time ago I worked on a patch for dovecot to work with vmailmgr http://mij.oltrelinux.com/net/dovecot-qmail-vmailmgr/ The patch was required because, despite vmailmgr complies with the checkpassword interface supported by dovecot, dovecot snips the mailbox directory returned by the authentication module at colon characters ':'. Incidentally, vmailmgr maps any "name.surname@domain" to "~domain/users/name:surname" (a standard practice in the qmail world, see eg http://www.qmail.org/man/man5/dot-qmail.html at "For security") This path dovecot would then parse as "~domain/users/name". An authentication module can't do anything about it, as this is due to dovecot collecting accounting information in one common buffer, tokenized by ':' separators. I soon stopped updating the patch because I didn't see much point in running indefinitely after releases. However, a bunch of people wrote me over the last years asking for details or updates. Partially for having a similar requirement myself, partially drafted by such feedback, I recently wrote a "compromise" wrapper solution (attached). It does not require patching dovecot (external module) and it's thus (supposedly) durable across dovecot releases; however, it cannot help with the colon problem. The wrapper works as follows: 1) compile and install: # cc -O2 -Wall -o checkvpw-dovecot-wrapper checkvpw-dovecot-wrapper.c # install -s -o root checkvpw-dovecot-wrapper /usr/local/bin 2) edit dovecot.conf, setup the auth section as follows: ============ auth default { mechanism = plain passdb checkpassword { args = /usr/local/bin/checkvpw-dovecot-wrapper } userdb prefetch { } user = root } ============ If "name.surname@domain" wants to be created, the administrator shall instead create the user "namesurname@domain" and an alias "name.surname@domain" pointing to it. This may be conceivable for new installations, but it is not for scenarios where dovecot is to replace another server on top of an existing user base. Of course, it's very desirable to support "." users too. I see that it would require several changes in the code, but I'd like to hear your opinion on this. What about - using a different separator than ":", less common and safer. Could '\0' be one? If not, what about '*'? - as a quicker & dirtier solution, what about allowing escaping? One can modify the auth module to replace ":" with "\:", if dovecot is instructed to avoid tokenizing when a "\" precedes a ":". - as an alternative, dovecot may require the module to chdir() to the mailbox directory instead of returning its path as a string, and subsequently operate locally on mailbox-relative paths. I can't guess how compatible this is with the current design. In the next days, I will publish such wrapper to the webpage. For your convenience, I will invite interested users to show up on this thread; this should help you in assessing how this is interesting for people. bye

4 7