- dovecot - dovecot.org

Non-standard socket locations w/ Dovecot + AWS Linux
by Antonio Leding 18 Jul '20

18 Jul '20

# === The post relates to Dovecot v2.2 running on AWS Linux v1 === # Hello all… The Dovecot sockets on this server are installed in two different locations one of which is different from what I have on my other Dovecot installations which run on Centos-7. Here are the sockets paths: — all sockets EXCEPT "auth-master” —> "/usr/local/var/run/dovecot” <<<<< this appears to be the default for this server — "auth-master” —> "/var/run/dovecot” <<<<< without this statement, Dovecot authentication always failed. The config stanza for this is shown below: service auth { unix_listener auth-userdb { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } } ============ The above has been working great for several years but the time eventually came where I needed to upgrade. This of course meant I had to move lots of maildata between the servers. Unfortunately, the “auth-userdb" config mentioned above prevented “dsync" from working properly. This is the error I received when trying “dsync”: Error: userdb lookup: connect(/usr/local/var/run/dovecot/auth-userdb) failed: No such file or directory This error led me to the eventual fix which was adding the following to the “dovecot.conf” file: auth_socket_path = /var/run/dovecot/auth-master ============ So, to my questions: (1) Why would the socket path on this AWS installation be different from what I see on my Centos-based Dovecot servers and also what I’ve read in several Dovecot mailer discussions? (2) Can the default socket path be set at compile time? If so, then I'm thinking maybe the AWS folks — for whatever reason — decided to install all sockets (except ”auth-master”) in the “/usr/local/var/run/dovecot” directory. Are there any benefits or reason to do this? (3) Is there any requirement that the “auth-master” socket be located in the “/var/run/dovecot” directory? Also, there is nothing else in that directory — just the “auth-master” socket file — that’s it. (4) Why is “dsync" looking for "auth-userdb" in the “/usr/local/var/run/dovecot” directory despite the “auth" stanza stating it is located elsewhere in "/var/run/dovecot”? (5) And last, why do I need to add the “auth_socket_path” statement to get “dsync” working even though the socket path is stated in the “auth" stanza? Thanks in advance for your time on this. I know this is mostly to help educate me on what is going on so I really appreciate your feedback…

1 0

Namespace issues & duplicate maiboxes
by Antonio Leding 18 Jul '20

18 Jul '20

Hello, I am seeing duplicate mailboxes when I perform the “doveadm mailbox list” command…the output is as follows: ================= INBOX INBOX.Drafts INBOX.Trash INBOX.Sent INBOX.INBOX INBOX.INBOX.Sent Messages INBOX.INBOX.Drafts INBOX.INBOX.Trash INBOX.INBOX.Deleted Messages ================= Here is namespace config that seems to have caused the above duplicates. Please help me understand what I’m doing wrong here…and also, not sure if this is relevant but the client is Apple Mail… ================= namespace inbox { type = private separator = . inbox = yes prefix = INBOX. mailbox Trash { auto = subscribe special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } }

2 2

Stuck here - help please
by Kishore Potnuru 18 Jul '20

18 Jul '20

Hi All, I have 2 test servers with the below configuration. ========================== Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1 ========================== Trying to create High Availability. I have added both of the above servers behind a F5 load balancer. I have got a Load Balancer FQDN "intl-dev-imaptest.testorg.com". I have enabled/opened the ports (25/110/143/993/995) on the above " intl-dev-imaptest.testorg.com". When I send 10 emails to "intl-dev-imaptest.testorg.com", then those 10 emails are getting distributed between the above 2 backend servers (5 emails to each server). I see those 5 emails each in both the servers. >From Outlook I have configured the email address using "POP and IMAP", when I gave the IMAP server as "intl-dev-imaptest.testorg.com" ,then it shows only 5 emails from server1 in outlook and after a few seconds/minutes, automatically it shows/refreshes the other 5 emails from server2. But I am not seeing all the 10 emails at the same time. why? So I tried the sync command. When I execute sync command like below from server1, it reflects the same emails in other server2 also. Then I see the same number of emails in both the servers. Is it not possible to access the both servers emails at one time with the "sync" command? Do we need to run this on all the email boxes on both servers? don't we miss/lose any emails during this sync process multiple times? "doveadm sync -f -u kishore(a)test.testorg.com remote:vmail@bal3200dev002.testorg.com" Is "replication" and "sync" are same? Why are we not able to see all the emails at one time without the "sync" command? What is the best and easiest way to create High Availability with just 2 servers, like emails should travel to both servers equally and if one server goes down also, another server should take care of the emails/functionality. This is my requirement. My current real time environment: I have around 10 email domains and each domain is having 10 imap emails. In total around 100 email boxes/addresses. We receive around 50K emails in a day to those email addresses. We are using the "Maildir" format in our environment. Want to move to the High Availability option with 2 servers. Please help me to fix the issue. Thanks & Regards, Kishore Potnuru

3 6

Outlook vs Thunderbird
by The Doctor 16 Jul '20

16 Jul '20

Got a client that usually uses Outlook I think 2010. This person tends to move their e-mails to certain folers. On Thunderbird, the move shows. Not on Outlook. Any explanation? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b A full cup must be carried steadily. -English proverb

12 22

Variable expansion in passwords
by lukn 16 Jul '20

16 Jul '20

Hello list A user reports failure to log in after password change. The client side error message indicates a lost or dropped connection by the server. A peek into the server logs reveales this: dovecot: imap(user(a)example.com)<53267><el0HoZGqHIdb0K2G>: Error: Failed to expand plugin setting plain_pass = 'asdf%?asdf': Unknown variable '%?' This looks a lot like a %-variable in the user provided password is tried to be expanded... Is this a bug or did I misconfigure something? output of dovecot -n is attached. regards lukn

1 0

NFS vs Replication
by Andrea Gabellini 16 Jul '20

16 Jul '20

Hello list, I built an email system using a proxy / director pair (IMAP, POP3, LMTP) and a backend pair. To have an HA system, I would like to understand if it is better to use an NFS export or replication to save emails and index files NFS is provided by a NAS (in HA), while for replication I would use the local backend disks Which of the two systems is more reliable? Are there any drawbacks for one or the other? Thanks, Andrea -- __________________________ Buy a Pentium 586/200 so you can reboot faster. __________________________ TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

5 8

Error in namespace config; how to move messages
by Antonio Leding 16 Jul '20

16 Jul '20

Hello, I inadvertently made an error re: the namespace prefix when setting up a few accounts and several messages have been saved in the Sent\Deleted folders under the incorrect namespace. Can I simply copy these messages to the relevant folder in the proper namespace? Or do I need to export\import these? Some other procedure? Thanks in advance for any feedback…

2 1

Massive alias / bulk delivery problem
by gnd 16 Jul '20

16 Jul '20

Hello list, we are experimenting with using Dovecot as part of a simplified mail stack with SQL for a internal messaging / notification system for our customers. Sometimes we need to send a message to thousands of customers at once and we do it by having aliases resolve to 10k and 20k+ mail accounts. When we send such a message the server load (obviously) is very high for a few minutes (in case of an alias containing 10k addresses its around 6-7 minutes for a 2 core machine with load around 20-30). Are there any optimizations or ways how to design the system around this problem ? Eg. is there a way how to deliver messages more slowly, and spread the load over longer time ? The stack is very simple with Postfix receiving the messages and Dovecot acting as a LMTP and IMAP server. Mailboxes are in the Maildir format on disk. Customers get the messages on login, a PHP script connects to the mail account associated with their ID via IMAP and sends unseen messages in the form of a JSON. Best regards, gnd/

5 6

doveadm quota question
by hfh＠cndns.com 15 Jul '20

15 Jul '20

I found that when the mailbox name contains special characters such as \x7f, when the doveadm quota recalc -u xxx command is executed, the messages under the mailbox name with special characters will not be counted. doveadm mailbox list -u xxx Actual mailbox name: doveadm quota recalc -u xxx, Mail under 'INBOX.Metaltex' will not be counted. hfh(a)cndns.com

1 0

dovecot 2.2.13
by Santhosh 14 Jul '20

14 Jul '20

all, below command not reporting the actual usage report on dovecot 2.2.13. please share your suggestion to how to fix this issue doveadm -f flow mailbox status -A -t 'messages vsize' '*' is just showing rkreddy messages=0 vsize=0 jcplho messages=0 vsize=0 planning messages=0 vsize=0 accounts messages=0 vsize=0 spam.notify messages=0 vsize=0 jsraju messages=0 vsize=0 amarnath messages=0 vsize=0 kamesh messages=0 vsize=0 moulivarma messages=0 vsize=0 test messages=0 vsize=0 electrical messages=0 vsize=0 subbarao messages=0 vsize=0 contracts messages=0 vsize=0 rrsrinivas messages=0 vsize=0 sralluri messages=0 vsize=0 jvgkraju messages=0 vsize=0 harikrishna messages=0 vsize=0 kvvnrao messages=0 vsize=0 chandrasekhar messages=0 vsize=0 admin messages=0 vsize=0 gsnraju messages=0 vsize=0 Thanks Kumar -- Sent from: http://dovecot.2317879.n4.nabble.com/

2 1

IMAP SEARCH over ALL mailboxes
by Filip Hanes 14 Jul '20

14 Jul '20

Hi, is it possible to SEARCH in dovecot IMAP over all messages in all mailboxes without selecting each mailbox?

2 2

Static users and doveadm
by Antonio Leding 14 Jul '20

14 Jul '20

Hello Dovecot users… I wanted to ask is using a static userdb will cause issues with some of the account and user related doveadm commands? If so, any suggestions on how to use doveadm in such a configuration? I have pasted both the cmd + error and userdb config below — Thanks in advance… sudo doveadm mailbox list -A Error: auth-master: userdb list: User listing returned failure doveadm: Error: Failed to iterate through some users userdb { args = uid=vmail gid=vmail home=/var/vmail allow_all_users=yes userdb_warning_disable=yes driver = static }

2 1

Apple Mail and subfolders
by Filip Hajný 14 Jul '20

14 Jul '20

Hi all, does anybody here use MacOS (Catalina) Mail, who can confirm that subfolders (i.e. folders inside folders) work for them? It seems that I cannot create/access Maildir subfolders at all. Subfolders created in Mail show up as '.folder\2esubfolder' on disk, suggesting that Apple Mail is URL-coding the dot separator before it passes it onto Dovecot. No such translation takes place when interpreting the IMAP tree though, resulting in subfolders rendered as plain entries with the dot separator preserved. Subfolders can be created from elsewhere (SoGO, Roundube, Thunderbird) just fine and work here just fine, suggesting that all is well in terms of Dovecot configuration. Subfolders created here though show up as a proper hierarchy in Apple Mail, but their contents is not displayed, so the user thinks the subfolder is empty. This definitely used to work fine in the past. Running 2.3.10.1 as part of the Mailcow suite. -F

