- dovecot - dovecot.org

Authentication problems due to file ownership issue.
by C. Petro 12 Oct '21

12 Oct '21

I am getting: Oct 03 20:19:52 auth: Error: net_connect_unix(auth-worker) in directory /run/dovecot failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +r perm: /run/dovecot/auth-worker, dir owned by 0:0 mode=0755) Because: root@mailserver:/run/dovecot# ls -l auth-worker srw------- 1 dovecot root 0 Oct 3 20:09 auth-worker When it really needs to be "vmail" (I think). I have set: service auth-worker { # Auth worker process is run as root by default, so that it can access # /etc/shadow. If this isn't necessary, the user should be changed to # $default_internal_user. user = vmail group = vmail } in 10-master.conf (because I'm using postfixadmin/mariadb to store user information, I don't *want* access to /etc/shadow) I set this about an hour ago, then applied some security patches and restarted (ubuntu 20.04 system) and it didn't change. I then manually did a "chown vmail: of that file, and I got further. I had a different problem that I resolved, and then restarted dovecot, and /run/dovecot/auth-worker reverted. I'm not sure where I need to set this. Thanks. Petro. :wq

2 2

haproxy config manual update for multiple ports
by Marc 09 Oct '21

09 Oct '21

https://wiki2.dovecot.org/HAProxy Maybe update this to having multiple ports (if this is even possible) frontend ft_imap bind :110 << bind :143 mode tcp default_backend bk_imap backend bk_imap mode tcp balance leastconn stick store-request src stick-table type ip size 200k expire 30m server s1 backend.example.com:10143 send-proxy-v2 <<< how to put more ports here?

3 7

SNI via lookup?
by Felipe Gasper 08 Oct '21

08 Oct '21

Hello, How (if at all) might I configure a Dovecot server to read its SNI configuration dynamically? Right now I’ve got thousands of domains all served from a quite-large static config file that has to be rebuilt every time a domain is added or removed. It would be much simpler if there were a way to make Dovecot call out to some external service to fetch a given domain’s certificate. Thank you in advance! cheers, -Felipe Gasper

3 5

writing Maildir subscriptions file outside of dovecot
by David Mandelberg 08 Oct '21

08 Oct '21

Hi, Is it safe to write to the Maildir subscriptions file directly? I'm trying to figure out a way to make sure the subscriptions match the actual folders exactly. I know how to subscribe to existing mailboxes with `doveadm mailbox list` and `doveadm mailbox subscribe`, but the latter seems to only accept mailboxes on the command line, and any local user can see the command line of any other user's commands. Also, that doesn't handle unsubscribing from non-existent mailboxes. I think unsubscribing from any mailboxes listed in `doveadm mailbox list -s` but not in `doveadm mailbox list` would work, but it has the same issue of mailboxes on the command line. It looks like I could do what I want with something like this command, but I'm not sure if it's safe to write directly to the subscriptions file: { echo INBOX; ls -1A | grep '^\.' | cut -c 2-; } > subscriptions (I was also thinking about using `doveadm mailbox list` to write the subscriptions file directly, but it looks like they use different separators and encodings.)

2 2

reconsidering my (your?) current setup
by Marc 07 Oct '21

07 Oct '21

