August 2014 - dovecot

[Dovecot] Replication and public namespaces
by Markus Weippert 11 Apr '16

11 Apr '16

Hi, I'm having some issues with replicating public namespaces. Everything seems to work fine for private namespaces, but while importing some huge mailboxes (many small mails) into a public namespace via imapsync, something goes wrong. The expected mail flow is: old-server (imapsync)> new-server1 (replication)> new-server2 But then, dovecot seems to run into race conditions when the replications process tries to sync the same public mailbox under two or more different users at the same time. As a result, messages get duplicated, new-server2 sends those back to new-server1 which then starts to produce duplicates too. If I don't kill the processes in time and delete the faulty mailbox, they start to produce thousands of mails. In fact, server2 should not export messages at all, since it's not productive yet and does not get any mail except from the replication. The only thing getting logged (only few compared to the huge amount of duplicates produced): "dsync-server(user(a)example.com): Warning: Maildir /...: Expunged message reappeared, giving a new UID" Is there any way to fix this? Regards, Markus doveadm_password = *********** doveadm_port = ***** mail_home = /var/vmail/private/%d/%n mail_location = maildir:~/mail mail_plugins = acl virtual listescape notify replication namespace inbox { inbox = yes location = prefix = separator = / type = private } namespace legacy { alias_for = # ... } namespace ns_public { list = children location = maildir:/var/vmail/public/%d prefix = Public/ separator = / subscriptions = no type = public } namespace virtual { # ... } plugin { mail_replica = tcps:************** } protocols = imap lmtp sieve replication_dsync_parameters = -d -l 60 -N -x virtual -x ns_public -U replication_full_sync_interval = 4 hours replication_max_conns = 20 service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service doveadm { inet_listener { port = 8143 ssl = yes } process_min_avail = 5 user = vmail vsz_limit = 4 G } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } }

3 7

doveadm-server does NOT know fts commands
by SATOH Fumiyasu 16 Dec '15

16 Dec '15

Hi, I'm using Dovecot 2.2.13 with Dovecot Director, Doveadm server and FTS. I want to run doveadm on Director hosts, but Dovecot server on backend hosts reject "fts *" commands. On Dovecot Director hosts: # doveadm fts optimize -u u0001(a)example.jp # echo $? 75 # doveadm fts rescan -u u0001(a)example.jp # echo $? 75 doveadm index -u u0001(a)example.jp INBOX # echo $? 0 On Dovecot backend hosts: # grep doveadm /var/log/maillog Jul 14 10:25:40 backend dovecot: doveadm: Error: doveadm: Client sent unknown command: fts optimize Jul 14 10:25:51 backend dovecot: doveadm: Error: doveadm: Client sent unknown command: fts rescan Is this doveadm-server restriction? On Dovecot backend hosts (2): # doveadm fts optimize -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server # echo $? 75 # doveadm fts rescan -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server # echo $? 75 # doveadm index -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server INBOX # echo $? 0 # doveadm fts optimize -u u0001(a)example.jp # echo $? 0 # doveadm fts rescan -u u0001(a)example.jp # echo $? 0 # doveadm index -u u0001(a)example.jp INBOX # echo $? 0 -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

2 3

[Dovecot] lmtp_rcpt_check_quota not working
by Bernhard Schmidt 06 Dec '15

06 Dec '15

