December 2011 - dovecot

[Dovecot] compile dovecot-sieve for dovecot 1.2.9 (ubuntu pkg)
by Julien Lacroix 21 Dec '11

21 Dec '11

Cheers, I've a running Dovecot 1.2.9, installed from the ubuntu 10.04 Lucid LTS repository and trying to get the dovecot-sieve plugin (which seems to be not included in the lucid repo) compiled. Method 1 listed in http://wiki.dovecot.org/LDA/Sieve/Dovecot wont work, seems the rpm was build without --enable-header-install Is it sufficient to download the sources from http://archive.ubuntu.com/ubuntu/pool/main/d/dovecot/dovecot_1.2.9.orig.tar… and use them for ./configure --with-dovecot=$path ? thanks and happy holidays julien

1 0

[Dovecot] Can I block dovecot from deleting read messages, after being fetched?
by Vasiliu Adrian 21 Dec '11

21 Dec '11

Hi all, Is there an option to disable (server-side) the deletion of read mails after fetching them via POP3, regardless of the MUA config? Here are the issues I'm facing: - my boss wants to force everyone into a server-side "no delete message"-policy, for archiving, auditing and backup&recovery purposes - the requisite here is pop3, so imap is out - the mailusers are virtual users (held in a mysql db) - don't have the budget to set up a separate mail-arvhing server - don't want to use shaggy ways (aka immutable flag, r/w permissions for Maildirs, etc) dovecot --version 2.0.15 Help? Thanks!

3 2

[Dovecot] Sieve filter not working
by Lars Larsen 21 Dec '11

21 Dec '11

Hi, Dovecot, the "deliver" LDA and managesieve are all working. However, the sieve rules do not seem to work: System info: CenOS 2.6.32-131.21.1.el6.x86_64 #1 SMP dovecot-pigeonhole-2.0.9-2.el6_1.1.x86_64 dovecot-2.0.9-2.el6_1.1.x86_64 /etc/dovecot/dovecot.conf: mbox_write_locks = fcntl protocols = imap pop3 sieve passdb { driver = pam } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } /etc/dovecot/conf.d/15-lda.conf: postmaster_address = postmaster(a)ourdomain.net hostname = mail.ourdomain.net sendmail_path = /usr/sbin/sendmail lda_mailbox_autocreate = yes protocol lda { log_path = info_log_path = syslog_facility = messages mail_plugins = sieve } /etc/dovecot/conf.d/90-sieve.conf plugin { sieve = ~/sieve/roundcube.sieve sieve_dir = ~/sieve } /home/lars/sieve/roundcube.sieve: require ["fileinto"]; # rule:[admin-root] if anyof (header :contains "From" "root", header :contains "Subject" "logwatch") { fileinto "Admin"; }

1 0

Re: [Dovecot] Why imap_open doesn't work as is expected to?
by Joseph Tam 21 Dec '11

21 Dec '11

I M <profymath(a)yahoo.com> writes: > Question: Why imap_open function doesn't work while getting a mailbox through telnet works perfectly? > Note:?imap.so is loaded!?imap.ini is parsed!? After the imap_open() invocation, you should check for error messages in your PHP logs, or dump all the errors using imap_errors(); Without more details, I would say you dropped one of those /option-flags or got the mailbox argument syntax wrong. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Mail lost - maybe a bug???
by Marco Carcano 21 Dec '11

21 Dec '11