With redhat 'dumping' the support for centos and the availability of containers. I thought about reconsidering my default dovecot setup. Since the concept of having a lts distribution that is supported by redhat/centos is more or less 'unavailable'. I thought about using the repo of dovecot with centos8stream. os == For now I stick with centos8stream, just because the rest is still on centos7 support and the ceph development team is using it as a default. (And can't yet let go of the idea this closest to professional distro ;)) auth uid gid os =============== I am not really convinced that storing users in mysql/postgres is a better alternative than having linux do auth. I also think it is good to have mailbox files stored with different uid's (no idea if this is even the case when dovecot is using mysql/maria/postgres) Normally I would use a synced ldap server on the vm for authentication. But I was thinking of using now an external ldap task from the container environment. To de-duplicate services/data and make the environment simple. Since rh is moving to a different ldap server, it would be good to have this seperated in the future. New to me is the sssd, used nscd/nslcd for decades without issues. I guess the best solution is to have the os uid/gid coming from sssd, configure sssd to have a huge timeout if the backend ldap auth is not available. What is your thought about this? auth uid gid dovecot ==================== I do not really have an idea if I should have dovecot use ldap directly or use this sssd pam? The advantage of using ldap directly is you could maybe skip identifying users in the os. But maybe then tools like dovadm that require a user are not working anymore. From the keep it simple perspective it is probably better to use sssd. However centos8stream and sssd are not really known to me. So any ideas/advice about this?

7 7

strange cache behavior
by Maciej Milaszewski 07 Oct '21

07 Oct '21

Hi I Migrate user from ldap to mysql (director+nodes) (2.2.36.4) All works fine but when I turn on debbug auth I get "cache differences " look: dovecot6 (lmysql)run: #doveadm user mx8(a)domain.ltd field value user domain.ltd_mx8 uid 300 gid 300 home /vmail2/na/domain.ltd_mx8 mail maildir:~/Maildir:INDEX=/var/dovecot_indexes/vmail2/na/domain.ltd_mx8 quota_rule *:bytes=10485760 In second time (via cache) I get: #doveadm user mx8(a)domain.ltd field value uid 300 gid 300 home /vmail2/na/domain.ltd_mx8 mail maildir:~/Maildir:INDEX=/var/dovecot_indexes/vmail2/na/domain.ltd_mx8 quota_rule *:bytes=10485760 cache not give me "user domain.ltd_mx8" value In ldap every time I get this same I try debbug and i found difference in 2 and 3 line: mysql: Oct 7 16:42:04 dovecot6 dovecot: auth: Debug: master in: USER#0111#011mx8(a)domain.ltd#011service=doveadm#011debug Oct 7 16:42:04 dovecot6 dovecot: auth: Debug: sql(mx8(a)natan-test.iq.pl): userdb cache hit: home=/vmail2/na/domain.ltd_mx8#011quota_rule=*:bytes=10485760 Oct 7 16:42:04 dovecot6 dovecot: auth: Debug: userdb out: USER#0111#011mx8@domain.ltd#011home=/vmail2/na/natan-test.iq.pl_mx8_natan-test#011quota_rule=*:bytes=10485760 in ldap: Oct 7 16:45:31 dovecot5 dovecot: auth: Debug: master in: USER#0111#011mx8(a)domain.ltd#011service=doveadm#011debug Oct 7 16:45:31 dovecot5 dovecot: auth: Debug: ldap(mx8(a)natan-test.iq.pl): userdb cache hit: home=/vmail2/na/domain.ltd_mx8#011quota_rule=*:bytes=10485760#011user=domain.ltd_mx8 Oct 7 16:45:31 dovecot5 dovecot: auth: Debug: ldap(mx8(a)natan-test.iq.pl): username changed mx8(a)domain.ltd-> domain.ltd_mx8 Oct 7 16:45:31 dovecot5 dovecot: auth: Debug: userdb out: USER#0111#011domain.ltd_mx8#011home=/vmail2/na/natan-test.iq.pl_mx8_natan-test#011quota_rule=*:bytes=10485760 first query witchout cache: ldap Oct 7 16:45:21 dovecot5 dovecot: auth: Debug: userdb out: USER#0111#011domain.ltd_mx8#011home=/vmail2/na/domain.ltd_mx8#011quota_rule=*:bytes=10485760 mysql Oct 7 16:41:34 dovecot6 dovecot: auth: Debug: userdb out: USER#0111#011domain.ltd_mx8#011home=/vmail2/na/domain.ltd_mx8#011quota_rule=*:bytes=10485760 And I dont known where is a problem ? maybe in the cache setting ? All dovecot hava this sam config (outside of the settings about auth query)

1 0

Re: Quota emails... nothing happened
by Stephane Magnier 07 Oct '21

07 Oct '21

Hi, sorry to bother you.. any idea ? how to give more space to a specific user ? And where to place the line, in order to overide the general rule ? I suspect that to increase the space for the specific user AZT000, that should be : quota_rule=azt000:storage=160gb.. but where Thanks and regards, Le 06/10/2021 à 15:49, Stephane Magnier a écrit : > not exactly.. > > Usernames are : azt000, azt001, azt002, etc..... > All of them have their mailbox in /var/spool2/mail/azt000, > /var/spool2/mail/azt001 ) > > Everybody will get 30Gb by default > Except the user *azt000*, who will have 160Gb > > So, I understand, that the general rule is this > > > plugin { > quota = maildir:User quota > quota_rule = *:storage=30GB > quota_rule2 = Trash:storage=+100MB > quota_rule3 = Spam:storage=+20%% > } > > > Now, I suppose , to specify the user *azt000 and only this one*, to > get a quota of 160Gb, I should write something like: > *quota_rule=azt000:storage=+160Gb *correct ?* > * > but where ! > > 1) If I had this sentence into_the plugin_ ( as it was before ) , it's > not considered. Every body stays with the general 30Gb allocated in my > example > 2) My understanding is, according to the link you sent to me, I have > to write this specific condition :***quota_rule=azt000:storage=+160Gb* > _Outside_ the plugin.. I've made different tests and all of them are > not working.. The Dovecot doesn't start > > I also tried this > > userdb { > driver = passwd > args = /etc/dovecot/quota-overrides > quota_rule=azt000:storage=+160Gb > result_success=continue-ok > } > > I would like to keep 30gb for any user AZTxxx, But for some specific > users ( like AZT000), I wish to adapt the quota limit > > sorry to bother with that. I hope not to be too much pain in the neck..:-) > Thanks !! > * > * > Le 06/10/2021 à 14:51, Aki Tuomi a écrit : >> No. The syntax is not correct. >> >> https://doc.dovecot.org/configuration_manual/quota/#quota-rules >> >> this says that the rule is: >> >> quota_rule = <mailbox name>:<limit configuration> >> >> so unless you want 160GB quota for mailbox folder `azt000` (not username), you want to use * here. >> >> Aki >> >>> On 06/10/2021 15:36 Stephane Magnier<steph.mag220(a)netcourrier.com> wrote: >>> >>> >>> OK, but is the syntax correct ? >>> >>> Should it be :azt000:quota_rule4=+160GB ? >>> Is that correct ? >>> >>> Because I've made the test.. It didn't "shoot at me" while restarting the service, it apparently accept the syntax, but the result is still wrong.. >>> It is still considering a limit of 30gb and not 160Gb >>> ( the line : quota_rule = *:storage=30GB ) >>> >>> To sum up , I have >>> >>> >>>> plugin { >>>> quota = maildir:User quota >>>> quota_rule = *:storage=30GB >>>> quota_rule2 = Trash:storage=+100MB >>>> quota_rule3 = Spam:storage=+20%% >>>> azt000:quota_rule4=+160GB >>>> >>>> >>>> quota_status_success = DUNNO >>>> quota_status_nouser = DUNNO >>>> quota_status_overquota = "552 5.2.2 Mailbox is full" >>>> quota_warning = storage=95%% quota-warning 95 %u >>>> quota_warning2 = storage=80%% quota-warning 80 %u >>>> quota_warning3 = storage=100%% quota-warning below %u >>>> quota_grace = 10%% >>>> >>>> # Quota plugin can also limit the maximum accepted mail size. >>>> quota_max_mail_size = 100M >>>> } >>>> >>> and >>> >>> >>>> userdb { >>>> driver = passwd >>>> args = /etc/dovecot/quota-overrides >>>> result_success=continue-ok >>>> } >>>> >>> but >>> >>> >>>> [root@mbox1 conf.d]# service dovecot restart >>>> Redirecting to /bin/systemctl restart dovecot.service >>>> [root@mbox1 conf.d]# doveadm quota get -u azt000 >>>> Quota name Type Value Limit % >>>> User quota STORAGE 22268406 31457280 70 >>>> User quota MESSAGE 29853 - 0 >>>> [root@mbox1 conf.d]# >>>> >>> >>> With 70% ; it's considering the 30Gb and not the 160Gb ( the AZT000 folder size is about 21Gb ) >>> >>> >>> >>> Le 06/10/2021 à 14:08, Aki Tuomi a écrit : >>> >>>> The rules must be consecutive, >>>> >>>> if your global config has >>>> >>>> quota_rule1 >>>> quota_rule2 >>>> >>>> then the userdb must return >>>> >>>> quota_rule3. Or it will overwrite an existing rule. >>>> >>>> Aki >>>> >>>> >>>> >>>>> On 06/10/2021 13:07 Stephane Magnier<steph.mag220(a)netcourrier.com> wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> OK, I wrote this : >>>>> >>>>> >>>>> >>>>>> userdb { >>>>>> driver = passwd >>>>>> args = /etc/dovecot/quota-overrides >>>>>> >>>>>> result_success=continue-ok >>>>>> >>>>>> # Override fields from passwd >>>>>> #override_fields = home=/home/virtual/%u >>>>>> } >>>>>> >>>>>> >>>>> but sorry I don't understand the following line >>>>> >>>>> username::::::::::quota_ruleX=... where X is the next rule number. >>>>> >>>>> What should I write ?...... for instance : ? something like that ?? >>>>> >>>>> >>>>> >>>>> >>>>> Le 06/10/2021 à 10:13, Aki Tuomi a écrit : >>>>> >>>>> >>>>>> That `*` there is actually mailbox mask. You have to return an additional quota_ruleN from your userdb for that user. >>>>>> >>>>>> You can do e.g. >>>>>> >>>>>> userdb { >>>>>> .. >>>>>> result_success=continue-ok} >>>>>> } >>>>>> >>>>>> userdb { >>>>>> driver = passwd >>>>>> args = /etc/dovecot/quota-overrides >>>>>> } >>>>>> >>>>>> and put in there >>>>>> >>>>>> username::::::::::quota_ruleX=... where X is the next rule number. >>>>>> >>>>>> the count of : might be wrong. >>>>>> >>>>>> Aki >>>>>> >>>>>> >>>>>> >>>>>>> On 06/10/2021 10:43 Stephane Magnier<steph.mag220(a)netcourrier.com> wrote: >>>>>>> >>>>>>> >>>>>>> Hi Again, >>>>>>> >>>>>>> Juste another one... >>>>>>> >>>>>>> The quota I've decided is 30Gb for everybody >>>>>>> I would like to add an exception for the user AZT000 so here is my test : >>>>>>> >>>>>>> I put 60 GB for AZT000, but apparently, this is not seen :-( No error message >>>>>>> Is there a general syntax for a specific user ? >>>>>>> >>>>>>> NB: I tried : >>>>>>> quota_rule = azt000:storage=+60GB orquota_rule1 = azt000:storage=+60GB same results >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> plugin { >>>>>>>> quota = maildir:User quota >>>>>>>> quota_rule = *:storage=30GB >>>>>>>> quota_rule2 = Trash:storage=+100MB >>>>>>>> quota_rule3 = Spam:storage=+20%% >>>>>>>> # quota_rule = *:storage=70GB >>>>>>>> # quota_rule = *:storage=70GB >>>>>>>> quota_rule = azt000:storage=+60GB >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> Le 06/10/2021 à 08:09, Stephane Magnier a écrit : >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Great !! works fine.. >>>>>>>> >>>>>>>> I had in fact, twice the same déclaration of quotat and storage on the same file..... one of them was with an upper case "S" for Storage.. >>>>>>>> >>>>>>>> Thanks again >>>>>>>> >>>>>>>> >>>>>>>> Le 06/10/2021 à 07:50, Aki Tuomi a écrit : >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>>> On 06/10/2021 08:38 Stephane Magnier<steph.mag220(a)netcourrier.com> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Le 06/10/2021 à 06:51, Aki Tuomi a écrit : >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> On 06/10/2021 07:30 Stephane Magnier<steph.mag220(a)netcourrier.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Le 06/10/2021 à 06:10, Stephane Magnier a écrit : >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> Hi, >>>>>>>>>>>>> I am just running Dovecot v 2.3.8 .. seems to work fine. >>>>>>>>>>>>> I just add the quota plugin.. and.. I cannot see any differences.. I cannot see any information on Quota per user.. No specific info on Log file :-( >>>>>>>>>>>>> >>>>>>>>>>>>> Any help please ? >>>>>>>>>>>>> >>>>>>>>>>>>> Tahnks for your help >>>>>>>>>>>>> >>>>>>>>>>>>> Here is my config : >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf >>>>>>>>>>>>> # Pigeonhole version 0.5.8 (b7b03ba2) >>>>>>>>>>>>> # OS: Linux 4.18.0-305.12.1.el8_4.x86_64 x86_64 CentOS Linux release 8.4.2105 nfs4 >>>>>>>>>>>>> # Hostname: mbox1.intranet.office.itx >>>>>>>>>>>>> auth_cache_negative_ttl = 5 mins >>>>>>>>>>>>> auth_cache_ttl = 5 mins >>>>>>>>>>>>> auth_mechanisms = plain login >>>>>>>>>>>>> auth_username_format = %u >>>>>>>>>>>>> debug_log_path = /var/log/dovecot-debug.log >>>>>>>>>>>>> default_vsz_limit = 4 G >>>>>>>>>>>>> info_log_path = /var/log/dovecot-info.log >>>>>>>>>>>>> listen = * [::] >>>>>>>>>>>>> log_path = /var/log/dovecot.log >>>>>>>>>>>>> login_trusted_networks = 172.18.0.0/16 127.0.0.1 ::1 >>>>>>>>>>>>> mail_access_groups = dovecot >>>>>>>>>>>>> mail_fsync = always >>>>>>>>>>>>> mail_location = maildir:/var/spool2/mail/%u:LAYOUT=fs >>>>>>>>>>>>> mail_nfs_storage = yes >>>>>>>>>>>>> mail_plugins = " quota" >>>>>>>>>>>>> mail_privileged_group = mail >>>>>>>>>>>>> managesieve_notify_capability = mailto >>>>>>>>>>>>> managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave >>>>>>>>>>>>> mbox_very_dirty_syncs = yes >>>>>>>>>>>>> mbox_write_locks = fcntl >>>>>>>>>>>>> mmap_disable = yes >>>>>>>>>>>>> namespace inbox { >>>>>>>>>>>>> disabled = no >>>>>>>>>>>>> ignore_on_failure = no >>>>>>>>>>>>> inbox = yes >>>>>>>>>>>>> list = yes >>>>>>>>>>>>> location = >>>>>>>>>>>>> mailbox Archive { >>>>>>>>>>>>> auto = no >>>>>>>>>>>>> comment = " All my Accepted/NON SPAM" >>>>>>>>>>>>> special_use = \Archive >>>>>>>>>>>>> } >>>>>>>>>>>>> mailbox Drafts { >>>>>>>>>>>>> auto = subscribe >>>>>>>>>>>>> special_use = \Drafts >>>>>>>>>>>>> } >>>>>>>>>>>>> mailbox Junk { >>>>>>>>>>>>> auto = subscribe >>>>>>>>>>>>> autoexpunge = 90 days >>>>>>>>>>>>> special_use = \Junk >>>>>>>>>>>>> } >>>>>>>>>>>>> mailbox Sent { >>>>>>>>>>>>> auto = subscribe >>>>>>>>>>>>> special_use = \Sent >>>>>>>>>>>>> } >>>>>>>>>>>>> mailbox Trash { >>>>>>>>>>>>> auto = no >>>>>>>>>>>>> autoexpunge = 60 days >>>>>>>>>>>>> special_use = \Trash >>>>>>>>>>>>> } >>>>>>>>>>>>> mailbox virtual/All { >>>>>>>>>>>>> auto = no >>>>>>>>>>>>> special_use = \All >>>>>>>>>>>>> } >>>>>>>>>>>>> prefix = >>>>>>>>>>>>> subscriptions = yes >>>>>>>>>>>>> type = private >>>>>>>>>>>>> } >>>>>>>>>>>>> passdb { >>>>>>>>>>>>> driver = pam >>>>>>>>>>>>> } >>>>>>>>>>>>> plugin { >>>>>>>>>>>>> quota_grace = 10%% >>>>>>>>>>>>> quota_max_mail_size = 100M >>>>>>>>>>>>> quota_rule = *:storage=10000M >>>>>>>>>>>>> quota_rule2 = Trash:Storage=+100M >>>>>>>>>>>>> quota_rule3 = Spam:storage=+20%% >>>>>>>>>>>>> quota_status_nouser = DUNNO >>>>>>>>>>>>> quota_status_overquota = 552 5.2.2 Mailbox is full >>>>>>>>>>>>> quota_status_success = DUNNO >>>>>>>>>>>>> quota_warning = storage=95%% quota-warning 95 %u >>>>>>>>>>>>> quota_warning2 = storage=80%% quota-warning 80 %u >>>>>>>>>>>>> quota_warning3 = -storage=100%% quota-warning below %u >>>>>>>>>>>>> sieve =file:~/sieve;active=~/.dovecot.sieve >>>>>>>>>>>>> } >>>>>>>>>>>>> pop3_uidl_format = %v-%u >>>>>>>>>>>>> service auth { >>>>>>>>>>>>> unix_listener auth-master { >>>>>>>>>>>>> mode = 0666 >>>>>>>>>>>>> } >>>>>>>>>>>>> unix_listener auth-userdb { >>>>>>>>>>>>> mode = 0600 >>>>>>>>>>>>> user = mail >>>>>>>>>>>>> } >>>>>>>>>>>>> } >>>>>>>>>>>>> service dict { >>>>>>>>>>>>> unix_listener dict { >>>>>>>>>>>>> mode = 0600 >>>>>>>>>>>>> user = mail >>>>>>>>>>>>> } >>>>>>>>>>>>> } >>>>>>>>>>>>> service imap-login { >>>>>>>>>>>>> inet_listener imap { >>>>>>>>>>>>> port = 143 >>>>>>>>>>>>> } >>>>>>>>>>>>> inet_listener imaps { >>>>>>>>>>>>> port = 993 >>>>>>>>>>>>> ssl = yes >>>>>>>>>>>>> } >>>>>>>>>>>>> process_min_avail = 4 >>>>>>>>>>>>> service_count = 0 >>>>>>>>>>>>> } >>>>>>>>>>>>> service lmtp { >>>>>>>>>>>>> inet_listener lmtp { >>>>>>>>>>>>> port = 24 >>>>>>>>>>>>> } >>>>>>>>>>>>> unix_listener /var/run/lmtp { >>>>>>>>>>>>> group = mail >>>>>>>>>>>>> mode = 0660 >>>>>>>>>>>>> user = mail >>>>>>>>>>>>> } >>>>>>>>>>>>> } >>>>>>>>>>>>> service pop3-login { >>>>>>>>>>>>> inet_listener pop3 { >>>>>>>>>>>>> address = * >>>>>>>>>>>>> port = 110 >>>>>>>>>>>>> } >>>>>>>>>>>>> inet_listener pop3s { >>>>>>>>>>>>> port = 995 >>>>>>>>>>>>> ssl = yes >>>>>>>>>>>>> } >>>>>>>>>>>>> } >>>>>>>>>>>>> service quota-warning { >>>>>>>>>>>>> executable = script /usr/local/bin/quota-warning.sh >>>>>>>>>>>>> unix_listener quota-warning { >>>>>>>>>>>>> user = mail >>>>>>>>>>>>> } >>>>>>>>>>>>> user = dovecot >>>>>>>>>>>>> } >>>>>>>>>>>>> service submission { >>>>>>>>>>>>> process_limit = 250 >>>>>>>>>>>>> } >>>>>>>>>>>>> ssl = required >>>>>>>>>>>>> ssl_ca = </etc/mail/ssl/ssl1/xxxxxp_net.ca-bundle >>>>>>>>>>>>> ssl_cert = </etc/mail/ssl/ssl1/xxxxxx_net.crt >>>>>>>>>>>>> ssl_cipher_list = HIGH:!aNULL:!ADH:!DH:!RC4:!MD5:!RSA >>>>>>>>>>>>> ssl_dh = # hidden, use -P to show it >>>>>>>>>>>>> ssl_key = # hidden, use -P to show it >>>>>>>>>>>>> userdb { >>>>>>>>>>>>> driver = passwd >>>>>>>>>>>>> } >>>>>>>>>>>>> verbose_proctitle = yes >>>>>>>>>>>>> protocol lmtp { >>>>>>>>>>>>> mail_fsync = optimized >>>>>>>>>>>>> mail_plugins = autocreate quota acl fts fts_solr zlib mail_log notify sieve >>>>>>>>>>>>> postmaster_address =it(a)intranet.office.itx >>>>>>>>>>>>> } >>>>>>>>>>>>> protocol lda { >>>>>>>>>>>>> mail_fsync = optimized >>>>>>>>>>>>> mail_plugins = " quota sieve quota" >>>>>>>>>>>>> } >>>>>>>>>>>>> protocol imap { >>>>>>>>>>>>> mail_max_userip_connections = 80 >>>>>>>>>>>>> mail_plugins = " quota quota imap_quota" >>>>>>>>>>>>> ssl_cert = </etc/mail/ssl/ssl1/STAR_aztgrp_net.crt >>>>>>>>>>>>> ssl_key = # hidden, use -P to show it >>>>>>>>>>>>> } >>>>>>>>>>>>> protocol pop3 { >>>>>>>>>>>>> mail_max_userip_connections = 10 >>>>>>>>>>>>> mail_plugins = " quota" >>>>>>>>>>>>> } >>>>>>>>>>>>> protocol submission { >>>>>>>>>>>>> mail_max_userip_connections = 10 >>>>>>>>>>>>> mail_plugins = " quota" >>>>>>>>>>>>> } >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> Just for info >>>>>>>>>>>> >>>>>>>>>>>> [root@mbox1 xenia]# doveadm quota get -A |grep "STORAGE" >>>>>>>>>>>> Nothing at all ?? weird >>>>>>>>>>>> [root@mbox1 xenia]# >>>>>>>>>>>> >>>>>>>>>>>> [root@mbox1 xenia]# doveadm quota get -u <user1> >>>>>>>>>>>> Quota name Type Value Limit % >>>>>>>>>>>> [root@mbox1 xenia]# >>>>>>>>>>>> => Absolutely nothing is displayed ???? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> normally, the size of the user1 email folder is about 21 Gb >>>>>>>>>>>> So..just modified the line :quota_rule = *:storage=100G >>>>>>>>>>>> But nothing has changed... >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> You are missing quota driver settings, the recommended settings are >>>>>>>>>>> >>>>>>>>>>> plugin { >>>>>>>>>>> quota = count >>>>>>>>>>> quota_vsizes = yes >>>>>>>>>>> } >>>>>>>>>>> >>>>>>>>>>> Aki >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> Hi Aki, >>>>>>>>>> Thanks for your reply.. >>>>>>>>>> >>>>>>>>>> I just tryed to ad it.. but this can't connect anymore . >>>>>>>>>> Here is my exact declaration "90-quota.conf" >>>>>>>>>> >>>>>>>>>> ( based on :https://doc.dovecot.org/configuration_manual/quota/ ) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> plugin { >>>>>>>>>>> quota = count >>>>>>>>>>> quota_vsizes = yes >>>>>>>>>>> #quota = maildir:User quota >>>>>>>>>>> quota_rule = *:storage=100GB >>>>>>>>>>> # quota_rule2 = Trash:storage=+100MB >>>>>>>>>>> # quota_rule3 = Spam:storage=+20%% >>>>>>>>>>> # 20% of 100GB = 20GB >>>>>>>>>>> quota_status_success = DUNNO >>>>>>>>>>> quota_status_nouser = DUNNO >>>>>>>>>>> quota_status_overquota = "552 5.2.2 Mailbox is full" >>>>>>>>>>> quota_warning = storage=95%% quota-warning 95 %u >>>>>>>>>>> quota_warning2 = storage=80%% quota-warning 80 %u >>>>>>>>>>> quota_warning3 = -storage=100%% quota-warning below %u >>>>>>>>>>> >>>>>>>>>>> # LDA/LMTP allows saving the last mail to bring user from under quota to >>>>>>>>>>> # over quota, if the quota doesn't grow too high. Default is to allow as >>>>>>>>>>> # long as quota will stay under 10% above the limit. Also allowed e.g. 10M. >>>>>>>>>>> quota_grace = 10%% >>>>>>>>>>> >>>>>>>>>>> # Quota plugin can also limit the maximum accepted mail size. >>>>>>>>>>> quota_max_mail_size = 100M >>>>>>>>>>> } >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> The error message I have now is : >>>>>>>>>> >>>>>>>>>> Oct 06 07:23:35 imap(azt000)<7381><3pAIWajNgdcgAUHQ/kJ8Aikr1PIAQmFL>: Error: Failed to initialize quota: Invalid quota root quota: Invalid rule Trash:Storage=+100M: Unknown rule limit name: Storage >>>>>>>>>> Oct 06 07:23:35 imap(azt000)<7382><jqwJWajNgtcgAUHQ/kJ8Aikr1PIAQmFL>: Error: Failed to initialize quota: Invalid quota root quota: Invalid rule Trash:Storage=+100M: Unknown rule limit name: Storage >>>>>>>>>> Oct 06 07:26:02 master: Warning: Killed with signal 15 (by pid=8420 uid=0 code=kill) >>>>>>>>>> Oct 06 07:26:10 imap(azt000)<8468><cDRLYqjNcsSsEgA3>: Error: Failed to initialize quota: Invalid quota root quota: Invalid rule Trash:Storage=+100M: Unknown rule limit name: Storage >>>>>>>>>> Oct 06 07:26:13 imap(azt000)<8469><mxN6YqjNdMSsEgA3>: Error: Failed to initialize quota: Invalid quota root quota: Invalid rule Trash:Storage=+100M: Unknown rule limit name: Storage >>>>>>>>>> >>>>>>>>>> Then you can see that I've removed the 2 lines >>>>>>>>>> # quota_rule2 = Trash:storage=+100MB >>>>>>>>>> # quota_rule3 = Spam:storage=+20%% >>>>>>>>>> >>>>>>>>>> but without any success >>>>>>>>>> >>>>>>>>>> Effectively.. what is the Word "Storage" for Dovecot ?? no idea ... I just wrote what I saw :-) >>>>>>>>>> >>>>>>>>>> For info : all the mailbox are placed on a NFS storage.. Don't know if this help to locate the problem.. >>>>>>>>>> Thanks and regards, >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> Did you try changing Storage => storage in your rule? It seems to be coming either from userdb or your config. >>>>>>>>> >>>>>>>>> Try `doveadm user azt000` to if your userdb is providing these rules. >>>>>>>>> >>>>>>>>> Aki >>>>>>>>> >>>>>>>>> >>>>>>>>> >

2 1

Quota emails... nothing happened
by Stephane Magnier 06 Oct '21

06 Oct '21

Hi, I am just running Dovecot v 2.3.8 .. seems to work fine. I just add the quota plugin.. and.. I cannot see any differences.. I cannot see any information on Quota per user.. No specific info on Log file :-( Any help please ? Tahnks for your help Here is my config : # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-305.12.1.el8_4.x86_64 x86_64 CentOS Linux release 8.4.2105 nfs4 # Hostname: mbox1.intranet.office.itx auth_cache_negative_ttl = 5 mins auth_cache_ttl = 5 mins auth_mechanisms = plain login auth_username_format = %u debug_log_path = /var/log/dovecot-debug.log default_vsz_limit = 4 G info_log_path = /var/log/dovecot-info.log listen = * [::] log_path = /var/log/dovecot.log login_trusted_networks = 172.18.0.0/16 127.0.0.1 ::1 mail_access_groups = dovecot mail_fsync = always mail_location = maildir:/var/spool2/mail/%u:LAYOUT=fs mail_nfs_storage = yes mail_plugins = " quota" mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mbox_very_dirty_syncs = yes mbox_write_locks = fcntl mmap_disable = yes namespace inbox { disabled = no ignore_on_failure = no inbox = yes list = yes location = mailbox Archive { auto = no comment = " All my Accepted/NON SPAM" special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 90 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = no autoexpunge = 60 days special_use = \Trash } mailbox virtual/All { auto = no special_use = \All } prefix = subscriptions = yes type = private } passdb { driver = pam } plugin { quota_grace = 10%% quota_max_mail_size = 100M quota_rule = *:storage=10000M quota_rule2 = Trash:Storage=+100M quota_rule3 = Spam:storage=+20%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u sieve = file:~/sieve;active=~/.dovecot.sieve } pop3_uidl_format = %v-%u service auth { unix_listener auth-master { mode = 0666 } unix_listener auth-userdb { mode = 0600 user = mail } } service dict { unix_listener dict { mode = 0600 user = mail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 4 service_count = 0 } service lmtp { inet_listener lmtp { port = 24 } unix_listener /var/run/lmtp { group = mail mode = 0660 user = mail } } service pop3-login { inet_listener pop3 { address = * port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = mail } user = dovecot } service submission { process_limit = 250 } ssl = required ssl_ca = </etc/mail/ssl/ssl1/xxxxxp_net.ca-bundle ssl_cert = </etc/mail/ssl/ssl1/xxxxxx_net.crt ssl_cipher_list = HIGH:!aNULL:!ADH:!DH:!RC4:!MD5:!RSA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { mail_fsync = optimized mail_plugins = autocreate quota acl fts fts_solr zlib mail_log notify sieve postmaster_address = it(a)intranet.office.itx } protocol lda { mail_fsync = optimized mail_plugins = " quota sieve quota" } protocol imap { mail_max_userip_connections = 80 mail_plugins = " quota quota imap_quota" ssl_cert = </etc/mail/ssl/ssl1/STAR_aztgrp_net.crt ssl_key = # hidden, use -P to show it } protocol pop3 { mail_max_userip_connections = 10 mail_plugins = " quota" } protocol submission { mail_max_userip_connections = 10 mail_plugins = " quota" }

2 11

sieve: active= doesn't seem to use bindir=
by David Mandelberg 05 Oct '21

05 Oct '21

Hi, I'm trying to set up dovecot to read sieve source files from a read-only directory, and save compiled binaries to a separate directory with the bindir option. That worked when I pointed the sieve option at a single file, but I just changed it to point at a directory and added the active= option, also pointing at a symlink in a read-only directory. It looks like dovecot is trying to save the compiled active script to the same directory as the source file, instead of to bindir. Am I missing something? $ doveconf -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-8-amd64 x86_64 Debian 11.0 ext4 ... plugin { sieve = file:/usr/local/etc/mail/%{domain}/%{username}/sieve;active=/usr/local/etc/mail/%{domain}/%{username}/sieve/.active.sieve;bindir=/var/cache/mail/%{domain}/%{username}/sieve sieve_before = file:/etc/dovecot/sieve-before sieve_filter_bin_dir = /etc/dovecot/sieve-filter-bin sieve_filter_exec_timeout = 30s sieve_global_extensions = +vnd.dovecot.filter sieve_plugins = sieve_extprograms sieve_user_log = /var/local/mail/persistent/mail/%{domain}/%{username}/sieve.log } ... Relevant logs: lmtp(david(a)mandelberg.org)<90751><rqtQHUiTXGF/YgEA4Ys4ZQ>: Error: open(/usr/local/etc/mail/mandelberg.org/david/sieve/.active.svbin.mail-stor… failed: Read-only file system lmtp(david(a)mandelberg.org)<90751><rqtQHUiTXGF/YgEA4Ys4ZQ>: Error: sieve: binary /usr/local/etc/mail/mandelberg.org/david/sieve/.active.svbin: save: failed to create temporary file: open(/usr/local/etc/mail/mandelberg.org/david/sieve/.active.svbin.) failed: Read-only file system

2 3

Issue with the log service after upgrading from 2.1.17 to 2.3.10.1
by Grant Keller 05 Oct '21

05 Oct '21

Hello, As stated in the subject we have been doing a pretty big version upgrade. Both new and old are on CentOS 7. For the second time, one of our upgraded servers have had the dovecot log process start consuming 100% cpu, and the strace output shows it trying to access /etc/localtime: stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 With no other output then that multiple times a second. The process itself shows this from ps: root 76106 8.3 0.0 15384 6532 ? R Sep29 140:21 dovecot/log [service too fast: 34/34/imap-postlogin: ] As a part of this upgrade we also modified our postlogin script to include an index location for each user, so I am not sure if this is related to that change or a change in the logging service. Any help tracking this down is appreciated. # OS: Linux 3.10.0-1160.42.2.el7.x86_64 x86_64 CentOS Linux release 7.9.2009 (Core) # Hostname: d.lab.imapd.sonic.net auth_failure_delay = 0 auth_master_user_separator = * auth_username_format = %Ln auth_verbose = yes auth_verbose_passwords = sha1 auth_worker_max_count = 64 default_client_limit = 10000 listen = * login_log_format_elements = user=<%u> session=%{session} method=%m rip=%r lip=%l mpid=%e %c login_trusted_networks = 64.142.18.0/24 64.142.111.71/32 64.142.111.37/32 76.191.254.238/32 64.142.111.79/32 64.142.111.34/32 157.131.224.152/32 157.131.224.153/32 184.23.168.75/32 184.23.168.76/32 mail_fsync = always mail_log_prefix = "%s(%u): session=%{session} " mail_plugins = zlib maildir_very_dirty_syncs = yes mmap_disable = yes passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = imap driver = pam } plugin { lazy_expunge = DELETED_MESSAGES. mail_log_events = delete expunge flag_change mail_log_fields = uid box msgid from flags size mwi_update_debug = no mwi_update_events = flag_change delete undelete expunge copy save mwi_update_hosts = 76.191.249.68 76.191.255.180 mwi_update_master_user = _mwi-master mwi_update_port = 6472 mwi_update_watch_folder = INBOX.Voicemail quota = fs:User quota stats_refresh = 30 secs stats_track_cmds = yes } protocols = imap pop3 service anvil { client_limit = 10000 } service auth { client_limit = 10000 vsz_limit = 1 G } service doveadm { inet_listener { port = 1842 } unix_listener doveadm-server { mode = 0666 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 7000 process_min_avail = 32 vsz_limit = 256 M } service imap-postlogin { executable = script-login -d /etc/dovecot/bin/sonic-imap-postlogin user = $default_internal_user } service imap { executable = imap imap-postlogin process_limit = 7000 vsz_limit = 2516 M } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_limit = 2000 process_min_avail = 32 vsz_limit = 512 M } service pop3-postlogin { executable = script-login -d /etc/dovecot/bin/sonic-pop3-postlogin user = $default_internal_user } service pop3 { executable = pop3 pop3-postlogin process_limit = 2000 vsz_limit = 512 M } shutdown_clients = no ssl = no ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL syslog_facility = local0 userdb { driver = passwd } verbose_proctitle = yes protocol imap { imap_id_send = support-url support-email imap_max_line_length = 128 k mail_max_userip_connections = 20 mail_plugins = zlib mwi_update mail_log notify imap_zlib } protocol pop3 { mail_plugins = zlib lazy_expunge pop3_fast_size_lookups = yes pop3_uidl_format = %f } Grant Keller System Operations grant.keller(a)sonic.com

1 1

Re: Re: Exporting a mailbox over IMAP.
by Xavier Morel 04 Oct '21

04 Oct '21

I'd seen them around yes, but that would require mounting a local dovecot to make the mailboxes available over IMAP no? And I was kinda hoping to avoid doing that, as as noted in the initial message I know very little about dovecot.

1 0

replicator: Panic: data stack: Out of memory when allocating ...
by Sebastian Podjasek 04 Oct '21

04 Oct '21

I've seen thread with problem identical to mine started "Fri May 28 13:54:27 EEST 2021" and I was wondering did you get to fix this issue? Mine looks like this: dovecot: replicator: Panic: data stack: Out of memory when allocating 1073741864 bytes dovecot: replicator: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f57c5a4c4e2] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f57c5a4c5fe] -> /usr/lib/dovecot/libdovecot.so.0(+0xfc49b) [0x7f57c5a5849b] -> /usr/lib/dovecot/libdovecot.so.0(+0xfc531) [0x7f57c5a58531] -> /usr/lib/dovecot/libdovecot.so.0(+0x53aee) [0x7f57c59afaee] -> /usr/lib/dovecot/libdovecot.so.0(+0x53435) [0x7f57c59af435] -> /usr/lib/dovecot/libdovecot.so.0(+0xf5d88) [0x7f57c5a51d88] -> /usr/lib/dovecot/libdovecot.so.0(+0x11b818) [0x7f57c5a77818] -> /usr/lib/dovecot/libdovecot.so.0(+0xf25f2) [0x7f57c5a4e5f2] -> /usr/lib/dovecot/libdovecot.so.0(+0xf26a9) [0x7f57c5a4e6a9] -> /usr/lib/dovecot/libdovecot.so.0(buffer_write+0x1e) [0x7f57c5a4e8be] -> dovecot/replicator(replicator_queue_push+0x14a) [0x55aabc673b1a] -> dovecot/replicator(+0x5296) [0x55aabc673296] -> dovecot/replicator(+0x493e) [0x55aabc67293e] -> dovecot/replicator(+0x4acc) [0x55aabc672acc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f57c5a6df59] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) [0x7f57c5a6f592] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f57c5a6e000] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f57c5a6e1c0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f57c59e44e3] -> dovecot/replicator(main+0x18d) [0x55aabc671cad] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f57c57b4d0a] -> dovecot/replicator(_start+0x2a) [0x55aabc671d6a] And setting vsz_limit = 0 doesn't help either - it just tries to allocate all available memory. I'm running: # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-8-amd64 x86_64 Debian 11.0 -- Sebastian Podjasek

2 1

Exporting a mailbox over IMAP.
by Xavier Morel 04 Oct '21

04 Oct '21

Hello, Upfront note: I know very little about dovecot and IMAP lingo / terms of art, I'll try to be clear and complete but I may be missing important bits. I have a VPS backup with mailboxes in the maildir dovecot format: $ ls some/folder/backup/mail/domain/\* cur dovecot-uidlist dovecot-uidvalidity.5c0637b7 dovecot.index.cache dovecot.mailbox.log subscriptions dovecot-keywords dovecot-uidvalidity dovecot.index dovecot.index.log new tmp Separately and independently, I also have an existing IMAP account I do not personally manage. By "account" I mean that if I connect to the IMAP server, LOGIN, then LIST I see a pretty standard set of folders: (\HasNoChildren) "/" INBOX (\HasNoChildren \Archive) "/" Archive (\HasNoChildren \Drafts) "/" Drafts (\HasNoChildren \XNotes) "/" Notes (\HasNoChildren \Sent) "/" Sent (\HasNoChildren \Junk) "/" Spam (\HasNoChildren \Trash) "/" Trash I would like to copy / upload / … the content of the backup mailboxes to the IMAP account, ideally without losing the metadata. I asked about this on IRC and user "cmouse" provided me with information about the imapc storage (plugin?), a sample "doveadmin import" command, and a sample dovecot configuration which I expanded to this (for simplicity, the original sample command used a lot of `-c` and I figured I could just shove them into the configuration file for readability): $ dovecot -n # 2.3.16 (): /opt/local/etc/dovecot/dovecot.conf # OS: Darwin 15.6.0 x86_64 auth_verbose = yes imapc_host = <server> imapc_password = # hidden, use -P to show it imapc_port = 993 imapc_ssl = imaps imapc_user = <user> mail_location = imapc: # did not setup a "vmail" user or group as I just want to move the contents mail_uid = <current_user> mail_gid = staff namespace { inbox = yes location = prefix = separator = / } ssl = no verbose_proctitle = yes verbose_ssl = yes That did not work as I guess "import" wants to create all the mailboxes, and these already exist: $ doveadm -Dv import maildir:some/folder/backup/mail/domain/\* '.' all […] Debug: Mailbox Archive: Mailbox opened because: import Debug: Mailbox spam: Mailbox opened because: import Debug: Mailbox Junk: Mailbox opened because: import Debug: Mailbox Trash: Mailbox opened because: import Debug: Mailbox Sent: Mailbox opened because: import Debug: Mailbox Drafts: Mailbox opened because: import Debug: Mailbox INBOX.Spam: Mailbox opened because: import Debug: Mailbox INBOX.Junk: Mailbox opened because: import Debug: Mailbox INBOX.Drafts: Mailbox opened because: import Debug: Mailbox INBOX: Mailbox opened because: import Debug: Namespace : Using permissions from : mode=0700 gid=default Error: Couldn't create mailbox ./INBOX: Mailbox already exists I tried messing around with the options but didn't achieve anything, the only change which did anything visible was to replace '.' with '.INBOX' which resulted in import creating `.IMPORT/IMPORT` and exiting with: Error: Couldn't create mailbox INBOX/INBOX: Invalid mailbox name which… fair enough. Looking around I found `doveadm sync` which seemed promising, so far I arrived not far: $ doveadm -Dv sync -f maildir:some/folder/backup/mail/domain/\* this ultimately fails as well: brain S: Local mailbox tree: INBOX guid=63ace42cc352935925190000691e7660 uid_validity=1315910895 uid_next=71 subs=no last_change=0 last_subs=0 brain M: Local mailbox tree: Trash guid=7f5af7ba291b2df1a11d573bdb55d7e9 uid_validity=1632758505 uid_next=6 subs=yes last_change=0 last_subs=0 brain S: Local mailbox tree: INBOX/Drafts guid=ebb8a22812fe675b34390000691e7660 uid_validity=1533541906 uid_next=2 subs=yes last_change=0 last_subs=0 brain M: Local mailbox tree: Spam guid=59c97b78ad43f83b1f91e47936e7e7d1 uid_validity=1632758508 uid_next=20 subs=yes last_change=0 last_subs=0 brain S: Local mailbox tree: INBOX/Junk guid=62ace42cc352935925190000691e7660 uid_validity=1490450196 uid_next=2 subs=yes last_change=0 last_subs=0 brain M: Local mailbox tree: Sent guid=bfb2e03fdce327671e82bf173b1ccb8b uid_validity=1632758506 uid_next=1 subs=yes last_change=0 last_subs=0 brain S: Local mailbox tree: INBOX/Spam guid=64ace42cc352935925190000691e7660 uid_validity=1315911183 uid_next=1 subs=yes last_change=0 last_subs=0 brain M: Local mailbox tree: Drafts guid=e0187b65e763143666d22094cedfe6a4 uid_validity=1632758507 uid_next=1 subs=yes last_change=0 last_subs=0 brain S: Local mailbox tree: Drafts guid=2fda3e14a611e860c43e2700d32ae34d uid_validity=1625821607 uid_next=1 subs=no last_change=0 last_subs=0 brain M: Local mailbox tree: Archive guid=51a58e1d1d5c491aac71488647b20224 uid_validity=1632758509 uid_next=1 subs=yes last_change=0 last_subs=0 brain S: Local mailbox tree: Sent guid=30da3e14a611e860c43e2700d32ae34d uid_validity=1625821608 uid_next=1 subs=no last_change=0 last_subs=0 brain M: Local mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1632758504 uid_next=13 subs=yes last_change=0 last_subs=0 brain S: Local mailbox tree: Trash guid=31da3e14a611e860c43e2700d32ae34d uid_validity=1625821609 uid_next=1 subs=no last_change=0 last_subs=0 brain S: Local mailbox tree: Junk guid=32da3e14a611e860c43e2700d32ae34d uid_validity=1625821610 uid_next=1 subs=no last_change=0 last_subs=0 brain S: Local mailbox tree: spam guid=33da3e14a611e860c43e2700d32ae34d uid_validity=1625821611 uid_next=1 subs=no last_change=0 last_subs=0 brain M: Remote mailbox tree: INBOX guid=63ace42cc352935925190000691e7660 uid_validity=1315910895 uid_next=71 subs=no last_change=0 last_subs=0 brain M: Remote mailbox tree: INBOX/Drafts guid=ebb8a22812fe675b34390000691e7660 uid_validity=1533541906 uid_next=2 subs=yes last_change=0 last_subs=0 brain M: Remote mailbox tree: INBOX/Junk guid=62ace42cc352935925190000691e7660 uid_validity=1490450196 uid_next=2 subs=yes last_change=0 last_subs=0 brain M: Remote mailbox tree: INBOX/Spam guid=64ace42cc352935925190000691e7660 uid_validity=1315911183 uid_next=1 subs=yes last_change=0 last_subs=0 brain M: Remote mailbox tree: Drafts guid=2fda3e14a611e860c43e2700d32ae34d uid_validity=1625821607 uid_next=1 subs=no last_change=0 last_subs=0 brain M: Remote mailbox tree: Sent guid=30da3e14a611e860c43e2700d32ae34d uid_validity=1625821608 uid_next=1 subs=no last_change=0 last_subs=0 brain M: Remote mailbox tree: Trash guid=31da3e14a611e860c43e2700d32ae34d uid_validity=1625821609 uid_next=1 subs=no last_change=0 last_subs=0 brain M: Remote mailbox tree: Junk guid=32da3e14a611e860c43e2700d32ae34d uid_validity=1625821610 uid_next=1 subs=no last_change=0 last_subs=0 brain M: Remote mailbox tree: spam guid=33da3e14a611e860c43e2700d32ae34d uid_validity=1625821611 uid_next=1 subs=no last_change=0 last_subs=0 brain S: Local mailbox tree: Archive guid=4d10f3271f03f7603b232100d32ae34d uid_validity=1533541907 uid_next=1 subs=yes last_change=0 last_subs=0 brain M: Remote mailbox tree: Archive guid=4d10f3271f03f7603b232100d32ae34d uid_validity=1533541907 uid_next=1 subs=yes last_change=0 last_subs=0 brain M: Mailbox Archive: local=51a58e1d1d5c491aac71488647b20224/0/1, remote=4d10f3271f03f7603b232100d32ae34d/0/1: GUIDs conflict - will be merged later brain M: Mailbox Drafts: local=e0187b65e763143666d22094cedfe6a4/0/1, remote=2fda3e14a611e860c43e2700d32ae34d/0/1: GUIDs conflict - will be merged later brain M: Mailbox INBOX: local=c92f64f79f0d1ed01e6d5b314f04886c/0/1, remote=63ace42cc352935925190000691e7660/0/1: GUIDs conflict - will be merged later brain M: Mailbox INBOX/Drafts: local=00000000000000000000000000000000/0/0, remote=ebb8a22812fe675b34390000691e7660/0/1: mailbox not selectable yet brain M: Mailbox INBOX/Junk: local=00000000000000000000000000000000/0/0, remote=62ace42cc352935925190000691e7660/0/1: mailbox not selectable yet brain M: Mailbox INBOX/Spam: local=00000000000000000000000000000000/0/0, remote=64ace42cc352935925190000691e7660/0/1: mailbox not selectable yet brain M: Mailbox Junk: local=00000000000000000000000000000000/0/0, remote=32da3e14a611e860c43e2700d32ae34d/0/1: mailbox not selectable yet brain M: Mailbox Sent: local=bfb2e03fdce327671e82bf173b1ccb8b/0/1, remote=30da3e14a611e860c43e2700d32ae34d/0/1: GUIDs conflict - will be merged later brain M: Mailbox Spam: local=59c97b78ad43f83b1f91e47936e7e7d1/0/1, remote=00000000000000000000000000000000/0/0: mailbox not selectable yet brain M: Mailbox Trash: local=7f5af7ba291b2df1a11d573bdb55d7e9/0/1, remote=31da3e14a611e860c43e2700d32ae34d/0/1: GUIDs conflict - will be merged later brain M: Mailbox forwebmaster: local=4602f79bfcc91efb337823d522c170b9/0/1, remote=00000000000000000000000000000000/0/0: mailbox not selectable yet brain M: Mailbox spam: local=00000000000000000000000000000000/0/0, remote=33da3e14a611e860c43e2700d32ae34d/0/1: mailbox not selectable yet Namespace : Using permissions from : mode=0700 gid=default Can't create mailbox Archive: Mailbox already exists brain S: Remote mailbox tree: Trash guid=7f5af7ba291b2df1a11d573bdb55d7e9 uid_validity=1632758505 uid_next=6 subs=yes last_change=0 last_subs=0 brain S: Remote mailbox tree: Spam guid=59c97b78ad43f83b1f91e47936e7e7d1 uid_validity=1632758508 uid_next=20 subs=yes last_change=0 last_subs=0 brain S: Remote mailbox tree: Sent guid=bfb2e03fdce327671e82bf173b1ccb8b uid_validity=1632758506 uid_next=1 subs=yes last_change=0 last_subs=0 brain S: Remote mailbox tree: Drafts guid=e0187b65e763143666d22094cedfe6a4 uid_validity=1632758507 uid_next=1 subs=yes last_change=0 last_subs=0 brain S: Remote mailbox tree: Archive guid=51a58e1d1d5c491aac71488647b20224 uid_validity=1632758509 uid_next=1 subs=yes last_change=0 last_subs=0 brain S: Remote mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1632758504 uid_next=13 subs=yes last_change=0 last_subs=0 So it looks like it can see both sides of the sync, sees that they diverge (because they were created independently so the folders of the mailboxes have the same names but different GUIDs), then it tries to create the "missing" folders (by guid) which I expect fails because there's already a folder with that name? Something like that? Anyway that's where I'm stuck so far, I've got no idea whether `sync` is even the right direction but I don't really know what to try. NOTES: the maildir I'm working on right now has 41 messages in it: $ ls some/folder/backup/mail/domain/\*/cur | wc -l 41 though the uidlist has 45 lines (which is 3 more than I'd have expected): $ wc -l some/folder/backup/mail/domain/\*/dovecot-uidlist 45 some/folder/backup/mail/domain/\*/dovecot-uidlist Xavier

4 3

ssl_cipher_list
by dovecot＠ptld.com 04 Oct '21

04 Oct '21

Is there a difference between not setting #ssl_cipher_list = or setting to nothing ssl_cipher_list = or setting to ssl_cipher_list = PROFILE=SYSTEM Which is the best preferred way for default? Also, the docs say "You should usually prefer server ciphers and their order, so setting ssl_prefer_server_ciphers=yes is recommended." however this setting is =no by default. Why? Should it be yes or not?

1 0

Panic during IMAP APPEND
by Gedalya 30 Sep '21

30 Sep '21

I don't know how I can tell which mailbox is selected / being appended to. Mailbox format is Maildir. Filesystem is XFS. System was upgraded from 2.2.36.1 to 2.3.16, and it seems this started happening following that. Sep 20 15:49:34 imap1 dovecot: imap(u@d)<17673><jfjuOW/Mf+xEgdSK>: Panic: file mail-index-map.c: line 558 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) Sep 20 15:49:34 imap1 dovecot: imap(u@d)<17673><jfjuOW/Mf+xEgdSK>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f363c72dc22] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f363c72dd3e] -> /usr/lib/dovecot/libdovecot.so.0(+0xff47b) [0x7f363c73c47b] -> /usr/lib/dovecot/libdovecot.so.0(+0xff511) [0x7f363c73c511] -> /usr/lib/dovecot/libdovecot.so.0(+0x5427c) [0x7f363c69127c] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x49e07) [0x7f363c84fe07] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xf0499) [0x7f363c8f6499] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_lookup_seq+0xf) [0x7f363c8ff20f] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_set_uid+0x2f) [0x7f363c8cf79f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_set_uid+0x35) [0x7f363c8559a5] -> /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so(+0x8d02) [0x7f363c255d02] -> /usr/lib/dovecot/modules/lib10_quota_plugin.so(+0x130f4) [0x7f363c45e0f4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x56) [0x7f363c8628a6] -> dovecot/imap [u@d xx.xx.xx.xx APPEND](+0x13e10) [0x55eae70f8e10] -> dovecot/imap [u@d xx.xx.xx.xx APPEND](command_exec+0xa4) [0x55eae7104844] -> dovecot/imap [u@d xx.xx.xx.xx APPEND](+0x1333b) [0x55eae70f833b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f363c752869] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) [0x7f363c7546d2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f363c754780] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f363c754940] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f363c6c4dd3] -> dovecot/imap [u@d xx.xx.xx.xx APPEND](main+0x500) [0x55eae70f7120] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f363c49ad0a] -> dovecot/imap [u@d xx.xx.xx.xx APPEND](_start+0x2a) [0x55eae70f721a] Sep 20 15:49:34 imap1 dovecot: imap(u@d)<17673><jfjuOW/Mf+xEgdSK>: Fatal: master: service(imap): child 17673 killed with signal 6 (core dumped) # doveconf -n # 2.3.16 (): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Linux 5.10.0-8-amd64 x86_64 Debian 11.0 # Hostname: imap1.xxxxx.com auth_default_realm = xxxxx.com auth_master_user_separator = * auth_mechanisms = plain login cram-md5 auth_proxy_self = xxxxxxxxxx auth_verbose = yes auth_verbose_passwords = plain dict { lastlogin = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it imap_hibernate_timeout = 10 secs lmtp_rcpt_check_quota = yes log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Dovecot ready login_log_format_elements = user=<%u> method=%m rip=%r lip=%l pip=%{real_rip} mpid=%e %c %k session=<%{session}> login_trusted_networks = xxxxxxxxxxxxxxxxx mail_attachment_detection_options = add-flags-on-save mail_gid = vmail mail_location = /nowhere mail_plugins = quota listescape mail_privileged_group = mail mail_uid = vmail managesieve_sieve_capability = fileinto envelope encoded-character subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables mailbox date index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } mailbox Trash/* { autoexpunge = 30 days } prefix = separator = / type = private } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { imapsieve_mailbox1_before = file:/usr/local/lib/imapsieve/report-spam.sieve imapsieve_mailbox1_causes = COPY APPEND imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/local/lib/imapsieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/usr/local/lib/imapsieve/report-ham.sieve imapsieve_mailbox3_causes = APPEND imapsieve_mailbox3_name = INBOX last_login_dict = proxy::lastlogin last_login_key = # hidden, use -P to show it quota = dict:user::proxy::quota quota_rule = *:storage=2G quota_rule2 = Trash:storage=+250M quota_rule3 = Junk:ignore quota_vsizes = yes quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=85%% quota-warning 85 %u sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve-global/fileinto-spam.sieve sieve_extensions = -vacation -body -reject -enotify -environment -virustest -spamtest sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_max_actions = 32 sieve_max_redirects = 4 sieve_max_script_size = 10K sieve_pipe_bin_dir = /usr/local/lib/imapsieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_quota_max_scripts = 100 sieve_quota_max_storage = 4M } pop3_fast_size_lookups = yes pop3_no_flag_updates = yes postmaster_address = postmaster(a)xxxxx.com protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth-worker { user = $default_internal_user } service auth { client_limit = 2448 unix_listener auth-userdb { group = root mode = 0600 user = vmail } } service dict { unix_listener dict { group = root mode = 0600 user = vmail } } service imap-hibernate { unix_listener imap-hibernate { group = $default_internal_group mode = 0660 } } service imap-login { process_min_avail = 4 service_count = 0 vsz_limit = 192 M } service imap { process_limit = 1024 unix_listener imap-master { user = $default_internal_user } vsz_limit = 384 M } service lmtp { inet_listener lmtp { port = 7025 } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 vsz_limit = 64 M } service managesieve { process_limit = 20 } service pop3-login { process_min_avail = 4 service_count = 0 vsz_limit = 192 M } service pop3 { process_limit = 1024 } service quota-warning { executable = script /usr/local/bin/quota-warning unix_listener quota-warning { user = vmail } user = dovecot } ssl_cert = </var/local/letsencrypt/live/xxxxxxxxxxx/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_min_protocol = TLSv1 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = quota listescape sieve } protocol lda { mail_plugins = quota listescape sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = quota listescape imap_quota imap_sieve last_login } protocol sieve { mail_max_userip_connections = 5 } protocol pop3 { mail_max_userip_connections = 10 mail_plugins = quota listescape last_login }

2 8

dovecot ldap and mysql
by Maciej Milaszewski 30 Sep '21

30 Sep '21

Hi I have dovecot director + nodes and migrate users from ldap to mysql. I allow to auth via e-mail and alias and uid - thats i need In director ( where users is in ldap ) all works fine - user is proxy to UID like: ... doveadm auth test ola(a)domain.ltd passs passdb: ola(a)domain.ltd auth succeeded extra fields: user=uid_122_ola_domain.ltd proxy original_user=ola(a)domain.ltd ... In lab director2 ( where users is in mysql) not: ... doveadm auth test ola(a)domain.ltd passs passdb: ola(a)domain.ltd auth succeeded extra fields: user=ola(a)domain.ltd proxy ... and I dont known where is a problem in mysql. Mayby subquery/other ?

2 3

dovecot and irc
by Maciej Milaszewski 30 Sep '21

30 Sep '21

Hi What is official irc server ? Freenode or libra or other ?

2 1

Broken links
by MAREN ZUBIZARRETA 30 Sep '21

30 Sep '21

Hello: We are using Single instance attachment storage (SIS). Recently we have updated to latest dovecot versión, and changed the storage system. After the change, we are perceiving that, for some random users and days, attachment links were not created. In some cases even the file itself is missing (we asume that this is because, if there is 0 links pointing to the attachment, it gets deleted, or not Created even). There is anybody else experiencing the same issues? Could it be caused from some bug? Any hint? Thnks for your help Maren Zubizarreta

1 0

Panic on service(imap) during FETCH/APPEND some messages
by Alessio Cecchi 26 Sep '21

26 Sep '21

Hi, when I check "doveadm log errors" I found some fatal error repeated many times by around the same users - Panic: file message-part-data.c May 31 21:03:46 pop08 dovecot: imap(user1(a)email.com) session=<tON64qTDu8OXFBVM>: Error: Mailbox INBOX: UID=3454: imap_bodystructure_parse() failed: message_part lines doesn't match lines in BODYSTRUCTURE May 31 21:03:46 pop08 dovecot: imap(user1(a)email.com) session=<tON64qTDu8OXFBVM>: Error: Mailbox INBOX: UID=3454: imap_bodystructure_parse() failed: message_part lines doesn't match lines in BODYSTRUCTURE May 31 21:03:46 pop08 dovecot: imap(user1(a)email.com) session=<tON64qTDu8OXFBVM>: Panic: file message-part-data.c: line 579 (message_part_is_attachment): assertion failed: (data != NULL) May 31 21:03:46 pop08 dovecot: imap(user1(a)email.com) session=<tON64qTDu8OXFBVM>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f294d7fdac2] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f294d7fdbce] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf3cde) [0x7f294d80acde] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf3d81) [0x7f294d80ad81] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f294d75c25a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xd377d) [0x7f294d7ea77d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x3ecbc) [0x7f294db0ccbc] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x3eca4) [0x7f294db0cca4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_set_attachment_keywords+0xe7) [0x7f294db0dd17] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xc15a4) [0x7f294db8f5a4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xc190e) [0x7f294db8f90e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_init_stream+0x332) [0x7f294db8fd32] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x77428) [0x7f294db45428] -> /usr/lib64/dovecot/libdovecot-storage.soindex-mail-headers.c.0(mail_get_hdr_stream_because+0x5b) [0x7f294db0d6ab] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_header_stream+0x18a) [0x7f294db8d68a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_header_stream+0x53) [0x7f294db0d493] -> /usr/lib64/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x5aa) [0x7f294dbd20aa] -> dovecot/imap [user1(a)email.com 18.123.45.76 UID FETCH](+0x235ae) [0x5568ba7fd5ae] -> dovecot/imap [user1(a)email.com 18.123.45.76 UID FETCH](+0x210ac) [0x5568ba7fb0ac] -> dovecot/imap [user1(a)email.com 18.123.45.76 UID FETCH](imap_fetch_more+0x35) [0x5568ba7fc6e5] -> dovecot/imap [user1(a)email.com 18.123.45.76 UID FETCH](cmd_fetch+0x34d) [0x5568ba7ec7ed] -> dovecot/imap [user1(a)email.com 18.123.45.76 UID FETCH](command_exec+0x64) [0x5568ba7f9614] -> dovecot/imap [user1(a)email.com 18.123.45.76 UID FETCH](+0x1d502) [0x5568ba7f7502] -> dovecot/imap [user1(a)email.com 18.123.45.76 UID FETCH](+0x1d591) [0x5568ba7f7591] -> dovecot/imap [user1(a)email.com 18.123.45.76 UID FETCH](+0x1d759) [0x5568ba7f7759] -> dovecot/imap [user1(a)email.com 18.123.45.76 UID FETCH](client_handle_input+0x205) [0x5568ba7f7a15] -> dovecot/imap [user1(a)email.com 18.123.45.76 UID FETCH](client_input+0x79) [0x5568ba7f7ff9] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7f294d822f45] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12b) [0x7f294d8248fb] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7f294d823049] May 31 21:03:46 pop08 dovecot: imap(user1(a)email.com) session=<tON64qTDu8OXFBVM>: Fatal: master: service(imap): child 21483 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) - Panic: file imap-bodystructure.c May 31 12:06:05 pop01 dovecot: imap(user2(a)email.com) session=<3b6TX53DetK5HrcI>: Panic: file imap-bodystructure.c: line 209 (part_write_body): assertion failed: (text == ((part->flags & MESSAGE_PART_FLAG_TEXT) != 0)) May 31 12:06:05 pop01 dovecot: imap(user2(a)email.com) session=<3b6TX53DetK5HrcI>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fe4e8000ac2] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fe4e8000bce] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf3cde) [0x7fe4e800dcde] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf3d81) [0x7fe4e800dd81] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fe4e7f5f25a] -> /usr/lib64/dovecot/libdovecot.so.0(imap_bodystructure_write+0x263) [0x7fe4e7fd6a53] -> /usr/lib64/dovecot/libdovecot.so.0(+0xbcca3) [0x7fe4e7fd6ca3] -> /usr/lib64/dovecot/libdovecot.so.0(imap_bodystructure_write+0x28a) [0x7fe4e7fd6a7a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xc0aa7) [0x7fe4e8391aa7] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xc1563) [0x7fe4e8392563] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xc190e) [0x7fe4e839290e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_init_stream+0x332) [0x7fe4e8392d32] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x77428) [0x7fe4e8348428] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_stream_because+0x64) [0x7fe4e83105a4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_prefetch+0x96) [0x7fe4e8393bc6] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_prefetch+0x2e) [0x7fe4e830fe4e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xc98cd) [0x7fe4e839a8cd] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x110) [0x7fe4e839ae30] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22) [0x7fe4e831eaa2] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_search_next+0x3d) [0x7fe4e831eb0d] -> dovecot/imap [user2(a)email.com 89.45.183.8 UID fetch](+0x211dc) [0x5649a2e121dc] -> dovecot/imap [user2(a)email.com 89.45.183.8 UID fetch](imap_fetch_more+0x35) [0x5649a2e136e5] -> dovecot/imap [user2(a)email.com 89.45.183.8 UID fetch](cmd_fetch+0x34d) [0x5649a2e037ed] -> dovecot/imap [user2(a)email.com 89.45.183.8 UID fetch](command_exec+0x64) [0x5649a2e10614] -> dovecot/imap [user2(a)email.com 89.45.183.8 UID fetch](+0x1d502) [0x5649a2e0e502] -> dovecot/imap [user2(a)email.com 89.45.183.8 UID fetch](+0x1d591) [0x5649a2e0e591] -> dovecot/imap [user2(a)email.com 89.45.183.8 UID fetch](+0x1d759) [0x5649a2e0e759] -> dovecot/imap [user2(a)email.com 89.45.183.8 UID fetch](client_handle_input+0x205) [0x5649a2e0ea15] -> dovecot/imap [user2(a)email.com 89.45.183.8 UID fetch](client_input+0x79) [0x5649a2e0eff9] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7fe4e8025f45] May 31 12:06:05 pop01 dovecot: imap(user2(a)email.com) session=<3b6TX53DetK5HrcI>: Fatal: master: service(imap): child 29622 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) - Panic: file index-mail-headers.c May 31 18:38:20 pop07 dovecot: imap(user3(a)email.com) session=<i5VgbaLD1f5QEZQ5>: Panic: file index-mail-headers.c: line 198 (index_mail_parse_header_init): assertion failed: (!mail->data.header_parser_initialized) May 31 18:38:20 pop07 dovecot: imap(user3(a)email.com) session=<i5VgbaLD1f5QEZQ5>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f73d1683ac2] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f73d1683bce] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf3cde) [0x7f73d1690cde] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf3d81) [0x7f73d1690d81] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f73d15e225a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_parse_header_init+0x3b9) [0x7f73d1a11dc9] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_parse_headers_internal+0x2b) [0x7f73d1a127eb] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_init_stream+0x19f) [0x7f73d1a15b9f] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x77428) [0x7f73d19cb428] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_stream_because+0x64) [0x7f73d19935a4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x77207) [0x7f73d19cb207] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_virtual_size+0x38) [0x7f73d1993158] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_save_finish+0x154) [0x7f73d19cc504] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_save_cancel+0x3e) [0x7f73d19a239e] -> dovecot/imap [user3(a)email.com 35.67.148.57 APPEND](+0xf5d2) [0x558743e215d2] -> dovecot/imap [user3(a)email.com 35.67.148.57 APPEND](+0x10918) [0x558743e22918] -> dovecot/imap [user3(a)email.com 35.67.148.57 APPEND](command_exec+0x64) [0x558743e31614] -> dovecot/imap [user3(a)email.com 35.67.148.57 APPEND](client_command_cancel+0x49) [0x558743e2edc9] -> dovecot/imap [user3(a)email.com 35.67.148.57 APPEND](+0x1cef4) [0x558743e2eef4] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x12b) [0x7f73d16a8d3b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xcc) [0x7f73d16aa89c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7f73d16a9049] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f73d16a9288] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f73d1613bb3] -> dovecot/imap [user3(a)email.com 35.67.148.57 APPEND](main+0x342) [0x558743e21202] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f73d11f1555] -> dovecot/imap [user3(a)email.com 35.67.148.57 APPEND](+0xf405) [0x558743e21405] May 31 18:38:20 pop07 dovecot: imap(user3(a)email.com) session=<i5VgbaLD1f5QEZQ5>: Fatal: master: service(imap): child 9786 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Are already know bugs? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