Hi, Dovecot 2.2.9 (Debian package from backports) does not seem to respect lmtp_rcpt_check_quota # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 deliver_log_format = from=<%e>, size=%p, message-id=<%m>, status=%$ disable_plaintext_auth = no lmtp_rcpt_check_quota = yes mail_debug = yes mail_gid = mstore mail_location = maildir:~/Maildir:INDEX=/var/cache/dovecot/index/%-1.1u/%u mail_plugins = quota mail_uid = mstore managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { quota = maildir quota_rule = ?:storage=512M quota_rule2 = INBOX.Trash:ignore quota_status_nouser = DUNNO quota_status_overquota = 452 4.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=85%% quota-warning 85 %u sieve = ~/currently-active-script.sieve sieve_dir = ~/sieve } pop3_uidl_format = %08Xv%08Xu protocols = imap lmtp sieve pop3 quota_full_tempfail = yes service anvil { client_limit = 3000 unix_listener anvil { group = sudo mode = 0660 } } service auth { client_limit = 3000 unix_listener auth-userdb { group = mstore mode = 0660 user = mstore } } service imap-login { client_limit = 1024 inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 2500 process_min_avail = 4 service_count = 0 } service lmtp { inet_listener lmtp { address = xxx port = 24 } } service managesieve-login { inet_listener sieve { port = 2000 } service_count = 1 } service managesieve { process_limit = 1024 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service quota-status { client_limit = 5 executable = quota-status -p postfix inet_listener { address = xxx port = 12340 } } service quota-warning { executable = script /etc/dovecot/quotawarnmsg.sh unix_listener quota-warning { user = mstore } user = mstore } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } verbose_proctitle = yes protocol imap { mail_plugins = quota imap_quota imap_zlib } protocol lda { mail_plugins = quota sieve } protocol lmtp { mail_plugins = quota sieve } so Dovecot should reject in RCPT TO phase, but according to the logs of the upstream Postfix it does so after END-OF-DATA (host xxx[2001:xxx] said: 452 4.2.2 <user(a)domain.de> Quota exceeded (mailbox for user is full) (in reply to end of DATA command)) I haven't seen any commits regarding to this in 2.2.10 or tip. Regards, Bernhard

3 6

[Dovecot] Pigeonhole sieve re-filter extension?
by T.B. 22 Sep '15

22 Sep '15

Dear Stephan Bosch, dear Dovecot community, "sieve-filter" re-filtering of existing mails is already a great progress for everyone using sieve! But as far as I know this functionality is just accessible by the server administrator. In the meanwhile everyone knows the comfort of re-executing filter scripts on his own existing mailboxes - triggered by himself! This service is already very widespread. Examples are MUA's like Outlook or Thunderbird which provide this service just on the client side. Or almost every web-mail provider offers this. Is there already an managesieve protocol extension that allows client triggered server side re-filtering? If not, maybe you could design a RFC for this? What do you think? Best regards. T.B.

4 8

[Dovecot] dsync replication errors
by Oli Schacher 09 Sep '15

09 Sep '15

