- dovecot - dovecot.org

Re: 2.3.1 Replication is throwing scary errors
by Michael Grimm 07 Jun '18

07 Jun '18

Am 2018-06-07 08:48, schrieb Remko Lodder: > On Thu, Jun 07, 2018 at 08:04:49AM +0200, Michael Grimm wrote: >> Conclusion: After 12 hours of running a patched FBSD port I do get >> those >> error messages but replictaion seems to work now. But, I still have >> the >> feeling that there might something else going wrong. > > I agree with that. Are you using the new pkg that ler@ prepared ? That > includes > the patch and is a 'native' package.. Yes, I am running this new port from ler@. And: Thanks for his very fast modification! Regards, Michael

1 0

Shared mailboxes, index files and 'per-user-seen' flags
by Thomas Robers 07 Jun '18

07 Jun '18

Hello, i have a dovecot server version 2.3.1 under CentOS 6.9 and we're using shared mailboxes with index files shared. With this configuration I can see a lot of error messages like: Jun 6 13:20:31 mail dovecot: Error: imap(userA(a)tutech.de)<4513> <onjjWPdtDuLAqG3R>: /export/home/imap/userA(a)tutech.de/shared /userB(a)tutech.de/folder/dovecot.index.pvt view is inconsistent In 10-mail.conf the location setting is: location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u I thought setting the index files to "not shared" might help to get rid of the errors, so I changed the setting to: location = maildir:%%h/Maildir:INDEX=%h/shared/%%u:INDEXPVT=%h /shared/%%u like it's mentioned in the Dovecot wiki. But that doesn't work as I expected, because the 'per-user-seen' flags do not work correctly anymore, i think. If UserA, who has UserB as shared mailbox, changes the seen flags of UserBs INBOX, UserBs seen flags are also changed. The other way, if UserB changes seen flags in his INBOX they are not changed in the shared view of UserA. Is this the supposed way to work or do i have an error in the configuration? Any help is appreciated. Thanks, Thomas. Here's my currently used configuration: # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) ext4 # Hostname: mail.tutech.de auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 12345 imap_max_line_length = 2 M mail_debug = yes mail_location = maildir:/export/home/imap/%Lu/Maildir mail_plugins = acl zlib mail_log notify mail_prefetch_count = 1 mailbox_idle_check_interval = 10 secs 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 index ihave duplicate mime foreverypart extracttext namespace { hidden = no ignore_on_failure = no inbox = no list = children location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = INBOX/ separator = / type = private } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/export/home/shared-db/shared-mailboxes mail_log_events = append delete undelete expunge copy mailbox_delete mailbox_rename flag_change mail_log_fields = uid box msgid size from flags mail_replica = tcp:mail2.tutech.de sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global = /var/lib/dovecot/sieve/global/ sieve_user_log = ~/.dovecot.sieve.log zlib_save = gz zlib_save_level = 6 } protocols = imap pop3 lmtp sieve sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service config { unix_listener config { user = vmail } } service doveadm { inet_listener { port = 12345 } user = vmail } service imap-login { inet_listener imaps { port = 993 ssl = yes } process_limit = 500 process_min_avail = 20 } service imap { executable = imap } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service pop3 { executable = pop3 } service replicator { unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </etc/pki/dovecot/certs/mail.tutech.de.crt_chain ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL:!EXPORT ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local6 userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lmtp { mail_plugins = acl zlib mail_log notify sieve } protocol imap { mail_max_userip_connections = 100 mail_plugins = acl zlib mail_log notify imap_zlib imap_acl rawlog_dir = /tmp/rawlog/%u }

2 1

Header DATE field not returned when placed after MIME section
by Xavier Guerin 06 Jun '18

06 Jun '18

Hello, I am using Dovecot 2.2.34p0 on OpenBSD 6.3 stable. I am writting an application using the vmime (http://www.vmime.org) library (x-ref issue: https://github.com/kisli/vmime/issues/199) I noticed through testing over my own e-mail server that in some situations the DATE field is not returned upon ENVELOPE or HEADER.FIELDS request. The e-mails at fault happen to have the DATE field at the very end of the header, after the MIME section. Example 1: Delivered-To: Received: Return-Path: Delivered-To: DKIM-Signature: From: To: Message-ID: Subject: MIME-Version: 1.0 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Fri, 01 Jun 2018 17:44:44 -0400 Example 2: Return-Path: Delivered-To: Received: Delivered-To: DKIM-Signature: From: Reply-To: To: Subject: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_338_1573405959.1527768044781" X-Mailer: EMail_2.0 Date: Fri, 01 Jun 2018 17:36:01 -0400 Thanks in advance for the insight,

3 2

offtopic: Solr compatible IMAP client
by Andy Smith 04 Jun '18

04 Jun '18

Hi, not sure if I'm allowed to go this off topic on here, sorry if not! I've just installed Solr FTS for Dovecot and its great, as is Dovecot! ;) It works perfectly for fast searches using Roundcube, but can anyone suggest any Windows and/or Linux mail clients that work well with IMAP searches rather than doing their own searches on local copies of mails? I've had a look at Thunderbird and you can use IMAP search, buy you have to manually select it from an advanced search dialogue and it seems you cannot make this the default behaviour. I also tried OperaMail but it doesn't appear to work at all (only header is searchable without downloading local copies). I'm pretty sure Outlook will only use its own search engine on its local copy of data. thanks a lot, Andy. PS this guide was really helpful for setting up Solr FTS with a recent release of Solr (I'm using 6.5), might be worth including a link somewhere on the Dovecot wiki?: http://mor-pah.net/2016/08/15/dovecot-2-2-with-solr-6-or-5

