- dovecot - dovecot.org

[Dovecot] Building Dovecot with OpenLDAP break PAM LDAP on Solaris
by Laurent Blume 07 Mar '08

07 Mar '08

Hi all, I'm back with more data on a problem Iposted about one month ago. To sum it up, my Solaris 10 box has local accounts as well as LDAP ones via PAM. They work well as-is, with no special configuratio, for WU IMAP (using the «other» entry in pam.conf. When I tried a self-built Dovecot, all accounts were authenticated without problem. Then I tried the Blastwave version, same release, but with more option, and this one didn't work with the exact same configuration: local accounts were authenticated, not the PAM LDAP ones. Now, it turns out that when Dovecot is built using OpenLDAP, then PAM LDAP account won't work. If it's built with Solaris LDAP, they work, everything else being equal. Is there any way to fix that? There's the Blastwave bug report with more details if needed: http://www.blastwave.org/mantis/view_bug_page.php?f_id=0002760 Thanks in advance for any help, Laurent -- / Leader de Projet & Communauté | I'm working, but not speaking for \ G11N http://fr.opensolaris.org | Bull Services http://www.bull.com / FOSUG http://guses.org |

2 2

[Dovecot] Squat Indexing
by Jeff Grossman 07 Mar '08

07 Mar '08

I tried Squat indexing on my very small home system and when I did a body search in Thunderbird, I got a TON, and I mean TON, of these messages in my log file: Mar 6 06:13:31 apple dovecot: child 14142 (imap) killed with signal 6 Mar 6 06:13:31 apple dovecot: IMAP(jeff): file file-lock.c: line 112: unreached Mar 6 06:13:31 apple dovecot: IMAP(jeff): Raw backtrace: imap [0x482771] -> imap [0x482166] -> imap [0x484d86] -> imap(file_wait_lock+0x35) [0x484ef5] -> /usr/local/lib/dovecot/imap/lib21_fts_squat_plugin.so [0x2b4664a69a0c] -> /usr/local/lib/dovecot/imap/lib21_fts_squat_plugin.so [0x2b4664a6a99b] -> /usr/local/lib/dovecot/imap/lib21_fts_squat_plugin.so(squat_trie_get_last_uid+0x4c) [0x2b4664a6ac1c] -> /usr/local/lib/dovecot/imap/lib20_fts_plugin.so [0x2b4664862d0b] -> /usr/local/lib/dovecot/imap/lib20_fts_plugin.so [0x2b4664863bb3] -> imap(cmd_search+0xd9) [0x41b909] -> imap(cmd_uid+0x52) [0x41ca12] -> imap [0x41d348] -> imap [0x41d3e9] -> imap [0x41db5f] -> imap(client_input+0x5f) [0x41dd8f] -> imap(io_loop_handler_run+0xf8) [0x4894c8] -> imap(io_loop_run+0x1d) [0x4887ad] -> imap(main+0x3c2) [0x424f52] -> /lib/libc.so.6(__libc_start_main+0xf4) [0x2b466451e1c4] -> imap [0x417df9] This is with version 1.1rc1. Here is a copy of my dovecot -n: # 1.1.rc1: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/stikman-godaddy.crt ssl_key_file: /etc/ssl/private/stikman-godaddy.key disable_plaintext_auth: no login_dir: /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 verbose_proctitle: yes mail_extra_groups: mail mail_location: maildir:~/Maildir dotlock_use_excl: no fsync_disable: yes lock_method: dotlock maildir_copy_with_hardlinks: no 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_plugins(default): fts fts_squat mail_plugins(imap): fts fts_squat mail_plugins(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 auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd plugin: fts: squat

2 2

[Dovecot] Squat performance
by Timo Sirainen 07 Mar '08

07 Mar '08

The initial building (and an occational compression) performance just got a major boost. I knew there was a problem there, but I hadn't realized it was this easy to fix: http://hg.dovecot.org/dovecot-1.1/rev/4445415da4ff My 1,4 GB test lkml mbox can be now indexed in 7 minutes, doubling the speed form earlier 14 minutes. I added some more benchmark results here: http://wiki.dovecot.org/Plugins/FTS So the initial Squat index building is about 2-3x slower than the non-indexed search. I think that's pretty good. Also I think it means that the non-indexed search code could be optimized more. :) Maildir test shows that it indexes about 5 MB/CPUsec. My earlier tests showed that it indexed 8-10 MB/CPUs when feeding data directly to it, so 3-5 MB/CPUs is going elsewhere, probably to message parsing and charset conversions and such..

1 0

[Dovecot] Upgrading from 0.99.10.5 to 1.1
by Anders 07 Mar '08

07 Mar '08

Hi, I am upgrading a setup from Dovecot 0.99 to 1.1. There are a bunch of .imap.index* files that it appears that I can just delete, and they will be recreated as dovecot.index* files. Right? Next, there are some .customflags that I have now learned are not being converted to dovecot-keywords (as we skipped the 1.0 version, and the conversion code appears to be removed in 1.1). Is there some way to convert this? Is it just a rename? Thanks, Anders.

2 2

[Dovecot] Deliver question
by Dien Phan 07 Mar '08

07 Mar '08