Hi I'm trying to build a cluster of two servers with dsync replication (based on http://wiki2.dovecot.org/Replication) My test setup works fine for very simple tests, I can log in to both servers, copy a message to one of the servers and it successfully apperars in the other account. But, if I try to copy a large amount of messages at once to one of the accounts, my maillogs get flodded with errors(see below) and the mailboxes seem to get out of sync and messages are duplicated over and over again (I originally copied 100 messages and ended up with thousands in both mailboxes until I killed dovecot) I'd appreciate if someone could have a look at my config and tell me what I did wrong. dovecot.conf of both servers, they are identical except for the target ip in mail_replica: dovecot -n # 2.2.beta1 (070ca24e5846+): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.19.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) disable_plaintext_auth = no mail_plugins = " notify replication" namespace { inbox = yes location = prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { mail_replica = remote:vmail@192.168.23.62 } protocols = pop3 imap service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener auth-master { group = vmail mode = 0660 user = vmail } user = root } service replicator { process_min_avail = 1 } ssl = no userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } Log on server1 after I copied 100 messages to an account on that server: Jan 31 10:41:04 doco1 dovecot: imap-login: Login: user=<user1>, method=PLAIN, rip=192.168.23.130, lip=192.168.23.61, mpid=1432, session=<OdjlbJLUmwDAqBeC> Jan 31 10:42:12 doco1 dovecot: doveadm: Error: dsync-remote(user1): Warning: Maildir /mailstore/user1/maildir: Expunged message reappeared, giving a new UID (old uid=72, file=1359625327.M621257P1432.doco1,S=2472,W=2547:2,) Jan 31 10:42:12 doco1 dovecot: dsync-local(user1): Error: Recent flags state corrupted for mailbox INBOX Jan 31 10:42:12 doco1 dovecot: doveadm: Error: dsync-remote(user1): Warning: Maildir /mailstore/user1/maildir: Expunged message reappeared, giving a new UID (old uid=73, file=1359625327.M740847P1432.doco1,S=2417,W=2492:2,) Jan 31 10:42:12 doco1 dovecot: doveadm: Error: dsync-remote(user1): Warning: Maildir /mailstore/user1/maildir: Expunged message reappeared, giving a new UID (old uid=74, file=1359625328.M206735P1432.doco1,S=2400,W=2474:2,) Jan 31 10:42:12 doco1 dovecot: doveadm: Error: dsync-remote(user1): Warning: Maildir /mailstore/user1/maildir: Expunged message reappeared, giving a new UID (old uid=75, file=1359625328.M668118P1432.doco1,S=2421,W=2496:2,) Jan 31 10:42:12 doco1 dovecot: doveadm: Error: dsync-remote(user1): Warning: Maildir /mailstore/user1/maildir: Expunged message reappeared, giving a new UID (old uid=76, file=1359625329.M167578P1432.doco1,S=2480,W=2559:2,) Jan 31 10:42:13 doco1 dovecot: doveadm: Error: dsync-remote(user1): Warning: Maildir /mailstore/user1/maildir: Expunged message reappeared, giving a new UID (old uid=77, file=1359625329.M520528P1432.doco1,S=2525,W=2604:2,) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 132: 1359625329.M520528P1432.doco1,S=2525,W=2604 (uid 77 -> 133) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 133: 1359625327.M621257P1432.doco1,S=2472,W=2547 (uid 72 -> 134) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 134: 1359625327.M740847P1432.doco1,S=2417,W=2492 (uid 73 -> 135) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 135: 1359625328.M206735P1432.doco1,S=2400,W=2474 (uid 74 -> 136) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 136: 1359625328.M668118P1432.doco1,S=2421,W=2496 (uid 75 -> 137) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 137: 1359625329.M167578P1432.doco1,S=2480,W=2559 (uid 76 -> 138) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 139: 1359625329.M782065P1432.doco1,S=2461,W=2539 (uid 78 -> 140) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 140: 1359625329.M973834P1432.doco1,S=2523,W=2602 (uid 79 -> 141) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 141: 1359625330.M114922P1432.doco1,S=2546,W=2626 (uid 80 -> 142) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 142: 1359625330.M255922P1432.doco1,S=2467,W=2546 (uid 81 -> 143) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 143: 1359625330.M403257P1432.doco1,S=2534,W=2611 (uid 82 -> 144) Jan 31 10:42:14 doco1 dovecot: doveadm(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 144: 1359625330.M486295P1432.doco1,S=2451,W=2529 (uid 83 -> 145) Jan 31 10:42:14 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Unexpected GUID mismatch for UID=85: 1359625327.M740847P1432.doco1,S=2417,W=2492 != 2e1b1ee97994566870c02910ea929091 Jan 31 10:42:15 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625329.M167578P1432.doco1,S=2480,W=2559 (UID=175) Jan 31 10:42:15 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625329.M167578P1432.doco1,S=2480,W=2559 (UID=150) Jan 31 10:42:15 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625329.M520528P1432.doco1,S=2525,W=2604 (UID=176) Jan 31 10:42:15 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625329.M520528P1432.doco1,S=2525,W=2604 (UID=179) Jan 31 10:42:15 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625327.M740847P1432.doco1,S=2417,W=2492 (UID=123) Jan 31 10:42:15 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625327.M740847P1432.doco1,S=2417,W=2492 (UID=147) Jan 31 10:42:15 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625328.M668118P1432.doco1,S=2421,W=2496 (UID=174) Jan 31 10:42:15 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625328.M668118P1432.doco1,S=2421,W=2496 (UID=149) Jan 31 10:42:15 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625328.M206735P1432.doco1,S=2400,W=2474 (UID=173) Jan 31 10:42:15 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625328.M206735P1432.doco1,S=2400,W=2474 (UID=148) Jan 31 10:42:16 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Importing mailbox INBOX failed Jan 31 10:42:16 doco1 dovecot: dsync-local(user1): Error: read(vmail(a)192.168.23.62) failed: EOF Jan 31 10:42:16 doco1 dovecot: dsync-local(user1): Error: Remote command returned error 75 Jan 31 10:42:20 doco1 dovecot: doveadm: Error: dsync-remote(user1): Error: Mailbox INBOX: Remote didn't send mail GUID=1359625329.M167578P1432.doco1,S=2480,W=2559 (UID=230) [...] Log on server2: Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 132: 1359625329.M520528P1432.doco1,S=2525,W=2604 (uid 77 -> 133) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 133: 1359625327.M621257P1432.doco1,S=2472,W=2547 (uid 72 -> 134) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 134: 1359625327.M740847P1432.doco1,S=2417,W=2492 (uid 73 -> 135) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 135: 1359625328.M206735P1432.doco1,S=2400,W=2474 (uid 74 -> 136) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 136: 1359625328.M668118P1432.doco1,S=2421,W=2496 (uid 75 -> 137) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 137: 1359625329.M167578P1432.doco1,S=2480,W=2559 (uid 76 -> 138) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 139: 1359625329.M782065P1432.doco1,S=2461,W=2539 (uid 78 -> 140) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 140: 1359625329.M973834P1432.doco1,S=2523,W=2602 (uid 79 -> 141) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 141: 1359625330.M114922P1432.doco1,S=2546,W=2626 (uid 80 -> 142) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 142: 1359625330.M255922P1432.doco1,S=2467,W=2546 (uid 81 -> 143) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 143: 1359625330.M403257P1432.doco1,S=2534,W=2611 (uid 82 -> 144) Jan 31 10:42:14 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: /mailstore/user1/maildir/dovecot-uidlist: Duplicate file entry at line 144: 1359625330.M486295P1432.doco1,S=2451,W=2529 (uid 83 -> 145) Jan 31 10:42:15 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: Maildir /mailstore/user1/maildir: Expunged message reappeared, giving a new UID (old uid=84, file=1359625330.M608391P1432.doco1,S=2480,W=2559:2,) Jan 31 10:42:15 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: Maildir /mailstore/user1/maildir: Expunged message reappeared, giving a new UID (old uid=85, file=1359625330.M813949P1432.doco1,S=2427,W=2502:2,) Jan 31 10:42:15 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: Maildir /mailstore/user1/maildir: Expunged message reappeared, giving a new UID (old uid=86, file=1359625331.M217320P1432.doco1,S=2547,W=2625:2,) Jan 31 10:42:15 doco2 dovecot: doveadm: Error: dsync-remote(user1): Warning: Maildir /mailstore/user1/maildir: Expunged message reappeared, giving a new UID (old uid=87, file=1359625331.M688431P1432.doco1,S=2529,W=2609:2,) [...] Thanks Oli -- message transmitted on 100% recycled electrons

