- dovecot - dovecot.org

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