3 5

Dovecot sieve filters
by j.emerlik 20 Sep '21

20 Sep '21

I'm have a problem where dovecot-sieve is used to run the script after moving emails from Junk Folder. config: imapsieve_mailbox2_name = * Imapsieve_mailbox2_from = INBOX.Junk imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/usr/local/lib/dovecot/sieve/report-ham.sieve filter: require [ "vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables", "fileinto", "envelope" ]; if environment :matches "imap.mailbox" "*" { set "mailbox" "${1}"; } if string "${mailbox}" "INBOX.Trash" { stop; } if environment :matches "imap.user" "*" { set "username" "${1}"; } pipe :copy "sa-learn-ham.sh" [ "${username}" ] It's working perfectly. However, I have a problem after adding : if envelope :is "from" "*" { set :lower "from" "${1}"; } pipe :copy "sa-learn-ham.sh" [ "${username}", "${from}" ] then appears error in log file: Error: sieve: report-ham: line 1: the envelope extension cannot be used in this context (needs access to message envelope) Is possible to use envelope extension to get sender address after moving message from Junk folder ? Regards, Jack

4 6

Mail error log polluted with dovecot imap errors
by Steve Dondley 17 Sep '21

17 Sep '21

I'm running debian bullseye. I've had issues running solr on debian due to some kind of bug I was able to patch by upgrading the os. After the upgrade, everything seems to work perfectly fine and the search feature in my client using solr now works. However, I get hundreds of these pairs of errors every minute in mail.err Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '102 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '103 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '104 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '105 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '106 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '118 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '132 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '133 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '134 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '135 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '136 Sep 17 04:47:52 email dovecot: imap: Error: ' Sep 17 04:47:52 email dovecot: imap(s)<8699><1eOe/CzMbOl/AAAB>: Error: fts_solr: received invalid uid '137 ...and so on The bug I patched also threw a similar kind of error: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970692 I don't know if this is another debian issue or a misconfiguration on my end. I'm not sure where to begin to look. Can someone please point me in the right direction?

1 2

Unprivileged users can't use doveadm anymore in 2.3.16
by dovecot＠ptld.com 17 Sep '21

17 Sep '21

What happened in 2.3.16 to doveadm? You can no longer use the command as an unprivileged user like you could in 2.3.8 Roundcube uses "doveadm pw" to change users passwords and runs as user apache. This works in 2.3.8 but in 2.3.16 you get an error. doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 19: ssl_key: Can't open file /etc/letsencrypt/live/example_cert/privkey.pem: Permission denied I tried "doveadm quota get ..." from the console as user apache and got the same error. I then tried running just "doveadm" and got the error, it wouldn't even display the help output. So it appears to not be directly related to using the "pw" feature. Just to trouble shoot i gave full read permission to privkey.pem just to see if doveadm would work. Doveadm still would not run for user apache but gave a different error: doveconf: Error: ssl enabled, but ssl_dh not set doveconf: Fatal: Invalid configuration Was this requirement to read the privkey.pem always there or just added in 2.3.16? Is this a deeper issue considering the ssl_dh error? Is there a way to fix this? Is this by design unprivileged user can no longer use doveadm?

3 2

Issue between roundcube and newer dovecot 2.3.16 with doveadm pw
by dovecot＠ptld.com 15 Sep '21

15 Sep '21

Aki; I know most likely this isn't dovecot's fault, however upgrading from 2.3.8 to 2.3.16 broke the password plugin for roundcube. Im only asking if you might know what changes in dovecot might have caused this incompatibility so i can fix it myself or point roundcube in the right direction to fix it. I submitted a bug report to roundcube with details of the issue. https://github.com/roundcube/roundcubemail/issues/8200

1 0

lmtp process dumps core after sieve error
by admin 15 Sep '21

15 Sep '21

Hi, We run dovecot + postfix + pigeonhole. Last week we observed some coredumps in dovecot's lmtp processes. For some emails, postfix mailq reported: > lost connection with nji9.de[/var/spool/postfix/private/dovecot-lmtp] while sending end of data -- message may be sent more than once Indeed, some users received some emails multiple times. dovecot.log contained a lot of related lines, all of them looking like this: > Sep 14 22:20:32 lmtp(user(a)example.com)<16323><abcdef:24>: Info: sieve: Execution of script /home/vmail/example.com/user/.dovecot.sieve failed, but implicit keep was successful (user logfile /home/vmail/example.com/user/.dovecot.sieve.log may reveal additional details) > Sep 14 22:20:32 lmtp(16323): Panic: file mail-user.c: line 229 (mail_user_deinit): assertion failed: ((*user)->refcount == 1) > Sep 14 22:20:32 lmtp(16323): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x43) [0x68ac383e6073] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x20) [0x68ac383e6190] -> /usr/lib/dovecot/libdovecot.so.0(+0xfaf1f) [0x68ac383f2f1f] -> /usr/lib/dovecot/libdovecot.so.0(+0xfafb1) [0x68ac383f2fb1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4cd20) [0x68ac38344d20] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x38bbc) [0x68ac384f6bbc] -> dovecot/lmtp(lmtp_local_data+0x400) [0xfb684d63190] -> dovecot/lmtp(client_default_cmd_data+0x19d) [0xfb684d61c5d] -> dovecot/lmtp(cmd_data_continue+0x191) [0xfb684d619e1] -> /usr/lib/dovecot/libdovecot.so.0(+0x6cb09) [0x68ac38364b09] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6b) [0x68ac38408ebb] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x13b) [0x68ac3840a5cb] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x51) [0x68ac38408f61] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x41) [0x68ac38409131] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x14) [0x68ac3837af74] -> dovecot/lmtp(main+0x235) [0xfb684d60615] -> /usr/lib/libc.so.6(__libc_start_main+0xd5) [0x68ac3814ab25] -> dovecot/lmtp(_start+0x2e) [0xfb684d6072e] > Sep 14 22:20:33 lmtp(16323): Fatal: master: service(lmtp): child 16323 killed with signal 6 (core dumped) Equally frequent, journalctl said: > Sep 14 22:20:33 nji9.de systemd-coredump[16358]: Process 16323 (lmtp) of user 0 dumped core. > Found module linux-vdso.so.1 with build-id: 7b6fd2add8450c7af3684522368e4ce83f762f41 > Found module libgcc_s.so.1 with build-id: 7f8508bb914546ada778809b64b99d234337d835 > Found module libffi.so.7 with build-id: de60e99f39569d11d09160bbdcd486cedc87d2b6 > Found module libp11-kit.so.0 with build-id: 5314ec746546ada6f442b6fdfae15eab9f6d3cdc > Found module libcrypt.so.2 with build-id: 3743451bdaf36f951f926927633fd964813025d0 > Found module librt.so.1 with build-id: 75484da2d6f1515189eefa076e0a40328834cd16 > Found module libnss_systemd.so.2 with build-id: 22990ff716d182c427e26b7a3cf94048b55b3e75 > Found module libnss_files.so.2 with build-id: 1a36dfc01d3a1010b2ee79766a24a8090a3266d5 > Found module libdovecot-sieve.so.0 with build-id: 8f87ae1b5f982453421532a7ac0f309813add7ce > Found module lib90_sieve_plugin.so with build-id: 4cd814cc28d0259b7f837b3b8583adabbf608d6a > Found module lib10_quota_plugin.so with build-id: a63664ff7754f0c234344a89f2d28aa3f6650929 > Found module libpthread.so.0 with build-id: 07c8f95b4f3251d08550217ad8a1f31066229996 > Found module libcrypto.so.1.1 with build-id: 6d23f0a3f354825868d044684fad31d482cc9210 > Found module libssl.so.1.1 with build-id: 959cd8f1dd43fc31aeb93caac4eda87c907ef18b > Found module libssl_iostream_openssl.so with build-id: 7cde2343f52a797e4fe77de7d0e7c1cb4983706b > Found module ld-linux-x86-64.so.2 with build-id: 040cc3dd10461562f177df39e3be2f3704258c3c > Found module libdl.so.2 with build-id: 5abc547e7b0949f89f3c0e21ab0c8331a7440a8a > Found module libc.so.6 with build-id: 4b406737057708c0e4c642345a703c47a61c73dc > Found module libdovecot.so.0 with build-id: e2c3dc8d5ee8012c83dc2a5f220de42e020857dc > Found module libdovecot-storage.so.0 with build-id: 1c80627fdc89752d8dc749ecfefae1e31445bb67 > Found module libdovecot-lda.so.0 with build-id: 826670da875938b71bd20af87dab4eb2cbbfef61 > Found module lmtp with build-id: 1f51ab7200356943590ecee21d298c808833d4e2 > Stack trace of thread 16323: > #0 0x000068ac3815fd22 raise (libc.so.6 + 0x3cd22) > #1 0x000068ac38149862 abort (libc.so.6 + 0x26862) > #2 0x000068ac38345084 n/a (libdovecot.so.0 + 0x4d084) > #3 0x000068ac383f2fb1 n/a (libdovecot.so.0 + 0xfafb1) > #4 0x000068ac38344d20 i_panic (libdovecot.so.0 + 0x4cd20) > #5 0x000068ac384f6bbc n/a (libdovecot-storage.so.0 + 0x38bbc) > #6 0x00000fb684d63190 lmtp_local_data (lmtp + 0x9190) > #7 0x00000fb684d61c5d client_default_cmd_data (lmtp + 0x7c5d) > #8 0x00000fb684d619e1 cmd_data_continue (lmtp + 0x79e1) > #9 0x000068ac38364b09 n/a (libdovecot.so.0 + 0x6cb09) > #10 0x000068ac38408ebb io_loop_call_io (libdovecot.so.0 + 0x110ebb) > #11 0x000068ac3840a5cb io_loop_handler_run_internal (libdovecot.so.0 + 0x1125cb) > #12 0x000068ac38408f61 io_loop_handler_run (libdovecot.so.0 + 0x110f61) > #13 0x000068ac38409131 io_loop_run (libdovecot.so.0 + 0x111131) > #14 0x000068ac3837af74 master_service_run (libdovecot.so.0 + 0x82f74) > #15 0x00000fb684d60615 main (lmtp + 0x6615) > #16 0x000068ac3814ab25 __libc_start_main (libc.so.6 + 0x27b25) > #17 0x00000fb684d6072e _start (lmtp + 0x672e) > Sep 14 22:20:33 nji9.de systemd[1]: systemd-coredump(a)32-16357-0.service: Deactivated successfully. The sieve logfile, which was mentioned in dovecot.log, contains: > sieve: info: started log at 2021-09-14 22:20:32 +0200. > error: msgid=<abcdefghi(a)example.com>: fileinto action: failed to store into mailbox 'INBOX.MyFolder': Mailbox doesn't exist: INBOX.MyFolder. After removing all failed sieve rules which appeared in the logs, the mail queue was processed without errors. There were no core dumps any more. The strange thing is that there are some failing sieve rules left. The sieve log of one user still contains errors. But there are no coredumps any more. > sieve: info: started log at 2021-09-14 23:30:31 +0200. > error: msgid=<abcdefghi(a)example.com>: fileinto action: failed to store into mailbox 'INBOX.OtherFolder': Mailbox doesn't exist: INBOX.OtherFolder. Dovecot version: 2.3.16 Operating system or Linux distribution name: Arch Linux CPU architecture: x86_64 Filesystem: ext4 Kernel: Linux nji9.de 5.13.16-hardened1-1-hardened #1 SMP PREEMPT Sun, 12 Sep 2021 20:28:26 +0000 x86_64 GNU/Linux I found a possibly related change (same error message as in the logs) in the dovecot changelog: > 2021-08-18 19:49:43 +0200 Timo Sirainen <timo.sirainen(a)open-xchange.com> (b401e41) > > imap: Fix mailbox leak if MOVE can't open the source mailbox > > Broken by 143b7c2b412ed8f155e812603fda81886bec466e > > Fixes: Panic: file mail-user.c: line 229 (mail_user_deinit): assertion > failed: ((*user)->refcount == 1) > > M src/imap/cmd-copy.c I don't know if that change fixes the issue. Note that there is no new dovecot release yet. Trying to reproduce the error would be hard because this is a production system. We have coredumps, but as they might contain sensitive information, we'd prefer to not send them over a public mailing list. Do you have any clue on this issue? Best regards, the nji9.de crew

2 1

Panic/Fatal error in lmtp when quota is full
by Alessio Cecchi 14 Sep '21

14 Sep '21

Hi, on dovecot 2.3.16 with delivery via LMTP I found many of this error when a user have the mailbox full and personal sieve rules: - lmtp.log: Sep 14 09:58:27 pop05 dovecot: lmtp(user1(a)company.com) session=<eAjRDSNWQGFCaQAAP27dBg>: sieve: deliverytime=122, msgid=<000601d7a8f8$fc350d50$f49f27f0$(a)company.com>, sender=user2(a)company.com, from=user2(a)company.com, subject="my subject 1": fileinto action: failed to store into mailbox 'INBOX/Personale': Quota exceeded (mailbox for user is full) Sep 14 09:58:27 pop05 dovecot: lmtp(user1(a)company.com) session=<eAjRDSNWQGFCaQAAP27dBg>: sieve: deliverytime=122, msgid=<000601d7a8f8$fc350d50$f49f27f0$(a)company.com>, sender=user2(a)company.com, from=user2(a)company.com, subject="my subject 1": failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full) Sep 14 09:58:27 pop05 dovecot: lmtp(user1(a)company.com) session=<eAjRDSNWQGFCaQAAP27dBg>: sieve: Execution of script /home/vmail/domains/company.com/user1/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /home/vmail/domains/company.com/user1/.dovecot.sieve.log may reveal additional details) Sep 14 09:58:27 pop05 dovecot: lmtp(26946): Panic: file mail-user.c: line 229 (mail_user_deinit): assertion failed: ((*user)->refcount == 1) Sep 14 09:58:27 pop05 dovecot: lmtp(26946): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f52dfb4e632] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f52dfb4e73e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf66fe) [0x7f52dfb5c6fe] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf67a1) [0x7f52dfb5c7a1] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [ 0x7f52dfaaba18] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x57567) [0x7f52dfe79567] -> dovecot/lmtp [10.0.2.26 DATA](lmtp_local_data+0x4dc) [0x55e09f333e2c] -> dovecot/lmtp [10.0.2.26 DATA](client_default_cmd_data+0x18b) [0x55e09f33273b] -> dovecot/lmtp [10.0.2.26 DATA](cmd_data_continue+0x204) [0x55e09f3324d4] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5fe64) [0x7f52dfac5e64] -> /usr/li b64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7f52dfb74ad5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12b) [0x7f52dfb7649b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7f52dfb74bd9] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f52dfb74e18] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f52dfadddf3] -> dovecot/lmtp [10.0.2.26 DATA](main+0x20b) [0x55e09f330f0b] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f52df6ba555] -> dovecot/lmtp [10.0.2.26 DATA](+0x6041) [0x55e09f331041] Sep 14 09:58:27 pop05 dovecot: lmtp(26946): Fatal: master: service(lmtp): child 26946 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) - sieve.log: sieve: info: started log at 2021-09-14 10:25:54 +0200. error: deliverytime=8, msgid=<49ef01d7a942$2168a200$6439e600$(a)company.com>, sender=sender1(a)company.com, from=sender1(a)company.com, subject="I: Undelivered Mail Returned to Sender": fileinto action: failed to store into mailbox 'INBOX/Comunicazioni': Quota exceeded (mailbox for user is full). error: deliverytime=9, msgid=<49ef01d7a942$2168a200$6439e600$(a)company.com>, sender=sender1(a)company.com, from=sender1(a)company.com, subject="I: Undelivered Mail Returned to Sender": failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full). Hope it can be fixed, Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 1

