- dovecot - dovecot.org

[Dovecot] SASL auth and proxy
by mailing＠securitylabs.it 02 Oct '10

02 Oct '10

Hello, I'm finding a way to have a pool of smtp-auth servers in front of my actuals servers to permit relay to our customers. Now users sends emails connecting to the right IP via mail.domain.tld, with authentication. Every server has it's own user database in mysql. I'd like to have a pool of server (with round robin, ideally with postfix + sasl + dovecot) that authenticate the users with the actuals servers and then pointing mail.domain.tld to this pool and not to one server. My trouble is how to authenticate users. Can I use: http://wiki.dovecot.org/Authentication/MultipleDatabases to tell Dovecot to authenticate with every MySQL database on the servers "behind"? If yes, is there a better way to do this considering I'm already using some proxy machines (dovecot) for pop3/imap and so I already have a db with domain.tld -> IP of the server? I also have some machine without a MySQL DB for users (vpopmail + cdb), so the option with MultipleDatabases will be good only for some machines. Something similar to the proxy mechanism that I already use for pop3/imsp will be good: the proxy connect to the machine behind that do the authentication, I only need a table with domain -> server IP (that I already have). Thanks for any advice.

3 4

[Dovecot] Dovecot v0.99.13-3 upgrade to 1.0.15-2 ??
by cajun 02 Oct '10

02 Oct '10

I've read some of the mailing lists looking for information on this. Thus far, about all I've found is there was a complete rewrite of Dovecot some time back. I'm wondering now is it even possible to use the same mbox's from 0.99.13-3 with version 1.0.15-2? Is there a procedure documented somewhere? Any pointers would be much appreciated. Thanks, Mike -- Let the machine do the dirty work. - Elements of Programming Style 15:50:02 up 1 day, 1:13, 2 users, load average: 0.52, 0.45, 0.36 Linux Registered User #241685 http://counter.li.org

8 19

[Dovecot] dovecot 2.04 broke folder sharing
by Robert Schetterer 02 Oct '10

02 Oct '10

Hi Timo, upgrading from 2.03 to 2.04 broke folder sharing at my setup double checked this with tests reverting versions etc setting acl and subcriptions are working with 2.04, but in difference to 2.03 no shared subfolder is created at acl/subscription set time so subscribing afterwards fail with ignore message by bad subscription the mails store is on drbd with ocfs2 i didnt change any other config parameter during the tests so some patch must have changed folder sharing behavior from 2.03 to 2.04 speculate something with default hardlinks etc? any idea ? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 10

[Dovecot] ACL handling bugs in v1.2.8+ and v2.0
by Timo Sirainen 01 Oct '10

01 Oct '10

I thought I'd write one mail about this, rather than duplicate the whole thing to both v1.2.15 and v2.0.5 release announcements. So, ever since this commit: 2009-11-10 Timo Sirainen <tss(a)iki.fi> * src/plugins/acl/acl-backend-vfile.c: acl: Merge group rights if user belongs to more than one. [76ff6831c9ae] The ACLs were being merged, rather than fully replaced, a bit too often. Since this is about merging, the problem could have happened only when using more than one entry in the ACL file. The main problems created by this were: a) If admin wanted to remove some rights from mailboxes in user's private namespace (e.g. symlinked shared mailboxes), they may not have gotten removed. b) When mixing up multiple ACL entries, such as groups/users the more specific entry may not have replaced the previous entry (e.g. group-override may not have worked as expected). The bug happened when two or more ACL entries of same "type" existed. The first entry was handled correctly, but the next ones may have only been adding ACLs rather than replacing them. For example if you had the following ACL file: group=people lrwi user=foo lr user=bar lr So basically everyone in "people" group should have "lrwi" rights, but foo and bar users should have only "lr" rights. If foo and bar didn't belong to people group, everything would work as expected. If they did, then what would happen is: * foo would work correctly, because it was the first entry of user type. * bar would keep "lrwi" rights, because the previous entry (user=foo) was of the same type (both are "user" type), so Dovecot decided to add the rights on top of group=people entry rather than replace them. BTW. The other ACL bug/"feature" of automatically adding admin rights that was fixed in v1.2.15 was already fixed in v2.0.beta2.

1 0

[Dovecot] Outlook 2010 Delayed Emails
by Munroe Sollog 01 Oct '10

01 Oct '10

dovecot --version = 1.2.11 dovecot -n: http://pastebin.com/ahCpdC0F I have a user that has no problem viewing email from roundcube (webmail) but Outlook 2010 doesn't seem to download random messages for a day or two, then they suddently show up. I saw the wiki had some suggestions for older versions of Outlook to fix other problems, but I didn't really see anything like this. Any help would be appreciated. Thanks. -- Munroe Sollog Digirati Consulting www.digiraticonsulting.com 610-332-7234 x805

