- dovecot - dovecot.org

dovecot.conf "local hostname" uses only one resolved value
by James 14 Mar '19

14 Mar '19

https://wiki.dovecot.org/SSL/DovecotConfiguration#Different_certificates_pe… says: local 192.0.2.10 { # instead of IP you can also use hostname, which will be resolved However if the name resolves to multiple values only one is used. Test. Choose any name with multiple values, I created a local name: $ nslookup multi.lan Server: 127.0.0.1 Address: 127.0.0.1#53 Name: multi.lan Address: 192.168.1.2 Name: multi.lan Address: 192.168.1.3 Name: multi.lan Address: 192.168.1.1 Minimal dovecot.conf: local multi.lan { protocol imap { ssl_cert = </path/to/certs/multi.lan.crt ssl_key = </path/to/certs/multi.lan.key } } $ dovecot -n -c dovecot.conf # 2.3.5 (513208660): dovecot.conf ... local 192.168.1.2 { protocol imap { ssl_cert = </path/to/certs/multi.crt ssl_key = # hidden, use -P to show it } } Only 192.168.1.2 appears. In my real case with A and AAAA records, only the AAAA record is used. Testing with "openssl s_client -starttls imap ..." gives me the wrong certificate for the IPv4 address. Workaround: specify all addresses and do not use lookup. James.

1 0

dovecot/config processes one more time - which are safe to kill?
by Arkadiusz Miśkiewicz 14 Mar '19

14 Mar '19

Hello. The problem with dovecot/config processes never ending and spawning new one on each reload (https://www.dovecot.org/list/dovecot/2016-November/106058.html) is becoming a problem here: # ps aux|grep dovecot/config|wc -l 206 That's a lot of wasted memory - dovecot/config processes ate over 30GB of ram on 64GB box. Before killing dovecot/config processes: # free -m total used free shared buff/cache available Mem: 64437 61656 483 0 2297 after: # free -m total used free shared buff/cache available Mem: 64437 23676 37822 0 2939 Currently on dovecot 2.3.3. I guess it's very low priority to handle that, so: how can I figure out which dovecot/config processes are safe to be killed by external script? Does "all beside 2 newest ones" rule look sane? Thanks, -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

3 5

Quota questions
by Peter Hudec 14 Mar '19

14 Mar '19

Hi all, I’m a little bit confused about the quota plugin in dovecot and fighting the the issues the people had years ago. I spent readingg the old archives and the mailing list for 3 days and not able to get work some features. Single user quota is fine and simple, the group quota /for example domain based/ makes me unhappy. Setup: CentOS7, dovecot comunity repo, dovecot 2.3.5 1) domain quota recalc domain quota recalc do not work properly. The domain qouta usage is worknig well, hwhen receiving/deleting mail, generaly if the operations are incremental. But if I run domain quota recalc, the doveadm is setting the domain quota after each user calculation, that means the domain quota is set to the last user. 2) multiple quota roots and rules According the documentation, there could be possible, from the sample configuration file # Multiple quota roots are also possible, for example this gives each user # their own 100MB quota and one shared 1GB quota within the domain plugin { quota = dict:User quota::proxy::quota quota2 = dict:Group quota:%d:proxy::quota_domain quota_rule = *:storage=1024M quota2_rule = *:storage=2048M } But If I run [TEST] root(a)mail-store01.test.host.sk: /etc/dovecot # doveadm quota get -u '*' Username Quota name Type Value Limit % test01(a)test.host.sk User quota STORAGE 1 1024 0 test01(a)test.host.sk User quota MESSAGE 1 - 0 test01(a)test.host.sk Group quota STORAGE 7 - 0 test01(a)test.host.sk Group quota MESSAGE 3 - 0 test03(a)test.host.sk User quota STORAGE 7 1024 0 test03(a)test.host.sk User quota MESSAGE 3 - 0 test03(a)test.host.sk Group quota STORAGE 7 - 0 test03(a)test.host.sk Group quota MESSAGE 3 - 0 The idea is to have overall domain quota, but for user able to set it’s personal quota. regards Peter

2 3

dovecot-keywords are not preserved any more when moving mails between folders
by Piper Andreas 14 Mar '19

14 Mar '19