Hello everybody I'm struggling against what seems a really serious trouble: sometimes mail get lost I did all the possible checks, but they seems really lost - I know is absurd, but it seems so it has been noticed by two users on my server: intially I tought that was their mistake (mail deleted, mail into spam, ecc), but it wasn't I deeply checked mail logs, and it seems that mail are delivered (the path is postfix->amavis->dovecotlda) - log files says that messages are delivered, but sometimes we lost a message. I also tried to get into the Maildir and grep the subject of the lost email: if it was addressed to more recipients I'm able to get it on some of them, but not to all (look at the example below) I hope I have clearly explained everything, otherwise let me knowmydomain now an extract from the log file: Oct 27 11:20:29 srv001 postfix/smtpd[24562]: connect from usstlz- psecap06.emerson.com[144.191.128.17] Oct 27 11:20:30 srv001 postfix/smtpd[24562]: CE0B74E4A9F: client=usstlz-psecap06.emerson.com[144.191.128.17] Oct 27 11:20:31 srv001 postfix/cleanup[25157]: CE0B74E4A9F: warning: header Subject: =?utf-8?B? RW1lcnNvbiBHbG9iYWwgVXNlcnMgRXhjaGFuZ2UgMjAxMiBpbiBEw7xzc2VsZG9yZiA6IFJlaWNoZW4gU2llIGpldHp0IElocmUgUHLDpHNlbnRhdGlvbmVuIGVpbg ==?= from usstlz-psecap06.emerson.com[144.191.128.17]; from=<Emerson.News(a)emersonprocess.com > to=<oil(a)mydomain.ch> proto=ESMTP helo=<USSTLZ-PSECAP06.EMERSON.COM> Oct 27 11:20:31 srv001 postfix/cleanup[25157]: CE0B74E4A9F: message- id=<e9447410-51fe-45ff-b624-197840b9a862(a)usstlz-pinfez02.emrsn.org> Oct 27 11:20:31 srv001 postfix/qmgr[11827]: CE0B74E4A9F: from=<Emerson.News(a)emersonprocess.com >, size=22689, nrcpt=3 (queue active) Oct 27 11:20:33 srv001 dovecot: imap(lromano): Disconnected: Logged out bytes=632/34319 Oct 27 11:20:34 srv001 postfix/smtpd[25162]: connect from localhost.localdomain[127.0.0.1] Oct 27 11:20:34 srv001 postfix/smtpd[25162]: B16284E4AA2: client=localhost.localdomain[127.0.0.1] Oct 27 11:20:34 srv001 postfix/cleanup[25157]: B16284E4AA2: message- id=<e9447410-51fe-45ff-b624-197840b9a862(a)usstlz-pinfez02.emrsn.org> Oct 27 11:20:34 srv001 postfix/qmgr[11827]: B16284E4AA2: from=<Emerson.News(a)emersonprocess.com >, size=23094, nrcpt=3 (queue active) Oct 27 11:20:34 srv001 amavis[22923]: (22923-01) Passed CLEAN, [144.191.128.17] [155.177.20.144] <Emerson.News(a)emersonprocess.com> -> <user1(a)mydomain.local>,<user2(a)mydomain.local>,<user3(a)mydomain.local>, Message-ID: <e9447410-51fe-45ff-b624-197840b9a862(a)usstlz-pinfez02.emrsn.org >, mail_id: 6rtF4927FAjt, Hits: -0.518, size: 22687, queued_as: B16284E4AA2, 3293 ms Oct 27 11:20:34 srv001 postfix/lmtp[25158]: CE0B74E4A9F: to=<user1(a)mydomain.local >, orig_to=<oil(a)mydomain.ch>, relay=127.0.0.1[127.0.0.1]:10024, delay=4.2, delays=0.95/0.01/0.01/3.3, dsn=2.0.0, status=sent (250 2.0.0 from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as B16284E4AA2) Oct 27 11:20:34 srv001 postfix/lmtp[25158]: CE0B74E4A9F: to=<user2(a)mydomain.local >, orig_to=<oil(a)mydomain.ch>, relay=127.0.0.1[127.0.0.1]:10024, delay=4.2, delays=0.95/0.01/0.01/3.3, dsn=2.0.0, status=sent (250 2.0.0 from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as B16284E4AA2) Oct 27 11:20:34 srv001 postfix/lmtp[25158]: CE0B74E4A9F: to=<user3(a)mydomain.local >, orig_to=<oil(a)mydomain.ch>, relay=127.0.0.1[127.0.0.1]:10024, delay=4.2, delays=0.95/0.01/0.01/3.3, dsn=2.0.0, status=sent (250 2.0.0 from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as B16284E4AA2) Oct 27 11:20:34 srv001 postfix/qmgr[11827]: CE0B74E4A9F: removed Oct 27 11:20:34 srv001 dovecot: lda(user1): msgid=<e9447410-51fe-45ff-b624-197840b9a862(a)usstlz-pinfez02.emrsn.org >: saved mail to INBOX Oct 27 11:20:34 srv001 postfix/pipe[25165]: B16284E4AA2: to=<user1(a)mydomain.local >, relay=dovecot, delay=0.04, delays=0.01/0.01/0/0.02, dsn=2.0.0, status=sent (delivered via dovecot service) Oct 27 11:20:34 srv001 dovecot: lda(user2): msgid=<e9447410-51fe-45ff-b624-197840b9a862(a)usstlz-pinfez02.emrsn.org >: saved mail to INBOX Oct 27 11:20:34 srv001 postfix/pipe[25168]: B16284E4AA2: to=<user2(a)mydomain.local >, relay=dovecot, delay=0.04, delays=0.01/0.01/0/0.02, dsn=2.0.0, status=sent (delivered via dovecot service) Oct 27 11:20:34 srv001 dovecot: lda(user3): msgid=<e9447410-51fe-45ff-b624-197840b9a862(a)usstlz-pinfez02.emrsn.org >: saved mail to INBOX Oct 27 11:20:34 srv001 postfix/pipe[25170]: B16284E4AA2: to=<user3(a)mydomain.local >, relay=dovecot, delay=0.05, delays=0.01/0.02/0/0.02, dsn=2.0.0, status=sent (delivered via dovecot service) Oct 27 11:20:34 srv001 postfix/qmgr[11827]: B16284E4AA2: removed Oct 27 11:20:36 srv001 postfix/smtpd[24562]: disconnect from usstlz- psecap06.emerson.com[144.191.128.17] as you can see there was a message for oil(a)mydomain.ch (I obviously changed the domain for privacy) - logs says that all the three users got the email, but the third user didn't. I do not know why and when it happens, but seldom we have this issue maybe is there some kind of bug in the maildrop version I use? by the way, I had this issue also before installing amavisd-new now some infos: CentOS 5.3 postfix-2.3.3-2.1.el5_2 amavisd-new-2.6.6-1.el5.rf dovecot-2.0.11-1_126 dovecot-managesieve-0.2.2-15 dovecot-pigeonhole-0.2.2-15 users are on a Kerberized OpenLDAP please help me because this is really driving me crazy - don't leave me alone, please Marco Carcano

