- dovecot - dovecot.org

[Dovecot] TLS timeout with 1.2a4
by Luigi Rosa 09 Jan '09

09 Jan '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a mail server CentOS 64bit (4 Gb RAM) with Dovecot 1.2a4 and three accounts. I use Thunderbird 2. If I enable SSL connection in Thunderbird 2, after three-five minutes I got a lot of different errors in Thunderbird (Server is not IMAP, Connection lost...). Everything comes back to normal if I restart Dovecot in the server, but after 5 minutes I got the same errors. This happens both with an ADSL connection (Thunderbird on Windows XP) AND with a direct 1 Gbit cross cable connection (Thunderbird on Ubuntu 64 8.10). If I disable SSL connection on Thunderbird, everything comes back to normal and I don't get any error. The SSL-related options in dovecot.conf are: ssl_disable = no ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem ssl_parameters_regenerate = 47 verbose_ssl = yes ssl_cipher_list = ALL:!LOW disable_plaintext_auth = no What kind of logging can I enable to trace this error? On the logfile I find something like taht (there are only 3 seconds between the first and the last line) dovecot: imap-login: Login: user=<lists(a)aaa.com>, method=CRAM-MD5, rip=xxx, lip=yyy, TLS dovecot: imap-login: Login: user=<lists(a)aaa.com>, method=CRAM-MD5, rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (auth failed, 1 attempts): method=CRAM-MD5, rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (no auth attempts): rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (no auth attempts): rip=xxx, lip=yyy, TLS handshaking dovecot: imap-login: Disconnected: Shutting down (no auth attempts): rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (no auth attempts): rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (no auth attempts): rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (auth failed, 1 attempts): method=CRAM-MD5, rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (no auth attempts): rip=xxx, lip=yyy, TLS handshaking dovecot: imap-login: Disconnected: Shutting down (no auth attempts): rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (auth failed, 1 attempts): method=CRAM-MD5, rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (auth failed, 1 attempts): method=CRAM-MD5, rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (auth failed, 1 attempts): method=CRAM-MD5, rip=xxx, lip=yyy, TLS dovecot: imap-login: Disconnected: Shutting down (no auth attempts): rip=xxx, lip=yyy, TLS dovecot: IMAP(lrosa(a)bbb.com): Disconnected: Logged out bytes=1028/49877 dovecot: IMAP(lrosa(a)bbb.com): Disconnected: Logged out bytes=2253/49352 dovecot: IMAP(lrosa(a)bbb.com): Connection closed bytes=20466/553071 dovecot: IMAP(lrosa(a)bbb.com): Connection closed bytes=19417/163412 dovecot: IMAP(lrosa(a)bbb.com): Disconnected: Logged out bytes=2937/69241 dovecot: imap-login: Login: user=<lrosa(a)bbb.com>, method=CRAM-MD5, rip=xxx, lip=yyy dovecot: imap-login: Login: user=<lists(a)aaa.com>, method=CRAM-MD5, rip=xxx, lip=yyy, TLS dovecot: imap-login: Login: user=<lrosa(a)bbb.com>, method=CRAM-MD5, rip=xxx, lip=yyy dovecot: imap-login: Login: user=<lrosa(a)bbb.com>, method=CRAM-MD5, rip=xxx, lip=yyy dovecot: imap-login: Login: user=<lists(a)aaa.com>, method=CRAM-MD5, rip=xxx, lip=yyy, TLS dovecot: imap-login: Login: user=<lrosa(a)bbb.com>, method=CRAM-MD5, rip=xxx, lip=yyy dovecot: imap-login: Login: user=<lists(a)aaa.com>, method=CRAM-MD5, rip=xxx, lip=yyy, TLS dovecot: imap-login: Login: user=<lrosa(a)bbb.com>, method=CRAM-MD5, rip=xxx, lip=yyy dovecot: IMAP(lrosa(a)bbb.com): Connection closed bytes=205/41166 dovecot: IMAP(lrosa(a)bbb.com): Connection closed bytes=609/217506 dovecot: imap-login: Login: user=<lrosa(a)bbb.com>, method=CRAM-MD5, rip=xxx, lip=yyy Ciao, luigi - -- / +--[Luigi Rosa]-- \ Fallo oggi, domani potrebbe essere illegale. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklBUKAACgkQ3kWu7Tfl6ZSQgwCbBoD6IEKjPNYriHrKmES4Zj+y ji0AnRZzU2ETJkVn72kmpR1C+cs3PNdf =T267 -----END PGP SIGNATURE-----

2 2

[Dovecot] dovecot 1.1.3: File attachment truncated after moving the message into another folder
by Christoph.Jakobs＠t-online.de 09 Jan '09

09 Jan '09

Sometimes file attachments are truncated after moving the message from one folder to another. # 1.1.3: /usr/local/etc/dovecot.conf ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 200 mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u imap_client_workarounds: delay-newmail auth default: passdb: driver: shadow args: blocking=yes userdb: driver: passwd

2 1

[Dovecot] verbose_proctitle not working with post-login
by Frank Elsner 09 Jan '09

09 Jan '09

Happy Xmas, when using a post-login procedure the "verbose_proctitle = yes" has no effect. If it is feature then please explain else please fix the bug fi --Frank Elsner

2 2

[Dovecot] Unknown quota backend / imap dump-capability process returned 89
by Frank Elsner 09 Jan '09

09 Jan '09

Hi all, I want to use maildir++ quota with dovecot but when starting I get: > service dovecot start Starting IMAP-Service (dovecot 1.1.7) ILoading modules from directory: /usr/dovecot/lib/dovecot/imap IModule loaded: /usr/dovecot/lib/dovecot/imap/lib10_quota_plugin.so IModule loaded: /usr/dovecot/lib/dovecot/imap/lib11_imap_quota_plugin.so IModule loaded: /usr/dovecot/lib/dovecot/imap/lib20_mail_log_plugin.so IEffective uid=65534, gid=65534, home=/tmp FUnknown quota backend: 0 Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /usr/local/dovecot/etc/dovecot.conf > dovecot -n # 1.1.7: /usr/local/dovecot/etc/dovecot.conf # OS: Linux 2.6.27 i686 Fedora Core release 6 (Zod) ext3 base_dir: /var/run/dovecot/ ssl_cert_file: /usr/local/etc/seymour.crt ssl_key_file: /usr/local/etc/seymour.key disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/dovecot/libexec/dovecot/imap-login login_greeting: c64.shuttle.de - Dovecot ready. login_log_format_elements: %u %r %c mail_max_userip_connections: 25 verbose_proctitle: yes first_valid_uid: 100 last_valid_uid: 65534 mail_location: maildir:/var/mail/%u:INDEX=MEMORY mail_debug: yes maildir_copy_preserve_filename: yes mail_executable: /usr/dovecot/libexec/dovecot/imap-quota mail_plugins: mail_log quota imap_quota mail_plugin_dir: /usr/dovecot/lib/dovecot/imap mail_log_prefix: %Us(%u,%r): mail_log_max_lines_per_sec: 0 imap_client_workarounds: netscape-eoh tb-extra-mailbox-sep imap_logout_format: [%i/%o] auth default: executable: /usr/dovecot/libexec/dovecot/dovecot-auth master_user_separator: / count: 2 passdb: driver: pam args: dovecot passdb: driver: passwd-file args: /usr/dovecot/etc/masters userdb: driver: passwd plugin: quota: maildir:INBOX mail_log_events: delete undelete expunge copy mailbox_delete The "mail_executable: /usr/dovecot/libexec/dovecot/imap-quota" currently reads: | #!/bin/sh | | /usr/bin/logger -p mail.info -t dovecot "imap-quota: Starting for $USER" | | exec /usr/dovecot/libexec/dovecot/imap In the future this procedure will provide QUOTA_RULESs per usr. Any pointers welcome. --Frank Elsner

2 2

[Dovecot] Master user with "user="?
by Alan Ferrency 09 Jan '09

09 Jan '09

Hello, In our configuration, we are using a "passdb passwd-file", with "user=" directives in each username, and a separate "userdb passwd-file" which contains the target usernames for the "user=" directives. This works fine, for normal logins via POP and IMAP. For customer support testing purposes, we also set up a temporary "master=yes" passwd-file. This works fine, for any passdb username that does not have a "user=" field. However, it seems that if we use the master user to log into a username that is in the passdb with a "user=" field, dovecot looks in the userdb for the original username, and not for the "user=" username specified in the passdb passwd-file. Is this a known bug? Maybe I'm doing something wrong? Thanks! Alan Ferrency pair Networks, Inc. alan(a)pair.com

2 4

[Dovecot] Debian packages for dovecot 1.1.x
by Seth Mattinen 09 Jan '09

09 Jan '09

Because I'm tired of seeing Debian users look like idiots for using such horribly out of date versions just because they run "stable", I've set up a page with .deb packages of my 1.1.x rebuilds for use under lenny. http://www.rollernet.us/opensource/ Standard disclaimer applies: use at your own risk, no warranty, no support, if it eats your first born or erases your computer I don't want to hear about it. ;) -- Seth Mattinen sethm(a)rollernet.us Roller Network LLC

3 8

[Dovecot] deliver & per user log file
by Marcin Rzepecki 09 Jan '09

09 Jan '09

Hello, is there a way to log Dovecot deliver actions in user home directory like procmail did (e.g. in ~/Mail/deliver.log)? Greetings, -- Marcin Rzepecki m.rzepecki(at)iem.pw.edu.pl

4 8

[Dovecot] apply Sieve filter to existing mails
by Jakob Grießmann 09 Jan '09

09 Jan '09

Hello, is it possible to apply Sieve filter to existing mails, e.g. for testing purposes whether my rules work as expected? Thanks, Jakob

1 0

[Dovecot] Error: dict: Failed to initialize dictionary 'expire'
by LÉVAI Dániel 09 Jan '09

09 Jan '09

