January 2007 - dovecot

[Dovecot] rc15 errors
by Nicolas STRANSKY 05 Jan '07

05 Jan '07

Hi, Since I installed rc15 I'm seing the following errors in logs of a server with several hundreds of pop3 and imap users. All the indexes have been erased and recreated after installation. Dec 21 21:06:46 rouge dovecot: pop3-login: inotify_init() failed: Too many open files The maildir mailboxes are on NFS, but the indexes are local. What should be done to correct this error ? These two error have appeared only once: Dec 22 11:02:07 rouge dovecot: IMAP(xxxxxx): file client.c: line 378 (client_handle_input): assertion failed: (!client->disconnected) Dec 22 11:02:07 rouge dovecot: child 31833 (imap) killed with signal 6 Dec 22 12:43:20 rouge dovecot: IMAP(xxxxxx): free(): invalid pointer 0x5bbbe0! Dec 22 12:43:20 rouge dovecot: child 26938 (imap) killed with signal 11 Dec 22 12:43:20 rouge kernel: imap[26938]: segfault at 0000000000000018 rip 00002b328a17e527 rsp 00007fff20bbb230 error 6 This one seems to have disappeared after patching src/lib-index/mail-index.c as you suggested on the list. Dec 21 14:15:44 rouge dovecot: child 21826 (imap) killed with signal 11 Dec 21 14:15:44 rouge kernel: imap[21826]: segfault at 0000000000000098 rip 0000000000425bf8 rsp 00007fffd7433b10 error 4 Are these errors harmful ? Regards, -- Nico Jamais un orateur n'a pensé en parlant ; jamais un auditeur n'a pensé en écoutant. -+- Émile Chartier, dit Alain (1868-1951), Propos sur l'éducation -+-

3 2

[Dovecot] suse spec for rc16 fixed
by Robert Schetterer 05 Jan '07

05 Jan '07

Hi Timo, hi all i fixed my spec , my failure i didnt looked exactly to it ( i had to change paths to modules ) now its compiling sorry Robert -- Diese Nachricht wurde auf Viren und andere gefährliche Inhalte untersucht und ist - aktuelle Virenscanner vorausgesetzt - sauber.

1 0

[Dovecot] Failed proxy auth drops connection for IMAP/POP3 proxy in 1.0-RC15
by Bruce Walter 05 Jan '07

05 Jan '07

Hello, I was seeing an odd behavior in a proxy-only configuration of dovecot. When a user entered an incorrect password in either IMAP or POP3, the Dovecot connection would be immediately dropped, sometimes with the auth failure message, sometimes without (a timing issue). I believe I have tracked down the cause to the code commented out in the attached diff. It appears that the proxy handlers are giving the client the go-ahead to attempt authorization again and then dismantling the proxy session. I believe the correct behavior would be to allow LOGOUT or QUIT to end the session and do the tear-down in client_destroy. The commented code all gets executed (with more error checking) in client_destroy, so there shouldn't be any memory leaks that I can see. Please advise if this seems correct or let me know of a different method of fixing. Thunderbird does 'Bad Things (tm)' when the connection is dropped without an authorization failed message... It doesn't re-prompt for the password and the user appears to have correctly authenticated, but the session just sits and no mail can be retrieved. Thanks, - Bruce -- __________________________ Bruce M. Walter Senior Network Manager Rho, Inc 6330 Quadrangle Drive Suite 500 Chapel Hill, NC 27517 T: 919.408.8000 x332 F: 919.408.0999

2 2

[Dovecot] Getting "Can't resolve address no: Name or service not known" error when starting Dovecot
by Francesco Piraneo Giuliano 05 Jan '07

05 Jan '07