Hello, after an upgrade of dovecot-2.2.5 to dovecot-2.3.4 the dovecot-keywords, which in my case are set by thunderbird, are not preserved any more when moving a mail between folders. Are there any ideas, what may be the reason. Thanks for any hints on that, Andreas 'doveconf -n' gives: # 2.3.4 (0ecbaf23d): /etc/opt/csw/dovecot/dovecot.conf # Pigeonhole version 0.5.4 (60b0f48d) # OS: SunOS 5.11 i86pc # Hostname: xxxxx.hrz.uni-marburg.de auth_cache_negative_ttl = 0 auth_cache_size = 10 M auth_master_user_separator = * auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_ auth_username_format = %u auth_worker_max_count = 1024 base_dir = /var/run/dovecot/ default_vsz_limit = 1 G first_valid_gid = 30000 first_valid_uid = 30000 imap_max_line_length = 640 k mail_debug = yes mail_location = maildir:%h/.maildir mail_plugins = " mail_log notify" mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace { hidden = no inbox = yes list = yes location = maildir:%h/.maildir prefix = separator = / subscriptions = yes type = private } namespace inbox { hidden = yes inbox = no list = no location = maildir:%h/.maildir prefix = mail/ separator = / subscriptions = no type = private } passdb { args = /etc/dovecot.deny deny = yes driver = passwd-file } passdb { args = /etc/opt/csw/dovecot/private/passwd.masterusers driver = passwd-file master = yes } passdb { args = /etc/opt/csw/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_default = /var/lib/dovecot/default.sieve } pop3_uidl_format = %08Xv%08Xu postmaster_address = postmaster(a)hrz.uni-marburg.de protocols = imap pop3 lmtp sieve service auth-worker { user = $default_internal_user } service auth { client_limit = 6000 } service imap-login { process_min_avail = 64 service_count = 0 } service imap { process_limit = 4096 } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/opt/csw/ssl/certs/imap+pop.hrz.uni-marburg.de.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/opt/csw/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol imap { mail_max_userip_connections = 25 ssl_cert = </etc/opt/csw/ssl/certs/imap+pop.hrz.uni-marburg.de.pem ssl_key = # hidden, use -P to show it } protocol lmtp { mail_plugins = " mail_log notify sieve" } protocol pop3 { ssl_cert = </etc/opt/csw/ssl/certs/imap+pop.hrz.uni-marburg.de.pem ssl_key = # hidden, use -P to show it }

5 8

replication dropped imap flags
by Patrick Cernko 14 Mar '19

14 Mar '19

Hi list, I think, I found a bug in the replication setup, that drops (custom) flags like Thunderbird labels. I have set up a simple 2 node setup to reproduce and explain it: Host adove.mpi-klsb.mpg.de and bdove.mpi-klsb.mpg.de (doveconf -n attached) have dovecot-imapd (from repo.dovecot.org) installed on an ext4 filesystem. They only have one account "test" via /etc/dovecot/userdb ("test:testpassword:::Test User::/bin/bash:"). It's mailbox contains one message, that is flagged with "$label1": doveadm -f flow fetch -u test 'guid flags' ALL guid=d1516a2b5c08fc5b541d00005a350039 flags=\Recent $label1 Now I simulate a node reinstall on adove by uninstalling dovecot, removing all remnants, reinstalling and configuring it again: apt purge dovecot-core dovecot-imapd rm -rf /var/vmail /var/lib/dovecot /etc/dovecot apt install dovecot-imapd # disable system auth : > /etc/dovecot/conf.d/auth-system.conf.ext # create /var/vmail install -d -o nobody -g nogroup -m 700 /var/vmail # create userdb echo 'test:testpassword:::Test User::/bin/bash:' > /etc/dovecot/userdb # create /etc/dovecot/local.conf # not described here, the resulting doveconf -n is attached! service dovecot restart When I check the flags of the mail of user test now, the "$label1" is disapeared on both machines, even after "doveadm replicator replicate -f test": doveadm -f flow fetch -u test 'guid flags' ALL guid=d1516a2b5c08fc5b541d00005a350039 flags=\Recent Any hints what I am doing wrong here or is this really a bug? Best, -- Patrick Cernko <pcernko(a)mpi-klsb.mpg.de> +49 681 9325 5815 Joint Administration: Information Services and Technology Max-Planck-Institute fuer Informatik & Softwaresysteme

1 2

Am I right to assume certificate renewal with the same filename requires a dovecot reload/restart
by Guido Goluke, MajorLabel 14 Mar '19