Password Schemes
by John Schmerold 14 Sep '21

14 Sep '21

My /etc/dovecot/conf.d/auth-passwdfile.conf.ext is configured to use MD5 passdb { driver = passwd-file args = scheme=MD5 username_format=%n /etc/exim4/domains/%d/passwd } userdb { driver = passwd-file args = username_format=%n /etc/exim4/domains/%d/passwd } /home/account/conf/mail/domain.com/passwd has a mixture of MD5 & SHA512-CRYPT: scanner:{MD5}$1$M5QuU7QI$AE7Nnorb8KC5KMvyYfVcr0:account:mail::/home/account:0:userdb_quota_rule=*:storage=0M test:{SHA512-CRYPT}$6$towo0IVjzBgZ0htU$uTFbyJ3aPunrhsEEC2alHz6SEuPyBdL3JYDWc6Z0ZtA2cMFjFVJNqAwn04OKQfsu99DNcDGu21zkvdYbsPmgJ0:account:mail::/home/account:0:userdb_quota_rule=*:storage=0M Everything is working fine, is this by design? In other words does the {MD5} vs {SHA512-CRYPT} in passwd over-rule auth-passwdfile.conf.ext ? -- John Schmerold Katy Computer Systems, Inc https://katycomputer.com St Louis

3 2

Re: Storing Last Login Plugin value in SQL
by dovecot＠ptld.com 14 Sep '21

14 Sep '21

> Assuming you use MariaDB / MySQL, you create this trigger in the > database. > Assuming your int/bigint/varchar column is lastlogin and the table name > is mailacct, > the trigger will update the datetime `logindate` column whenever the > table is updated, > by whatever existing queries you have. This is your recourse when you > can't get your > queries to do the right thing in the first place. Thank you for the solution of using sql triggers. I was able to get it working that way. I hope it doesn't add too much overhead as it feels like a band-aid and duct-tape fix.

2 1

submission server fails to relay messages
by Шварц Сергей Владимирович 13 Sep '21

13 Sep '21

Hi guys! I'm using dovecot submission server for clients to send emails and relay them to postfix. Everything works fine unless a client tries to send large (40Mbs) messages. No big deal one can say just set "message_size_limit = 314572800" in postfix and it should just work, but no, it does not, client gets "552 5.2.3 Message size exceeds administrative limit.". I've increased verbosity for smtpd process and get this logs for a failed attempt Sep 12 13:43:21 mx10 postfix/smtpd[73602]: connection established > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: master_notify: status 0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: name_mask: resource > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: name_mask: software > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: watchdog_start: 0x563f80b341b0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 5 for > 0x7fdef6cf4700 0x563f80b393d0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 5 for > 0x7fdef6cf4700 0x563f80b1ee10 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 100 for > 0x7fdef6d56b20 0x0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 1000 for > 0x7fdef6cf4720 0x563f80b1ee10 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 1000 for > 0x7fdef6cf4720 0x563f80b393d0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: select_delay 0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: timer > 0x7fdef6cf4700 0x563f80b393d0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: rewrite stream disconnect > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_disable_readwrite: fd 20 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_cancel_timer: > 0x7fdef6cf4700 0x563f80b393d0 -1 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_cancel_timer: > 0x7fdef6cf4720 0x563f80b393d0 985 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: timer > 0x7fdef6cf4700 0x563f80b1ee10 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: proxymap stream disconnect > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_disable_readwrite: fd 10 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_cancel_timer: > 0x7fdef6cf4700 0x563f80b1ee10 -1 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_cancel_timer: > 0x7fdef6cf4720 0x563f80b1ee10 985 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: watchdog_stop: 0x563f80b341b0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: watchdog_start: 0x563f80b341b0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: connect from > localhost[127.0.0.1] > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 85 for > 0x7fdef6d56b20 0x0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: localhost: no > match > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: select_delay 85 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: 127.0.0.1: > no match > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: localhost: no > match > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: 127.0.0.1: > no match > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: smtp_stream_setup: maxtime=300 > enable_deadline=0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_hostname: > smtpd_client_event_limit_exceptions: localhost ~? 127.0.0.0/8 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_hostaddr: > smtpd_client_event_limit_exceptions: 127.0.0.1 ~? 127.0.0.0/8 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 220 > mx10 ESMTP Postfix (Debian/GNU) > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: watchdog_pat: 0x5609a03c01b0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: vstream_fflush_some: fd 10 > flush 47 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: vstream_buf_get_ready: fd 10 > got 21 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: < localhost[127.0.0.1]: EHLO > mx10 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: localhost: no > match > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: 127.0.0.1: > no match > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 250-mx10 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: > 250-PIPELINING > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: > 250-SIZE 314572800 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 250-VRFY > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 250-ETRN > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: > 250-ENHANCEDSTATUSCODES > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: > 250-8BITMIME > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 250-DSN > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 250 > CHUNKING > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: watchdog_pat: 0x5609a03c01b0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: vstream_fflush_some: fd 10 > flush 138 > Sep 12 13:43:22 mx10 postfix/smtpd[73602]: vstream_buf_get_ready: fd 10 > got 6 > Sep 12 13:43:22 mx10 postfix/smtpd[73602]: < localhost[127.0.0.1]: QUIT > Sep 12 13:43:22 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 221 > 2.0.0 Bye > looks like submission server just quits if I configure imap client /Thunderbird to connect directly to postfix everything works just fine. doveconf -n output is attached just in case

2 1

Storing Last Login Plugin value in SQL
by dovecot＠ptld.com 13 Sep '21

13 Sep '21

The last-login plugin sends a number (epoch seconds) as uint or string in a query to sql. If i create a column type in sql of varchar() the number is saved in the column as a string, but not very useful. I can not figure out how to get that value into a date/time column such as date, datetime or timestamp. All three cause an error of Incorrect datetime value: '1631556506' for column. Anyone have any idea how to get the last-login plugin to update a date/time column in sql?

2 3

Problem with copy e-mails via doveadm
by Christian Küppers 13 Sep '21

13 Sep '21

2 12

Restricting commands used in http api
by Christian Küppers 13 Sep '21

13 Sep '21

Hello, is it possible to restrict api methods (https://doc.dovecot.org/admin_manual/doveadm_http_api/#api-methods) without restricting doveadm usage on console. something like: service doveadm { unix_listener doveadm-server { user = vmail } inet_listener { port = 2425 allowed_commands = ALL } inet_listener http { port = 8080 allowed_commands = fetch, copy, search #ssl = yes # uncomment to enable https } } Reason for question: We want to be able to use all commands as administrators on console but some external software using the dovecot api should not be able to do admin like tasks like "doveadm director flush". our setup: multiple replicated dovecot backend servers frontend with dovecot director ring and proxy enabled (provides api endpoint) Kind regards, Christian Küppers Expert Administrator onOffice GmbH Charlottenburger Allee 5 | 52068 Aachen Tel. +49 (0)241 446 86-0 | Fax. +49 (0)241 446 86-250 E-Mail:c.kueppers@onoffice.de| Web:www.onOffice.com Registergericht: Amtsgericht Aachen, HRB 21420 Geschäftsführer: Dipl.-Kfm. Stefan Mantl Prokuristen: Janosch Reuschenbach, Kristina Andresen, Christian Mähringer

1 1

SQL help please (Mysql/MariaDB).
by C. Petro 12 Sep '21

12 Sep '21

I'm trying to build a mail server for a friend using Postfix, Dovecot and Postfixadmin, using Mariadb as the backend for user information and authentication. I've got it *almost* working. (dovecot -n at the bottom because I don't think the problem is in the SQL) I have things up to the point where mail comes in, and where you can get Thunderbird to connect to Dovecot, but delivery is looking at a different directory than IMAP: root@mailserver:/var/mail/vmail# find ./ ./ ./petro(a)republicofmean.com ./petro(a)republicofmean.com/dovecot.index.log ./petro(a)republicofmean.com/dovecot-uidvalidity.6136d995 ./petro(a)republicofmean.com/tmp <...> ./petro(a)republicofmean.com/new ./petro(a)republicofmean.com/subscriptions ./republicofmean.com ./republicofmean.com/petro ./republicofmean.com/petro/tmp ./republicofmean.com/petro/cur ./republicofmean.com/petro/new ./republicofmean.com/petro/new/1630897562.Vfd00Ib40009M307139.mailserver <....> ./republicofmean.com/petro/new/1630899062.Vfd00Ib40011M264001.mailserver ./republicofmean.com/cer ./republicofmean.com/cer/tmp ./republicofmean.com/cer/cur ./republicofmean.com/cer/new ./republicofmean.com/cer/new/1630900562.Vfd00Ib40013M218855.mailserver ./republicofmean.com/cer/new/1630899062.Vfd00Ib40010M259724.mailserver The SQL I think Dovecot is using: root@mailserver:/etc/dovecot# grep -i select dovecot-sql.conf.ext | grep -v "^#" password_query = SELECT username as user, domain, password FROM mailbox WHERE username = '%u' user_query = select CONCAT("/var/mail/vmail/",maildir) as home, 500 as uid, 500 as gid from mailbox where username="%u" Here's what Postfix is using: mysql_virtual_alias_domain_catchall_maps.cf: query = SELECT goto FROM alias,alias_domain WHERE alias_domain.alias_domain = '%d' and alias.address = CONCAT('@', alias_domain.target_domain) AND alias.active = 1 AND alias_domain.active='1' mysql_virtual_alias_domain_mailbox_maps.cf: query = SELECT maildir FROM mailbox,alias_domain WHERE alias_domain.alias_domain = '%d' and mailbox.username = CONCAT('%u', '@', alias_domain.target_domain) AND mailbox.active = 1 AND alias_domain.active='1' mysql_virtual_alias_domain_maps.cf: query = SELECT goto FROM alias,alias_domain WHERE alias_domain.alias_domain = '%d' and alias.address = CONCAT('%u', '@', alias_domain.target_domain) AND alias.active = 1 AND alias_domain.active='1' mysql_virtual_alias_maps.cf: query = SELECT goto FROM alias WHERE address='%s' AND active = '1' mysql_virtual_domains_maps.cf: query = SELECT domain FROM domain WHERE domain='%s' AND active = '1' mysql_virtual_mailbox_limit_maps.cf: query = SELECT quota FROM mailbox WHERE username='%s' AND active = '1' mysql_virtual_mailbox_maps.cf: query = SELECT maildir FROM mailbox WHERE username='%s' AND active = '1' # dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-81-generic x86_64 Ubuntu 20.04.3 LTS ext4 # Hostname: <redacted> auth_mechanisms = plain login log_path = /var/log/dovecot.log login_greeting = Not your mail server mail_location = maildir:/var/mail/vmail/%u/ mail_max_userip_connections = 50 mail_privileged_group = vmail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocols = " imap lmtp pop3 submission" service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = </etc/letsencrypt/live/<redacted>/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver =

3 5

Re: Problem with the dovecot-fts-xapian package.
by Bob Marcan 12 Sep '21

12 Sep '21

On Sun, 12 Sep 2021 11:36:46 +0100 Joan Moreau <jom(a)grosjo.net> wrote: > This is where I am for now : > > https://koji.fedoraproject.org/koji/packageinfo?packageID=34417 > > Probably, I should wait for Fedora batch programs to push that into main rep > > On 2021-09-12 11:18, Joan Moreau wrote: > > > Hi Bob, > > > > I am trying to achieve that. > > > > But do you know the process of pushing an update as a maintainer, in > fedore repositories ? > > > > Thank you > > > > On 2021-09-12 11:02, Bob Marcan wrote: > > On Sun, 12 Sep 2021 09:45:35 +0100 > > Joan Moreau <jom(a)grosjo.net> wrote: > > > > Thank you for notice. > > > > What is the process to rebuild the package with recent dovecot, as > (instead of existing 1.4.12-1) ? > > There are no (yet) 1.4.12-2 in updates-testing or > updates-testing-modular repository. > > Should i'll wait for update? > > BR, Bob Got the new version and there is no more API mismatch. It's not so important for me, since i'm retired and i'm running this on my home computer. But i think it needs more support from te dovecot group. There a lot file protection issues nad lack of documentation on dovecot side. BR, Bob

3 2

suse.de dovecot issues
by Bernhard M. Wiedemann 12 Sep '21

12 Sep '21

Hi, I am one of the people taking over our new suse.de email setup (consisting of dovecot+rspamd+postfix) and wanted to report some issues we experience: 1. we use dovecot-director to distribute users between 2 backend servers that share an NFS mount. We found that it proxies lmtp to a different backend than imap of the same user and that caused NFS stale-filehandle errors on the dovecot-uidlist. It then proceeds to re-generate the dovecot-uidlist with new UIDs that creates trouble for users. a) shouldn't dovecot use locks (fcntl or flock) to protect such files from concurrent updates? b) could it generate uidlist in a way that re-generating it, assigns the same UIDs again? E.g. via hash over file content c) how to get dovecot-director to send all traffic for a user to one backend? 2. We have 2 backends so that we can do maintenance on one of them while users can still access their emails through the other backend. However, we found that stopping dovecot on one backend left users unable to access their mails. Maybe this is related to how user auth works? How to get this HA setup right, so that we don't have a single point of failure? grep PRETTY /etc/os-release PRETTY_NAME="SUSE Linux Enterprise Server 15 SP3" rpm -q dovecot23 dovecot23-2.3.15 https://www.zq1.de/~bernhard/temp/dovecot/ has some sysreports. Ciao Bernhard M.

5 12

Problem with the dovecot-fts-xapian package.
by Bob Marcan 12 Sep '21

12 Sep '21

Problem with the dovecot-fts-xapian package. Fedora 34 with latest updates. dovecot-2.3.16-1.fc34.x86_64 dovecot-fts-xapian-1.4.12-1.fc34.x86_64 [root@smicro conf.d]# systemctl restart dovecot [root@smicro conf.d]# doveadm index -A \* Fatal: Couldn't load required plugin /usr/lib64/dovecot/lib21_fts_xapian_plugin.so: Module is for different ABI version 2.3.ABIv15(2.3.15) (we have 2.3.ABIv16(2.3.16)) BR, Bob

2 1

Looking for SNI feature
by Sherin A 10 Sep '21

10 Sep '21

Hello, I am looking for an alternative feature for SNI certificates in dovecout. Current dovecot need to integreate the sni codes into the configuration as follows, local_name imap.example.org { ssl_cert = </etc/ssl/certs/imap.example.org.crt ssl_key = </etc/ssl/private/imap.example.org.key } I have thousands of domain in the server. So during the ssl certificate creation of each domain , I need to add the codes to the configuration and reload the service. That looks not a suitable feature. So my question is Do dovecot have a feature to read the certificate of every domain from another service , let us say I have service that will send the above sni setting to a socket and dovecot read it from that socket. Kindly let me know if dovecot have any such feature exists. This feature may be like the authentication using dictionary proxy service ? -- Regards Sherin A

1 0

Failed to do incremental sync
by Andrea Gabellini 09 Sep '21

09 Sep '21

Hello, Two dovecot server with replication and version 2.3.10.1 Today i have many warnings like those: Sep 9 12:13:43 dovecot: doveadm: Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (uidnext 4465 < 4517) Sep 9 12:13:56 dovecot: doveadm: Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 4016 no longer in transaction log (highest=4106, last_common_uid=3451, nextuid=3452)) Do you have some suggestions on how to debug this? Or something I can check? Thanks, Andrea -- __________________________ There were computers in Biblical times. Eve had an Apple. __________________________ 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.

2 2

Using %{ssl_security} in the policy server
by Andrea Gabellini 09 Sep '21

09 Sep '21

Hello, I am looking for a way to verify, at the moment of the connection, who does not use encryption or uses weak encryption. My choice was the use of the policy server because I would like to block only a certain number of users per day, so as not to overload the support service. In the call to the policy server, only tls = true / false is passed as information. I would also be interested in %{ssl_security} but it is not present among the usable variables. Is there any way, perhaps using userdb/passdb, to be able to pass this variable to the policy server? Thanks, Andrea -- __________________________ Seen it all, done it all, can't remember most of it __________________________ 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.

2 1

SSL errors after certificate renewal
by Amol Kulkarni 08 Sep '21

08 Sep '21

Hello, After I replaced my certificate with a new one yesterday, I'm seeing some ssl related errors. There are successful pop/imap logins using SSL also. So I think the certificate in itself is fine. No user has complained as yet, so I don't know for sure. However the count of errors has surely increased after installing the new certificate. There are 2 errors seen : dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=, lip =, TLS handshaking: SSL_accept() failed: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown: SSL alert number 46, session=<9m0AnVnL 2pHf4hso> dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=, lip =, TLS: SSL_read() failed: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate: SSL alert number 42, session=<ww/b6VfLmeR7yTog> Kindly help with some pointers. Thanks and Regards, Amol

8 8

How can I always send a vacation response with sieve?
by Steve Dondley 08 Sep '21

08 Sep '21

I don't want dovecot to wait X days before sending out another vacation response. However, setting the :days to "0" doesn't work. RFC https://www.rfc-editor.org/rfc/rfc5230.html#section-4.1 says: 4.1. Days Parameter The ":days" argument is used to specify the period in which addresses are kept and are not responded to, and is always specified in days. The minimum value used for this parameter is normally 1. Sites MAY define a different minimum value as long as the minimum is greater than 0. Sites MAY also define a maximum days value, which MUST be greater than 7, and SHOULD be greater than 30. If ":days" is omitted, the default value is either 7 or the minimum value (as defined above), whichever is greater. If the parameter given to ":days" is less than the minimum value, then the minimum value is used instead. If ":days" exceeds the site-defined maximum, the site-defined maximum is used instead. Sorry if this is more of a sieve question and is slightly off topic.

5 7

Dovecot - FTS Solr: disk usage & position information?
by Vincent Brillault 07 Sep '21

07 Sep '21

Dear all, On a local dovecot cluster currently hosting roughly 2.1TB of data, using Solr as its FTS backend, we now have 256GB of data in Solr, split in 12 shard (to which replication adds 256GB of data through 12 additional cores). I'm now trying to see if we can optimize that data. Looking at one core at random (22G), I see that the data is split mostly between - .pos files: 12G - .tim files: 4.2G - .doc files: 3.8G - .cfs files: 1.8G Looking around a bit, I found https://lucene.apache.org/core/6_2_0/core/org/apache/lucene/codecs/lucene50… (which is unfortunately a bit outdated I think) that explains each file content: - .tim: Term Dictionary - .tip: Term Index - .doc: Frequencies and Skip Data - .pos: Positions - .pay: Payloads and Offsets So clearly the file naming convention have changed, but still if .pos is really position information ("lists of positions that each term occurs at within documents."), this sounds rather useless for the dovecot integration. Looking at Solr documentation on search (https://solr.apache.org/guide/8_6/the-standard-query-parser.html) it seems that position aware query are written as `"term1 term2"~[0-9]+`. Looking at the dovecot code (https://github.com/dovecot/core/blob/master/src/plugins/fts-solr/fts-backen…) I don't see this kind of query being made, `~` only being used for fuzzy search. Has anyone ever tried to set omitTermFreqAndPositions or omitPositions to true for the text fields in the Solr Schema? It sounds that this could improve a lot the disk space used by Solr without losing any feature. The only thing I'm not too clear about is the "autoGeneratePhraseQueries" which is enabled in https://github.com/dovecot/core/blob/master/doc/solr-schema-7.7.0.xml. Thanks in advance, Vincent Brillault PS: I have attached the schema we are using for completeness. It's based on the one in the dovecot repo, with a bit of simplification for headers that don't really require as much massaging.

3 7

Solr FTS - when does indexing happen?
by Shawn Heisey 06 Sep '21

06 Sep '21

I have Solr FTS on my dovecot install. I followed the instructions on the dovecot wiki. How long a delay should I expect to see between new mail being delivered with the dovecot LDA and an indexing request sent to Solr? Because I get a LOT of email from various mailing lists, and I do not see any activity in Solr's log. When I did doveadm index -A -q '*' there was a lot of indexing activity in Solr's log, as expected. One time I looked at the Solr index and it had been 23 hours since it's last update ... I can guarantee that I received a lot of new messages in that time. What do I need to look at for further troubleshooting? I can confirm that when I issue a search in the TypeApp app on my phone (an IMAP app for android), I see the query in Solr's logfile. Thanks, Shawn

2 4

Dovecot, Last Login Plugin and PostfixAdmin
by White, Daniel E. (GSFC-770.0)[NICS] 03 Sep '21

03 Sep '21

https://doc.dovecot.org/configuration_manual/lastlogin_plugin/ Is there any documentation about how to get the "Last Login" info into the PostfixAdmin database ?

2 1

100 MB RAM per clinet in an imap-proxy setup ...
by Tobias Oetiker 03 Sep '21

03 Sep '21

Hi All, I spent some quality time yesterday, tuning dovecot on a server which serves as an imap-proxy in front of a zimbra setup the imap proxy does ldap client-cert authentication and works well. BUT I found that the imap-login processes seem to gain 100 MB per connection they are accepting ... this seems pretty hefty. It does not seem to be a leak, since the setup is stable when client_limit and process_limit are set appropriately. Any ideas what part of the code I should be looking at ? Or is this a configuration problem ? cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi(a)oetiker.ch +41 62 775 9902

2 4

Using a DICT PROXY with SQL for AUTH
by dovecot＠ptld.com 02 Sep '21

02 Sep '21

https://doc.dovecot.org/configuration_manual/dict/#dict-sql https://doc.dovecot.org/configuration_manual/dict/#dict-proxy https://doc.dovecot.org/configuration_manual/dict/proxy/ I can't get the complete picture from these pages how to implement proxy with sql. I have direct sql setup now, how do i use this with proxy? passdb { driver = sql args = /etc/dovecot/mysql_login } userdb { driver = prefetch } /etc/dovecot/mysql_login: driver = mysql connect = host=/var/lib/mysql/mysql.sock dbname=redacted user=redacted password=redacted default_pass_scheme = redacted password_query = SELECT ... I feel like there is a disconnect. It says how to make a proxy service with service dict{} and it says put a dict name but where? And how do i connect my password_query to a dict? Or can you not use the proxy service for auth service? "The <destination dict> contains the dict name in the dict { .. } settings" service dict(1) { unix_listener dict(2) { mode = 0600 user = vmail } } What is the dict name, the first dict(1) or the second dict(2) or neither? Can you change "dict" in the service or unix_listner or does it always have to be "dict"? Can you use dict-async with sql?

1 0

Over Quota Reply Codes
by dovecot＠ptld.com 02 Sep '21

02 Sep '21

Dovecot quota plugin returns code 554 5.2.2 when a user inbox is full. Why 554 (transaction failed) instead of 552 (exceeded storage allocation)? Im curious behind the logic as im trying to determine the best code to use to reject a user sending more emails than their number-of-emails-limit quota. If anyone has an option to share on the best code to return it would be appreciated; 550 (policy reasons) 552 (exceeded ... allocation) 554 (transaction failed) 5.2.2 (mailbox full) 5.5.3 (Too many recipients) 5.7.0 (Other security related) 5.7.1 (delivery not authorized) Which fits best?

2 1

maildirfolder file created in maildir root during auto-creation with 2.3.4.1 but not 2.2.27
by Christian Balzer 02 Sep '21

02 Sep '21

