December 2006 - dovecot

[Dovecot] Correct usage of NFS mounted Maildirs
by Fran Fabrizio 18 Jan '07

18 Jan '07

Dovecot 1.0RC15 running on Fedora Core 5 kernel 2.6.18-1.2257.fc5smp. A SLES10 server (kernel 2.6.16.21-0.8-smp) has the home directories on an ext3 partition mounted with options (rw,acl,user_xattr,usrquota) which is then exposed as an NFS mount with server side options (rw,no_root_squash,no_acl,async). The home directories include Maildirs to which postfix delivers. The Fedora Core 5 dovecot&postfix machine then mounts this NFS mount with options (rw,hard,intr) Dovecot variables: mmap_disable=yes lock_method=dotlock default_mail_env = maildir:~/Maildir:INDEX=/usr/local/dovecot/indexes/%u (only one dovecot server and wanted to see if local indices helped) I didn't turn off the attribute caching of NFS since I only have one dovecot server, I think the wiki said it was safe to leave on in this case. With this configuration, I am seeing a lot of NFS Stale Filehandle errors, even after moving the index files to a local disk. Here's an excerpt from the log: dovecot: Dec 22 11:23:06 Info: Dovecot v1.0.rc15 starting up dovecot: Dec 22 11:23:22 Info: imap-login: Login: user=<nfsuser1>, method=plain, rip=138.26.64.50, lip=138.26.64.5 dovecot: Dec 22 11:23:24 Info: imap-login: Login: user=<nfsuser1>, method=plain, rip=138.26.64.50, lip=138.26.64.5 dovecot: Dec 22 11:24:48 Info: imap-login: Login: user=<nfsuser1>, method=plain, rip=138.26.64.50, lip=138.26.64.5 dovecot: Dec 22 11:26:43 Error: IMAP(nfsuser1): inotify_add_watch(/nethome/facstaff/nfsuser1/Maildir/.Trash/new) failed: Stale NFS file handle dovecot: Dec 22 11:26:43 Error: IMAP(nfsuser1): inotify_add_watch(/nethome/facstaff/nfsuser1/Maildir/new) failed: Stale NFS file handle To be honest, I'm not 100% sure this is a dovecot problem, because I also see that I am getting stale filehandles when postfix tries to deliver the mail to the Maildir, but I'm curious as to whether this is because of something dovecot did because I have it misconfigured. Does anything about my dovecot config provide any clues as to what I might have done wrong? The NFS mounts are completely stable everywhere except within the Maildirs. From the shell, I can run a loop to call 'ls' 1000 times outside of a Maildir and it works fine. Inside a Maildir, I will get Stale NFS Filehandle errors before long. Does this sound like it could have something to do with my Dovecot config, given that it is happening even after I moved indices to the local disk (still getting stale filehandle errors on files like dovecot-keywords). I performed the following procedure: - shut down dovecot - did a rm-rf Maildir on my test account - unmounted the NFS mount /nethome/facstaff - remounted the NFS mount /nethome/facstaff - set the index files to be local in dovecot.conf and created that directory (/usr/local/dovecot/index/) - sent a few test mails to the user (to recreate the Maildir) - started dovecot - logged in (via Thunderbird) to account through dovecot. - read test message - deleted test message - opened shell to dovecot server - cd'ed into user's Maildir - ran 'ls' a few times. Got Stale Filehandle errors after a few. - back in Thunderbird, tried to read/move/delete other test mails, got the above errors in the log. If it's not a dovecot issue I know it's off-topic, but has anyone else seen similar? I might be imagining this, but I think the problem started when I moved from SLES9 to SLES10 for my fileserver (newer kernel, newer version of NFS, perhaps an incompatibility here?) Thanks, Fran

2 1

[Dovecot] Custom mail directory with LDAP
by Maykel Moya 18 Jan '07

18 Jan '07

