February 2010 - dovecot

[Dovecot] v2.0.beta2 released
by Timo Sirainen 02 Feb '10

02 Feb '10

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz.sig I tried to keep the configuration and APIs compatible with v2.0.beta1, but unfortunately there were a few things that really had to be changed: 1. passdbs and userdbs have now a separate "driver" setting inside them. So for example if you had: userdb passwd { } You'll now need to use instead: userdb { driver = passwd } 2. Services now have default inet_listeners. You need to either remove your existing ones, or override the defaults by giving the listeners's name like shown in the new example master.conf. For example if you had: service imap-login { inet_listener { port = 1234 .. change it to: service imap-login { inet_listener imap { port = 1234 If you want to disable a default listener, you can set its port to 0. Some new features: - Added auth_verbose_passwords = no|plain|sha1. If authentication fails, this setting logs the used password. If you don't really need to know what the password itself was, but are more interested in knowing if the user is simply trying to use the wrong password every single time or if it's a brute force attack, you can set this to "sha1" and only the SHA1 of the password is logged. That's enough to know if the password is same or different between login attempts. - lazy-expunge: Support a single-namespace configuration. In this setup if mailbox has some expunged messages and then the whole mailbox gets deleted, they get merged into the same deleted mailbox. - protocol !imap { .. } adds configuration to all protocols except imap. - imap/pop3 proxying supports now async DNS lookups for hosts. There's a separate dns-client service doing the lookups using OS's own blocking resolver. - dovecot-config file changed in a way that it'll be easier to create external software linking against dovecot libraries. This made Pigeonhole's configure script a lot simpler. And of course there have been lots of fixes.

3 4

[Dovecot] proxy_maybe regex
by David Halik 02 Feb '10

02 Feb '10

Does anyone know if dovecot support regex lookups for proxy/proxy_maybe, rather than mysql/ldap etc? I've been comparing it with perdition to see which one might be better for us to do layer7 username switching. Perdition supports the ability to not have any auth/db looks, but rather just a regex file that parses the usernames as they come in and forwards to the particular machine on the same port. For example: username:host ^[a-d]: 192.168.xxx.1 ^[e-k]: 192.168.xxx.2 and so on... I didn't think this was supported in dovecot, but I wanted to check first. I think this is going to end up being what we use to avoid NFS problems. It's lightweight, drops into our current setup, and doesn't require a mysql database which adds another point of failure. -- ================================ David Halik System Administrator OIT-CSS Rutgers University dhalik(a)jla.rutgers.edu ================================

3 6

[Dovecot] Want to have some users with Maildir, some with mbox
by Stewart Dean 01 Feb '10

01 Feb '10

Want to have some users with Maildir, some with mbox, as I migrate from mbox format to maildir over the space of a month. After everyone is converted to maildir, I'll change the mail_location in dovecot.conf. During the interim, can I use the Custom mailbox location script (at the bottom of the Mail Location DC Wiki page)? > if [ -d $HOME/.maildir ]; then > export MAIL=maildir:$HOME/.maildir > else > export MAIL=mbox:$HOME/mail:INBOX=/var/mail/$USER > fi > Questions: 1) What does explicitly specifying MAIL this way override? The dovecot.conf mail_location variable? 2) My mail_location var is defined as: mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u and my prospective maildir INBOX and mail folder root is to be ~/Maildir. So would I change the above to: > if [ -d $HOME/Maildir ]; then > export MAIL=maildir:$HOME/Maildir:INDEX=/var/dcindx/$USER > else > export MAIL=mbox:$HOME/mail:INBOX=/var/spool/mail/$USER: > INDEX=/var/dcindx/$USER > fi Question 3: When converting existing users from mbox to maildir, should I delete the index contents? Thanks in advance! dovecot -n output # 1.2.8: /usr/local/etc/dovecot.conf # OS: AIX 3 0001378F4C00 listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1280 mail_max_userip_connections: 12 verbose_proctitle: yes first_valid_uid: 200 mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u mbox_write_locks: fcntl mbox_dirty_syncs: no lda: postmaster_address: postmaster(a)example.com auth default: passdb: driver: pam userdb: driver: passwd -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 9

[Dovecot] index location
by Dave Brenner 01 Feb '10

01 Feb '10

Greetings. We are testing with 1.2.9 and have found that with mail_full_filesystem_access set to 'yes', we cannot force indexes for folders under ~/mail to be stored in /var/dovecot/indexes/%u. /var/dovecot/indexes/%u/.imap/INBOX/dovecot.index* is created just fine, but everything else ends up in ~mail/.imap. If I change mail_full_filesystem_access to 'no', then all indexes are created in the expected location: $ ls -la /var/dovecot/indexes/blitz/ total 4 drwxr-xr-x 4 blitz popuser 512 Jan 25 11:46 . drwxrwxr-x 5 root popuser 512 Jan 22 16:16 .. drwxr-xr-x 3 blitz popuser 512 Jan 22 16:16 .imap drwxr-xr-x 3 blitz popuser 512 Jan 25 11:46 mail (I probably need to set the sticky bit for this, but for testing this is OK) We are setting the index location from /etc/passwd-dove: blitz:x:14267:500::/usr/users/dialups/blitz::userdb_mail=mbox:~/:INBOX=/var/mail/%u:INDEX=/var/dovecot/indexes/%u Is there a way to get this to function the way we'd like, with all indexes stored in /var/dovecot/indexes/u% ? My apologies if I missed an explanation about this in the list archive. Dave

2 9

[Dovecot] Extraneous information
by Michael M. Slusarz 01 Feb '10

01 Feb '10

Not technically a bug, but a small waste of bandwidth: it seems (at least as of 1.2.10) that if neither CONDSTORE/QRESYNC are enabled dovecot still sends HIGHESTMODSEQ info: a examine Testing.AAA * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $Forwarded impflag0 impflag1 impflag2) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 309 EXISTS * 0 RECENT * OK [UNSEEN 5] First unseen. * OK [UIDVALIDITY 1225053009] UIDs valid * OK [UIDNEXT 387] Predicted next UID * OK [HIGHESTMODSEQ 136] Highest a OK [READ-ONLY] Select completed. I'm guessing this would only happen if using a client that supports QRESYNC (like IMP) and then switching later to a client that doesn't support.

2 2

[Dovecot] [dovecot] Problems installing managesieve and then managesieve-login
by Jonathan Siegle 01 Feb '10

01 Feb '10

Hi, Software: AIX 5.3 dovecot-2.0-pigeonhole revision 1234:7b3db97399de with dovecot revision 10621:a978089d090b I'm having problems installing managesieve. I modified the Makefile because DESTDIR was not being found. Here is what I changed to make it work: echo " $(INSTALL_PROGRAM_ENV) $(LIBTOOL) --mode=install $(dovecot_pkglibexecPROGRAMS_INSTALL) '$$p' '/usr/local/dovecot2.0beta2/bin$(dovecot_pkglibexecdir)/$$f'"; \ $(INSTALL_PROGRAM_ENV) $(LIBTOOL) --mode=install $(dovecot_pkglibexecPROGRAMS_INSTALL) "$$p" "/usr/local/dovecot2.0beta2/bin$(dovecot_pkglibexecdir)/$$f" || exit 1; \ --- Here is ORIGINAL: echo " $(INSTALL_PROGRAM_ENV) $(LIBTOOL) --mode=install $(dovecot_pkglibexecPROGRAMS_INSTALL) '$$p' '$(DESTDIR)$(dovecot_pkglibexecdir)/$$f'"; \ $(INSTALL_PROGRAM_ENV) $(LIBTOOL) --mode=install $(dovecot_pkglibexecPROGRAMS_INSTALL) "$$p" "$(DESTDIR)$(dovecot_pkglibexecdir)/$$f" || exit 1; \ Here is the error: test -z "" || /usr/local/src/imapservers/dovecothg/dovecot-2.0-pigeonhole/install-sh -d "" /bin/sh ../../libtool --mode=install /usr/ladmin/bin/install -c 'managesieve' '/managesieve' libtool: install: `' must be an absolute directory name Try `libtool --help --mode=install' for more information. gmake[3]: *** [install-dovecot_pkglibexecPROGRAMS] Error 1 managesieve-login is having the same problem. sieve-tools installed just fine. On my configure line I have: $ ./configure --with-dovecot=../dovecot-2.0 --prefix=/usr/local/dovecot2.0beta2 --with-managesieve=yes Thanks, Jonathan

2 2

[Dovecot] Not understanding namespaces
by Stewart Dean 01 Feb '10

01 Feb '10

I have been diligently reading about namespace in the DC doc and what I can find in Google. Like the blind men and the elephant, I see the nature of some individual bits of namespace, some syntax and the overall purpose (overriding defaults and providing extensions), but I don't see the whole thing and how it is used. I am looking to do some maildir testing in what is a mbox default system, so I thought to employ namespace to do so. I see that namespace(s) can be defined in dovecot.conf and I see that it can be defined in TBird (under ServerSettings, Advanced Account Settings), but it isn't clear to me how they are made to work together. Some questions: - Is it that you can define multiple namespaces in dovecot.conf and then specify which of these you use in the TBird server settings? - What is the syntax of the TBird namespace specification? -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

4 8

[Dovecot] lda sieve bug ?
by Lampa 01 Feb '10

01 Feb '10

Hello, weird lines in dovecot lda log appers: 2010-02-01T13:48:10.108065+01:00 hermes dovecot: deliver(user(a)domain.tld): sieve: !!BUG!!: binary compiled from /home/mail/domain.tl/user/.dovecot.sieve is still corrupt; bailing out and reverting to default delivery drwx------ 4 vmail vmail 74 Feb 1 13:13 . drwx------ 1715 vmail vmail 49152 Feb 1 12:32 .. lrwxrwxrwx 1 root root 17 Feb 1 13:13 .dovecot.sieve -> sieve/redir.sieve -rw------- 1 vmail vmail 496 Feb 1 13:48 .dovecot.svbin drwx------ 13 vmail vmail 4096 Feb 1 12:58 Maildir drwx------ 3 vmail vmail 34 Feb 1 13:13 sieve ls -la sieve/ drwx------ 3 vmail vmail 34 Feb 1 13:13 . drwx------ 4 vmail vmail 74 Feb 1 13:13 .. -rw------- 1 vmail vmail 563 Feb 1 11:37 redir.sieve drwx------ 2 vmail vmail 6 Dec 13 14:30 tmp -- Lampa

2 1

[Dovecot] sieve script
by Lampa 01 Feb '10

01 Feb '10

Hello, after qmail migration need convert some .procmailrc scripts. Found converter procmail -> sieve, but i'm not sure of quality of conversion. My script: --------------- if header :contains "from" ["user(a)domain1.tld", "user2(a)domain2.tld", "user3(a)domain3.tld"] { redirect "foo1(a)bar.tld"; redirect "foo2(a)bar.tld"; .... redirect "foo20(a)bar.tld"; } else { keep; } --------------- Converter script: --------------- require ["fileinto","regex","envelope","vacation"]; if envelope :comparator "i;octet" :contains "From.*(user@domain1.tld|user2@domain2.tld|user3@domain3.tld)" "" { redirect "foo1(a)bar.tld foo2(a)bar.tld .... foo20(a)bar.tld"; } if true { fileinto "$DEFAULT"; } --------------- Converter script is cannot be compiled. But it used other style envelope. So what is difference between envelope and header ? And there are some limits for redirect ? Thank you. -- Lampa

5 7

[Dovecot] sieve or another vacation/autoreply
by Lampa 01 Feb '10

01 Feb '10

Hello, i'm trying to do some delivery notification for each incoming address. Problem is that sieve vacation has :days but minimum value is 1 eg period in which addresses are kept and are not responded to - but that is not that i want. Is there other extension (in devel ???) or some other way (lda using procmail or maildrop) how to implement my request ? (Before migration we used qmail + procmail). Thank you for your advices -- Lampa

4 8