Hi gentlemen! After running for six month Dovecot 0.99.14 I decided to upgrade to 1.0rc15. Actually Dovecot is running under Slackware Linux 10.2 and I got the package from http://www.linuxpackages.net. Problems? Yes, one! When I try to startup Dovecot program hung: Fatal: Can't resolve address no: Name or service not known I'm not a Dovecot or IMAP guru and I can't imagine what kind of address number (I think is complaining about the machine's IP address) or "name" or "service" that it doesn't know! I googled for the entire afternoon for someone that meet the same problem but I got no interesting clues... Yesterday I installed also iptables and I thought the two things are related so I disabled iptables but... nothing! Here some valuables (I hope!) informations for the good guys that want to help my desperate soul... Thank you again and I hope everybody enjoy the Christmas holidays... Bye! Francesco P.S.: I hope also that the Dovecot team develop an online documentation that reflect the versatility and complexity of the program.... ;-) dovecot --version 1.0.rc15 dovecot --build-options Build options: ioloop=poll notify=inotify ipv6 openssl SQL drivers: Passdb: checkpassword passwd passwd-file shadow Userdb: checkpassword passwd prefetch passwd-file static dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/errors.log info_log_path: /var/log/dovecot/info.log protocols: imap listen: *:143 ssl_listen: no ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_max_processes_count: 8 mail_location: mbox:/home/mail/%u:INBOX=/var/mail/%u auth default: cache_size: 128 cache_ttl: 60 count: 8 passdb: driver: shadow userdb: driver: passwd Follows the full configuration file: # Base directory where to store runtime data. base_dir = /var/run/dovecot/ # Protocols we want to be serving: imap imaps pop3 pop3s # If you only want to use dovecot-auth, you can set this to "none". protocols = imap # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. listen = 192.168.1.100 protocol imap { listen = *:143 } # Disable LOGIN command and all other plaintext authentications disable_plaintext_auth = no # Should all IMAP and POP3 processes be killed when Dovecot master process # shuts down. shutdown_clients = yes # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). log_path = /var/log/dovecot/errors.log # For informational messages, use this logfile instead of the default info_log_path = /var/log/dovecot/info.log # Prefix for each line written to log file. % codes are in strftime(3) # format. log_timestamp = "%b %d %H:%M:%S " # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. syslog_facility = mail ## ## SSL settings ## ssl_listen = no # Disable SSL/TLS support. ssl_disable = yes ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. login_dir = /var/run/dovecot/login # User to use for the login process. login_user = dovecot # Set max. process size in megabytes. login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? login_process_per_connection = yes # Number of login processes to keep for listening new connections. login_processes_count = 3 # Maximum number of login processes to create. login_max_processes_count = 8 # Greeting message for clients. login_greeting = Dovecot ready. # Space-separated list of elements we want to log. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. login_log_format = %$: %s ## ## Mailbox locations and namespaces ## # Location for users' mailboxes. mail_location = mbox:/home/mail/%u:INBOX=/var/mail/%u ## ## IMAP specific settings ## protocol imap { # Login executable location. login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location. mail_executable = /usr/libexec/dovecot/imap } ## ## Authentication processes ## # Executable location auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. auth_process_size = 256 # Authentication cache size in kilobytes. 0 means it's disabled. auth_cache_size = 128 # Time to live in seconds for cached data. auth_cache_ttl = 60 # List of allowed characters in username. auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth default { # Space separated list of wanted authentication mechanisms mechanisms = plain # /etc/shadow or similiar, using getspnam(). passdb shadow { } # /etc/passwd or similar, using getpwnam() userdb passwd { } # User to use for the process. user = root # Number of authentication processes to create count = 8 } ## ## Dictionary server settings ## dict { } ## ## Plugin settings ## plugin { }

3 6

[Dovecot] POP3S doesn't work anymore
by Johann Burkard 05 Jan '07

05 Jan '07

Hello, I use 1.0_rc15 on Gentoo Linux and since upgrading from the previous version (0.97 something?), POP3S stopped working. My USE flags are USE="[...]maildir [...] pop3d" I configured Dovecot to use POP3S: -- 8< -- # Protocols we want to be serving: # imap imaps pop3 pop3s #protocols = imap imaps protocols=pop3s -- >8 -- The pop3 binary exists: -- 8< -- # cd /usr/libexec/dovecot/ # dir total 3224 -rwxr-xr-x 1 root root 56596 Dec 10 22:51 checkpassword-reply* -rwxr-xr-x 1 root root 708532 Dec 10 22:51 deliver* -rwxr-xr-x 1 root root 144664 Dec 10 22:51 dict* -rwxr-xr-x 1 root root 276188 Dec 10 22:51 dovecot-auth* -rwxr-xr-x 1 root root 56596 Dec 10 22:51 gdbhelper* -rwxr-xr-x 1 root root 785052 Dec 10 22:51 imap* -rwxr-xr-x 1 root root 178516 Dec 10 22:51 imap-login* -rwxr-xr-x 1 root root 708428 Dec 10 22:51 pop3* -rwxr-xr-x 1 root root 170188 Dec 10 22:51 pop3-login* -rwxr-xr-x 1 root root 94476 Dec 10 22:51 rawlog* -rwxr-xr-x 1 root root 60928 Dec 10 22:51 ssl-build-param* -- >8 -- However only IMAPS is used: -- 8< -- # /etc/init.d/dovecot restart * Stopping dovecot... [ ok ] * Starting dovecot... [ ok ] # netstat -l Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:imaps *:* LISTEN tcp 0 0 *:imap2 *:* LISTEN [...] -- >8 -- Any hints? Thanks, Johann