4 7

Re: SSL error after upgrading to 2.31
by Aki Tuomi 01 Jun '18

01 Jun '18

You forgot to cc the list. ssl_ca is used only for validating client certificates. ---Aki TuomiDovecot oy -------- Original message --------From: Marc Perkel <marc(a)perkel.com> Date: 21/05/2018 18:25 (GMT+02:00) To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Subject: Re: SSL error after upgrading to 2.31 On 05/21/2018 07:54 AM, Aki Tuomi wrote: Does ssl_cert file contain intermediates? No - but the ssl_ca does. --- Aki Tuomi Dovecot oy -------- Original message -------- From: Marc Perkel <marc(a)perkel.com> Date: 21/05/2018 16:32 (GMT+02:00) To: dovecot(a)dovecot.org Subject: SSL error after upgrading to 2.31 After upgrading to 2.31 I'm getting this error. Not sure what I'm doing wrong. No (No signatures could be verified because the chain contains only one certificate and it is not self signed.) ssl = yes ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt local mail.ctyme.com { protocol imap { ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt } protocol pop3 { ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt } } local mail.junkemailfilter.com { protocol imap { ssl_cert = </etc/exim/certs/junkemailfilter.com.crt ssl_key = </etc/exim/certs/junkemailfilter.com.key ssl_ca = </etc/exim/certs/ca.crt } protocol pop3 { ssl_cert = </etc/exim/certs/junkemailfilter.com.crt ssl_key = </etc/exim/certs/junkemailfilter.com.key ssl_ca = </etc/exim/certs/ca.crt } }

3 9

Struggling with sieve, fileinto and variables.
by Barry Pearce 31 May '18

31 May '18

Hi, Im on Manjaro linux fully up to date running dovecot 2.3.1-2 pigeonhole 0.5.1-2 All is running well except I am having problems with fileinto - it refuses to use variables, and mailboxexists is also failing for me. Im just dealing with plus addressing - should be simple but the behaviour Im experiencing isnt right. require ["variables", "envelope", "fileinto", "subaddress", "mailbox"]; if envelope :matches :detail "to" "*" { set :lower "name" "${1}"; } fileinto :create "folder3"; This works, but changing the last line to: fileinto :create "${name}"; fails and files into inbox. As does: fileinto :create "${1}"; It makes no difference if the fileinto is placed inside the if statement or otherwise. Using sieve-test suggests the basic script it should work and traces show the right action. On a related matter the script Im actually trying to get to work is: require ["variables", "envelope", "fileinto", "subaddress", "mailbox"]; if envelope :matches :detail "to" "*" { set :lower "name" "${1}"; } if mailboxexists "${name}" { fileinto :create "${name}"; } But fails and files in the inbox. Modifying the script to: require ["variables", "envelope", "fileinto", "subaddress", "mailbox"]; if envelope :matches :detail "to" "*" { set :lower "name" "${1}"; } if mailboxexists "${name}" { fileinto :create "folder7"; } else { fileinto :create "folder8"; } Files into folder8. So the mailboxexists is failing. ## Started executing script 'plus-addressing' 3: envelope test 3: starting `:matches' match with `i;ascii-casemap' comparator: 3: getting `to' part from message envelope 3: extracting `detail' part from address <test+folder4(a)test.net> 3: matching value `folder4' 3: with key `*' => 1 3: finishing match with result: matched 3: jump if result is false 3: not jumping 4: set command 7: modify :lower "folder4" => "folder4" 7: assign `name' [0] = "folder4" 7: mailboxexists test 7: mailbox `folder4' cannot be opened 7: some mailboxes are unavailable 7: jump if result is false 7: jumping to line 9 10: fileinto action 10: store message in mailbox `folder8' ## Finished executing script 'plus-addressing' Here folder4 actually does exist - so the sieve-test confirms that issue. Im at a loss as to whats going on. Im particularly perplexed by the difference in behaviour between sieve-test and the result under the live server. Any ideas?

