- dovecot - dovecot.org

Percent character in mail_crypt_private_password not possible
by mabi 04 Jul '19

04 Jul '19

Hello, I am using the mail_crypt plugin with Dovecot 2.3 and have issues trying to use a mail crypt private password which contains a percent "%" character as you can see below: $ doveadm -o plugin/mail_crypt_private_password=SomethingWith\%Percent mailbox cryptokey generate -u email(a)domain.tld -URf doveadm(email(a)domain.tld): Error: Failed to expand plugin setting mail_crypt_private_password = 'SomethingWith%Percent': Unknown variable '%P' Note here that the percent is escaped with a backslash "\%" in order for the shell not to process it. Regards, Mabi

2 11

mail_crypt: multiple keypairs
by mabi 04 Jul '19

04 Jul '19

Hello, I am testing mail_crypt plugin with per account encryption and wanted to generate a new keypair for an account but noticed that I now end up with 2 keypairs where one is active and the other inactive as you can see below: $ doveadm mailbox cryptokey list -u email(a)domain.tld -U Folder Active Public ID yes 7b140b4f3d6d68eed2c59259ac5e6f6a280dc82990292dc415b4100d6c797f67 no 1c1dd1c955757da7c19f1eeb6d6c4d0d66e6355baa2d844bc2623052e1aa2f91 Does this mean now that all existing emails get encrypted with both keypairs? or does this mean only the active keypair is used to encrypt new emails? Is it possible to delete the inactive keypair? if yes how? Regards, Mabi

3 4

fts_lucene
by Ignacio García 04 Jul '19

04 Jul '19

Hi everybody... I've inherited 2 servers with dovecot and fts_lucene enabled, which I plan to switch to fts-solr instead. My plan is to disable lucene in dovecot.conf, delete all cache associated files, and start configuring the fts plugin from scratch. I need to make sure that I don't mess up things pretty bad and delete the correct files. Are those to be deleted all dovecot.index* files located in the Maildir folder? Is there anything else I should be aware of? Thanks so much in advance for your kind help! Ignacio

1 0

dsync not replicatiing .dovecot.sieve
by Laura Smith 04 Jul '19

04 Jul '19

There was a post on this topic to the list Aug 06, 2018 to which Aki replied "Thank you for reporting this, we'll take a look at this.". But its not clear what (if anything) has happened since ? The problem still seems to exist in 2.3.3 (original report by previous poster was for 2.3.2.1) The scenario I'm seeing is pretty much identical to the original poster's. Mail seems to be replicating fine, but sieve doesn't replicate at all.

2 1

Sieve question
by ＠lbutlr 04 Jul '19

04 Jul '19

I have the following in my active sieve file, and there are no errors logged. if header :contains "to" "+root" { setflag "\\Seen"; fileinto :create "root"; stop; } The message is put in .root, bit is not marked as seen. Is the default action to put mail in a folder matching the extension taking precedence?

2 2

mail_replica equivalent to replicator_host/replicator_port
by Laura Smith 03 Jul '19

03 Jul '19

Silly question but regarding https://wiki.dovecot.org/Replication, is the mail_replica parameter shown in the docs equivalent to replicator_host and replicator_port in 2.3.3 ? 2.3.3 doesn't seem to like the mail_replica param (and indeed doveconf -a doesn't show it as an option) Thanks !

2 1

Dovecot LMTP mixing up users on multi-recipient mail
by Bernhard Schmidt 03 Jul '19

03 Jul '19

