- dovecot - dovecot.org

Expunge messages older than
by absolutely_free＠libero.it 09 Mar '15

09 Mar '15

Hi, I am using Dovecot 2.2.13 on cPanel server. Is there a way to delete messages older than some date for a number of users (in every subfolder)? Thank you

3 2

Re: Outlook 2013/2010 nightmare
by Joseph Tam 09 Mar '15

09 Mar '15

"David.M.Clark" <david(a)davrom.com> writes: > I do have some customers using Outlook or Windows Live Mail, and these > are for the most part working fine with IMAP - I don't do POP. > ... > The issue starts when you add an IMAP user to the Outlook client and > upon opening it, initially, it tries to find a "Sent" Items folder under > IMAP to send from. To this end I have traditionally gone into the > dialogue box that opens, click on the IMAP account to receive a list of > possible folders, but it now immediately crashes indicating Outlook has > had an error, and it all goes to hell from there. Outlook then cannot > open but keeps crashing with its "unknown error". > Up to last week at another site with Windows Live Mail, this was not an > issue. Just a shot in the dark, but have you enabled the workarounds? http://wiki2.dovecot.org/Clients Some clients like, like Outlook, have known problems which dovecot can dance around. in 20-imap.conf # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example OSX # Mail (<v2.1). Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # tb-extra-mailbox-sep: # Thunderbird gets somehow confused with LAYOUT=fs (mbox and dbox) and # adds extra '/' suffixes to mailbox names. This option causes Dovecot to # ignore the extra '/' instead of treating it as invalid mailbox name. # tb-lsub-flags: # Show \Noselect flags for LSUB replies with LAYOUT=fs (e.g. mbox). # This makes Thunderbird realize they aren't selectable and show them # greyed out, instead of only later giving "not selectable" popup error. # # The list is space-separated. imap_client_workarounds = delay-newmail Joseph Tam <jtam.home(a)gmail.com>

1 0

dovecot auth-worker error happens when I enabled the dovecot to consider both the system account and the MySQL virtual mailbox databases.
by Emmanuel Chanel 09 Mar '15

09 Mar '15