7 45

[Dovecot] Dovecot FTS using ElasticSearch
by Darvin Denmian 21 Jul '15

21 Jul '15

Hi, I would like to know if is possible to use ElasticSearch instead of Solr for FTS. Regards, Erick Vitor de Barros.

6 6

[Dovecot] imapc - different settings for different namespaces
by Timo Sirainen 20 Mar '15

20 Mar '15

Originally I was planning on allowing all kinds of mail settings inside namespace {}, including imapc_* settings. But that's a bit difficult to implement (although I think it will happen some day). So for now I was thinking: imapc foo { host = imap.foo.com master_user = foomaster password = foopass } imapc bar { host = imap.bar.com ... } namespace { prefix = foo/ location = imapc:foo } namespace { prefix = bar/ location = imapc:bar } So basically if the path after imapc isn't absolute (/path or ~/path), then treat the path as the imapc section name and use its settings. Anyone have any improvement suggestions? I was planning on adding this to v2.2.3. I'm not sure if the section names should be "imapc" or something else (e.g. imap_remote {}).

2 2

[Dovecot] Sieve vacation not working
by Phill Edwards 24 Feb '15

24 Feb '15

I've been trying all night to get vacation working in my .dovecot.sieve file. The way our email works is we have one account on dovecot which serves my mail and my wife's and we use procmail and sieve to put the emails in different folders depending on who it's for. I'm trying to set up a vacation reply on my wife's email address (aaaaaaaa@optus* below) so people can update to her new address. Here's my file with the email addresses masked: require ["fileinto", "vacation"]; if address :is "to" "xxxxxxxxxxxxxxx(a)ozemail.com.au" { fileinto "Phill_OzEmail_Folder"; stop; } elsif address :is "to" "yyyyyyyyyyyyyyyyy(a)optusnet.com.au" { fileinto "Phill_Optus_Folder"; stop; } elsif address :matches "to" "aaaaaaaa@optus*" { vacation "Please update my email address to bbbbbbbbb(a)exemail.com.au"; fileinto "Sarah_Optus_Folder"; stop; } else { keep; stop; } The problem I'm having is that no auto-replies are sent. I removed .dovecot.lda-dupes and that didn't help; so then I touched it and now it's a 0 byte file and that didn't help. There is no dovecot.sieve.err file and I can't see anything in /var/log/dovecot.log which gives any message about why this wouldn't work. The emails to aaaaaaa@optus* get filed into the right folder so I know the matching is working. I've also tried a reject recipe and that worked fine, so I know that it can send an email if it chooses to. So it's a complete black box mystery as to why it just won't send a reply. Regards, Phill