Hello, as the tin says. I have several servers running 2.2.27 (Debian stretch) and am adding new ones with 2.3.4.1 (Debian buster). The configs were upgraded where needed but neither 10-mail.conf nor 15-mailboxes.conf were changed. 15-mailboxes is all commented out (I guess the default is auto-create, which isn't documented anywhere I could find) and the only non-comments in 10-mail.conf are --- mail_location = maildir:%h mail_privileged_group = mail --- So yes, no namespaces are explicitly defined/declared. The 2.3.4.1 version wrongly creates a maildirfolder file in the home directory (maildir root), preventing exim from correctly creating/using maildirsize. a) Is this expected behavior and can it be changed? b) How can I disable inbox auto-creation if a) doesn't pan out? Thanks, Christian -- Christian Balzer Network/Systems Engineer chibi(a)gol.com Rakuten Mobile Inc.

2 5

Duplicate plugins - FTS Xapian
by Joan Moreau 01 Sep '21

01 Sep '21

Hi There seems to be 2 plugins doing the same thins - https://github.com/slusarz/dovecot-fts-flatcurve/ - https://github.com/grosjo/fts-xapian/ (mine) Both are in the doc of dovecot https://doc.dovecot.org/configuration_manual/fts/ I am currently working hard to push it to RPM package, and plugin is already approved by ArchLinux and Debian Isn't there double work here ? Thanks JM

7 9

User deleted the folder
by Казанцев Владимир Серге евич 01 Sep '21

01 Sep '21

Hello, please tell me what kind of information is stored in this file: doveadm dump -t mailboxlog dovecot.mailbox.log -- С уважением, Казанцев Владимир Сергеевич системный администратор отдела ИТ АО «Елецгидроагрегат» Тел. +7 (47467) 78-1-16, Моб. +7 980 263 26 69 kazantsev.vs(a)gidroagregat.ru <mailto:kazantsev.vs@gidroagregat.ru> /Настоящее почтовое сообщение является собственностью АО «Елецгидроагрегат», конфиденциально и предназначено для получателя письма. Если Вы не являетесь получателем, вероятнее всего Вы получили письмо по ошибке и в этом случае любое его использование, перенаправление, вывод на печать или копирование данного сообщения запрещаются. Если Вы получили сообщение по ошибке, пожалуйста свяжитесь с отправителем письма. Любые взгляды или мнения, представленные в письме, могут не совпадать с точкой зрения АО «Елецгидроагрегат» и отражают только точку зрения отправителя. Однако настоящее почтовое сообщение и любые вложения в него не содержат вирусов или каких-то других недостатков, которые могли бы причинить вред Вашей системе; тем не менее, АО «Елецгидроагрегат» не несет никакой ответственности за причинение ущерба результате получения данного письма./

1 0

User deleted the folder
by Казанцев Владимир Серге евич 01 Sep '21

01 Sep '21

Hello, please tell me what kind of information is stored in this file: doveadm dump -t mailboxlog dovecot.mailbox.log -- С уважением, Казанцев Владимир Сергеевич системный администратор отдела ИТ АО «Елецгидроагрегат» Тел. +7 (47467) 78-1-16, Моб. +7 980 263 26 69 kazantsev.vs(a)gidroagregat.ru <mailto:kazantsev.vs@gidroagregat.ru> /Настоящее почтовое сообщение является собственностью АО «Елецгидроагрегат», конфиденциально и предназначено для получателя письма. Если Вы не являетесь получателем, вероятнее всего Вы получили письмо по ошибке и в этом случае любое его использование, перенаправление, вывод на печать или копирование данного сообщения запрещаются. Если Вы получили сообщение по ошибке, пожалуйста свяжитесь с отправителем письма. Любые взгляды или мнения, представленные в письме, могут не совпадать с точкой зрения АО «Елецгидроагрегат» и отражают только точку зрения отправителя. Однако настоящее почтовое сообщение и любые вложения в него не содержат вирусов или каких-то других недостатков, которые могли бы причинить вред Вашей системе; тем не менее, АО «Елецгидроагрегат» не несет никакой ответственности за причинение ущерба результате получения данного письма./

1 0

indexer crash
by Onno Molenkamp 31 Aug '21

31 Aug '21

Hi, Because I was getting segfaults in libc in calloc calls by the indexer process of Dovecot 2.3.16, I ran indexer with valgrind to look for possible memory corruption. It did indeed find that indexer was accessing memory that had already been freed, I've attached the log file. I've then tried running Dovecot with the fix in commit 97367ef61784a364ccf615cb816be6492329050d, but that didn't make any difference. Reverting (just the code in src/indexer) to the last revision before the recent rewrite to use connection.c (d76761698a06bab60a741c6794252fddec4292ef) did: valgrind doesn't log any errors anymore, and indexer has stopped crashing. Onno

3 3

Dovecot Director: Preferred backend server
by Steven Varco 31 Aug '21

31 Aug '21

Hi All I have a dovecot cluster with directror and two IMAP Servers behind. Since they are in geographical different locations I would like to have users to go to a specific IMAP backend server (if both are up) and only switch to the other if one goes down (failover). As to my current knowledge the PassDB extra field „host=„ is not suitable in this case as it would never route the client to a different backend, even if the „user specific backend“ would be down. Is their a way in dovecot to achive this? As far as I searched the documentation I could not find any information on this so far. If not, it may also help if I could get certain users to „initially" go to a specific backend (since director usually routes a client/user to the same backend server it initially connects) and therefore it would be interesting to know how dovecot director chooses wether a user goes to server1 or server2? And if a client already gets to server2, how to bring it „back“ to server1? thanks in advance, Steven -- https://steven.varco.ch/ https://www.tech-island.com/

4 7

lmtp panic with 2.3.16 (runnung ubuntu) and larger mails
by Friedhelm Buescher 30 Aug '21

30 Aug '21

Hi, when sending larger Mails (> 1MB, for example a jpg attachment), the lmtp crashes: ######################################################################### syslog: Aug 29 17:05:34 mail dovecot: lmtp(xxxx)<720677><5RuZHDCiK2El/woAkAJtwA>: Panic: Buffer write out of range (0 + 1) Aug 29 17:05:34 mail dovecot: lmtp(xxxx)<720677><5RuZHDCiK2El/woAkAJtwA>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x41) [0x7f10ae1fb151] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x22) [0x7f10ae1fb272] -> /usr/lib/dovecot/libdovecot.so.0(+0x1092eb) [0x7f10ae2082eb] -> /usr/lib/dovecot/libdovecot.so.0(+0x109387) [0x7f10ae208387] -> /usr/lib/dovecot/libdovecot.so.0(+0x5d018) [0x7f10ae15c018] -> /usr/lib/dovecot/libdovecot.so.0(+0x5bee1) [0x7f10ae15aee1] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_binary_emit_integer+0x6a) [0x7f10ad79dfea] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_binary_save+0x1e3) [0x7f10ad79c553] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_binary_file_update_resource_usage+0x128) [0x7f10ad79dcc8] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_binary_close+0x7d) [0x7f10ad79ab4d] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3f65) [0x7f10ae0f3f65] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x17a) [0x7f10ae4490ea] -> dovecot/lmtp(lmtp_local_default_deliver+0x1d8) [0x557cc4da83c8] -> dovecot/lmtp(lmtp_local_data+0x5ac) [0x557cc4da8b1c] -> dovecot/lmtp(client_default_cmd_data+0x191) [0x557cc4da74a1] -> dovecot/lmtp(cmd_data_continue+0x180) [0x557cc4da7230] -> /usr/lib/dovecot/libdovecot.so.0(+0x7c286) [0x7f10ae17b286] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6d) [0x7f10ae21e67d] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x145) [0x7f10ae21fd15] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x54) [0x7f10ae21e724] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f10ae21e890] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x17) [0x7f10ae1913a7] -> dovecot/lmtp(main+0x22f) [0x557cc4da5edf] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f10adf250b3] -> dovecot/lmtp(_start+0x2e) [0x557cc4da5fee] Aug 29 17:05:34 mail dovecot: lmtp(xxxx)<720677><5RuZHDCiK2El/woAkAJtwA>: Fatal: master: service(lmtp): child 720677 killed with signal 6 (core dumped) ######################################################################### uname -a Linux mail 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Installed Packages: dovecot-lmtpd=2:2.3.16-2+ubuntu20.04 dovecot-mysql=2:2.3.16-2+ubuntu20.04 dovecot-imapd=2:2.3.16-2+ubuntu20.04 dovecot-sieve=2:2.3.16-2+ubuntu20.04 dovecot-pop3d=2:2.3.16-2+ubuntu20.04 dovecot-lucene=2:2.3.16-2+ubuntu20.04 dovecot-core=2:2.3.16-2+ubuntu20.04 dovecot-managesieved=2:2.3.16-2+ubuntu20.04 dovecot-solr=2:2.3.16-2+ubuntu20.04 postfix=3.4.13-0ubuntu1.1 Tried to downgrade to dovecot-lmtpd=2:2.3.15-1+ubuntu20.04 dovecot-mysql=2:2.3.15-1+ubuntu20.04 dovecot-imapd=2:2.3.15-1+ubuntu20.04 dovecot-sieve=2:2.3.15-1+ubuntu20.04 dovecot-pop3d=2:2.3.15-1+ubuntu20.04 dovecot-lucene=2:2.3.15-1+ubuntu20.04 dovecot-core=2:2.3.15-1+ubuntu20.04 dovecot-managesieved=2:2.3.15-1+ubuntu20.04 dovecot-solr=2:2.3.15-1+ubuntu20.04 postfix=3.4.10-1ubuntu1 , which does not solve the error. ######################################################################### config: # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Linux 5.4.0-81-generic x86_64 Ubuntu 20.04.3 LTS ext4 # Hostname: xxxx auth_verbose_passwords = plain lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_location = maildir:/var/maildirs/%u mail_plugins = " quota acl fts fts_solr" mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace { list = children location = maildir:%%h:INDEX=%h/shared/%%u:CONTROL=%h/shared/%%u prefix = shared.%%u. separator = . subscriptions = no type = shared } namespace inbox { inbox = yes location = prefix = separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile fts = solr fts_autoindex = yes fts_solr = url=http://127.0.0.1:8983/solr/dovecot/ recipient_delimiter = . sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve pop3" recipient_delimiter = . service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = postfix user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } vsz_limit = 1 G } ssl = required ssl_cert = </etc/letsencrypt/live/xxx/fullchain.pem ssl_cipher_list = ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_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 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota acl fts fts_solr sieve notify push_notification" postmaster_address = postmaster@xxx } protocol lda { mail_plugins = " quota acl fts fts_solr sieve fts fts_solr notify push_notification" } protocol imap { mail_plugins = quota imap_quota fts fts_solr } ######################################################################### sieve-file involved: # Sieve Filter # Generated by Ingo (http://www.horde.org/apps/ingo/) (05/17/2019, 06:17:18 PM) require ["fileinto", "imap4flags", "mailbox", "subaddress", "envelope", "variables", "body", "regex", "copy"]; # PDFs nach attachments speichern, damit diese lokal gespeichert werden koennen .. if body :raw :regex ["filename=.+\\.pdf"] { fileinto :create :copy "INBOX.attachments"; }

2 2

Local auth works with dovecot-proxy, remote does not
by Camilo Sperberg 30 Aug '21

30 Aug '21

Hi list! I've configured dovecot-proxy to redirect users to another server if their data is indeed on that other server. Webmail (which runs on the same machine) works perfectly fine, but clients such as Thunderbird and Outlook do not work as intended, I suspect it to be a problem with the IP that dovecot-proxy sees, but I can't figure out what is wrong: I've already done a lot of Googling and also tried to change the login_trusted_networks value, but to no avail. I've enabled debug log and here is the relevant part of a call that fails and another one that succeeds (FYI 10.164.0.3 is the machine that is doing the proxying and where webmail is located, 10.164.0.20 is the 'node', these logs come from that node, doveconf -n is also provided in the gist): https://gist.github.com/unreal4u/64de0f05b6e3b98034cdb0ae52ce1196 So as far as I can interpret the logs, in the failure case it is basically saying it should go to the node, despite it already being on that node: Aug 24 11:29:07 mail-node-2 dovecot: auth: Debug: client passdb out: OK#0112#011user=me(a)XXXXXX.XX #011host=10.164.0.20#011port=143#011proxy#011pass=<hidden> In the success case, I don't see any mention of a proxy: Aug 24 11:35:21 mail-node-2 dovecot: auth: Debug: client passdb out: OK#0116#011user=me(a)XXXXXXXXX.XX What am I missing here? Has this something to do with authentication-allow-nets or authentication-allow-real-nets ? If so: where to define it? Is there something else I'm missing? Thanks in advance for your help, Camilo Sperberg

1 1

tls_early_post_process_client_hello:unsupported protocol
by Elise 30 Aug '21

30 Aug '21

I just read a line in my logfile that I haven't noticed before: Aug 29 22:17:23 <myserver> dovecot[50098]: imap-login: Disconnected: Connection closed: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol (no auth attempts in 2 secs): user=<>, rip=104.152.52.31, lip=10.10.10.37, TLS handshaking: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol, session=</w+MZ7jKvLhomDQf> Is this a TLS 1.3 related issue? /elise

2 1

%{cert} variable
by Andrea Gabellini 27 Aug '21

27 Aug '21

Hello, I am using Dovecot version 2.3.16. I'm experimenting with client certificates and the "ssl_verify_client_cert = yes" option. By putting the server in debug mode, I can verify that the client is correctly providing the certificate. I am trying to log using %{cert} adding it to login_log_format_elements, as per the documentation, but I get the error: "Failed to expand log_format_elements=cert=%{cert}: Unknown variable '%cert'" Also the documentation says that the short name is %k, but it overlaps with %{ssl_security}. Is the documentation wrong or is there a bug? Thanks, Andrea -- __________________________ One of the things we can do to help the poor is not to become one of them. __________________________ 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.

1 0

Logging to remote server
by James Brown 26 Aug '21

26 Aug '21

My Google searches must be off, I couldn’t see how to do this. Is there a way to log to a local file, but also send to a remote server? Eg: Log_path = /var/log/dovecot.log, @mylogserver.example.com:514 Thanks, James

3 2

Creating/Learning about services
by Dan Conway 25 Aug '21

25 Aug '21

Hello, I'm currently researching how services work within Dovecot and what scope these services are capable of. For example, I created a service as such: service myservice { executable = /home/me/executable type = worker unix_listener myservice { mode = 0666 } } When data is provided to the myservice unix socket, Dovecot appears to create a new process by executing "/home/me/executable". I found out about "status updates" through examining the logs. At first I received this: master: Error: service(myservice): Initial status notification not received in 30 seconds, killing the process What is this status notification? I found out that writing to file descriptor 5 from the executable does seem to be valid. When I write out 12 bytes I don't get an error, but when I write out 13 bytes I get the following: master: Error: service(dmon): service sent partial status update (13 bytes) What I've also noticed is that exiting 0 will cause Dovecot to spawn the process again, in what appears to be infinitely. Are there any resources/documentation that I could reference to learn more about how services work on a lower level besides just looking at the source code? Thanks.

2 2

What kind of search response time are you setting with solr full text search?
by Steve Dondley 25 Aug '21

25 Aug '21

MY SETUP: I have apache solr full text search enabled with dovecot. I have an inbox with about 40 subfolders. I'm using the roundcube web-based mail client. The find command is showing 15823 email files and apache solr reports the same number. I'm running a dedicated mail server with a 1 GB of ram. The solr machine is running on a separate machine with 4 GB ram. THE PROBLEM: When I do a full text search through all my inbox and all subfolders on a single word, search results are returned in about 10 to 15 seconds. This is better than the 40 seconds or so I'm getting when I turn off the fts and fts_solr plugins but still a little disappointing. WHAT I'D LIKE: Now, I don't expect instant search results like gmail, but getting the search results to display in less than 5 seconds would be a lot less painful that 10 to 15 seconds. WHAT I'VE TRIED: I have reindexed the emails on solr to try to speed things upit up. ANY ADVICE? Curious to know what response times others are seeing and if there is anything else I might try to speed things up. Maybe the number of subfolders is slowing things down?

6 23

JMAP Support Status
by David Klingenberg 25 Aug '21

25 Aug '21

Hello, what is the current status of JMAP support in Dovecot? Is it already supported or is there any ongoing work on it? I have found some older threads mentioning it as planned, but they are quite old and I haven't found anything new on that topic. Best Regards, David

1 0

Mail duplication on multimaster replication
by Alexey 24 Aug '21

24 Aug '21

Hello. I have 3 machines with dovecot with a circular replication: 1 → 2 → 3 → 1. As I notice there is two anomalies: 1) Mass expunge often not replicated with fast replication (default replicator mode). Replication happens only after incremental replication (full of course too, but it is not necessary). I mean, that after mail was expunged on first server via imap, I can get it with doveadm fetch on second. 2) There is some odd lines in log: doveadm(mail(a)domain.org)<10620><...>: Info: copy from INBOX: box=INBOX, uid=137704, msgid=<...>, size=2877 doveadm(mail(a)domain.org)<10620><...>: Info: expunge: box=INBOX, uid=134812, msgid=<...>, size=2877 What is the copy from INBOX to INBOX. I guess that after this actions of replicator I got a ton of duplicates of removed to Trash mails. Only IMAP is in use. All 3 servers use the same version: # dovecot --version 2.3.15 (0503334ab1) doveconf -n # 2.3.15 (0503334ab1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.15 (e6a84e31) # OS: Linux 5.10.0-0.bpo.3-amd64 x86_64 Debian 10.10 auth_verbose = yes default_vsz_limit = 30 G doveadm_password = # hidden, use -P to show it doveadm_port = 4545 first_valid_gid = 500 imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags last_valid_gid = 500 last_valid_uid = 500 log_path = /var/log/dovecot/dovecot.log mail_attribute_dict = file:%h/dovecot-attributes mail_gid = dmail mail_location = mdbox:~/mdbox mail_log_prefix = "%s(%u): " mail_plugins = " mail_log notify notify replication" mail_uid = dmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = xapian fts_autoindex = yes fts_autoindex_exclude = \Trash fts_decoder = decode2text fts_enforced = yes fts_xapian = partial=3 full=20 verbose=1 attachments=0 mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size mail_replica = tcp:10.1.1.137:4545 plugin = fts fts_xapian replication_max_conns = 100 sieve_before = /var/lib/dovecot/sieve.d/vmail/ sieve_dir = ~/sieve sieve_global_extensions = +vnd.dovecot.duplicate sieve_trace_debug = no sieve_trace_level = actions } protocols = " imap lmtp sieve sieve" service aggregator { fifo_listener replication-notify-fifo { group = dmail user = dmail } unix_listener replication-notify { group = dmail user = dmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = dmail mode = 0600 user = dmail } } service decode2text { executable = script /usr/lib/dovecot/decode2text.sh unix_listener decode2text { mode = 0666 } user = dovecot } service doveadm { inet_listener { port = 4545 } } service imap-login { inet_listener imaps { port = 993 ssl = yes } } service indexer-worker { vsz_limit = 15 G } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = dmail mode = 0660 user = dmail } } service stats { unix_listener stats-reader { group = dmail mode = 0660 user = dmail } unix_listener stats-writer { group = dmail mode = 0660 user = dmail } } ssl = required ssl_cert = # hidden, use -^^ to show it ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " mail_log notify notify replication sieve" } protocol lda { mail_plugins = " mail_log notify notify replication sieve" } protocol imap { mail_plugins = " mail_log notify notify replication fts fts_xapian" }

1 0

Problem deleting a parent folder with child folder(s)
by David Härdeman 24 Aug '21

24 Aug '21

Hi, I'm seeing some odd behavior wrt deleting a parent folder which has child/inferior folders: root@vmtest2:~# telnet localhost 143 Trying ::1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Debian) ready. 1 LOGIN "test(a)example.com" "foobar" 1 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE SAVEDATE LITERAL+ NOTIFY SPECIAL-USE QUOTA] Logged in 2 LIST "" "*" * LIST (\HasNoChildren \UnMarked \Trash) "." INBOX.Trash * LIST (\HasNoChildren \UnMarked \Sent) "." INBOX.Sent * LIST (\HasNoChildren \UnMarked \Junk) "." INBOX.Spam * LIST (\HasNoChildren \UnMarked \Archive) "." INBOX.Read * LIST (\HasNoChildren \UnMarked \Drafts) "." INBOX.Drafts * LIST (\HasChildren) "." INBOX 2 OK List completed (0.002 + 0.000 + 0.001 secs). 3 CREATE ParentA.ChildA 3 OK Create completed (0.017 + 0.000 + 0.017 secs). 4 LIST "" "*" * LIST (\Noselect \HasChildren) "." ParentA * LIST (\HasNoChildren) "." ParentA.ChildA * LIST (\HasNoChildren \UnMarked \Trash) "." INBOX.Trash * LIST (\HasNoChildren \UnMarked \Sent) "." INBOX.Sent * LIST (\HasNoChildren \UnMarked \Junk) "." INBOX.Spam * LIST (\HasNoChildren \UnMarked \Archive) "." INBOX.Read * LIST (\HasNoChildren \UnMarked \Drafts) "." INBOX.Drafts * LIST (\HasChildren) "." INBOX 4 OK List completed (0.001 + 0.000 secs). 5 EXAMINE ParentA 5 NO Mailbox doesn't exist: ParentA (0.001 + 0.000 secs). 6 DELETE ParentA.ChildA 6 OK Delete completed (0.022 + 0.000 + 0.021 secs). 7 CREATE ParentB 7 OK Create completed (0.019 + 0.000 + 0.018 secs). 8 CREATE ParentB.ChildB 8 OK Create completed (0.009 + 0.000 + 0.008 secs). 9 LIST "" "*" * LIST (\HasChildren) "." ParentB * LIST (\HasNoChildren) "." ParentB.ChildB * LIST (\HasNoChildren \UnMarked \Trash) "." INBOX.Trash * LIST (\HasNoChildren \UnMarked \Sent) "." INBOX.Sent * LIST (\HasNoChildren \UnMarked \Junk) "." INBOX.Spam * LIST (\HasNoChildren \UnMarked \Archive) "." INBOX.Read * LIST (\HasNoChildren \UnMarked \Drafts) "." INBOX.Drafts * LIST (\HasChildren) "." INBOX 9 OK List completed (0.001 + 0.000 secs). 10 DELETE ParentB 10 OK Delete completed (0.015 + 0.000 + 0.014 secs). 11 LIST "" "*" * LIST (\HasChildren) "." ParentB * LIST (\HasNoChildren) "." ParentB.ChildB * LIST (\HasNoChildren \UnMarked \Trash) "." INBOX.Trash * LIST (\HasNoChildren \UnMarked \Sent) "." INBOX.Sent * LIST (\HasNoChildren \UnMarked \Junk) "." INBOX.Spam * LIST (\HasNoChildren \UnMarked \Archive) "." INBOX.Read * LIST (\HasNoChildren \UnMarked \Drafts) "." INBOX.Drafts * LIST (\HasChildren) "." INBOX 11 OK List completed (0.001 + 0.000 secs). 12 EXAMINE ParentB 12 NO Mailbox doesn't exist: ParentB (0.001 + 0.000 secs). I would have expected the output from the "11 LIST..." command to be identical to that of the "4 LIST..." command, i.e. that "ParentB" would be listed as "\Noselect" in the response to "11 LIST...". I've tracked the contents of the local /var/vmail/.../Maildir folder while executing the above commands, and it appears to correspond to the expected situation (i.e. ".ParentA.ChildA" is created, then deleted, then ".ParentB" is created, then ".ParentB.ChildB" is created, and finally ".ParentB" is deleted - in other words, neither the ".ParentA" nor the ".ParentB" folders exist at the time when I issue the "4 LIST..." and "11 LIST..." commands). That "ParentB" should have a "\Noselect" flag in the last "LIST" also appears to be what's mandated by RFC3501, section 6.3.4: ... The DELETE command MUST NOT remove inferior hierarchical names. For example, if a mailbox "foo" has an inferior "foo.bar" (assuming "." is the hierarchy delimiter character), removing "foo" MUST NOT remove "foo.bar". It is an error to attempt to delete a name that has inferior hierarchical names and also has the \Noselect mailbox name attribute (see the description of the LIST response for more details). It is permitted to delete a name that has inferior hierarchical names and does not have the \Noselect mailbox name attribute. In this case, all messages in that mailbox are removed, and the name will acquire the \Noselect mailbox name attribute. ... Tested using the default dovecot package in Debian Bullseye, which is version 1:2.3.13+dfsg1-2. The file system is ext4, and Dovecot is running in a virtual (systemd-nspawn) machine for testing purposes. I've tried grepping through the git changelogs and sources, but I couldn't find anything which would appear to be relevant post-2.3.13. Any ideas? (Please CC me on replies, not subscribed) doveconf -n output ================== # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-8-amd64 x86_64 Debian 11.0 # Hostname: localhost auth_default_realm = example.com auth_mechanisms = plain login doveadm_password = # hidden, use -P to show it doveadm_port = 12345 mail_gid = vmail mail_home = /var/vmail/%d/%n mail_location = maildir:~/Maildir mail_privileged_group = vmail mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = yes location = mailbox INBOX.Drafts { auto = subscribe special_use = \Drafts } mailbox INBOX.Read { auto = subscribe special_use = \Archive } mailbox INBOX.Sent { auto = subscribe special_use = \Sent } mailbox INBOX.Spam { auto = subscribe special_use = \Junk } mailbox INBOX.Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot.deny deny = yes driver = passwd-file } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf driver = ldap } plugin { imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = INBOX.Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = INBOX.Spam imapsieve_mailbox2_name = * quota = maildir:User quota sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /usr/bin sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = imap lmtp sieve service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service doveadm { inet_listener doveadm { port = 12345 ssl = yes } } service imap-login { inet_listener imap { address = 127.0.0.1, [::1] port = 143 } inet_listener imaps { port = 993 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/pki/realms/domain/default.crt ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } protocol imap { mail_plugins = " notify replication quota imap_sieve imap_quota" } protocol lmtp { mail_plugins = " notify replication quota sieve" postmaster_address = postmaster(a)example.com }

1 0

Different userdb per inet_listener
by Miloslav Hůla 24 Aug '21

24 Aug '21

Hello, we are running Dovecot (2.3.4.1-5+deb10u6) with PostgreSQL passdb and userdb and for remote Postfix: auth_mechanisms = plain login inet_listener { address = 127.0.0.1 port = 12345 } It works perfectly. Now we would like to disable authentication for Postfix (SMTP), but allow it for Dovecot (IMAP & POP3). Something like "receive-only". Is there any way we can configure different passdb for mentioned inet_listener? Or is there any variable with "auth requetor name" we can use in SQL query to differentiate the result? Regards Miloslav

2 3

Director vs Proxy
by MRob 24 Aug '21

24 Aug '21

Hello, I understand director is like coordinated state database for the proxies. Is it like a special lookup resource for Dovecot proxy? If correct, makes sense proxies and directors should be deployed in pairs. But few places the docs talk about maybe different number of directors v. proxies or putting directors on different hardware from proxies. What is reason to separate director and proxy? Thank you.

1 0

Problems with anvil-auth-penalty and login_trusted_networks
by Ricardo Machini Barbosa 20 Aug '21

20 Aug '21

Hello, On my environment I have: 1 cluster of webmail servers 1 cluster of dovecot proxy dovecot servers n dovecot backend servers On my dovecot backend servers, I use the login_trusted_networks option with the IP range of my servers in the dovecot proxy cluster. But and I'm having problems where the IP addresses of the webmail cluster servers are receiving anvil-auth-penalty penalty. I tried to use in the login_trusted_networks option both the IP range of the dovecot proxy cluster and IP range of the webmail cluster, but this configuration had no effect and I still have my webmail IP's blocked. Is there anything I can do in this scenario to have the webmail cluster IP's whitelisted in anvil-auth-penalty ? Regards, Ricardo

1 0

handling public namespace (under mdbox/sdbox)
by Michal Soltys 20 Aug '21

20 Aug '21

Besides of course a "dummy" user that has admin rights to all subfloders - and handles delivery via Public/ prefix. For example using: public-dummy+Public/path/to/subfloder. But - with maildir I've been using a dedicated user that sees public namespace as its own mailbox - so all the alises/redirects go w/o Public/ prefix in such case - for example: public-dedicated+path/to/subfloder . This has been working fine with old maildir, but will this be ok for dbox mailboxes as well ?

1 0

dovecot flags lost after move/copy
by ciuga 20 Aug '21

20 Aug '21

Dear Community, I have a issue with our dovecot server ( 2.3.4.1 (f79e8e7e4) ) with maildir Flags are lost after a copy (or move), as you can see on this exemple : * Before doing anything, list detail of a mail : doveadm fetch -u XXX flags mailbox-guid f303160f6df58c5b67040200bc34b0e6 uid 46126 flags: \Seen $Labelimportant File name also contents the 'e' at the end : 1628631415.M671664P17659.mail7,S=14835,W=15111:2,Se * Copy it for testing doveadm copy -u XXX Archive mailbox INBOX mailbox-guid f303160f6df58c5b67040200bc34b0e6 uid 46126 * Fetch flag of this new mail doveadm -v fetch -u XXX flags mailbox Archive flags: \Seen File name also don't content the flags -rw------- 2 XXX users 14835 août 10 23:36 '1628631415.M671664P17659.mail7,S=14835,W=15111:2,S' Do you known how to keep flags after move and/or copy ? Thanks in advance -- Chris

1 0

dovecot 3.16 replicator Problem?
by Günther J. Niederwimmer 20 Aug '21

20 Aug '21

Hello list, I have a problem with the replicator (config) I mean it doesn't work anymore since version 3.16? How can you turn up the log level with this tool? I think the full sync is still possible to some extent. I deleted a test user who was restored after a day. Question: has something changed in the config so that the whole thing works again Thanks for a answer, -- mit freundlichen Grüßen / best regards Günther J. Niederwimmer

2 1

ssl_params error on RHEL7 FIPS enabled
by Brad Partin 19 Aug '21

19 Aug '21

All, The machine I’m running dovecot on is: RHEL7.9 3.10.0-1160.31.1.el7.x86_64 I can run Systemctl restart dovecot then status or /usr/libexec/dovecot/ssl-params and I get the following error. Info: Generating SSL parameters Fatal: ssl_iostream_generate_params(4096) failed: DH_generate_parameters(bits=512, gen=2) failed: error:0506A06E:lib(5):func(106):reason(110), error 0506A003:lib(5):func(106):reason(3) Error: child process failed with status 22784 I can generate a diffie-hellman pem with openssl dhparam -out /etc/dovecot/dh.pem 4096 But dovecot 2.2.36 does not have the option of telling it where the dh.pem file is located in the config like version 2.3 does. Is my error related to FIPS and is there a way around it? My dovecot version is: Dovecot version 2.2.36 release 8.el7 Thanks in advance to anyone willing to help out, I know it’s voluntary 🙏 Thanks, bpartin2009 Sent from my iPhone

2 1

Something obvious in my sieve?
by ＠lbutlr 19 Aug '21

19 Aug '21