For certain users, I have their mail boxes under /srv/mpop/<username>/Maildir. For the rest, I have their mail boxes under /srv/vmail/<username>/Maildir. mpop/ users are stored in LDAP, vmail/ users are local users so I discard the idea of set a fixed mail_location. In dovecot-ldap.conf I can't get the picture to set /srv/mpop/<username>/Maildir as mail. I'd tried user_attrs = /srv/mpop/uid/Maildir=mail but watching the logs I saw that a '/srv/mpop/uid/Maildir' is queried to the LDAP Server. Would be nice to have a user_global_mail equivalent to user_global_uid for LDAP user lookups. Regards, maykel

2 1

[Dovecot] auth unix sockets
by Uldis Pakuls 18 Jan '07

18 Jan '07

Hi, I'm working on "avelsieve" SqurrelMail plug-in to implement SIEVE "file" back end for dovecot. 1. My be someone my explain me, how to use client auth socket to authenticate against dovecot-auth unix socket. As fas as I understood login must be sent in form "user\0\user\0password" as base64 encoded string. pp code (I'm using socket used by postfix auth): -------------------- <?php $authstr = base64_encode('test@virtual.net\0test@virtual.net\0test'); $fp = fsockopen("unix:///var/spool/postfix/private/auth",0, $errno, $errstr, 30); if (!$fp) { echo "$errstr ($errno)<br />\n"; } else { $out = "$authstr\r\n"; fwrite($fp, $out); while (!feof($fp)) { echo fgets($fp, 128); } fclose($fp); } ?> ----------------------- Dovecot auth complains about syntax It seems 'auth mech' also is required. thus; how to correctly use dovecot client auth socket to authenticate? (some FAQ?, php sample code?) 2. [most important] dovecot LDA uses auth maser sockets to read userdb and get home directory path to deliver mail and locate sieve scripts. I need some home path to locate users sieve script. Wow to obtain it using dovecot auth sockets? Tnx Uldis

3 2

[Dovecot] Index corruption causes child process to die
by Juha Saarinen 16 Jan '07

16 Jan '07

My recent migration from Courier-IMAP to Dovecot has been marred by these errors: Oct 24 12:12:40 server dovecot: IMAP(juha): Fixed index file ~user/Maildir/.Geekzone/dovecot.index: first_recent_uid_lowwater 431 -> 430 Oct 24 12:12:40 server dovecot: IMAP(juha): Corrupted index file ~user/Maildir/.Geekzone/dovecot.index: Duplicate header extension keywords Oct 24 12:12:40 server dovecot: child 5786 (imap) killed with signal 11 They happen with Thunderbird 1.5.0.7 and I'm using Dovecot 1.0RC7 from the FreeBSD ports. I think the index corruption may be caused by Tbird's message filtering - I'm asking it to filter certain messages from INBOX to subfolders. When the error occurs, Tbird pops up an error message saying it can't connect to the mail server, but I don't lose any messages it seems. Instead, I get duplicates and even triplicates when I restart Tbird. Any work around for this? -- Juha http://www.geekzone.co.nz/juha

7 35

[Dovecot] segfault in RC15
by Cor Bosman 15 Jan '07

15 Jan '07