4 10

[Dovecot] APOP and AuthDatabase/SQL
by Peter Smith 21 Dec '11

21 Dec '11

Hi, We're running dovecot 1.2.15 and use SQL authentication. We'd like to be able to support APOP, but can't see how this would fit in with SQL auth. Currently we have: password_query = SELECT email as user, password FROM virtual_users WHERE email='%u' or (email LIKE '%n@%%' AND unhashed='%w') It seems that in order to auth APOP logins, we'd need to access variables containing the authentication string sent by the client, and also variables containing the auth string sent in the POP3 greeting. Incidentally, the RFC (1939) suggests using: <pid.time@hostname> for the greeting, but it looks as if dovecot uses something else? I'm seeing greetings such as: +OK Dovecot ready. <260f.4abcc.4ef11550.cJD6sQSUSnmPS1B/5RGF0Q==(a)myhostname.com> base64 encoding? Thanks in advance, Peter Smith

2 1

[Dovecot] Why imap_open function doesn't work while getting a mailbox through telnet works perfectly?
by I M 20 Dec '11

20 Dec '11

Hi, everybody! Question: Why imap_open function doesn't work while getting a mailbox through telnet works perfectly? Note: imap.so is loaded! imap.ini is parsed!php flags is checked! Is it a bug?

2 1

[Dovecot] Why imap_open doesn't work as is expected to?
by I M 20 Dec '11

20 Dec '11

