- dovecot - dovecot.org

[Dovecot] dovecot rejecting auth after working a few times
by Matthew Thorley 15 Feb '08

15 Feb '08

Greetings all, I've got a dovecot server up that works just fine for a few minutes, and then suddenly won't authenticate users. On top of it, it keeps spawning dovecot-auth processes that won't go away. If any one has seen this or knows what's causing it I sure could use some help. Thanks much. I've included my relevant config info below -- Matthew Thorley dovecot --version 1.0.beta3 grep -v \# /etc/dovecot/dovecot.conf | grep -vE "^$" protocols = imaps pop3s listen = * ssl_disable = no ssl_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key_file = /etc/ssl/private/ssl-cert-snakeoil.key disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " login_user = dovecot mail_extra_groups = mail mail_debug = yes default_mail_env = maildir:/var/mail/%u protocol imap { } protocol pop3 { pop3_uidl_format = %v-%u } auth_verbose =yes auth_debug = yes auth_debug_passwords = yes auth_worker_max_count = 10 auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } plugin { }

3 9

[Dovecot] Managesieve with local accounts
by Michael Baecker 15 Feb '08

15 Feb '08

Hello, I've got a problem using the plugin managsieve in dovecot (1.0.10 on gentoo linux). I use local unix accounts on a linux machine, one for each user with a .maildir in there home directory. Here is a snippet of the logging. Feb 14 20:17:48 obelix dovecot: Dovecot v1.0.10 starting up Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out Feb 14 20:19:04 obelix dovecot: managesieve-login: Disconnected: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS I don't get the sieve script and can't also save a script. It looks quite ugly "login: Disconnected" in the last line. Here is my config file (without the comments): protocols = imap managesieve listen = * disable_plaintext_auth = yes ssl_disable = no ssl_cert_file = /etc/ssl/dovecot/server.pem ssl_key_file = /etc/ssl/dovecot/server.key mail_location = maildir:~/.maildir mail_debug = no verbose_proctitle = yes first_valid_uid = 10 protocol imap { } protocol pop3 { } protocol managesieve { sieve=~/.dovecot.sieve sieve_storage=~/sieve listen = *:2000 } protocol lda { postmaster_address = postmaster(a)baecker.com mail_plugins = cmusieve } auth default { mechanisms = plain passdb pam { args = "*" } userdb passwd { args = blocking=yes } user = root socket listen { client { path = /var/spool/postfix/auth/dovecot mode = 0666 user = postfix group = postfix } master { path = /var/spool/postfix/auth/auth-master mode = 0666 user = postfix group = postfix } } } dict { } plugin { } The client worked already with pysieved over xinetd (Horde Ingo and squirrelmail with avelsieve worked). But this isn't realy a solution. Can anybody help me? Do you need anything, I didn't wrote her? Thanks in advance Michael Baecker

2 2

[Dovecot] Finding Dovecot 1.1 hg
by Asheesh Laroia 15 Feb '08

15 Feb '08

When I do either: $ hg clone http://hg.dovecot.org/dovecot/1.1/ or $ hg clone http://hg.dovecot.org/dovecot/ and cd into the resulting directory ("1.1/" or "dovecot/") and do autogen.sh and configure, ./configure tells me at the end: NOTE: This is the UNSTABLE development branch of Dovecot v1.2. I wanted Dovecot v1.1, I thought, to help Timo get that out the door! Timo? -- Asheesh. -- Leibowitz's Rule: When hammering a nail, you will never hit your finger if you hold the hammer with both hands.

4 4

[Dovecot] Solaris 10 / 1.1.beta15 imap cores
by Tomi Vainio 15 Feb '08

15 Feb '08

