- dovecot - dovecot.org

[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