Hi! Using dovecot-1.1.17, and BDB-4.6.21. I'm having this error in every two weeks or so. I've running this in a crontab: /usr/local/sbin/dovecot --exec-mail \ ext /usr/local/libexec/dovecot/expire-tool The expire plugin and tool is working fine, the configuration is ok, and I'm using the BDB backend. What happens in every ~two weeks is dovecot starts to give me this error messages: Error: dict: db_env: Unable to allocate memory for transaction detail Error: dict: Failed to initialize dictionary 'expire' Reading thru Oracle's Berkeley DB FAQ: http://www.oracle.com/technology/products/berkeley-db/faq/db_faq.html#28 "This error means the maximum number of active transactions configured for Berkeley DB has been reached [...] When all of the memory available in the database environment for transactions is in use, calls to being a transaction will fail until some active transactions complete. By default, the database environment is configured to support at least 20 active transactions." What could be happening here? Why coudn't it finish its transactions? After a dovecot restart it works fine :\ Thanks in advance for any hints. Daniel -- LEVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1

2 4

[Dovecot] assert with zlib and (maybe) fts
by Matthias Rieber 09 Jan '09

09 Jan '09

Hi, I compressed a folder with the following script: ... for i in *.*.*; do file $i | grep bzip2 >/dev/null 2>&1 if [ $? -ne 0 ]; then echo "Compress: $i" cat "$i" | bzip2 -9 > ../tmp/$i if [ $? -eq 0 ]; then mv ../tmp/$i $i fi else echo "Alread DONE: $i"; fi done ... it works mostly, but there seems to be at leas one messages that cause a problem, during syncing the whole folder or performing a search, I get an assert: @40000000494044a53ae8e4fc dovecot: Info: auth(default): new auth connection: pid=24651 @40000000494044dd09e0bd6c dovecot: Error: IMAP(matthias): read(mail, uid=8235) failed: Invalid argument @40000000494044dd0b155d3c dovecot: Error: IMAP(matthias): *** glibc detected *** imap: free(): invalid next size (normal): 0x099995f8 *** @40000000494044dd0b4f12ac dovecot: Error: IMAP(matthias): ======= Backtrace: ========= @40000000494044dd0b4f1a7c dovecot: Error: IMAP(matthias): /lib/libc.so.6[0xb7eea815] @40000000494044dd0b4f1e64 dovecot: Error: IMAP(matthias): /lib/libc.so.6(cfree+0x9c)[0xb7eec6bc] @40000000494044dd0b4f2634 dovecot: Error: IMAP(matthias): /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so[0xb7fc3e04] @40000000494044dd0b4f2a1c dovecot: Error: IMAP(matthias): imap(io_stream_unref+0x40)[0x80eb290] @40000000494044dd0b4f2e04 dovecot: Error: IMAP(matthias): imap(i_stream_unref+0x1c)[0x80dc2cc] @40000000494044dd0b4f83f4 dovecot: Error: IMAP(matthias): imap(index_mail_close+0x6b)[0x809ad6b] @40000000494044dd0b4f87dc dovecot: Error: IMAP(matthias): imap[0x8098dc8] @40000000494044dd0b4f8bc4 dovecot: Error: IMAP(matthias): imap(index_mail_set_seq+0x40)[0x80991f0] @40000000494044dd0b4f8fac dovecot: Error: IMAP(matthias): imap(index_storage_search_next_nonblock+0xef)[0x809d2ef] @40000000494044dd0b4f9394 dovecot: Error: IMAP(matthias): /usr/local/lib/dovecot/imap/lib20_fts_plugin.so[0xb7e7cd6e] @40000000494044dd0b4fa71c dovecot: Error: IMAP(matthias): imap[0x8060a36] @40000000494044dd0b4fab04 dovecot: Error: IMAP(matthias): imap[0x8060e86] @40000000494044dd0b4faeec dovecot: Error: IMAP(matthias): imap(io_loop_handle_timeouts+0xe9)[0x80de919] @40000000494044dd0b4fb2d4 dovecot: Error: IMAP(matthias): imap(io_loop_handler_run+0x82)[0x80df1d2] @40000000494044dd0b4fd5fc dovecot: Error: IMAP(matthias): imap(io_loop_run+0x20)[0x80de6c0] @40000000494044dd0b4fd9e4 dovecot: Error: IMAP(matthias): imap(main+0x46a)[0x806b67a] @40000000494044dd0b4fddcc dovecot: Error: IMAP(matthias): /lib/libc.so.6(__libc_start_main+0xe5)[0xb7e96455] @40000000494044dd0b4fe59c dovecot: Error: IMAP(matthias): imap[0x805cac1] @40000000494044dd0b4fe984 dovecot: Error: IMAP(matthias): ======= Memory map: ======== @40000000494044dd0b50917c dovecot: Error: IMAP(matthias): 08048000-08101000 r-xp 00000000 fd:0b 1541448 /usr/local/libexec/dovecot/imap @40000000494044dd0b50994c dovecot: Error: IMAP(matthias): 08101000-08107000 rwxp 000b9000 fd:0b 1541448 /usr/local/libexec/dovecot/imap @40000000494044dd0b509d34 dovecot: Error: IMAP(matthias): 08107000-09ae3000 rwxp 08107000 00:00 0 [heap] @40000000494044dd0b50a11c dovecot: Error: IMAP(matthias): b7163000-b7928000 rwxs 00000000 fd:0b 508303 /home/matthias/Maildir/REMOVED/dovecot.index.search.uids @40000000494044dd0b50c05c dovecot: Error: IMAP(matthias): b7928000-b79ea000 rwxp b7928000 00:00 0 @40000000494044dd0b50c444 dovecot: Error: IMAP(matthias): b7a22000-b7a63000 rwxp b7a22000 00:00 0 @40000000494044dd0b50c82c dovecot: Error: IMAP(matthias): b7a63000-b7a81000 r-xs 00000000 fd:0b 508302 /home/matthias/Maildir/REMOVED/dovecot.index.cache @40000000494044dd0b50f324 dovecot: Error: IMAP(matthias): b7c00000-b7c21000 rwxp b7c00000 00:00 0 @40000000494044dd0b50f70c dovecot: Error: IMAP(matthias): b7c21000-b7d00000 ---p b7c21000 00:00 0 @40000000494044dd0b50faf4 dovecot: Error: IMAP(matthias): b7dde000-b7dea000 r-xp 00000000 fd:0b 1655254 /lib/libgcc_s.so.1 @40000000494044dd0b511264 dovecot: Error: IMAP(matthias): b7dea000-b7deb000 rwxp 0000b000 fd:0b 1655254 /lib/libgcc_s.so.1 @40000000494044dd0b511a34 dovecot: Error: IMAP(matthias): b7df0000-b7df7000 r-xs 00000000 fd:0b 1477936 /usr/lib/gconv/gconv-modules.cache @40000000494044dd0b511e1c dovecot: Error: IMAP(matthias): b7df7000-b7e0d000 rwxp 00000000 fd:0b 508359 /home/matthias/Maildir/REMOVED/dovecot.index @40000000494044dd0b513974 dovecot: Error: IMAP(matthias): b7e0d000-b7e16000 r-xp 00000000 fd:0b 1655734 /lib/libnss_files-2.7.so @40000000494044dd0b513d5c dovecot: Error: IMAP(matthias): b7e16000-b7e18000 rwxp 00008000 fd:0b 1655734 /lib/libnss_files-2.7.so @40000000494044dd0b51452c dovecot: Error: IMAP(matthias): b7e18000-b7e20000 r-xp 00000000 fd:0b 1655736 /lib/libnss_nis-2.7.so @40000000494044dd0b516c3c dovecot: Error: IMAP(matthias): b7e20000-b7e22000 rwxp 00007000 fd:0b 1655736 /lib/libnss_nis-2.7.so @40000000494044dd0b517024 dovecot: Error: IMAP(matthias): b7e22000-b7e35000 r-xp 00000000 fd:0b 1655731 /lib/libnsl-2.7.so @40000000494044dd0b51740c dovecot: Error: IMAP(matthias): b7e35000-b7e37000 rwxp 00012000 fd:0b 1655731 /lib/libnsl-2.7.so @40000000494044dd0b517bdc dovecot: Error: IMAP(matthias): b7e37000-b7e39000 rwxp b7e37000 00:00 0 @40000000494044dd0b51934c dovecot: Error: IMAP(matthias): b7e39000-b7e40000 r-xp 00000000 fd:0b 1655732 /lib/libnss_compat-2.7.so @40000000494044dd0b519b1c dovecot: Error: IMAP(matthias): b7e40000-b7e42000 rwxp 00006000 fd:0b 1655732 /lib/libnss_compat-2.7.so @40000000494044dd0b519f04 dovecot: Error: IMAP(matthias): b7e42000-b7e4e000 r-xp 00000000 fd:0b 1541765 /usr/local/lib/dovecot/lib21_fts_squat_plugin.so @40000000494044dd0b51ba5c dovecot: Error: IMAP(matthias): b7e4e000-b7e4f000 rwxp 0000c000 fd:0b 1541765 /usr/local/lib/dovecot/lib21_fts_squat_plugin.so @40000000494044dd0b51be44 dovecot: Error: IMAP(matthias): b7e4f000-b7e5e000 r-xp 00000000 fd:0b 1655094 /lib/libbz2.so.1.0.4 @40000000494044dd0b51c614 dovecot: Error: IMAP(matthias): b7e5e000-b7e5f000 rwxp 0000f000 fd:0b 1655094 /lib/libbz2.so.1.0.4 @40000000494044dd0b51e93c dovecot: Error: IMAP(matthias): b7e5f000-b7e73000 r-xp 00000000 fd:0b 1476476 /usr/lib/libz.so.1.2.3.3 @40000000494044dd0b51f10c dovecot: Error: IMAP(matthias): b7e73000-b7e74000 rwxp 00013000 fd:0b 1476476 /usr/lib/libz.so.1.2.3.3 @40000000494044dd0b51f4f4 dovecot: Error: IMAP(matthias): b7e76000-b7e77000 r-xp 00000000 fd:0b 1487847 /usr/lib/gconv/ISO8859-1.so @40000000494044dd0b524ae4 dovecot: Error: IMAP(matthias): b7e77000-b7e79000 rwxp 00001000 fd:0b 1487847 /usr/lib/gconv/ISO8859-1.so @40000000494044dd0b5252b4 dovecot: Error: IMAP(matthias): b7e79000-b7e7e000 r-xp 00000000 fd:0b 1541764 /usr/local/lib/dovecot/lib20_fts_plugin.so @40000000494044dd0b52569c dovecot: Error: IMAP(matthias): b7e7e000-b7e7f000 rwxp 00004000 fd:0b 1541764 /usr/local/lib/dovecot/lib20_fts_plugin.so @40000000494044dd0b5271f4 dovecot: Error: IMAP(matthias): b7e7f000-b7e80000 rwxp b7e7f000 00:00 0 @40000000494044dd0b5275dc dovecot: Error: IMAP(matthias): b7e80000-b7fb8000 r-xp 00000000 fd:0b 1655725 /lib/libc-2.7.so @40000000494044dd0b5279c4 dovecot: Error: IMAP(matthias): b7fb8000-b7fb9000 r-xp 00138000 fd:0b 1655725 /lib/libc-2.7.so @40000000494044dd0b528194 dovecot: Error: IMAP(matthias): b7fb9000-b7fbb000 rwxp 00139000 fd:0b 1655725 /lib/libc-2.7.so @40000000494044dd0b52a8a4 dovecot: Error: IMAP(matthias): b7fbb000-b7fbe000 rwxp b7fbb000 00:00 0 @40000000494044dd0b52ac8c dovecot: Error: IMAP(matthias): b7fbe000-b7fc0000 r-xp 00000000 fd:0b 1655728 /lib/libdl-2.7.so @40000000494044dd0b52b074 dovecot: Error: IMAP(matthias): b7fc0000-b7fc2000 rwxp 00001000 fd:0b 1655728 /lib/libdl-2.7.so @40000000494044dd0b52b45c dovecot: Error: IMAP(matthias): b7fc3000-b7fc6000 r-xp 00000000 fd:0b 1541911 /usr/local/lib/dovecot/lib20_zlib_plugin.so @40000000494044dd0b52cfb4 dovecot: Error: IMAP(matthias): b7fc6000-b7fc7000 rwxp 00002000 fd:0b 1541911 /usr/local/lib/dovecot/lib20_zlib_plugin.so @40000000494044dd0b52d784 dovecot: Error: IMAP(matthias): b7fc7000-b7fc9000 rwxp b7fc7000 00:00 0 @40000000494044dd0b52db6c dovecot: Error: IMAP(matthias): b7fc9000-b7fca000 r-xp b7fc9000 00:00 0 [vdso] @40000000494044dd0b52f2dc dovecot: Error: IMAP(matthias): b7fca000-b7fe4000 r-xp 00000000 fd:0b 1655345 /lib/ld-2.7.so @40000000494044dd0b52f6c4 dovecot: Error: IMAP(matthias): b7fe4000-b7fe6000 rwxp 0001a000 fd:0b 1655345 /lib/ld-2.7.so @40000000494044dd0b52fe94 dovecot: Error: IMAP(matthias): bf8c0000-bf8d5000 rw-p bf8c0000 00:00 0 [stack] @40000000494044dd0b5321bc dovecot: Error: child 24572 (imap) killed with signal 6 It's dovecot 1.1.7 on Debian Lenny in linux-vserver(x86). If you guys need more information let me know. matthias