I get the following error for this: line 24 is the "contains subset" line .active_sieve: line 24: error: expecting test identifier after ',' in test list, but found '('. .active_sieve: line 24: error: expecting ',' or end of test list ')', but found '{'. .active_sieve: error: parse failed. if anyof (body :contains "files transferred: 0", (header :contains "subject" "a specific subject goes here" ) { This clause produces no error if anyof (header :contains "from" "@unwanted", envelope :matches :detail "to" "extension", exists "X-Facebook" ){ What am I missing? -- "Are you pondering what I'm pondering?" "Yes Brain, but if our knees bent the other way, how would we ride a bicycle?"

2 2

Odd config problem in Debian Bullseye / dovecot 2.3.13
by Perry E. Metzger 19 Aug '21

19 Aug '21

Hi all! For a long time, I've been running this out of cron as user "perry": /usr/bin/doveadm expunge -u perry mailbox SPAM not seen before 7d After upgrading to 2.3.13 as a result of a debian upgrade, this broke. I now am suddenly getting: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 132: ssl_key: Can't open file /etc/ssl/private/ssl-cert-snakeoil.key: Permission denied Attempting things like setting "-o ssl_key=/dev/null" and the like don't work. I could of course run this as root but I'd strongly prefer not to. Anyone have any ideas? Perry

2 3

Snarf plugin retirement
by Brent Busby 19 Aug '21

19 Aug '21

I wondered if it's possible to get the Snarf plugin back, if not in the official Dovecot distribution, then at least to somehow build the plugin source on a modern release...because: Though the documented purpose for Snarf was to ease migration off of UW-IMAP, that's not the only thing it was useful for. Unfortunately, every mailreader that I've seen that can run within Emacs -- and I've tried Gnus, VM, and RMAIL -- all _require_ the use of a ~/mbox file when pulling from a local mail spool on the same machine. (This does not affect IMAP usage of those mailreaders, only local file access.) Non-Emacs mailreaders like Alpine and Mutt have sufficiently robust file-locking safety that they can work on the local mail spool in /var/spool/mail or /var/mail or what have you directly without copying your mail somewhere else first, so for Alpine and Mutt, use of ~/mbox is possible but not necessary. But it seems that for every mailreader that does run within Emacs, if the mail source is local rather than IMAP, there is no other way to operate the program than to have it copy your mail from the spool to ~/mbox. On a system where there are users who sometimes work that way, doing local mail access in Emacs, and other times use IMAP via Dovecot, you have a mess without the Snarf plugin. I realize this is a peculiar situation, so I don't expect Snarf to necessarily be put back into Dovecot. I was wondering how it might be possible to build it today though...for any out there who may use Emacs for mail most of the time...but occasionally also want Dovecot IMAP on the same machine where they're normally using an ~/mbox file for Emacs' sake. UW-IMAP may be dead...but long live GNU Emacs! -- + Brent A. Busby + "We've all heard that a million monkeys + Sr. UNIX Systems Admin + banging on a million typewriters will + University of Chicago + eventually reproduce the entire works of + James Franck Institute + Shakespeare. Now, thanks to the Internet, + Materials Research Ctr + we know this is not true." -Robert Wilensky

3 2

BUG REPORT: MAIL-CRYPT plugin: doveadm mailbox cryptokey -O option
by ean365 17 Aug '21

17 Aug '21

Aki: I have identified a bug in the "*-O*" option of "*doveadm mailbox cryptokey password*" plugin command -- it is expecting an argument, but it is supposed to be a boolean option. I have also identified the (simple) fix to the source on github... /I am a dovecot community noob, so please forgive me if this has already been identified... (if so, I hope it gets fixed soon)... / The "-O" option in *struct doveadm_cmd_mcp_key_password* is set to expect a *STR* parameter, but it should be *BOOL*. See line 1027 in plugins/mail-crypt/doveadm-mail-crypt.c of master branch... Currently: ***DOVEADM_CMD_PARAM**(**'O'**, **"ask-old-password"**, CMD_PARAM_STR, **0**) *Should be: ***DOVEADM_CMD_PARAM**(**'O'**, **"ask-old-password"**, CMD_PARAM_BOOL, **0**)* Workaround is to specify *-O* last on command line with a dummy argument, like this: *doveadm mailbox cryptokey password -N -O ""* Also, a quick question and suggestion -- Why does the *doveadm mailbox cryptokey password* command not ask for a new password twice, with a check that both entries must match before the password is changed? The last thing we would want is to type something wrong accidentally, and change the new password to something unknown -- rendering encrypted email unrecoverable. I would like to suggest that the code in *cmd_mcp_key_password_run* be amended to include verifying password entry twice. (I am writing a simple addition to postfixadmin that changes the user's mail-crypt password whenever they use postfixadmin to change their login password. It calls *doveadm* to change the keys. I came across this bug while working through this.) Thanks for all your help! Eric **

2 5

SSL TLS SNI error certificate is empty
by silvan＠datavenia.nl 16 Aug '21

16 Aug '21

Hello, I’ve tried implementing TLS SNI for my Postfix/Dovecot setup. I have it working in Postfix, but this example for Dovecot: https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/#wit… doesn’t seem to work for me. I’m using LetsEncrypt certificates. They work without a problem with the regular ssl_cert and ssl_key settings like this: ssl_cert = </docker/rancher-active-proxy/letsencrypt/live/datavenia.nl/fullchain.pem ssl_key = </docker/rancher-active-proxy/letsencrypt/live/datavenia.nl/privkey.pem … but as soon as I put them in local_name blocks like this: local_name datavenia.nl { ssl_cert = </docker/rancher-active-proxy/letsencrypt/live/datavenia.nl/fullchain.pem ssl_key = </docker/rancher-active-proxy/letsencrypt/live/datavenia.nl/privkey.pem } local_name verovia.nl { ssl_cert = </docker/rancher-active-proxy/letsencrypt/live/verovia.nl/fullchain.pem ssl_key = </docker/rancher-active-proxy/letsencrypt/live/verovia.nl/privkey.pem } and restart dovecot I get the following error: dovecot: imap-login: Error: Failed to initialize SSL server context: Can't load SSL certificate (ssl_cert setting): The certificate is empty: user=<>, rip=213.127.63.224, lip=142.93.135.7, session=<wKjTIaLJtSXVfz/g> I have verified that the certificate paths are correct, the files have content. I’ve already checked permissions (chmodded 777 to debug), as well as the that these are actually symlinks (updated the config to point to the real files) but nothing so far seems to change anything. I have also recreated my dh.pem (4096). I’m hoping anyone has any idea where I might be going wrong. Kind regards, Silvan Output of dovecot -n: # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.11.0-25-generic x86_64 Ubuntu 21.04 ext4 # Hostname: azrael00 auth_mechanisms = plain login mail_location = maildir:/var/mail/vhosts/%d/%n 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-sql.conf.ext driver = sql } postmaster_address = postmaster(a)datavenia.nl <mailto:postmaster@datavenia.nl> protocols = imap lmtp service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0666 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_dh = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } local_name datavenia.nl { ssl_cert = </docker/rancher-active-proxy/letsencrypt/live/datavenia.nl/fullchain.pem ssl_key = # hidden, use -P to show it } local_name verovia.nl { ssl_cert = </docker/rancher-active-proxy/letsencrypt/live/verovia.nl/fullchain.pem ssl_key = # hidden, use -P to show it }

2 2

auth-worker looses MySQL connection and doesn't reconnect when MySQL/MariaDB has been restarted
by Christian Ruppert 16 Aug '21

16 Aug '21

Hey, I have MariaDB 10.5.10 and Dovecot 2.3.14.1 right now but it's broken since a few months already. I don't remember when it started and what versions I had running of both. As stated in the subject, the Dovecot auth-worker looses connection during a MySQL/MariaDB restart, which is ok so far, but it doesn't reconnect for some reason and instead all further actions fail because of it, like doveadm or IMAP login / commands etc. Aug 15 13:21:28 thor dovecot[20862]: auth-worker(24450): Warning: sqlpool(mysql): Query failed, retrying: Connection was killed Aug 15 13:21:28 thor dovecot[20862]: auth-worker(24450): Error: conn unix:auth-worker (pid=24449,uid=97): auth-worker<376>: sql(user@example.com,::1,<somesession>): Password query failed: Connection was killed Aug 15 13:21:30 thor dovecot[20862]: imap-login: Disconnected (auth service reported temporary failure): user=<user(a)example.com>, method=PLAIN, rip=::1, lip=::1, secured, session=<somesession> This repeats basically for every command / action I do until I restart dovecot or kill the auth-worker process. Both works. dovecot-sql.conf.ext: driver = mysql connect = host=/run/mysqld/mysqld.sock dbname=mail user=dovecot password=SOMEPW Steps to reproduce: Use MySQL in Dovecot Restart MySQL while Dovecot is running Do either some doveadm commands or try to login e.g. using IMAP or just try to navigate through your mailbox See errors / logs pkill -f 'dovecot/auth worker' Try doveadm etc. again Works -- Regards, Christian Ruppert

1 0

i_stream_read_memarea: assertion failed: (!stream->blocking)
by Stuart Henderson 16 Aug '21

16 Aug '21

Continuation of https://dovecot.org/pipermail/dovecot/2021-January/121235.html - I didn't get a reply to my last mail, so ended up deleting the various messages (or in some cases mailboxes) and stopped running into problems for a while, but am now seeing it again. I get "i_stream_read_memarea: assertion failed: (!stream->blocking)" when accessing some messages. Backtrace and doveconf -n below. $ doveadm -D search from abcdefghij [...] Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1177: Looked up field guid from mail cache Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1177: Opened mail because: 1/1 headers not cached (first=from) (Mail has other cached fields, reset_id=1470764070) Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1178: Looked up field guid from mail cache Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1178: Looked up field guid from mail cache Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1178: Looked up field guid from mail cache Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1178: Opened mail because: 1/1 headers not cached (first=from) (Mail has other cached fields, reset_id=1470764070) Aug 13 17:30:02 doveadm(sthen): Panic: file istream.c: line 345 (i_stream_read_memarea): assertion failed: (!stream->blocking) Abort trap (core dumped) Some other searches hitting the same message do succeed though e.g. "doveadm search mailbox trash". Somehow after various other searches trying to figure out what triggered the crash and what didn't (e.g. "doveadm -D search mailbox trash uid 1170:12000 from abc" crashed but "uid 1170:1190" didn't) it has stopped failing with that particular message, but I am still hitting it in at least one other mailbox. The messages where I'm seeing this so far seem to all be stored with lz4 (a couple of years old mostly). Any ideas? GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-openbsd6.9". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from doveadm...Reading symbols from /usr/local/bin/.debug/doveadm.dbg...done. done. [New process 130792] Core was generated by `doveadm'. Program terminated with signal SIGABRT, Aborted. #0 thrkill () at /tmp/-:3 3 /tmp/-: No such file or directory. (gdb) bt #0 thrkill () at /tmp/-:3 #1 0x00000c3b2a1ee58e in _libc_abort () at /usr/src/lib/libc/stdlib/abort.c:51 #2 0x00000c3b2780f876 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:459 #3 0x00000c3b2780dc94 in fatal_handler_real (ctx=0x7f7ffffcb040, format=<error reading variable: Unhandled dwarf expression opcode 0xa3>, args=<error reading variable: Unhandled dwarf expression opcode 0xa3>) at failures.c:471 #4 0x00000c3b2780dc51 in default_fatal_handler (ctx=0x0, format=0x6 <error: Cannot access memory at address 0x6>, args=0x0) at failures.c:479 #5 0x00000c3b2780ded2 in i_panic (format=0x6 <error: Cannot access memory at address 0x6>) at failures.c:524 #6 0x00000c3b2781db26 in i_stream_read_memarea (stream=0xc3b41c94080) at istream.c:345 #7 0x00000c3b27827c2f in read_more (sstream=0xc3b41c80c00) at istream-seekable.c:152 #8 0x00000c3b27827a70 in read_from_buffer (sstream=0xc3b41c80c00, ret_r=0x7f7ffffcb188) at istream-seekable.c:207 #9 0x00000c3b27826f67 in i_stream_seekable_read (stream=0xc3b41c80c00) at istream-seekable.c:269 #10 0x00000c3b2781da74 in i_stream_read_memarea (stream=0xc3b41c80c80) at istream.c:326 #11 0x00000c3b2782568c in i_stream_limit_read (stream=0xc3b1097d000) at istream-limit.c:51 #12 0x00000c3b2781da74 in i_stream_read_memarea (stream=0xc3b1097d080) at istream.c:326 #13 0x00000c3b2781e16c in i_stream_read_copy_from_parent (istream=<optimized out>) at istream.c:400 #14 0x00000c3bc821b24a in i_stream_mail_read (stream=0xc3b41c83200) at istream-mail.c:115 #15 0x00000c3b2781da74 in i_stream_read_memarea (stream=0xc3b41c83280) at istream.c:326 #16 0x00000c3b2781ef0a in i_stream_read (stream=0xc3b41c83280) at istream.c:283 #17 i_stream_read_data (stream=0xc3b41c83280, data_r=0x7f7ffffcb3b8, size_r=0x7f7ffffcb3b0, threshold=1) at istream.c:760 #18 0x00000c3b277e4016 in i_stream_read_bytes (stream=0x0, data_r=<optimized out>, size_r=<optimized out>, wanted=<optimized out>) at ../../src/lib/istream.h:220 #19 message_parse_header_next (ctx=0xc3b109a4300, hdr_r=0x7f7ffffcb470) at message-header-parser.c:85 #20 0x00000c3b277dc5f2 in read_header (mstream=0xc3b41cb0800) at istream-header-filter.c:195 #21 i_stream_header_filter_read (stream=0xc3b41cb0800) at istream-header-filter.c:450 #22 0x00000c3b2781da74 in i_stream_read_memarea (stream=0xc3b41cb0880) at istream.c:326 #23 0x00000c3b2781ef0a in i_stream_read (stream=0xc3b41cb0880) at istream.c:283 #24 i_stream_read_data (stream=0xc3b41cb0880, data_r=0x7f7ffffcb568, size_r=0x7f7ffffcb560, threshold=1) at istream.c:760 #25 0x00000c3b277e4016 in i_stream_read_bytes (stream=0x0, data_r=<optimized out>, size_r=<optimized out>, wanted=<optimized out>) at ../../src/lib/istream.h:220 #26 message_parse_header_next (ctx=0xc3b1097a800, hdr_r=0x7f7ffffcb5b8) at message-header-parser.c:85 #27 0x00000c3b277e4879 in message_parse_header (input=0xc3b41cb0880, hdr_size=0x0, flags=<optimized out>, callback=0xc3bc822a3a0 <search_header>, context=0x7f7ffffcb608) at message-header-parser.c:392 #28 0x00000c3bc8229c62 in search_arg_match_text (args=0xc3b10987110, ctx=0xc3b41c89400) at index-search.c:769 #29 search_match_once (ctx=0xc3b41c89400) at index-search.c:1408 #30 0x00000c3bc822883e in search_match_next (ctx=0xc3b41c89400) at index-search.c:1516 #31 search_more_with_mail (ctx=0xc3b41c89400, mail=<optimized out>) at index-search.c:1632 #32 search_more_with_prefetching (ctx=0xc3b41c89400, mail_r=0x7f7ffffcb770) at index-search.c:1714 #33 search_more (ctx=0xc3b41c89400, mail_r=0x7f7ffffcb770) at index-search.c:1788 #34 0x00000c3bc82282cf in index_storage_search_next_nonblock (_ctx=0xc3b41c89400, mail_r=0x7f7ffffcb848, tryagain_r=0x7f7ffffcb7bf) at index-search.c:1816 #35 0x00000c3bc8282636 in mailbox_search_next_nonblock (ctx=0xc3b41c89400, mail_r=0x7f7ffffcb848, tryagain_r=<optimized out>) at mail-storage.c:2290 #36 mailbox_search_next (ctx=0xc3b41c89400, mail_r=0x7f7ffffcb848) at mail-storage.c:2275 #37 0x00000c38e91eeb31 in cmd_search_box (ctx=<optimized out>, info=<optimized out>) at doveadm-mail-search.c:36 #38 cmd_search_run (ctx=<optimized out>, user=<error reading variable: Unhandled dwarf expression opcode 0xa3>) at doveadm-mail-search.c:61 #39 0x00000c38e91e3ec3 in doveadm_mail_next_user (ctx=0xc3b10980048, error_r=0x7f7ffffcb9b0) at doveadm-mail.c:462 #40 0x00000c38e91e565a in doveadm_mail_cmd_exec (ctx=0xc3b10980048, wildcard_user=0x0) at doveadm-mail.c:653 #41 0x00000c38e91e51e3 in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at doveadm-mail.c:1153 #42 0x00000c38e91f7f38 in doveadm_cmd_run_ver2 (argc=3, argv=0x7f7ffffcbc98, cctx=0x7f7ffffcbb70) at doveadm-cmd.c:575 #43 0x00000c38e91f78e5 in doveadm_cmd_try_run_ver2 ( cmd_name=<error reading variable: Unhandled dwarf expression opcode 0xa3>, argc=0, argv=0x6, cctx=0x7f7ffffcbb70) at doveadm-cmd.c:497 #44 0x00000c38e91fb636 in main (argc=6, argv=0x0) at doveadm.c:366 (gdb) frame 6 #6 0x00000c3b2781db26 in i_stream_read_memarea (stream=0xc3b41c94080) at istream.c:345 345 i_assert(!stream->blocking); (gdb) p *stream $1 = { v_offset = 0, stream_errno = 0, mmaped = false, blocking = true, closed = false, readable_fd = false, seekable = false, eof = true, real_stream = 0xc3b41c94000 $ doveconf -n # some parts replaced with <snip> # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: OpenBSD 6.9 amd64 # Hostname: naiad.spacehopper.org dsync_remote_cmd = /usr/bin/ssh <snip> first_valid_uid = 1000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> %k login_trusted_networks = 127.0.0.1 <snip> mail_location = mdbox:~/mdbox mail_plugins = " zlib notify replication" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext vacation-seconds spamtest spamtestplus imapsieve vnd.dovecot.imapsieve mbox_write_locks = fcntl mdbox_rotate_interval = 4 days mdbox_rotate_size = 15 M mmap_disable = yes 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 = separator = / } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { imapsieve_mailbox1_before = file:/etc/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = zSpam imapsieve_mailbox2_before = file:/etc/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = zSpam imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/etc/dovecot/sieve/report-ham.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = zHam mail_replica = <snip> sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.d/ sieve_extensions = +spamtest +spamtestplus +vacation-seconds sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /etc/dovecot/sieve/bin sieve_plugins = sieve_imapsieve sieve_extprograms sieve_spamtest_max_header = X-Spamd-Result: default: [[:alnum:]]+ \[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\] sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+ \[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\] sieve_spamtest_status_type = score sieve_vacation_default_period = 6h sieve_vacation_max_period = 0 sieve_vacation_min_period = 1m } protocols = imap pop3 lmtp sieve replication_max_conns = 4 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { group = _postfix mode = 0660 user = _postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap { vsz_limit = 512 M } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = _postfix mode = 0660 user = _postfix } vsz_limit = 512 M } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } service_count = 1 } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl_alt_cert = </etc/letsencrypt/live/junkpile.org/fullchain.pem ssl_cert = </etc/letsencrypt/live/junkpile.org/fullchain.ecpem ssl_cipher_list = TLSv1.2+AEAD+ECDHE:TLSv1.2+AEAD+DHE:ECDHE-RSA-AES128-SHA ssl_curve_list = X25519:P-521:P-384 ssl_dh = # hidden, use -P to show it ssl_min_protocol = TLSv1 ssl_prefer_server_ciphers = yes userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } verbose_proctitle = yes protocol lmtp { mail_plugins = " zlib notify replication sieve" } protocol lda { mail_plugins = " zlib notify replication sieve" postmaster_address = postmaster(a)spacehopper.org } protocol imap { mail_max_userip_connections = 21 mail_plugins = " zlib notify replication imap_sieve imap_zlib" }

2 2

Enabling autoexpunge for mailboxes created by sieve rules
by Salatiel Filho 16 Aug '21

16 Aug '21

Hi everyone. I have global sieve rules that can create mailboxes automatically by using "fileinto :create some/mailbox/that/does/not/exist". The emails are delivered to dovecot using lmtp and I can see the mailboxes created just fine. Is there a way to configure all new mailboxes created by those sieve rules to automatically set to autoexpunge after 15 days ? I tried this , but it did not work. namespace { type = public separator = / prefix = mypublic/ location = maildir:/var/spool/vmail/dovecot/mail/ subscriptions = no list = children mailbox * { autoexpunge=15d } } plugin { acl = vfile } # dovecot --version 2.3.15 (0503334ab1) Thanks!

1 0

Why do so many dovecot list mails fail dmarc?
by dovecot＠ptld.com 16 Aug '21

16 Aug '21

Im trying to get my head around this problem that too many valid emails from the mailing list fail dmarc. Why when other mailing list don't seem to have the same problem? I see today it says "signature verification failed", but why? Is there a problem with protonmail's dkim key? Is the dovecot list altering the message body? Is something wrong on my server's end? The example today was an email from @protonmail.ch, and the headers were: Return-Path: <dovecot-bounces(a)dovecot.org> Delivered-To: dovecot(a)ptld.com Received: from smtp.ptld.com by host.ptld.com with LMTP id +SjBLQqiFmFSbgIAjbxwTg (envelope-from <dovecot-bounces(a)dovecot.org>) for <dovecot(a)ptld.com>; Fri, 13 Aug 2021 12:47:06 -0400 Received: from talvi.dovecot.org (talvi.dovecot.org [94.237.25.159]) by smtp.ptld.com (Postfix) with ESMTPS id 4GmTx61z3fz4l3g2 for <dovecot(a)ptld.com>; Fri, 13 Aug 2021 12:47:06 -0400 (EDT) Authentication-Results: smtp.ptld.com; dmarc=fail (p=quarantine dis=none) header.from=protonmail.ch Authentication-Results: smtp.ptld.com; spf=pass smtp.mailfrom=dovecot.org Authentication-Results: smtp.ptld.com; dkim=fail reason="signature verification failed" (1024-bit key; secure) header.d=protonmail.ch header.i=(a)protonmail.ch header.a=rsa-sha256 header.s=protonmail header.b=ivRoCAz3 Received: from talvi.dovecot.org (localhost.localdomain [127.0.0.1]) by talvi.dovecot.org (Postfix) with ESMTP id 3862D32297F; Fri, 13 Aug 2021 19:46:41 +0300 (EEST) X-Original-To: dovecot(a)dovecot.org Delivered-To: dovecot(a)dovecot.org Received: from mail-41113.protonmail.ch (mail-41113.protonmail.ch [185.70.41.113]) by talvi.dovecot.org (Postfix) with ESMTPS id 07C532E9ADB for <dovecot(a)dovecot.org>; Fri, 13 Aug 2021 19:46:37 +0300 (EEST) Date: Fri, 13 Aug 2021 16:46:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.ch; s=protonmail; t=1628873196; bh=HCYF6+sDiqNN6f9T2srf/HEjnr5eJacuoNxBWXk1XJA=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=ivRoCAz3tXqh7Rk7Orxq6sdNGdIZ8eir4AX6OGxorOOza+XFOLQfBBIp4LfFEFV0y hV6b8z8gLmkZaEquwTyh+/Hx3lfpxts6Jvh1zpdL7YvahS2kOjSt0XikXulVgwvvxk BNmFxlLWwyVETRpgm5qsQHsNDjYb8HuYID4r1AXM= To: Aki Tuomi <aki.tuomi(a)open-xchange.com> From: Laura Smith <n5d9xq3ti233xiyif2vp(a)protonmail.ch> Subject: Re: Undefined symbols (macOS Big Sur Intel) during compiling, update Message-ID: <tQIPhn9Wc9ZCxjWv-REC0bXuE3RgBI1H69xIL0TOnDj-kWvhZXEF7ZR6BevaNCeu8AG9Ypvd7gsnbMEZFAAIkvGmNM3y3UealzoYw9HZSCg=(a)protonmail.ch> In-Reply-To: <180775367.20741.1628870488641(a)appsuite-dev-gw1.open-xchange.com> References: <CH2PR06MB6453C343867ECBFD79B73853BCF19(a)CH2PR06MB6453.namprd06.prod.outlook.com> <CH2PR06MB6453D734B09C7D6D2D807787BCFA9(a)CH2PR06MB6453.namprd06.prod.outlook.com> <180775367.20741.1628870488641(a)appsuite-dev-gw1.open-xchange.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mailout.protonmail.ch ARC-Seal: i=1; s=arc; d=dovecot.org; t=1628873197; a=rsa-sha256; cv=none; b=nuVCke6mta+nYIMyYvb2qRkTUyHSfKXEpp2vTds/ioq0kV4fyIL9oEON09yOoYcrQwci6D /EBrkZQI6nBjz592m7oslCjeNTcprIJr5QqLY6mJwW7mu+tp4rSEppIyD+r+9dbICExfFO p3j43c/m0J2acYc5pzZyJM7gLx/RBj2GURAUrP0JaX+y7moB/XQNPIJir2rE/jjNwojKCX keLRjlzOn7N4dLZxnKHgevDu6tH6gb0OzLPJO7W2IloMxdLZ/ab0PPZOj/M+BaYqnfa1Hs T4EvKhSwDjLyhjUQh7QTkmYm/FryVnIxEawEM+huOW9djJe7pIijuNFTqOR4Xg== ARC-Authentication-Results: i=1; talvi.dovecot.org; dkim=pass header.d=protonmail.ch header.s=protonmail header.b=ivRoCAz3; spf=pass (talvi.dovecot.org: domain of n5d9xq3ti233xiyif2vp(a)protonmail.ch designates 185.70.41.113 as permitted sender) smtp.mailfrom=n5d9xq3ti233xiyif2vp(a)protonmail.ch ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=dovecot.org; s=arc; t=1628873197; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=HCYF6+sDiqNN6f9T2srf/HEjnr5eJacuoNxBWXk1XJA=; b=EYR3Jyq5jrpho8glpLHD60ehlmLaGqrfdZepsfTTJtkjb0AkScBiUB0JX5hGbeyQCdeFvF zr0g/tfST7KEANMdZ0GK+rmwwSZC7LuKzszXWP+Pi5kBxsDPPU4BUivUkP3abCnGIixXfq LrEe+/bDrbMkM01wO8sJ0mZccYwURDMTJc7gFjcdSye+3FfKPZAvT9OG2aD2yQhtIVwpbv +Hg7P5v5Et/muT1E8NHZRBGOPhv4OZ/A2TcOLpafXejddNj2pRtVo8NlFzzT2PBn+KV49M nhI4ZDGk43l66nud7wMGDNdUcqYQl6CBQww+kC4ewfNbTy5D27wQwFzpVWGfFQ== Cc: "dovecot(a)dovecot.org" <dovecot(a)dovecot.org>, Beosdoc <beosdoc(a)hotmail.com> X-BeenThere: dovecot(a)dovecot.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Dovecot Mailing List <dovecot.dovecot.org> List-Unsubscribe: <https://dovecot.org/mailman/options/dovecot>, <mailto:dovecot-request@dovecot.org?subject=unsubscribe> List-Archive: <https://dovecot.org/pipermail/dovecot/> List-Post: <mailto:dovecot@dovecot.org> List-Help: <mailto:dovecot-request@dovecot.org?subject=help> List-Subscribe: <https://dovecot.org/mailman/listinfo/dovecot>, <mailto:dovecot-request@dovecot.org?subject=subscribe> Reply-To: Laura Smith <n5d9xq3ti233xiyif2vp(a)protonmail.ch> Errors-To: dovecot-bounces(a)dovecot.org Sender: "dovecot" <dovecot-bounces(a)dovecot.org>

4 3

Help to setup a Unix socket based authentication server for dovecot in Python
by Sherin A 15 Aug '21

15 Aug '21

Hi, I am building a custom server platform in which dovecot is used for imap/pop . But the default authentication mechanism is not suitable for me becuase each domain will have different system users and different location for mail storage . So I need to create a custom authentication mechanism using python . There is an option to use Key-value authentication (dict) database via socket as per https://doc.dovecot.org/configuration_manual/authentication/dict/#complete-… The above documentation link have a sample perl script too to send authentication to uri = proxy:/var/run/auth_proxy_dovecot/socket:somewhere So my question is how the inputs are send to the socket file ? in which format ? How the result return ? and in which format ? Let us say I can create a python socket program that can listen to /var/run/auth_proxy_dovecot/socket for getting the inputs from dovecot , but what is the format Is it like the following AUTH PLAIN USER test(a)myemail.com PASS mypassword I looked into the documentation and developer documentation, I am unable to see how dovecot send the data , I can see a sample perl for answering dict lookups. Any one have a python alternative for it. ? -- *Sherin Abdulkhareem* Chairman & Managing Director email Email sherin(a)sherin.in <mailto:sherin@sherin.in> mobile Mobile (+91)9496533234 office Office (+91)4716007799 *Syslint Technologies India Private Limited* First Floor,Asiatic Business Center Kazhakkootam, Trivandrum PIN-695582 India Facebook <https://facebook.com/sherin.co.in> LinkedIn <https://linkedin.com/in/sherina> Google+ <https://plus.google.com/+sherinAbdulkhareem> sherin.in <http://sherin.in>

2 1

Sieve Rule help
by Jorge Bastos 15 Aug '21

15 Aug '21

Howdy, I have an user with the rule below. Since it's discarding the match first, should it be stop there and don't redirect it to the next rule? Thanks in advanced, ### require ["date","relational","vacation"]; # rule:[xxx] if header :contains "from" "icnf.pt" { discard; } # rule:[redir] if true { redirect "jorge(a)myemail.pt"; stop; } ###

2 3

Undefined symbols (macOS Big Sur Intel) during compiling
by Beosdoc 13 Aug '21

13 Aug '21

Hi, I’m trying to compile Dovecot 2.3.15 on a Intel Mac with Big Sur and Xcode 12.5.1 with command line. I’ve compiled openSSL -1.1.1k in its own directory and pointed dovecot to use that directory. I’m getting undefined symbols during the linking (see below). I’ve been trying to figure out what’s missing but not having any luck Here’s the configure: CPPFLAGS="-I/Library/MWSrvrSrvcs/openssl/include" LDFLAGS="-L/Library/MWSrvrSrvcs/openssl/lib" ./configure --prefix=/Library/MWSrvrSrvcs/dovecot --with-ssl=openssl --with-gnu-ld --with-pgsql=auto --with-mysql=auto --with-sqlite=auto --with-gssapi=yes --with-ldap=auto --with-solr=no --with-libwrap=auto --with-ioloop=no --with-bzlib --with-zlib --with-notify=no --without-shared-libs --sysconfdir=/Library/MWSrvrSrvcs/Mail/Config --datadir=/Library/MWSrvrSrvcs/Mail/Data Here’s where it errors out: /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wno-duplicate-decl-specifier -Wstrict-aliasing=2 -module -avoid-version -L/Library/MWSrvrSrvcs/openssl/lib -o libssl_iostream_openssl.la -rpath /Library/MWSrvrSrvcs/dovecot/lib/dovecot dovecot-openssl-common.lo iostream-openssl.lo iostream-openssl-common.lo iostream-openssl-context.lo istream-openssl.lo ostream-openssl.lo -lssl -lcrypto libtool: link: gcc -o .libs/libssl_iostream_openssl.so -bundle .libs/dovecot-openssl-common.o .libs/iostream-openssl.o .libs/iostream-openssl-common.o .libs/iostream-openssl-context.o .libs/istream-openssl.o .libs/ostream-openssl.o -L/Library/MWSrvrSrvcs/openssl/lib -lssl -lcrypto -g -O2 -fstack-protector-strong Undefined symbols for architecture x86_64: "_buffer_append", referenced from: _openssl_iostream_error in iostream-openssl-common.o _o_stream_ssl_sendv in ostream-openssl.o "_buffer_create_dynamic", referenced from: _o_stream_ssl_sendv in ostream-openssl.o "_buffer_delete", referenced from: _o_stream_ssl_flush_buffer in ostream-openssl.o "_buffer_free", referenced from: _o_stream_ssl_destroy in ostream-openssl.o "_buffer_get_writable_size", referenced from: _o_stream_ssl_sendv in ostream-openssl.o _o_stream_ssl_get_buffer_avail_size in ostream-openssl.o "_default_pool", referenced from: _openssl_iostream_set_error in iostream-openssl.o _openssl_iostream_bio_sync in iostream-openssl.o _openssl_iostream_handle_error in iostream-openssl.o _openssl_iostream_create in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _openssl_iostream_set_log_prefix in iostream-openssl.o _openssl_iostream_free in iostream-openssl.o ... "_i_debug", referenced from: _openssl_iostream_set_error in iostream-openssl.o _openssl_iostream_handle_error in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _openssl_info_callback in iostream-openssl.o _openssl_iostream_verify_client_cert in iostream-openssl.o _ssl_iostream_context_init_common in iostream-openssl-context.o _ssl_servername_callback in iostream-openssl-context.o ... "_i_error", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o _ssl_tmp_dh_callback in iostream-openssl-context.o "_i_fatal", referenced from: _ssl_iostream_openssl_init in iostream-openssl.o _ssl_iostream_context_init_common in iostream-openssl-context.o _ssl_ctx_use_certificate_chain in iostream-openssl-context.o "_i_fatal_status", referenced from: _dovecot_openssl_malloc in dovecot-openssl-common.o _dovecot_openssl_realloc in dovecot-openssl-common.o _openssl_iostream_error in iostream-openssl-common.o "_i_info", referenced from: _openssl_iostream_verify_client_cert in iostream-openssl.o "_i_panic", referenced from: _dovecot_openssl_common_global_unref in dovecot-openssl-common.o _openssl_iostream_shutdown in iostream-openssl.o _openssl_iostream_bio_sync in iostream-openssl.o _openssl_iostream_handle_error in iostream-openssl.o _openssl_iostream_create in iostream-openssl.o _openssl_iostream_unref in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o ... "_i_strdup", referenced from: _openssl_iostream_set_error in iostream-openssl.o _openssl_iostream_bio_sync in iostream-openssl.o _openssl_iostream_handle_error in iostream-openssl.o _openssl_iostream_create in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _openssl_iostream_set_log_prefix in iostream-openssl.o _openssl_iostream_verify_client_cert in iostream-openssl.o ... "_i_strdup_printf", referenced from: _openssl_iostream_create in iostream-openssl.o "_i_stream_alloc", referenced from: _i_stream_ssl_read in istream-openssl.o "_i_stream_close", referenced from: _openssl_iostream_shutdown in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _i_stream_ssl_close in istream-openssl.o "_i_stream_create", referenced from: _openssl_i_stream_create_ssl in istream-openssl.o (maybe you meant: _openssl_i_stream_create_ssl) "_i_stream_free_buffer", referenced from: _i_stream_ssl_destroy in istream-openssl.o "_i_stream_get_data", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_i_stream_get_data_size", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o _i_stream_ssl_read in istream-openssl.o "_i_stream_get_error", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_i_stream_get_fd", referenced from: _openssl_i_stream_create_ssl in istream-openssl.o "_i_stream_get_name", referenced from: _openssl_iostream_create in iostream-openssl.o "_i_stream_get_root_io", referenced from: _openssl_iostream_create in iostream-openssl.o "_i_stream_read_data", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_i_stream_ref", referenced from: _openssl_o_stream_create_ssl in ostream-openssl.o "_i_stream_set_input_pending", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_i_stream_set_name", referenced from: _openssl_iostream_create in iostream-openssl.o "_i_stream_skip", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_i_stream_try_alloc", referenced from: _i_stream_ssl_read in istream-openssl.o "_i_stream_unref", referenced from: _openssl_iostream_free in iostream-openssl.o _o_stream_ssl_destroy in ostream-openssl.o "_i_strocpy", referenced from: _pem_password_callback in iostream-openssl-context.o "_io_stream_set_error", referenced from: _i_stream_ssl_read in istream-openssl.o _o_stream_ssl_flush in ostream-openssl.o _o_stream_ssl_flush_buffer in ostream-openssl.o "_iostream_ssl_module_init", referenced from: _ssl_iostream_openssl_init in iostream-openssl.o "_o_stream_close", referenced from: _openssl_iostream_shutdown in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _o_stream_ssl_close in ostream-openssl.o "_o_stream_cork", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_o_stream_create", referenced from: _openssl_o_stream_create_ssl in ostream-openssl.o (maybe you meant: _openssl_o_stream_create_ssl) "_o_stream_flush", referenced from: _openssl_iostream_shutdown in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _plain_flush_callback in ostream-openssl.o "_o_stream_get_buffer_avail_size", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_o_stream_get_buffer_used_size", referenced from: _o_stream_ssl_flush in ostream-openssl.o _o_stream_ssl_get_buffer_used_size in ostream-openssl.o "_o_stream_get_error", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_o_stream_get_fd", referenced from: _openssl_o_stream_create_ssl in ostream-openssl.o "_o_stream_get_name", referenced from: _openssl_iostream_create in iostream-openssl.o "_o_stream_ref", referenced from: _plain_flush_callback in ostream-openssl.o "_o_stream_send", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_o_stream_set_flush_callback", referenced from: _openssl_o_stream_create_ssl in ostream-openssl.o "_o_stream_set_flush_pending", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o _o_stream_ssl_sendv in ostream-openssl.o _o_stream_ssl_flush in ostream-openssl.o _o_stream_ssl_flush_pending in ostream-openssl.o _plain_flush_callback in ostream-openssl.o "_o_stream_set_max_buffer_size", referenced from: _o_stream_ssl_set_max_buffer_size in ostream-openssl.o "_o_stream_set_name", referenced from: _openssl_iostream_create in iostream-openssl.o "_o_stream_set_no_error_handling", referenced from: _openssl_iostream_create in iostream-openssl.o "_o_stream_switch_ioloop_to", referenced from: _o_stream_ssl_switch_ioloop_to in ostream-openssl.o "_o_stream_uncork", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o _openssl_iostream_create in iostream-openssl.o "_o_stream_unref", referenced from: _openssl_iostream_free in iostream-openssl.o _plain_flush_callback in ostream-openssl.o "_pool_alloconly_create", referenced from: _ssl_iostream_context_init_common in iostream-openssl-context.o "_safe_memset", referenced from: _openssl_iostream_load_key in iostream-openssl-context.o "_ssl_iostream_check_cert_validity", referenced from: _openssl_iostream_handshake in iostream-openssl.o "_ssl_iostream_context_ref", referenced from: _openssl_iostream_create in iostream-openssl.o _openssl_iostream_change_context in iostream-openssl.o "_ssl_iostream_context_unref", referenced from: _openssl_iostream_change_context in iostream-openssl.o _openssl_iostream_free in iostream-openssl.o _openssl_iostream_context_init_client in iostream-openssl-context.o _openssl_iostream_context_init_server in iostream-openssl-context.o "_ssl_iostream_handshake", referenced from: _openssl_iostream_shutdown in iostream-openssl.o _openssl_iostream_more in iostream-openssl.o "_ssl_iostream_has_valid_client_cert", referenced from: _openssl_iostream_cert_match_name in iostream-openssl.o _openssl_iostream_get_peer_name in iostream-openssl.o "_ssl_iostream_settings_init_from", referenced from: _ssl_iostream_context_init_common in iostream-openssl-context.o "_ssl_iostream_unref", referenced from: _openssl_iostream_destroy in iostream-openssl.o _i_stream_ssl_destroy in istream-openssl.o _o_stream_ssl_destroy in ostream-openssl.o "_str_c", referenced from: _openssl_iostream_error in iostream-openssl-common.o "_str_printfa", referenced from: _openssl_iostream_error in iostream-openssl-common.o "_t_malloc0", referenced from: _openssl_iostream_get_peer_name in iostream-openssl.o _openssl_iostream_error in iostream-openssl-common.o "_t_str_new", referenced from: _openssl_iostream_error in iostream-openssl-common.o "_t_strconcat", referenced from: _openssl_iostream_create in iostream-openssl.o "_t_strdup_noconst", referenced from: _openssl_iostream_use_certificate in iostream-openssl.o _openssl_iostream_load_key in iostream-openssl-context.o _ssl_iostream_context_init_common in iostream-openssl-context.o _ssl_ctx_use_certificate_chain in iostream-openssl-context.o "_t_strdup_printf", referenced from: _dovecot_openssl_common_global_set_engine in dovecot-openssl-common.o _openssl_iostream_handle_error in iostream-openssl.o _openssl_iostream_create in iostream-openssl.o _openssl_iostream_get_security_string in iostream-openssl.o _openssl_iostream_use_certificate in iostream-openssl.o _openssl_iostream_verify_client_cert in iostream-openssl.o _openssl_cert_match_name in iostream-openssl-common.o ... ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[3]: *** [libssl_iostream_openssl.la] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Thanks Mitch

3 4

Preventing clients from trying to create folders under inbox
by Bryan K. Walton 13 Aug '21

13 Aug '21

Our Dovecot installation is configured as such: mail_location = mbox:/var/vmail/%u:DIRNAME=.mboxdata:INBOX=/var/vmail/%u/INBOX:INDEX=/var/vmail/indexes/%u This allows us to continue using mbox formatted files, storing those mbox data files in a file called .mboxdata. This allows our users to create folders and subfolders. The only exception to this is our inboxes, which are more traditional mbox files. However, we have some Outlook users that insist on trying to create subfolders of their inbox. This doesn't work, since the inbox is a file. But Outlook still does it and it causes sync issues, as there is now a subfolder under the user's inbox, but that subfolder is ONLY present in Outlook (it isn't present on the server). Is there anything that we can configure so that Dovecot instructs Outlook that it cannot attempt to create subfolders under the inbox, but allow subfolders elsewhere? Thanks! Bryan

2 1

Re: Help to setup a Unix socket based authentication server for dovecot in Python
by dovecot＠ptld.com 13 Aug '21

13 Aug '21

> So this is a single system user with single email, there are a > number of system users and email accounts, I don't need to use SQL or > LDAP or another password file. I can write python script to analyze > the logins and the mail folders including quota and send to socket file > , But how the formats as dict ? How the user input ( email/password > ) send to that unix socket ? I mean the format The documentation > doesn't say anything about it. https://doc.dovecot.org/configuration_manual/authentication/dict/ There is an example script done in perl at the bottom of the page. Maybe it can give you hints as to the format needed for a python script. On the same page it also says: When given a proxy URL the Dict backend speaks a simple protocol over a UNIX socket. The protocol is defined in src/lib-dict/dict-client.h https://github.com/dovecot/core/blob/master/src/lib-dict/dict-client.h

1 0

Help to setup a Unix socket based authentication server for dovecot in Python
by Sherin A 13 Aug '21

13 Aug '21

Hi, I am building a custom server platform in which dovecot is used for imap/pop . But the default authentication mechanism is not suitable for me becuase each domain will have different system users and different location for mail storage . So I need to create a custom authentication mechanism using python . There is an option to use Key-value authentication (dict) database via socket as per https://doc.dovecot.org/configuration_manual/authentication/dict/#complete-… The above documentation link have a sample perl script too to send authentication to uri = proxy:/var/run/auth_proxy_dovecot/socket:somewhere So my question is how the inputs are send to the socket file ? in which format ? How the result return ? and in which format ? Let us say I can create a python socket program that can listen to /var/run/auth_proxy_dovecot/socket for getting the inputs from dovecot , but what is the format Is it like the following AUTH PLAIN USER test(a)myemail.com PASS mypassword I looked into the documentation and developer documentation, I am unable to see how dovecot send the data , I can see a sample perl for answering dict lookups. Any one have a python alternative for it. ? -- *Sherin Abdulkhareem* Chairman & Managing Director email Email sherin(a)sherin.in <mailto:sherin@sherin.in> mobile Mobile (+91)9496533234 office Office (+91)4716007799 *Syslint Technologies India Private Limited* First Floor,Asiatic Business Center Kazhakkootam, Trivandrum PIN-695582 India Facebook <https://facebook.com/sherin.co.in> LinkedIn <https://linkedin.com/in/sherina> Google+ <https://plus.google.com/+sherinAbdulkhareem> sherin.in <http://sherin.in>

2 1

Sharing or not sharing the INBOX
by Stephane Magnier 13 Aug '21

13 Aug '21

Hi, I am using Dovecot and Sendmail ( as lmtp server ) I would like to consider having some users using there emails and having their "private Ibox" ( I would say as a normal use ) and some users sharing their Inbox 1) Should I consider using and configure 2 different email servers ? ( one sharing the inbox of any users, the other one, not sharing the inbox...) or I can have this config with the same email server ? 2) if so, how to tell Dovecot to get for user1 and user2 the same Inbox and (user3 and user4) Not sharing their inbox ? - ... like private emails and a tech support, which should share the same folder 3) or Can I say : User1 -> User 4 have private emails Inbox.. but user3 and user4 are also sharing the same folder /var/spool/mail/support/ for example I should admit that I don't know where to go :-( Thanks for your help

1 1

dovecot 2.3.16 fail one test on s390x, alpine linux
by Milan P. Stanić 13 Aug '21

13 Aug '21

Hi, I'm trying to upgrade dovecot from version 2.3.15 to 2.3.16 for alpine linux. Build and 'make check' pass on all alpine architectures except on s390x which is big-endian while all other are little-endian. here is the part from CI build log which fails: ------------ mail cache size corruption ........................................... : ok 0 / 10 tests failed test-mail-cache-fields.c:50: Assert failed: cache_field.last_used == priv->field.last_used && cache_field.decision == priv->field.decision test-mail-cache-fields.c:65: Assert failed: cache_field.last_used == priv->field.last_used && cache_field.decision == priv->field.decision test-mail-cache-fields.c:94: Assert failed: cache_field.last_used == priv->field.last_used && cache_field.decision == priv->field.decision mail cache fields read-write ......................................... : FAILED 1 / 1 tests failed make[3]: *** [Makefile:1279: check-local] Error 1 make[3]: Leaving directory '/builds/alpine/aports/main/dovecot/src/dovecot-2.3.16/src/lib-index' make[2]: *** [Makefile:1049: check-am] Error 2 make[2]: Target 'check' not remade because of errors. make[2]: Leaving directory '/builds/alpine/aports/main/dovecot/src/dovecot-2.3.16/src/lib-index' Making check in lib-storage ------------ Full log is here: https://gitlab.alpinelinux.org/alpine/aports/-/jobs/459182/raw -- Kind regards

3 8

Dovecot (>= 2.3.15) is not properly replicating Expunge commands running in a containerised environment
by A. Schulze 12 Aug '21

12 Aug '21

Hello *, migrating a mailbox setup for several tens of thousands of customers to Docker containers running on Debian VMs, we are currently observing Expunge commands not being replicated properly between two Dovecot containers. Delivering a new message into someones' inbox is replicated instantly via dsync (using TLS). However, expunging a message from the very same inbox via > doveadm expunge -u [users' email address] mailbox '*' header Message-ID [MID of the message in question] is not replicated, since a > doveadm fetch -u [users' email address] text header Message-ID [MID of the message in question] still returns the mail on the replica. Sometimes, a > doveadm replicator replicate [users' email address] fixes this, but mostly, it does not. While doing all of this, these messages are logged by Dovecot: > doveadm: Info: copy from INBOX: box=INBOX, uid=13, msgid=<[MID of the message in question]>, size=1793 > doveadm: Info: expunge: box=INBOX, uid=12, msgid=<[MID of the message in question]>, size=1793 > doveadm: Error: dsync(x): I/O has stalled, no activity for 600 seconds (last sent=handshake, last recv=handshake) > doveadm: Error: Timeout during state=slave_recv_last_common > doveadm: Error: dsync(x): I/O has stalled, no activity for 600 seconds (last sent=mailbox_delete, last recv=mailbox_delete) > doveadm: Error: Timeout during state=slave_recv_mailbox > doveadm: Error: dsync(SSL x): I/O has stalled, no activity for 600 seconds (version not received) > doveadm: Error: Timeout during state=slave_recv_handshake Unfortunately, these errors do not seem to be reproducible very well - the underlying behaviour however is. Setting > replication_sync_timeout = 2s , as mentioned in https://doc.dovecot.org/settings/plugin/replication-plugin/ (the "s" seems to be bogus, though, as Dovecot complains about an invalid timeframe given) results in these messages: > doveadm(x): Error: doveadm client disconnected before handshake: Connection closed > replicator: Panic: data stack: Out of memory when allocating 268435496 bytes > replicator: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(backtrace_append+0x3d) [0x7ff8f55343dd] -> /usr/local/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7ff8f55344fe] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xfcc6b) [0x7ff8f5540c6b] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xfcd01) [0x7ff8f5540d01] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x533e7) [0x7ff8f54973e7] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x52dcb) [0x7ff8f5496dcb] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xf6625) [0x7ff8f553a625] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x11c248) [0x7ff8f5560248] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xf2655) [0x7ff8f5536655] -> /usr/local/lib/dovecot/libdovecot.so.0(buffer_write+0x67) [0x7ff8f5536867] -> dovecot/replicator(replicator_queue_push+0xe9) [0x5619b1b81a39] -> dovecot/replicator(+0x61f8) [0x5619b1b811f8] -> dovecot/replicator(+0x58ef) [0x5619b1b808ef] -> dovecot/replicator(+0x5ab2) [0x5619b1b80ab2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7ff8f5556b99] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x131) [0x7ff8f5558101] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7ff8f5556c3c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7ff8f5556db0] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ff8f54cb7b3] -> dovecot/replicator(main+0x18f) [0x5619b1b7fc4f] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7ff8f52a309b] -> dovecot/replicator(_start+0x2a) [0x5619b1b7fd0a] > replicator: Fatal: master: service(replicator): child 175 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2) Not having observed this behaviour on physical or virtual Linux machines, we are pretty much out of ideas on what to do. https://dovecot.org/pipermail/dovecot/2019-November/117467.html sounds like being a related issue. Thank you in advance for any hints and replies. root@x:/# doveconf -n # 2.3.15 (0503334ab1): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.15 (e6a84e31) # OS: Linux 4.9.0-16-amd64 x86_64 Debian 10.10 # Hostname: x auth_cache_negative_ttl = 1 mins auth_cache_size = 10 k auth_master_user_separator = "#" auth_mechanisms = plain login auth_verbose_passwords = sha1 doveadm_password = # hidden, use -P to show it doveadm_port = 12345 first_valid_uid = 8 imap_hibernate_timeout = 1 mins imap_id_log = * lmtp_save_to_detail_mailbox = yes log_path = /dev/stderr log_timestamp = login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> %k mail_access_groups = dovecot mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_gid = mail mail_location = maildir:~/Maildir/ mail_plugins = acl quota mail_log notify replication mail_uid = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext vacation-seconds passdb { args = /etc/dovecot/conf.d/ldap-searches/ldap.conf driver = ldap } plugin { acl = vfile acl_defaults_from_inbox = yes acl_shared_dict = file:/data/acl_shared_dict/acl_shared_dict mail_replica = tcps:x sieve_extensions = +vacation-seconds sieve_vacation_min_period = 1m } pop3_uidl_format = %f postmaster_address = x protocols = imap lmtp pop3 sieve replication_dsync_parameters = -d -N -l 60 -U service aggregator { fifo_listener replication-notify-fifo { group = mail mode = 0666 user = mail } unix_listener replication-notify { group = mail mode = 0666 user = mail } } service auth-worker { user = $default_internal_user } service auth { unix_listener /socket/dovecot/x/sasl-server { group = postfix mode = 0660 user = postfix } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-hibernate { unix_listener imap-hibernate { user = mail } } service imap { unix_listener imap-master { group = dovecot mode = 0660 } } service lmtp { inet_listener { port = 24 ssl = yes } unix_listener /socket/dovecot/x/lmtp-server { mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = mail mode = 0600 user = mail } } ssl_cert = </acme/live/x/cert+intermediate.pem ssl_cipher_list = ECDHE+AESGCM:ECDHE+CHACHA20 ssl_client_ca_dir = /etc/ssl/certs/ ssl_client_cert = </acme/live/x/cert+intermediate.pem ssl_client_key = # hidden, use -P to show it ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_options = no_ticket ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/conf.d/ldap-searches/ldap.conf driver = ldap } userdb { args = /etc/dovecot/conf.d/ldap-searches/ldap-catchall.conf driver = ldap } verbose_proctitle = yes protocol imap { imap_metadata = yes mail_plugins = acl quota mail_log notify replication fts fts_squat imap_acl imap_quota mail_log notify } protocol lmtp { mail_plugins = acl quota mail_log notify replication sieve notify mail_log ssl = required ssl_ca = </etc/ssl/certs/ca-certificates.crt ssl_min_protocol = TLSv1.3 ssl_verify_client_cert = yes }

1 1

Panic: lib-sql: Too many bind args
by Joseph D Wagner 12 Aug '21

12 Aug '21

From /etc/dovecot/dovecot.conf: mail_attribute_dict = proxy::attr dict { attr = pgsql:/etc/dovecot/dovecot-attr-sql.conf.ext } From /etc/dovecot/dovecot-attr-sql.conf.ext: map { pattern = $key table = attributes fields { attr_name = $key } username_field = username value_field = attr_value } From /var/log/maillog: dovecot[51153]: dict(51395): Panic: lib-sql: Too many bind args (2) for statement: SELECT attr_name FROM attributes WHERE attr_name LIKE AND username = ? dovecot[51153]: dict(51395): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xf8cab) [0x7f4c92274cab] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf8d47) [0x7f4c92274d47] -> /usr/lib64/dovecot/libdovecot.so.0(+0x55c1d) [0x7f4c921d1c1d] -> dovecot/dict(+0x649a) [0x55921892349a] -> dovecot/dict(sql_statement_query+0x3e) [0x55921892a14e] -> dovecot/dict(+0xa296) [0x559218927296] -> /usr/lib64/dovecot/libdovecot.so.0(dict_iterate+0x23) [0x7f4c92238a23] -> dovecot/dict(+0x7860) [0x559218924860] -> dovecot/dict(+0x808c) [0x55921892508c] -> dovecot/dict(+0x8200) [0x559218925200] -> dovecot/dict(dict_command_input+0xee) [0x55921892534e] -> dovecot/dict(+0x6b9b) [0x559218923b9b] -> /usr/lib64/dovecot/libdovecot.so.0(connection_input_default+0x1b2) [0x7f4c9226fd42] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x73) [0x7f4c9228c413] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x135) [0x7f4c9228dac5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f4c9228c4c0] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x48) [0x7f4c9228c628] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x17) [0x7f4c92203fd7] -> dovecot/dict(main+0x185) [0x559218923895] -> /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f4c91dda493] -> dovecot/dict(_start+0x2e) [0x5592189238ee] Joseph D Wagner