2 3

strange misflagging of incoming mail as trash
by Robb Aley Allan 31 May '18

31 May '18

Setting up postfix/dovecot on a clean FreeBSD cloud server, and have discovered a strange problem resulting from the interaction of Mac OS X Mail and dovecot (using the Maildir file structure). Essentially, under very specific circumstances, Mail somehow tells dovecot that a new incoming message is trash, dovecot marks it as such, and the message effectively vanishes. The specific circumstance is as follows: 1. A message is sent to a server running postfix. It is placed in the Maildir mail structure in the “new” directory. 2. OS X Mail is used to retrieve mail via IMAP, and dovecot transfers the message from “new” to “cur”. 3. OS X Mail has a rule that seeks to transfer an incoming message to a subfolder if the message sender belongs to a group created in the Contacts app (IOW the sender is matched against an OS-internal contacts database). 4. IF the sender is the user, AND the user is in the group against which the rule is compared, the message is marked as trash (suffix “T”) and is never loaded into the mail client, either in the inbox or in the trash folder. For all intents and purposes, it disappears. The connection log shows the following line: "WROTE May 30 23:38:11.960 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:cloud.helical.com -- port:993 -- socket:0x6080004b6c80 -- thread:0x604000678e40 12.3 UID STORE 125 +FLAGS.SILENT (\Deleted)” which appears to be the client instructing dovecot to mark the message as deleted. I have the log files from the connection on both sides, and the console log from the Mac, but can’t understand 1. how Mail decides that the message should be deleted, and 2. why Mail “loses” the message (doesn’t appear in the Trash mailbox or anywhere else). _____ Robb Aley Allan

1 0

imapsieve: mailbox Trash: FLAG event
by Peter Schiffer 30 May '18

30 May '18

Hi all, after upgrade from Dovecot 2.2 to 2.3 I started to see that emails from Trash folder are automatically deleted after ~7 days. Email clients are not configured to automatically expunge or empty trash on log out (I see this behavior for multiple mailboxes, with different clients). With mail_debug enabled, I see this log message for every email that gets deleted from Trash: May 29 08:02:17 hostname dovecot: imap(some@mail)<7725><xxb6+VFtL+JT0CE 8>: Debug: imapsieve: mailbox Trash: FLAG event (changed flags: \Deleted) I have Dovecot 2.3.1 (8e2f634) and Pigeonhole 0.5.1 for sieve. My configuration can be found here: https://github.com/pschiffe/mailcow-dockerized/tree/master/data/conf/dovecot There is enabled support for sieve config in sql, but all sieve tables are empty, and there are no sieve filters for Trash flagging. Do you know how to find the source of that Trash flag event? I need to disable it or to configure it so it deletes emails at least couple of months old. Thanks all, peter

2 1

Re: Fatal: nfs flush requires mail_fsync=always
by Juan C. Blanco 30 May '18

30 May '18