4 5

[Dovecot] expire plugin with pgsql not working
by LÉVAI Dániel 09 Jan '09

09 Jan '09

Hi! I've configured dovecot, and created the db/table/trigger according to http://wiki.dovecot.org/Quota/Dict. I'm using dovecot-1.1.7 and pgsql. When moving a message inside the "monitored" directory, the expires table won't get updated because of an error: statement: INSERT INTO expires (expire_stamp, mailbox) VALUES ('1229993423', 'leva/spamassassin.SPAM') INSERT ERROR: null value in column "username" violates not-null constraint Wonder why doesn't dovecot pass the username too. What could be the problem? Daniel -- LEVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1

2 4

[Dovecot] Sudden, large numbers of "Timeout while waiting for lock for transaction log ..."
by Jack Stewart 09 Jan '09

09 Jan '09

Hi, Up until yesterday, our environment which consists an NFS maildir file store with multiple front end servers, was working fine. We've verified that the server clocks and machines clocks are in sync. Starting yesterday afternoon, We are getting ~850 log entries of the form 'Timeout while waiting for lock for transaction log files' or 'Our dotlock file was modified, assuming it wasn't overridden (kept it 180 sec) Based on packet capture, just one of these index files shows 28553 GETATTRs queries in in a one minute. At this happened at exactly the same time on all of our servers, it is pretty clear that the back-end system (or network) is a major factor although nobody will confess that they made any changes. It would be helpful, and very appreciated, to get more information about what this might be so that we can nudge the correct people to undo whatever it is that they didn't do. We are running currently dovecot 1.1.3 an 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Timeout while waiting for lock for transaction log file /var/spool/dovecot/indexes/z/zabala/.INBOX/dovecot.index.log Jan 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Our dotlock file /var/spool/maildir/z/zabala/dovecot-uidlist.lock was deleted (kept it 180 secs) Jan 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Timeout while waiting for lock for transaction log file /var/spool/dovecot/indexes/z/zabala/.INBOX/dovecot.index.log Jan 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Our dotlock file /var/spool/maildir/z/zabala/dovecot-uidlist.lock was modified (1231233482 vs 1231233662), assuming it wasn't overridden (kept it 180 secs) Jan 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Timeout while waiting for lock for transaction log file /var/spool/dovecot/indexes/z/zabala/.INBOX/dovecot.index.log Jan 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Our dotlock file /var/spool/maildir/z/zabala/dovecot-uidlist.lock was modified (1231233482 vs 1231233662), assuming it wasn't overridden (kept it 180 secs) Jan 6 01:21:04 fire-griffen dovecot: IMAP(sukwon): Timeout while waiting for lock for transaction log file /var/spool/dovecot/indexes/s/sukwon/.Trash/dovecot.index.log -- Jack Stewart Academic Computing Services, IMSS, California Institute of Technology jstewart(a)caltech.edu 626-395-4690 office

2 5

[Dovecot] Enforcing TLS
by Ed Schouten 09 Jan '09

09 Jan '09

