- dovecot - dovecot.org

[Dovecot] 1.0.rc23 released
by Timo Sirainen 22 Feb '07

22 Feb '07

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If pop3_uidl_format=%m, we generate a unique X-Delivery-ID header when saving mails to make sure the UIDL is unique. + PAM: blocking=yes in args uses an alternative way to do PAM checks. Try it if you're having problems with PAM. + userdb passwd: blocking=yes in args makes the userdb lookups be done in auth worker processes. Set it if you're doing remote NSS lookups (eg. nss_ldap problems are fixed by this). + If PAM child process hasn't responded in two minutes, send KILL signal to it (only with blocking=no) - IMAP: APPEND ate all CPU while waiting for more data from the client (broken in rc22) - mbox: Broken X-UID headers assert-crashed sometimes - mbox: When saving a message to an empty mbox file it got an UID which immediately got incremented. - mbox: Fixed some wrong "uid-last unexpectedly lost" errors. - auth cache: In some situations we crashed if passdb had extra_fields. - auth cache: Special extra_fields weren't saved to auth cache. For example allow_nets restrictions were ignored for cached entries. - A lot of initial login processes could cause auth socket errors in log file at startup, if dovecot-auth started slowly. Now the login processes are started only after dovecot-auth has finished initializing itself. - imap/pop3 proxy: Don't crash if the remote server disconnects before we're logged in. - deliver: Don't bother trying to save the mail twice into the default mailbox (eg. if it's over quota). - mmap_disable=yes + non-Linux was really slow with large dovecot.index.cache files - MySQL couldn't be used as a masterdb - Trash plugin was more or less broken - imap/pop3 couldn't load plugins if they chrooted - imap/pop3-login process could crash in some conditions - checkpassword-reply crashed if USER/HOME wasn't set

4 8

[Dovecot] Solaris/SSLonly/Lots of Users
by Steven F Siirila 22 Feb '07

22 Feb '07

Anyone running Dovecot on Solaris, requiring only SSL connections, and servicing thousands of simultaneous users? Our past attempts to do so have failed due to dovecot-auth using up all 256 of its file descriptors. I say 256 since we are limited to that by the 32-bit libraries. We are looking at either compiling Dovecot in 64-bit and letting dovecot-auth file descriptors accumulate (not ideal), or providing Timo with access to one of our test servers so he can debug the problem. However, I would like to hear of anyone in the same boat first. Thanks! -- 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

4 5

[Dovecot] Dovecot Quota + LDAP
by Venilton Junior 22 Feb '07

22 Feb '07

Hie Folks, I'm having a little problem with quota + ldap. I want to use per user quota settings. So I configured quota on my /etc/dovecot.conf like this site http://wiki.dovecot.org/Quota examples. Here follows my /etc/dovecot.conf: protocols = imap imaps pop3 pop3s ssl_disable = no ssl_cert_file = /usr/share/ssl/certs/cert.pem ssl_key_file = /usr/share/ssl/private/pkey.pem mail_extra_groups = mail valid_chroot_dirs = /var/lib/imap/vmail/domains default_mail_env = maildir:/var/lib/imap/vmail/domains/%d/%n/mail::INDEX=/var/run/dovecot/i ndexes/%n lock_method = dotlock mmap_disable = yes auth_debug = yes auth_debug_passwords = yes first_valid_uid = 202 last_valid_uid = 202 first_valid_gid = 202 last_valid_gid = 202 maildir_copy_with_hardlinks = no login_greeting = Sercomtel Internet ready. disable_plaintext_auth = no protocol imap { mail_plugins = quota imap_quota } protocol lda { postmaster_address = postmaster(a)domain.com mail_plugins = quota } protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_plugins = quota } auth default_with_listener { mechanisms = plain login userdb ldap { args = /etc/dovecot-ldap.conf } passdb ldap { args = /etc/dovecot-ldap.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = vmail group = mail } } } plugin { # quota = maildir:/var/lib/imap/vmail/%d/%u/mail:storage=102400 # convert_mail = maildir:/var/lib/imap/vmail/%d/%u/mail #quota = maildir:storage=102400 } And here is my user attributes in my dovecot-ldap.conf: user_attrs = mail,homeDirectory,,,,quotaStorage=quota=dirsize:storage user_filter = (&(objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) As you can see above in my dovecot.conf, I made a comment at plugin section to ensure that there's no quota usage for all system. I'd like to have per user quota stored in my ldap base. Here is a value off my quota attribute: quota = 122880 Making tests, the user already have 138 Mb. Does anyone have any idea how to set up quota with ldap and get it working? Tnx for any reply. Best regards, Venilton C. Junior

