- dovecot - dovecot.org

Dovecot, sa-learn and sieve - where to save the Bayes DB
by Francis Augusto Medeiros-Logeay 31 Oct '20

31 Oct '20

Hi! I have dovecot, Spamassassin and postfix running. I started to use sa-learn to get better and more precise spam identification and filtering. I have not set the Bayes_path preference on my local.cf file, thus when I call sa-learn -u myuser(a)mydomain.org --spam, the Bayes DB gets updated at /root/.spamassassin. I decided then to create a sieve filter on dovecot, as described on Dovecot's wiki page. Basically, Dovecot's sieve plugin execute sa-learn with a -u argument, apparently the same way I do when I use it manually. BUT, the thing is that when Dovecot executes sa-learn, the bayes database is created on the virtual user's folder, ie., /var/mail/vmail/mydomain.org/user/.spamassassin. When I call it manually, the db used is /root/.spamassassin` I am now confused as I don't know if, when evaluating spam, spamd will use the Bayes DB on the user's Maildir, or if it will use the one under /root/.spamassassin. I would really like to have my spam evaluation done per user, not site wide, so I wonder: - How can I configure bayes_path for each user, individually, on a virtual users setup? - Does calling spamd with --virtual-config-dir have anything to do with this? I tried it, setting it up with my virtual users path, but it didn't seem to make any difference when it comes to what I describe in this post. With or without it set up, the results above are the same. -- Francis Augusto Medeiros-Logeay Oslo, Norway

1 0

Odd replication behaviour
by James Pattinson 31 Oct '20

31 Oct '20

Hi, I have just built a new pair of similar machines both running CentOS 8.2 (selinux disabled) and Dovecot 2.3.8 (9df20d2db). One machine is a VPS (host A) and one is on my home network (host B). The idea is that they are set up in a master/master config with Dovecot replication. I seem to have this 95% working but there is one strange issue I can’t work out. Currently B is a perfect replica of A. I have pointed an instance of Thunderbird at it, and I can see all my mails. If I delete any mails or change any flags, I see the same changes almost instantly on the A side. PROBLEM: if host A receives a new mail, I don’t see it on B until I do ‘something’ to change metadata, for example deleting any random email, or marking an email as read on EITHER side causes the new email to appear almost instantly on the B side. I would have expected emails on B to appear immediately. Am I doing something wrong? Extra info - my mailboxes are in Maildir format with single OS user (vmail). I have about 4000 emails in the Inbox and about 30k in other folders. There are only 5 users and I’m using passdb as the very simple backend. Replication is via doveadm on a specified port (not SSH). Some output from dovecot -n is below. Cheers James HOST A # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-193.28.1.el8_2.x86_64 x86_64 CentOS Linux release 8.2.2004 (Core) xfs # Hostname: hosta.domain auth_mechanisms = plain login doveadm_password = # hidden, use -P to show it doveadm_port = 4040 first_valid_uid = 1000 mail_debug = yes mail_home = /srv/vmail/%u mail_location = maildir:/srv/vmail/%u mail_plugins = notify replication 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 mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = scheme=BLF-CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { mail_replica = tcp:b.b.b.b:4040 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/mail/SpamToJunk.sieve } protocols = imap lmtp service aggregator { fifo_listener replication-notify-fifo { group = root mode = 0660 user = vmail } unix_listener replication-notify { group = root mode = 0660 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } service doveadm { inet_listener { port = 4040 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/mail2.pattinson.org/fullchain.pem ssl_cipher_list = PROFILE=SYSTEM ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = username_format=%u /etc/dovecot/users default_fields = uid=vmail gid=mail home=/srv/vmail/%u driver = passwd-file } protocol lmtp { mail_plugins = sieve } protocol lda { mail_plugins = notify replication sieve } HOST B # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-193.28.1.el8_2.x86_64 x86_64 CentOS Linux release 8.2.2004 (Core) ext4 # Hostname: hostb auth_mechanisms = plain login doveadm_password = # hidden, use -P to show it doveadm_port = 4040 first_valid_uid = 1000 mail_debug = yes mail_home = /srv/vmail/%u mail_location = maildir:/srv/vmail/%u mail_plugins = notify replication 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 mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = scheme=BLF-CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { mail_replica = tcp:a.a.a.a:4040 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/mail/SpamToJunk.sieve } protocols = imap lmtp service aggregator { fifo_listener replication-notify-fifo { group = root mode = 0660 user = vmail } unix_listener replication-notify { group = root mode = 0660 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } service doveadm { inet_listener { port = 4040 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/mail2.pattinson.org/fullchain.pem ssl_cipher_list = PROFILE=SYSTEM ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = username_format=%u /etc/dovecot/users default_fields = uid=vmail gid=mail home=/srv/vmail/%u driver = passwd-file } protocol lmtp { mail_plugins = sieve } protocol lda { mail_plugins = notify replication sieve }