Hi, I've upgraded a mailstore from Debian Jessie (aka oldstable) with Dovecot 2.2.13 to Debian Buster (next stable) with Dovecot 2.3.4.1 today. It worked pretty well, except that we're seeing error messages very similar to this old thread https://dovecot.org/pipermail/dovecot/2015-July/101396.html It appears to be happening when a mail with multiple recipients on this message store is getting delivered through lmtp. Jun 27 11:47:36 lxmhs74 dovecot: lmtp(user1)<47683><sGwaD7eQFF1DugAAgkzuhA:18>: Error: open(/var/cache/dovecot/index/n/user2n/.INBOX/dovecot.index.cache) failed: Permission denied (euid=3814520(<unknown>) egid=12(man) missing +x perm: /var/cache/dovecot/index/n/user2, dir owned by 3391995:12 mode=0700) user1 uid is 3814520, user2n uid is 3391995. Dovecot appears to be trying to deliver the message to user1 while using the index directory of user2n. Further configuration: - message store is on NFS - cache directory is on local disk - users are coming from LDAP, one UID per user user_attrs = cn=user,homeDirectory=home,uidNumber=uid,gidNumber=gid - index directory is calculated from the username maildir:~/Maildir:INDEX=/var/cache/dovecot/index/%-1.1n/%n Despite the error messages (which appear dozens of times per delivery attempt) delivery seems to work. Workaround was to set lmtp_destination_recipient_limit = 1 on the postfix in front of the message store. Despite the report linked above being quite old, I can't recall having issues with 2.2.13. === doveconf -n === # OS: Linux 4.19.0-5-amd64 x86_64 Debian 10.0 # Hostname: lxmhs74.srv.lrz.de default_vsz_limit = 512 M deliver_log_format = from=<%e>, size=%p, message-id=<%m>, status=%$ imap_id_log = * imap_id_send = * lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_greeting = Dovecot ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> cipher=<%k> mail_gid = mstore mail_location = maildir:~/Maildir:INDEX=/var/cache/dovecot/index/%-1.1n/%n mail_plugins = quota listescape 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 index ihave duplicate mime foreverypart extracttext 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=1024M 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=90%% quota-warning 90 %u sieve = ~/currently-active-script.sieve sieve_dir = ~/sieve } pop3_uidl_format = %v-%u 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 imap { process_limit = 8192 } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { 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 = 20 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /etc/dovecot/quotawarnmsg.sh unix_listener quota-warning { group = mstore mode = 0660 user = mstore } user = mstore } service stats { process_limit = 8192 } ssl_cert = </etc/dovecot/dovecot.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } verbose_proctitle = yes protocol imap { mail_plugins = quota listescape imap_quota imap_zlib } protocol lda { mail_plugins = quota listescape sieve } protocol lmtp { mail_plugins = quota listescape sieve } remote 127.0.0.1 { disable_plaintext_auth = no } remote ::1 { disable_plaintext_auth = no } === Thanks, Bernhard

2 1

Replicate shared folders to warm standby host
by Axel Gluth 03 Jul '19

03 Jul '19

We like to set up our mail system in two datacenters but the wiki<https://wiki.dovecot.org/Replication> says "Shared folder replication doesn't work correctly..." I'm thinking about using an external loadbalancer to ensure that only one host will get connections. Normal operations: client ==imap=> loadbalancer ==imap=> host1 ==replication=> host2 Host1 or Datacenter1 is down: client ==imap=> loadbalancer ==imap=> host2 I see possible problems if host1 comes back and clients connect to host1 before the replication has caught up. But in our case that will be acceptable. Do you consider my idea as safe for production use? Has anybody real world experience with such a setup? Is there a better way to replicate shared folders? Thank you in advance for spending your time on thinking about my problem. Axel

1 0

Dovecot/MSQL issue
by Nathan 03 Jul '19

03 Jul '19

Hello, I'm trying to work through an issue that cropped up on a server I've been working on and haven't found a very good workaround. Dovecot is operating in a jailed environment. The configuration in dovecot-sql.conf.ext has been set appropriately with the host=127.0.0.1 (which works from a jailed environment) and when dovecot attempts to auth it appears to perform a reverse dns lookup and overwrites the host with the result localhost before using the msql credentials 'user'@'localhost' which then fails after timing out. I'm currently running version 2.2.33.2 of dovecot. The workaround seems to be to have two credentials for the same user. 'user@'localhost' and 'user'@'127.0.0.1'; postfix operates in a jail as well and works around the jail issue in the same way but doesn't overwrite the specified host with a reverse dns lookup. Anyone have any suggestions on how to handle this issue better? or maybe there's a way to force different behavior which I haven't yet found in the documentation? Any help is much appreciated. Best Regards.

4 5

dovecot.index.log: duplicate transaction log sequence (3)
by mabi 02 Jul '19

02 Jul '19

Hello, I am running Dovecot 2.3.5.1 on OpenBSD 6.5 with RainLoop as IMAP webmail client and just noticed the following error messages about duplicate transaction log sequences in the index log: Jul 01 13:15:58 Error: imap(<REMOVED_EMAIL1>)<21324><TVSmwJyMd0C5D+Vb>: Transaction log /var/vmail/<REMOVED_DOMAIN>/<REMOVED_EMAIL1>/dovecot.index.log: duplicate transaction log sequence (3) Jul 02 16:33:35 Error: imap(<REMOVED_EMAIL2>)<6812><gn4yobOMJlW5D+Vb>: Transaction log /var/vmail/<REMOVED_DOMAIN>/<REMOVED_EMAIL2>/dovecot.list.index.log: duplicate transaction log sequence (2) Jul 02 16:33:35 Panic: imap(<REMOVED_EMAIL2>)<6812><gn4yobOMJlW5D+Vb>: file mail-index-write.c: line 137 (mail_index_write): assertion failed: (file->hdr.prev_file_seq == hdr->log_file_seq) Jul 02 16:33:35 Fatal: imap(<REMOVED_EMAIL2>)<6812><gn4yobOMJlW5D+Vb>: master: service(imap): child 6812 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service imap { drop_priv_before_exec=yes }) Could this problem occur because I am using a Linux NFS server to store all the mails mounted under /var/mail ? Any hints what I can do to avoid these error messages? Thank you in advance. Best regards, Mabi

2 4