5 7

Syncing emails from external server like Gmail
by Vitalii 14 Jul '20

14 Jul '20

Greeting I've managed to backup my emails from external email server via dsync and imapc: protocol like this: doveadm -Dv -o imapc_user='user(a)gmail.com' -o imapc_password="pass" -o imapc_host=imap.gmail.com backup -R -u duke(a)ejoom.com imapc: taken from https://wiki.dovecot.org/Migration/Dsync I wish to do regular syncing of 5min interval to substitute 'getmail' program. When I repeat the command It doesn't download all the attachments(!good) but It seems that at retrieve all the the GUIDs and UIDs(!bad) again that take quite long considering 30K emails. The question is how to speed it up and retrieve only new emails? Does anyone have a solution for regular synchronization? What is the best way? Logs look like this: https://gist.githubusercontent.com/vnagara/87e0da1b21b51f68fd74270b3ec653b3… It wrights that "Mailboxes are equal" but still verifies all the UIDs again. Thanks.

4 11

Fwd: Dsync mail migration from v2.2 --> v2.3
by Antonio Leding 14 Jul '20

14 Jul '20

Two items I forgot to mention in my initial post: (A) I am running the sync command on the new v2.3 server. (B) To get sync to work, I had to add the following to the old v2.2 server: auth_socket_path = /var/run/dovecot/auth-master I think this relates to what I said in my initial post about AWS linux installing all of the sockets into a non-standard location. I say this because when I was trying get this working but before I had added the above setting, I noticed the following message: Error: userdb lookup: connect(/usr/local/var/run/dovecot/auth-userdb) failed: No such file or directory This seemed to indicate that the old server was looking for the auth socket in the incorrect location. So, I decided to correct this with the setting I noted above. Please let me know if I had this correct or perhaps there is something else going on here… Thanks... > Begin forwarded message: > > From: Antonio Leding <tech(a)leding.net> > Subject: Dsync mail migration from v2.2 --> v2.3 > Date: July 13, 2020 at 8:45:18 PM PDT > To: dovecot(a)dovecot.org > > Hello all, > > I’ve been battling how to migrate my imap mail following a new server install that has Dovecot and Postfix upgrades. > > The research seems pretty clear that the preferred method is to use dsync to get the mail from Server-A to B. After several hours and several different combos, I think I might finally have this working. However, before committing to my procedure and running it against all mailboxes, I wanted to bounce this off of the community and get any feedback that might catch possible issues and\or offer some advice. > > Environment > > Old server: Dovecot 2.2.2 running on AWS linux 1 (I believe that is based on RHEL 4 or 5). > New server: Dovecot 2.3.10.1 running on CentOS 7.6. > All authentication is done by Dovecot against a mySQL (and Maria) database — nothing is in files. > All mail data and mailboxes are owned by a dedicated user “vmail” and I’m using a static userdb. > SSH is via public key file only — no PW based SSH is allowed. > SSH is on a non-standard port > > Operations > > I’ve decided to migrate one mailbox per command. I only have about 30 accounts on the server so this shoudn't be a huge deal. > Here is the command that I believe is good to go: > > sudo doveadm -Dv sync -u [ MBOX_TO_MIGRATE ] remote:vmail@[ SERVER ] > > The SERVER references a host stanza in root's SSH connection file: /root/.ssh/config > I need to use the config file because I (a) use a non-standard SSH port; (b) need to login as “vmail” ; (c) need to use the “vmail" identity file. > > Comments & notes > > The Dovecot 2.2 package for AWS Linux was apparently setup to install all of the sockets in /usr/local/var/run/dovecot. This must have caused authentication issues because to get it working properly, I then had to add "path = /var/run/dovecot/auth-master” statement to the “auth" stanza in dovecot.conf file. > Also, the fact that I do not use a “standard” SSH config was an issue early on but once I committed to allowing vmail to SSH into the old server, that part became moot. For security purposes, I will probably disable vmail SSH after the data is migrated. > > Questions > > First and foremost — any obvious issues here? > Next, any advice and\or lessons learned with this type of migration? > Finally, presuming this is the proper way to do this, will this migrate all mail content including Sent, Deleted, Drafts, etc.? > > > Thanks in advance for taking the time and providing any feedback — very much appreciated... > >

1 0

Dsync mail migration from v2.2 --> v2.3
by Antonio Leding 14 Jul '20

14 Jul '20

Hello all, I’ve been battling how to migrate my imap mail following a new server install that has Dovecot and Postfix upgrades. The research seems pretty clear that the preferred method is to use dsync to get the mail from Server-A to B. After several hours and several different combos, I think I might finally have this working. However, before committing to my procedure and running it against all mailboxes, I wanted to bounce this off of the community and get any feedback that might catch possible issues and\or offer some advice. Environment Old server: Dovecot 2.2.2 running on AWS linux 1 (I believe that is based on RHEL 4 or 5). New server: Dovecot 2.3.10.1 running on CentOS 7.6. All authentication is done by Dovecot against a mySQL (and Maria) database — nothing is in files. All mail data and mailboxes are owned by a dedicated user “vmail” and I’m using a static userdb. SSH is via public key file only — no PW based SSH is allowed. SSH is on a non-standard port Operations I’ve decided to migrate one mailbox per command. I only have about 30 accounts on the server so this shoudn't be a huge deal. Here is the command that I believe is good to go: sudo doveadm -Dv sync -u [ MBOX_TO_MIGRATE ] remote:vmail@[ SERVER ] The SERVER references a host stanza in root's SSH connection file: /root/.ssh/config I need to use the config file because I (a) use a non-standard SSH port; (b) need to login as “vmail” ; (c) need to use the “vmail" identity file. Comments & notes The Dovecot 2.2 package for AWS Linux was apparently setup to install all of the sockets in /usr/local/var/run/dovecot. This must have caused authentication issues because to get it working properly, I then had to add "path = /var/run/dovecot/auth-master” statement to the “auth" stanza in dovecot.conf file. Also, the fact that I do not use a “standard” SSH config was an issue early on but once I committed to allowing vmail to SSH into the old server, that part became moot. For security purposes, I will probably disable vmail SSH after the data is migrated. Questions First and foremost — any obvious issues here? Next, any advice and\or lessons learned with this type of migration? Finally, presuming this is the proper way to do this, will this migrate all mail content including Sent, Deleted, Drafts, etc.? Thanks in advance for taking the time and providing any feedback — very much appreciated...

1 0

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17
by Claudio Corvino 13 Jul '20

13 Jul '20

Hi Jochen, the ID has not changed, in addition the "permission denied" error is random, most of the time Dovecot works well. How can I check the mappings NFS uses? After the Debian upgrade I was using these NFS mount options: rw,user,rsize=8192,wsize=8192,timeo=30,intr Now trying to fix the problem I set "defaults" mount option, but nothing has changed. Thanks On 13/07/20 13:08, Jochen Bern wrote: > On 07/13/2020 12:57 PM, Claudio Corvino wrote: >> we just upgraded our mail server from Debian 8 to Debian 9, so our >> dovecot packages just got upgraded from version 2.2.13 to 2.2.17. > [...] >> Every directory and sub-dir under >> /mnt/mail-storage >> is assigned to vmail:vmail with >> drwx------ >> permission set. > Just a quick shot into the dark, you verified the ownerships on the NFS > *client*, not the NFS *server*, yes? Because NFS speaks UIDs and GIDs, > not their names, so if your Debian 9 installation assigned different IDs > to "vmail" ... > > (You might also want to check what mappings the NFS mount uses, > including possible *default* behaviour.) > > Good luck,

1 0

Dovecot permission denied errors on NFS after upgrade to 2.2.17
by Claudio Corvino 13 Jul '20

13 Jul '20

Hi everyone, we just upgraded our mail server from Debian 8 to Debian 9, so our dovecot packages just got upgraded from version 2.2.13 to 2.2.17. Now we have a lot of errors in our dovecot.log about permission denied (our Mailboxes are on NFS remote server since years without problems) like these: Jul 13 12:39:23 Error: imap(XXXXXXXXX): open(/mnt/mail-storage/XXXXXXXXX/Maildir/cur/1594378191.M653755P26498.ganimede,S=12716,W=12984:2,S) failed: Permission denied (euid=501(vmail) egid=501(vmail) missing +r perm: /mnt/mail-storage/XXXXXXXXX/Maildir/cur/1594378191.M653755P26498.ganimede,S=12716,W=12984:2,S stat(/mnt/mail-storage/XXXXXXXXX/Maildir/cur/1594378191.M653755P26498.ganimede,S=12716,W=12984:2,S) failed: Permission denied) For some user this is not a problem, for some other user this blocks their mail client (Thunderbird). We use vmail user for running Dovecot and I can't find a permission problem on the path indicated by the mail error, user vmail can read and write and uid and gid seems to be correct. Permissions on /mnt/mail-storage was drwx------ 94 vmail vmail 4096 ago 29 2019 mail-storage I just changed to drwxr-xr-x 94 root root 4096 ago 29 2019 mail-storage but nothing has changed. Every directory and sub-dir under /mnt/mail-storage is assigned to vmail:vmail with drwx------ permission set. If try to stat on /mnt/mail-storage/XXXXXXXXX/Maildir/cur/1594378191.M653755P26498.ganimede,S=12716,W=12984:2,S I get permission denied. We use LMTP and Postfix to deliver mail to mailbox. mail_debug=yes already enabled; mail_fsync is set to never (should I change to always?). Please could you give us help on the matter as I don't know where to look further. Thanks Claudio

1 0

Re: Please Help me
by Kishore Potnuru 13 Jul '20

13 Jul '20

Hi Vitalii, I am using "Maildir". Thanks Kishore Potnuru On Mon, Jul 13, 2020 at 10:32 AM Vitalii <vnagara(a)yandex.com> wrote: > On Sun, 12 Jul 2020 21:17:48 +0100 > Kishore Potnuru <kishore.reachme(a)gmail.com> wrote: > > > Hi All, > > > > I need to migrate the complete data & setup/environment from an old > > dovecot environment to a new dovecot environment. > > Hi Kishore, > I was wondering what mail format do you use Maildir/mdbox/sdbox? >

1 0

Please Help me
by Kishore Potnuru 13 Jul '20

13 Jul '20