2 2

[Dovecot] zlib plugin weirdness
by Kyle Wheeler 01 Oct '10

01 Oct '10

Hello, I'm trying to get the zlib plugin working on my 2.0 server. I started with an mbox that Dovecot can read just fine. Then I gzipped it, and now Dovecot complains that it's corrupted: Error: Next message unexpectedly corrupted in mbox file /var/lib/vpopmail/domains/memoryhole.net/kyle/Maildir/Archive/Intellego.gz at 1907 Error: Unexpectedly lost From-line from mbox file /var/lib/vpopmail/domains/memoryhole.net/kyle/Maildir/Archive/Intellego.gz at 1907 Error: zlib.read(/var/lib/vpopmail/domains/memoryhole.net/kyle/Maildir/Archive/Int…: unexpected EOF at 1765954 Error: i_stream_get_size() failed with mbox file /var/lib/vpopmail/domains/memoryhole.net/kyle/Maildir/Archive/Intellego.gz: No such file or directory A similar thing happens when I bzip it. I was worried that it wasn't even using the zlib plugin, but since it makes reference to zlib.read, I assume that it is. Does anyone know what might be going wrong? ~Kyle -- The only way to oppose a bad idea is to replace it with a good idea. -- Jack Kemp

2 5

[Dovecot] LMTP don't accept jobs for system users
by Alejandro Maurich 01 Oct '10

01 Oct '10

Hi, I'm trying to configure Dovecot 2.0.1 to deliver email to users in /etc/passwd using the Dovecot LMTP service. So far, I can sucessufully do POP3 for system users, but when Postfix tries to deliver email to the Dovecot LMTP service the LMTP reject the job with: "User doesn't exist ale(a)centos54.mydomain.com" Any suggestions? The user 'ale' is a valid user: # grep ale /etc/passwd ale:x:500:500:Alex:/home/ale:/sbin/nologin This is the dovecot -n output: # 2.0.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-164.el5xen i686 CentOS release 5.4 (Final) disable_plaintext_auth = no mail_location = maildir:~/Maildir mail_privileged_group = mail mbox_write_locks = fcntl passdb { args = session=yes failure_show_msg=yes dovecot driver = pam } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 10050 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } protocol lmtp { mail_plugins = $mail_plugins }

2 1

[Dovecot] IMAP connection timeout value?
by Tamas Kadar 01 Oct '10

01 Oct '10

So we're having some ISP issues lately, meaning we have to reboot our cable modem like 2-3 times a day. An unfortunate side-effect I've found is, once the users max out their connection limit (which I've set to 10, and many people do), if we reboot the cable modem, they can't log in cause their connections get 'stuck' until I `doveadm kick` them, or wait for the connections to timeout which takes ??? minutes. Can I adjust that value to something like 30 seconds? Thanks and best regards, KT

5 8

[Dovecot] SSL strangeness with dovecot-lda in 2.0.4
by Glyn Faulkner 01 Oct '10

01 Oct '10

Hello, First of all, thank you for developing a fantastic IMAP server! I've just upgraded to 2.0.4 (from 2.0.1) and when I try to run /usr/lib/dovecot/deliver (either directly from the commandline, or from within the MTA) I get the following error: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: ssl enabled, but ssl_key not set I converted my old config file settings using "dovecot -c /etc/dovecot/dovecot.orig -n > /etc/dovecot/dovecot.conf" as some of the option names had changed. The computer has been rebooted since the upgrade. The odd thing is that "dovecot -n" says that ssl_key _is_ set: [gerbil@pleione dovecot]$ dovecot -n # 2.0.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.35-ARCH i686 listen = 127.0.0.1 mail_location = maildir:~/Common/Maildir passdb { driver = pam } service auth { user = root } service imap { process_limit = 5 } service pop3 { process_limit = 5 } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol lda { mail_plugins = sieve postmaster_address = postmaster@localhost } Both of the .pem files do exist (they are unchanged from before the upgrade), and are readable by root: [gerbil@pleione dovecot]$ ls -al /etc/ssl/*/dovecot.pem -rw-r--r-- 1 root root 1005 Nov 2 2009 /etc/ssl/certs/dovecot.pem -rw------- 1 root root 887 Nov 2 2009 /etc/ssl/private/dovecot.pem Any advice you can give would be gratefully received. Many thanks, Glyn

2 2

Re: [Dovecot] dovecot Digest, Vol 90, Issue 3
by arif khwaja 01 Oct '10

01 Oct '10

Dear All, Thanks for all your replied but still I don't know how to install from 1.0.7 to 1.2.14. What should I consider to keep the same configuration during or after upgrade? It is the first time I am trying to upgrade my Dovecot. Thank a lot for your help --- On Fri, 1/10/10, dovecot-request(a)dovecot.org <dovecot-request(a)dovecot.org> wrote: From: dovecot-request(a)dovecot.org <dovecot-request(a)dovecot.org> Subject: dovecot Digest, Vol 90, Issue 3 To: dovecot(a)dovecot.org Date: Friday, 1 October, 2010, 15:25 Send dovecot mailing list submissions to dovecot(a)dovecot.org To subscribe or unsubscribe via the World Wide Web, visit http://dovecot.org/cgi-bin/mailman/listinfo/dovecot or, via email, send a message with subject or body 'help' to dovecot-request(a)dovecot.org You can reach the person managing the list at dovecot-owner(a)dovecot.org When replying, please edit your Subject line so it is more specific than "Re: Contents of dovecot digest..." Today's Topics: 1. Re: Dovecot v0.99.13-3 upgrade to 1.0.15-2 ?? (Noel Butler) 2. Re: how to upgrade dovecot (Noel Butler) 3. Re: Dovecot v0.99.13-3 upgrade to 1.0.15-2 ?? (Jerry) 4. Re: Dovecot v0.99.13-3 upgrade to 1.0.15-2 ?? (Jerry) 5. Re: how to upgrade dovecot (fakessh) 6. Re: Dovecot v0.99.13-3 upgrade to 1.0.15-2 ?? (Stan Hoeppner) 7. v1 ok, v2 not (Alberto) 8. Re: Possible bug with proxy in 2.0.4 (Ed W) ---------------------------------------------------------------------- Message: 1 Date: Fri, 01 Oct 2010 22:37:25 +1000 From: Noel Butler <noel.butler(a)ausics.net> Subject: Re: [Dovecot] Dovecot v0.99.13-3 upgrade to 1.0.15-2 ?? To: dovecot(a)dovecot.org Message-ID: <1285936645.21841.19.camel@tardis> Content-Type: text/plain; charset="utf-8" On Fri, 2010-10-01 at 14:20 +0200, Jakob Curdes wrote: > All true, but there is a current 1.2.14 out there which should probably > be preferred ove a two-and-a-half year old 1.0.15. > Jakob > Indeed, but some people who use certain distros are scared shitless of using source packages and will insist on using a several yo version because thats all <insert distro X or Y here> provides, the 1.2 branch is rock solid stable and time proven, if distro X/Y only oifferes 1.0.x, well, that says a lot about distro X/Y, we all know who X 'n Y are, without mentioning names :)

1 0

[Dovecot] Possible bug with proxy in 2.0.4
by Ed W 01 Oct '10

01 Oct '10

Hi, I *think* there might be an auth/proxy bug in 2.0.4 Specifically I cloned my 1.2 virtual machine, upgraded the clone to 2.0.4 and tested it by trying to login using CRAM-MD5. I get the errors: Sep 29 22:50:23 mail_test dovecot: imap-login: Disconnected (auth failed, 1 attempts): user=<demo(a)abc.com>, method=CRAM-MD5, rip=x.x.x.x, lip=x.x.x.x, mpid=0, TLS Sep 29 22:50:30 mail_test dovecot: auth: mysql: Connected to mysql-local (postfix) Sep 29 22:50:30 mail_test dovecot: imap-login: Error: proxy: password not given: user=<demo(a)abc.com>, method=CRAM-MD5, rip=x.x.x.x, lip=x.x.x.x, mpid=0, TLS Interestingly the config here (accidently as it happens) causes the connection to use the dovecot "proxy" feature back to the original 1.2 machine. I updated my config so that everything stays on the 2.0.4 machine and authentication proceeds normally, messages about generating MD5 hash from the DB, etc, logged in ok. I then change the configuration so that the 2.0.4 machine proxies the connection back to the 1.2 machine (again) and try to login to the 2.0.4 machine and get the same errors as above. Seems like the error is only when proxying (needless to say, the old 1.2 machine works fine with CRAM and that's how it's normally accessed, so also does the 2.0.4 machine, it's only proxying one to the other which isn't apparently working?) It's late and so I haven't managed to probe the 1.2 machine too much, but initially looking at the log files I don't see any evidence of the 2.0.4 machine actually contacting it? Does this make sense? Thanks Ed W

2 4

[Dovecot] v1 ok, v2 not
by Alberto 01 Oct '10

01 Oct '10

hello everybody! This's my very first post in dovecot. I'm installing a new server for backup site, with qmail + vpopmail 5.4.32 + dovecot. Production server, more or less outdated, runs with Couier Imap, but everybody know the history.. I've been fighting for several days...And no luck with version 2.0.4, 2.0.3 neither. My first asumption was to review things thousand of times due to newbie condition... This morning I've tried version 1.2.14 and voila! , it works perfectly! The error log with version 2 was the famous unkown user one: dovecot: auth: vpopmail(test4(a)adomain.com,10.206.16.10): unknown user test4 user worked perfectly with pop3... Just FYI, is this can help. Regards!

1 0

[Dovecot] How does sieve's vacation keep track of duplicates?
by ben＠electricembers.net 01 Oct '10

01 Oct '10

I see the .dovecot.lda-dupes file that is created, but it doesn't seem like just plain text, and it doesn't seem to include strings of the senders, just the recipient. But I know the vacation functionality is clever enough to keep track of who it's already autoreplied to. On a related note, I'm curious about other smarts built in to sieve's vacation responder -- what other things does it check, like Precedence header? Benjamin

2 1

[Dovecot] Vacation script execution question.
by Lauro Costa G. Borges 30 Sep '10

30 Sep '10

dovecot 1.2.9 --- I wanna know how the vacation script works. I don't understand why it tries to find locally (using LDAP) a recipient for the "vacation notification email". On the log, "sender_email(a)gmail.com" is the person sending email to "lauro(a)my.domain.org", which is on vacation. Deliver tries to find locally "sender_email(a)gmail.com", to send the vacation notification message: ---- imap dovecot: deliver(lauro(a)my.domain.org): sieve: msgid=<AANLkTim2HNbM=7WNoMOySg3UXgrikGnVdXR+wjhOG7(a)mail.gmail.com>: sent vacation response to <sender_email(a)gmail.com> imap dovecot: deliver(lauro(a)my.domain.org): Namespace : Using permissions from /var/mail/mailboxes/my.domain.org/lauro~my.domain.org: mode=0700 gid=-1 imap postfix/cleanup[21083]: 3E01140A59: message-id=<dovecot-sieve-1285855441-226458-0@imap> imap postfix/qmgr[21051]: 3E01140A59: from=<>, size=615, nrcpt=1 (queue active) imap postfix/trivial-rewrite[21082]: dict_ldap_debug: ldap_build_search_req ATTRS: associatedDomain imap postfix/local[21089]: warning: dict_ldap_open: /etc/postfix/ldap-domain-maps.cf: Fixed query_filter (objectclass=domainRelatedObject) is probably useless imap postfix/pipe[21090]: warning: dict_ldap_open: /etc/postfix/ldap-domain-maps.cf: Fixed query_filter (objectclass=domainRelatedObject) is probably useless imap dovecot: deliver(sender_email(a)gmail.com): Loading modules from directory: /usr/lib/dovecot/modules/lda imap dovecot: deliver(sender_email(a)gmail.com): Module loaded: /usr/lib/dovecot/modules/lda/lib10_quota_plugin.so imap dovecot: deliver(sender_email(a)gmail.com): Module loaded: /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so imap dovecot: auth(default): master in: USER#0111#011sender_email(a)gmail.com#011service=deliver imap dovecot: auth(default): prefetch(sender_email(a)gmail.com): passdb didn't return userdb entries, trying the next userdb imap dovecot: auth(default): ldap(sender_email(a)gmail.com): user search: base=ou=gmail.com,ou=mail,ou=services,dc=ufsc,dc=br scope=subtree filter=(& (cn=sender_email)(objectclass=nisMailAlias)(ContaAtiva=TRUE) ) fields=rfc822MailMember,EmailQuota,EmailQuotaSpecial,eduPersonPrincipalName imap dovecot: auth(default): ldap(sender_email(a)gmail.com): ldap_search((& (cn=sender_email)(objectclass=nisMailAlias)(ContaAtiva=TRUE) )) failed: No such object : Why is that? ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

[Dovecot] dovecot-lda segfaults with some sieve scripts
by interfaSys sàrl 30 Sep '10

30 Sep '10

Hello, One account couldn't get emails all the sudden. dovecot-lda was crashing with "signal 11 (segmentation fault)". There was absolutely nothing in the dovecot logs, even with mail_debug=yes. I found out that it was because of the following lines in a sieve script that were generated by a script generator (Ingo). if true { keep; stop; } I'm using the latest revision of pigeonhole with Dovecot 2.0.4. Cheers, Olivier

2 9

[Dovecot] Fwd: NFS question
by Nick Edwards 30 Sep '10

30 Sep '10

Resent to list, since my previous direct emails to Timo have gone unanswered I am NOT a member of this list so Timo please reply direct I do not wish responses from those who are not developers of dovecot, many I have since had discussions with on another list and spam binned (abusive souls like charlie marcus) some for trolling, I seek a definitive answer and there is only one man who can give this, but I likely was mailing a old address he doesn't read ---------- Forwarded message ---------- From: Nick Edwards <nick.z.edwards(a)gmail.com> Date: Fri, Sep 24, 2010 at 6:15 PM Subject: NFS question To: timo(a)iki.fi After reading the archives recently on a few threads about NFS I have concerns over our plans to move from cyrus to dovecot, we initially discounted dovecot as a choice over it, but since dovecot and sieve go well together, I am just re-capping everything before we approve move to courier or back to dovecot, having re read those threads over a couple of times, am I right in assuming that this caching problem, is really only a problem if using imap and the chances of it being an issue with pop3 is very rare? If this is the case, then we certainly would approve move to dovecot. I note some people who have apparently much larger systems than us, say that they have seen no problems but others say they may have had just not noticed. So, if smtp3 delivers to storage MailDir and pop3-1 connects to get mail - at the same time: no problem just wont see that message until next refresh at the same time: will see message if smtp3 and smtp1 deliver at same time there lies the corruption issue? If so, it will be reindexed at next delivery or pop3? Just trying to understand where it will be a problem, we will use postfix setting of virtual_transport = dovecot and dovecot_destination_recipient_limit = 1 We dont allow multiple logins either, we have only intention for one imap server, to compliment our two pop3's and 4 smtp's. We intend to use - pop3_lock_session=yes maildir_very_dirty_syncs=yes auth_verbose = yes auth_cache_size = 512 auth_cache_ttl = 3600 auth_cache_negative_ttl = 0 mail_location = maildir:/var/vmail/%1d/%d/%n/Maildir mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes protocol lda { mail_plugins = quota cmusieve quota_full_tempfail = yes auth_socket_path = /var/run/dovecot/auth-master } Also, will this be more of a problem if we use dovecot v1.2 or v2.0 ? (only examples of configs we have for our move is for v1.2 at present for debian) Hope you do not mind me asking this in private, but given how those threads ended up in personal attacks, I would rather not reignite any fires. Nick

6 8

[Dovecot] Problem with dovecot/deliver and SSL in 2.0.4
by Rainer Ophoven 30 Sep '10

30 Sep '10

I'm facing a problem with dovecot/deliver and SSL in 2.0.4 which did not occur in earlier releases: I get this error message: postfix/local[18259]: 687CE86514: to=<rainer(a)homenet.local>, relay=local, delay=0.08, delays=0.02/0/0/0.06, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexe c/dovecot/deliver". Command output: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: ssl enabled, but ssl_key not set ) My System is: Linux mylfs 2.6.27.53 #1 Mon Aug 30 14:28:06 CEST 2010 i686 pentium3 i386 GNU/Linux and dovecot -n reads like this: # 2.0.3: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.53 i686 auth_mechanisms = plain login digest-md5 cram-md5 disable_plaintext_auth = no mail_location = maildir:~/Maildir passdb { args = dovecot driver = pam } passdb { args = /etc/mail/dovecot/dovecot-cram-md5.pwd driver = passwd-file } service auth { user = root } service imap-login { inet_listener imap { address = * } inet_listener imaps { address = * } } service pop3-login { inet_listener pop3 { address = 192.168.1.2 } inet_listener pop3s { address = 192.168.1.2 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol pop3 { pop3_client_workarounds = outlook-no-nuls pop3_uidl_format = %08Xu%08Xv } protocol lda { postmaster_address = postmaster(a)homenet.local sendmail_path = /usr/bin/mutt } I reverted to 2.0.3 and the error does not occur anymore. Rainer Ophoven

3 3

[Dovecot] 1.2.14 --- auth(default) Error: LDAP: Connection lost to LDAP server, reconnecting
by Denny Schierz 30 Sep '10

30 Sep '10

hi, I see in dovecots logfile some error messages: Sep 29 15:33:43 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:34:15 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:34:50 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:35:22 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:36:01 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:36:37 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:37:16 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:37:52 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:38:24 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting I don't know, what could be the problem. I upgraded Dovecot from 1.2.13 to 1.2.14 to solving the problem, but ... no success. Our LDAP Server is 2.4.23 and works for our network without any problems. If I try to use ldapsearch from the Dovecot host, while I see the messages, ldapsearch works withouch any timeout. I enabled caching for auth too, but the problem still exists. My DoveCot Config: http://pastebin.com/W7zHf4fT the LDAP part: hosts = ldap ldap2 auth_bind = yes ldap_version = 3 base = cn=accounts, dc=foo user_attrs = postalAddress=domain, homeDirectory=/imap/spool/%d/%1n/%n, myMailQuota=quota_rule=*:storage=%$M user_filter = (&(objectClass=posixAccount)(uid=%n)) pass_attrs = postalAddress=domain, uid=user, userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%n)) default_pass_scheme = MD5 any suggestions? cu denny ps. when does dovecot switches to ldap2?

3 6

[Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Director instead of LDAP?
by Edward Carraro 29 Sep '10

29 Sep '10

We have a Dovecot installation of several nodes that share an NFS mount for the user data. We are trying to configure Dovecot Proxy with Director in order to have Director select the appropriate IMAP server for a given user on behave of Dovecot Proxy. So far all examples I've seen on the dovecot site require the proxy to know the exact mail server to pass the user to by way of an LDAP lookup. Does anyone know of a way to have Dovecot Proxy pick a server from Directors status list instead of looking it up from LDAP? Also, how does Director discover that an IMAP server is up or down so that it can adjust in the case of a server failure? Is this something that Director does automatically or do we need to manually change the mail servers vhost count in case of an IMAP node failure? Thanks

3 8

[Dovecot] Doveadm expunge purge optimize
by Thiago Henrique 29 Sep '10

29 Sep '10

Hello, I'm testing Dovecot 2.0.3. I plan to use Dovecot with 10 thousands domains per server (~50 thousands accounts). I use 'mdbox' as mailbox format. So, I have two cron jobs before backup: ################################################################################ 01 22 * * * root nice -n 19 /usr/bin/doveadm expunge -A mailbox SPAM BEFORE 60d 01 00 * * * root nice -n 19 /usr/bin/doveadm purge -A 01 02 * * * root nice -n 19 My_Backup_aplication ################################################################################ Each doveadm command walks through the whole file system. Is there a way to run the two operations into a single walk? Does anyone have a suggestion that helps optimize this? Thank you in advance. Best Regards My confs : ################################################################################ root@server:# dovecot -n # 2.0.3 (02a9cf90ad02): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-24-server x86_64 Ubuntu 10.04.1 LTS auth_cache_negative_ttl = 3600 s auth_cache_size = 33554432 auth_master_user_separator = * auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@= auth_worker_max_count = 10 disable_plaintext_auth = no listen = server.com login_greeting = Dovecot server ! mail_gid = dovemail mail_plugins = $mail_plugins quota mail_uid = dovemail managesieve_sieve_capability = fileinto reject envelope vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include imapflags notify mmap_disable = yes passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } plugin { autocreate = SPAM autosubscribe = SPAM quota = dict:User quota::file:/var/lib/imap/user/%2.256RHn/% n/dovecot-quota quota_rule = *:storage=1GB sieve = /var/lib/imap/sieve/%2.256RHn/%n/phpscript.script sieve_dir = /var/lib/imap/sieve/%2.256RHn/%n sieve_extensions = comparator-i;ascii-numeric copy envelope fileinto imapflags include notify regex reject relational subaddress vacation sieve_max_script_size = 512KB sieve_quota_max_scripts = 2 } protocols = imap pop3 lmtp sieve service auth-worker { user = $default_internal_user } service auth { process_limit = 1 process_min_avail = 1 } service imap-login { inet_listener imap { address = server.com port = 143 } } service imap { process_limit = 1024 process_min_avail = 10 } service lmtp { inet_listener { address = server.com port = 2003 } process_limit = 256 process_min_avail = 10 } service managesieve-login { inet_listener sieve { address = server.com port = 4190 } inet_listener sieve_deprecated { address = server.com port = 2000 } } service managesieve { process_limit = 20 process_min_avail = 10 } service pop3-login { inet_listener pop3 { address = server.com port = 110 } } service pop3 { process_limit = 256 process_min_avail = 10 } ssl = no userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol imap { imap_idle_notify_interval = 120 s imap_max_line_length = 65536 mail_max_userip_connections = 10 mail_plugins = $mail_plugins quota imap_quota autocreate } protocol lmtp { mail_plugins = $mail_plugins sieve quota autocreate } protocol sieve { mail_plugins = $mail_plugins sieve managesieve_implementation_string = Dovecot ManageSieve Pigeonhole server managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 managesieve_sieve_capability = comparator-i;ascii-numeric copy envelope fileinto imapflags include notify regex reject relational subaddress vacation } protocol pop3 { mail_plugins = $mail_plugins quota autocreate } root@server:# ################################################################################ -- []'s Thiago Henrique Network Administration Digirati Networks K8 Networks

2 1

[Dovecot] Problem with dovecot-acl
by dss 29 Sep '10

29 Sep '10

I have a problem with dovecot-acl. Some of our users need to use the same Mailbox with all folders: Inbox (with subfolders), Outbox, Send and Deleted, (some users need in full righs, some - readonly) so I choosed Symlinking mailboxes and tried to use dovecot-acl file. cat dovecot-acl: user=t1 lrwsti user=operolegs lrwsti user=operantona lrwsti user=operdss lr User operdss have lrwsti rights in this shared mailbox unstead of lr! But if I comment out other users in the dovecot-acl: #user=t1 lrwsti #user=operolegs lrwsti #user=operantona lrwsti user=operdss lr User operdss have lr rights. Whats wrong? It seems, that dovecot-acl is working only for one user. How can I fix it? === Here is my configs. imap:~# dovecot -n # 1.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian 5.0.6 log_timestamp: %Y-%m-%d %H:%M:%S disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock mail_plugins: acl imap_acl auth default: passdb: driver: pam userdb: driver: passwd plugin: acl: vfile ---- imap:~# ls -l /home/t1/Maildir lrwxrwxrwx 1 root root 21 2010-09-22 16:03 /home/t1/Maildir -> /var/mail/720/Maildir imap:~# ls -l /home/operolegs/Maildir lrwxrwxrwx 1 root root 21 2010-09-23 16:00 /home/operolegs/Maildir -> /var/mail/720/Maildir imap:~# ls -l /home/operantona/Maildir lrwxrwxrwx 1 root root 21 2010-09-23 16:00 /home/operantona/Maildir -> /var/mail/720/Maildir imap:~# ls -l /home/operdss/Maildir lrwxrwxrwx 1 root root 16 2010-09-28 16:32 /home/operdss/Maildir -> /home/t1/Maildir --- imap:/home/t1/Maildir# ls -l total 112 drwxrws--- 2 t1 mshare 4096 2010-09-27 10:46 cur -rw-rw---- 1 t1 mshare 99 2010-09-29 15:56 dovecot-acl -rw-rw---- 1 operdss mshare 312 2010-09-29 16:43 dovecot-acl-list -rw-rw---- 1 operolegs mshare 1144 2010-09-24 12:16 dovecot.index -rw-rw---- 1 t1 mshare 41984 2010-09-28 16:39 dovecot.index.cache -rw-rw---- 1 t1 mshare 25068 2010-09-28 16:38 dovecot.index.log -rw-rw---- 1 operantona mshare 17 2010-09-23 16:41 dovecot-keywords -rw-rw---- 1 operantona mshare 1941 2010-09-27 10:46 dovecot-uidlist -rw-rw---- 1 t1 mshare 8 2010-09-29 16:43 dovecot-uidvalidity -rw-rw---- 1 t1 mshare 0 2010-09-22 10:54 dovecot-uidvalidity.4c99a82f drwxrws--- 2 t1 mshare 4096 2010-09-27 10:46 new -rw-rw---- 1 operdss mshare 327 2010-09-29 16:43 subscriptions drwxrws--- 2 t1 mshare 4096 2010-09-27 10:46 tmp ----- imap:/home/t1/Maildir# dpkg --list|grep dovecot ii dovecot-common 1:1.2.13-1~bpo50+1 secure mail server that supports mbox and maildir mailboxes ii dovecot-imapd 1:1.2.13-1~bpo50+1 secure IMAP server that supports mbox and maildir mailboxes dovecot packages - from backports --- Linux: Debian Lenny up2date

2 1

[Dovecot] problems and dovecot & manegesieve
by Jose Luis Faria 29 Sep '10

29 Sep '10

Hello, my server is working with dovecot-2.0.2+dovecot-2.0-pigeonhole-0.2.0. but if activate managesieve, is not listening in 4190! any help? I setup this: ---------------------------------- ## ## ManageSieve specific settings ## # Service definitions service managesieve-login { inet_listener sieve { port = 4190 } #inet_listener sieve_deprecated { # port = 2000 #} # Number of connections to handle before starting a new process. Typically # the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0 # is faster. <doc/wiki/LoginProcess.txt> #service_count = 1 # Number of processes to always keep waiting for more connections. #process_min_avail = 0 # If you set service_count=0, you probably need to grow this. #vsz_limit = 64M } service managesieve { # Max. number of ManageSieve processes (connections) #process_count = 1024 } # Service configuration protocol sieve { # Maximum ManageSieve command line length in bytes. ManageSieve usually does # not involve overly long command lines, so this setting will not normally need # adjustment #managesieve_max_line_length = 65536 # Maximum number of ManageSieve connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 10 # Space separated list of plugins to load (none known to be useful so far). Do NOT # try to load IMAP plugins here. #mail_plugins = # MANAGESIEVE logout format string: # %i - total number of bytes read from client # %o - total number of bytes sent to client #managesieve_logout_format = bytes=%i/%o # To fool ManageSieve clients that are focused on CMU's timesieved you can specify # the IMPLEMENTATION capability that the dovecot reports to clients. # For example: 'Cyrus timsieved v2.2.13' #managesieve_implementation_string = Dovecot Pigeonhole # Explicitly specify the SIEVE and NOTIFY capability reported by the server before # login. If left unassigned these will be reported dynamically according to what # the Sieve interpreter supports by default (after login this may differ depending # on the user). #managesieve_sieve_capability = #managesieve_notify_capability = # The maximum number of compile errors that are returned to the client upon script # upload or script verification. #managesieve_max_compile_errors = 5 # Refer to 90-sieve.conf for script quota configuration and configuration of # Sieve execution limits. } -- :) cumprimentos ---------------------- José Luís Faria Network Eng./Administrador de Sistemas Departamento de Informática Universidade do Minho Braga, Portugal

2 3

Re: [Dovecot] Sieve during read or login?
by Rick Romero 29 Sep '10

29 Sep '10

Sent from my iPhone On Sep 28, 2010, at 6:43 PM, Stephan Bosch <stephan(a)rename-it.nl> wrote: > Op 28-9-2010 23:02, Rick Romero schreef: >> >> I was wondering if anyone thought of applying filters to email post >> delivery, pre-read. >> >> Basically the idea would be to head off Spam, Malware or Phishing >> for already delivered email. Malware would probably be the least >> likely target, as (knock on wood) user workstations would be >> updated, but a targeted phishing scam would not create a public >> signature that would be downloaded, yet an admin may have a regex >> that could be used to remove that email before it left the server. >> >> I used to run find and grep on my Maildirs, but that's no longer >> practical. I think maybe an 'on connect', or 'on read' might be an >> option. >> > I am not sure I understand the benefit of filtering things like spam > and scams post-delivery as opposed to filtering on-delivery as it is > now. > > Please explain further. If you assume the user retrieves their mail soon after delivery, it doesn't make sense. :) I think the biggest benefit to my service is the catching is phisjing scams aimed at my users. I usually get a copy (dolts), and I will block the reply to addresses, but it would be better to remove it cpmpletely. Another possible use might be URL scanning for updated malware sites and labeling it accordingly -but modifying an email might a little excessive for this function. Rick

1 0

[Dovecot] Sieve during read or login?
by Rick Romero 29 Sep '10

29 Sep '10

I was wondering if anyone thought of applying filters to email post delivery, pre-read. Basically the idea would be to head off Spam, Malware or Phishing for already delivered email. Malware would probably be the least likely target, as (knock on wood) user workstations would be updated, but a targeted phishing scam would not create a public signature that would be downloaded, yet an admin may have a regex that could be used to remove that email before it left the server. I used to run find and grep on my Maildirs, but that's no longer practical. I think maybe an 'on connect', or 'on read' might be an option. Thoughts? Rick

2 1

[Dovecot] auth: Fatal: Unknown passdb driver 'mysql'
by Vaidas Jablonskis 29 Sep '10

29 Sep '10

Hi People, I am setting up a new dovecot server for testing first prior production upgrade from 1.2.x to 2.0.x. I used the RPMs from ATrpms: dovecot-2.0.0-1_117.el5.x86_64.rpm The errors I am getting: ----------------------------- Aug 27 18:15:29 testbox dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Aug 27 18:15:29 testbox dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so Aug 27 18:15:29 testbox dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so Aug 27 18:15:29 testbox dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_pgsql.so Aug 27 18:15:29 testbox dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Aug 27 18:15:29 testbox dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libmech_gssapi.so Aug 27 18:15:29 testbox dovecot: auth: Fatal: Unknown passdb driver 'mysql' Aug 27 18:15:29 testbox dovecot: master: Error: service(auth): command startup failed, throttling Aug 27 18:15:59 testbox dovecot: imap-login: Error: Timeout waiting for handshake from auth server. my pid=4323, input bytes=0 ------------------------------ # dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: cydir maildir mbox mdbox raw sdbox shared SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) nss passwd prefetch passwd-file sql # ls -l /usr/lib64/dovecot/*sql* -rwxr-xr-x 1 root root 15704 Aug 20 16:51 /usr/lib64/dovecot/libdriver_mysql.so -rwxr-xr-x 1 root root 21464 Aug 20 16:51 /usr/lib64/dovecot/libdriver_pgsql.so -rwxr-xr-x 1 root root 11848 Aug 20 16:51 /usr/lib64/dovecot/libdriver_sqlite.so It is clearly seen that mysql drivers are installed and being loaded during dovecot startup. ----------------------- /etc/dovecot/conf.d/auth-sql.conf.ext passdb { driver = mysql args = /etc/dovecot/dovecot-sql.conf.ext } userdb { driver = prefetch } userdb { driver = mysql args = /etc/dovecot/dovecot-sql.conf.ext } ------------------------- Any ideas what else could be wrong? Thanks, Vaidas

2 2