- dovecot - dovecot.org

dovecot update from 2.1.16 to 2.2.36.4 but I have a trouble.
by iriya＠peach.ocn.ne.jp 13 Dec '19

13 Dec '19

Hi,I have a troble and can not resolve it. Please help me. I updated dovecot from 2.1.16 to 2.2.36.4. As a result, I had a client who could not access via imap. The client showed his logs (- folder not exists:INBOX ) I did not change dovecot config files. So I searched a difference between 2.1.16 and 2.2.36.4, I discovered . Please refer below results. [2.1.16] a03 list "" "*" * LIST (\HasChildren) "." "INBOX" * LIST (\HasNoChildren) "." "INBOX.Drafts" * LIST (\HasNoChildren) "." "INBOX.Sent" * LIST (\HasNoChildren) "." "INBOX.Spam" * LIST (\HasNoChildren) "." "INBOX.Trash" [2.2.36.4] a03 list "" "*" * LIST (\HasChildren) "." INBOX * LIST (\HasNoChildren) "." INBOX.Drafts * LIST (\HasNoChildren) "." INBOX.Sent * LIST (\HasNoChildren) "." INBOX.Spam * LIST (\HasNoChildren) "." INBOX.Trash For example, I noticed INBOX and "INBOX". 2.2.36.4 dovecot is no [""]. What should I do?

2 1

v2.2.36 to v2.3.8 maildirlock bug
by lty＠cndns.com 12 Dec '19

12 Dec '19