Hi, I've been using 1.0 but moved to beta to see if it works before release. Both b14 and b15 dies sometimes when accessing folders. Last time I fixed this by moving one message from folder to another and then back. Next I'm trying to build this with debugging enabled. Tomppa > Feb 14 11:52:33 dovecot: [ID 107833 mail.crit] IMAP(tomppa): file message-parser.c: line 674: assertion failed: (ctx->part->physical_pos >= ctx->input->v_offset) > Feb 14 11:52:34 genunix: [ID 603404 kern.notice] NOTICE: core_log: imap[5995] core dumped: /v/tmp/core.imap.5995 > Feb 14 11:52:40 dovecot: [ID 107833 mail.crit] IMAP(tomppa): file message-parser.c: line 674: assertion failed: (ctx->part->physical_pos >= ctx->input->v_offset) > Feb 14 11:52:40 genunix: [ID 603404 kern.notice] NOTICE: core_log: imap[5997] core dumped: /v/tmp/core.imap.5997 > Feb 14 11:52:47 dovecot: [ID 107833 mail.crit] IMAP(tomppa): file message-parser.c: line 674: assertion failed: (ctx->part->physical_pos >= ctx->input->v_offset) > Feb 14 11:52:47 genunix: [ID 603404 kern.notice] NOTICE: core_log: imap[5999] core dumped: /v/tmp/core.imap.5999 > )# dbx /usr/local/libexec/dovecot/imap /v/tmp/core.imap.5999 > For information about new features see `help changes' > To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc > Reading imap > core file header read successfully > Reading ld.so.1 > Reading librt.so.1 > Reading libnsl.so.1 > Reading libsocket.so.1 > Reading libsendfile.so.1 > Reading libc.so.1 > Reading libaio.so.1 > Reading libmd.so.1 > Reading libc_psr.so.1 > Reading 8859-1%UTF-8.so > program terminated by signal ABRT (Abort) > 0xff1c5c14: __lwp_kill+0x0008: bcc,a,pt %icc,__lwp_kill+0x18 ! 0xff1c5c24 > (dbx) where > =>[1] __lwp_kill(0x0, 0x6, 0x0, 0x6, 0xfc00, 0x0), at 0xff1c5c14 > [2] raise(0x6, 0x0, 0x0, 0xff1a8c20, 0xffffffff, 0x6), at 0xff164c44 > [3] abort(0x2, 0x1, 0xe83c4, 0xad324, 0xff1f1318, 0x0), at 0xff1410f8 > [4] 0xaa4f0(0x2, 0x100400, 0xd5400, 0x100ba0, 0xea000, 0xea078), at 0xaa4f0 > [5] i_panic(0xd4a6c, 0xea000, 0x2a2, 0xfeb88, 0xea16c, 0xaa464), at 0xa9de4 > [6] 0xa2ec4(0x157170, 0xffbff544, 0xd4800, 0x0, 0x1380e0, 0xfe800), at 0xa2ec4 > [7] message_parser_parse_next_block(0x157170, 0xffbff544, 0x1, 0x0, 0xfe800, 0xa2d4c), at 0xa3064 > [8] 0xa4554(0x151158, 0x14fc88, 0x138090, 0xffbff534, 0x80000000, 0xd4cc4), at 0xa4554 > [9] message_search_msg(0x151158, 0x14fc88, 0x137ff0, 0x14fc60, 0xe0, 0x60), at 0xa45d4 > [10] 0x67a40(0x10c588, 0x10, 0x10c588, 0x14fb38, 0x151158, 0xffbff6e4), at 0x67a40 > [11] mail_search_args_foreach(0x10c588, 0x679a4, 0xffbff6e4, 0x1, 0x1, 0xffffffff), at 0x6f688 > [12] 0x67d68(0x10c550, 0x137b68, 0x67800, 0xffffffff, 0xffffffff, 0x14fc88), at 0x67d68 > [13] index_storage_search_next_nonblock(0x137b68, 0x137be8, 0x1, 0xffbff81f, 0xea000, 0x113b28), at 0x69368 > [14] 0x26008(0x10c500, 0x40000000, 0x2, 0x10c5c8, 0x80000000, 0xc2000), at 0x26008 > [15] 0x262c8(0x10c500, 0x100550, 0x1, 0xea000, 0xea058, 0x10c2a0), at 0x262c8 > [16] 0xb1c10(0x109518, 0x10a610, 0x3, 0x3e8, 0xea0b8, 0xd64f8), at 0xb1c10 > [17] io_loop_handle_timeouts(0x109518, 0x3, 0x0, 0x10624c00, 0x0, 0x0), at 0xb1c70 > [18] io_loop_handler_run(0x109518, 0x0, 0x2, 0x29414, 0xd6400, 0x10a5b0), at 0xb2380 > [19] io_loop_run(0x80, 0x0, 0x80000000, 0x80000000, 0x10a5b0, 0x109518), at 0xb1cc4 > [20] main(0x100800, 0x10c2a0, 0xe8c00, 0x10000, 0x100978, 0x1008c4), at 0x330ac > (dbx) # /usr/local/sbin/dovecot -n # 1.1.beta15: /usr/local/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 640). Either grow the limit or change login_max_processes_count and max_mail_processes settings base_dir: /var/run/dovecot/ ssl_cert_file: /etc/mail/certs/imapd.pem ssl_key_file: /etc/mail/certs/key.pem disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 100 mail_location: mbox:~/Posti/:INBOX=/var/mail/%u:INDEX=/var/dovecot/indexes/%u auth default: passdb: driver: pam userdb: driver: passwd

3 3

[Dovecot] Best way to push Squat forward
by Asheesh Laroia 15 Feb '08

15 Feb '08

Timo, you mentioned you're getting tired of fighting Squat bugs lately. Does that mean you know all the bugs, and just need time to find and fix them? Or should instead I try harder to find bugs by using Dovecot 1.1 on a daily basis, and then sending you copies of mails that break it, like http://www.dovecot.org/list/dovecot/2007-October/026179.html ? -- Asheesh. -- Parting is such sweet sorrow. -William Shakespeare

1 0

[Dovecot] Deleting messages from MailDir
by Matt Richards 14 Feb '08

14 Feb '08

Hello, I have dovecot running with MailDir as a backend to store email and I would like to remove mail that is older that 30 days. I can do this by running 'find' on the MailDir but will this cause any issues with dovecot? Thanks, Matt. -- Matt Richards

10 25