Hello all, I've happily been using Dovecot for a couple of years now, but only a couple of days ago I configured it to speak both TLS and SSL for both POP3 and IMAP. Ideally I want users to use TLS, but I've enabled SSL, because some mailers (at least Apple Mail on OS X Tiger) don't support TLS. Right now I'm in sort of a transitional phase, where I'm asking users to enable TLS in their email clients, if not enabled already. After a couple of weeks/months I want to disable any (non-local) connections that don't use TLS or SSL. I already asked on IRC whether this was possible, because I was unable to find this on the Wiki. It turns out there is a configuration switch called `disable_plaintext_auth', but looking at the description this only prevents people from using plain-text username/password authentication. It does not actually enforce TLS or SSL. My question: is there support to enforce TLS when people connect to non-SSL ports? If someone comes up with a solution, I'll add it to the SSL article on the Wiki. I'm using Dovecot 1.1.7, installed on a FreeBSD 6.4-STABLE system. Thanks! -- Ed Schouten <ed(a)80386.nl> WWW: http://80386.nl/

5 8

[Dovecot] Restoring individual messages from a backup into a Maildir setup?
by Thomas Harold 09 Jan '09

09 Jan '09

We have a user who deleted IMAP folders from his account, so I simply tried to restore the folder ".FolderName" from our backup. I checked that file/folder ownership was the same as the original, but the Dovecot IMAP server is throwing errors at the client. I've tried copying the individual message files from the "cur" folders in the backup directory, but Dovecot immediate goes into panic mode and throws errors at the IMAP client when I do that. Even if the file is owned by the currect UID. I've tried putting those files into "tmp" and "new" as well, with no luck. I looked at the following thread, but it didn't help. http://www.dovecot.org/list/dovecot/2007-August/024971.html The thread from Sep 2008 wasn't much help either: http://www.mail-archive.com/dovecot@dovecot.org/msg12846.html ... Eh, I figured this out before I even posted. Restoration is indeed that simple. The problem is that the files were not labeled with the proper SELinux security context after being restored. When the file was restored, it was assigned a context of "root:object_r:file_t", which is not a context that the Dovecot service has permissions to interact with. I had to re-label the files after restoring them with # chcon -R user_u:object_r:mail_spool_t foldername So the lesson here is to check /var/log/messages and look for sealert indicators when restoring files. ... Hopefully that helps some other people out when dealing with Red Hat / CentOS with SELinux set to enforcing mode.

3 7

[Dovecot] dovecot-auth Temporary But Frequent CPU Spike
by Joe Clark 09 Jan '09

09 Jan '09

Hi.. I am setting up a new server (2GHz CPU, Ubuntu 8.10) and am using dovecot for an IMAP server. I have installed dovecot 1.1.4 and Squirrelmail 1.4.15. sudo dovecot -n shows this: # 1.1.4: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_process_per_connection: no mail_privileged_group: mail auth default: passdb: driver: pam userdb: driver: passwd The problem I'm noticing is that if I do top -d 1 while clicking links in Squirrelmail (e.g., logging in, the Inbox link, opening a message), I see that a "dovecot-auth" process maximizes the CPU for about a second. While this is not a huge amount, it seems like with multiple users it could quickly bog down a server . Are there any recommendations or thoughts on what might cause the one-second CPU spike? -- or is that just normal operation? Thanks for your thoughts. - Joe Clark

2 1

[Dovecot] v1.1.8 released
by Timo Sirainen 09 Jan '09

09 Jan '09

http://dovecot.org/releases/1.1/dovecot-1.1.8.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.8.tar.gz.sig Most importantly mbox bugfixes. v1.1 should finally be as stable with mboxes as it was with v1.0. Hopefully we'll also soon have the first v1.2 beta release and the final v1.2.0 somewhat soon after that. - mbox: Several bugfixes. Fixes "next message unexpectedly lost" errors and perhaps some other problems as well. - deliver: It wasn't possible to override boolean settings in lda section by setting them to "no". - Maildir++ quota didn't correctly check if maildirs had changed during recalculation. - kqueue notify: Fixed assert-crash in some situations - dbox: Several fixes to handling Maildir migrations - Logging/error message improvements

6 13

[Dovecot] cannot delete emails in inbox
by JANE CUA 09 Jan '09

09 Jan '09

I am working on upgrading our current squirrelmail and replace uw-imap with dovecot. I have what looks like a successful installation. My current setup is: Centos 5.2 sendmail 8.13.8 dovecot 1.1.17 (imap) squirrelmail 1.4.17 I can send and receive email fine. However when I try to delete an email in my Inbox, it doesn't get deleted. It only sends a copy to the Trash folder. But the email is still in the Inbox. I can purge and delete the contents in my Trash and Sent folder, no problem. I am not sure if this is a Squirrelmail issue or a Dovecot issue. Please advice. Thank you -- Jane

4 8

[Dovecot] Dovecot-auth timeouts
by Javier Fox 08 Jan '09

08 Jan '09

Hello, I've unfortunately been unable to find anything relating to the problem I'm having specifically, in searching the list or google, and so I now plead to you to assistance. I'm running Dovecot as an LDA and SASL auth for Postfix on a Debian 4 box. Dovecot is version 1.0.rc15 (the official debian pkg version). The problem I'm running into is this. After some time of running (lately it's been as little as 5 minutes), I start to see the following errors in dovecot.log: deliver(user(a)domain.com): "Dec 23 14:38:47 "Error: User request from dovecot-auth timed out deliver(anotheruser(a)domain.com): "Dec 23 14:38:48 "Error: User request from dovecot-auth timed out Postfix responds to these by simply deferring the messages. Dovecot itself, however, begins to return 'Authentication failed' messages after significant lag time (sometimes greater than 30s): Connected to localhost. Escape character is '^]'. +OK Dovecot-POP user username +OK pass mypassword -ERR Authentication failed. Now, for authentication, Dovecot is using LDAP on the local server. The only additional information I can find pertaining to these errors is the following from slapd.log: slapd[22593]: connection_input: conn=6 deferring operation: pending operations These messages correspond 1-to-1 to the above 'deliver' errors, where 'conn' is always the same number. Restarting dovecot and ldap resolves the issue for a few minutes, but sure enough the errors start flowing again. I'm really at the end of my rope on this, as nothing I do seems to help. I have a good 500+ customers being effected by this as well, and they're all none too pleased by it. If this is something that will absolutely be resolved by upgrading from source, that is doable, but we'd prefer to stick with the official package version if possible. Dovecot configs follow Thanks, J. Fox ----- configs follow ----- dovecot.conf ------------ auth_verbose = yes auth_debug = yes auth_debug_passwords = yes mail_debug = no base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s protocol lda { postmaster_address = postmaster(a)spiritone.com auth_socket_path = /var/run/dovecot/auth-master log_path = /var/log/dovecot.log info_log_path = /var/log/mail.info } listen = * shutdown_clients = yes mmap_disable = yes lock_method = dotlock maildir_copy_with_hardlinks = no log_path = /var/log/dovecot.log info_log_path = /var/log/mail.log log_timestamp = "%b %d %H:%M:%S " syslog_facility = mail auth_default_realm = involved.com disable_plaintext_auth = no ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem login_chroot = yes valid_chroot_dirs = /home/vmail/ login_user = postfix login_process_per_connection = yes login_processes_count = 2 login_max_processes_count = 64 login_max_connections = 128 login_greeting = Involved login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c login_log_format = %$: %s default_mail_env = maildir:/home/vmail/domains/%d/%u first_valid_uid = 103 pop3_uidl_format = %08Xu%08Xv auth_cache_size = 10485760 auth_cache_ttl = 3600 auth_worker_max_count = 10 #auth_worker_max_request_count = 50 auth default { mechanisms = PLAIN LOGIN passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 user = vmail group = vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } user = vmail } dovecot-ldap.conf ----------------- hosts = localhost auth_bind = yes auth_bind_userdn = cn=%n,ou=%d,ou=mail,dc=domain,dc=com ldap_version = 3 base = ou=mail,dc=domain,dc=com dn = cn=Manager,dc=domain,dc=com dnpass = secret deref = never scope = subtree pass_attrs = mail=user,userPassword=password user_filter = (&(objectClass=VirtualMailAccount)(accountActive=TRUE)(mail=%u)) pass_filter = (&(objectClass=VirtualMailAccount)(accountActive=TRUE)(mail=%u)) user_global_uid = 1001 user_global_gid = 1001 ---end---

2 1

[Dovecot] Panic in v1.1.8
by Mark Sapiro 08 Jan '09

08 Jan '09

I just tried installing dovecot 1.1.8 as an upgrade to 1.1.7 and encountered Panics like the following with pop3 accesses Jan 8 10:55:31 sbh16 dovecot: Killed with signal 15 Jan 8 10:55:49 sbh16 dovecot: Dovecot v1.1.8 starting up Jan 8 10:57:01 sbh16 dovecot: pop3-login: Login: user=<user2>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Jan 8 10:57:01 sbh16 dovecot: Panic: POP3(user2): file mbox-transaction.c: line 54 (mbox_transaction_commit): assertion failed: (mbox->ibox.box.transaction_count > 0 || mbox->mbox_lock_type == F_UNLCK) Jan 8 10:57:01 sbh16 dovecot: POP3(user2): Raw backtrace: pop3 [0x80c4400] -> pop3 [0x80c445a] -> pop3 [0x80c3d5c] -> pop3 [0x806e209] -> pop3(index_transaction_commit+0x4e) [0x809251e] -> pop3(mailbox_transaction_commit+0x26) [0x80942a6] -> pop3(client_command_execute+0x3c5) [0x805b1f5] -> pop3 [0x805a152] -> pop3(io_loop_handler_run+0x100) [0x80cc100] -> pop3(io_loop_run+0x28) [0x80cb208] -> pop3(main+0x5d2) [0x805bda2] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x4614cdec] -> pop3 [0x80594d1] Jan 8 10:57:01 sbh16 dovecot: child 32263 (pop3) killed with signal 6 I have a few users who access their mailbox via pop3 every few minutes and they all hit this. I reverted to 1.1.7 and all was OK Here's dovecot -n from 1.1.7. The dovecot.conf for 1.1.8 was the same. # 1.1.7: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) ext3 protocols: pop3 pop3s ssl_cert_file: /etc/postfix/grizz-cert.pem ssl_key_file: /etc/postfix/grizz-key.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_access_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_lock_session: yes auth default: mechanisms: plain apop login worker_max_count: 5 passdb: driver: passwd-file args: /usr/local/etc/dovecot.passwd passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2

[Dovecot] delivers mail to bad directory(prefix) using sieve filters
by Radim Roska 08 Jan '09

08 Jan '09

Hi, I've installed dovecot debian stable(from backports) version (1.0.15). Its great..i just have problem with sieve filters. I use only web tool for creating filters that works for me (avelsieve plugin for squirrelmail). it creates rules, where specified folder has prefix INBOX. Thats fine.. Since dovecot has configured prefix INBOX too. BUT mails are delivered to INBOX.INBOX.test_folder and thats ugly and not usable. I've figured out new version 1.2 should work, but i dont like idea to install not stable version to production server. Is there any patch or something for stable version? Thanks a lot! Radim

4 9

[Dovecot] Bug Report in Connection with Expire Plugin
by Jörg Leis 08 Jan '09

08 Jan '09

If the expire plugin is enabled and a new message (not in trash) is deleted via IMAP in Mozilla Thunderbird (only tested in this client), it will indefinately copy the message into the folder. Dovecot, meanwhile, occupies itself with this: root@server:~# cat /var/log/dovecot.log [...] dovecot: 2008-12-26 09:21% Error: child 6132 (imap) killed with signal 11 dovecot: 2008-12-26 09:21% Error: child 6133 (imap) killed with signal 11 dovecot: 2008-12-26 09:21% Error: child 6134 (imap) killed with signal 11 dovecot: 2008-12-26 09:21% Error: child 6135 (imap) killed with signal 11 dovecot: 2008-12-26 09:21% Error: child 6136 (imap) killed with signal 11 dovecot: 2008-12-26 09:21% Error: child 6138 (imap) killed with signal 11 dovecot: 2008-12-26 09:21% Error: child 6139 (imap) killed with signal 11 dovecot: 2008-12-26 09:21% Error: child 6140 (imap) killed with signal 11 dovecot: 2008-12-26 09:21% Error: child 6142 (imap) killed with signal 11 [...] root@server:~# cat /var/log/dovecot.info [...] dovecot: 2008-12-26 09:21% Info: imap-login: Login: user=<admin(a)bildig.ch>, method=CRAM-MD5, rip=84.75.159.19, lip=92.42.190.87, TLS dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Loading modules from directory: /usr/lib/dovecot/modules/imap dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Module loaded: /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Module loaded: /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Module loaded: /usr/lib/dovecot/modules/imap/lib20_expire_plugin.so dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Effective uid=5000, gid=5000, home=/home/vmail/Maildirs/bildig.ch/admin dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Quota root: name=User Quota backend=maildir args= dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Quota rule: root=User Quota mailbox=* bytes=524288000 (0%) messages=0 (0%) dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Quota rule: root=User Quota mailbox=Trash bytes=52428800 (0%) messages=0 (0%) dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Quota warning: bytes=498073600 (95%) messages=0 (0%) command=/usr/local/bin/mail-quota-warning.sh 95 dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Quota warning: bytes=419430400 (80%) messages=0 (0%) command=/usr/local/bin/mail-quota-warning.sh 80 dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): maildir: data=/home/vmail/Maildirs/bildig.ch/admin dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): maildir++: root=/home/vmail/Maildirs/bildig.ch/admin, index=, control=, inbox=/home/vmail/Maildirs/bildig.ch/admin dovecot: 2008-12-26 09:21% Info: imap-login: Login: user=<admin(a)bildig.ch>, method=CRAM-MD5, rip=84.75.159.19, lip=92.42.190.87, TLS dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Loading modules from directory: /usr/lib/dovecot/modules/imap dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Module loaded: /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Module loaded: /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Module loaded: /usr/lib/dovecot/modules/imap/lib20_expire_plugin.so dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Effective uid=5000, gid=5000, home=/home/vmail/Maildirs/bildig.ch/admin dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Quota root: name=User Quota backend=maildir args= dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Quota rule: root=User Quota mailbox=* bytes=524288000 (0%) messages=0 (0%) dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Quota rule: root=User Quota mailbox=Trash bytes=52428800 (0%) messages=0 (0%) dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Quota warning: bytes=498073600 (95%) messages=0 (0%) command=/usr/local/bin/mail-quota-warning.sh 95 dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): Quota warning: bytes=419430400 (80%) messages=0 (0%) command=/usr/local/bin/mail-quota-warning.sh 80 dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): maildir: data=/home/vmail/Maildirs/bildig.ch/admin dovecot: 2008-12-26 09:21% Info: IMAP(admin(a)bildig.ch): maildir++: root=/home/vmail/Maildirs/bildig.ch/admin, index=, control=, inbox=/home/vmail/Maildirs/bildig.ch/admin [...] When the expire plugin is disabled no error occurs. I use Dovecot 1.1.4 on Ubuntu 8.10 Intrepid with following settings: root@server:~# dovecot -n # 1.1.4: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.info log_timestamp: %Y-%m-%d %H:%M% protocols: imaps pop3s ssl_cert_file: /etc/ssl/certs/www_bildig_ch__chained.crt ssl_key_file: /etc/ssl/private/www_bildig_ch.key login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_greeting: Dovecot ready login_process_per_connection: no login_processes_count: 1 login_max_processes_count: 8 login_max_connections: 64 valid_chroot_dirs: /var/spool/vmail mail_debug: yes mail_location: maildir:/home/vmail/Maildirs/%d/%n mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_process_size: 64 mail_plugins(default): expire imap_quota quota mail_plugins(imap): expire imap_quota quota mail_plugins(pop3): expire quota mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08%08Xv auth default: mechanisms: cram-md5 passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=vmail gid=vmail home=/home/vmail/Maildirs/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: expire: Trash 30 Trash/* 30 Spam 30 expire_dict: proxy::expire quota: maildir:User Quota quota_rule: *:storage=500M quota_rule2: Trash:storage=50M quota_warning: storage=95%% /usr/local/bin/mail-quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/mail-quota-warning.sh 80 dict: expire: mysql:/etc/dovecot/dovecot-dict-expire.conf root@server:~# cat /etc/dovecot/dovecot-sql.conf driver = mysql connect = host=127.0.0.1 dbname=mailserver user=mailserver password=testpwd1 default_pass_scheme = CRAM-MD5 password_query = SELECT email AS user, password, quota_rule FROM view_users WHERE email='%u' root@server:~# cat /etc/dovecot/dovecot-dict-expire.conf connect = host=localhost dbname=mailserver user=mailserver_exp password=testpwd2 table = expire select_field = expire_stamp where_field = mailbox I tried using a "user_field = user" additionally as is written here: http://wiki.dovecot.org/Plugins/Expire. (Incidentally, there must be some mismatch in the documentation because the tables for v1.1 do not contain a field username). Of course I adapted the MySQL database accordingly. Unfortunately I was unable to produce a backtrace. Thanks, Joerg Leis

2 1

[Dovecot] Apple patches 1-5
by Mike Abbott 08 Jan '09

08 Jan '09

Here are the first few simple patches from Apple, based on dovecot-1.1.7. The comments with "APPLE" in them helped us merge in your new releases; feel free to remove them. Please let me know if you want subsequent patches in a different format, or if you have any questions. Patch #1. Some versions of Mac OS X have buggy CMSG_* macros. Patch #2. Don't set "<username>=1" in the environment. Patch #3. Some versions of Mac OS X return near-duplicate kevents. Patch #4. Null renames are actually pretty slow on HFS (Apple's file system), so avoid them. Patch #5. Required by Apple's lawyers.

3 12

[Dovecot] Apple patches 6-8
by Mike Abbott 08 Jan '09

08 Jan '09

Here are a few more patches. Still keeping it easy for now. Again the basis for these patches is dovecot-1.1.7. Patch #6. Solve a cross-compilation endianness issue. Currently, Dovecot assumes that the endianness of the build system is the same as the endianness of the runtime system. This is not necessarily true. We ran into this while compiling for i386 on a ppc machine. The patch switches to using gcc's __BIG_ENDIAN__ macro; see the comment in the patch to configure.in. It also removes the related and unused MAIL_INDEX_COMPAT_FLAGS parameter. This patch may be applicable to other build environments with a little tweaking. Patch #7. Replace all occurrences of "hash_create" and "hash_destroy" with "hash_table_create" and "hash_table_destroy" respectively. The symbols hash_create and hash_destroy conflict with symbols defined in <strhash.h> and libc. This showed up when loading dovecot's quota plugin (one of our future patches will add a hash table to it; stay tuned). The wrong hash_create was called which caused a crash at the first hash_insert. Apparently this is only a problem in loaded dynamic libraries and not linked-in ones. Patch #8. Back off after auth failures to deter abusers. Stalls 5 seconds per failed attempt. PS -- Please forgive me if I make a mistake at some point while splitting these patches out from our source tree. They're all mingled together on my end and it's sometimes tricky to extract just the right changes for each patch. If anything seems fishy just let me know and I'll take another look. Thanks.

4 8

[Dovecot] ManageSieve woes
by Rodti MacLeary 08 Jan '09

08 Jan '09

Hi everyone, New to the list, and fairly confident that this issue is purely down to my own idiocy, so please go easy on me! I've been running Dovecot 1.0.13 on Debian (via Aptitude package) for some time, and have been delighted with it. For a while I've toyed with the idea of using ManageSieve as there's a nice plugin for Roundcube, so I'm trying to follow the how-to at http://wiki.dovecot.org/ManageSieve. First of all I've downloaded the Dovecot 1.1.7 source and compiled it myself. I've patched it using the appropriate ManageSieve 1.1.7 diff file referenced in the how-to, and it all appears to be running fine. The next step is to compile the ManageSieve 0.10.4 source itself. I've extracted the tarball and attempted ./configure, but it's failing with the following errors: ./configure: line 19826: cd: ../dovecot: No such file or directory ./configure: line 19829: cd: ../dovecot-sieve-1.1: No such file or directory dovecot-config not found from /home/user/dovecot-1.1-managesieve-0.10.4, use --with-dovecot=PATH to give path to compiled Dovecot sources or to a directory with the installed dovecot-config file. configure: error: dovecot-config not found I'm not entirely sure what I'm supposed to be pointing --with-dovecot to here. I've tried the Dovecot 1.1.7 source, and /etc/dovecot. Any help greatly appreciated! Rodti

2 2

[Dovecot] Debugging sieve scripts
by Andrzej Adam Filip 08 Jan '09

08 Jan '09

Where can I find "step by step" procedure to debug sieve scripts? [ something pretty simple that should work, does not work ] -- [pl>en: Andrew] Andrzej Adam Filip : anfi(a)onet.eu : anfi(a)xl.wp.pl Sex dumps core (Sex is a Simple editor for X11) -- Seen on debian bugtracking

1 0

[Dovecot] LDA - no bounces
by Andrzej Adam Filip 08 Jan '09

08 Jan '09

How to call deliver program to be sure it will *NEVER* generate bounce messages? [all signalling via deliver exit code ] -- [pl>en: Andrew] Andrzej Adam Filip : anfi(a)onet.eu : anfi(a)xl.wp.pl You k'n hide de fier, but w'at you gwine do wid de smoke? -- Joel Chandler Harris, proverbs of Uncle Remus

2 2

[Dovecot] Checking for strtoumax and strtoimax
by J Springer 08 Jan '09

08 Jan '09

Tru64 5.1b PK6 : dovecot 1.1.7 : cc Configuration checks for strtoumax and strtoimax are positive but both are unresolved during compilation. strtoq and strtouq checks are negative. I can modify compat.c to use "unsigned long ret = 0;" in place of strtoumax (does this break anything?) and/but I would like to know how to handle strtoimax. Thanks in advance.

2 5

[Dovecot] allow_nets overridden by cache
by Guy 08 Jan '09

08 Jan '09

Hi, I've just started trying allow_nets on one of my servers. I have auth_debug and auth_verbose both enabled and the output is as follows: Oct 28 13:05:48 mink dovecot: auth-worker(default): auth(user(a)domain.net,x.x.x.x): allow_nets: Matching for network 127.0.0.1/8 Oct 28 13:05:48 mink dovecot: auth-worker(default): auth(user(a)domain.net,x.x.x.x): allow_nets: Matching for network 10.0.7.176/28 Oct 28 13:05:48 mink dovecot: auth-worker(default): passdb(user(a)domain.net,x.x.x.x): allow_nets check failed: IP not in allowed networks Oct 28 13:05:50 mink dovecot: auth(default): client out: FAIL 1265 user=username(a)aluminati.net Oct 28 13:05:50 mink dovecot: auth(default): cache(user(a)domain.net,x.x.x.x): hit: <hidden> user=user(a)domain.net Oct 28 13:05:50 mink dovecot: auth(default): client out: OK 1266 user=user(a)domain.net auth_cache_ttl is set to 300. If I set it to 1 then the allow_nets successfully rejects. Once I set it back up to 300 the cache overrides the result from the allow_nets check and let's the account log in even though the allow_nets check fails. I've tried waiting for longer than the 300 seconds and then logged in again, but I still get the same result as above. Is there a gotcha that I'm unaware of or have I done something stupid (which seems the most likely :P)? Thanks Guy -- Don't just do something...sit there!

2 4

[Dovecot] Setting IMAP keywords/flags on delivery
by Matt Doran 08 Jan '09

08 Jan '09

Hi there, We've been long time users of Dovecot, and have found it a great IMAP server. I don't think we've had any serious problems in the 3-4 years of use. So great work. :) We have a IMAP inbox that is accessed by a number of different users from Thunderbird. We have a rule in Thunderbird to flag new emails as "TO DO", so someone can unflag the email once it has been actioned. This process works fairly well for a simple workflow, but problems arise when someone connects to the inbox with a Thunderbird instance that doesn't have the "TO DO" rule configured. The email will not be flagged properly. :( I'd like to be able to set this flag/keyword when the mail is delivered to the inbox, on the server side. That way the flag will be set no matter which client accesses the Inbox first. We currently use mail drop for our server-side mail filtering .... and would like to do a similar thing with this flagging process. We're using Dovecot 1.0.15 on Debian Testing, and use Maildir storage and maildrop as our delivery agent. I've read about how the keywords and Thunderbird labels work in the wiki article here (http://wiki.dovecot.org/MailboxFormat/Maildir) So I could probably write some sort of script to query the "dovecot-keywords" file, and rename the Maildir file to set the appropriate flag. But this sounds a like a bit of a hack, and maybe a little dangerous. Does anyone have any recommendations as to how I could achieve something like this? I'm keen to hear any ideas, whether it's through scripting, or some sort of scriptable/command-line IMAP client. Ideally, we'd have a way to set the flag at the time when the mail is delivered.... or when the first client retrieves any new mail? Thanks in advance!! -- Matt Doran PaperCut Software International Pty. Ltd. Phone: +61 (3) 9807 5767 E-mail: matt.doran(a)papercut.com Profile: http://www.papercut.com/about/#matt Blog: http://www.papercut.com/blog/

2 3

[Dovecot] Default dirs in ./configure?
by Peter Lindgren 08 Jan '09

08 Jan '09

Hi! I try to build a new 1.1.7 installation. Since I'm not a large sysadmin, just my own private mail server admin, I just wonder why the sysconf and state dirs defaults to $prefix? Maybe I'm old-school, but isn't /etc and /var, respectively, a better default than /usr/local? Should require two new variables in the configure script, though. (and yes, I know I set them with --sysconfdir=/etc --localstatedir=/var --sharedstatestatedir=/var ) /Peter -- Peter Lindgren http://www.norrskenkonsult.com

6 6

Re: [Dovecot] login fails when username has apostrophe
by Karl Latiss 08 Jan '09

08 Jan '09

Sorry to bump so quickly but I have a handful of users who can't log in at the moment and would like to get this fixed. Am I missing a config option or is this a bug? The only reference I can find in the mailing list archives is that this configuration should be supported. Karl. -------------------------------------------------------------- Hi I've added the apostrophe character to auth_username_chars however authentication still fails. I'm using LDAP with the following details: dovecot version 1.1.7 openldap client library 2.4.11 With auth_verbose = yes and auth_debug = yes set I see the following in the logs. Note the initial escaped apostrophe and the subsequent escaped escape in the filter! ----- start log ----- Jan 5 16:15:05 www-example1 dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=10.1.1.180 rip=10.3.96.60 lport=143 rport=48733 resp=<hidden> Jan 5 16:15:05 www-example1 dovecot: auth(default): ldap(julie.o \'reilly(a)example.com,10.3.96.60) pass search: base=dc=example, dc=com scope=subtree filter=(&(objectClass=qmailUser)(uid=julie.o\\'reilly)) field s=mail,userPassword Jan 5 16:15:05 www-example1 dovecot: auth(default): ldap(julie.o \'reilly(a)example.com,10.3.96.60) unknown user Jan 5 16:15:07 www-example1 dovecot: auth(default): client out: FAIL 1 user=julie.o\'reilly(a)example.com failed, 1 attempts): user=<julie.o\'reilly(a)example.com>, method=PLAIN, rip=10.3.96.60, lip=10.1.1.180 ----- end log ----- Users without apostrophes can authenticate successfully. If I've missed anything please let me know. # dovecot -n # 1.1.7: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.0-RELEASE amd64 ufs protocols: imap listen: 10.1.1.180 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting_capability: yes verbose_proctitle: yes first_valid_uid: 999 first_valid_gid: 999 mail_privileged_group: mail mail_uid: 999 mail_gid: 999 mail_location: maildir:/usr/home/vmail/%Ld/%Ln imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep auth default: mechanisms: plain login username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@' username_format: %Lu passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail # grep -v '^ *$#.*$\?$' dovecot-ldap.conf uris = ldap://www-example1:389 dn = uid=xxxx,dc=example,dc=com dnpass = xxxx sasl_bind = no tls = no auth_bind = no ldap_version = 3 base = dc=example, dc=com user_attrs = homeDirectory=home=/usr/home/vmail/%L $,mailMessageStore=mail=maildir:/usr/home/vmail/%L$,=uid=999,=gid=999 user_filter = (&(objectClass=qmailUser)(uid=%n)) pass_attrs = mail=user,userPassword=password pass_filter = (&(objectClass=qmailUser)(uid=%n)) default_pass_scheme = PLAIN -- Karl Latiss <klatiss(a)nextdigital.com> Next Digital

5 19

[Dovecot] Problem with opening ports in alpha5 ?
by Bruce A. Mallett 07 Jan '09

07 Jan '09

If I leave the "listen" value as the default in /etc/dovecot.conf I'll get a message similar to the following on each port that it tries to open during startup: # dovecot -F Fatal: listen(::, 143) failed: Address already in use If I set either: listen = * or listen = [::] then it will start up fine. Perhaps it is as though the code tries to open the port twice for both ip4 and ip6? - Bruce

2 6

[Dovecot] Apple patches 11-14
by Mike Abbott 07 Jan '09

07 Jan '09

These are the last patches for now, and they're small. The base for each of them is dovecot-1.1.7 + Apple patches 9 and 10, again not because of a logical dependency but just because these patches change parts of the earlier patches. Patch #11 adds a few dtrace providers to key points in the code. We are still validating the correct placement and usefulness of these. One cool thing about dtrace is that when not in use the hooks literally are just a couple of no-op instructions. Patch #12 increases many listen queue sizes to handle high loads better. The new values are not necessarily the best possible values but they do allow more throughput. Patch #13 makes dovecot adapt to dynamic host identity changes upon config reload. Patch #14 covers three miscellaneous changes, to support more file descriptors and an "unlimited" number of mail processes, and a different default mail user. That's all our patches for now!

3 5

[Dovecot] Obtaining the chroot-cage directory of the mailstore
by Stefan Jurisch 07 Jan '09

07 Jan '09

Hello, I'd like to find a function in the sourcecode which enables me to get the chroot-path of the mailstore, so I can concatenate it with the result of mail_storage_get_mailbox_path to get the full path of a mailbox within the filesystem. Does such a function exist? Who can help me? Thanks in advance. Stefan -- SIEGNETZ.IT GmbH { w3o-services } Schneppenkauten 1a D-57076 Siegen Tel.: 0271 68193-0 Fax: 0271 68193-29 Geschäftsführer: Oliver Seitz Handelsregister-Nummer: HRB4838 Registergericht: Amtsgericht Siegen -------------------------------- Das Wort “WINDOWS” stammt aus einem alten Sioux-Dialekt und bedeutet: “Weißer Mann starrt durch Glasscheibe auf Sanduhr.” -------------------------------- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 2

[Dovecot] Bug Report on Expire PlugIn (update)
by Jörg Leis 07 Jan '09

07 Jan '09

I did the same thing on the console and this is what happens: bash-3.2$ openssl s_client -connect example.com:993 CONNECTED(00000003) [...] Server certificate -----BEGIN CERTIFICATE----- [...] -----END CERTIFICATE----- [...] CA --- No client certificate CA names sent --- SSL handshake has read 4595 bytes and written 322 bytes --- New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA Server public key is 2048 bit Compression: NONE Expansion: NONE SSL-Session: [...] --- * OK Dovecot ready . login admin(a)example.com secret . OK Logged in. . select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft KMAILFORWARDED KMAILTODO KMAILWATCHED KMAILIGNORED $FORWARDED $TODO $WATCHED $IGNORED NonJunk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft KMAILFORWARDED KMAILTODO KMAILWATCHED KMAILIGNORED $FORWARDED $TODO $WATCHED $IGNORED NonJunk \*)] Flags permitted. * 4 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1230136990] UIDs valid * OK [UIDNEXT 77] Predicted next UID . OK [READ-WRITE] Select completed. . copy 1 Trash closed

1 0

[Dovecot] IMAP Folder permissions
by Stuart Gall 07 Jan '09

07 Jan '09

Hello, Happy new year. I have a dovecot with exim installation. I am using virtual users for mail and IMAP. When dovecot creates a folder from imap user the permissions are rwx------ I need them to be rwxrwx--- Is there a way to change this in the configuration file ? TIA Stuart Stuart Gall ------------------------------------------------------------------------ ---------- There are three sorts of mathematician: those that can count and those that can't. ------------------------------------------------------------------------ ----------

2 1

[Dovecot] writing a dovecot plugin / segfault
by Stefan Jurisch 07 Jan '09

07 Jan '09

Hi together, I am new to this list and new to dovecot itself. I have to write a plugin that implements some ACL-voodoo to be used instead of the standard ACL stuff of dovecot (it shall allow just application-driven folder-sharing - no more, no less). Though I started programming with C, my last experiences are some days old, but now I have written the function sekeletons and the registration function with the 'register-command"-calls etc. The makefile-stuff I copied from the imap-quota-plugin and modified it, so all appearances of "lib11_imap_quota_plugin..." and similar are now found as "lib11_folderacl_plugin..." and so on. In short words: I think I have done all nessessary mods to the source (I tried it some days ago with a slightly older version of dovecot, and until I did some unknown thing, it worked quite well...) to make the whole thing work. One example function is (just testing at the moment): /* MYRIGHTS <folder>: retreive the rights of the current folder */ static bool cmd_myrights(struct client_command_context *cmd) { struct mail_storage *storage; struct mailbox *folder; const char *folder_name; string_t *response; /* read argument: <folder> */ if (!client_read_string_args(cmd, 1, &folder_name)) return FALSE; /* work done from here... */ /* for the moment, do a dummy response */ str_append(response, "* MYRIGHTS "); str_append(response, folder_name); str_append(response, " lrswipcda"); client_send_line(cmd->client, str_c(response)); client_send_tagline(cmd, "OK Completed."); return TRUE; } But when testing via "telnet localhost 143" and doing a "20 myrights INBOX" the imap thread just crashes and does not give any answer. in /var/log/messages I only find something like the following entry: Jan 5 13:40:12 kungfu kernel: imap[8991]: segfault at 4 ip 080d5c67 sp bf82b040 error 4 in imap[8048000+b8000] Maybe somebody can tell me, what this is? If needed, I also post the complete code itself somewhere. Thanks in advance. Stefan -- SIEGNETZ.IT GmbH { w3o-services } Schneppenkauten 1a D-57076 Siegen Tel.: 0271 68193-0 Fax: 0271 68193-29 Geschäftsführer: Oliver Seitz Handelsregister-Nummer: HRB4838 Registergericht: Amtsgericht Siegen -------------------------------- Das Wort “WINDOWS” stammt aus einem alten Sioux-Dialekt und bedeutet: “Weißer Mann starrt durch Glasscheibe auf Sanduhr.” -------------------------------- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 1

[Dovecot] mbox "Next message unexpectedly lost" bug fixed
by Timo Sirainen 07 Jan '09

07 Jan '09

Good news, everyone! The most annoying bug in v1.1 series should finally be fixed by these patches: http://hg.dovecot.org/dovecot-1.1/rev/f28348c5201e http://hg.dovecot.org/dovecot-1.1/rev/74c47fcfb420 http://hg.dovecot.org/dovecot-1.1/rev/a28520d26b5a http://hg.dovecot.org/dovecot-1.1/rev/539f8d983285 http://hg.dovecot.org/dovecot-1.1/rev/9b7af230f9f0 They also make sure that mbox is never read while it's not locked. I think that could have happened in some situations with v1.1. Hopefully mbox handling will now finally be as stable in v1.1 as it was in v1.0. I'll make a new v1.1 release after seeing what bug fixes are coming from Apple, so probably next week.

3 3

[Dovecot] New SSL certificate problem
by Stewart Dean 05 Jan '09

05 Jan '09

Our DC has been using a Verisign certificate. Over the past year, we've been using a Digicert Wildcard Plus certificate for almost all of our machines, and I wanted to switched over our DC mailserver. I used the following command to generate the CSR and key: openssl req -new -newkey rsa:1024 -nodes -out star_bard_edu.csr -keyout star_bard_edu.key -subj "/C=US/ST=NY/L=ourtown/O=Bard College IT/OU=Bard College /CN=*.bard.edu" The resultant CSR verified and I submitted it to digicert and got back our cert, plus their intermediate and Trusted root certs. I killed the root instance of dovecot and waited for all the children to die I put together the intermediate cert (first) and our cert (second) into /usr/ssl/certs/dovecot.pem I put the key star_bard_edu.key in /var/ssl/private/dovecot.pem I restarted dovecot, but the imap login instances didn't appear, so I shifted back to the original combined cert file and key, restarted dovecot and it came up OK I check the syslog and saw these error messages: Jan 5 10:19:49 mercury mail:err|error dovecot: imap-login: Can't load private k ey file /var/ssl/private/dovecot.pem: error:0B080074:x509 certificate routines:X 509_check_private_key:key values mismatch Jan 5 10:19:49 mercury mail:err|error last message repeated 8 times Jan 5 10:19:49 mercury mail:err|error dovecot: child 4051108 (login) returned e rror 89 Jan 5 10:19:49 mercury mail:err|error dovecot: child 4231382 (login) returned e rror 89 I checked my key and it has the same time stamp as my CSR, so I didn't somehow get the wrong key. Both the old and new key are 600; if the old one works based on perms, the new one should too. Would some kind soul tell me what I'm missing? Or is there a problem using wild card certificate with DC? Is there an openssl command to verify the key. Or is it that the key is unencrypted? -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 2

[Dovecot] login fails when username has apostrophe
by Karl Latiss 05 Jan '09

05 Jan '09

Hi I've added the apostrophe character to auth_username_chars however authentication still fails. I'm using LDAP with the following details: dovecot version 1.1.7 openldap client library 2.4.11 With auth_verbose = yes and auth_debug = yes set I see the following in the logs. Note the initial escaped apostrophe and the subsequent escaped escape in the filter! ----- start log ----- Jan 5 16:15:05 www-example1 dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=10.1.1.180 rip=10.3.96.60 lport=143 rport=48733 resp=<hidden> Jan 5 16:15:05 www-example1 dovecot: auth(default): ldap(julie.o \'reilly(a)example.com,10.3.96.60) pass search: base=dc=example, dc=com scope=subtree filter=(&(objectClass=qmailUser)(uid=julie.o\\'reilly)) field s=mail,userPassword Jan 5 16:15:05 www-example1 dovecot: auth(default): ldap(julie.o \'reilly(a)example.com,10.3.96.60) unknown user Jan 5 16:15:07 www-example1 dovecot: auth(default): client out: FAIL 1 user=julie.o\'reilly(a)example.com failed, 1 attempts): user=<julie.o\'reilly(a)example.com>, method=PLAIN, rip=10.3.96.60, lip=10.1.1.180 ----- end log ----- Users without apostrophes can authenticate successfully. If I've missed anything please let me know. # dovecot -n # 1.1.7: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.0-RELEASE amd64 ufs protocols: imap listen: 10.1.1.180 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting_capability: yes verbose_proctitle: yes first_valid_uid: 999 first_valid_gid: 999 mail_privileged_group: mail mail_uid: 999 mail_gid: 999 mail_location: maildir:/usr/home/vmail/%Ld/%Ln imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep auth default: mechanisms: plain login username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@' username_format: %Lu passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail # grep -v '^ *$#.*$\?$' dovecot-ldap.conf uris = ldap://www-example1:389 dn = uid=xxxx,dc=example,dc=com dnpass = xxxx sasl_bind = no tls = no auth_bind = no ldap_version = 3 base = dc=example, dc=com user_attrs = homeDirectory=home=/usr/home/vmail/%L $,mailMessageStore=mail=maildir:/usr/home/vmail/%L$,=uid=999,=gid=999 user_filter = (&(objectClass=qmailUser)(uid=%n)) pass_attrs = mail=user,userPassword=password pass_filter = (&(objectClass=qmailUser)(uid=%n)) default_pass_scheme = PLAIN -- Karl Latiss <klatiss(a)nextdigital.com> Next Digital

1 0

[Dovecot] Permission to distribute Dovecot run file
by Rick Widmer 05 Jan '09

05 Jan '09

I am working on updating the Shupp toaster, http://shupp.org/toaster/ a set of files and instructions for installing qmail, vpopmail, qmailadmin and squirrelmail. Two of my most important goals are switching the imap program from courier to Dovecot, and closer integration with OpenSuSE. (Which I run my mail servers on.) To follow the style of the toaster I need a place where I can obtain the init.d script from http://wiki.dovecot.org/DovecotInit I would prefer to have permission to host the file myself so I don't have to worry about creating patches if there is ever a need for my run file to be different from yours. If that is not acceptable, would you please either provide a URL where I can download just the run file, or include it in the distribution. Thanks, Rick

3 2

[Dovecot] Warnings compiling on OpenBSD 4.4 i386
by Peter Lindgren 04 Jan '09

04 Jan '09

Hi, probably just nothing to worry about, but I get the following warnings when building 1.1.7 on OpenBSD 4.4 on i386. If I remove the --with-bsdauth config option, they all disappear. I won't use it anyway, but maybe there are others. $ dmesg OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008 deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Xeon(R) CPU 3040 @ 1.86GHz ("GenuineIntel" 686-class) 1.87 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR real mem = 1071788032 (1022MB) avail mem = 1027936256 (980MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xfd460, SMBIOS rev. 2.4 @ 0xdc010 (48 entries) bios0: vendor HP version "O10" date 07/20/2007 bios0: HP ProLiant ML110 G4 $ ./configure --without-pop3d --with-deliver --with-passwd --with-passwd-file --with-bsdauth --without-ldap --sysconfdir=/etc --localstatedir=/var --sharedstatedir=/var mail-index-map.c: In function `mail_index_map_ext_hdr_check': mail-index-map.c:171: warning: comparison between signed and unsigned mail-index-map.c: In function `mail_index_map_clone': mail-index-map.c:1112: warning: comparison between signed and unsigned mail-index-sync-update.c: In function `sync_header_update': mail-index-sync-update.c:419: warning: comparison between signed and unsigned mail-transaction-log-file.c: In function `log_file_track_mailbox_sync_offset_hdr': mail-transaction-log-file.c:682: warning: comparison between signed and unsigned passdb-bsdauth.c: In function `bsdauth_preinit': passdb-bsdauth.c:59: warning: implicit declaration of function `auth_cache_parse_key' passdb-bsdauth.c:60: warning: assignment makes pointer from integer without a cast /Peter -- Peter Lindgren http://www.norrskenkonsult.com

2 1

[Dovecot] convert non-standard mbox to maildir
by Maarten Bezemer 04 Jan '09

04 Jan '09

Hi, Let me start with wishing you all the best for this new year, and I hope we'll see a lot of new features and not so much new bugs ;-) I'm trying to convert a number of PSTs to maildir. Just plain drag&drop in Outlook doesn't work (gives a very cryptic error message in a certain folder, but that folder is perfectly all right), and using the import option also barfs when it's not even half-way through the PST. So, I took aid4mail and it converted the PST to mbox wihtout any problem. But now, I have a directory structure, filled with mbox mailboxes. Like: INBOX INBOX/mailbox INBOX/subfolder INBOX/subfolder/mailbox INBOX/subfolder/subsubfolder INBOX/subfolder/subsubfolder/mailbox INBOX/subfolder2 INBOX/subfolder2/mailbox etc. This differs from normal mbox setup, but given the fact that there are both folders AND messages below inbox, this is indeed the only useful way to do it. But now I cannot convert this to maildir using either dovecot or mb2md, since it's not the usual mbox setup. Any suggestions would be greatly appreciated! Thanks in advance, Maarten

2 3

[Dovecot] deliver looking into root directory for sieve configuration ?
by Guillaume Hilt 03 Jan '09

03 Jan '09

Hi, I'm using dovecot (+sieve), dspam, clamav and postfix with wirtual users and domains. When the server receive an email, I get this error : Jan 2 14:48:52 mail postfix/qmgr[13573]: 89DE1276C42B: from=<postmaster(a)shadowprojects.org>, size=926, nrcpt=1 (queue active) Jan 2 14:48:52 mail deliver(postmaster(a)adomain.fr): chdir(/root) failed: Permission denied Jan 2 14:48:52 mail deliver(postmaster(a)adomain.fr): stat(/root/.dovecot.sieve) failed: Permission denied Jan 2 14:48:52 mail deliver(postmaster(a)adomain.fr): msgid=<495E1B33.5020009(a)shadowprojects.org>: saved mail to INBOX Jan 2 14:48:52 mail postfix/lmtp[13584]: 89DE1276C42B: to=<postmaster(a)adomain.fr>, relay=mail.mydomain.com[/var/run/dspam/dspam.sock], delay=0.07, delays=0.05/0/0/0.01, dsn=2.6.0, status=sent (250 2.6.0 <postmaster@adomain> Message accepted for delivery) Why does it look inside the /root folder for sieve configuration ? All virtual mailboxes are in /home/vmail/DOMAIN/USER/.maildir (owned by postfix:postfix; dspam has been put in the postfix group) I uploaded the following config files in http://hiltg.pastebin.com/ : - main.cf - master.cf - dovecot.conf - dspam.conf (mails are supposed to be delivered to the mailbox by dovecot, which is called by dspam) Any idea please ? Thanks and happy new year to you all, -- Guillaume Hilt

4 17

[Dovecot] Per-namespace proxying?
by VanL 03 Jan '09

03 Jan '09

Hello, Searching in the archives, I saw the following posting from Timo Sirainen: [Dovecot] Roadmap to future (06 Dec 2007): [...] > Proxying > -------- > > - These could be implemented to v1.2. - Log in normally (no proxying) > if destination IP is the server itself. > > - Support for per-namespace proxying: > > namespace public { > prefix = Public/ > location = proxy:public.example.org > } > > There are two choices for this: Dummy IMAP proxying or handling it with > a mail storage backend. Dummy IMAP proxying would just let the remote server > whose mailbox is currently selected handle most of the commands and their > replies. I'm just afraid that this will become problematic in future. > ... (continues) Was this feature ever implemented? Is it in the 1.2 alphas? On a related note, were virtual mailboxes implemented? Thanks, Van

2 1

[Dovecot] Unkillable imap process?
by Johan Persson 03 Jan '09

03 Jan '09

Hi, Not sure if this is relevant but having been running dovecot 1.1.4 for a long time (without any problem) I recently upgraded to 1.1.7 when I switched to SuSE 11.1 This is just running on my home server and it's a fairly standard fetchmail-procmail-dovecot setup. However I recently had an incident which I cannot quite explain. I suspect it could be a possible disk problem but I did run a SMART check and the disks and HW seems ok. The mail store is mounted on a separate partition using ext3 fs What happened was that I noticed that the load on my server went through the roof and that the imap process was hogging 100% of the CPU and it had been running so for over an hour. Before this happened I had just setup a new laptop with Thunderbird as the mail client and had just done a off-line sync of my whole mail store (~1.5GB). So for a short time the dovecot server would have been under maximum load. I tried to recover by gracefully shutting down dovecot and when that didn't stop the imap process I first tried to be nice by sending it the TERM signal and when that didn't do it, the KILL signal. However, I was not able to stop the imap process. I then decided to recycle the server and initiated a shutdown. However, not even that was able to complete (since the shutdown process seemed to be hanging on not being able to stop the imap process). In the end I was (for the first time in over 6 years) forced to use the hard reset button on the server. I do realize that this is almost impossible to diagnose, but does anyone now in general what could possible cause the imap process to so completely be locked up that it is impossible to even shut it down? The dovecot -n output is 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.7-9-pae i686 openSUSE 11.1 (i586) ext3 log_path: /var/log/dovecot.err info_log_path: /var/log/dovecot.info login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_processes_count: 2 login_max_processes_count: 2 login_max_connections: 5 max_mail_processes: 32 mail_max_userip_connections: 8 mail_location: maildir:/srv/mail/%u mailbox_idle_check_interval: 15 fsync_disable: yes auth default: passdb: driver: pam userdb: driver: passwd Cheers Johan

3 2

[Dovecot] Possible to log IMAP connections to MySQL Table?
by Corey Shaw 03 Jan '09

03 Jan '09

Is it currently possible to log all IMAP connection attempts to a MySQL table? Thanks. _____________________ Corey

8 13

[Dovecot] NFS, IDLE, and index locking
by Jack Stewart 31 Dec '08

31 Dec '08

Hi, I'll try to keep short. My primary question is what, in people's experience, are the best configuration settings for to avoid potential NFS cache locking issues in an interesting heterogeneous environment? We appear to have a workaround for some locking issues we have seen, which is turning off IDLE. Upgrading our version of dovecot from 1.1.4 is likely to address some core issues, but I want to get the system setup in tune first. There are some things in our setup that seem dumb, and I would like to make sure they are dumb. As far as our environment goes, it isn't unusual for our users to connect with multiple different clients from multiple locations. Some of these clients behave well, and some not so well. In addition we have multiple distributed servers with multiple instances. Generally the connection from one of their clients/desktops goes to the same server but their different desktops may connect to different servers. If anyone has a similar enough environment, do you find it better to have the hard link setting off or is it better for you to turn it on? The attribute cache is the default (60 seconds) which works well enough in a polling setting but may be a problem with IDLE (30 second check). Do you find it better to bump up the IDLE check interval or drop the attribute cache? Our cache and maildir are on separate NFS volumes so we can change one without changing the other. Our tcp timeout setting is too long (it is the default). Do you find 180-300 seconds more reasonable? ---Jack To give some context, we have a handful of users with intermittent caching locking where the dovecot.index.cache file would simply not update. One of our internal people managed to get this problem when he was using pine (non-IDLE) with gnubiff (IDLE) from the same desktop. We haven't had any alarms since taking the brute force approach of turning off IDLE. Unfortunately other projects are inhibiting my capacity for additional debugging at this time. Also, it isn't clear to me that we will learn anything useful since the servers do not appear to be tuned and they are only running dovecot 1.1.4. Just for reference, below is our dovecot configutation. disable_plaintext_auth = yes base_dir = /var/run/dovecot/imap-server-its/ protocols = imap imaps syslog_facility = local4 shutdown_clients = yes ssl_cert_file = xxx.pem ssl_key_file = yyy.key ssl_ca_file = zzz.pem mail_location = maildir:/var/spool/maildir/%1Ln/%Ln:INDEX=/var/spool/dovecot/indexes/%1Ln/%Ln login_greeting_capability = no verbose_proctitle = yes mail_debug = yes imap_capability = "IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1" # MAILDIR Performance settings maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = no # Handling web logins & imap traffic login_processes_count = 16 login_max_processes_count = 2048 max_mail_processes = 4096 mail_max_userip_connections = 2000 # NFS settings mmap_disable = yes fsync_disable = no mail_nfs_index = yes mail_nfs_storage = yes dotlock_use_excl = yes lock_method =fcntl protocol imap { listen = *:10143 ssl_listen = *:10993 imap_client_workarounds = delay-newmail outlook-idle netscape-eoh } ## Authentication processes namespace private { separator = . prefix = Mail. inbox = yes } auth_verbose = yes auth default { mechanisms = plain login passdb ldap { args = /etc/dovecot.conf-ldap } userdb static { args = uid=vmail gid=mail home=/var/spool/maildir/%1Ln/%Ln } socket listen { master { path = /var/run/dovecot/imap-server-its/auth-master user = vmail group = mail } user = root }

2 2

Re: [Dovecot] Bug in Dovecot 1.0.5 - CRYPT-MD5 not working
by Timo Sirainen 31 Dec '08

31 Dec '08

On Dec 31, 2008, at 1:50 AM, Jim Salter wrote: > Hrm. OK, not arguing, just curious: where is the MD5-CRYPT standard > defined? I don't think it's a real standard. It's just something that libcs started implementing. I think OpenBSD did it first and then others started copying. > Worth noting that the (Apache?) standard in question is also the one > used in vpopmail vpasswd.cdb files (authdb vpopmail, userdb vpopmail). Would it work if you simply changed $apr1$ to $1$? I can't really see why $apr1$ would otherwise work in glibc. I just checked its sources and also Ubuntu patches. There's no mention of apr1 in them.

2 1

[Dovecot] Bug in Dovecot 1.0.5 - CRYPT-MD5 not working
by Jim Salter 31 Dec '08

31 Dec '08

Problem: Using MySQL storage for the user and password db with MD5-CRYPT hashes, Dovecot fails to successfully authenticate when the MD5-CRYPT or MD5 settings are specified as default_pass_scheme in dovecot-mysql.conf. Dovecot /does/ successfully authenticate against MD5-CRYPT hashes when default_pass_scheme is set to CRYPT, which according to the docs should be DES encryption. (I do not know whether or not CRYPT actually works with DES hashes.) I am positive that I am using MD5-CRYPT hashes, as I have dropped in hashes from a Qmail/Vpopmail vpasswd file and they work with the CRYPT setting in Dovecot, as do hashes generated using htpasswd -nmb. Test system: Ubuntu Server 7.10, amd64 Dovecot 1.0.5 (from Ubuntu repositories) Postfix 2.4.5 (from Ubuntu repositories) Demonstration: # cat /etc/dovecot/dovecot-mysql.conf driver = mysql connect = dbname=redacted user=redacted host=127.0.0.1 password=redacted default_pass_scheme = MD5-CRYPT password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT maildir, 105 AS uid, 114 AS gid FROM mailbox WHERE username = '%u' # htpasswd -nmb user password user:$apr1$bZQl//..$2IPoOibTBaqpG7pPFigOy/ # mysql -u postfix -p mysql> use redacted; Database changed mysql> update userdb set password='$apr1$bZQl//..$2IPoOibTBaqpG7pPFigOy/' where username='user'; Query OK, 1 rows affected (0.00 sec) mysql>quit Bye # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. a login user password a NO Authentication failed. a logout * BYE Logging out a OK Logout completed. Connection closed by foreign host. # replace MD5-CRYPT CRYPT -- /etc/dovecot/dovecot-mysql.conf # /etc/init.d/dovecot restart * Restarting IMAP/POP3 mail server dovecot [ OK ] # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. a login user password a OK Logged in. a logout * BYE Logging out a OK Logout completed. Connection closed by foreign host.

2 1