1 0

[Dovecot] login and plain-md5 in sql query
by Adrian Stoica 22 Feb '07

22 Feb '07

i use last dovecot rc23 with users/passwords in mysql 1) How can i define a sql query for each auth mechanism ? 2)Why i can't set "default_pass_scheme = login" in my dovecot-sql.conf? : dovecot: Feb 21 09:46:22 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGFkaUBhZHJpYW4uZXUAcGFyb2xh dovecot: Feb 21 09:46:22 Info: auth-worker(default): sql(adi(a)adrian.eu,127.0.0.1): query: SELECT IF('adrian.eu'='',clear,crypt) AS password , user FROM mailbox WHERE user = 'adi' AND domain = 'adrian.eu' AND status = '1' LIMIT 1 dovecot: Feb 21 09:46:22 Info: auth-worker(default): auth(adi(a)adrian.eu,127.0.0.1): username changed adi(a)adrian.eu -> adi dovecot: Feb 21 09:46:22 Error: auth-worker(default): sql(adi,127.0.0.1): Unknown password scheme login dovecot: Feb 21 09:46:23 Info: auth(default): client out: FAIL 1 user=adi(a)adrian.eu dovecot: Feb 21 09:46:23 Info: imap-login: Disconnected: user=<adi(a)adrian.eu>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured 3)Whi i can't use plain-md5 in dovecot.conf : auth default { mechanisms = login plain <- plain-md5 passdb sql { args=/etc/dovecot-sql.conf } userdb sql { args=/etc/dovecot-sql.conf } } dovecot: Feb 21 09:43:48 Error: auth(default): Unknown authentication mechanism 'plain-md5'

2 1

[Dovecot] pop3_lock_session
by Rene Luria 22 Feb '07

22 Feb '07

Hi guys, How can I modify the timeout value for the pop3_lock_session ? I'd like it to be much bigger.

2 4

[Dovecot] crash in mail_cache_transaction_reset on rc22
by Dan Price 22 Feb '07

22 Feb '07

I've not been able to roll out rc23 yet (tonight, I hope) but I just saw a crash which I'm not sure I've seen reported before, following a server outage (that is to say, the server came back up and one of the users had a dovecot core). #0 0x0005d720 in mail_cache_transaction_reset (ctx=0xcf928) at mail-cache-transaction.c:71 No locals. #1 0x0005e8bc in mail_cache_add (ctx=0xcf928, seq=233, field=4294967295, data=0xb7600, data_size=1063) at mail-cache-transaction.c:752 file_field = 19 data_size32 = 1063 fixed_size = 4294967295 full_size = 831272 __PRETTY_FUNCTION__ = "mail_cache_add" #2 0x00057160 in index_mail_parse_header (part=0xe9, hdr=0x14, mail=0xd33e8) at index-mail-headers.c:125 data = (struct index_mail_data *) 0xd3450 cache_field_name = 0xe9 <Address 0xe9 out of bounds> field_idx = 0 count = 21 match = (uint8_t *) 0xcf928 "" __PRETTY_FUNCTION__ = "index_mail_parse_header" #3 0x00079848 in _read (stream=0xe2aa0) at istream-header-filter.c:173 ret = 0 pos = 854336 #4 0x00085818 in i_stream_read (stream=0xe2ac8) at istream.c:58 _stream = (struct _istream *) 0xcaf28 #5 0x00085ca4 in i_stream_read_data (stream=0xe2ac8, data=0xffbff5ec, size=0xffbff5e8, threshold=1) at istream.c:250 ret = 0 read_more = false #6 0x0007e8c4 in message_get_body_size (input=0xe2ac8, body=0xffbff660, has_nuls=0x0) at message-size.c:105 msg = ( const unsigned char *) 0xe2cf7 "\ndary_(ID_/CFD74Co3EWCZqYkdHlE8A)\"\r\nt>\r\nSS(a)cox.net>,\r\nil.com>,\r\n\r\n" i = 0 ---Type <return> to continue, or q <return> to quit--- size = 1 missing_cr_count = 0 __PRETTY_FUNCTION__ = "message_get_body_size" #7 0x0002e5e4 in fetch_body_header_fields (ctx=0xc6a08, mail=0xffbff660, context=0xc6c98) at imap-fetch-body.c:448 size = {physical_size = 1357, virtual_size = 0, lines = 26} old_offset = Unhandled dwarf expression opcode 0x93 -- Daniel Price - Solaris Kernel Engineering - dp(a)eng.sun.com - blogs.sun.com/dp