1 1

Sieve filter script EXECUTION FAILED
by ＠lbutlr 31 Oct '20

31 Oct '20

So, I have the sieve working up to the point that it calls the script, and the script is called (I get different errors if the script is not there, for example). filter action execute program `darkmode.sh' [[EXECUTION ABORTED]] There's no other error logged (for example, when I had sieve_filter_bin_dir miss-set, I would get: sieve: action filter: failed to execute program `darkmode.sh': vnd.dovecot.filter extension is unconfigured In /var/log/messages, but I fixed that. I assume there is something wrong with what I am doing in the script, bit that is something I am not finding any examples on that are proving useful. The script file is simply: Darkmode.sh: #!/bin/sh echo $1 | sed -e '|</head>|<style>* {color:white !important; background-color: black !important; } </style></head>|' Which is somehwat similar to a working script for reporting spam: sa-learn-spam.sh: #!/bin/sh exec /usr/local/bin/sa-learn -u ${1} --spam -- "Are you pondering what I'm pondering?" "I think so, Brain, but won't it go straight to my hips?!"

5 8

Re: Sieve filter script EXECUTION FAILED
by Aki Tuomi 30 Oct '20

30 Oct '20

> On 30/10/2020 19:25 Bernd Petrovitsch <bernd(a)petrovitsch.priv.at> wrote: > > > On 30/10/2020 17:11, @lbutlr wrote: > [...] > > echo $1 | sed -e '|</head>|<style>* {color:white !important; background-color: black !important; } </style></head>|' > > What should the sed stuff do? > TTBOMK '|' is not known by sed ... > > MfG, > Bernd sed accepts | as alternative for / as boundary. But I think the sed here is missing 's' from start, so this does not actually do anything... Aki

5 5

Re: Sieve filter script EXECUTION FAILED
by Aki Tuomi 30 Oct '20

30 Oct '20

> On 30/10/2020 20:34 @lbutlr <kremels(a)kreme.com> wrote: > > > On 30 Oct 2020, at 11:57, Aki Tuomi <aki.tuomi(a)open-xchange.com> wrote: > > But I think the sed here is missing 's' from start, so this does not actually do anything... > > Copy/paste/edit error. The s is there in the file. > > darkmode.sh: > #!/bin/sh > echo $1 | sed -e 's|</head>|<style>* {color:white !important; background-color: black !important; } </style></head>|' > > I am not sure about the $1. I think filter just pipes the message (or part of the message. > > I will see what happens without the echo I suppose. > > Nope, still the same. > > 32: starting `:contains' match with `i;ascii-casemap' comparator: > 32: matching value `<!DOCTYPE html><html lang="en"><head><title>29-Oct-2020 ""</title> <style>?? ...' > 32: with key `</head>' => 1 > 32: finishing match with result: matched > 32: jump if result is false > 32: not jumping > 34: filter action > 34: execute program `darkmode.sh' > 34: [[EXECUTION ABORTED]] > > -- > They looked at the drinks. > They drank the drinks. I am pretty sure that you are holding filter wrong, it expects you to process the entire mail, not just $1. Aki

1 0

how to enable automatic sharing of folders added/created in an already shared folder hiearchy?
by PGNet Dev 30 Oct '20

30 Oct '20

I'm running dovecot --version 2.3.11.3 (502c39af9) folder sharing is enabled & working. as long as I manually enable enable sharing for each folder/subfolder. e.g., if I enable sharing for each of: sharedtopfolder subfolder1 subfolder2 then all's good -- shared-to users can access according to set permissions. BUT, if I drag any folder under that shared-hierarchy e.g., sharedtopfolder subfolder1 subfolder2 + subfolder3 + subfolder4 the just-added subfolder3 subfolder4 are NOT shared. They CAN be -- manually. And, as soon as they are, they're, again, usable by target users. I'd like to have any/all newly-created, or dragged-in, folders under the already-shared "sharedtopfolder" to be **automatically** enabled for sharing. how is that explicitly setup? is it 'just' Dovecot config? &/or does it require some Sieve?

1 0

Sieve matching the raw body
by ＠lbutlr 30 Oct '20

30 Oct '20