Dear all, Dovecot upgraded from v2.2.36 to v2.3.8 There is no problem with the configuration, but the lock directory seems to have an error. [root@spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1 Panic: BUG: No IOs or timeouts set. Not waiting for infinity. 19276[root@spam dovecot]# Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xe227a) [0x7f1cb567a27a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe2321) [0x7f1cb567a321] -> /usr/lib64/dovecot/libdovecot.so.0(+0x40f31) [0x7f1cb55d8f31] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf93b4) [>xrf1cb56913b4] -> /usr/ Lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x28) [0x7f1cb5693918] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5c) [0x7f1cb5691aac] -> /usr/lib64/dovecot/libdovecot. So.0(io_loop_run+0x38) [0x7f1cb5691cc8] -> /usr/libexec/dovecot/maildirlock(main+0x242) [0x7f1cb5b522c2] -> /lib64/libc.so.6(__libc_start_main+0x100) [0x7f1cb5222d20] -> / Usr/libexec/dovecot/maildirlock(+0xfa9) [0x7f1cb5b51fa9] After google seems to be a bug, this is the address Https://bugs.gentoo.org/682498 If this is not fixed, we are temporarily unable to upgrade to use the new version. Will the next version be fixed? We are looking forward to seeing that we have returned v2.2.36

4 5

Lightweight LMTP daemon to avoid overkill MTA
by William Edwards 12 Dec '19

12 Dec '19

Hi, My situation is as follows. -An internet-facing spam filter relays email to destination mail server (Dovecot) with SMTP. - Dovecot should take email and deliver it to user's mailboxes. I guess I'd need LMTP for this. - An external SMTP relay is already in place. I am thinking of using Dovecot submission to relay to the external relaying cluster. So, both relaying and routing are done externally - the Dovecot machine should only store mail. Of course, there should also be a mechanism that takes care of local delivery to Dovecot, like LMTP. Usually, I would use an MTA like Exim to take care of local delivery. I feel like a fully-featured MTA is overkill, though, as all other roles such an MTA would fulfill - relaying and spam filtering - are fulfilled on external servers. Q: Does anyone know of a lightweight LMTP daemon that can take care of local delivery to Dovecot without the need for a full MTA? With kind regards, William Edwards T. 040 - 711 44 96 E. wedwards(a)cyberfusion.nl

3 7

Submission config being ignored
by William Edwards 12 Dec '19

12 Dec '19

I'm having trouble setting up submission with Dovecot proxy. The submission config seems to be getting ignored, but I'm probably doing something wrong. Expected behaviour: have messages sent to submission ports (25, 465) relayed to `submission_relay_host`. -- root@imapproxy1:~# cat /etc/dovecot/conf.d/20-submission.conf submission_logout_format = in=%i out=%o submission_relay_host = smtp.prorelay.nl submission_relay_port = 587 submission_relay_ssl = starttls submission_relay_ssl_verify = no service submission { } service submission-login { inet_listener submission_25 { port = 25 } inet_listener submission_465 { port = 465 ssl = yes } } -- What happens instead: Dovecot is attempting to send mail to the host specified in the passdb file: root@imapproxy1:~# cat /etc/virtual/xalys.nl/passwd test:$password.:8:8::/home/test.nl/test:/bin/false:userdb_quota_rule=*:bytes=0 proxy_maybe=y host=$ipaddr How do I get Dovecot to relay mail sent to submission ports to 'submission_relay_host'? Met vriendelijke groeten, William Edwards T. 040 - 711 44 96 E. wedwards(a)cyberfusion.nl submission_relay_host

2 2

Duplicate e-mail with Dovecot and Sieve
by Claudio Corvino 12 Dec '19

12 Dec '19

Hi everyone, we have a duplicate e-mail problem with Dovecot 2.2.13 (LMTP as MDA) on a Debian 8 server. Our users are on external LDAP. We just need to setup a vacation responder (with Sieve) for our employees with a redirect to an alias (a distribution list), let's call it /LIST(a)domain.com/, that comprehends even the user that just activated the out of office. This generates a loop: when someone write to LIST(a)domain.com every user of the aforementioned distribution list receives a duplicate e-mail generated from the sieve script of the user with vacation responder active that contains the redirect to LIST(a)domain.com. We just tried activating the duplicate extension into sieve script but the redirected e-mail has a different MSG-ID and it's not recognized as a duplicate by the server. Our dovecot conf is: /# 2.2.13: /etc/dovecot/dovecot.conf auth_mechanisms = plain login default_vsz_limit = 512 M disable_plaintext_auth = no dotlock_use_excl = no info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_fsync = never mail_location = maildir:~/Maildir mail_max_userip_connections = 50 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 duplicate mmap_disable = yes passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-ldap-archive.conf driver = ldap } plugin { sieve = file:/var/www/html/ooo/%n/script sieve_dir = /var/www/html/ooo/%n/ sieve_duplicate_default_period = 1m sieve_duplicate_max_period = 1d sieve_extensions = +vnd.dovecot.duplicate +notify +imapflags +vacation-seconds sieve_global = /etc/dovecot/sieve/ sieve_max_redirects = 10 sieve_user_log = file:/var/www/html/ooo/%n/sieve_error.log sieve_vacation_default_period = 1d sieve_vacation_max_period = 90d sieve_vacation_min_period = 5s } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } user = root } service imap-login { process_limit = 200 } service lmtp { executable = lmtp -L process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } user = vmail } service managesieve-login { executable = /usr/lib/dovecot/managesieve-login inet_listener sieve { port = 4190 } process_min_avail = 10 service_count = 1 } service managesieve { executable = /usr/lib/dovecot/managesieve } ssl_cert = </etc/ssl/*xxxxxxxxxxxxxxxxxxxxxxxx* ssl_cipher_list = ALL:!LOW:!aNULL:!eNULL:!SSLv2:!RC4:!MD5:!DES:!EXP:!SEED:!IDEA:!3DES ssl_key = </etc/ssl/private/*xxxxxxxxxxxxxxxxxx* userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap-archive.conf driver = ldap } protocol lda { auth_socket_path = /var/run/dovecot/auth-master hostname = *xxxxxxxxxxxxxxxxx* info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log mail_plugins = " autocreate sieve quota" } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log log_path = /var/log/dovecot-lmtp-errors.log mail_plugins = " autocreate sieve quota" postmaster_address = postmaster@*xxxxxxxxxx* } protocol sieve { info_log_path = log_path = mail_max_userip_connections = 10 managesieve_implementation_string = dovecot managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 }/ An example of user sieve script is: /require ["vnd.dovecot.duplicate","copy","fileinto","vacation-seconds"]; # rule:[Outofoffice] if true { vacation :addresses "xxxxxxx(a)domain.tld" :subject "Automatic Reply" text: / /<Text here> . ; fileinto "INBOX";/ / redirect "LIST(a)domain.com";/ /}/ Please could someone give us support on the matter? Removing the redirect from sieve user script is not an option :-) Thanks Cheers -- *Claudio Corvino IT Systems Administrator* Trust Italia S.p.A. <https://www.trustitalia.it/> *DigiCert Italian Affiliate Certified Partner Platinum Elite* Via Flaminia, 497 - 00191 Roma *tel.: +39 06332287* *fax: +39 063336145* *e-mail: * ccorvino(a)trustitalia.it <mailto:ccorvino@trustitalia.it> *website: * www.trustitalia.it <https://www.trustitalia.it> Symantec Authentication Service Le modalità di trattamento dei dati a cui è stato dato il consenso e le relative finalità sono consultabili al link <https://www.trustitalia.it/archivio/legal_agreements/informativa_privacy_em…>. Qualora non desiderasse ricevere le nostre comunicazioni, potrà comunicarlo mediante il seguente link <https://www.trustitalia.it/site/info_css/05110101/revoca-del-consenso>. Inoltre, in ogni momento, potrà modificare o cancellare i dati presenti nel nostro archivio contattandoci all'indirizzo privacy(a)trustitalia.it <mailto:privacy@trustitalia.it> Se possibile non stamparmi! Se possibile, non stamparmi!

8 13

Lmtp redirection to other backend server
by Marc Roos 11 Dec '19

11 Dec '19

I have currently a working local delivery working ok on 2 backend servers. The backend servers use slapd/nslcd/nscd for local accounts. If I enable proxy=yes in the lmtp config section, I am getting this error 'auth: Debug: passdb out: FAIL#0111#011reason=Configured passdbs don't support credentials lookups' which is obvious because I do not have a passdb. I am not sure if it is possible to get this value from the system environment eg. nslcd/nscd, without the need to configure some separate ldap lookup in dovecot? Or do I really need to configure a ldap lmtp lookup just for this host attribute? What would be an efficient solution?

1 1

dkim + arc
by Aki Tuomi 11 Dec '19

11 Dec '19

If I don't get swamp of errors with this email, I'll stop the From munging starting tomorrow. There is now ARC signing done for mails. Lets see how this works, if we can stop rewriting from I'll be happy. Aki

2 2

Ban Atomia.com?
by LuKreme 11 Dec '19

11 Dec '19

Can a mail admin ban atomia.com from posting? I mean, I like the idea that every post is clogging up their support queue, but really, not that much. Sent from my iPhone

5 4

RE: lmtp delivery auth error, but successful delivery
by Marc Roos 11 Dec '19

11 Dec '19

It is a test environment, so I do not have much data. I am testing with 'mail wegjd' seems to deliver ok every time. -----Original Message----- Subject: RE: lmtp delivery auth error, but successful delivery Can you let me know if you get lots of delivery failures? Aki -------- Original message -------- From: Marc Roos <M.Roos(a)f1-outsourcing.eu> Date: 11/12/2019 22.16 (GMT+02:00) To: dovecot <dovecot(a)dovecot.org> Subject: lmtp delivery auth error, but successful delivery How to fix the auth passwd-file unknown user error? I guess I maybe have something active that I do not need? With this configuration in sendmail FEATURE(`local_lmtp',`[IPC]',`TCP [192.168.10.44] 24')dnl MAILER(local)dnl Dec 11 21:04:18 mailsvr dovecot: lmtp(15361): Connect from 192.168.10.44 Dec 11 21:04:18 mailsvr dovecot: auth: passwd-file(wegjd,192.168.10.44): unknown user Dec 11 21:04:18 mailsvr dovecot: lmtp(wegjd): msgid=<201912112004.xBBK4HoZ015358(a)mailsvr.xxxxxx.xxx>: saved mail to INBOX Dec 11 21:04:18 mailsvr dovecot: lmtp(15361): Disconnect from 192.168.10.44: Successful quit With this configuration in sendmail: FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot/lmtp')dnl MAILER(local)dnl Dec 11 21:11:50 mailsvr dovecot: lmtp(15754): Connect from local Dec 11 21:11:51 mailsvr dovecot: auth: passwd-file(wegjd): unknown user Dec 11 21:11:51 mailsvr dovecot: lmtp(wegjd): msgid=<201912112011.xBBKBoRB015751(a)mailsvr.xxxxxx.xxx>: saved mail to INBOX Dec 11 21:11:51 mailsvr dovecot: lmtp(15754): Disconnect from local: Successful quit

1 0

lmtp delivery auth error, but successful delivery
by Marc Roos 11 Dec '19

11 Dec '19

How to fix the auth passwd-file unknown user error? I guess I maybe have something active that I do not need? With this configuration in sendmail FEATURE(`local_lmtp',`[IPC]',`TCP [192.168.10.44] 24')dnl MAILER(local)dnl Dec 11 21:04:18 mailsvr dovecot: lmtp(15361): Connect from 192.168.10.44 Dec 11 21:04:18 mailsvr dovecot: auth: passwd-file(wegjd,192.168.10.44): unknown user Dec 11 21:04:18 mailsvr dovecot: lmtp(wegjd): msgid=<201912112004.xBBK4HoZ015358(a)mailsvr.xxxxxx.xxx>: saved mail to INBOX Dec 11 21:04:18 mailsvr dovecot: lmtp(15361): Disconnect from 192.168.10.44: Successful quit With this configuration in sendmail: FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot/lmtp')dnl MAILER(local)dnl Dec 11 21:11:50 mailsvr dovecot: lmtp(15754): Connect from local Dec 11 21:11:51 mailsvr dovecot: auth: passwd-file(wegjd): unknown user Dec 11 21:11:51 mailsvr dovecot: lmtp(wegjd): msgid=<201912112011.xBBKBoRB015751(a)mailsvr.xxxxxx.xxx>: saved mail to INBOX Dec 11 21:11:51 mailsvr dovecot: lmtp(15754): Disconnect from local: Successful quit

1 0