2 3

ACL's using SQL Backend
by Joseph D Wagner 11 Aug '21

11 Aug '21

I don't want to use vfile as the acl backend. I want to use sql, but it seems to be sparsely documented. Would this work? create table acls ( acl_name varchar(255) not null, username varchar(320) not null default '', acl_value varchar not null, constraint acls_pk primary key (acl_name, username) ); map { pattern = $key table = acls fields { acl_name = $key } username_field = username value_field = acl_value } Thanks. Joseph D. Wagner

1 0

Get Director vhostCount
by William Edwards 11 Aug '21

11 Aug '21

Hi, I would like to monitor each mail server's amount of available vhosts, so I can take action when a certain threshold is reached (e.g. adding mail servers). I'm using Dovecot 2.3.4.1 with Director. My first idea was to use the Doveadm HTTP API, but the 'directorStatus' command doesn't return the 'vhostCount' attribute (although the 'directorAdd' and 'directorUpdate' commands take it as input). My second idea was to directly connect to the 'director-admin' socket and look at the output of 'HOST-LIST'. I can find all the information I need in doveadm-connection.c, but I'm not getting the impression that we're meant to interact with the socket directly. I can't find protocol documentation, and the error message "doveadm not compatible with this server (mixed old and new binaries?)" when passing faulty input gives me the impression that the socket is only meant to be used by Dovecot directly. My third idea is to parse 'doveadm director status', but in that case I'd like to know if that output is likely to change in the future. New major versions aside, of course. Or, if anyone else has a better idea, which could very well be the case, I'd love to hear how people monitor this in the real world. TIA. -- With kind regards, William Edwards