I have tried the following to match the string '</head>' in the body of an email: if body :raw :contains "</head>" { if body :content "text/html" :contains "</head>" { if body :contains "</head>" { All three result in matching value `' with key `</head>' => 0 finishing match with result: not matched RFC 5173 says: 5.1. Body Transform ":raw" The ":raw" transform matches against the entire undecoded body of a message as a single item. Which seems like exactly what I want. :content does not seem like what I want since it appears to only match the non HTML code content of the mime part. Eventually what I want to do is to alert some of the code in the HTML portion the email. Failing that, to remove the HTML mime part entirely, but that is less desirable. NB: I am not getting sieve.log errors the code seems to parse fine, it's just not matching how I expect. -- I'm the High King of Fillory. I took a blood test.

1 1

Filtering mails with sieve filters
by Odhiambo Washington 30 Oct '20

30 Oct '20

Hello good people, I have dovecot- 2.3.7.2 (Ubuntu Ubuntu 20.04.1 LTS) running fine. However, I have a hitch with mail filtering. Using SOGo as the webmail UI, I created a filter rule which resulted into the rule below: require ["fileinto"]; if allof (address :contains "from" "odhiambo") { fileinto "INBOX/Odhiambo"; } However, the test mail I sent did not end up the folder expected. lda.log contains this info: Oct 30 07:39:07 lda(wash@mydomain)<2415266><tSKSHhvDm1+i2iQA9H6eMA>: Info: sieve: msgid=<CAAdA2WNqXpG1qmOmKp_pJPS6iQrEPeS6=vM_= o8UnvR152x54Q(a)mail.gmail.com>: stored mail into mailbox 'INBOX' Oct 30 07:39:07 lda(wash@mydomain)<2415266><tSKSHhvDm1+i2iQA9H6eMA>: Info: sieve: Execution of script /var/spool/virtual/mydomain/wash/.dovecot.sieve failed, but implicit keep was successful (user logfile /var/spool/virtual/mydomain/wash/.dovecot.sieve.log may reveal additional details) And the .dovecot.sieve.log contains: sieve: info: started log at Oct 30 07:39:07. error: msgid=<CAAdA2WNqXpG1qmOmKp_pJPS6iQrEPeS6=vM_= o8UnvR152x54Q(a)mail.gmail.com>: failed to store into mailbox 'INBOX/Odhiambo': *Invalid mailbox name: Name must not have '/' characters.* What might be the problem here?? dovecot -n output is below: # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-29-generic x86_64 Ubuntu 20.04.1 LTS ext4 # Hostname: jp.mydomain auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb debug_log_path = /var/log/dovecot/debug.log default_login_user = dovecot default_vsz_limit = 2 G disable_plaintext_auth = no first_valid_uid = 110 hostname = gw.mydomain info_log_path = /var/log/dovecot/info.log log_path = /var/log/dovecot/error.log mail_gid = Debian-exim mail_location = maildir:/var/spool/virtual/%d/%n/Maildir:INDEX=/var/spool/virtual/indexes/%d/%1n/%n mail_plugins = fts mail_privileged_group = mail mail_server_admin = postmaster@mydomain mail_uid = Debian-exim 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 imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = 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 = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts_autoindex_exclude3 = \Drafts fts_autoindex_exclude4 = \Spam fts_enforced = yes imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * plugin = fts managesieve sieve sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } postmaster_address = postmaster@mydomain protocols = imap lmtp sieve service auth { unix_listener auth-client { mode = 0600 user = Debian-exim } unix_listener auth-userdb { group = Debian-exim user = Debian-exim } } service stats { unix_listener stats-reader { user = Debian-exim } unix_listener stats-writer { user = Debian-exim } } service submission-login { inet_listener submission { port = 2587 } } ssl_cert = </etc/letsencrypt/live/mydomain/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { info_log_path = /var/log/dovecot/lmtp.log log_path = /var/log/dovecot/lmtp-errors.log mail_plugins = fts sieve postmaster_address = postmaster@mydomain } protocol lda { info_log_path = /var/log/dovecot/lda.log log_path = /var/log/dovecot/lda-errors.log mail_plugins = fts sieve } -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

2 3

doveadm replicator, what decides the timing on a full resync?
by Norman King 30 Oct '20

30 Oct '20

Hello. If running dovadm replicator status, i get something like the following. root@mail2:~# doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 4 Waiting 'failed' requests 0 Total number of known users 1000 When would these full resyncs happen? Is it on a schedule? and if so where is said schedule configured? doveadm replicator dsync-status shows plenty of available sessions. Thanks. -- regards Norman King Compass Foundation sysadmin/tech support Phone, 856-974-5335 ext 221 support(a)compassfoundation.io <mailto:support@compassfoundation.io> Website <https://compassfoundation.io>

1 0

When is the Dovecot 2.3.12 release due?
by Sidsel Jensen 30 Oct '20

30 Oct '20

Hi We are very eager to test the zstd compression in the upcoming Dovecot 2.3.12 release - any pointer as to when that is expected to be released? Kind Regards, Sidsel

1 0

dovecot replicator not replicating automatically?
by Norman King 29 Oct '20

29 Oct '20

Hello all. I'm trying to set up the dovecot replicator plugin to automatically replicate mail between 2 servers. The servers are both using iredmail with dovecot as the imap server. I have everything working if i run dovecot replicator replicate \* all accounts update. But if an account receives a message it isn't automatically sent to the other system. The system config. OS, ubuntu 20.04 db, postgresql 12 dovecot info. root@mail:~# dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.3.18-2-pve x86_64 Ubuntu 20.04.1 LTS # Hostname: mail.daystar.io auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN deliver_log_format = from=%{from}, envelope_sender=%{from_envelope}, subject=%{subject}, msgid=%m, size=%{size}, delivery_time=%{delivery_time}ms, %$ dict { acl = pgsql:/etc/dovecot/dovecot-share-folder.conf lastlogin = pgsql:/etc/dovecot/dovecot-last-login.conf quotadict = pgsql:/etc/dovecot/dovecot-used-quota.conf } doveadm_password = # hidden, use -P to show it doveadm_port = 10993 first_valid_uid = 2000 last_valid_uid = 2000 listen = * [::] login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k session=<%{session}> mail_gid = 2000 mail_location = maildir:%Lh/Maildir/:INDEX=%Lh/Maildir/ mail_plugins = quota mailbox_alias acl mail_log notify mail_uid = 2000 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 metric imap_command_finished { event_name = imap_command_finished } namespace { inbox = yes location = mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox "Junk E-mail" { auto = no special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } namespace { list = children location = maildir:%%Lh/Maildir/:INDEX=%%Lh/Maildir/Shared/%%Ld/%%Ln prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-pgsql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-master-users driver = passwd-file master = yes } plugin { acl = vfile acl_shared_dict = proxy::acl mail_log_events = delete undelete expunge copy mailbox_create mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from subject flags mail_replica = tcp:10.2.2.113:10993 mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_old = Sent mailbox_alias_old2 = Sent quota = dict:user::proxy::quotadict quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=100%% quota-warning 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u sieve = ~/sieve/dovecot.sieve sieve_before = /var/vmail/sieve/dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/vmail/sieve sieve_max_redirects = 30 sieve_vacation_send_from_recipient = yes } protocols = pop3 imap sieve lmtp service anvil { client_limit = 7000 } service auth { client_limit = 7000 unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service doveadm { inet_listener { port = 10993 } } service imap-login { process_limit = 6144 service_count = 1 } service imap { process_limit = 6144 } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } service pop3-login { service_count = 1 } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12340 } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } service stats { client_limit = 5000 fifo_listener stats-mail { mode = 0644 user = vmail } inet_listener { address = 127.0.0.1 port = 24242 } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl = required ssl_ca = </etc/ssl/certs/star.daystar.io.crt ssl_cert = </etc/ssl/certs/star.daystar.io-chained.crt ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local5 userdb { args = /etc/dovecot/dovecot-pgsql.conf driver = sql } protocol lda { lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_plugins = quota mailbox_alias acl mail_log notify sieve } protocol lmtp { lmtp_save_to_detail_mailbox = yes mail_plugins = quota mailbox_alias acl mail_log notify sieve recipient_delimiter = + } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 100 mail_plugins = quota mailbox_alias acl mail_log notify imap_quota imap_acl } protocol pop3 { mail_max_userip_connections = 50 mail_plugins = quota mailbox_alias acl mail_log notify pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } What's wrong with this picture? Thanks. -- regards Norman King Compass Foundation sysadmin/tech support Phone, 856-974-5335 ext 221 support(a)compassfoundation.io <mailto:support@compassfoundation.io> Website <https://compassfoundation.io>

2 3

Re: dovecot replicator not replicating automatically?
by Aki Tuomi 29 Oct '20

29 Oct '20

Hi! In order for replication to trigger, you need - load the replication plugin - use dovecot-lda / lmtp to deliver mail If you have done these both, please provide doveconf -n and output of mail_debug=yes logs. Aki > On 29/10/2020 19:10 Norman King <norman(a)compassfoundation.io> wrote: > > > Thanks for that tip. > I loaded the replication plugin but still have the same issue. Anything else i can check? > > > > > regards > Norman King > Compass Foundation sysadmin/tech support > Phone, 856-974-5335 ext 221 > support(a)compassfoundation.io > Website (https://compassfoundation.io) > On 10/29/2020 12:17 PM, Sami Ketola wrote: > > > > > > > > > > > > On 29. Oct 2020, at 17.24, Norman King <norman(a)compassfoundation.io> wrote: > > > > > > > > > Hello all. > > > I'm trying to set up the dovecot replicator plugin to automatically replicate mail between 2 servers. > > > The servers are both using iredmail with dovecot as the imap server. > > > > > > I have everything working if i run dovecot replicator replicate \* all accounts update. But if an account receives a message it isn't automatically sent to the other system. > > > > > > > > > The system config. > > > > > > > > > mail_plugins = quota mailbox_alias acl mail_log notify > > > > > > > > > > > > > your mail_plugins does not even load replication plugin. > > > > > > Sami > > > >

1 0

Re: Support of INDEXPVT in Dovecot 2.3 with replication
by Aki Tuomi 29 Oct '20

29 Oct '20

At the moment the correct way to use shared folders in a replication pair is to access them with imapc from the other pair. Aki > On 29/10/2020 14:43 Ralf Becker <rb(a)egroupware.org> wrote: > > > In reference to an earlier mail from me, I'd like to ask: > > Have there been any changes in regard to INDEXPVT and replication or are > there any plans in that direction? > > Thanks :) > > Ralf > > > On 03.08.20 at 11:20 Ralf Becker wrote: > > So far the only thing we noticed: private seen flags on shared user > > folders (which were never supported for replication!) seem to be not > > functioning any more in 2.3. Not functioning means, if they are > > configured you can not set a mail to seen in a shared user folder. After > > removing this configuration: > > > > location = mdbox:%%h/mdbox:INDEXPVT=~/shared/%%u --> mdbox:%%h/mdbox > > > > seen flags behave as expected / are identical now if you access the > > mailbox direct or via the shared user folder, and the are identical on > > both backends. > > > > Ralf > > -- > Ralf Becker > EGroupware GmbH [www.egroupware.org] > Handelsregister HRB Kaiserslautern 3587 > Geschäftsführer Birgit und Ralf Becker > Leibnizstr. 17, 67663 Kaiserslautern, Germany > Telefon +49 631 31657-0

2 1

Support of INDEXPVT in Dovecot 2.3 with replication
by Ralf Becker 29 Oct '20

29 Oct '20

In reference to an earlier mail from me, I'd like to ask: Have there been any changes in regard to INDEXPVT and replication or are there any plans in that direction? Thanks :) Ralf On 03.08.20 at 11:20 Ralf Becker wrote: > So far the only thing we noticed: private seen flags on shared user > folders (which were never supported for replication!) seem to be not > functioning any more in 2.3. Not functioning means, if they are > configured you can not set a mail to seen in a shared user folder. After > removing this configuration: > > location = mdbox:%%h/mdbox:INDEXPVT=~/shared/%%u --> mdbox:%%h/mdbox > > seen flags behave as expected / are identical now if you access the > mailbox direct or via the shared user folder, and the are identical on > both backends. > > Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

1 0

dovecot quota-warning detection mail
by 森川　孝司 29 Oct '20

29 Oct '20

Hi, all. we use quota-warning emails to notify you of quotas. In rare cases, the email address has changed to the logged-in user. (Because the address of %u is passed as the logged-in user.) So I couldn’t send the email with “Recipient address rejected: User unknown in local recipient table”. Why does my email address change to a logged-in user? %u of "quota_warning = storage = 95 %% quota-warning 95% u" The output is the logged-in user. By Morikawa

3 16

Directors and LMTP: mailAlternateAddress of same user
by Paterakis E. Ioannis 28 Oct '20

28 Oct '20

Good evening everyone, I'd like to paste a problem i experience the last days with a mail cluster system based on three dovecot servers and two directors in front of them. The Directors are proxying the auth requests to the dovecot servers below (LDAP). The protocols i use are imap/managesieve/lmtp. The setup works as intented, exept one detail. There are a lot of users that happen to have mailAlternateAddress attriutes with different e-mail addresses. The problem is that when a mail arrives to the lmtp of the directors, and the recipient is one of the mailalternateAddresses the same user has, director/lmtp doesn't recognise the real user of that e-mail address, and routes the e-mail to a different dovecot server than the real user is logged in, resulting in a corrupted .index.cache file. I've searched around for a solution to this, and figured out that a special userdb {} section in the protocol lmtp {} section, with driver = ldap etc etc so that i 'd be able to "show" the correct user to the lmtp might work, but strangely that userdb {} setting looks like being ignored by lmtp. Has any of you guys have an idea how will i be able to solve that issue because i get thousands of corrupted .index.cache files every day.... Thank you very much in advance, Ioannis

2 2

Looking for a guide to collect all e-mail from the ISP mail server
by R. Diez 28 Oct '20

28 Oct '20

Hi all: I am evaluating mail server solutions for a small business. The trouble is, I am only a part-time admin and a newbie to mail servers. Most guides I have seen are rather unrealistic: they encourage you to expose your e-mail server to the Internet, and hope that you have the resources to keep it patched up. I would rather have an internal mail server that collects e-mails from a standard ISP mail server. It is like the old "POP3 Connector" that came with Microsoft Exchange. Sometimes, there is a mailbox per user on the ISP, and a corresponding one on the local server. Other times, there is a single "catch all" or "multidrop" mailbox on the ISP. Users can still access their internal mailboxes from outside through an OpenVPN connection. The goal is that only VPN, and perhaps SSH, are accessible from the outside. We do not need to arrange any special SMTP configuration with the ISP either. This kind of mail server setup is rather different to the standard configuration. You do not normally need you own antivirus and spam filter, and you do not need to configure SSL certificates, MX or SPF DNS records. Most ISP handle that correctly and economically. Internal e-mail does not leave your LAN, and your internal SMTP server is just a relay for the external ISP SMTP server. Furthermore, most guides do not explain how to setup an autoresponder ("I am on holiday until xxx") so that users can enable theirs with the mouse. Editing configuration files over SSH is not really an option for normal users. This detail is important because it could be the only thing I need above standard e-mail. Further groupware features can be seen as nice but ultimately unnecessary luxury, and a basic shared calendar can be accomplished with a separate server like https://radicale.org/ and a calendar client like one built into Thunderbird. Hopefully, that is all I would need for a small business. Can anyone point me to the kind of guide I need? Failing that, I would need information or examples about using fetchmail, getmail or similar software with Dovecot. Good or bad experiences from you guys would also help. Each of those tools has a detailed man page, but there are many options and ways with different advantages and disadvantages. I would need a simpler guide to get started. I am aware that there are pre-packaged mail server solutions that would perhaps bring an easy-to-use autoresponder, but I haven't seen one yet that where you could tick a box like "this server is only internal and collects mail from the ISP server" during installation. Nor have I seen instructions about reconfiguring the mail server for my ISP mail scenario. I am prepared to learn more and write my own Perl scripts and/or installation guide, but it would be stupid to waste time if something easy already exists. After all, the setup I am describing (external ISP mail server + internal mail server) is not so weird. Thanks in advance, rdiez

21 82

doveadm SSL problem with recent update
by Trever L. Adams 27 Oct '20

27 Oct '20

With a recent update, I started seeing this: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 14: ssl_cert: Can't open file /etc/letsencrypt/live/SERVER/fullchain.pem: Permission denied 1 4 * * * vmail /usr/bin/doveadm expunge -A mailbox MAILBOXINQUESTION savedbefore 1w is one of the crontab entries I am seeing this for. Is there an option to keep doveadm from trying to use the ssl cert from that configuration file? I do not want to have the vmail user having access to the pem cert. Thank you. Trever

2 2

Newbie question about replication
by Piotr Auksztulewicz 27 Oct '20

27 Oct '20

Hi, I am a long-time dovecot user/admin for my family mail server, but I had ventured into configuring replication only recently and I am not sure about how it should work and what are the good practices. My intent for replication was to have another instance to switch to in a short time if something fails. I have daily backups, but it will take much more time to rebuild and restore than just to switch to a good instance while taking time to restore the bad one. The setup seems to work just fine from IMAP client point of view (minus sieve scripts - but I have worked it around as I am not yet ready to upgrade dovecot beyond what's in stable Debian at the moment). I have my clients configured to access instance A exclusively; instance B is just sitting around with no clients routinely connected. Also only instance A is receiving deliveries from both my primary and secondary MTAs. I have some doubt however if this is the right thing to do and if it is correct from the dovecot server point of view. I have observed my mail storage directories on both instances and have noticed that they diverge a little over time - the instance B not having all the updates. However the moment I connect another client to instance B and log in as a particular user, the state on instance B springs to the correct state and I see the same content on both clients, and the storage directories become identical as well. I am afraid that, if instance A fails, I would not have the current state on instance B. Is there anything I should have done differently? Here is dovecot -n output of instance A. Instance B config is symmetrical with imap1/2 hostnames switched. FYI: actual domain is substituted for privacy. mail.mydomain.net is an internal subdomain with private IP addresses. Instances of dovecot are containerized with access to internal virtual bridge on which MTAs and supporting processes are present as well. The access from outside is provided by port forwarding/NAT, only for imaps and pop3s ports. Other ports are only internally accessible for local clients (postfix, mutt, doveadm command line tool etc.) or debug purposes. # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-cloud-amd64 x86_64 # Hostname: imap1.mail.mydomain.net auth_failure_delay = 3 secs auth_verbose = yes auth_worker_max_count = 5 deliver_log_format = msgid=%m; from=%f: %$ disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 4551 first_valid_uid = 100 login_greeting = # <redacted> mail_attribute_dict = file:mail/dovecot-attributes mail_gid = 122 mail_home = /var/vmail/%u mail_location = maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 mail_plugins = " notify replication" mail_privileged_group = vmail mail_uid = 113 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 editheader vnd.dovecot.debug namespace inbox { inbox = 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 = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext.local driver = sql } plugin { mail_replica = tcp:imap2.mail.mydomain.net sieve = ~/.sieve sieve_dir = ~/sieve sieve_extensions = +vnd.dovecot.debug +editheader sieve_user_log = ~/log/sieve.log } pop3_fast_size_lookups = yes pop3_lock_session = yes pop3_no_flag_updates = yes pop3_save_uidl = yes protocols = " imap lmtp sieve pop3" replication_max_conns = 5 service aggregator { fifo_listener replication-notify-fifo { group = root mode = 0660 user = vmail } unix_listener replication-notify { group = root mode = 0660 user = vmail } } service auth-worker { chroot = /etc/dovecot/db process_limit = 10 unix_listener auth-worker { mode = 0600 user = doveauth } user = doveauth } service auth { client_limit = 64 inet_listener sasl { address = imap1.mail.mydomain.net port = 9192 } unix_listener auth-userdb { group = vmail mode = 0660 user = doveauth } user = doveauth } service dict-async { protocol = none } service dict { protocol = none } service director { protocol = none } service doveadm { inet_listener doveadm { address = imap1.mail.mydomain.net port = 4551 } } service imap-hibernate { protocol = none } service imap-login { inet_listener imap { address = imap1.mail.mydomain.net port = 143 } process_limit = 30 service_count = 1 } service imap-urlauth-login { protocol = none } service imap-urlauth-worker { protocol = none } service imap-urlauth { protocol = none } service imap { chroot = /var/vmail client_limit = 15 process_limit = 30 service_count = 32 user = vmail } service indexer-worker { process_limit = 3 user = vmail } service indexer { chroot = $base_dir } service lmtp { client_limit = 1 extra_groups = group = vmail inet_listener lmtp { address = imap1.mail.mydomain.net port = 2306 } process_limit = 6 user = vmail } service log { user = $default_internal_user } service managesieve-login { inet_listener sieve { address = imap1.mail.mydomain.net port = 4190 } process_limit = 3 service_count = 1 } service managesieve { chroot = /var/vmail process_limit = 3 service_count = 1 user = vmail } service pop3-login { inet_listener pop3 { port = 0 } process_limit = 4 service_count = 1 } service pop3 { chroot = /var/vmail process_limit = 4 service_count = 1 user = vmail } service replicator { unix_listener replicator-doveadm { group = root mode = 0600 user = vmail } } service submission-login { protocol = none } service tcpwrap { protocol = none } ssl_cert = </etc/dovecot/private/dovecot.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext.local driver = sql } valid_chroot_dirs = /var/vmail /etc/dovecot/db verbose_proctitle = yes protocol lmtp { mail_plugins = " notify replication sieve" } protocol imap { imap_metadata = yes } -- Piotr "Malgond" Auksztulewicz firstname(a)lastname.net

2 5

Re: Dovecot replication not picking up new mail in maildir
by Justin Ridge 27 Oct '20

27 Oct '20

On 26/10/2020 19:25, John Fawcett wrote: > On 25/10/2020 17:19, jayare~dcml at videocoding.org wrote: >> I've got a basic dovecot master-master replication setup between two >> servers (imap1 and imap2). Actions such as deleting messages or moving >> them between folders are replicated correctly and quickly. >> >> However, when new mail is delivered by postfix, replication does not >> occur until something else triggers it, such as one of the delete/move >> actions mentioned earlier. A search suggested this may be due to the >> notify plugin, but I don't see any issue with the settings. Output of >> doveconf -n: > > Hi > > is there any error in the log? > > Can you show some evidence or an example? ie some email delivery in the > master but not on the slave? > > Can you be sure to check both new and cur subdirectories on master and > slave? > > John There's precisely nothing in the log. The new mail arrives on the master, and it is as though dovecot completely ignores it for the purposes of replication. However, I think I have solved the problem by enabling LMTP and forcing postfix to go through that rather than writing to the maildir directly. Perhaps LMTP is required for replication and I just didn't realize it. End result is (I think) it is working properly. J

3 3

imapsieve: setting imapsieve_url disables admin scripts
by Gedalya 27 Oct '20

27 Oct '20

Hello, The documentation says imapsieve_url "has no effect on the administrator-controlled Sieve scripts". However, when setting this item, I get lines such as: Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script mailbox attribute: Mailbox attributes not enabled and that's it. imapsieve_mailboxXXX_* settings are completely ignored. Unsetting imapsieve_url makes it all work again. # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (6c69c917) # OS: Linux 4.19.0-5-amd64 x86_64 Debian bullseye/sid xfs # Hostname: ------ auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes imapc_features = rfc822.size fetch-headers imapc_host = imap.gmail.com imapc_port = 993 imapc_ssl = imaps log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = vmail mail_home = /srv/mail/domains/%d/%n mail_location = mdbox:/srv/mail/domains/%d/%n/mdbox mail_plugins = quota fts fts_solr mail_prefetch_count = 20 mail_privileged_group = mail mail_uid = vmail 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 imapsieve vnd.dovecot.imapsieve mdbox_preallocate_space = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = solr fts_autoindex = yes fts_solr = url=http://127.0.0.1:8983/solr/dovecot/ fts_tika = http://127.0.0.1:9998/tika/ imapsieve_mailbox1_before = file:/usr/local/lib/imapsieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/local/lib/imapsieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/usr/local/lib/imapsieve/report-spam.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = Junk2 imapsieve_mailbox4_before = file:~/sieve/IMAP-Sent.sieve imapsieve_mailbox4_causes = APPEND COPY imapsieve_mailbox4_name = Sent quota = count:User quota:noenforcing quota_rule = *:storage=5120M quota_vsizes = yes sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve-global/fileinto-spam.sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/local/lib/imapsieve sieve_plugins = sieve_imapsieve sieve_extprograms } pop3_fast_size_lookups = yes pop3_no_flag_updates = yes protocols = " imap lmtp sieve pop3" quota_full_tempfail = yes service auth-worker { user = $default_internal_user } service auth { unix_listener auth-client { group = Debian-exim mode = 0660 user = Debian-exim } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = $default_internal_user } service imap-login { inet_listener imap { port = 143 } service_count = 0 } service imap { vsz_limit = 512 M } service lmtp { inet_listener lmtp { address = ------- port = 2525 } unix_listener lmtp { group = Debian-exim mode = 0660 user = root } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 } service pop3-login { inet_listener pop3 { port = 110 } service_count = 0 } ssl = required ssl_cert = </etc/letsencrypt/live/--------/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = quota fts fts_solr sieve ssl = no } protocol !indexer-worker { mail_vsize_bg_after_count = 100 } protocol lda { mail_plugins = quota fts fts_solr sieve } protocol imap { mail_max_userip_connections = 30 mail_plugins = quota fts fts_solr imap_quota imap_sieve } protocol sieve { mail_max_userip_connections = 10 }

2 2

imapc_port not working
by David Tildesley 27 Oct '20

27 Oct '20

Hi, Dovecot v2.3.7.2 on Ubuntu 18.04LTS I have configured for imap proxy to imap.gmail.com However whilst the imapc_host setting is working, imapc_port is not - it ignores the value I set and dovecot always tries to connect to gmail on port 143 (as per error log output). I have the imapc settings in the 10-mail.conf which gets loaded by dovecoat.conf Looks like a bug. Any assistance would appreciated. Regards,David.

2 9

forwarding email with sieve of spf domains
by Marc Roos 27 Oct '20

27 Oct '20

Say someone has setup spf for his domain and sends an email to a user that has in roundcube enabled the sieve forward. If the message is forwarded without altering the message headers, this could result in a message being blocked or not relayed, because sending hosts ip, is not in the spf of the from: domain. Possible solutions are: - add option if enabled, it replaces the From: with that of the email address of the sieve user. (Maybe move the original sender to the Reply-To header? Maybe exception for 'internal' forward?) - Upon processing the message, check the spf records, if they are enforced, do the above, otherwise do nothing. https://tools.ietf.org/html/rfc5228#section-4.2

6 7

Roundcube can't receive emails
by direktor 26 Oct '20

26 Oct '20

Hello, Can someone guide me how to test the mail software? I can send emails but can't receive. I have Dovecot - telnet to 143 port says Dovecot OK. Same with port 25. I get back mail delivery problem. 550. No mail shows in Roundcube. Log files maillog shows nothing, seems empty. It's clean install. On testing Exim log I get something like this: pop3-login auth Error: passrd-file: stat (/etc/exim/domains/myserver/passwd) failed: No such file or directory So what is wrong, how to check and how to fix it? -- Sent from: http://dovecot.2317879.n4.nabble.com/

1 0

Dovecot replication not picking up new mail in maildir
by jayare~dcml＠videocoding.org 26 Oct '20

26 Oct '20

I've got a basic dovecot master-master replication setup between two servers (imap1 and imap2). Actions such as deleting messages or moving them between folders are replicated correctly and quickly. However, when new mail is delivered by postfix, replication does not occur until something else triggers it, such as one of the delete/move actions mentioned earlier. A search suggested this may be due to the notify plugin, but I don't see any issue with the settings. Output of doveconf -n: # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # OS: Linux 4.19.118-0-vanilla x86_64 CentOS Linux release 7.8.2003 (Core) # Hostname: imap1 disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it first_valid_uid = 1000 haproxy_trusted_networks = 172.16.0.0/24 mail_location = maildir:~/Mail mail_plugins = zlib notify replication mailbox_list_index = yes mailbox_list_index_include_inbox = yes maildir_empty_new = yes mbox_write_locks = fcntl namespace inbox { inbox = 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 = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:imap2:9943 replication_sync_timeout = 2 } protocols = imap service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = dovecot } unix_listener replication-notify { mode = 0666 user = dovecot } } service config { unix_listener config { user = dovecot } } service doveadm { inet_listener { port = 9943 } } service imap-login { inet_listener imap_hpx { haproxy = yes port = 943 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = no userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = zlib notify replication } protocol imap { mail_plugins = zlib notify replication imap_zlib } I specifically tried setting the following as no and yes as they can affect notifications: mailbox_list_index = yes mailbox_list_index_include_inbox = yes maildir_empty_new = yes The other server has the same settings except obviously mail_replica = tcp:imap1:9943. Any suggestions welcome, thanks!

2 1