Version: 2.2.9 & 2.2.15 ( http://ppa.launchpad.net/malte.swart/dovecot-2.2/ubuntu ) OS: Ubuntu 14.04 Server LTS I installed Ubuntu 14.04.2 LTS newly on my new server... And I try to configure the mail server considering both my system account and the virtual mailboxes, by seeing https://www.exratione.com/2014/05/a-mailserver-on-ubuntu-1404-postfix-dovec… But when I configured by uncommenting #!include auth-sql.conf.ext , it doesn't auth... Possibly, it's a trouble with the configurations of postfix and of dovecot. But I don't understand why... When I enable either auth-system.conf.ext or auth-sql.conf.ext , it works... My doveconf -n http://pastebin.com/MU1LL63d dovecot-sql.conf.ext http://pastebin.com/PJkTnPB3 tail /var/log/mail.log by debug mode / dovecot 2.2.15 http://pastebin.com/1TRQL49d Mar 6 07:45:12 gateway dovecot: auth: Debug: client in: AUTH#0114#011PLAIN#011service=imap#011secured#011session=xS6uSpIQvQDAqAAC#011lip=192.168.0.1#011rip=192.168.0.2#011lport=143#011rport=38333 Mar 6 07:45:12 gateway dovecot: auth: Debug: client passdb out: CONT#0114#011 Mar 6 07:45:12 gateway dovecot: auth: Debug: client in: CONT<hidden> Mar 6 07:45:12 gateway dovecot: auth-worker(22933): Debug: pam(emmanuel,192.168.0.2): lookup service=dovecot Mar 6 07:45:12 gateway dovecot: auth: Error: auth worker: Aborted PASSV request for emmanuel: Worker process died unexpectedly Mar 6 07:45:12 gateway dovecot: auth-worker(22936): Debug: sql(emmanuel,192.168.0.2): query: SELECT username as user, password, '/home/vmail//emmanuel' as userdb_home, 'maildir:/home/vmail//emmanuel' as userdb_mail, 65000 as userdb_uid, 8 as userdb_gid FROM mailbox WHERE username = 'emmanuel' AND active = '1' Mar 6 07:45:12 gateway dovecot: auth-worker(22933): Fatal: master: service(auth-worker): child 22933 killed with signal 11 (core dumped) Mar 6 07:45:12 gateway dovecot: auth-worker(22936): sql(emmanuel,192.168.0.2): unknown user Mar 6 07:45:12 gateway dovecot: auth-worker(23755): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Mar 6 07:45:12 gateway dovecot: auth-worker(23755): Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Mar 6 07:45:14 gateway dovecot: auth: Debug: client passdb out: FAIL#0114#011user=emmanuel#011temp Mar 6 07:45:14 gateway dovecot: auth: Debug: client in: AUTH#0115#011LOGIN#011service=imap#011secured#011session=xS6uSpIQvQDAqAAC#011lip=192.168.0.1#011rip=192.168.0.2#011lport=143#011rport=38333 Mar 6 07:45:14 gateway dovecot: auth: Debug: client passdb out: CONT#0115#011VXNlcm5hbWU6 Mar 6 07:45:14 gateway dovecot: auth: Debug: client in: CONT<hidden> Mar 6 07:45:14 gateway dovecot: auth: Debug: client passdb out: CONT#0115#011UGFzc3dvcmQ6 Mar 6 07:45:14 gateway dovecot: auth: Debug: client in: CONT<hidden> Mar 6 07:45:14 gateway dovecot: auth-worker(22936): Debug: pam(emmanuel,192.168.0.2): lookup service=dovecot Mar 6 07:45:14 gateway dovecot: auth: Error: auth worker: Aborted PASSV request for emmanuel: Worker process died unexpectedly Mar 6 07:45:14 gateway dovecot: auth-worker(23755): Debug: sql(emmanuel,192.168.0.2): query: SELECT username as user, password, '/home/vmail//emmanuel' as userdb_home, 'maildir:/home/vmail//emmanuel' as userdb_mail, 65000 as userdb_uid, 8 as userdb_gid FROM mailbox WHERE username = 'emmanuel' AND active = '1' Mar 6 07:45:14 gateway dovecot: auth-worker(22936): Fatal: master: service(auth-worker): child 22936 killed with signal 11 (core dumped) Mar 6 07:45:14 gateway dovecot: auth-worker(23755): sql(emmanuel,192.168.0.2): unknown user Mar 6 07:45:14 gateway dovecot: auth-worker(23764): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Mar 6 07:45:14 gateway dovecot: auth-worker(23764): Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Mar 6 07:45:16 gateway dovecot: auth: Debug: client passdb out: FAIL#0115#011user=emmanuel#011temp Mar 6 07:45:16 gateway dovecot: auth: Debug: client in: AUTH#0116#011PLAIN#011service=imap#011secured#011session=xS6uSpIQvQDAqAAC#011lip=192.168.0.1#011rip=192.168.0.2#011lport=143#011rport=38333#011resp=<hidden> Mar 6 07:45:16 gateway dovecot: auth-worker(23755): Debug: pam(emmanuel,192.168.0.2): lookup service=dovecot Mar 6 07:45:16 gateway dovecot: auth: Error: auth worker: Aborted PASSV request for emmanuel: Worker process died unexpectedly Mar 6 07:45:16 gateway dovecot: auth-worker(23764): Debug: sql(emmanuel,192.168.0.2): query: SELECT username as user, password, '/home/vmail//emmanuel' as userdb_home, 'maildir:/home/vmail//emmanuel' as userdb_mail, 65000 as userdb_uid, 8 as userdb_gid FROM mailbox WHERE username = 'emmanuel' AND active = '1' Mar 6 07:45:16 gateway dovecot: auth-worker(23755): Fatal: master: service(auth-worker): child 23755 killed with signal 11 (core dumped) Mar 6 07:45:16 gateway dovecot: auth-worker(23764): sql(emmanuel,192.168.0.2): unknown user Mar 6 07:45:16 gateway dovecot: auth-worker(23767): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Mar 6 07:45:16 gateway dovecot: auth-worker(23767): Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Mar 6 07:45:18 gateway dovecot: auth: Debug: client passdb out: FAIL#0116#011user=emmanuel#011temp -- Emmanuel Chanel( emmanuelchanel(a)gmail.com )

1 3

Sieve can't find Extprograms or Extdata
by E.B. 09 Mar '15

09 Mar '15

Hi, On a new install-from-source with Dovecot 2.2.16rc1, Piegeonhole 0.4.6 and a grab of the newest Extdata code, I confirmed basic Sieve functionality is working (made a simple sieve script with a test on message subject resulting in a fileinto action). But I cannot get Sieve to see Extdata or Extprograms. sievec reports "Warning: sieve: ignored unknown extension 'vnd.dovecot.filter' while configuring available extensions" and the same for vnd.dovecot.extdata. And of course for the user script, "error: require command: unknown Sieve capability `vnd.dovecot.filter'" (same with extdata) I'm pretty sure this is a library path problem, but I've tried symlinking and restarting dovecot with as many iterations of library paths as I can think of but still same problem. The lib90_sieve_extdata_plugin.so and lib90_sieve_extprograms_plugin.so are in /usr/local/lib/dovecot/sieve and all the rest of the normal dovecot libraries are one level above in /usr/local/lib/dovecot. I tried creating symlinks for a "modules" directory and a "modules/sieve" directory, I tried symlinking these two librarie files themselves into the top level dovecot library directory, and a few other ideas, but no luck. Is there a way I can tell where Sieve expects its libraries to reside? To see where it is looking? I didn't provide any arguments to the configure command for pigeonhole as well as extdata and it seems like the libs got placed somewhere sensible, but I don't know what else to do.

2 3

[PATCH] Fix dovecot 1.2 build with LibreSSL
by Bernard Spil 07 Mar '15

07 Mar '15

Hi All, mail/dovecot build fails when linked against LibreSSL. This is due to LibreSSL no longer including comp.h from ssl.h/ssl3.h. See https://wiki.freebsd.org/LibreSSL as well. This patch fixes the build failure. Build log attached as well (not any more, too large! Get it via link just above). Please commit this fix to the 1.2 branch (2.1 branch is not affected) Kind regards, Bernard Spil.

1 0

Identify mail for attachment hash
by Daniel Miller 07 Mar '15

07 Mar '15

How can I find the message associated with a given attachment hash? For example, if I know that: /ff/23/ff23873c712474ad0f48cbd81485eaeaba3d8468-e1b4513a2eb8eb53b16400009db5accb is missing, I want to find the message associated with it so I can determine if it's critical and I need to recover it from another source, or if I can simply delete the old message. -- Daniel

1 0

Sieve editheader should support adding Received and Auto-Submitted headers
by Lee Maguire 07 Mar '15

07 Mar '15

In order to simplify auto-response suppression and other filtering, I want to synthesise an Auto-Submitted header on notification mails that should have them but do not. In a sieve file I add the following: if anyof ( header :contains ["From","Sender"] “info(a)example.com" ) { if header :contains "Subject" [" just joined "," just left "] { if not exists "Auto-Submitted" { addheader "Auto-Submitted" "auto-generated (via sieve)"; } } However this doesn’t work and results in the following error > main script: line 205: warning: addheader action: specified header field `Auto-Submitted' is protected; modification denied. (Workaround for this specific issue would probably be to use a List-* header instead.) Looking at http://hg.rename-it.nl/dovecot-2.2-pigeonhole/file/c8edece267cd/src/lib-sie… I can see that "Auto-Submitted” and “Received” are hardcoded to be blocked without reference to whether they are to be added or removed. However, the hard restriction in RFC 5293 on Auto-Submitted and Received only applies to the use of deleteheader and not addheader. https://tools.ietf.org/html/rfc5293#section-6 > As a matter of local policy, implementations MAY limit which header > fields may be deleted and which header fields may be added. However, > implementations MUST NOT permit attempts to delete "Received" and > "Auto-Submitted" header fields and MUST permit both addition and > deletion of the "Subject" header field. Using Dovecot version 2.1.7 but I assume it’s not version specific issue.

2 1

LMTP error: Too many concurrent deliveries for user (in reply to end of DATA command)
by Ralf Hildebrandt 06 Mar '15

06 Mar '15

I updated dovecot today and all over a sudden I'm getting: Mar 6 14:40:46 mail postfix/lmtp[3150]: 3kz95y3nX3zCtTS: to=<recipient(a)backup.invalid>, relay=127.0.0.1[private/dovecot-lmtp], delay=88, delays=87/0.94/0.01/0.01, dsn=4.3.0, status=deferred (host 127.0.0.1[private/dovecot-lmtp] said: 451 4.3.0 <recipient(a)backup.invalid> Too many concurrent deliveries for user (in reply to end of DATA command)) Why is that? Which setting must I tweak? -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

3 6

IP drop list
by Jim Pazarena 06 Mar '15

06 Mar '15

I wonder if there is an easy way to provide dovecot a flat text file of ipv4 #'s which should be ignored or dropped? I have accumulated 45,000+ IPs which routinely try dictionary and 12345678 password attempts. The file is too big to create firewall drops, and I don't want to compile with wrappers *if* dovecot has an easy ability to do this. If dovecot could parse a flat text file of IPs and drop connections it would sure put a dent in these attempts. Thanks.

15 28

Fwd: Re: IP drop list
by Jim Pazarena 06 Mar '15

06 Mar '15

On 2015-03-02 2:02 AM, Jochen Bern wrote: > On 03/01/2015 08:53 AM, Jim Pazarena wrote: >> I wonder if there is an easy way to provide dovecot a flat text file of >> ipv4 #'s which should be ignored or dropped? >> >> I have accumulated 45,000+ IPs which routinely try dictionary and >> 12345678 password attempts. The file is too big to create firewall >> drops [...] > > The inherent assumption here is that dovecot, using a "flat file", will > be able to process the block list more effectively than the firewall, > which is a tool written for the *purpose* but supposedly unable to even > *try* due to the list's size. That sounds ... counterintuitive. I am the original poster and just came back to this thread. When the first couple replies were "fail2ban" I lost interest. The reason I contemplated a flat text scan by dovecot is because, for the most part, my dovecot is low volume. So even if parsing a flat text file is less 'efficient' than a firewall insertion, it WOULD serve to defeat dictionary attacks rather readily. I already have a routine which scans my dovecot logs for goofy attacks such as dictionary or 12345 attempts. And since the attacks are pop/IMAP only, that is the only avenue which I wanted to defeat. This question garnered lots and lots of responses and I appreciate them all and read them all. And out of all the responses I think I will pursue the ipset routine. It seems easy enough and can act at the firewall level. The DNS RBL would be cool. I am also cognizant that 45,000 SHOULD have a TTL. However, these were IPs attempting to fetch email with obviously hacker type passwords. If, later, a given IP is re-assigned to a 'legitimate' person, they would still be able to send an email to me ' postmaster@ ' asking about an inability to fetch email. But parsing the flat text file would STILL be my preference. I'll look at the source and see if I can figure out where to inject such code. Like I said, my dovecot is low volume, so a fraction of a second at connection time is low impact. Considering that the flat text file may hang around in the memory cache it could even be less impact than low.

4 3