5 9

[Dovecot] Disk Encryption
by Simon Brereton 17 Oct '14

17 Oct '14

Hi As I understand it email headers need to be unencrypted (otherwise DKIM doesn't work). From the MUA to either Postfix, or Dovecot the connection is (or can/should be) secured with TLS/SSL. What I would like to know is if it is possible to encrypt the mailstore? Postfix is using Dovecot for delivery so it's only Dovecot that would need to encrypt/decrypt the mailstore. Is this possible? Is there a terrible reason to do it even if it is possible? I realise that from MTA to MTA there's no guarantee of encryption (and in fact it's very unlikely unless keys have been exchanged), but my primary goal is supplement the physical security of the mail store of mails we already have or have sent. Mostly just idle curiosity as to what has been done, or what could be done. What is worth doing is a separate thread entirely. Thanks. Simon

11 28

Sieve filter extracting wrong header value on certain mail messages
by gowen (dovecot) 09 Oct '14

09 Oct '14

# 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.15.4-x86_64-linode45 x86_64 openSUSE 12.3 (x86_64) Short version: 1) I filter out spam by using a dovecot sieve filter to act based on a header inserted by bogofilter 2) In some cases, sieve fails to correctly file based on this header 3) Testing with sieve-test indicates that it's testing the wrong header 4) Suggestions? Am I doing something wrong? Is there a problem with these headers that bends test-sieve out of shape? 5) Test files from below are also available via http://www.swynwyr.com/sieve-test/ Any help is appreciated!!! Long version with full details: Here is the simple sieve filter I'm using to test, and two different variants of an email which triggers this problem. I basically deleted things one by one from an original email (1) to get minimal testcases that triggered (2) or did not trigger (3) the problem. The filter: === begin test.sieve === require ["fileinto", "body", "regex"]; if header :contains "X-Bogosity" "Spam," { fileinto "SPAM.SPAM"; stop; } elsif header :contains "X-Bogosity" "Unsure," { fileinto "SPAM.UNSURE"; stop; } keep; stop; === end test.sieve === Here is an example email that will cause this filter to not function as expected: === begin message.2 === Return-Path: <alora(a)promosforusio.org> Subject: =?utf-8?B?QUhTIEtpdGNoZW4gTWFrZW92ZXIgR2l2ZWF3YXkg?= Subject: ÎHS KitÑhen ÎakÐµovÐµr GivÐµaway Subject: =?ISO-8859-1?Q?AHS Kitchen Makeover Giveaway =A0=A0=A0?= Subject: Subject: AHS Kitchen Makeover Giveaway X-Bogosity: Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3 Home Warranty Summer Giveaway === end message.2 === If I run test-sieve on this, we can clearly see in the trace log that when it's supposed to test for header "X-Bogosity" it in fact looks at one of the multiple "Subject" headers. Note that the result is storing in INBOX rather than SPAM.SPAM, and that the "matching value" for "X-Bogosity headers" is actually the contents of the final "Subject" header in the test on line 3. In the second test, on line 6, it uses a different and correct value for the same header! But too late to help as the first test was the one it should have had a match on. === begin session === $ sieve-test -t trace2.log -Tlevel=matching test.sieve message.2 Performed actions: * store message in folder: INBOX Implicit keep: (none) sieve-test(gowen): Info: final result: success $ cat trace2.log ## Started executing script 'test' 3: header test 3: starting `:contains' match with `i;ascii-casemap' comparator: 3: extracting `X-Bogosity' headers from message 3: matching value `AHS Kitchen Makeover Giveaway' 3: with key `Spam,' => 0 3: finishing match with result: not matched 3: jump if result is false 3: jumping to line 6 6: header test 6: starting `:contains' match with `i;ascii-casemap' comparator: 6: extracting `X-Bogosity' headers from message 6: matching value `Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3' 6: with key `Unsure,' => 0 6: finishing match with result: not matched 6: jump if result is false 6: jumping to line 11 11: keep action; store message in default mailbox 12: stop command; end all script execution ## Finished executing script 'test' $ === end session === Now lets remove the "Return-Path" from that message. (Of the original 26 headers, all but the 7 shown in message.2 could be removed and still have this message break the filter). This alters thing enough that sieve starts working as expected (in fact, removing any one of the 6 non-X-Bogosity headers will cause this to start working). === begin message.3 === Subject: =?utf-8?B?QUhTIEtpdGNoZW4gTWFrZW92ZXIgR2l2ZWF3YXkg?= Subject: ÎHS KitÑhen ÎakÐµovÐµr GivÐµaway Subject: =?ISO-8859-1?Q?AHS Kitchen Makeover Giveaway =A0=A0=A0?= Subject: Subject: AHS Kitchen Makeover Giveaway X-Bogosity: Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3 Home Warranty Summer Giveaway === end message.3 === Now when we run test-sieve it works as expected, filing into SPAM.SPAM and showing the correct matching value for line 3: === begin session === $ sieve-test -t trace3.log -Tlevel=matching test.sieve message.3 Performed actions: * store message in folder: SPAM.SPAM Implicit keep: (none) sieve-test(gowen): Info: final result: success $ cat trace3.log ## Started executing script 'test' 3: header test 3: starting `:contains' match with `i;ascii-casemap' comparator: 3: extracting `X-Bogosity' headers from message 3: matching value `Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3' 3: with key `Spam,' => 1 3: finishing match with result: matched 3: jump if result is false 3: not jumping 4: fileinto action 4: store message in mailbox `SPAM.SPAM' 5: stop command; end all script execution ## Finished executing script 'test' $ === end session ===

3 3