Hi, everybody! Question: Why imap_open function doesn't work while getting a mailbox through telnet works perfectly? Note: imap.so is loaded! imap.ini is parsed!

1 0

[Dovecot] Sieve too rfc compliant ;-)
by Jan-Frode Myklebust 20 Dec '11

20 Dec '11

It seems we have a few email addresses that are not RFC 5322 compliant, and now that we've started using sieve these are failing. The problem is that we have a few addresses with leading, trailing or double dots in the local part: jan..frode(a)tanso.net .janfrode(a)tanso.net janfrode.(a)tanso.net I believe these has been working fine with everything else in dovecot (lda, lmtp, imap, pop), but that sieve is more strict. I think it's fair enough that it's strict with messages generated by sieve scripts, but it would be nice if it could be more tolerant with messages addressed for the sieve script. So, is there any setting for making it more tolerant ? -jf

2 1

Re: [Dovecot] Question about index reset in dovecot 2.0.15
by Maria Arrea 20 Dec '11

20 Dec '11

Hello Timo, thank you in advance. Full log here (1 hour time range) Dec 14 21:19:43 buzon postfix/pipe[27103]: 4423BC7C31: to=<fmcarrasco@domain>, relay=dovecot, delay=0.24, delays=0.03 /0/0/0.2, dsn=2.0.0, status=sent (delivered via dovecot service) Dec 14 21:20:59 buzon dovecot: imap(fmcarrasco): Disconnected: Logged out bytes=556/2245 Dec 14 21:44:30 buzon dovecot: imap(fmcarrasco): Error: /indices_dovecot/indices/07/47/fmcarrasco/mailboxes/INBOX/dovecot.index reset, view is now inconsistent Dec 14 21:44:30 buzon dovecot: imap(fmcarrasco): Disconnected: IMAP session state is inconsistent, please relogin. bytes=42402/3153543 Dec 14 21:45:30 buzon dovecot: imap-login: Login: user=<fmcarrasco>, method=PLAIN, rip=192.168.1.13, lip=192.168.4.80, mpid=20035, TLS Dec 14 22:01:27 buzon dovecot: imap(fmcarrasco): Error: /indices_dovecot/indices/07/47/fmcarrasco/mailboxes/INBOX/dovecot.index reset, view is now inconsistent Dec 14 22:01:27 buzon dovecot: imap(fmcarrasco): Disconnected: IMAP session state is inconsistent, please relogin. bytes=343/8671 Dec 14 22:02:58 buzon dovecot: imap-login: Login: user=<fmcarrasco>, method=PLAIN, rip=192.168.1.13, lip=192.168.4.80, mpid=2685, TLS Dec 14 22:13:46 buzon dovecot: lda(fmcarrasco): sieve: msgid=<f81a253ebaceca9bf0a6635027e4d747s>: stored mail into mailbox 'INBOX' Dec 14 22:13:46 buzon postfix/pipe[21152]: AAD36C8501: to=<fmcarrasco>, relay=dovecot, delay=0.34, delays=0.03/0.01/0/0.31, dsn=2.0.0, status=sent (delivered via dovecot service) The other one: Dec 14 20:53:38 buzon dovecot: pop3(cfp): Connection closed top=0/0, retr=0/0, del=0/3605, size=446902389 Dec 14 21:38:34 buzon postfix/qmgr[4015]: A90CFC7C31: from=<scet2012a(a)confcfp.org>, size=23256, nrcpt=1 (queue active) Dec 14 21:43:00 buzon postfix/qmgr[4015]: E7E61C7DED: from=<scet2012a(a)confcfp.org>, size=23244, nrcpt=1 (queue active) Dec 14 21:50:38 buzon dovecot: imap(cfp): Error: /indices_dovecot/indices/16/58/cfp/mailboxes/Sent/dovecot.index reset, view is now inconsistent Dec 14 21:50:38 buzon dovecot: imap(cfp): Disconnected: IMAP session state is inconsistent, please relogin. bytes=32118/127014 Dec 14 21:50:38 buzon dovecot: imap(cfp): Error: Recent flags state corrupted for mailbox Trash Dec 14 21:50:38 buzon dovecot: imap(cfp): Error: /indices_dovecot/indices/16/58/cfp/mailboxes/Trash/dovecot.index reset, view is now inconsistent Dec 14 21:50:38 buzon dovecot: imap(cfp): Disconnected: IMAP session state is inconsistent, please relogin. bytes=38097/309083 Dec 14 21:50:38 buzon dovecot: imap(cfp): Error: Recent flags state corrupted for mailbox Preinscripcion Dec 14 21:50:38 buzon dovecot: imap(cfp): Error: /indices_dovecot/indices/16/58/cfp/mailboxes/Preinscripcion/dovecot.index reset, view is now inconsistent Dec 14 21:50:38 buzon dovecot: imap(cfp): Disconnected: IMAP session state is inconsistent, please relogin. bytes=33263/164275 Dec 14 21:50:38 buzon dovecot: imap(cfp): Error: /indices_dovecot/indices/16/58/cfp/mailboxes/Emagister/dovecot.index reset, view is now inconsistent Dec 14 21:50:38 buzon dovecot: imap(cfp): Disconnected: IMAP session state is inconsistent, please relogin. bytes=35437/111594 Dec 14 21:50:38 buzon dovecot: imap-login: Login: user=<cfp>, method=PLAIN, rip=192.168.1.13, lip=192.168.4.80, mpid=24811, TLS Dec 14 21:50:39 buzon dovecot: imap-login: Login: user=<cfp>, method=PLAIN, rip=192.168.1.13, lip=192.168.4.80, mpid=24822, TLS Dec 14 21:52:12 buzon postfix/cleanup[21212]: 9A22CC816C: message-id=<CAP3xem+Vzw4b_dmDnr=ajn9cfpA8TNotxAVbkM5xoBzxPfu_bQ(a)mail.gmail.com> Dec 14 22:00:27 buzon dovecot: imap(cfp): Error: /indices_dovecot/indices/16/58/cfp/mailboxes/Sent/dovecot.index reset, view is now inconsistent Dec 14 22:00:27 buzon dovecot: imap(cfp): Disconnected: IMAP session state is inconsistent, please relogin. bytes=554/169764 Dec 14 22:00:27 buzon dovecot: imap(cfp): Error: /indices_dovecot/indices/16/58/cfp/mailboxes/Trash/dovecot.index reset, view is now inconsistent Dec 14 22:00:27 buzon dovecot: imap(cfp): Disconnected: IMAP session state is inconsistent, please relogin. bytes=533/10963 Dec 14 22:00:27 buzon dovecot: imap(cfp): Error: /indices_dovecot/indices/16/58/cfp/mailboxes/Preinscripcion/dovecot.index reset, view is now inconsistent Dec 14 22:00:27 buzon dovecot: imap(cfp): Disconnected: IMAP session state is inconsistent, please relogin. bytes=629/39790 Dec 14 22:00:27 buzon dovecot: imap(cfp): Error: /indices_dovecot/indices/16/58/cfp/mailboxes/INBOX/dovecot.index reset, view is now inconsistent Dec 14 22:00:27 buzon dovecot: imap(cfp): Disconnected: IMAP session state is inconsistent, please relogin. bytes=613/496956 Dec 14 22:00:27 buzon dovecot: imap-login: Login: user=<cfp>, method=PLAIN, rip=192.168.1.13, lip=192.168.4.80, mpid=464, TLS Dec 14 22:00:27 buzon dovecot: imap-login: Login: user=<cfp>, method=PLAIN, rip=192.168.1.13, lip=192.168.4.80, mpid=465, TLS Dec 14 22:00:27 buzon dovecot: imap-login: Login: user=<cfp>, method=PLAIN, rip=192.168.1.13, lip=192.168.4.80, mpid=466, TLS Dec 14 22:00:27 buzon dovecot: imap-login: Login: user=<cfp>, method=PLAIN, rip=192.168.1.13, lip=192.168.4.80, mpid=467, TLS Dec 14 22:30:28 buzon dovecot: pop3-login: Login: user=<cfp>, method=PLAIN, rip=192.168.1.13, lip=192.168.4.80, mpid=25194 I do not see any pattern about this problem of index reset, logs from other day, maybe the problem is I/O load based: Dec 15 13:16:06 buzon dovecot: imap(ehlers): Connection closed bytes=357/20249 Dec 15 13:16:06 buzon dovecot: imap(ehlers): Connection closed bytes=70/12804 Dec 15 13:16:12 buzon dovecot: imap-login: Login: user=<ehlers>, method=PLAIN, rip=192.168.1.150, lip=192.168.4.80, mpid=1005 Dec 15 13:16:12 buzon dovecot: imap(ehlers): Connection closed bytes=103/818 Dec 15 13:16:19 buzon dovecot: imap-login: Login: user=<ehlers>, method=PLAIN, rip=192.168.1.150, lip=192.168.4.80, mpid=1419 Dec 15 13:16:19 buzon dovecot: imap(ehlers): Error: Mailbox Archivador/Facultad/curso whiteboard: Corrupted index, uidvalidity=0 Dec 15 13:16:19 buzon dovecot: imap(ehlers): Warning: mdbox /buzones/domain/11/53/ehlers/storage: rebuilding indexes Dec 15 13:16:19 buzon dovecot: imap-login: Login: user=<ehlers>, method=PLAIN, rip=192.168.1.150, lip=192.168.4.80, mpid=1426 Dec 15 13:16:19 buzon dovecot: imap(ehlers): Connection closed bytes=459/3205 Dec 15 13:16:32 buzon dovecot: imap(ehlers): Error: /indices_dovecot/indices/11/53/ehlers/mailboxes/INBOX/dovecot.index reset, view is now inconsistent Dec 15 13:16:32 buzon dovecot: imap(ehlers): Disconnected: IMAP session state is inconsistent, please relogin. bytes=195/963 Dec 15 13:16:32 buzon dovecot: imap-login: Login: user=<ehlers>, method=PLAIN, rip=192.168.1.150, lip=192.168.4.80, mpid=2006 Dec 15 13:16:32 buzon dovecot: imap(ehlers): Connection closed bytes=274/80860 Dec 15 13:16:49 buzon dovecot: imap-login: Login: user=<ehlers>, method=PLAIN, rip=192.168.1.150, lip=192.168.4.80, mpid=2735 Any idea? Regards Maria On Wed, 2011-12-14 at 22:10 +0100, Maria Arrea wrote: > I have seen some strange error log messages in our dovecot server (2.0.15, RHEL 5.7x64, mdbox+zlib, local storage, high load) > > Dec 14 22:01:27 buzon dovecot: imap(fmcarrasco): Error: /indices_dovecot/indices/07/47/fmcarrasco/mailboxes/INBOX/dovecot.index reset, view is now inconsistent > Dec 14 22:00:27 buzon dovecot: imap(cfp): Error: /indices_dovecot/indices/16/58/cfp/mailboxes/Sent/dovecot.index reset, view is now inconsistent These messages shouldn't appear alone. Is there anything else logged about them? > Dec 14 20:56:46 buzon dovecot: imap(rcam): Error: Corrupted index cache file /indices_dovecot/indices/03/6b/rcam/mailboxes/INBOX/dovecot.index.cache: Broken virtual size for mail UID 132197 Possibly related to zlib.. Again it should have logged another error message just before this. > Dec 14 21:50:38 buzon dovecot: imap(cfp): Error: Recent flags state corrupted for mailbox INBOX Possibly related to other errors. So .. none of the errors above really were what I'd call the actual cause of the problems. They were just after effects. > I have been googling without luck, why does this happen? I have tried with doveadm force-resync, maybe this could solve this issues. All of those should be fixed automatically. Do they keep happening if you don't do force-resync? How often do they happen anyway? Do they happen at any specific times (e.g. during doveadm purge)?

2 1