Hi All, I need to migrate the complete data & setup/environment from an old dovecot environment to a new dovecot environment. Old environment details: ======================== Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6 New Environment details: ( 2 systems) ======================== Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1 In the new environment, I have 2 servers. I have got 2 of the above servers with above configuration and need to create HA/Resilience. I know there is advanced versions in Redhat and Dovecot. As per my organisation's existing support/policy, that is what maximum supported RHEL and official version of dovecot as per RHEL 7.7. Now my questions are: 1. I will stop the dovecot/postfix services on the server in old environment. Is it possible to move/copy the complete configuration along with data (directories/sub-directories/users/groups/existing email in new or cur folders/complete email domains along with complete structure) to the other 2 servers in new env? Could you please suggest me the commands or steps follow that? 2. Now, With the above 2 servers, I would like to create the HA/Resilience. I know there is a Replication options which are there. Could you please provide me the steps/video, how it needs to be done? I have got the systems and I need to move/copy the environment to a new environment and create the HA/Resilience. I am not sure, how to proceed and what needs to be done clearly? I am stuck here. Please help me in this step by step procedure. Thanks, Kishore Potnuru

3 2

INBOX folders disappeared after upgrading
by Dave 12 Jul '20

12 Jul '20

Hi, tried to Google/etc to see what to tweak.. not finding anything helpful. So.. I've been running my private mail through a Linux server since approx year 2000. The OS has been various flavors of Fedora or CentOS, since for work, I have to spend all day supporting some sort of Red Hat flavor. So I run SquirrelMail on top of Dovecot and Postfix on CentOS 7, things have been great for like forever. I recently ran updates and all my INBOX folders disappeared. I have made no configuration changes in at least 5 years. I can't seem to resolve/figure out what's going on. I have backups to see everything before the update. I've noticed that my subscriptions file is missing all the folders, which are all in this file in the backups. If I repopulate this file with the names, the next time I access mail, they are all removed. Most of my mail is in folders, therefore I have access to almost none of it (can see new stuff coming in, but can't sort it anywhere). k, for the details.. I was running dovecot-2.2.10 (2.2.10-8.el7.x86_64) and was updated to dovecot-2.2.36 (2.2.36-3.el7_7.1.x86_64) with yum updates. # dovecot --version 2.2.36 (1f10bfa63) # dovecot -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1062.18.1.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) # Hostname: vm1.tech...com auth_mechanisms = plain login login_greeting = IMAP ready. mail_location = maildir:~/Maildir 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 { driver = pam } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0600 user = postfix } } service imap-login { inet_listener imap { address = 127.0.0.1,68.139.25.150 } inet_listener imaps { address = 127.0.0.1,68.139.25.150 } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = 127.0.0.1,68.139.25.150 } } ssl = required ssl_cert = </etc/pki/tls/certs/mail.tech...com.crt ssl_cipher_list = ALL:!aNULL:!eNULL:!LOW:!EXP:!RC4 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = passwd } Regards, -Dave

2 4

2.3.10.1 on OpenBSD
by Rupert Gallagher 12 Jul '20

12 Jul '20

Apart from a few warnings (attached), and a bit of patience, the compiler terminates without error. On patience, OBSD has two processes who took almost half the CPU when compiling: reaper and zerothread. Will look into the warnings, and the testing errors (also attached). Let see how it works on this machine. OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 real mem = 17125511168 (16332MB) avail mem = 16593879040 (15825MB) bios0: Supermicro A2SDi-4C-HLN4F OpenBSD clang version 8.0.1 (tags/RELEASE_801/final) (based on LLVM 8.0.1) Target: amd64-unknown-openbsd6.7 Thread model: posix

3 6

Per-user sieve_before settings?
by Gionatan Danti 11 Jul '20

11 Jul '20

Hi all, I wonder if using a per-user sieve_before setting (ie: a relative path to user home, as ~/filter.sieve) is expected to work corretly. Full disclaimer: I am migrating an old CentOS 6.10 box with dovecot 2.0.9 and an old pigenhole version. I now want to redirect emails from old account to new account (I have a csv with old->new address pairs). My first approach using a single, big filter file somewhat works, but it is not optimal. I am currently setting sieve_before = /var/vmail/autoreply.sieve, and it that file I have something as: ... if header :contains "to" "aaa(a)olddomain.com" { redirect "aaa(a)newdomain.com"; stop; } if header :contains "to" "bbb(a)olddomain.com" { redirect "bbb(a)newdomain.com"; stop; } ... Problem is that whan an email has multiple to or cc, the filter is evaluated multiple times (one per recipient) and I end with multiple email copies on the same destination address. For example, sending and email to aaa(a)olddomain.com, cc bbb(a)olddomain.com is evaluated *two* times: when delivering the email to aaa(a)olddomain.com, with a corresponding redirect to aaa(a)newdomain.com, and when delivering the email to bbb(a)olddomain.com, with *another* redirect to aaa(a)newdomain.com (ending with two email copies). Using a per-user filter file solves the problem, as the filter is evaluated in the context of the right user only (ie: an email sent to aaa(a)olddomain.com, cc bbb(a)olddomain.com is evaluated only in aaa(a)olddomain.com context, with a corresponding single email on aaa(a)newdomain.com) However, I would avoid manipulating the already present per-user file (roundcube.sieve), as I need to add my custom rules on top of that file. Moreover, users would be able to disable the redirect filter. Using a per-user before_sieve filter file seems the right solution, *if* it works using multiple files rather than a single global one. If not, do you have any other suggestion/approach to share? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it [1] email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

1 1

antispam
by Matthew Broadhead 10 Jul '20

10 Jul '20

in dovecot/conf.d/90-plugin.conf i have plugin { # man antispam #setting_name = value antispam_debug_target = syslog antispam_verbose_debug = 1 antispam_backend = pipe antispam_signature = X-DSPAM-Signature # action to take on mails without signature # (used with any backend requiring a signature) # (we recommend only setting this to 'move' after verifying that the # whole setup is working) # antispam_signature_missing = move # move silently without training antispam_signature_missing = error antispam_trash = Trash antispam_spam = Junk antispam_pipe_program_spam_arg = --spam antispam_pipe_program_notspam_arg = --ham antispam_pipe_program = /usr/bin/sa-learn antispam_pipe_program_args = --username=%Lu } it seems to be going into the database ok but it doesn't seem to be applying anything it is learning. might there be some configuration option missing?

1 0

Ms Exchange vs dovecot
by Marc Roos 10 Jul '20

10 Jul '20

I have recently been working/testing with exchange 2016 and started thinking if I should even migrate to this platform. I assume more people here have experience with exchange and this idea. I was wondering if this is possible with a dovecot setup 1. public folder can be implemented with a public mailbox? 2. authorize users via groups access to mailboxes/folders of the public folder/mailbox. I think I saw ACL's with dovecot, does this compare to 'folder permissions' 3. is it possible with sieve to apply a rule on any mailbox/folder? Thus if I 'drag' a message to a folder, the sieve rule is activated?

18 25

Dovecot FTS with Solrcloud
by Patrik Peng 10 Jul '20

10 Jul '20

Greetings We are looking into a solution to set up full text search for our multiple Dovecot instances. According to the Dovecot Wiki, fts_solr is one of the recommended plugins to use. Since we have more than just a few hundred mailboxes, I guess one Solr instance will not suffice. So I took a look at SolrCloud and set up a small cluster with three nodes and shards. I have no preceding experience with Solr or SolrCloud and now it's not clear to me, how dovecot can interact with this cluster. Has anyone ever tried to setup dovecot FTS with a SolrCloud cluster and is willing to share his findings? Regards Patrik

1 0

BUG report: dbox movealt doesn't move reverse (to default location)
by Vitalii 09 Jul '20

09 Jul '20

Hi, Here is the problem that occured: #sudo doveadm -D altmove -u vv(a)vito.pp.ua all works properly and moves all storage to alt dir. However, to move it back to default storage I add '-r' by manual: #sudo doveadm -D altmove -u vv(a)vito.pp.ua -r all That seems behave like the original command ignoring '-r'. my dovecot conf: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 # Hostname: qemu7.internetguru.ca auth_mechanisms = plain login disable_plaintext_auth = no imapc_features = rfc822.size fetch-headers imapc_host = imap.gmail.com imapc_port = 993 imapc_ssl = imaps imapc_user = %u listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_attachment_dir = /wd640/mdbox-att/%d/%n mail_max_userip_connections = 100 mail_prefetch_count = 20 mail_privileged_group = vmail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { quota = dict:user::file:/var/vmail/%d/%n/.quotausage sieve = /var/vmail/%d/%n/.sieve sieve_max_redirects = 25 } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service imap-login { client_limit = 1000 process_limit = 512 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_cert = </etc/postfix/smtpd.cert 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 driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota postmaster_address = postmaster(a)some.ca } protocol lmtp { mail_plugins = quota sieve postmaster_address = postmaster(a)some.ca } I am using debian 10. P.S. I have not found much information about dbox attachments commands. Seems none needs them.

1 0

Urgent Help required
by Kishore Potnuru 09 Jul '20

09 Jul '20

Hi All, I request your help on this. I have 2 dovecot test servers (IMAP protocol) installed with the following configuration. ============= [root@devap01 ~]# cat /etc/redhat-* Red Hat Enterprise Linux Server release 6.10 (Santiago) [root@devap01 ~]# dovecot --version 2.0.9 [root@devap01 ~]# postconf | grep mail_version mail_version = 2.6.6 =============== I have another server also "devap02" with the same configuration. Couple of points/questions/queries here. 1. I know these servers are having old dovecot versions. I would like to upgrade to the latest versions. Could you please suggest the steps for upgrading to the latest version in redhat (step by step details are helpful please) . If I upgrade to the latest version, will there be any impact on the existing configuration/setup? 2. Now I have added these 2 servers behind the Load Balancer. Enabled 110/143 ports on the Load Balancer FQDN (test.pop3.testing.com) and opened the firewall ports. Here I configured IMAP settings from microsoft outlook to see the emails. I gave the Incoming Mail Server & Outgoing mail server as "test.pop3.testing.com". It is configured without errors in Outlook. But I see these 2 types issues (shared storage & individual storage) a) individual separate storage - When I send 10 emails to LB FQDN ( test.pop3.testing.com) the emails are going to 2 backend servers. But when i see the emails from Outlook inbox, it shows 5 emails from one server for some time. After sometime it shows other 5 emails in the inbox. But, I am not able to see all 10 emails at same time in my inbox. Please suggest how to fix this issue? In this scenario, I have separate individual storage in both the servers. b) common shared storage - I have tried a different scenario also. I also have one common NFS storage. So, I have configured that storage in both the servers. So when I sent 10 emails, I see all the 10 emails from both the servers as it is common shared storage. But, I am not getting those 10 emails delivered into my Outlook. I have made all the configuration correctly. Please suggest what is the mistake here. Dovecot.conf ========================================================= [root@devap01 ~]# cat /etc/dovecot/dovecot.conf disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.log mail_location = maildir:/r3/mail/virtual/%d/%n/Maildir/ passdb { args = /etc/dovecot/passwd driver = passwd-file } pop3_uidl_format = %g protocols = imap pop3 ssl = yes ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = uid=vmail gid=vmail home=/r3/mail/virtual/%d/%n driver = static } mail_debug = no verbose_ssl = no ========================================================= Please help me here. Thanks, Kishore Potnuru

9 15

Dovecot - Xoauth2 - keycloak
by la.jolie＠paquerette 09 Jul '20

09 Jul '20

Hello, Still trying to make roundcube / Dovecot works with Keycloak. Dovecot can't seem to validate the access_token that Roundcube gave. ----- Jul 08 20:48:05 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…] Sent header Jul 08 20:48:05 auth: Debug: http-client[1]: peer 11.22.33.44:443: No more requests to service for this peer (1 connections exist, 0 pending) Jul 08 20:48:05 auth: Debug: http-client[1]: conn 11.22.33.44:443 [0]: Got 404 response for request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…] (took 11 ms + 19 ms in queue) Jul 08 20:48:05 auth: Debug: oauth2(my.mail@whatever,::1,<Z2mDOfSpJJ8AAAAAAAAAAAAAAAAAAAAB>): oauth2: callback(0, Invalid token) ---- The access_token used by Dovecot is the right one. Dovecot also has the right login (my.mail@whatever) The Nginx and Keycloak logs show this: ---- - - [08/Jul/2020:23:25:18 +0200] "POST /auth/realms/test_saml/protocol/openid-connect/token HTTP/1.1" 200 3171 "-" "Guzzle/5.3.1 curl/7.64.0 PHP/7.3.14-1~deb10u1" - - [08/Jul/2020:23:42:05 +0200] "GET /auth/realms/test_saml/protocol/openid-connect/tokeneyJhbGciOiJFUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJEZzR2aWtndzN2MWVpQVgxMU10YkFIaXRaUnM2R2RlVzN3b3hGTTBpd1NnIn0.eyJleHAiOjE1OTQyNDE0NjUsImlhdCI6MTU5NDI0MTI4NSwiYXV0aF90aW1lIjoxNTk0MjM0ODI3LCJqdGkiOiI0NjRlZjc5NS0yZDYzLTQzYjktYjU4My1iYTY2MmFkMWRhYzUiLCJpc3MiOiJodHRwczovL3Nzby5udWJvLmNvb3AvYXV0aC9yZWFsbXMvdGVzdF9zYW1sIiwiYXVkIjoiYWNjb3VudCIsInN1YiI6IjhlZWNiODVjLTZlMDYtNGZhNC1iYTAwLTdlMGRlM2MyMWYxNCIsInR5cCI6IkJlYXJlciIsImF6cCI6InJvdW5kY3ViZSIsInNlc3Npb25fc3RhdGUiOiJmOTYyNWM3OS02OTM5LTRkZjEtOGM2Yi1hYWM5Y2EzYWJkY2YiLCJhY3IiOiIwIiwiYWxsb3dlZC1vcmlnaW5zIjpbImh0dHA6Ly9yYy5udWJvLmRvbWFpbmVwdWJsaWMubmV0Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIl19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiYWNjb3VudCI6eyJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJvcGVuaWQgbWljcm9wcm9maWxlLWp3dCBwcm9maWxlIGVtYWlsIG9mZmxpbmVfYWNjZXNzIiwidWlkIjoicXVlbmVubmkiLCJ1cG4iOiJxdWVuZW5uaSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwibmFtZSI6Iktlbm55IExvdXZlYXV4IExvdXZlYXV4IiwiZ3JvdXBzIjpbIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXSwicHJlZmVycmVkX3VzZXJuYW1lIjoicXVlbmVubmkiLCJnaXZlbl9uYW1lIjoiS2VubnkgTG91dmVhdXgiLCJmYW1pbHlfbmFtZSI6IkxvdXZlYXV4IiwiZW1haWwiOiJrZW5ueUBudWJvLnNpdGUifQ.TsUBiZ5nSTuA9ojr6bao5NQUHeNRmcYQZsC95rrhYca9FsFG4xG8mT53X9eOSNEqzRMJiPHaDuAh-3Bq8Rjdlg HTTP/1.1" 404 1465 "-" "dovecot-oauth2-passdb/2.3.4.1" DEBUG [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-2) RESTEASY002315: PathInfo: /realms/test_saml/protocol/openid-connect/tokeneyJhbGciOiJFUzI1N iIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJEZzR2aWtndzN2MWVpQVgxMU10YkFIaXRaUnM2R2RlVzN3b3hGTTBpd1NnIn0.eyJleHAiOjE1OTQyNDQ3MDQsImlhdCI6MTU5NDI0NDUyNCwiYXV0aF90aW1lIjoxNTk0MjQ0MzQ3LCJqdGk iOiIyYTg3MjQ3NS0zMGMxLTRmMDctODg5Ny04YmQ4OTJjMGI1MjEiLCJpc3MiOiJodHRwczovL3Nzby5udWJvLmNvb3AvYXV0aC9yZWFsbXMvdGVzdF9zYW1sIiwiYXVkIjoiYWNjb3VudCIsInN1YiI6IjhlZWNiODVjLTZlMDYtNGZhN C1iYTAwLTdlMGRlM2MyMWYxNCIsInR5cCI6IkJlYXJlciIsImF6cCI6InJvdW5kY3ViZSIsInNlc3Npb25fc3RhdGUiOiJmMjY0OTQyMy0xNmZkLTQzMTgtYTVkYy04NWJhNmU3YTQ4MWYiLCJhY3IiOiIwIiwiYWxsb3dlZC1vcmlnaW5 zIjpbImh0dHA6Ly9yYy5udWJvLmRvbWFpbmVwdWJsaWMubmV0Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIl19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiYWNjb3VudCI6e yJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJvcGVuaWQgbWljcm9wcm9maWxlLWp3dCBwcm9maWxlIGVtYWlsIG9mZmxpbmVfYWNjZXNzIiwidWl kIjoicXVlbmVubmkiLCJ1cG4iOiJxdWVuZW5uaSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwibmFtZSI6Iktlbm55IExvdXZlYXV4IExvdXZlYXV4IiwiZ3JvdXBzIjpbIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iX SwicHJlZmVycmVkX3VzZXJuYW1lIjoicXVlbmVubmkiLCJnaXZlbl9uYW1lIjoiS2VubnkgTG91dmVhdXgiLCJmYW1pbHlfbmFtZSI6IkxvdXZlYXV4IiwiZW1haWwiOiJrZW5ueUBudWJvLnNpdGUifQ.TsUBiZ5nSTuA9ojr6bao5NQUHe NRmcYQZsC95rrhYca9FsFG4xG8mT53X9eOSNEqzRMJiPHaDuAh-3Bq8Rjdlg --- Dovecot does a GET request where the access_token is directly attached to the 'tokeninfo_url' option. Is that the correct/normal way? Shouldn't it be a POST with data passed as params? Or is it Keycloak that should accept that request? Thanks Kenny

2 1

Re: Urgent Help required
by Kishore Potnuru 08 Jul '20

08 Jul '20

Hi, Our organisation has dependencies. There is a separate team/department who creates the servers for us. When they build a new RHEL system, the system will come up with various in-house softwares/tools. Those tools are not compatible as of now with RHEL8. So, our organisation is going with redhat 7.7 only as of today which is supported for all in-house tools also. This is my current situation: 1) I have 2 test servers which are loaded with the following configuration. ============= [root@devap01 ~]# cat /etc/redhat-* Red Hat Enterprise Linux Server release 6.10 (Santiago) [root@devap01 ~]# dovecot --version 2.0.9 [root@devap01 ~]# postconf | grep mail_version mail_version = 2.6.6 =============== So, I would like to install the max possible dovecot version on the above servers for the testing purpose. I would like to implement the HA/Resilience with those 2 servers. I have shared storage and individual storage in this environment. But I am seeing some issues with both of them ( I explained details in my first email thread). please see if you can help. 2) If it is successful, I will get two RHEL 7.7 servers to implement the same in LIVE environment for HA/Resilience. First I am going with compatibility issues to resolve in my environment. Once that is resolved, I will go with HA/Resilience implementation. Please let me know if you need any more details. Thanks & Regards, Kishore Potnuru On Wed, Jul 8, 2020 at 8:57 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > > >>> with broken or vulnerable software is there really a benefit? > >> > >> LTS distributions back port necessary patches > > >Then the OP should be able to update to a dovecot that doesn't have the > issue, right? > > I have no idea what his issue is, and why he is stuck even in specific > releases. I have been running dovecot on el6 and el7 for years and years > without issues. > > > > > > > >

2 1

RE: Urgent Help required
by Marc Roos 08 Jul '20

08 Jul '20

>>The other side of the question is, Why is the software always so "vulnerable" and "broken" in the first >>place as to be unsuitable for Long Term Support? >> >>If the software code worked when it was released some number of years ago, then why doesn't it still work >>the same way today as it it did when it was released? Whenever I hear people complain about computers and/or software. I always suggest them to use something like the abacus of 2000 bc. You should be glad for what they do for you ;) And since humans operate them, you will find annoyances as with doctors amputating the wrong limb.

1 0

Re: Urgent Help required
by Kishore Potnuru 08 Jul '20

08 Jul '20

Thank you for your reply. 1. Am i able to upgrade directly from 2.0 to 2.3? or I should go periodically from 2.0 to 2.1, then 2.1 to 2.2, then 2.2 to 2.3....? 2. could you please suggest me steps to pick the correct package to upgrade in the above version (2.1, 2.2, 2.3)? 3. which location i need to download the packages? 4. I am using redhat servers. Am i able to directly download and upgrade the software from my redhat linux server? please advise step-by-step instructions for this? Thanks, Kishore Potnuru On Wed, Jul 8, 2020 at 11:00 AM Apostolis Hardalias <a.hardalias(a)skroutz.gr> wrote: > > On 7/8/20 12:53 PM, Kishore Potnuru wrote: > > Hi All, > > > > I request your help on this. > > > > I have 2 dovecot test servers (IMAP protocol) installed with the > > following configuration. > > ============= > > [root@devap01 ~]# cat /etc/redhat-* > > Red Hat Enterprise Linux Server release 6.10 (Santiago) > > > > [root@devap01 ~]# dovecot --version > > 2.0.9 > > > > [root@devap01 ~]# postconf | grep mail_version > > mail_version = 2.6.6 > > =============== > > > > I have another server also "devap02" with the same configuration. > > > > Couple of points/questions/queries here. > > > > 1. I know these servers are having old dovecot versions. I would like > > to upgrade to the latest versions. Could you please suggest the steps > > for upgrading to the latest version in redhat (step by step details > > are helpful please) . If I upgrade to the latest version, will there > > be any impact on the existing configuration/setup? > > Check the documents posted here: > > https://doc.dovecot.org/installation_guide/upgrading/from-2.0-to-2.1/ > > https://doc.dovecot.org/installation_guide/upgrading/from-2.1-to-2.2/ > > https://doc.dovecot.org/installation_guide/upgrading/from-2.2-to-2.3/ > > Depending on your setup, you may also need to check for changes to > additional software (e.g. amavis) > > > > > 2. Now I have added these 2 servers behind the Load Balancer. Enabled > > 110/143 ports on the Load Balancer FQDN (test.pop3.testing.com > > <http://test.pop3.testing.com>) and opened the firewall ports. Here I > > configured IMAP settings from microsoft outlook to see the emails. I > > gave the Incoming Mail Server & Outgoing mail server as > > "test.pop3.testing.com <http://test.pop3.testing.com>". It is > > configured without errors in Outlook. But I see these 2 types issues > > (shared storage & individual storage) > > > > a) individual separate storage - When I send 10 emails to LB FQDN > > (test.pop3.testing.com <http://test.pop3.testing.com>), the emails are > > going to 2 backend servers. But when i see the emails from Outlook > > inbox, it shows 5 emails from one server for some time. After sometime > > it shows other 5 emails in the inbox. But, I am not able to see all 10 > > emails at same time in my inbox. Please suggest how to fix this issue? > > In this scenario, I have separate individual storage in both the servers. > > I'm not sure if you've set it up already because it's unclear from the > configuration you posted but, you may wanna have a look at: > https://wiki.dovecot.org/Replication > > I suggest using replication after you've upgraded since earlier versions > of dovecot had a few issues. > > > > b) common shared storage - I have tried a different scenario also. > > I also have one common NFS storage. So, I have configured that storage > > in both the servers. So when I sent 10 emails, I see all the 10 emails > > from both the servers as it is common shared storage. But, I am not > > getting those 10 emails delivered into my Outlook. I have made all the > > configuration correctly. Please suggest what is the mistake here. > > > > Dovecot.conf > > ========================================================= > > > > [root@devap01 ~]# cat /etc/dovecot/dovecot.conf > > disable_plaintext_auth = no > > > > listen = * > > log_path = /var/log/dovecot.log > > mail_location = maildir:/r3/mail/virtual/%d/%n/Maildir/ > > passdb { > > args = /etc/dovecot/passwd > > driver = passwd-file > > } > > pop3_uidl_format = %g > > protocols = imap pop3 > > ssl = yes > > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > > ssl_key = </etc/pki/dovecot/private/dovecot.pem > > > > userdb { > > args = uid=vmail gid=vmail home=/r3/mail/virtual/%d/%n > > driver = static > > } > > mail_debug = no > > verbose_ssl = no > > ========================================================= > > > > Please help me here. > > > > Thanks, > > Kishore Potnuru >

1 1

Dovecot Maildirs multi language
by Luca Müller 07 Jul '20

07 Jul '20

Hello, I'm hosting a few customers on a dovecot Server. Most users speak german and have german as their main language. I configured the IMAP Foldernames in a Dovecot configuration file like this: ##### root@srv04:~# cat /etc/dovecot/conf.d/105-mailboxes.conf imap_capability = +XLIST namespace inbox { inbox = yes location = separator = / mailbox "Entwürfe" { auto = subscribe special_use = \Drafts auto=subscribe } mailbox Junk-E-Mail { special_use = \Junk auto=subscribe } mailbox "Gelöschte Elemente" { special_use = \Trash auto=subscribe } mailbox "Gesendete Elemente" { special_use = \Sent auto=subscribe } mailbox Archive { special_use = \Archive auto=subscribe } } ##### Dovecot Version: 2.3.10 (0da0eff44) ##### Is it possible to change this configuration for specific users or to provide multi language support somehow? Thanks in advance. Best regards, Luca

4 4

dovecot oauth
by la.jolie＠paquerette 06 Jul '20

06 Jul '20

Hello, I'm trying to configure roundcube / dovecot to work with keycloak. I activated xoauth2 oauthbearer in dovecot. But a problem occurs when dovecot tries to contact the keycloak server (logs are below). My problem looks like this one: https://dovecot.org/pipermail/dovecot/2019-December/117768.html The response to this problem was about a bug in oauth driver (https://dovecot.org/pipermail/dovecot/2019-December/117787.html) Mizuki was using Dovecot v2.2.36 (1f10bfa63) I have Dovecot Dovecot v2.3.4.1 (f79e8e7e4) I'm wondering if this bug is still present in my version or if I have another problem. Both my servers (dovecot and keycloak) are using let's encrypt certificates. I tried to configure Keycloak with nginx proxy and without it (access via port 8443) (in case the problem came from the ssl config on the keycloak server), but still the same error. If the bug is fixed, then could someone tell me what do I have to put in the option tls_ca_cert_file? I tried with /etc/letsencrypt/live/my.host/chain.pem and also certs I got from let's encrypt website (https://letsencrypt.org/certificates/ / tried ISRG Root X1 (self-signed) & Let’s Encrypt Authority X3 (IdenTrust cross-signed) & Let’s Encrypt Authority X3 (Signed by ISRG Root X1)) But I always have the same error. Thanks, Kenny My configs: - I'm on a Debian Buster with Dovecot / postfix / roundcube - dovecot -n : --- # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-5-cloud-amd64 x86_64 Debian 10.4 auth_debug = yes auth_mechanisms = xoauth2 oauthbearer login auth_verbose = yes debug_log_path = /var/log/dovecot-debug.log first_valid_gid = 10000 first_valid_uid = 10000 info_log_path = /var/log/dovecot.log last_valid_gid = 20000 last_valid_uid = 20000 lda_mailbox_autocreate = yes log_path = /var/log/dovecot.log mail_debug = yes mail_gid = mail mail_location = maildir:~/Maildir mail_privileged_group = mail 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-ldap.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-oauth2.conf.ext driver = oauth2 mechanisms = xoauth2 oauthbearer } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0600 user = postfix } unix_listener auth-master { mode = 0600 user = mail } unix_listener auth-userdb { mode = 0600 user = mail } } service stats { unix_listener stats-reader { mode = 0600 user = mail } unix_listener stats-writer { mode = 0600 user = mail } } ssl_cert = </etc/letsencrypt/live/my.host/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 ssl_prefer_server_ciphers = yes ssl_require_crl = no userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = gid=mail home=/var/mail/%u driver = static } verbose_ssl = yes protocol lda { info_log_path = /var/log/dovecot-deliver.log log_path = /var/log/dovecot-deliver-errors.log } ------ - dovecot-oauth2.conf.ext ----- tokeninfo_url = https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/token introspection_mode = post introspection_url = https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke… username_attribute = email tls_ca_cert_file = /etc/letsencrypt/live/my.host/chain.pem #tls_ca_cert_file = /etc/ssl/certs/letsencrypt.pem #active_attribute = enableMail #active_value = TRUE debug = yes rawlog_dir = /tmp/oauth2 ----- * Logs: ------- Jul 04 17:00:12 auth: Debug: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2: Making token validation lookup to https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/token Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Host created Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Host session created Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: IPs have expired; need to refresh DNS lookup Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Performing asynchronous DNS lookup Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Submitted (requests left=1) Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: DNS lookup successful; got 1 IPs Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14 (shared): Peer created Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14: Peer pool created Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Peer created Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Setting up connection to 151.62.56.14 (SSL=my.keycloak.host) (1 requests pending) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Linked queue https://my.keycloak.host (1 queues linked) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Started new connection to 151.62.56.14 (SSL=my.keycloak.host) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Creating 1 new connections to handle requests (already 0 usable, connecting to 0, closing 0) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Making new connection 1 of 1 (0 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Connecting Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Waiting for connect (fd=22) to finish for max 0 msecs Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: HTTPS connection created (1 parallel connections exist) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Client connected (fd=22) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connected Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Starting SSL handshake Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x10, ret=1: before SSL initialization Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: before SSL initialization Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server certificate Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server key exchange Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server done Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client key exchange Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write change cipher spec Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished ==> dovecot.log <== Jul 04 17:00:12 auth: Info: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 ==> dovecot-debug.log <== Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read change cipher spec Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x20, ret=1: SSL negotiation finished successfully Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=1: SSL negotiation finished successfully Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Connection failed (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14: Failed to make connection (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Failed to establish any connection within our peer pool: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Failed to set up connection to 151.62.56.14 (SSL=my.keycloak.host): SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (1 peers pending, 1 requests pending) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Failed to set up any connection; failing all queued requests Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Unlinked queue https://my.keycloak.host (0 queues linked) Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Error: 9003 SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Dropping request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)] Jul 04 17:00:12 auth: Debug: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2: callback(-1, SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3) ==> dovecot.log <== Jul 04 17:00:12 auth: Error: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2 failed: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 ==> dovecot-debug.log <== Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Destroy (requests left=1) Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Free (requests left=0) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection close Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection disconnect Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Disconnected: Connection closed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (fd=22) Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Detached peer Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection destroy -------

2 4

export of information about mail into csv
by Marcel Blenkers 05 Jul '20

05 Jul '20

3 3

Quota: How/where to set/change
by Frank Elsner 03 Jul '20

03 Jul '20

Hi experts. in the output of imapsync I found: Host2: found quota, presented in raw IMAP Sending: 7 GETQUOTAROOT INBOX Sent 22 bytes Read: * QUOTAROOT INBOX "User quota" * QUOTA "User quota" (STORAGE 420325 1953125) 7 OK Getquotaroot completed (0.001 + 0.000 secs). Host2: Quota current storage is 430412800 bytes. Limit is 2000000000 bytes. So 21.52 % full Host2 is under my control and running dovecot-2.3.10.1. I need to increase the quota above 2 GB but don't know where it comes from and therefor don't know what to do. This is the doveconf -a: | # 2.3.10.1 (a3d0e1171): /usr/local/dovecot/etc/dovecot/dovecot.conf | # OS: Linux 5.7.6-201.fc32.x86_64 x86_64 Fedora release 32 (Thirty Two) ext3 | # Hostname: christo.fritz.box | # NOTE: Send doveconf -n output instead when asking for help. | auth_anonymous_username = anonymous | auth_cache_negative_ttl = 1 hours | auth_cache_size = 0 | auth_cache_ttl = 1 hours | auth_cache_verify_password_with_worker = no | auth_debug = no | auth_debug_passwords = no | auth_default_realm = | auth_failure_delay = 2 secs | auth_gssapi_hostname = | auth_krb5_keytab = | auth_master_user_separator = | auth_mechanisms = plain login | auth_policy_check_after_auth = yes | auth_policy_check_before_auth = yes | auth_policy_hash_mech = sha256 | auth_policy_hash_nonce = | auth_policy_hash_truncate = 12 | auth_policy_log_only = no | auth_policy_reject_on_fail = no | auth_policy_report_after_auth = yes | auth_policy_request_attributes = login=%{requested_username} pwhash=%{hashed_password} remote=%{rip} device_id=%{client_id} protocol=%s | auth_policy_server_api_header = | auth_policy_server_timeout_msecs = 2000 | auth_policy_server_url = | auth_proxy_self = | auth_realms = | auth_socket_path = auth-userdb | auth_ssl_require_client_cert = no | auth_ssl_username_from_cert = no | auth_stats = no | auth_use_winbind = no | auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ | auth_username_format = %Lu | auth_username_translation = | auth_verbose = no | auth_verbose_passwords = no | auth_winbind_helper_path = /usr/bin/ntlm_auth | auth_worker_max_count = 30 | base_dir = /var/run/dovecot | config_cache_size = 1 M | debug_log_path = | default_client_limit = 1024 | default_idle_kill = 1 mins | default_internal_group = dovecot | default_internal_user = dovecot | default_login_user = dovenull | default_process_limit = 256 | default_vsz_limit = 512 M | deliver_log_format = msgid=%m: %$ | dict_db_config = | director_flush_socket = | director_mail_servers = | director_max_parallel_kicks = 100 | director_max_parallel_moves = 100 | director_output_buffer_size = 10 M | director_ping_idle_timeout = 30 secs | director_ping_max_timeout = 1 mins | director_servers = | director_user_expire = 15 mins | director_user_kick_delay = 2 secs | director_username_hash = %Lu | disable_plaintext_auth = yes | dotlock_use_excl = yes | doveadm_allowed_commands = | doveadm_api_key = | doveadm_http_rawlog_dir = | doveadm_password = | doveadm_port = 0 | doveadm_socket_path = doveadm-server | doveadm_ssl = no | doveadm_username = doveadm | doveadm_worker_count = 0 | dsync_alt_char = _ | dsync_commit_msgs_interval = 100 | dsync_features = | dsync_hashed_headers = Date Message-ID | dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -U | first_valid_gid = 1 | first_valid_uid = 200 | haproxy_timeout = 3 secs | haproxy_trusted_networks = | hostname = | imap_capability = | imap_client_workarounds = | imap_fetch_failure = disconnect-immediately | imap_hibernate_timeout = 0 | imap_id_log = | imap_id_retain = no | imap_id_send = name * | imap_idle_notify_interval = 2 mins | imap_literal_minus = no | imap_logout_format = in=%i out=%o deleted=%{deleted} expunged=%{expunged} trashed=%{trashed} hdr_count=%{fetch_hdr_count} hdr_bytes=%{fetch_hdr_bytes} body_count=%{fetch_body_count} body_bytes=%{fetch_body_bytes} | imap_max_line_length = 64 k | imap_metadata = no | imap_urlauth_host = | imap_urlauth_logout_format = in=%i out=%o | imap_urlauth_port = 143 | imapc_cmd_timeout = 5 mins | imapc_connection_retry_count = 1 | imapc_connection_retry_interval = 1 secs | imapc_features = | imapc_host = | imapc_list_prefix = | imapc_master_user = | imapc_max_idle_time = 29 mins | imapc_max_line_length = 0 | imapc_password = | imapc_port = 143 | imapc_rawlog_dir = | imapc_sasl_mechanisms = | imapc_ssl = no | imapc_ssl_verify = yes | imapc_user = | import_environment = TZ CORE_OUTOFMEM CORE_ERROR | info_log_path = | instance_name = dovecot | last_valid_gid = 0 | last_valid_uid = 65534 | lda_mailbox_autocreate = no | lda_mailbox_autosubscribe = no | lda_original_recipient_header = | libexec_dir = /usr/local/dovecot/libexec/dovecot | listen = * | lmtp_add_received_header = yes | lmtp_client_workarounds = | lmtp_hdr_delivery_address = final | lmtp_proxy = no | lmtp_proxy_rawlog_dir = | lmtp_rawlog_dir = | lmtp_rcpt_check_quota = no | lmtp_save_to_detail_mailbox = yes | lmtp_user_concurrency_limit = 0 | lock_method = fcntl | log_core_filter = | log_debug = | log_path = syslog | log_timestamp = "%b %d %H:%M:%S " | login_access_sockets = | login_greeting = m28a.ddns.net - IMAPs Service (dovecot) ready. | login_log_format = %$: %s | login_log_format_elements = %u %r %c | login_plugin_dir = /usr/local/dovecot/lib/dovecot/login | login_plugins = | login_proxy_max_disconnect_delay = 0 | login_proxy_notify_path = proxy-notify | login_source_ips = | login_trusted_networks = | mail_access_groups = | mail_always_cache_fields = | mail_attachment_detection_options = | mail_attachment_dir = | mail_attachment_fs = sis posix | mail_attachment_hash = %{sha1} | mail_attachment_min_size = 128 k | mail_attribute_dict = | mail_cache_compress_continued_percentage = 200 | mail_cache_compress_delete_percentage = 20 | mail_cache_compress_header_continue_count = 4 | mail_cache_compress_min_size = 32 k | mail_cache_fields = flags | mail_cache_min_mail_count = 0 | mail_cache_record_max_size = 64 k | mail_cache_unaccessed_field_drop = 30 days | mail_chroot = | mail_debug = no | mail_fsync = optimized | mail_full_filesystem_access = no | mail_gid = | mail_home = | mail_index_log2_max_age = 2 days | mail_index_log_rotate_max_size = 1 M | mail_index_log_rotate_min_age = 5 mins | mail_index_log_rotate_min_size = 32 k | mail_index_rewrite_max_log_bytes = 128 k | mail_index_rewrite_min_log_bytes = 8 k | mail_location = maildir:/var/spool/mail/%u:LAYOUT=fs | mail_log_prefix = "%Us(%u,%r): " | mail_max_keyword_length = 50 | mail_max_lock_timeout = 0 | mail_max_userip_connections = 10 | mail_never_cache_fields = imap.envelope | mail_nfs_index = no | mail_nfs_storage = no | mail_plugin_dir = /usr/dovecot/lib/dovecot/ | mail_plugins = notify quota fts fts_squat acl | mail_prefetch_count = 0 | mail_privileged_group = | mail_save_crlf = no | mail_server_admin = | mail_server_comment = | mail_shared_explicit_inbox = no | mail_sort_max_read_count = 0 | mail_temp_dir = /tmp | mail_temp_scan_interval = 1 weeks | mail_uid = | mail_vsize_bg_after_count = 0 | mailbox_idle_check_interval = 30 secs | mailbox_list_index = yes | mailbox_list_index_include_inbox = no | mailbox_list_index_very_dirty_syncs = no | maildir_broken_filename_sizes = no | maildir_copy_with_hardlinks = yes | maildir_empty_new = no | maildir_stat_dirs = no | maildir_very_dirty_syncs = no | master_user_separator = | mbox_dirty_syncs = yes | mbox_dotlock_change_timeout = 2 mins | mbox_lazy_writes = yes | mbox_lock_timeout = 5 mins | mbox_md5 = apop3d | mbox_min_index_size = 0 | mbox_read_locks = fcntl | mbox_very_dirty_syncs = no | mbox_write_locks = dotlock fcntl | mdbox_preallocate_space = no | mdbox_rotate_interval = 0 | mdbox_rotate_size = 10 M | mmap_disable = no | namespace inbox { | disabled = no | hidden = no | ignore_on_failure = no | inbox = yes | list = yes | location = | mailbox Drafts { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Drafts | } | mailbox Gesendet { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Sent | } | mailbox SPAM { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Junk | } | mailbox Sent { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Sent | } | mailbox Trash { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Trash | } | order = 0 | prefix = | separator = | subscriptions = yes | type = private | } | old_stats_carbon_interval = 30 secs | old_stats_carbon_name = | old_stats_carbon_server = | old_stats_command_min_time = 1 mins | old_stats_domain_min_time = 12 hours | old_stats_ip_min_time = 12 hours | old_stats_memory_limit = 16 M | old_stats_session_min_time = 15 mins | old_stats_user_min_time = 1 hours | passdb { | args = dovecot | auth_verbose = default | default_fields = | deny = no | driver = pam | master = no | mechanisms = | name = | override_fields = | pass = no | result_failure = continue | result_internalfail = continue | result_success = return-ok | skip = never | username_filter = | } | plugin { | fts = squat | fts_squat = partial=4 full=10 | mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append | mail_log_fields = uid box from subject msgid size flags | mail_log_group_events = yes | quota = maildir:User quota | quota_rule = ?:storage=5G | quota_rule2 = Trash:storage=+100M | } | pop3_client_workarounds = | pop3_delete_type = default | pop3_deleted_flag = | pop3_enable_last = no | pop3_fast_size_lookups = no | pop3_lock_session = no | pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s | pop3_no_flag_updates = no | pop3_reuse_xuidl = no | pop3_save_uidl = no | pop3_uidl_duplicates = allow | pop3_uidl_format = %08Xu%08Xv | pop3c_features = | pop3c_host = | pop3c_master_user = | pop3c_password = | pop3c_port = 110 | pop3c_quick_received_date = no | pop3c_rawlog_dir = | pop3c_ssl = no | pop3c_ssl_verify = yes | pop3c_user = %u | postmaster_address = mailonator(a)mailbox.org | protocols = imap | quota_full_tempfail = no | rawlog_dir = | recipient_delimiter = + | rejection_reason = Your message to <%t> was automatically rejected:%n%r | rejection_subject = Rejected: %s | replication_dsync_parameters = -d -N -l 30 -U | replication_full_sync_interval = 1 days | replication_max_conns = 10 | replicator_host = replicator | replicator_port = 0 | sendmail_path = /usr/sbin/sendmail | service aggregator { | chroot = . | client_limit = 0 | drop_priv_before_exec = no | executable = aggregator | extra_groups = | fifo_listener replication-notify-fifo { | group = | mode = 0600 | user = | } | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener replication-notify { | group = | mode = 0600 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service anvil { | chroot = empty | client_limit = 1024 | drop_priv_before_exec = no | executable = anvil | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 1 | protocol = | service_count = 0 | type = anvil | unix_listener anvil-auth-penalty { | group = | mode = 0600 | user = | } | unix_listener anvil { | group = | mode = 0600 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service auth-worker { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = auth -w | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 1 | type = | unix_listener auth-worker { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service auth { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = auth | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener auth-client { | group = exim | mode = 0660 | user = exim | } | unix_listener auth-login { | group = | mode = 0600 | user = $default_internal_user | } | unix_listener auth-master { | group = | mode = 0600 | user = | } | unix_listener auth-userdb { | group = | mode = 0666 | user = $default_internal_user | } | unix_listener login/login { | group = | mode = 0666 | user = | } | unix_listener token-login/tokenlogin { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service config { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = config | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = config | unix_listener config { | group = | mode = 0600 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service dict-async { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = dict | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener dict-async { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service dict { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = dict | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener dict { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service director { | chroot = . | client_limit = 0 | drop_priv_before_exec = no | executable = director | extra_groups = | fifo_listener login/proxy-notify { | group = | mode = 00 | user = | } | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener director-admin { | group = | mode = 0600 | user = | } | unix_listener login/director { | group = | mode = 00 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service dns_client { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = dns-client | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener dns-client { | group = | mode = 0666 | user = | } | unix_listener login/dns-client { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service doveadm { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = doveadm-server | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 1 | type = | unix_listener doveadm-server { | group = | mode = 0600 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service health-check { | chroot = | client_limit = 1 | drop_priv_before_exec = yes | executable = script -p health-check.sh | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service imap-hibernate { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = imap-hibernate | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = imap | service_count = 0 | type = | unix_listener imap-hibernate { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service imap-login { | chroot = login | client_limit = 0 | drop_priv_before_exec = no | executable = imap-login | extra_groups = | group = | idle_kill = 0 | inet_listener imap { | address = | haproxy = no | port = 143 | reuse_port = no | ssl = no | } | inet_listener imaps { | address = | haproxy = no | port = 993 | reuse_port = no | ssl = yes | } | privileged_group = | process_limit = 512 | process_min_avail = 3 | protocol = imap | service_count = 1 | type = login | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service imap-postlogin { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = script-login /usr/local/sbin/dovecot-imap-post-login | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | user = | vsz_limit = 18446744073709551615 B | } | service imap-urlauth-login { | chroot = token-login | client_limit = 0 | drop_priv_before_exec = no | executable = imap-urlauth-login | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = login | unix_listener imap-urlauth { | group = | mode = 0666 | user = | } | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service imap-urlauth-worker { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = imap-urlauth-worker | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 1024 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = | unix_listener imap-urlauth-worker { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service imap-urlauth { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = imap-urlauth | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1024 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = | unix_listener token-login/imap-urlauth { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service imap { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = imap | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 128 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = | unix_listener imap-master { | group = | mode = 0600 | user = | } | unix_listener login/imap { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service indexer-worker { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = indexer-worker | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 10 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener indexer-worker { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service indexer { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = indexer | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener indexer { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service ipc { | chroot = empty | client_limit = 0 | drop_priv_before_exec = no | executable = ipc | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener ipc { | group = | mode = 0600 | user = $default_internal_user | } | unix_listener login/ipc-proxy { | group = | mode = 0600 | user = $default_login_user | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service lmtp { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = lmtp | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = lmtp | service_count = 0 | type = | unix_listener lmtp { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service log { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = log | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = log | unix_listener log-errors { | group = | mode = 0600 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service old-stats { | chroot = empty | client_limit = 0 | drop_priv_before_exec = no | executable = old-stats | extra_groups = | fifo_listener old-stats-mail { | group = | mode = 0600 | user = | } | fifo_listener old-stats-user { | group = | mode = 0600 | user = | } | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener old-stats { | group = | mode = 0600 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service pop3-login { | chroot = login | client_limit = 0 | drop_priv_before_exec = no | executable = pop3-login | extra_groups = | group = | idle_kill = 0 | inet_listener pop3 { | address = | haproxy = no | port = 110 | reuse_port = no | ssl = no | } | inet_listener pop3s { | address = | haproxy = no | port = 995 | reuse_port = no | ssl = yes | } | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = pop3 | service_count = 1 | type = login | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service pop3 { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = pop3 | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 128 | process_min_avail = 0 | protocol = pop3 | service_count = 1 | type = | unix_listener login/pop3 { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service replicator { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = replicator | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener replicator-doveadm { | group = | mode = 00 | user = $default_internal_user | } | unix_listener replicator { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service stats { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = stats | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener stats-reader { | group = | mode = 0600 | user = | } | unix_listener stats-writer { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service submission-login { | chroot = login | client_limit = 0 | drop_priv_before_exec = no | executable = submission-login | extra_groups = | group = | idle_kill = 0 | inet_listener submission { | address = | haproxy = no | port = 587 | reuse_port = no | ssl = no | } | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = submission | service_count = 1 | type = login | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service submission { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = submission | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 1024 | process_min_avail = 0 | protocol = submission | service_count = 1 | type = | unix_listener login/submission { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | shutdown_clients = yes | ssl = yes | ssl_alt_cert = | ssl_alt_key = | ssl_ca = | ssl_cert = </usr/local/etc/Certs/m28a.crt | ssl_cert_username_field = commonName | ssl_cipher_list = ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH | ssl_client_ca_dir = | ssl_client_ca_file = | ssl_client_cert = | ssl_client_key = | ssl_client_require_valid_cert = yes | ssl_crypto_device = | ssl_curve_list = | ssl_dh = # hidden, use -P to show it | ssl_key = # hidden, use -P to show it | ssl_key_password = | ssl_min_protocol = TLSv1 | ssl_options = | ssl_prefer_server_ciphers = no | ssl_require_crl = yes | ssl_verify_client_cert = no | state_dir = /var/lib/dovecot | stats_writer_socket_path = stats-writer | submission_client_workarounds = | submission_host = | submission_logout_format = in=%i out=%o | submission_max_mail_size = 0 | submission_max_recipients = 0 | submission_relay_command_timeout = 5 mins | submission_relay_connect_timeout = 30 secs | submission_relay_host = | submission_relay_master_user = | submission_relay_max_idle_time = 29 mins | submission_relay_password = | submission_relay_port = 25 | submission_relay_rawlog_dir = | submission_relay_ssl = no | submission_relay_ssl_verify = yes | submission_relay_trusted = no | submission_relay_user = | submission_ssl = no | submission_timeout = 30 secs | syslog_facility = mail | userdb { | args = | auth_verbose = default | default_fields = | driver = passwd | name = | override_fields = | result_failure = continue | result_internalfail = continue | result_success = return-ok | skip = never | } | valid_chroot_dirs = | verbose_proctitle = yes | verbose_ssl = no | version_ignore = no | protocol lmtp { | mail_plugins = notify quota fts fts_squat acl | } | protocol lda { | mail_plugins = notify quota fts fts_squat acl | } | protocol imap { | imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags | imap_id_log = * | imap_logout_format = [%i/%o] | mail_max_userip_connections = 0 | mail_plugins = notify quota fts fts_squat acl quota imap_quota listescape fts fts_squat | } The config may be sub-optimal. Please concentrate on my quota problem. Stay healthy, Frank Elsner

1 0

Mail replication fails between v2.2.27 and v2.3.4.1
by Apostolis Hardalias 03 Jul '20

03 Jul '20

Hello, I have two installations of dovecot configured to replicate mailboxes between them. recently, i upgraded the operating system on one of them (mx2.example.com) and now i'm running one installation on version 2.2.27 (debian stretch) and another on version 2.3.4.1 (mx1.example.com debian buster). My setup includes 3 shared namespaces that point to the mailboxes of 3 accounts. these accounts are setup to use maildir format. After upgrading one of the hosts, i started having issues with failed replications on those mailboxes. I tried running the replication manually and repeatedly by issuing the following on mx1.example.com: doveadv -d sync -u exception_bucket(a)example.com -d -l 30 -n -u and the logs on mx2.example.com included the following lines consistently: Jul 02 14:21:58 dsync-server(exception_bucket(a)example.com): Debug: brain S: Change during sync: Mailbox GUID 2d32711ddfd27250390e0000a712b6e3 was lost Jul 02 14:21:58 dsync-server(exception_bucket(a)example.com): Debug: brain S: We don't have mailbox 2d32711ddfd27250390e0000a712b6e3 I double checked for the existance of the mailbox with that guid (that guid points to the inbox) and the mailbox existed on both servers but, the contents of the mailbox on the two servers where different (missing e-mails on both servers). I attempted running a force-resync command as follows but with no luck. doveadm -d force-resync -u exception_bucket(a)example.com inbox but the issue persisted. admittedly, i didn't run the command on both servers because i read it doesn't replicate after figuring a workaround. The next thing i tried was attempting replication without the -n flag, given that you mention that there are some issues replicating shared namespaces. That didn't fix the replication status either. After looking around, i came onto the solution on this thread: https://dovecot.org/pipermail/dovecot/2017-october/109620.html which proposed setting mailbox_list_index = no. This was the default setting on version 2.2.27, so i changed that setting on mx2.example.com which was running version 2.3.4.1. This allowed the replication to work but i don't think it is a setting i want in my configuration. Is there something i can do to re-enable dovecot to check index files instead of mailboxes? Could that be an issue when replicating between those two different versions? I'm attaching the configuration files for both the mailservers, a separate configuration file is included since mail_replica settings are set from there, and a link to the compressed log file i pulled during the operation. https://filebin.net/d9yygnq8jg74unwb/replication_debug.log.bz2?t=vv2o81ka Thank you in advance, Apostolis Hardalias

1 0

local stanza only generated for IPv6
by Jeremy Ardley 02 Jul '20

02 Jul '20

I have a mail server with multiple IP addresses and associated DNS names In the dovecot configuration I have a listen directive: listen = mail.example.com.com,mail.otherexample.com,localhost Multiple local stanzas are of the form: local mail.example.com { protocol imap { ssl_cert = </etc/letsencrypt/live/mail.example.com/fullchain.pem ssl_key = </etc/letsencrypt/live/mail.example.com/privkey.pem service imaps_login { inet_listener imaps { address=mail.example.com } inet_listener imap { address=mail.example.com } } } } mail.example.com has IPv4 and IPv6 addresses in DNS When I run doveconf -n the local configuration is only generated for the IPv6 address. I can test the operation on IPv6 using openSSL and see different server certificates on different IP addresses as expected. How do I force local generation for both IPv4 and IPv6 ?

3 4

dovecot: doveconf: Fatal: block_alloc(134217728): Out of memory
by Brent Clark 30 Jun '20

30 Jun '20

Good day Guys Currently on Debian Stretch (2.2.27). This morning we enabled SNI for our clients (file per domain). On going live with the new server configuration, we started getting the following on our shared hosting servers. Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: doveconf: Fatal: block_alloc(134217728): Out of memory Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: config: Fatal: block_alloc(134217728): Out of memory Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: config: Fatal: master: service(config): child 64008 returned error 83 (Out of memory (service config { vsz_limit=512 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) Jun 30 07:25:34 REMOVED_HOSTNAME dovecot: doveconf: Panic: data stack: Out of memory when allocating 2147483688 bytes Jun 30 07:25:37 REMOVED_HOSTNAME dovecot: config: Panic: data stack: Out of memory when allocating 2147483688 bytes This is a server with 2414 domains. On a few of our servers, to buy time, we had to set: default_vsz_limit =10096M A question I would like to ask is. Based on the following change notice, could the following be the problem. https://dovecot.org/pipermail/dovecot-news/2019-July/000412.html - config: Memory leak in config process when ssl_dh setting wasn't set and there was no ssl-parameters.dat file. This caused config process to die once in a while with "out of memory". If anyone could provide any assistance or share a tip on where we can look it would be appreciated. This one has my team and I stumped. Kind regards Brent Clark

1 0

POP3Deleted flag issues
by Justina Colmena ~biz 29 Jun '20

29 Jun '20

Hello, I have been running my own mail server with Dovecot, Postfix, and Cyrus-SASL for authentication. = dovecot22u.x86_64 1:2.2.36.4-1.el7.ius @ius I am basically trying to tune the system for better performance. The flat files "/var/mail/justina" etc exhibit locking issues and conflicts when fetching mail at the same time new mail is being delivered by Postfix. Other mail is stored in "Maildir" type folders accessible via IMAP. These exhibit better performance with finer grained locking. There's an "idea" that was posted to the list 7 years ago, shows up top rank on Google. https://dovecot.org/pipermail/dovecot/2013-May/090114.html I fear either an incomplete implementation of the feature or "here-be-dragons" code that may or may not be completely documented. I would like all the "$POP3Deleted" mail to be moved to an "Archive" Maildir folder accessible via IMAP. How do I accomplish this? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0

layout:fs info
by Stefano Gatto - Fly2Net sas 29 Jun '20

29 Jun '20

Hi all, my dovecot version is 2.2.13, quite standard configuration. Can I add directive LAYOUT=fs in dovecot configuration without losing all my archived messages? This should modify the separator of email folders from dots to slashes, correct? BR Stefano

2 2

Plugin ABI compat between v2.3.8 and v2.3.9
by Alexander Strasser 24 Jun '20

24 Jun '20

Hi all! This is my first post on this list. Please pardon me if I overlooked or misunderstood some things. I had some imap crashes (sig11) starting at the end of 2019 after an upgrade of dovecot. I found out, that I didn't have any problems using version v2.3.8, but any version v2.3.9 and higher would trigger the crashes. After investigating more deeply and creating a core dump, I saw that the crash happened in an external plugin fetchmail_wakeup[1]. After recompiling that plugin with up to date dovecot headers, I didn't get crashes anymore. So I suspect there were ABI incompatible changes and it was forgotten to bump the minimum Plugin-ABI version supported. I could try to follow up some more details, but it would be quite a burden because of rebuilding the plugin with debug symbols against version 2.3.8 of dovecot and triggering the crash etc. Despite that I think it should be possible to detect changes that are ABI incompatible, as otherwise plugin users would always have to find out first hand with unknown consequences. That said there could be a possibility of the plugin using the API/ABI in an invalid way. If that was the cause, then the plugin should be changed. Hope this report turns out to help improve the situation. I don't have problems currently and will in future be sensitive to this specific possible cause of problems, but not having such crashes in the first place, would be worth it and maybe could still help others. Best regards, Alexander 1: slightly reduced version of: https://github.com/marschap/fetchmail_wakeup

2 4

Converting dot-namespaced Maildir to /-namespaced
by Guido Goluke, MajorLabel 24 Jun '20

24 Jun '20

I have a couple of domains on my server, all of them namespaced with a dot. It's 10-15 mailboxes at the most. Is there good way to convert them to / (slash) namespaced folders? Maybe some bash script lying around somewhere?

1 0

dovecot fts configuration without solr
by Danilo Tomasoni 24 Jun '20

24 Jun '20

Hello All, I always used dovecot and I'm pretty happy with it, but recently I changed OS (to ubuntu 18) and to get dovecot LTS with lucene (the default I was using on my previous arch installation) I needed to build from source the version 2.3.10 (the one that came with the repos was older and clucene was not actually supported) The problem is that the Clucene is not behaving well, It indexes only some mails but definitely not all according to my tests (there are also strange assertion errors in the logs) I also tried xapian fts index but is very slow indexing and definitely doesn't seem to work. The problem with solr fts is that solr doesn't even start on my tiny system (odroid C2 with 2GB RAM) and anyway I don't want to bloat all the system for the indexing if possible.. Anyone can suggest me a proper minimal and working configuration? Thank you Danilo

2 2

JMAP support
by Martynas Bendorius 23 Jun '20

23 Jun '20

Hello, Is there any ETA set for JMAP support? Thank you! >> On 11/27/2016 5:28 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> Hi! >> We are working on including JMAP support to Dovecot. At this moment I cannot give any promise for exact version, but hopefully it will be part of v2.3 >> >> Aki Tuomi >> Dovecot Oy -- Best regards, Martynas Bendorius

3 2

Apple mail works but thunderbird unable to connect
by Dshah 23 Jun '20

23 Jun '20

Dear all, I am stuck on this issue for days, I am able to connect on my IMAP server using Apple mail client but thunderbird shows me this error: "improper command pipelining after EHLO" I have tried all the ports in manual config but it just is not working while Apple Mail is able to connect perfectly, here are my configuration details of "postconf -n" , "doveconf -n" and " master.cf" https://pastebin.com/M3XG9DXA Thanks in advance.

6 12

problem with warnings
by Maciej Milaszewski 23 Jun '20

23 Jun '20

Hi I have a problem with warrnings in log Yesterday "big gays" change datastore and After this time i get warrnings in dovecot like: Warning: Created dotlock file's timestamp is different than current time (1592878268 vs 1592871191): /vmail/us/username/Maildir/dovecot-uidlist Before that there was no problem with warnnings I have dovecot director with 5 dovecot-nodes and storage always was mounted via nfs /vmail on /vmail type nfs (rw,noexec,noatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=120,acregmax=120,acdirmin=120,acdirmax=120,hard,nocto,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.100.41,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=xxx.xxx.xxx.xxx) # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.rc1 (debaa297) # OS: Linux 3.16.0-10-amd64 x86_64 Debian 8.11

1 0

from field encoding
by Jan Jurko 23 Jun '20

23 Jun '20

Good day. I have a dovecot 2.3.4.1 on debian 10 as an imap server. I found there are emails where the header field From has no encoding even if there is a name with special characters like Žlutý Kůň. The header looks like: From: "Žlutý Kůň" <zluty.kun(a)domain.tld> In this case the email client - roundcube, outlook etc. will show the From with wrong characters. This behaviour is typical only for dovecot, not for courier-imap - it was installed before dovecot with no problems. If there is corretly encoded From filed, the client shows the From correctly. Is there a way to set up the dovecot to show the field correctly even without encoding stuff? Some default/fallback settings? Thank you very much for your help Jan Jurko

2 3

nodelay passdb extra field does not work?
by Joe Wong 23 Jun '20

23 Jun '20

Hello, I have added 'y' as nodelay in my passdb query and I see the following in log: dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay does it mean this option is no longer supported in 2.3.10 ? - Joe

2 4

AW: replicator: Panic: data stack: Out of memory
by Thomas Tsiakalakis 23 Jun '20

23 Jun '20

I managed to convince the System that I really want a core dump Thomas Tsiakalakis Team Applikationsbetrieb GDV Dienstleistungs-GmbH Tel: +49(40)33449-4318 Fax: E-Mail: Thomas.Tsiakalakis(a)gdv-dl.de<mailto:Thomas.Tsiakalakis@gdv-dl.de> GDV Dienstleistungs-GmbH Glockengießerwall 1 D-20095 Hamburg www.gdv-dl.de<http://www.gdv-dl.de> Niederlassungen: Wilhelmstraße 43 / 43 G 10117 Berlin Frankenstraße 18 20097 Hamburg Sitz und Registergericht: Hamburg HRB 145291 USt.-IdNr : DE 205183123 Geschäftsführer: Dr. Jens Bartenwerfer Fred di Giuseppe Chiachiarella Aufsichtsratsvorsitzender: Werner Schmidt ------------------------------------------------------------------ Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe der E-Mail ist nicht gestattet. This e-mail and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Von: Thomas Tsiakalakis Gesendet: Donnerstag, 18. Juni 2020 16:26 An: 'dovecot(a)dovecot.org' <dovecot(a)dovecot.org> Betreff: replicator: Panic: data stack: Out of memory Hi, I have set up 2 SLES 15 Hosts with dovecot and replication. Everything seems to work fine but every time a message is delivered, I get an out of memory error in the logs. The Replication itself seems to work fine though. I increased default_vsz_limit to 512M but the only thing that changed was that dovecot was trying to allocate 1073741864 bytes instead of 268435496 As I said, I’m running SLES 15 SP1 and Dovecot 2.3.10 (0da0eff44) (both Hosts have the same version) Each Host currently has 8GB of Memory. # free -h total used free shared buff/cache available Mem: 7.8Gi 278Mi 7.3Gi 47Mi 183Mi 7.2Gi Swap: 4.0Gi 0B 4.0Gi # journalctl -f Jun 18 15:55:48 mail1 postfix/pickup[3457]: 18533C009C8: uid=0 from=<root> Jun 18 15:55:48 mail1 postfix/cleanup[3669]: 18533C009C8: message-id=<20200618135548.18533C009C8@mail1> Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: from=<root@mail1>, size=431, nrcpt=1 (queue active) Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Connect from local Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f8346d6d262] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f8346d6d37e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebcee) [0x7f8346d77cee] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebd91) [0x7f8346d77d91] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8346cd1f8b] -> /usr/lib64/dovecot/libdovecot.so.0(t_pop_last_unsafe+0) [0x7f8346d73660] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe7a50) [0x7f8346d73a50] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10eb58) [0x7f8346d9ab58] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe3ac5) [0x7f8346d6fac5] -> /usr/lib64/dovecot/libdovecot.so.0(buffer_write+0xf2) [0x7f8346d6fdb2] -> dovecot/replicator(replicator_queue_push+0xde) [0x5648989a5cde] -> dovecot/replicator(+0x5464) [0x5648989a5464] -> dovecot/replicator(+0x4a0b) [0x5648989a4a0b] -> dovecot/replicator(+0x4c02) [0x5648989a4c02] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f8346d90c99] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x134) [0x7f8346d92574] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f8346d90d9c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f8346d90fc8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f8346d01873] -> dovecot/replicator(main+0x1a0) [0x5648989a3cb0] -> /lib64/libc.so.6(__libc_start_main+0xea) [0x7f83468f534a] -> dovecot/replicator(_start+0x2a) [0x5648989a3d5a] Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Sync failure: Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Remote sent invalid input: - Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: msgid=<20200618135548.18533C009C8@mail1>: saved mail to INBOX Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Disconnect from local: Client has quit the connection (state=READY) Jun 18 15:55:48 mail1 postfix/lmtp[3672]: 18533C009C8: to=<test(a)example.com>, orig_to=<test(a)domain.com>, relay=mail1[private/dovecot-lmtp], delay=0.17, delays=0.02/0.01/0.02/0.13, dsn=2.0.0, status=sent (250 2.0.0 <test(a)example.com> q5sLCGRy615ZDgAATn/NZw Saved) Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: removed Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Fatal: master: service(replicator): child 2948 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2)

1 0