- 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