14 Mar '19

Running dovecot 2.2, apologies if this question has been asked before: I've done the research but couldn't find anything. I run a server that uses dovecot as a MUA for Postfix and have a Let's Encrypt certificate that auto-renews through certbot on Ubuntu server 16.04. Dovecot did not pick up on the new certificate for the hostname. It did after a restart. To be clear: Let's Encrypt overwrites the previous certificate using the same path and filename. Am I right to assume that Dovecot needs a reload/restart after the certificate has been renewed in order to 'pick up' on the new certificate and if so, would I require a reload or a restart? Thank you in advance -- MajorLabel

4 8

Unable to set quota-fs plugin
by Eric Grammatico 14 Mar '19

14 Mar '19

Hello There, I am try desperatly to setup quota-fs plugin in Dovecot. I have the following configuration in place: /etc/dovecot/conf.d/10-mail.conf:mail_plugins = $mail_plugins quota zlib /etc/dovecot/conf.d/20-imap.conf: mail_plugins = $mail_plugins imap_quota /etc/dovecot/conf.d/90-quota.conf: plugin { #quota = dirsize:User quota #quota = maildir:User quota #quota = dict:User quota::proxy::quota #quota = fs:User quota:user quota = fs:user } The logs report the following error each time quota is requested: Mar 11 17:56:20 mail.xxxxxxx.xx dovecot[4923]: imap(xxxx): Error: Failed to get quota resource STORAGE: quota-fs: quotactl(Q_GETQUOTA, /dev/vda1) failed: No such file or directory I have no idea of which file or directory is missing. Any advice is welcome. Thanks and best regards, - Eric Grammatico _/)

3 11

rsync /old/server new/server ?
by Voytek Eymont 13 Mar '19

13 Mar '19

I have Centos 7 with dovecot/postfix/mysql Maildir I want to bring in a new server, new server will have same hostname as current, but, different IP I was intending to rsync -avzhe ssh vmail@oldserver:/var/vmail/vmail1 /var/vmail/vmail1 and, then, re run as necessary when/if mail still arrives on old server is that "a good plan" ...? TIA, V

4 3

recipient bcc and dovecot
by ＠lbutlr 13 Mar '19

13 Mar '19

I have a recipient_bcc_maps which contains a bcc map that is updated everyday: rbcc.pcre: if !/backup.*@/ /^([^+_]*).*(a)([^.]*)/ backup+071.${1}-${2}(a)adomain.tld endif the 071 portion is changed each day to the current day of the year. Everything works, but I get an error from dovecot on every message: lda(backup(a)adomain.tld): Error: User initialization failed: Namespace '': Ambiguous mail location setting, don't know what to do with it: /usr/local/virtual/backup(a)adomain.tld (try prefixing it with mbox: or maildir:) The mail is delivered two the right directory anyway, but after a temporary failure. I'd like to eliminate the error. the backup user is not a 'real' user (it is not in the lookup map) so should I bypass dovecot entirely in delivering these messages? (and if so, how) If not, where/how would I add the prefix maildir: Is there something I can add to dovecot to specifically deal with messages coming in to backup(a)adomain.tld and add the maildir: specification there? (Still on dovecot 2.2.35) -- And sometimes there's a short cut. A door or a gate. Some standing stones. A tree cleft by lightning, a filing cabinet. Maybe just a spot on some moorland somewhere... A place where THERE is very nearly HERE... If some people knew where such a spot was, if they had experience of what happens when here and there become entangled, then they might - if they knew how - mark such a spot with certain stones. In the hope that enough daft buggers would take it as a warning and keep away. (Lords and Ladies)

2 3

sieve vacation to an alias group
by Monis Monther 13 Mar '19

13 Mar '19

Hi, We have an alias group named xyz(a)example.com, this alias group has 3 actual users a(a)example.com, b(a)example.com and c(a)example.com We set vacation rule on the generic sieve rule, the problem is that 3 responses are sent to the original sender. (obviously because the rule is being executed with each user in the alias group) Is it possible to set auto response only once, we tried the ( :days 1) option but still all 3 respond back. How can such a setup be achieved. (Single auto response to an alias group) CentOS 7.5 dovecot-pigeonhole-2.3.4.1-1.x86_64 dovecot-2.3.4.1-1.x86_64 postfix 2.10-1 -- Best Regards Monis

4 14