Hello, any news about the attached error? I'm preparing the 2.2 to 2.3 upgrade and having the same error. We have the mail stores in an NFS filer. Regards > On 19.01.2018 11:55, Søren Skou wrote: >> Hiya all, >> >> I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on >> my testbed. The issue is that from what I can see, mail_fsync is set >> to always : >> >> # doveconf -n | grep mail_fs >> mail_fsync = always >> >> The result is that the client does not connect at all, which is not >> really what I wanted to happen :) >> >> Any idea what is going wrong here? >> >> Best regards >> Søren P. Skou >> >> doveconf -n >> >> # 2.3.1.alpha0 (bdfa22623) [XI:2:2.3.1~alpha0-1~auto+14]: >> /etc/dovecot/dovecot.conf >> # Pigeonhole version 0.5.1.alpha0 (d5f710e0) >> # OS: Linux 4.9.0-4-amd64 x86_64 Debian 9.3 nfs >> auth_worker_max_count = 200 >> dict { >> expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext >> quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext >> sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext >> } >> disable_plaintext_auth = no >> lock_method = dotlock >> mail_fsync = always >> mail_location = maildir:/mnt/virtual_mail/%d/%n >> mail_nfs_index = yes >> mail_nfs_storage = yes >> mail_plugins = quota >> mailbox_list_index = no >> metric imap_select_no { >> event_name = imap_command_finished >> filter { >> name = SELECT >> tagged_reply_state = NO >> } >> } >> mmap_disable = yes >> namespace inbox { >> inbox = yes >> location = >> mailbox Drafts { >> special_use = \Drafts >> } >> mailbox Junk { >> auto = subscribe >> special_use = \Junk >> } >> mailbox Sent { >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> special_use = \Sent >> } >> mailbox Trash { >> special_use = \Trash >> } >> prefix = >> } >> passdb { >> args = /etc/dovecot/dovecot-sql.conf.ext >> driver = sql >> } >> plugin { >> quota = dict:User quota::proxy::sqlquota >> quota_grace = 10%% >> quota_rule = *:storage=1000m:messages=300000 >> quota_rule2 = Trash:storage=+10%%:messages=+10%% >> quota_rule3 = Junk:storage=+20%%:messages=+20%% >> quota_status_nouser = DUNNO >> quota_status_overquota = 552 5.2.2 Mailbox is full >> quota_status_success = DUNNO >> quota_warning = storage=75%%:messages=75%% quota-warning 75 %u >> quota_warning2 = storage=95%%:messages=95%% quota-warning 95 %u >> quota_warning3 = -storage=100%%:messages=100%% quota-warning below %u >> sieve = /etc/dovecot/sieve/default.sieve >> sieve_global_dir = /etc/dovecot/sieve >> } >> protocols = " imap pop3" >> service dict { >> unix_listener dict { >> mode = 0600 >> user = vmail >> } >> } >> service imap { >> executable = imap >> } >> service quota-status { >> client_limit = 1000 >> executable = quota-status -p postfix >> inet_listener { >> address = 127.0.0.1 >> port = 12340 >> } >> } >> service quota-warning { >> executable = script /usr/local/bin/quota-warning.sh >> user = vmail >> } >> ssl_ca = /etc/ssl/certs/ca-root.crt >> ssl_cert = </etc/ssl/certs/stjerne.danskkabeltv.dk-2019.crt >> ssl_cipher_list = TLSv1+HIGH !SSLv2 !RC4 !aNULL !eNULL !3DES-CBC !3DES @STRENGTH >> ssl_dh = # hidden, use -P to show it >> ssl_key = # hidden, use -P to show it >> userdb { >> args = uid=2000 gid=2000 home=/mnt/virtual_mail/%d/%n >> driver = static >> } >> protocol lmtp { >> mail_plugins = quota >> } >> protocol lda { >> mail_plugins = quota >> } >> protocol imap { >> mail_plugins = quota imap_quota >> rawlog_dir = /tmp/rawlog/%u >> } > > Hi! > > Thanks, we'll look into it. > > Aki -- +-------------------------------------------------------------------+ | Juan C. Blanco | | | | Centro de Calculo | | | E.T.S. Ingenieros Informáticos | E-mail: jcblanco(a)fi.upm.es | | Universidad Politécnica de Madrid | | | Campus de Montegancedo | | | Boadilla del Monte | Tel.: (+34) 91 067 2771 | | 28660 MADRID (Spain) | Fax : (+34) 91 336 7412 | +-------------------------------------------------------------------+

2 2

Second rule isn't apply when first rule matches
by daniel_1983＠protonmail.com 30 May '18

30 May '18

Dear list, I want to define two concurrent rules : 1. I want to flag an e-mail containing the word "cloud" in the body 2. I want to move mail sent explicitly to me (as opposed to mail sent to an alias I am part of) going to "INOBX.I must answere this" If I put rule (1) first, everything works as expected. If put rule (2) first, only that rule applies. Here's a small test case you should be able to reproduce on your setup. Let's work on this fake test e-mail : $ cat testmail.eml Date: Mon, 28 May 2018 12:41:53 +0100 From: friend(a)otherdomain.tld To: me(a)mydomain.tld Subject: dur dur la vie mon frère, le cloud c'est le top du top Here's the first, broken version of the script $ cat test.sieve require ["body","fileinto","imap4flags","vacation"]; # rule:[Mail about me] if anyof (header :contains "to" "me(a)mydomain.tld", body :text :contains "ahmed") { fileinto "INBOX.I must answere this"; } # rule:[Mail about the Cloud] if body :text :contains "cloud" { addflag "\\Flagged"; } Let's test it out, the two rules should be applied : $ sieve-test test.sieve testmail.eml Performed actions: * store message in folder: INBOX.I must answere Implicit keep: (none) sieve-test(root): Info: final result: success $ Notice that the last rule isn't applied although it matches. Now we invert the order of the rules and apply the script on the same test e-mail : $ cat test.sieve require ["body","fileinto","imap4flags","vacation"]; # rule:[Mail about the Cloud] if body :text :contains "cloud" { addflag "\\Flagged"; } # rule:[Mail about me] if anyof (header :contains "to" "me(a)mydomain.tld", body :text :contains "ahmed") { fileinto "INBOX.I must answere this"; } Running the test again : $ sieve-test test.sieve testmail.eml Performed actions: * store message in folder: INBOX.I must answere + add IMAP flags: \flagged Implicit keep: (none) sieve-test(root): Info: final result: success $ The IMAP flag was set ! Any ideas ?

2 3