1 1

JWT local validation
by Tomas Habarta 11 Aug '21

11 Aug '21

Hello, I have a working setup with Roundcube using OAuth2 -- introspection works without any problem, unfortunately local validation does not as tokens are missing "typ" header (seems that one is indeed optional per RFC7519 and therefore not present in the implementation in place). Is there any parameter to assert the token type or any other workaround to make local validation work as it currently fails with: oauth2 failed: Local validation failed: Cannot find 'typ' field. dovecot v2.3.15 Roundcube 1.5beta CentOS 8 Thanks, regards Tomas

2 3

Test for implicit keep within a sieve script
by Eric Durand 11 Aug '21

11 Aug '21

Hi folks, Is there a good way to test for an implicit keep in a sieve script ? At the end of my sieve script, if a message still has an implicit keep, it will end up in my inbox, and I would like to push a notification. Right now I am doing this with an ad-hoc variable that is essentially emulating the implicit keep, is there a better way to do this ? Thanks! Eric

2 1

pigeonhole-0.5.16 compilation error?
by Sylvain Robitaille 11 Aug '21

11 Aug '21

Hello Dovecot folks ... In response to the recent announcement of Dovecot-2.3.16 and pigeonhole-0.5.16, we decided to update our installation (full disclosure: this is really an update from dovecot-1.2.x in progress; we're working on a development system where we already had dovecot-2.3.x installed and running). The update of dovecot itself (compiled from source), to version 2.3.16 was quite uneventful, and I can report that it's working. We're seeing some behaviour with indexing that will need attention, but I suspect that that's a matter of configuration, and is completely unrelated to what I'm reporting. More disclosure: we've never used nor compiled pigeonhole on our systems before. We've been using procmail for decades, but are now looking into potentially switching to sieve, and as I understand it, that means installing pigeonhole. I downloaded dovecot-2.3-pigeonhole-0.5.16 at the same time that I downloaded dovecot-2.3.16, a few days ago. My build-time configure and make for pigeonhole is relatively simple, but fails to build: ./configure --prefix=/local/pkg/pigeonhole-0.5.16/root \ --sbindir=/local/pkg/pigeonhole-0.5.16/root/bin \ --localstatedir=/var \ --mandir=/local/pkg/pigeonhole-0.5.16/root/man \ --with-dovecot=/local/pkg/dovecot-CURRENT/root/lib/dovecot make -j2 "/local/pkg/dovecot-CURRENT/root/lib/dovecot" is correct for us, if I understand the installation instructions correctly: -rw-r--r-- 1 root root 1324 Aug 3 14:03 /local/pkg/dovecot-CURRENT/root/lib/dovecot/dovecot-config The make fails, while compiling sieve-extprograms-common.c: sieve-extprograms-common.c: In function ‘sieve_extprogram_run’: sieve-extprograms-common.c:639:7: error: ‘PROGRAM_CLIENT_EXIT_STATUS_INTERNAL_FAILURE’ undeclared (first use in this function) case PROGRAM_CLIENT_EXIT_STATUS_INTERNAL_FAILURE: ^ sieve-extprograms-common.c:639:7: note: each undeclared identifier is reported only once for each function it appears in sieve-extprograms-common.c:641:7: error: ‘PROGRAM_CLIENT_EXIT_STATUS_FAILURE’ undeclared (first use in this function) case PROGRAM_CLIENT_EXIT_STATUS_FAILURE: ^ sieve-extprograms-common.c:643:7: error: ‘PROGRAM_CLIENT_EXIT_STATUS_SUCCESS’ undeclared (first use in this function) case PROGRAM_CLIENT_EXIT_STATUS_SUCCESS: ^ I decided to check against dovecot-2.3-pigeonhole-0.5.15, figuring that problems compiling that version likely would have been reported already, and sure enough I find the following difference in this file: --- ./dovecot-2.3-pigeonhole-0.5.15/src/plugins/sieve-extprograms/sieve-extprograms-common.c 2021-06-14 09:41:29.000000000 -0400 +++ ./dovecot-2.3-pigeonhole-0.5.16/src/plugins/sieve-extprograms/sieve-extprograms-common.c 2021-08-06 05:26:46.000000000 -0400 @@ -635,6 +635,14 @@ int sieve_extprogram_set_input_mail int sieve_extprogram_run(struct sieve_extprogram *sprog) { - return program_client_run(sprog->program_client); + switch (program_client_run(sprog->program_client)) { + case PROGRAM_CLIENT_EXIT_STATUS_INTERNAL_FAILURE: + return -1; + case PROGRAM_CLIENT_EXIT_STATUS_FAILURE: + return 0; + case PROGRAM_CLIENT_EXIT_STATUS_SUCCESS: + return 1; + } + i_unreached(); } ... and no mention of these PROGRAM_CLIENT_EXIT_STATUS_* constants anywhere else in the code, in either version. Have I stumbled onto an omission in the packaged sources, or is there some other package missing on my system, or is there perhaps even some other explanation for what I'm seeing? I've checked the mailing list archive and found no mention of anyone else having the same (or similar) problem, so I do think it's possible that I'm just missing something ... Thanks in advance for any insight folks might be able to give me ... -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------

1 1

GSSAPI mail home mapping problem
by Lucas Castro 10 Aug '21

10 Aug '21

Hello, I'm trying to map authenticated kerberos users to mail_location, The problem when I set mail_home = /var/mail/virtual/domain1.zw.loca/%n works fine. But if mail_home is set as /var/mail/virtual/%d/%n I get Apr 12 19:53:18 postfix10 dovecot: imap-login: Login: user=<user0>, method=GSSAPI, rip=172.16.0.44, lip=10.16.0.220, mpid=2428, session=<iPA4Yc6/lJCsEAAs> Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Added userdb setting: plugin/=yes Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Effective uid=5000, gid=5000, home=/var/mail/virtual/domain1.zw.local =login_user=user0/user0 Right here, I can't figure out why login_user=user0/user0 Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail Now login_user=user0 Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: maildir++: root=/var/mail/virtual/domain1.zw.local =login_user=user0/user0/mail, index=, indexpvt=, control=, inbox=/var/mail/virtual/domain1.zw.local =login_user=user0/user0/mail, alt= then login_user=user0/user0/mail Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Mailbox INBOX: Mailbox opened because: SELECT doveconf -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 5.10.0-7-amd64 x86_64 Debian 10.6 # Hostname: postfix10.zw.local auth_debug = yes auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/imap.keytab auth_mechanisms = gssapi auth_verbose = yes disable_plaintext_auth = no import_environment = TZ KRB5CCNAME=/etc/dovecot/imap.ticket KRB5_KTNAME=/etc/dovecot/imap.keytab mail_debug = yes mail_gid = 5000 mail_home = /var/mail/virtual/%d/%n mail_location = maildir:~/mail mail_privileged_group = mail mail_uid = 5000 namespace inbox { disabled = no inbox = yes list = 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 = type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = " imap lmtp pop3" service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = no ssl_cert = </etc/dovecot/private/dovecot.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { driver = prefetch } protocol lmtp { postmaster_address = postmaster(a)zw.local } egrep -v "^$|^#" /etc/dovecot/dovecot-ldap.conf.ext uris = ldap://ldap10.zw.local auth_bind = yes sasl_bind = yes sasl_mech = gssapi sasl_realm = zw.local debug_level = -1 ldap_version = 3 base = dc=zw,dc=local user_attrs = \ =user=%{ldap:mail} \ =login_user=%{ldap:uid} user_filter = (uid=%n) pass_attrs = \ =user=%{ldap:uid},\ =k5principals=%{ldap:krbPrincipalName} pass_filter = (&(objectClass=krbPrincipalAux)(uid=%n)) -- Lucas Castro

1 1

Replication stalled by failed attemts to read attachments (mail_attachment_dir)
by Ralf Becker 09 Aug '21

09 Aug '21

I'm migrating an older Dovecot 2.2.19 installation with dbox and mail_attachment_dir to 2.3.15 with replication to a second server. The storage from the old server was rsync'ed to a new server running Dovecot 2.3.15 in a container using similar configuration with dbox and mail_attachments. That servers alone seems to run fine. As a next step I tried to establish replication to the second empty server, which is configured to use mdbox and no mail_attachment_dir, as the rest of my Dovecot servers. Looking at "doveadm replicator status '*'" some of the mailboxes replicate correct, but roughly half of them fail :( Looking a the Dovecot log with mail_debug=yes shows the replication fails on the source (server with dbox and mail_attachment_dir) typically with one of two errors: a) attachment has different size: Aug 05 15:41:58 doveadm: Debug: Mailbox INBOX: UID 30: Looked up field date.received from mail cache Aug 05 15:41:58 doveadm: Error: dsync(cdaf50f7580e): read(attachments-connector(/var/dovecot/imap/<domain>/<user>/mailboxes/INBOX/dbox-Mails/u.30)) failed: read(/var/dovecot/imap/attachments/64/4e/644ecfbc09223b8ccafc6f36aa86603cde91e76716b9b5ed0cf875bc0e183b6b4581d671f8321647be99f26d2d22088e999714529e189b25a6e7d5b428fbf5d5-1a6b701e68c9c050b10a0000838cbfe1-f86a701e68c9c050b10a0000838cbfe1-30[base64:18 b/l]) failed: Stream is larger than expected (262658 > 262657, eof=1) (last sent=mail, last recv=mail_request (EOL)) showing on the other log as: Aug 05 15:49:18 doveadm: Debug: Mailbox INBOX: UID 29: Looked up field guid from mail cache Aug 05 15:49:19 doveadm: Error: dsync(142878d8d6bf): read() failed: read(10.44.99.1) failed: dot-input stream ends without '.' line (last sent=mail_request (EOL), last recv=mail) b) attachment is not found at all: Aug 05 15:43:58 doveadm(<user>@<domain> 1441): Debug: fs-sis: fs-sis: fs-posix: open(/var/dovecot/imap/attachments/e2/0a/e20ab165f3a2e7164520341cddb06cd053dc1a87fdd5c6360b45c20a2c9d33576c8ea2daa42062f9bb0fd94f9c5f9919ad86fb11e29effe3bdf4e853fa7c0e1d-20a0b63613e6c050620b0000838cbfe1-c8d5221c39a40b61250900007dc04144-3) failed: No such file or directory Aug 05 15:43:58 doveadm(<user>@<domain> 1441): Error: dsync(cdaf50f7580e): read(attachments-connector(/var/dovecot/imap/<domain>/<user>/mailboxes/INBOX/dbox-Mails/u.3)) failed: read(/var/dovecot/imap/attachments/e2/0a/e20ab165f3a2e7164520341cddb06cd053dc1a87fdd5c6360b45c20a2c9d33576c8ea2daa42062f9bb0fd94f9c5f9919ad86fb11e29effe3bdf4e853fa7c0e1d-20a0b63613e6c050620b0000838cbfe1-c8d5221c39a40b61250900007dc04144-3[base64:19 b/l]) failed: open(/var/dovecot/imap/attachments/e2/0a/e20ab165f3a2e7164520341cddb06cd053dc1a87fdd5c6360b45c20a2c9d33576c8ea2daa42062f9bb0fd94f9c5f9919ad86fb11e29effe3bdf4e853fa7c0e1d-20a0b63613e6c050620b0000838cbfe1-c8d5221c39a40b61250900007dc04144-3) failed: No such file or directory (last sent=mail, last recv=mail_request (EOL)) That caused the replication to fail and not newer mails to be replicated for the given user and mailbox, which can be verified eg. with "doveadm mailbox status -u <user>@<domain> all inbox". The concerned mails are pretty old / the attachment itself can not be recovered, and nothing can be done about them. But how can I repair the mailbox, so all unaffected mails / attachments get replicated? I already tried multiple "doveadm force-resync -u <user>@<domain> INBOX" in case a) with no visible effect / still same error. Both Dovecot configurations are attached, in case they matter ... Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

2 4

Pigeonhole Sieve Config Warning
by dovecot＠ptld.com 09 Aug '21

09 Aug '21

In the sieve plugin settings i have plugin { ... sieve_user_email = %u } Variables pages says %u = full username (e.g. user@domain) This config seems to work in practice, the email is from: the users email address. However on starting dovecot im getting a warning twice: dovecot[35893]: managesieve: Warning: sieve: Invalid address value for setting `sieve_user_email': Missing domain dovecot[35893]: master: Dovecot v2.3.8 (9df20d2db) starting up for imap, lmtp, sieve dovecot[35897]: managesieve: Warning: sieve: Invalid address value for setting `sieve_user_email': Missing domain So is there really an issue? Or just an improper warning?

2 3

v2.3.16 released
by Timo Sirainen 09 Aug '21

09 Aug '21

Hi, One interesting thing in this release is the support for configuring OAUTH2 openid-configuration element. It would be nice if IMAP clients started supporting this feature to enable OAUTH2 for all IMAP servers, not just Gmail and a few others. This would allow all kinds of new authentication methods for IMAP and improve the authentication security in general. https://dovecot.org/releases/2.3/dovecot-2.3.16.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.16.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot <https://hub.docker.com/r/dovecot/dovecot> * Any unexpected exit() will now result in a core dump. This can especially help notice problems when a Lua script causes exit(0). * auth-worker process is now restarted when the number of auth requests reaches service auth-worker { service_count }. The default is still unlimited. + Event improvements: Added data_stack_grow event and http-client category. See https://doc.dovecot.org/admin_manual/list_of_events/ + oauth2: Support RFC 7628 openid-configuration element. This allows clients to support OAUTH2 for any server, not just a few hardcoded servers like they do now. See openid_configuration_url setting in dovecot-oauth2.conf.ext. + mysql: Single statements are no longer enclosed with BEGIN/COMMIT. + dovecot-sysreport --core supports multiple core files now and does not require specifying the binary path. + imapc: When imap_acl plugin is loaded and imapc_features=acl is used, IMAP ACL commands are proxied to the remote server. See https://doc.dovecot.org/configuration_manual/mail_location/imapc/ + dict-sql now supports the "UPSERT" syntax for SQLite and PostgreSQL. + imap: If IMAP client disconnects during a COPY command, the copying is aborted, and changes are reverted. This may help to avoid many email duplicates if client disconnects during COPY and retries it after reconnecting. - master process was using 100% CPU if service attempted to create more processes due to process_min_avail, but process_limit was already reached. v2.3.15 regression. - Using attachment detection flags wrongly logged unnecessary "Failed to add attachment keywords" errors. v2.3.13 regression. - IMAP QRESYNC: Expunging UID 1 mail resulted in broken VANISHED response, which could have confused IMAP clients. v2.3.13 regression. - imap: STORE didn't send untagged replies for \Seen changes for (shared) mailboxes using INDEXPVT. v2.3.10 regression. - rawlog_dir setting would not log input that was pipelined after authentication command. - Fixed potential infinite looping with autoexpunging. - Log event exporter: Truncate long fields to 1000 bytes - LAYOUT=index: ACL inheritance didn't work when creating mailboxes - Event filters: Unquoted '?' wildcard caused a crash at startup - fs-metawrap: Fix to handling zero sized files - imap-hibernate: Fixed potential crash at deinit. - acl: dovecot-acl-list files were written for acl_ignore_namespaces - program-client (used by Sieve extprograms, director_flush_socket) may have missed status response from UNIX and network sockets, resulting in unexpected failures.

7 16

Problem migrating POP accounts into dovecot
by Jesús Ángel del Pozo Domínguez 09 Aug '21

09 Aug '21

Hello, I am trying to migrate mailboxes from an old pop/imap server to a new one using Dovecot 2.3.15. The old server uses tpop3d and courier as POP and IMAP servers, respectively. Whereas I can migrate IMAP mailboxes without many problems, I am facing difficulties while trying to do the same with POP ones. The problem is that dsync opens simultaneous connections to the remote POP server, so the remote mailbox gets locked and dsync can not copy the messages. This is the command I am using to migrate POP mailboxes: # doveadm -Dv -c dovecot-migration.conf -o pop3c_password="*******" backup -R -u test2(a)testemail.domain.com pop3c: And these are some interesting lines from the output of the above command: Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Looking up IP address Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Connecting to 10.0.0.104:110 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Authenticating as 'test2(a)testemail.domain.com' (with USER+PASS) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: Adding field pop3.uidl to cache for the first time (uid=1) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: UID 1: Opened mail because: virtual size (Cache file is unusable) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: quota: quota_over_flag check: STORAGE ret=3value=3 limit=104857600 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: quota: quota_over_flag check: MESSAGE ret=4value=1 limit=0 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: quota: quota_over_flag=0((null)) vs currently overquota=0 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain M: Locking done locally in /var/mail/testemail.domain.com/test2/.dovecot-sync.lock (local hostname=tremedal.domain.com, remote hostname=tremedal.domain.com) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain S: Namespace has location pop3c: Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Looking up IP address Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Connecting to 10.0.0.104:110 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Authenticating as 'test2(a)testemail.domain.com' (with USER+PASS) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: Adding field pop3.uidl to cache for the first time (uid=1) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain S: Local mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1628081654 uid_next=2 subs=no last_change=0 last_subs=0 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain M: Remote mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1628081654 uid_next=2 subs=no last_change=0 last_subs=0 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain M: Mailbox INBOX: local=00000000000000000000000000000000/0/0, remote=c92f64f79f0d1ed01e6d5b314f04886c/0/1: mailbox not selectable yet Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Namespace : /var/mail/testemail.domain.com/test2/Mailbox/inbox doesn't exist yet, using default permissions Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Namespace : Using permissions from /var/mail/testemail.domain.com/test2/Mailbox: mode=0700 gid=default Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Namespace : /var/mail/testemail.domain.com/test2/Mailbox/inbox doesn't exist yet, using default permissions Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Namespace : Using permissions from /var/mail/testemail.domain.com/test2/Mailbox: mode=0700 gid=default Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain S: Mailbox INBOX: local=c92f64f79f0d1ed01e6d5b314f04886c/0/1, remote=00000000000000000000000000000000/0/0: mailbox not selectable yet Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Looking up IP address Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Connecting to 10.0.0.104:110 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Authenticating as 'test2(a)testemail.domain.com' (with USER+PASS) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: Adding field pop3.uidl to cache for the first time (uid=1) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: doveadm-sieve: Iterating Sieve mailbox attributes Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: Pigeonhole version 0.5.15 (e6a84e31) initializing Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Storage path `/var/mail/testemail.domain.com/test2/sieve' not found Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Using active Sieve script path: /var/mail/testemail.domain.com/test2/.dovecot.sieve Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Using script storage path: /var/mail/testemail.domain.com/test2/sieve Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Using permissions from defaults: mode=0700 gid=-1 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Created storage directory /var/mail/testemail.domain.com/test2/sieve/tmp Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Relative path to sieve storage in active link: sieve/ Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: sync: Synchronization active Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain M: Import INBOX: Last common UID=0. Delayed expunges= Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain M: Import INBOX: Import change type=save GUID=1a82a18794d50d5de2b3f0faa8a6e27c UID=1 hdr_hash= result=Mail's UID is above local UIDNEXT - No more local mails found Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: UID 1: Opened mail because: mail stream Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: Adding field size.virtual to cache for the first time (uid=1) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: Adding field size.physical to cache for the first time (uid=1) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox POP3-MIGRATION-NS/INBOX: Mailbox opened because: pop3_migration Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Looking up IP address Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Connecting to 10.0.0.104:110 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Authenticating as 'test2(a)testemail.domain.com' (with USER+PASS) Aug 04 14:54:22 dsync(test2(a)testemail.domain.com): Error: pop3_migration: Couldn't sync mailbox POP3-MIGRATION-NS/INBOX: Unable to open mailbox; it may be locked by another concurrent session. In the remote server I get these lines from the tpop3d log: Aug 4 14:54:14 lmail1 tpop3d[1887]: authcontext_new_user_pass: began session for `test2(a)testemail.domain.com' with mysql; uid 30018, gid 8 Aug 4 14:54:14 lmail1 tpop3d[1887]: fork_child: [6]test2(a)testemail.domain.com(10.0.0.105): successfully authenticated with mysql Aug 4 14:54:14 lmail1 tpop3d[2270]: mailspool_new_from_file: indexed mailspool /var/spool/mail/testemail.domain.com/test2 (2831 bytes) in 0.000s Aug 4 14:54:14 lmail1 tpop3d[2270]: connections_post_select: connection_read: client [6]test2(a)testemail.domain.com(10.0.0.105): closed connection Aug 4 14:54:14 lmail1 tpop3d[2270]: authcontext_delete: finished session for `test2(a)testemail.domain.com' with mysql Aug 4 14:54:14 lmail1 tpop3d[1887]: authcontext_new_user_pass: began session for `test2(a)testemail.domain.com' with mysql; uid 30018, gid 8 Aug 4 14:54:14 lmail1 tpop3d[1887]: fork_child: [5]test2(a)testemail.domain.com(10.0.0.105): successfully authenticated with mysql Aug 4 14:54:14 lmail1 tpop3d[2272]: mailspool_new_from_file: indexed mailspool /var/spool/mail/testemail.domain.com/test2 (2831 bytes) in 0.000s Aug 4 14:54:14 lmail1 tpop3d[2272]: connections_post_select: connection_read: client [5]test2(a)testemail.domain.com(10.0.0.105): closed connection Aug 4 14:54:14 lmail1 tpop3d[2272]: authcontext_delete: finished session for `test2(a)testemail.domain.com' with mysql Aug 4 14:54:14 lmail1 tpop3d[1887]: authcontext_new_user_pass: began session for `test2(a)testemail.domain.com' with mysql; uid 30018, gid 8 Aug 4 14:54:14 lmail1 tpop3d[1887]: fork_child: [5]test2(a)testemail.domain.com(10.0.0.105): successfully authenticated with mysql Aug 4 14:54:14 lmail1 tpop3d[2273]: mailspool_new_from_file: indexed mailspool /var/spool/mail/testemail.domain.com/test2 (2831 bytes) in 0.000s Aug 4 14:54:14 lmail1 tpop3d[1887]: authcontext_new_user_pass: began session for `test2(a)testemail.domain.com' with mysql; uid 30018, gid 8 Aug 4 14:54:14 lmail1 tpop3d[1887]: fork_child: [5]test2(a)testemail.domain.com(10.0.0.105): successfully authenticated with mysql Aug 4 14:54:22 lmail1 tpop3d[2274]: mailspool_new_from_file: failed to lock /var/spool/mail/testemail.domain.com/test2: Resource temporarily unavailable Aug 4 14:54:22 lmail1 tpop3d[2274]: dotfile_unlock(/var/spool/mail/testemail.domain.com/test2): lockfile does not have our PID Aug 4 14:54:22 lmail1 tpop3d[2274]: authcontext_delete: finished session for `test2(a)testemail.domain.com' with mysql Aug 4 14:54:22 lmail1 tpop3d[2273]: connections_post_select: connection_read: client [5]test2(a)testemail.domain.com(10.0.0.105): closed connection Aug 4 14:54:22 lmail1 tpop3d[2273]: authcontext_delete: finished session for `test2(a)testemail.domain.com' with mysql As you can see, in the first five lines the first connection from dsync is opened and closed. Then, the same sequence is repeated again (second connection from dsync). However, on opening the third connection, it is not closed before the fourth one is opened. On authenticating a user, the tpop3d server locks the mailbox to prevent other clients wirting to it. That is why the fourth connection fails as it can not get a lock for the mailbox: Aug 4 14:54:22 lmail1 tpop3d[2274]: mailspool_new_from_file: failed to lock /var/spool/mail/testemail.domain.com/test2: Resource temporarily unavailable Aug 4 14:54:22 lmail1 tpop3d[2274]: dotfile_unlock(/var/spool/mail/testemail.domain.com/test2): lockfile does not have our PID Could you please tell me how can I avoid this problem? I wonder why dsync opens so many connections to the remote server, and why it does not close the previous connections before opening new ones. Regards,

2 2

dsync and sieve script
by Andrea Gabellini 09 Aug '21

09 Aug '21

Hello, I'm testing the migration from and old dovecot server 2.2.24 to a new one with 2.3.15 using this command: doveadm -c /etc/dovecot/dovecot-migration.conf -o mail_fsync=never backup -x "shared" -x "shared/*" -x "dovecot/sieve" -R -T 60 -u andrea.gabellini.sc(a)telecomitalia.sm imapc: This command replicate email messages but not the sieve scripts. The esclusion of "dovecot/sieve" is mandatory because the old server is misconfigured and doesn't have a separate home and maildir location. Is dsync able to replicate the sieve scripts or I'm doing something wrong? Thanks, Andrea -- __________________________ The less a man knows the easier it is to convince him he knows it all. __________________________ 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.

2 1

doveadm Mail storage autodetection failed
by Joseph D Wagner 09 Aug '21

09 Aug '21

I have a mixture of virtual mailboxes and local mailbox. I got this: # doveadm quota get -A doveadm(nobody): Error: Namespace '': Mail storage autodetection failed with home=/ doveadm(systemd-coredump): Error: Namespace '': Mail storage autodetection failed with home=/ doveadm(polkitd): Error: Namespace '': Mail storage autodetection failed with home=/ doveadm(unbound): Error: Namespace '': Mail storage autodetection failed with home=/etc/unbound doveadm(libstoragemgmt): Error: Namespace '': Mail storage autodetection failed with home=/var/run/lsm doveadm(clevis): Error: Namespace '': Mail storage autodetection failed with home=/var/cache/clevis doveadm(cockpit-ws): Error: Namespace '': Mail storage autodetection failed with home=/ doveadm(setroubleshoot): Error: Namespace '': Mail storage autodetection failed with home=/var/lib/setroubleshoot doveadm(sssd): Error: Namespace '': Mail storage autodetection failed with home=/ doveadm(insights): Error: Namespace '': Mail storage autodetection failed with home=/var/lib/insights doveadm(chrony): Error: Namespace '': Mail storage autodetection failed with home=/var/lib/chrony doveadm(cockpit-wsinstance): Error: Namespace '': Mail storage autodetection failed with home=/nonexisting doveadm(rngd): Error: Namespace '': Mail storage autodetection failed with home=/var/lib/rngd doveadm(dovenull): Error: Namespace '': Mail storage autodetection failed with home=/usr/libexec/dovecot doveadm(opendkim): Error: Namespace '': Mail storage autodetection failed with home=/run/opendkim doveadm(vmail): Error: Namespace '': Mail storage autodetection failed with home=/home/vmail doveadm(policyd-spf): Error: Namespace '': Mail storage autodetection failed with home=/home/policyd-spf doveadm(nginx): Error: Namespace '': Mail storage autodetection failed with home=/var/lib/nginx ... plus valid and expected output here. Is there some way I can get rid of these errors while preserving local delivery for valid local mailboxes? Thanks. Config below. Joseph D. Wagner # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-315.el8.x86_64 x86_64 CentOS Stream release 8 # Hostname: <localdomain> auth_mechanisms = plain login auth_username_format = %{if;%d;eq;<localdomain>;%Ln;%Lu} dict { attr = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } imap_metadata = yes mail_attribute_dict = proxy::attr mail_plugins = " quota" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Archive { auto = create special_use = \Archive } mailbox "Deleted Items" { auto = create special_use = \Trash } mailbox Drafts { auto = create special_use = \Drafts } mailbox "Junk Email" { auto = create special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Items" { special_use = \Sent } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { driver = pam } plugin { imap_compress_deflate_level = 9 quota = count:User quota quota_vsizes = yes sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_cipher_list = AESGCM:CHACHA20:AESCCM:ARIA:+AES128:+ARIA128:!aNULL:!eNULL:!aDH:!kRSA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } userdb { driver = passwd } protocol lmtp { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota imap_zlib" }

2 1