[Dovecot] Restrict user on IMAP or POP
by Sebastien Roy 14 Feb '08

14 Feb '08

Hey guys, Is it possible to deny a user on POP or IMAP! For example, on the primary server we use POP3 and IMAP but how I can force a user to use POP3 and be unable to authenticate on IMAP ? Thanks Sebastien

1 0

[Dovecot] Apple Mail for 10.4/Shadow/SSL -> Problem.
by Phredd Groves 14 Feb '08

14 Feb '08

I have recently gotten Dovecot running on my Solaris 5.8 mail server in order to replace UW IMAP. I'm currently testing it out with mail clients popular amongst my users. It's been working very well, with one vital exception. Apple Mail on OS X 10.4 is not completing authentication (I don't think it's even getting that far). All I'm seeing in the syslog for attempts with Apple Mail (for both IMAP and POP3) is a single line per attempt: Jan 29 17:20:01 paradox dovecot: [ID 107833 mail.info] imap-login: Disconnected: rip=X.X.X.X, lip=Y.Y.Y.Y, TLS handshake This is even with verbose for auth and for SSL. I know syslog plays well with mail.warning and mail.debug and mail.notice, so I'm not quite sure what's going on there. Nothing shows up in authlog or messages either. The OS X 10.5 Apple mail client works just fine, as do Thunderbird and even Eudora. There did not seem to be any coverage of this when I googled and went through the dovecot archives, so I'm thinking it might be some weird interaction between that particular client and the SSL/shadow implementation in dovecot (Things work in UW IMAP for the client). Any suggestions? thanks! # /usr/local/sbin/dovecot -n # 1.0.10: /usr/local/etc/dovecot.conf protocols: imaps pop3s ssl_listen(default): *:997 ssl_listen(imap): *:997 ssl_listen(pop3): *:998 ssl_cert_file: /usr/local/ssl/certs/imapd.pem ssl_key_file: /usr/local/ssl/certs/imapd.pem verbose_ssl: yes shutdown_clients: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting_capability(default): no login_greeting_capability(imap): no login_greeting_capability(pop3): yes first_valid_uid: 100 mail_location: mbox:~/mail:INBOX=/var/mail/%u mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: verbose: yes passdb: driver: shadow userdb: driver: passwd Phredd Groves -- Systems Administrator Psychology Department Columbia University [212] 854-8167

2 2

[Dovecot] ManageSieve v0.10.0 released for Dovecot 1.1.beta15
by Stephan Bosch 13 Feb '08

13 Feb '08

Hello Dovecot users, I finally managed to upgrade the ManageSieve implementation to dovecot-1.1. This also resulted in major restructuring of the code. The actual ManageSieve implementation is now available as a separate package and the patch now only contains the changes to the dovecot-1.1 tree that are necessary to use the ManageSieve service. The patch and the new package no longer contain another copy of the CMU Sieve code; the package depends on dovecot-sieve-1.1 for the sieve implementation. Change Log v0.10.0 ------------------- (Changed version scheme from vY to vX.Y.Z) * Upgraded to Dovecot 1.1: - The actual managesieve implementation is now a separate package. The dovecot tree still needs to be patched though to make dovecot recognize the new managesieve service. - Incorporated changes to imap/imap-login into the equivalent managesieve processes. - Removed cmusieve implementation from managesieve sources. It is now linked externally from the dovecot-sieve-1.1 package. - Restructured README.managesieve file into separate README, NEWS, TODO, DESIGN and INSTALL files. * Added support for new libsieve implementation (to be released). This package can be compiled with either the new or the old Sieve implementation (autodetected). If the new Sieve becomes stable, this package will be merged with it to make a single package for Dovecot Sieve support. Installation ------------ Patch your dovecot-1.1.beta15 source tree with the following patch: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.beta15-managesieve-0.10.0.d… The patched Dovecot can be compiled and installed as usual. Download and unpack the dovecot-1.1-managesieve package: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.0.tar.gz The README and INSTALL files therein should provide enough information to build, install and configure the ManageSieve service. After patching, your Dovecot source tree contains an updated dovecot-example.conf with a configuration example. The documentation is still pretty sparse however, but I intend to build a wiki page in the near future. Have fun testing the Dovecot ManageSieve service. Don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

2 1

[Dovecot] convert-tool, exit code wrong?
by Ingo Rogalsky 13 Feb '08

13 Feb '08

Hello, I use convert-tool regularly for converting mbox based mail accounts to maildir based mail accounts. Today I tuned my convert script around convert-tool. I'm irritated about the exit codes. It seems, they should be inverted or am I wrong? $ /opt/dovecot-1.0.10/bin/convert-tool rogtest1 /home/mail01/rogtest1 mbox:/home/rogtest1/mail maildir:/home/mail01/rogtest1/Maildir 1 Error: Source storage not found $ echo $? 0 $ /opt/dovecot-1.0.10/bin/convert-tool rogtest1 /home/mail01/rogtest1 mbox:/home/rogtest1/mail maildir:/home/mail01/rogtest1/Maildir 1 Info: Successfully converted $ echo $? 1 Ingo

3 2