Hi all, ive seen a few segfaults in RC15. It's hard for me to reproduce but I was able to get a core when it happened with one of our customers. RC15 FreeBSD 4.10 X86 NFS/NetApp It's squirrelmail/webmail client. Can't reproduce it, cant turn on dovecot.rawlog because I dont know in advance which customer will hit this. See it about 5 times per hour, with thousands of logins per hour. Here's the backtrace.. Cor ------ Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libc.so.4...done. Reading symbols from /usr/local/lib/dovecot/imap/lib01_quota_plugin.so...done. Reading symbols from /usr/lib/librpcsvc.so.2...done. Reading symbols from /usr/local/lib/dovecot/imap/lib02_imap_quota_plugin.so...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 maildir_save_file_get_path (_t=0x80d72c0, seq=37) at maildir-save.c:242 242 i_assert(seq >= ctx->first_seq); (gdb) bt full #0 maildir_save_file_get_path (_t=0x80d72c0, seq=37) at maildir-save.c:242 _t = (struct mailbox_transaction_context *) 0x80d72c0 seq = 37 ctx = (struct maildir_save_context *) 0x0 mf = (struct maildir_filename *) 0x80d72c0 #1 0x80682ca in maildir_mail_get_virtual_size (_mail=0x80e9440) at maildir-mail.c:145 mail = (struct index_mail *) 0x80e9440 mbox = (struct maildir_mailbox *) 0x80d8c40 data = (struct index_mail_data *) 0x80e94a4 path = 0x80e94a4 "" fname = 0x80d72c0 "@\214\r\bà¶\f\b\004" virtual_size = 580366801855675066 flags = 19 #2 0x8097b22 in mail_get_virtual_size (mail=0x80e9440) at mail.c:68 mail = (struct mail *) 0x80d72c0 #3 0x805cf4d in fetch_rfc822_size (ctx=0x80de088, mail=0x80e9440, context=0x0) at imap-fetch-body.c:839 ctx = (struct imap_fetch_context *) 0x80d72c0 size = 135099072 #4 0x805b395 in imap_fetch (ctx=0x80de088) at imap-fetch.c:265 ctx = (struct imap_fetch_context *) 0x80de088 handlers = (struct imap_fetch_context_handler *) 0x80de1a8 ret = 1 #5 0x8056e0b in cmd_fetch (cmd=0x80db044) at cmd-fetch.c:171 cmd = (struct client_command_context *) 0x80db044 client = (struct client *) 0x80db000 ctx = (struct imap_fetch_context *) 0x80de088 args = (struct imap_arg *) 0x80dc048 search_arg = (struct mail_search_arg *) 0x80de050 messageset = 0x25 <Address 0x25 out of bounds> ret = 135099072 #6 0x805955a in cmd_uid (cmd=0x80db044) at cmd-uid.c:19 cmd = (struct client_command_context *) 0x80db044 cmd_name = 0x80dc0f8 "FETCH" #7 0x8059f45 in client_handle_input (cmd=0x80db044) at client.c:382 cmd = (struct client_command_context *) 0x80db044 client = (struct client *) 0x80db000 #8 0x805a01e in _client_input (context=0x80db000) at client.c:433 client = (struct client *) 0x80db000 cmd = (struct client_command_context *) 0x80db044 ret = 2 #9 0x80a9608 in io_loop_handler_run (ioloop=0x80d7000) at ioloop-poll.c:199 ctx = (struct ioloop_handler_context *) 0x80cb0a0 pollfd = (struct pollfd *) 0x2 tv = {tv_sec = 0, tv_usec = 888475} io = (struct io *) 0x80cb4a0 t_id = 2 msecs = 135099072 ret = 0 call = 135099072 #10 0x80a901d in io_loop_run (ioloop=0x80d7000) at ioloop.c:281 ioloop = (struct ioloop *) 0x80d7000 #11 0x8060f1d in main (argc=1, argv=0xbfbff624, envp=0xbfbff62c) at main.c:280 No locals.

2 17

[Dovecot] [minor] stale auth-worker sockets
by Luigi Rosa 09 Jan '07

09 Jan '07

I was fooling around the /var/run/dovecot directory and I noticed a lot of stale auth-worker.xxxxx sockets, probably left there by unexpected termination of old versions of Dovecot. Just to know who does what, have I to clean up the stale sockets, or a future version of Dovecot will get rid of this unused sockets? Ciao, luigi -- / +--[Luigi Rosa]-- \ Syntactic sugar causes cancer of the semi-colons;

2 1

[Dovecot] dovecot rc7 assert, core
by Jeff A. Earickson 09 Jan '07

09 Jan '07

Hi, Wow, I haven't had an assert/core in dovecot in a long time. Here goes: Setup: Solaris 10, dovecot built with gcc 4.1.1, imap and imaps only. User's home directory lives on a ZFS filesystem, but I don't think that makes a difference. So does every other user here (>3K). Assert: IMAP(mulepri): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) gdb backtrace and other poking at the core is attached. Jeff Earickson Colby College

2 1

[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] 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] 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