- dovecot - dovecot.org

feature request: doveadm purge taking guid argument
by Marc 18 Mar '21

18 Mar '21

Hi Timo, What about giving doveadm purge an argument to delete a specific message guid? Is that a lot of work?

1 0

Some questions about code in lib-storage/index/maildir
by songliny 18 Mar '21

18 Mar '21

Hi, Recently, I have read some code in dovecot 2.3.13. And I have 2 questions about some lines of code in lib-storage/index/maildir Firstly, in the function, maildir_scan_dir, from lib-storage/index/maildir/maildir-sync.c around line 575 (https://github.com/dovecot/core/blob/6986a435e31dfe5bcd14985534b76b3c735f78…) I would like to know that after successfully stat the cur directory, does it assign the max value between st.st_mtime and start_time intensionally to new_check_time? Or maybe should it assign the value to the cur_check_time. if (stat(ctx->cur_dir, &st) == 0) { ctx->mbox->maildir_hdr.new_check_time = I_MAX(st.st_mtime, start_time); ctx->mbox->maildir_hdr.cur_mtime = st.st_mtime; ctx->mbox->maildir_hdr.cur_mtime_nsecs = ST_MTIME_NSEC(st); } Secondly, in the function, maildir_uidlist_sync_next_uid, from lib-storage/index/maildir/maildir-uidlist.c (https://github.com/dovecot/core/blob/6986a435e31dfe5bcd14985534b76b3c735f78… rc/lib-storage/index/maildir/maildir-uidlist.c#L1760) Is it ok to remove MAILDIR_UIDLIST_REC_FLAG_NEW_DIR flag from the record for the record that is not found in ctx->files just like the behavior (https://github.com/dovecot/core/blob/6986a435e31dfe5bcd14985534b76b3c735f78… the function, maildir_uidlist_sync_next_partial (https://github.com/dovecot/core/blob/6986a435e31dfe5bcd14985534b76b3c735f78…) from the same file? I think when it gets to the function, maildir_uidlist_sync_next_uid, the mail file have already been moved to cur directory. And maybe it is ok to remove MAILDIR_UIDLIST_REC_FLAG_NEW_DIR flag from the record. That is, is it ok to add this line rec->flags &= ENUM_NEGATE(MAILDIR_UIDLIST_REC_FLAG_NEW_DIR); just before rec->flags = (rec->flags | flags) & ENUM_NEGATE(MAILDIR_UIDLIST_REC_FLAG_NONSYNCED); in maildir_uidlist_sync_next_uid? Thank you in advance to he lp me get more understanding to these questions, Sony

1 0

dovecot director and keepalived
by Steven Varco 18 Mar '21

18 Mar '21

Hi All I’m trying to establish a dovecot HA setup with two loadbalancers, running keepalived for sharing a virtual public IP. On the same machines I’m running a dovecot director which proxies the requests to two underlying mail servers (on seperate machines). Now I’m hitting the issue with the way director determines his „Self IP“ by trying to bind to all configured director_servers IPs, taking the first one possible. However this approach only works, when the sysctl setting is: net.ipv4.ip_nonlocal_bind=0 On the other side keepalived needs net.ipv4.ip_nonlocal_bind=1 in order to bind the VIP. The last topic on that is dating back to 2016 (https://dovecot.org/pipermail/dovecot/2016-August/105191.html) with references to 2012 (https://www.dovecot.org/list/dovecot/2012-November/087033.html) and no solution posted so far. After five more years :D, I’m asking myself if we finally have a solution for that, or if my approach of achieving clustered director servers is potentially wrong? Other possible solutions I could think about: - Configure each director as „independent“ by setting only one IP in director_servers. => With this aporach you would loose the user to mailserver mapping, although only in a a case of a failover on the loadbalancer, which might can be neglected (or are there any other fallbacks?) - Only have director running on the currently active loadblancer node and stopped on the passive loadblancer node (would possibly have the same effects as above). - Putting director on seperated intermediate machines and proxing the requests through haproxy on the keepalived servers (keepalived -> haproxy -> director -> IMAP => Besides the disadvantage of having another bunch of servers in the chain, also some special configuration on the directory servers might be neccessary to assure director works neatly with haproxy. So 2021, what is the „correct“ (best practive) way of having a reduntant HA setup for dovecot? This means a MUA connects to one public IP and gets connected to (preferably the same) IMAP Server, no matter which machine in the whole chain might be down? PS: Using just multiple A records on the mail domain name (round-robin), while working perfectly for SMTP is not accepatbl for IMAP IMHO, as in case of a failure every second request from the client (MUA) would fail and most MUAs are not automatially reconnecting again in that case. thanks, Steven -- https://steven.varco.ch/

7 10

best practice purging only moved messages
by Marc 18 Mar '21

18 Mar '21

If I move a message from the 'inbox' namespace to my 'archive' namespace. The message is expunged at the 'inbox' namespace and added to the 'archive' namespace. What is the best way to only purge messages that have been moved. (I do not want to purge emails that have been deleted yet)

1 0

How can I migrate mailboxes after changing hierarchy separator?
by Popkornium18 17 Mar '21

17 Mar '21

Hi, I had a common problem (folders can't contain dots) and the obvious solution seems to be changing the hierarchy separator and using the listescape plugin. My question is: Do I need to take any extra steps after changing the separator to migrate my existing mailboxes? If so, which? I tried just simply renaming the folders and doing a `doveadm force-resync` but that did not work as intended. Afterwards I wasn't able to subscribe to any of my folders, so I guess that isn't the way to go. Kind regards Simon

1 0

inconsistency in reporting from mdbox_deleted
by Marc 17 Mar '21

17 Mar '21

This reports all folders, ok [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' '*' 2011 messages=0 vsize=0 2012 messages=0 vsize=0 2013 messages=0 vsize=0 2014 messages=0 vsize=0 2015 messages=0 vsize=0 2016 messages=0 vsize=0 2017 messages=0 vsize=0 2018 messages=0 vsize=0 2019 messages=0 vsize=0 doveadm(testtest): Error: Mailbox Archive: Failed to lookup mailbox status: Mailbox doesn't exist: Archive INBOX messages=15 vsize=12066832 This gets folder INBOX, ok [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' 'INBOX' INBOX messages=15 vsize=12066832 This reports error that a folder does not exist, ok [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' 'asdfasdfasdfasdf' doveadm(testtest): Error: Mailbox asdfasdfasdfasdf: Failed to lookup mailbox status: Mailbox doesn't exist: asdfasdfasdfasdf This query for Archive/2012 reports same as for 2012(?), by design, I guess ok [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' 'Archive/2012' Archive/2012 messages=0 vsize=0 This reports 0?, This should either report the folder does not exist, or it should report the same as getting the INBOX, like previous result [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' 'Archive/INBOX' Archive/INBOX messages=0 vsize=0

1 0

feature request: prevent linking of email
by Marc 17 Mar '21

17 Mar '21

What I have been doing wrong with testing expunged emails, is working with linked copies of emails. Although thunderbird copies the message, it looks like the message is NOT copied but linked. If I drag 3 emails from my desktop to a folder INBOX/test4 and copy 1 message from INBOX to INBOX/test4. I have 4 messages in this folder. I now shift+del this folder. The expunged messages listing gives me the expected 3 messages doveadm -o mail_location=mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index mailbox status -u testtest 'messages vsize' '*' Sent messages=0 vsize=0 Drafts messages=0 vsize=0 INBOX/test2 messages=0 vsize=0 Junk messages=0 vsize=0 Trash messages=0 vsize=0 test3 messages=0 vsize=0 test1 messages=0 vsize=0 RESTORED messages=0 vsize=0 INBOX messages=3 vsize=18079344 Lets recover these: doveadm -v import -u testtest 'mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index' RESTORED ALL Now I have 3 messages back, as expected. From an end users perspective if you delete a folder with 4 emails, you want your restored backup to have 4 emails, not 3 because one is already somewhere else in your folder/mailbox structure. The reason for copying an email to a different folder is that it is important. You do not want to loose it, and you want to be able to find it there. It is wrong to assume that a user will notice that these emails are missing and should look for them elsewhere. Say you have folder for a court case, and you copy emails there relevant for the court case. How can you ever know after a restore that a few email are missing from the folder, and which ones. I think it is bad this email is currently 'lost'. I rather have an option in dovecot that disables this hidden 'deduplication' feature. I think this should be the default setting also. This current deduplication feature also is hazardous because if this one copy of the email gets corrupted on the storage, you have no copies left. That is exactly the opposite of what user wants to accomplish with creating a copy. Feature request: disable this automatic linking of emails between mailboxes. Feature request: set this as a default.

2 3

Ability to put dovecot version in received header
by Kamil Jońca 17 Mar '21

17 Mar '21

I know that some time ago there was a discussion and this is conscious decision to remove dovecot version from headers during lmtp delievery. But is it possible to restore it as an option? -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html

3 3

Latest dovecot does not work with latest MUA (thunderbird)
by lja＠koti 17 Mar '21

17 Mar '21

Hi, Latest dovecot does not work with latest thunderbird. It does not react to sent emails. They are put to maildir by postfix a-ok. The version of thunderbird that works ok: 68.12.1 Distro: Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal $ dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.9.0-rc5 x86_64 Ubuntu 20.04.2 LTS # Hostname: superman.sillywalk.org auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot-debug.log info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_debug = yes 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 } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = mail mode = 0660 user = postfix } } ssl_cert = </etc/letsencrypt/live/lja.fi/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol imap { imap_metadata = yes } local_name paxsudos.fi { ssl_cert = </etc/letsencrypt/live/somethingB.fi/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it } local_name paxsudos.com { ssl_cert = </etc/letsencrypt/live/somethingB.com/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it } local_name lja.fi { ssl_cert = </etc/letsencrypt/live/somethingA.fi/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it } -- <https://paxsudos.com/> ,-- Information -------------------------------------------------------- ------ --- -- - | Lauri Jakku | Contact: | Phone: +358 40 220 3910 | Address: Puusepänkatu 1 A 3, 90130 Oulu, Finland '--------------- -------- ----- ----- ------- ---- --- -- Firmani, Paxsudos IT, kautta olen jättämässä oman, vaikka pienen, jäljen ympäristötekoina, että tulevaisuudessakin voimme nauttia luonnosta. Ympäristö ja luonto on sellaista joita otamme itsestäänselvyyksinä, tuon takia on käymässä niin että havahdumme kun on tilanne erittäin huono. We offset our carbon footprint via Ecologi <https://ecologi.com/paxsudosit> ,-- Virus scan done for content -------------------------------------------------------- ------ --- -- - | Known viruses: 10722370 | Engine version: 0.102.4 | Scanned directories: 0 | Scanned files: 1 | Infected files: 0 | Data scanned: 0.01 MB | Data read: 0.01 MB (ratio 1.00:1) | Time: 16.864 sec (0 m 16 s) '--------------- -------- ----- ----- ------- ---- --- --

5 9

feature request: doveadm -Dv purge
by Marc 17 Mar '21

17 Mar '21

Maybe list emails being purged

1 0