2 2

[Dovecot] deliver as LMTP server?
by Barry Warsaw 05 Jan '07

05 Jan '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 One other question; has anybody considered writing a tool that integrates Dovecot's deliver script and an LMTP server? I'm architecting my system so that my internet facing SMTP is Postfix, but the mail folders live on a different machine. Right now, I'm considering putting a highly restricted Postfix on the internal machine, which only accepts forwards from the external machine. IWBNI I could eliminate that extra Postfix process by just letting the external one deliver to an LMTP on the internal machine, which was integrated with Dovecot's deliver. Does anything like that exist? I have a reasonably robust Python LMTP server in the current Mailman trunk. Would it be insane to try to marry that with deliver? ;) - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRZC95XEjvBPtnXfVAQJgDQP+PxNPZ2453Bb8poBbwtgKAZjwmAJnX4L3 SzipzaoEE8/P8oj/sRwwRO19ViTPmXGZTgQQTF8ipqNL2YAL73QlyeLypzu0ZBBi WyplPkgFlgMeS5rnk9ibyejerO+JdsZt6zKnyKDqdhnhVsgTwvzMsNlu6MaWqtl8 fXPd5Gur6+M= =HGgh -----END PGP SIGNATURE-----

4 5

[Dovecot] Client transaction logging in dovecot.
by Tan Shao Yi 05 Jan '07

05 Jan '07

Hi, Seasons greetings! :) May I know if it's possible to log the commands issued by clients in dovecot? For instance, RETR and DELE commands in POP3 and their equivalent in IMAP? I can't seem to be able to find the appropriate configuration key. Thanking in advance. Cheers. Tan Shao Yi

2 3

[Dovecot] Problems with dovecot-sieve on Debian Etch using dovecot LDA
by Samir M. Nassar 05 Jan '07

05 Jan '07

I am running debian etch with dovecot 1.0 rc15 from the debian repository with postfix 2.3 I am using virtual users in a postgreSQL database as taken from the dovecot wiki while making use of the password field for authentication I am using deliver as LDA and I am attempting to use the sieve plugin but try as I might I can't seem to get it working. Am I wrong in thinking that a sieve daemon should become active when dovecot starts? Here is my .dovecot.sieve require "fileinto"; if address :is "from" "foo@example" { fileinto ".INBOX.test"; } else { # The rest goes into INBOX # default is "implicit keep", we do it explicitly here keep; } Here is my dovecot.conf: base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/info.log log_timestamp: %Y-%m-%d %H:%M:%S syslog_facility: mail protocols: imaps listen: *:143 ssl_listen: ssl_disable: no ssl_ca_file: ssl_cert_file: xxxx.pem ssl_key_file: xxxx.pem ssl_key_password: ssl_parameters_regenerate: 168 ssl_cipher_list: ssl_verify_client_cert: no disable_plaintext_auth: no verbose_ssl: no shutdown_clients: yes nfs_check: yes version_ignore: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_user: dovecot login_greeting: Dovecot ready. login_log_format_elements: user=<%u> method=%m rip=%r lip=%l %c login_log_format: %$: %s login_process_per_connection: yes login_chroot: yes login_greeting_capability: no login_process_size: 32 login_processes_count: 3 login_max_processes_count: 128 login_max_connections: 256 valid_chroot_dirs: mail_chroot: max_mail_processes: 1024 verbose_proctitle: no first_valid_uid: xxxx last_valid_uid: xxxx first_valid_gid: xxxx last_valid_gid: xxxx mail_extra_groups: default_mail_env: mail_location: maildir:/home/%d/mailboxes/%n mail_cache_fields: flags mail_never_cache_fields: imap.envelope mail_cache_min_mail_count: 0 mailbox_idle_check_interval: 30 mail_debug: no mail_full_filesystem_access: no mail_max_keyword_length: 50 mail_save_crlf: no mail_read_mmaped: no mmap_disable: no mmap_no_write: no lock_method: fcntl maildir_stat_dirs: no maildir_copy_with_hardlinks: no mbox_read_locks: fcntl mbox_write_locks: dotlock fcntl mbox_lock_timeout: 300 mbox_dotlock_change_timeout: 120 mbox_min_index_size: 0 mbox_dirty_syncs: yes mbox_very_dirty_syncs: no mbox_lazy_writes: yes dbox_rotate_size: 2048 dbox_rotate_min_size: 16 dbox_rotate_days: 1 umask: 63 mail_drop_priv_before_exec: no mail_executable: /usr/lib/dovecot/imap mail_process_size: 256 mail_plugins: mail_plugin_dir: /usr/lib/dovecot/modules/imap mail_log_prefix: %Us(%u): imap_max_line_length: 65536 imap_capability: imap_client_workarounds: outlook-idle pop3_no_flag_updates: no pop3_enable_last: no pop3_reuse_xuidl: no pop3_lock_session: no pop3_uidl_format: pop3_client_workarounds: pop3_logout_format: top=%t/%p, retr=%r/%b, del=%d/%m, size=%s auth default: mechanisms: login realms: default_realm: cache_size: 0 cache_ttl: 3600 executable: /usr/lib/dovecot/dovecot-auth user: root chroot: username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ username_translation: username_format: %n@%d master_user_separator: anonymous_username: anonymous krb5_keytab: verbose: yes debug: yes debug_passwords: yes ssl_require_client_cert: no ssl_username_from_cert: no count: 1 worker_max_count: 30 process_size: 256 passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf deny: no pass: no master: no userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 438 user: group: master: path: /var/run/dovecot/auth-master mode: 438 user: group: Thank you very much, Samir M. Nassar