2 1

[Dovecot] Understanding fcntl() error messages
by Dean Manners 22 Feb '07

22 Feb '07

Hey guys, After many trials and tribulations I have now got some fairly stable NFS clients serving dovecot-lda and pop3/imap. Over a 9 hour postal/rabid stress test only saw 5 errors for the 4 servers. Wondering if anyone can shed a bit more light on what they mean exactly. I have tried to find "Resource temporarily unavailable" and "No locks available" in the src to get some understanding - however it appears these messages are from a lower level. With pop3: ------------------ Feb 22 03:36:32 mailget01 dovecot: POP3(test992(a)mailtest06.com): fcntl() failed with file /mnt/mailstore/mailtest06.com/8/test992/dovecot.index.log: Resource temporarily unavailable Feb 22 03:36:32 mailget01 dovecot: POP3(test992(a)mailtest06.com): mail_index_wait_lock_fd() failed with file /mnt/mailstore/mailtest06.com/8/test992/dovecot.index.log: Resource temporarily unavailable Feb 22 04:16:45 mailget01 dovecot: POP3(test445(a)mailtest03.com): fcntl() failed with file /mnt/mailstore/mailtest03.com/4/test445/dovecot.index.log: Resource temporarily unavailable Feb 22 04:16:45 mailget01 dovecot: POP3(test445(a)mailtest03.com): mail_index_wait_lock_fd() failed with file /mnt/mailstore/mailtest03.com/4/test445/dovecot.index.log: Resource temporarily unavailable ------------------ ------------------ Feb 22 13:07:27 mailget01 dovecot: POP3(test999(a)mailtest06.com): fcntl() failed with file /mnt/mailstore/mailtest06.com/8/test999/dovecot.index: Resource temporarily unavailable Feb 22 13:07:27 mailget01 dovecot: POP3(test999(a)mailtest06.com): fcntl() failed with file /mnt/mailstore/mailtest06.com/8/test999/dovecot.index: Resource temporarily unavailable Feb 22 13:07:27 mailget01 dovecot: POP3(test999(a)mailtest06.com): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2007-02-22 13:07:27] Feb 22 13:07:27 mailget01 dovecot: POP3(test999(a)mailtest06.com): No INBOX for user top=0/0, retr=0/0, del=0/0, size=0 ------------------ Does this mean that pop3 was waiting for a lock, but timed out ? What are the likely affects of this on a client POPing - session times out and they need to reconnect? The "No INBOX" error is little more odd, the same user had successful login 90 minutes earlier. With deliver: ------------------ Feb 22 01:42:03 mailfilter01 deliver(test680(a)mailtest04.com): fcntl() failed with file /mnt/mailstore/mailtest04.com/10/test680/dovecot.index: No locks available Feb 22 01:42:06 mailfilter01 deliver(test265(a)mailtest03.com): fcntl() failed with file /mnt/mailstore/mailtest03.com/1/test265/dovecot.index: No locks available Feb 22 03:25:42 mailfilter02 deliver(test454(a)mailtest03.com): fcntl() failed with file /mnt/mailstore/mailtest03.com/2/test454/dovecot.index: No locks available Feb 22 03:25:45 mailfilter02 deliver(test397(a)mailtest03.com): fcntl() failed with file /mnt/mailstore/mailtest03.com/7/test397/dovecot.index: No locks available ------------------ I assume this means deliver tried to obtain a lock on the index file (probably many times) but failed. Are the likely affects that the message still gets saved to the maildir but the index doesn't get updated? Regards __________________________________________ Dean Manners

