August 2008 - dovecot

[Dovecot] 1.1.2 segfaults when using passdb passwd and md5 mechanism
by Miguel Filho 04 Aug '08

04 Aug '08

Setting passdb to passwd and enabling cram-md5 or digest-md5 makes dovecot crash. The documentation says that I can use md5 with passwd. I had to use strace to figure it, because dovecot segfaults and doesn't log the error. Using CenOS 5.2 x86_64 Regards, Miguel # dovecot -n # 1.1.2: /etc/dovecot.conf listen: 127.0.0.1 login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no mail_max_userip_connections(default): 5 mail_max_userip_connections(imap): 5 mail_max_userip_connections(pop3): 10 verbose_proctitle: yes first_valid_uid: 100 mail_debug: yes mail_executable: /mail/bin/resolv_mailbox.sh mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 auth default: mechanisms: plain login gssapi digest-md5 passdb: driver: passwd args: blocking=yes userdb: driver: passwd args: blocking=yes Backtrace: #0 0x0000000000410337 in hash_lookup (table=0x0, key=0xa85) at hash.c:159 node = <value optimized out> #1 0x0000000000405dae in log_it (log_io=0x1736ee00, line=0x1736f922 "DIGEST-MD5 mechanism can't be supported with given passdbs", continues=false) at log.c:128 process = <value optimized out> log_type = LOG_TYPE_FATAL #2 0x0000000000405e48 in log_write_pending (log_io=0x1736ee00) at log.c:51 _data_stack_cur_id = 3 line = 0x1736f920 "\001FDIGEST-MD5 mechanism can't be supported with given passdbs" #3 0x00000000004060e8 in log_read (log_io=0x1736ee00) at log.c:176 data = <value optimized out> line = <value optimized out> size = 0 ret = <value optimized out> #4 0x0000000000406188 in log_deinit () at log.c:316 next = (struct log_io *) 0xa85 #5 0x000000000040335d in auth_process_destroy (p=0x1736ee60) at auth-process.c:345 iter = <value optimized out> key = (void *) 0x6 value = <value optimized out> pos = <value optimized out> #6 0x00000000004034f9 in auth_process_input (process=0x1736ee60) at auth-process.c:266 line = <value optimized out> #7 0x0000000000412df8 in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:201 ctx = <value optimized out> event = (const struct epoll_event *) 0x1736ef0c list = (struct io_list *) 0x17370aa0 io = (struct io_file *) 0x17370a60 tv = {tv_sec = 0, tv_usec = 970535} events_count = <value optimized out> t_id = 2 msecs = <value optimized out> ret = 3 i = 1 call = <value optimized out> #8 0x0000000000411fad in io_loop_run (ioloop=0x1736eab0) at ioloop.c:308 No locals. #9 0x0000000000409f4f in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:558 _data_stack_cur_id = 0 ---Type <return> to continue, or q <return> to quit--- exec_protocol = 0x0 exec_args = (const char **) 0x0 foreground = <value optimized out> ask_key_pass = false log_error = false dump_config = false dump_config_nondefaults = false i = <value optimized out> #10 0x00002b11b72cc8b4 in __libc_start_main () from /lib64/libc.so.6 No symbol table info available. #11 0x0000000000402eb9 in _start () No symbol table info available. -- http://osysadmin.blogspot.com

2 1

[Dovecot] Dovecot doesn't read users and passwords from config files
by Marco Fioretti 04 Aug '08

04 Aug '08

