- dovecot - dovecot.org

[Dovecot] Ignoring the quota by the LDA?
by Holger Richter 07 Jun '10

07 Jun '10

Is it possible to configure dovecot in a manner that only the imap process respects the quota, and the local delivery ignores completely the quota? I think it should happen if I don't activate the quota plugin in the lda section but only in the imap section. protocol lda { ... # mail_plugins = ... } protocol imap { ... mail_plugins = quota imap_quota ... } Will it work or will it result in a big mess? I've the aim that a mail will never be rejected because the recipient is over his/her quota. Regards, Holger

3 4

Re: [Dovecot] Problems with the IMAP proxy after upgrading from dovecot 1.1.16 to 1.211
by Holger Richter 07 Jun '10

07 Jun '10

>> >> May 7 14:47:42 ttt dovecot: auth(default): >> >> worker-server(uid,yyy.yyy.yyy.yyy): Aborted: Lookup timed out >> >> May 7 14:47:42 ttt dovecot: auth-worker(default): mysql: Connected to >> >> lll.lll.lll.lll (imapauth) >> > >> > "Lookup timed out" really shouldn't be happening.. That sounds like >> > Dovecot's MySQL connections hangs after a while? You have some stateful >> > firewall between Dovecot and MySQL that drops idling connections and >> > afterwards starts dropping the connection's packets? >> >> Indeed, there is a firewall with stateful inspection between Dovecot >> and MySQL. > > Right, so the "Lookup timed out" works as intended. But I guess it > should automatically retry when that happens. There would still be that > 1 minute delay before that happens though. > >> The only workaround is a downgrade to Dovecot 1.1.20. > > Wonder what v1.1 does differently. I can't think of anything, really. > The main fundamental problem is still that mysql connection hangs and > the hang can't be detected/avoided. I think the right fix here would be > to change your firewall settings.. > >> I think my problem has to do with the changes in >> src/auth/auth-worker-server.c in changeset 8859. > > 8559:b0bc4519332f? Yep.

1 0

[Dovecot] Problems with the IMAP proxy after upgrading from dovecot 1.1.16 to 1.211
by Holger Richter 07 Jun '10

07 Jun '10

We have frequent timeout problems after upgrading our imap servers from dovecot 1.1.16 to dovecot 1.2.11. One server acts as proxy only, and the other one is the "real" imap server". The credentials for the proxy service are stored in a remote MYSQL database. There were no trouble with dovecot 1.1.16. But now, with the most recent version, we get frequent login failures. It seems dovecot reconnects too late to the MySQL database after a timeout, after sending the SQL query. Here's a piece of my log file: May 7 14:46:32 ttt dovecot: auth(default): new auth connection: pid=5136 May 7 14:46:42 ttt dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=imap^Isecured^Ilip=xxx.xxx.xxx.xxx^Irip=yyy.yyy.yyy.yyy^Ilport=sss^Irport=26480^Iresp=<hidden> May 7 14:46:42 ttt dovecot: auth-worker(default): sql(uid,yyy.yyy.yyy.yyy): query: SELECT NULL as password, destuser, host, 'zzz' as port, 'Y' as proxy, '0' as proxy_timeout, 'Y' as nopassword, 'Y' as nodelay from accounts where user ='uid'; May 7 14:47:42 ttt dovecot: auth(default): worker-server(uid,yyy.yyy.yyy.yyy): Aborted: Lookup timed out May 7 14:47:42 ttt dovecot: auth-worker(default): mysql: Connected to lll.lll.lll.lll (imapauth) May 7 14:47:44 ttt dovecot: auth(default): client out: FAIL^I1^Iuser=uid^Itemp May 7 14:47:49 ttt dovecot: imap-login: Disconnected (auth failed, 1 attempts): user=<uid>, method=PLAIN, rip=yyy.yyy.yyy.yyy, lip=xxx.xxx.xxx.xxx, TLS May 7 14:48:26 ttt dovecot: auth(default): new auth connection: pid=5159 May 7 14:48:47 ttt dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=imap^Isecured^Ilip=xxx.xxx.xxx.xxx^Irip=yyy.yyy.yyy.yyy^Ilport=sss^Irport=6243^Iresp=<hidden> May 7 14:48:47 ttt dovecot: auth-worker(default): sql(uid,yyy.yyy.yyy.yyy): query: SELECT NULL as password, destuser, host, 'zzz' as port, 'Y' as proxy, '0' as proxy_timeout, 'Y' as nopassword, 'Y' as nodelay from accounts where user ='uid'; May 7 14:48:47 ttt dovecot: auth(default): client out: OK^I1^Iuser=uid^Idestuser=luid^Ihost=mmm.mmm.mmm.mmm^Iport=zzz^Iproxy^Iproxy_timeout=0^Ipass=<hidden> May 7 14:48:47 ttt dovecot: imap-login: proxy(uid): started proxying to mmm.mmm.mmm.mmm:zzz/luid: user=<uid>, method=PLAIN, rip=yyy.yyy.yyy.yyy, lip=xxx.xxx.xxx.xxx, TLS May 7 14:48:48 ttt dovecot: imap-login: proxy(uid): disconnecting yyy.yyy.yyy.yyy As you can see, the second login attempt is always successful. Of course I've tried out various values (0, 60, 90, 300) for the proxy_timeout parameter - but without any success.