2 2

[Dovecot] critical performance problem
by Rene Luria 22 Feb '07

22 Feb '07

I have been using dovecot 1.0alpha4 + deliver/sieve in production for a few accounts (400'000). After testing 1.0.rc22 I decided to upgrade one of the imap servers... And... what a mess ! The server just gets unusable. I don't know why but with new release, it just overloads the system with I/O. It turns that with 1.0.rc22 I get 15Mo/s read on disk average, without any reason. What did really change ? How come a system (with a few thousand accounts) works perfectly and then with 1.0.rc22 gets unusable with a load approaching 300 ? If you have any ideas...

5 18

[Dovecot] 1.0.rc23 tomorrow
by Timo Sirainen 22 Feb '07

22 Feb '07

http://dovecot.org/nightly/dovecot-latest.tar.gz Would be nice to get some testing before the actual release. I've now finally gone through all the "TODO" mails in this list and my INBOX and fixed pretty much every problem I know of. There are still some mbox bugs, but I can't really get them fixed unless someone figures out how to reproduce them (http://wiki.dovecot.org/MboxProblems) I think documentation is the last thing that should be done before v1.0. I'm happy enough with the code as it is now, unless some new bugs again appear. The notable changes since rc22: * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. + PAM: blocking=yes in args uses an alternative way to do PAM checks. Try it if you're having problems with PAM. + userdb passwd: blocking=yes in args makes the userdb lookups be done in auth worker processes. Set it if you're doing remote NSS lookups (eg. nss_ldap problems are fixed by this). + If PAM child process hasn't responded in two minutes, send KILL signal to it (only with blocking=no) - IMAP: APPEND ate all CPU while waiting for more data from the client (broken in rc22) - mbox: When saving a message to an empty mbox file it got one UID which immediately was incremented. - mbox: Fixed some wrong "uid-last unexpectedly lost" errors. - auth cache: In some situations we crashed if passdb had extra_fields. - auth cache: Special extra_fields weren't saved to auth cache. For example allow_nets restrictions were ignored for cached entries. - A lot of initial login processes could cause auth socket errors in log file at startup, if dovecot-auth started slowly. Now the login processes are started only after dovecot-auth has finished initializing itself. - imap/pop3 proxy: Don't crash if the remote server disconnects before we're logged in. - deliver: Don't bother trying to save the mail twice into the default mailbox (eg. if it's over quota). - mmap_disable=yes + non-Linux was really slow with large dovecot.index.cache files - MySQL couldn't be used as a masterdb - Trash plugin was more or less broken - imap/pop3 couldn't load plugins if they chrooted - imap/pop3-login process could crash in some conditions - checkpassword-reply crashed if USER/HOME wasn't set

6 19

[Dovecot] --log-error and the mysterious "not starting" problem
by Marshal Newrock 21 Feb '07

21 Feb '07

I've finally upgraded to 1.0.rc21. If I run "dovecot --log-error", then dovecot fails to start. The following appears in the log: Feb 5 10:54:00 taurus1 dovecot: Dovecot v1.0.rc21 starting up Feb 5 10:54:00 taurus1 dovecot: This is Dovecot's error log Without --log-error, it will start up fine from command-line. Dovecot still fails to start, as near as I can tell, in the specific condition that it is being started from a non-interactive shell and there is a mail_plugin set in "protocol imap". mail plugins set for pop or lda do not cause this problem. The failure to start appears in only two instances that I can see: on boot, or by a monitoring script if dovecot crashes, or, since I haven't seen dovecot die, when I manually stop it to see if the monitoring program will restart it. With the above problem, if the init script has --log-error when I try to make the monitoring program restart dovecot, then nothing still gets logged. -- Marshal Newrock, Ideal Solution LLC http://www.idealso.com

2 8