Greetings, I am setting up Dovecot 1.0.15 on my home Fedora Core 8 pc ONLY to access my mail archives across several mail clients. No access from the internet is possible or needed here. I cannot log in with any client, the login always fails. The reason, as I understand, is that when dovecot starts it doesn't read any user name from the userdb file, so when I try to login it doesn't recognize my name and so doesn't even try to verify the password: maillog excerpt: Aug 3 00:06:11 polaris dovecot: Dovecot v1.0.15 starting up Aug 3 00:06:11 polaris dovecot: auth(default): passwd-file /etc/local_dovecot_passwords: Read 0 users Aug 3 00:06:11 polaris dovecot: auth(default): passwd-file /etc/local_dovecot_users: Read 0 users Aug 3 00:06:12 polaris dovecot: auth(default): new auth connection: pid=5150 Aug 3 00:06:12 polaris dovecot: auth(default): new auth connection: pid=5148 Aug 3 00:06:12 polaris dovecot: auth(default): new auth connection: pid=5149 Aug 3 00:06:26 polaris dovecot: auth(default): client in: AUTH#0111#011PLAIN#011service=IMAP#011secured#011lip=127.0.0.1#011rip=127.0.0.1#011resp=AG1hcmNvAGdpZ2V0dG8= Aug 3 00:06:26 polaris dovecot: auth(default): passwd-file(marco,127.0.0.1): lookup: user=marco file=/etc/local_dovecot_passwords Aug 3 00:06:26 polaris dovecot: auth(default): passwd-file(marco,127.0.0.1): unknown user Aug 3 00:06:27 polaris dovecot: auth(default): client out: FAIL#0111#011user=marco Aug 3 00:06:27 polaris dovecot: imap-login: Disconnected: user=<marco>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured the dovecot.conf file, purged by comments, is below. What am I missing? TIA, Marco ############################################################## protocols = imap listen = localhost:143 mail_location = maildir:/home/marco/.MAIL/home_imap/ protocol imap { } protocol pop3 { } protocol lda { postmaster_address = postmaster(a)example.com } auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain login passdb passwd-file { args = /etc/local_dovecot_passwords } userdb passwd-file { args = /etc/local_dovecot_users } user = root } dict { } plugin { } ################################################### the local_dovecot_passwords and local_dovecot_users files are identical, and have permission 644: marco:{PLAIN}thepassword:500:500::/home/marco/.MAIL/home_imap/ -- Reality is for those who lack imagination

2 5

[Dovecot] Server power loss and "Dovecot is already running with PID xxx"
by Pekka Savola 04 Aug '08

04 Aug '08

Hi, I'm running Dovecot 1.0.7 (with various patches) on CentOS 5.2. The server has suffered a couple of power loss events. Dovecot is run as a standalone server. The problem is that dovecot refuses to start up at boot because the PID file from before the power loss is left behind. The message is as follows: $ /sbin/service dovecot start Starting Dovecot Imap: Error: Dovecot is already running with PID 10825 (read from /var/run/dovecot/master.pid) Fatal: Invalid configuration in /etc/dovecot.conf [FAILED] (Note: there is nothing wrong in the configuration file so the error message is somewhat misleading.) I looked at the release notes of 1.0.xx releases and they didn't mention this. Is this already a known problem? Should the start-up logic be made more robust (e.g. check whether a process corresponding to the PID actually exists)? -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

4 6

[Dovecot] 1.1.2: imap crash with SIGSEGV
by Ralf Hildebrandt 04 Aug '08

04 Aug '08

GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... Reading symbols from /lib/i686/cmov/libdl.so.2...Reading symbols from /usr/lib/debug/lib/i686/cmov/libdl-2.7.so...done. done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /lib/i686/cmov/libc.so.6...Reading symbols from /usr/lib/debug/lib/i686/cmov/libc-2.7.so...done. done. Loaded symbols for /lib/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.7.so...done. done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/local/lib/dovecot/imap/lib10_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_trash_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_trash_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_fts_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_fts_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib21_fts_squat_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib21_fts_squat_plugin.so Core was generated by `/usr/local/libexec/dovecot/imap'. Program terminated with signal 11, Segmentation fault. [New process 23474] #0 mail_transaction_log_file_lock (file=0x0) at mail-transaction-log-file.c:257 257 if (file->locked) #0 mail_transaction_log_file_lock (file=0x0) at mail-transaction-log-file.c:257 #1 0x080ba2fd in mail_transaction_log_lock_head (log=0x91cfd68) at mail-transaction-log.c:419 #2 0x080ba36d in mail_transaction_log_sync_lock (log=0x91cfd68, file_seq_r=0xbff348a4, file_offset_r=0xbff34880) at mail-transaction-log.c:451 #3 0x080c44bb in mail_index_fsck (index=0x91cf828) at mail-index-fsck.c:424 #4 0x080b0296 in mail_index_map (index=0x91cf828, type=MAIL_INDEX_SYNC_HANDLER_HEAD) at mail-index-map.c:888 #5 0x080acde3 in mail_index_try_open (index=0x91cf828) at mail-index.c:290 #6 0x080ad0a7 in mail_index_open (index=0x91cf828, flags=49, lock_method=FILE_LOCK_METHOD_FCNTL) at mail-index.c:338 #7 0x080a1112 in index_storage_mailbox_open (ibox=0x91d02b0) at index-storage.c:383 #8 0x0807094b in maildir_open (storage=0x91bacc0, name=0x91bf6ee "Drafts", flags=0) at maildir-storage.c:448 #9 0x08070ab4 in maildir_mailbox_open (_storage=0x91bacc0, name=0x91bf6ee "Drafts", input=0x0, flags=0) at maildir-storage.c:512 #10 0xb7ea61ca in mail_log_mailbox_open (storage=0x91bacc0, name=0x91bf6ee "Drafts", input=0x0, flags=0) at mail-log-plugin.c:450 #11 0xb7eb761a in quota_mailbox_open (storage=0x91bacc0, name=0x91bf6ee "Drafts", input=0x0, flags=0) at quota-storage.c:366 #12 0x080a51d9 in mailbox_open (storage=0x91bacc0, name=0x91bf6ee "Drafts", input=0x0, flags=0) at mail-storage.c:459 #13 0x08060c89 in cmd_select_full (cmd=0x91bb5f0, readonly=false) at cmd-select.c:32 #14 0x08060e69 in cmd_select (cmd=0x91bb5f0) at cmd-select.c:87 #15 0x0806271c in client_command_input (cmd=0x91bb5f0) at client.c:580 #16 0x080627b3 in client_command_input (cmd=0x91bb5f0) at client.c:629 #17 0x08062d6d in client_handle_input (client=<value optimized out>) at client.c:670 #18 0x080631ee in client_input (client=0x91bb3a8) at client.c:725 #19 0x080dd730 in io_loop_handler_run (ioloop=0x91b79b0) at ioloop-epoll.c:201 #20 0x080dcc10 in io_loop_run (ioloop=0x91b79b0) at ioloop.c:308 #21 0x0806b35a in main (argc=152894696, argv=0xbff34f34, envp=0xbff34f3c) at main.c:293 -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de "FOOT-AND-MOUTH BELIEVED TO BE FIRST VIRUS UNABLE TO SPREAD THROUGH MICROSOFT OUTLOOK Researchers Shocked to Finally Find Virus That Email App Doesn't Like".

2 2

[Dovecot] related, but off-topic: how to allow users to change password?
by Sahil Tandon 04 Aug '08

04 Aug '08

My dovecot is currently configured to authenticate vs. a userdb/passdb passwd-file that contains, for each user: username:passhash:5000:5000::/path/to/home::userdb_mail=/path/to/maildir Is it possible to let users authenticate and change their passwords? There are some webmail client add-ons that allow such things if users are system accounts or in a MySQL/LDAP db. Does anyone else use passdb/userdb passwd-files like above and have a method for allowing users to change their passwords from the web? Sorry for the slightly off-topic question, but hoping another Dovecot admin has solved this problem. Preference is to not to be tied to any particular webmail client just for this change password feature.

3 7

[Dovecot] Thunderbird and Dovecot on FC5 taking a long time to retrieve message
by Bruen, Mark 02 Aug '08

02 Aug '08

I'm running FC5 (2.6.15-1.2054_FC5smp) and Dovecot dovecot-1.0-0.beta8.2.fc5 with Thunderbird 2.0.0.16. I set up imap (dovecot) so I can access my mail locally or remotely. It seems to take a very long time (minutes sometimes) for an Email to be retrieved after I select it in the folder list and/or in the Email list locally or remotely. I've traced the imap process and found it doing a lot of reading (read() system calls) for a long time. I do have a high message count in some of these folders (i.e.: 20000 or so). Is there any way to improve performance (use more memory, cache indexes, tune I/O parameters, etc...) ? Thanks. -Mark

2 1

[Dovecot] POP3 locking
by Adrian Overbury 02 Aug '08

02 Aug '08

I'm trying to understand what dovecot's behavior will be in a given scenario to see if it will work as a (hopefully better) replacement for the home-grown pop3 server we currently use. User A is on a slow dialup connection, and uses, oh, let's say Outlook, since that's where most of our problems seem to spring from. User A uses outlook to download his mail over pop3. Half way through downloading a particularly large message, Outlook decides that the whole process isn't happening fast enough, so it opens another connection to the server and tries to download (potentially) the same message again. Now, our current server establishes a lock on the mailbox, and when that second connection happens it simply responds that there's no messages to collect... we used to have it terminate the connection, but this brings up confusing error messages on User A's client, and they call up and complain -- not an ideal situation. I've got a dovecot installation on my testing server, and I think I've set everything up correctly; it authenticates from my LDAP database, finds the home directory, lists the mail, all that... I believe somewhere it there it uses fcntl to establish an advisory lock on the mailbox (oh, we're using Maildir, by the way). I'm not sure where, though, or how long the lock persists for, or what its actual purpose is, because my tests show me that I can log the same users in with two concurrent sessions and get the same message twice. It's probably a fault in my understanding of how locking in user sessions of a pop3 server should work, but that doesn't sound right to me. Can someone explain if what I'm seeing is correct, or what problem it may be symptomatic of? Does dovecot even do concurrent-user-session locking? So far I've enjoyed playing with dovecot -- far more than the current server we use. I'd like to use it as our primary pop3 server, but preventing users from having concurrent sessions and getting the same message more than once, and keeping them from seeing errors because of their client trying to open multiple sessions is important. Oh, and I'm user dovecot 1.0.beta3, since I don't really have the option of upgrading the OS on my mail servers any time soon. Adrian

9 13

[Dovecot] Quota warnings wrong behaviour (1.1.2)
by Włodek Waligórski 02 Aug '08

02 Aug '08

Hi, I use the latest version of dovecot 1.1.2. Thanks to the excellent docs I managed to get everything working so far, but ... I'm experiencing such strange behaviour when user gets over 90% of quota (the threshold is such): 1. user uses say 89% of his ~/Maildir 2. message arrives that increases quota usage to 92% 3. quota_warning is _NOT_ triggered 4. user deletes the surplus message and gets back to 89% (quota_rule2: Trash:ignore) 5. quota_warning is triggered and quota warning message arrives So the event gets triggered when user passes the quota threshold, but from a "wrong direction". I would expect that message should arrive together with the surplus message. Below I paste my dovecot.conf and "./configure" opts: -------------------cut--------------------------------------- # dovecot -n # 1.1.2: /usr/local/etc/dovecot.conf base_dir: /usr/local/var/run/dovecot/ log_path: /dev/stderr info_log_path: /dev/stderr log_timestamp: listen: 127.0.0.1:143 ssl_listen: 0:993 ssl_cert_file: /var/qmail/control/servercert.pem ssl_key_file: /var/qmail/control/servercert.pem ssl_cipher_list: ALL:!LOW verbose_ssl: yes login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 89 last_valid_uid: 89 mail_uid: vpopmail mail_gid: vchkpw mail_location: maildir:~/Maildir mail_debug: yes mail_plugins: quota imap_quota imap_client_workarounds: outlook-idle auth default: user: vpopmail verbose: yes debug: yes passdb: driver: vpopmail args: quota_template=quota_rule=*:backend=%q userdb: driver: vpopmail plugin: quota: maildir quota_rule: ?:storage=110485760 quota_rule2: Trash:ignore quota_warning: storage=90%% /usr/local/bin/imap-quota-warning 90 ----------------------------------------------------------------------------------- # grep "./configure" config.log | head -1 $ ./configure --disable-ipv6 --without-passwd --without-passwd-file --without-shadow --without-pam --without-checkpassword --without-bsdauth --without-gssapi --without-sia --without-ldap --with-vpopmail --without-static-userdb --without-prefetch-userdb --without-sql --without-pgsql --without-mysql --without-sqlite --with-ssl=openssl ------------------------------------------------------------------------------------ My system is x86 Debian-testing, SMP. -Włodek

1 0

[Dovecot] Permission denied creating inbox file in /var/mail
by Steve Ochani 01 Aug '08

01 Aug '08

Hello all, I'm using dovecot version 1.07 on CentoOS 5 (clone of RHEL 5). When there is no existing mbox file for a user in /var/mail I get the following error: --------------- Jul 31 16:32:32 newnewton dovecot: imap-login: Login: user=<testm2>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured Jul 31 16:32:32 newnewton dovecot: IMAP(testm2): open(/var/mail/testm2, O_CREAT) failed: Permission denied Jul 31 16:32:32 newnewton dovecot: IMAP(testm2): access() failed with mbox file /var/mail/testm2: No such file or directory Jul 31 16:32:32 newnewton dovecot: IMAP(testm2): stat() failed with mbox file /var/mail/testm2: No such file or directory Jul 31 16:32:32 newnewton dovecot: IMAP(testm2): Connection closed ---------------- My persimmons on /var/mail (which is a symlink to /var/spool/mail) : drwxrwxr-x 2 root mail 4096 Jul 31 16:32 mail I have tried adding the mail group as mail_privileged_group, the output of dovecot -n : -------------------- # 1.0.7: /etc/dovecot.conf login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_privileged_group: mail mail_location: mbox:~/IMAPmail:INBOX=/var/mail/%u mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd -------------------- Here is the permission on /etc/dovecot.conf -rw-r--r-- 1 root root 42833 Jul 31 15:30 /etc/dovecot.conf I've searched google and the mailing list archive and tried the couple of things commonly suggested. As for a test I changed perms on /var/spool/mail to 777 and then dovecot made the inbox file. The file ended up being owned by the user and the group owner was the group that the user belongs to, not mail. When I create new users using useradd there is a 0 byte file created in /var/mail for the user but I use scripts to create student accounts every semester (about 10,000) so I'm trying to avoid having to add more things that the script will have to create. Any help is greatly appreciated. Thanks -Steve O.

3 4

[Dovecot] dovecot.sieve file location?
by kbajwa 01 Aug '08

01 Aug '08

CentOS 5.2 Postfix-2.3.3 Dovecot-1.1.1 Dovecot.Sieve-1.1.5 I have setup with: home_mailbox = Maildir/ (/etc/postfix/main.cf) & mail-location = maildir:~/Maildir (/etc/dovecot.conf) I have created a 'test' user to test Sieve 'Vacation' setup. My questions are: 1. Which folder '.dovecot.sieve' script is copied into? Is it 'home/test' -or- 'home/test/Maildir' or someplace else? 2. '.dovecot.sieve' script parameter ":days 1" means that the reply is sent once a day. Is it possible to send the reply 'immediately'? Kirti

2 1