2 2

[Dovecot] authentification failure: double quotes in password
by Martin Ott 07 Jun '10

07 Jun '10

we use Passdb LDAP with authentication binds against an Active Directory Server. The problem with one of our users seems to be the usage of double quotes in his password, as the windows-login works: /var/log/dovecot-info.log auth(default): Info: ldap(testuser 77.22.xx.xxx): invalid credentials (given password: xxxxx"xxxxxxx) Which chars in passwords does the dovecot auth process not like? Is there something similar to auth_username_chars for passwords? thanks, martin

2 2

[Dovecot] Dovecot SSL/TLS on multiple interfaces ?
by Frank Bonnet 07 Jun '10

07 Jun '10

Hello I have a server which has two gigabits interfaces with different IP addresses and DNS names I would like to let IMAP(S) users access both. Is it possible to generate a SSL cert for each IP address on the same dovecot instance in the configuration file ? Thanks a lot

2 2

[Dovecot] How to autosubscribe Folder in dovecot
by mungalal2000＠indiatimes.com 07 Jun '10

07 Jun '10

Hi all, I have changed my imap server from courier to dovecot, Now i am facing problem to subscribe the existing mail folder after change of imap server by default they are showing in the unsubscribe folder list, is there any command or mechanism in dovecot to subscribe all the folder. i am using maildir format to store mail. Thanks & Regards. Munga (System Engginer) -- Click for exclusive coverage on the New Bajaj Pulsar 220 the fastest Indian bike http://www.zigwheels.com/Features/Bajaj-Pulsar-220-DTSi-Special-Coverage/Pu…

3 3

[Dovecot] raw backtrace in masses
by John Adams 06 Jun '10

06 Jun '10

Hi I've got huge amounts of May 3 15:47:37 host dovecot: [ID 583609 mail.error] IMAP(user): close(/home/user/Mail/R-Help.lock) failed: Disc quota exceeded May 3 15:47:37 host dovecot: [ID 583609 mail.error] IMAP(user): Raw backtrace: 0xb0e58 -> 0xb0894 -> 0x552b4 -> 0x55508 -> 0x55774 -> 0x55d9c -> 0x5759c -> 0x57ad0 -> 0x713cc -> 0x64284 -> 0x57be0 -> 0x71178 -> 0x6841c -> 0x76a38 -> 0x76a6c -> 0x25a08 -> 0x2afd4 -> 0x2bee4 -> 0x2bea0 -> 0x2c1f8 -> 0x2cb4c -> 0xb9450 -> 0xb8d00 -> 0x35294 -> 0x246e8 May 3 15:47:37 host dovecot: [ID 583609 mail.error] dovecot: child 3892 (imap) killed with signal 6 (core dumps disabled) May 3 15:47:49 host dovecot: [ID 583609 mail.error] IMAP(user): Raw backtrace: 0xb0e58 -> 0xb0894 -> 0x552b4 -> 0x55508 -> 0x55774 -> 0x55d9c -> 0x5759c -> 0x57ad0 -> 0x713cc -> 0x64284 -> 0x57be0 -> 0x71178 -> 0x6841c -> 0x76a38 -> 0x76a6c -> 0x25a08 -> 0x2afd4 -> 0x2bee4 -> 0x2bea0 -> 0x2c1f8 -> 0x2cb4c -> 0xb9450 -> 0xb8d00 -> 0x35294 -> 0x246e8 May 3 15:47:49 host dovecot: [ID 583609 mail.error] dovecot: child 4277 (imap) killed with signal 6 (core dumps disabled) The backtrace is always the same content. is this a disc quota problem? Dovecot is 1.2.11, managesieve patched. Thanks

3 9

[Dovecot] DOES NOT PERTAIN TO DOVECOT: Does anyone use postfix for some help?
by Jerrale Gayle 05 Jun '10

05 Jun '10

When mail is sent from the mail server, it shows up as originating from the MAIN ip address of the server, 173.50.101.11, when the mail server is bound to 173.50.101.12. I have already set smtp_bind_address: 173.50.101.12 in main.cf and 173.50.101.12:smtp inet - - smtpd in master.cf. This prevents smtp connects TO any other ip but 173.50.101.12 BUT mail STILL shows up originating from eth1, where 173.50.101.12 is eth1:2 I think this is *nix related and most here, on dovecot mailing list, could provide help.

3 2

[Dovecot] mdbox error with 2.0.beta5
by Mike Abbott 05 Jun '10

05 Jun '10

Running 2.0.beta5 on Mac OS X with HFS+J, I often see this error in the log: Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Error: mdbox /var/spool/imap/dovecot/mail/mailboxes/INBOX/Foobar/dbox-Mails: map uidvalidity mismatch (1273852899 vs 1273853949) Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Disconnected: Internal error occurred. Refer to server log for more information. [2010-05-14 12:25:59] bytes=1337/4443 Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Warning: mdbox /var/spool/imap/dovecot/mail/storage: rebuilding indexes The logs also reveal that this user was logged in twice at the time. There appear to be two issues here: the uidvalidity mismatch, and the path in the "rebuilding indexes" message does not match the path in the "uidvalidity mismatch" error.

2 6

[Dovecot] Managesieve connection hangs with TLS
by Joel James Adamson 04 Jun '10

04 Jun '10

Hello, I've got dovecot 1.2.11 running on Fedora 12 (x86_64) with the managesieve protocol and sieve plugins enabled, with deliver handling local delivery. I've set disable_plaintext_auth = yes ssl = yes ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem ssl_key_file = /etc/pki/dovecot/private/dovecot.pem mail_debug = yes protocol managesieve { listen = *:2000 login_executable = /usr/libexec/dovecot/managesieve-login mail_executable = /usr/libexec/dovecot/managesieve } and generated local SSL certificates; everything is going fine on the IMAP end of things (clients ask if I trust the certificate the first time, etc). I've open the appropriate ports, etc. No problems with mail delivery. However, I can't connect to the managesieve daemon. I've tried the Emacs client[1], and it just hangs. I tried manual login to port 2000 and here's what happened: joel@chondestes: /etc/mail > gnutls-cli --starttls -p 2000 localhost Resolving 'localhost'... Connecting to '127.0.0.1:2000'... - Simple Client Mode: "IMPLEMENTATION" "dovecot" "SIEVE" "comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date" "SASL" "PLAIN" "STARTTLS" "NOTIFY" "mailto" "VERSION" "1.0" OK "Dovecot ready." *** Starting TLS handshake C-c C-c That last line is me hanging up in Emacs' shell buffer because nothing was happening. Sorry to sound like such a newbie, but what do I need on the client end to complete the TLS transaction? What else do I need to set up to get managesieve to connect? Thanks, Joel Footnotes: [1] http://josefsson.org/sieve/ -- Joel J. Adamson Servedio Lab University of North Carolina at Chapel Hill FSF Member #8164 http://www.unc.edu/~adamsonj

2 2