8 31

[Dovecot] file descriptor leak?
by Steven F Siirila 04 Jan '07

04 Jan '07

We are having problems with the latest Dovecot 1.0 (RC15) regarding file descriptors > 255 being handed off to fdopen() via crypt() via PAM(?). This is a problem on Solaris 10 due to the fact that the stdio library does not support file descriptors > 255 (in order to remain binary-compatibile with older binaries). Here are the messages we run into if we get too many (~250?) concurrent IMAP/POP sessions: Jan 3 13:03:14 hostname dovecot-auth[5799]: crypt: fdopen(265) failed: Too many open files Jan 3 13:03:14 hostname dovecot-auth[5799]: crypt: fdopen(265) failed: Too many open files Jan 3 13:03:15 hostname dovecot: auth(default): pam(username,10.1.1.1): Child process died Jan 3 13:03:15 hostname dovecot: auth(default): PAM: Child 5799 died with signal 11 Questions: 1) Is there a file descriptor leak, or are there supposed to be this many open pipes in dovecot-auth? (master dovecot has way more than 256 at this point, but apparently does not use stdio.) 2) Has anyone tried compiling Dovecot in 64-bit mode (-xarch=v9)? I have tested the fact that this removes the >255 fd limitation in Solaris 9/10. 3) Has anyone even run into this problem on Solaris? I imagine anyone with more than 250 or so simultaneous IMAP/POP sessions would have had to run into it by now. 4) Anyone have any suggested workarounds (besides compiling in 64-bit mode)? We have upwards of 4500 simultaneous IMAP connections alone on some of our servers (running UW IMAP still), so we obviously need to address this problem before we can fully deploy dovecot in our environment. -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 4

[Dovecot] Too many open files
by Daniel Cox 04 Jan '07

04 Jan '07

I am running Dovecot 1.0rc15 on NetBSD 3.1 with only a few connections. It is built from pkgsrc-2006Q3, with mail/dovecot/ updated to HEAD. kqueue is a default build option - I haven't tried without yet. Mail directories/indexes are on a Linux 2.6.16.29 NFS file system, I have set these options and it performs well: mmap_disable=yes lock_method=fcntl FYI. rc7 had very high CPU use with the same options, which rc15 seems to have fixed :-) I also have this problem with dovecot-nightly-20060225 (1.0beta3) on NetBSD 2.1RC3 using a local ffs file system. This appears in /var/log/maillog: Jan 4 18:44:42 server dovecot: pipe() failed: Too many open files # ps ax|grep dovecot 723 ?? Ss 2:14.15 /usr/pkg/sbin/dovecot 822 ?? S 0:07.79 dovecot-auth # sysctl proc.723.rlimit proc.723.rlimit.descriptors.soft = 64 proc.723.rlimit.descriptors.hard = 1772 If I change /etc/login.conf to contain: ----- default|default class:\ :openfiles-max=2048:\ :openfiles-cur=1024: ----- Then login as root and /etc/rc.d/dovecot restart, the new soft limit is applied which helps but only delays the error. I haven't worked out how to make this happen automatically on restart. NOTE: hard never goes above kern.maxfiles which is 1772 (I think the kernel needs to be recompiled to increase further). proc.21494.rlimit.descriptors.soft = 1024 proc.21494.rlimit.descriptors.hard = 1772 # fstat -p 21494 root dovecot 21494 45* pipe 0xcc4e0138 <- 0xcc4e0648 rn Shows an increasing number of pipe files open. This NetBSD 3.1 system is a test server which I can experiment with if there is anything further I can do to help find the problem. Thank you, Daniel.

2 1