Hi, I searched whole 2007-2008 mailing lists for answer but couldn\'t find. I think it\'s easier and quicker to ask here. Suppose I have a message saved in file /tmp/afile. How can I tell deliver to deliver it to user\'s abc(a)domain.com mail box SPAM? I tried two following ways but no success: 1. more /tmp/afile | deliver -d abc(a)domain.com -m SPAM 2. deliver -d abc(a)domain.com -m SPAM < /tmp/afile Thank you for help. --------------- Thư điện tử tiếng Việt, đơn giản và thuận tiện: http://mail.vn-mail.net

2 1

[Dovecot] Future enhancement of imap: sorting?
by Andy Dills 07 Mar '08

07 Mar '08

After solving a problem with a sweet little application I discovered (more on that below), I wanted to get some feedback about a potential enhancement for IMAP: standardized, MUA independant, server-side sorting. Currently, there are two basic solutions for sorting: handle it during delivery or handle it in the MUA. However, if you handle it in the MUA, you lose some of the client independancy and portability that imap was designed to address, as there is no mechanism to sync sorting rules between clients, and many lightweight clients don't support sorting at all. On the flip side, in distributed mail envrionments sorting at delivery time isn't feasible, as you typically have the entire mailspool owned by a single UID and mounted via NFS. My basic point is that the two paradigms for sorting have fundemental flaws that severaly limit them. It occured to me that it would be ideal to enable sorting in the imap daemon, enabling users to implement sorting rules which are stored in their directory (similar to the other imap metadata), and which get invoked whenever mail is checked. Perhaps that is beyond the reasonable scope of the imap protocol, but in my mind sorting is a critical task that is poorly addressed and needs to be standardized. I'd love to hear opinions on this. See, in our mail cluster environment, it's basically impossible to use procmail without forwarding your mail to our shell server (nor are we able to use the dovecot LDA). So, the question presented to me by one of my business partners was, since Outlook was shortsighted and didn't include the ability to sync sorting rules between clients, nor did they implement sorting functionality whatsoever on the windows mobile version, what options does he have to ensure proper sorting of his mail without having to leave outlook running 24x7? He doesn't want to have to wade through mailing list email on his mobile outlook, nor does he want to have to ensure his filter rules are consistent in both his outlook and our webmail. So, I poked around in the ports tree, and found a gem: imapfilter. http://imapfilter.hellug.gr/ It's configured via lua, supports a very rich array of actions and queries, and has proven to be very robust and lightweight. I helped him get started with some sample rules, added it to run every minute as a cron job, and boom: robust, fully featured, MUA independant filtering in an environment that can't support procmail or the dovecot LDA. As nice as it is, it's still a personal solution. In my mind we need to have standardized, server-side, MUA-independant sorting rules that get invoked when a mailbox is checked. Thoughts? Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---

2 5

[Dovecot] Outlook 2003 marks email for deletion
by Jan van den Berg 07 Mar '08

07 Mar '08

Hi, Im running Dovecot 1.1RC1 (only IMAP). I noticed that when I connect with Outlook 2003; and I start reading new email some mails get marked (completely random) for deletion (,S -> ,ST) ?? I can set this mail to unread, undo the deletion read it again and it will stay OK. But other emails will still get marked. This only seems to happen with Outlook 2003 not with Outlook Express or Thunderbird and only with new unread mail. Any ideas why Outlook marks this mail for deletion? Cheers, Jan

3 3

[Dovecot] auth_debug_passwords only on mismatches?
by Mike 07 Mar '08

07 Mar '08

>From the configuration notes (1.0.10), it sounds like setting 'auth_debug_passwords' will only log the user supplied password if there was a mismatch.. When I set it (with auth_debug=no), I get a good amount of auth debug info, regardless of password matching.. ------ dovecot.conf: # In case of password mismatches, log the passwords and used scheme so the # problem can be debugged. Requires auth_debug=yes to be set. auth_debug_passwords = yes ------ I'm basically looking to just add a "login failed" line, with the username, and supplied passsword when a mismatch occurs.. Is there currently a way to do this without modifying the code? Thanks! -Mike

2 1

[Dovecot] dovecot-auth-master Error
by Paul Roberts 07 Mar '08

07 Mar '08

I'm getting this error in my dovecot-deliver.log file... deliver(paul3(a)fleeky.com): Mar 06 10:15:08 Error: net_connect(/usr/local/var/run/dovecot-auth-master) failed: Permission denied What does that mean? If you guys need more information just ask but I just don't now what the problem is... -Paul

2 1

Re: [Dovecot] Wrong message information reported shortly after delivery
by Ron Avriel 07 Mar '08

07 Mar '08

> On Thu, 2008-03-06 at 08:21 -0800, Ron Avriel wrote: > > If an IMAP fetch is issued some "short" time after a message was delivered > > with dovecot deliver then dovecot reports wrong (zero) values > > for that new message. Afterward, it reports the information OK. > > What OS/filesystem do you use? I don't see how this is possible. The > mails are first written to tmp/ directory and then they're atomically > rename()d to the new/ or cur/ directory. > > I also tested this myself, rapidly sending the same FETCH command 1000 > times/sec while delivering 40MB mails to the maildir. The size was > always correct. I'm using standard out of the box Redhat EL 4 with an ext3 filesystem. Since I can reproduce it easily on different RHEL4 machines, tell me what additional information you'd like. Thanks again, Ron ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

2 1