- 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

Atomia user activation
by Atomia 11 Dec '19

11 Dec '19

Hi Claudio Corvino via dovecot, A new Atomia account has been created for you. Click the url below to activate your account and select a password! https://support.atomia.com/register/KfOvGCowO4TkXeAXlMH0 If the above URL does not work try copying and pasting it into your browser. If you continue to have problems, please feel free to contact us. Regards, Atomia

1 0

Can't see a specific mail in thunderbird but with mobile mail client
by J. Echter 11 Dec '19

11 Dec '19

Hi, i've seen a strange behaviour in our system (centos 7, dovecot 2.2.36 (1f10bfa63) today. We got a mail and it got delivered. Dec 3 07:56:25 mail postfix/lmtp[4013]: 915B0CEF4C2: to=<user@domain>, relay=mail[private/dovecot-lmtp], delay=1.5, delays=1.3/0.03/0.02/0.19, dsn=2.0.0, status=sent (250 2.0.0 <user@domain> AOhCNBgH5l2vDwAAtnFApQ:2 Saved) Dec 3 07:56:25 mail dovecot: lmtp(user@domain): AOhCNBgH5l2vDwAAtnFApQ:2: sieve: msgid=<289913405.81.1575356173625.JavaMail.SYSTEM@EUWS0716>: stored mail into mailbox 'INBOX' I also see this mail on the filesystem in the users cur dir: -rw-r--r--. 1 vmail vmail 448818 3. Dez 07:56 1575356184.M937345P4015.mail,S=611100,W=619338:2,Sae But i don't see this single mail in thunderbird and not in sogo (http://www.sogo.nu) but i can see it in the mobile mail client. Does anyone have a suggfestion what may be wrong here? I paste my dovecot -n output here: # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 3.10.0-1062.4.3.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) xfs # Hostname: mail.workgroup.local auth_master_user_separator = * auth_verbose = yes base_dir = /var/run/dovecot/ default_vsz_limit = 2 G imap_id_log = * imap_id_send = * log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_gid = 5000 mail_home = /DATEN/vmail/%Ld/%Ln mail_location = maildir:/DATEN/vmail/%Ld/%Ln/mail/ mail_plugins = " zlib fts fts_solr mail_log notify" mail_uid = 5000 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 namespace inbox { inbox = yes location = mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { fts = solr fts_autoindex = yes fts_solr = break-imap-search url=http://localhost:8983/solr/dovecot/ imapsieve_mailbox1_before = file:/etc/dovecot/sieve/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/etc/dovecot/sieve/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_new3 = Deleted Messages mailbox_alias_new4 = Papierkorb mailbox_alias_new5 = Spam mailbox_alias_old = Sent mailbox_alias_old2 = Sent mailbox_alias_old3 = Trash mailbox_alias_old4 = Trash mailbox_alias_old5 = Junk mailbox_list_index = yes recipient_delimiter = + sieve = /DATEN/vmail/%Ld/%Ln/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /usr/bin sieve_plugins = sieve_imapsieve sieve_extprograms zlib_save = gz zlib_save_level = 6 } protocols = sieve imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = root } service imap-login { chroot = login executable = /usr/libexec/dovecot/imap-login inet_listener imap { port = 0 } process_min_avail = 4 user = dovecot } service imap { executable = /usr/libexec/dovecot/imap } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { chroot = login user = dovecot } service pop3-login { chroot = login user = dovecot } ssl = required ssl_cert = </etc/pki/tls/certs/server.crt ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } valid_chroot_dirs = /var/spool/vmail protocol lda { mail_plugins = sieve postmaster_address = postmaster } protocol imap { mail_plugins = " zlib fts fts_solr mail_log notify imap_zlib imap_sieve" } protocol lmtp { mail_plugins = " zlib fts fts_solr mail_log notify quota sieve" postmaster_address = postmaster@domain } Thanks for any hints. Greetings Juergen

4 7

configured solr - question 2
by Wojciech Puchar 11 Dec '19

11 Dec '19

How to free space when say folders are removed in mail account. Or whole account is removed?

1 0

configured solr - question 1
by Wojciech Puchar 11 Dec '19

11 Dec '19

tested dovecot with solr. Works well. But it uses TCP connection between solr server and dovecot. Can it be password protected? I have other things than IMAP on the same server including remote users. i don't want them to be able to do mess.

1 0

Solr for Dovecot on Debian 9, package has correct binary?
by John Gateley 11 Dec '19

11 Dec '19

Hello, I am trying to get Solr full text searching working on Debian 9 with Dovecot, and I suspect the binary for dovecot does not have solr enabled (--with-solr). root@elephant:/etc/dovecot/conf.d# /usr/sbin/dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw fail SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) nss passwd prefetch passwd-file sql root@elephant:/etc/dovecot/conf.d# If I want to use solr, do I have to build dovecot myself? I'd prefer to use the debian package (Debian 9 for now). Thanks! John

2 1

Learning ham/spam with IMAPSieve: sa-learn-ham.sh terminated abnormally, signal 11
by Jens Rey 11 Dec '19

11 Dec '19

Hello, I am trying to get rspam to learn what is spam and what is ham. After following the IMAPSieve guide in the dovecot wiki (https://wiki2.dovecot.org/HowTo/AntispamWithSieve) the mail.log shows the following, whenever I move a mail from the Spam folder to my inbox and vice versa: sieve: Opening script 1 of 1 from `/usr/lib/dovecot/sieve/report-ham.sieve' sieve: Loading script /usr/lib/dovecot/sieve/report-ham.sieve sieve: Script binary /usr/lib/dovecot/sieve/report-ham.svbin successfully loaded sieve: binary save: not saving binary /usr/lib/dovecot/sieve/report-ham.svbin, because it is already stored sieve: Executing script from `/usr/lib/dovecot/sieve/report-ham.svbin' sieve: action pipe: running program: sa-learn-ham.sh Mailbox INBOX: Opened mail UID=2996 because: mail stream Debug: waiting for program `/usr/lib/dovecot/sieve/sa-learn-ham.sh' to finish after 0 msecs Error: program `/usr/lib/dovecot/sieve/sa-learn-ham.sh' terminated abnormally, signal 11 Error: sieve: pipe action: failed to pipe message to program `sa-learn-ham.sh': refer to server log for more information. [2019-11-17 00:39:33] Error: sieve: Execution of script /usr/lib/dovecot/sieve/report-ham.sieve failed My relevant dovecot configuration: plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * sieve = file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } $ dovecot --version 2.2.27 (c0f36b0) $ ls -l /usr/lib/dovecot/sieve/ total 24 -rw-r--r-- 1 root root 314 Nov 17 00:25 report-ham.sieve -rw-r--r-- 1 root root 448 Nov 17 00:30 report-ham.svbin -rw-r--r-- 1 root root 199 Nov 17 00:25 report-spam.sieve -rw-r--r-- 1 root root 354 Nov 17 00:30 report-spam.svbin -rwxr-xr-x 1 root root 41 Nov 17 00:32 sa-learn-ham.sh -rwxr-xr-x 1 root root 42 Nov 17 00:32 sa-learn-spam.sh $ cat sa-learn-ham.sh #!/bin/sh exec /usr/bin/rspamc learn_ham When I execute the script manually, it seems to work: $ cat [some-mail] | /usr/lib/dovecot/sieve/sa-learn-ham.sh Results for file: stdin (0.011 seconds) success = true; filename = "stdin"; scan_time = 0.012000; Again, with the same mail: $ cat [some-mail] | /usr/lib/dovecot/sieve/sa-learn-ham.sh Results for file: stdin (0.000 seconds) error = "<some-mail> has been already learned as ham, ignore it"; filename = "stdin"; scan_time = 0.0; Any ideas what causes the abnormal temrination of the script? Regards, Jens

3 8

Re: fts_solr: Error: fts_solr: received invalid uid '0'
by Fabian Kuran 10 Dec '19

10 Dec '19

Hi, > Am 23.09.2019 um 09:36 schrieb Filip Hanes <filip.hanes(a)ringier.sk>: > > > št 19. 9. 2019 o 15:30 Fabian via dovecot <dovecot(a)dovecot.org <mailto:dovecot@dovecot.org>> napísal(a): > Are there any other hints or tips regarding this „invalid uid ‚0‘"-message? > from fts-solr source: > case SOLR_XML_CONTENT_STATE_UID: > if (uint32_parse(str, len, &ctx->uid) < 0 || ctx->uid == 0) { > i_error("fts_solr: received invalid uid '%s'", t_strndup(str, len)); > It means that plugin tries to parse '0' when in state of parsing uid in xml response from solr or there is a bug in xml response parser. > I would enable rawlog_dir in config and look there for unusual response or extra tags near usual uid in xml response. For example: > plugin { > fts = solr > fts_solr = url=... rawlog_dir=/var/log/fts-solr/ > } > Thanks for this tip! The rawlog_dir option is not yet supported in our version 2.3.4. What we could provide now would be the XML-Response from Solr. The corresponding search query sometimes causes this error. But Solr's answer seems to always remain the same - in my opinion this already indicates a bug of Dovecot? The XML response can be downloaded here: https://owncloud.eideo.de/index.php/s/8oyJaf5HBK6zdbr Kind regards, Fabian

4 6

Re: Dovecot & OAuth
by Aki Tuomi 10 Dec '19

10 Dec '19

Hi! It seems there is a bug in the oauth2 driver, it loads the cert files wrong way. I'll make an internal bug report of this. Aki > On 06/12/2019 16:42 mizuki <mizuki0621(a)gmail.com> wrote: > > > Hi, > > For troubleshooting purposes, I change the read/write permissions on the certs and confirmed 'dovecot' can read them w/o problem, but still seeing the same errors. :( > Mizuki > > > On Fri, Dec 6, 2019 at 1:35 AM Aki Tuomi <aki.tuomi(a)open-xchange.com> wrote: > > > > Is the key/cert pair readable by dovecot user? auth process does not run as root. > > > > > > > > > > You can add > > > > > > > > > > service auth { > > > > extra_groups = ssl_cert > > > > } > > > > > > > > > > and chgrp the cert to ssl_cert to allow access to the cert. > > > > > > > > > > Aki > > > > > On 06/12/2019 04:16 mizuki via dovecot <dovecot(a)dovecot.org> wrote: > > > > > > > > > > > > > > > > > > > > > > > > I changed some of the tls options following the document, now config is following: > > > > > > > > > > > > > > > > > > > > > > > > tokeninfo_url = https://keycloak.com/auth/realms/mail/protocol/openid-connect/token > > > introspection_url = https://dovecot:7598e21b-ec34-481f-80d0-059bddae0923@keycloak.com/auth/real… > > > introspection_mode = post > > > debug = yes > > > rawlog_dir = /tmp/oauth2 > > > #force_introspection = yes > > > username_attribute = username > > > #active_attribute = active > > > #active_value = true > > > tls_ca_cert_file = /etc/pki/CA/certs/incommon-rsa-server-ca.crt > > > tls_cert_file = /etc/pki/dovecot/certs/dovecot.pem > > > tls_key_file = /etc/pki/dovecot/private/dovecot.pem > > > > > > > > > --------------- > > > > > > > > > > > > > > > The debug log is showing now slightly different msg ex: > > > > > > Dec 5 21:09:59 mktst4 dovecot: auth: Error: oauth2(mizuki,10.0.2.1,<29b4iv+YKuuCx5Tr>): oauth2 failed: Couldn't initialize SSL context: Can't load SSL certificate: There is no valid PEM certificate. > > > > > > > > > > > > > > > Still not able to connect to the keyclaok server. :( > > > > > > > > > > > > > > > > > > PS: Dovecot & Keycloak severs are both using the same legit cert/key pair with CA file configured. > > > > > > > > > > > > > > > Thanks! > > > > > > Mizuki > > > > > > > > > > > > > > > > > > > > > On Thu, Dec 5, 2019 at 3:06 PM Aki Tuomi < aki.tuomi(a)open-xchange.com> wrote: > > > > > > > > > > Before declaring it not ready for prime time, did you try setting > > > > > > > > tls_ca_cert_file = /etc/ssl/certs/ca-certificates.crt > > > > > > > > In the oauth2 configuration file as documented in https://doc.dovecot.org/configuration_manual/authentication/oauth2 ? > > > > > > > > Aki > > > > > > > > > On 05/12/2019 21:58 mizuki via dovecot < dovecot(a)dovecot.org> wrote: > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > We'd like to enable OAuth with Keycloak in Dovecot, after enabling 'OAUTHBEARER XOAUTH2' in Dovecot based on online document, I can confirm Dovecot is ready for OAuth using openssl command, however when the auth request comes in, it failed in establishing a SSL connection with Keycloak server on port 443, shown as following in debug logs. I can confirming using commands 'openssl s_client -connect <keycloak_server>:443' or 'curl -v https://<keycloak_server/' all returns normal and no errors. Altering some of the SSL options in dovecot such as 'ssl_ca = </etc/pki/CA/certs/root_ca.pem' or 'ssl_client_ca_file = </etc/pki/CA/certs/root_ca.pem' does not help either. The certificate are NOT self-signed but signed the legit authorities. So I'm not sure why dovecot could not establish the connections. > > > > > > > > >

3 4

OAuth2 mail client
by mizuki 10 Dec '19

10 Dec '19

Hi all, I'm wondering if there are any IMAP client software alternative to Thunderbird who can handle OAuth2 other than using gmail, yahoo etc (ex, talk to local auth provider)? Thunderbird does not seem to support well at the time being so I'm wondering what other choices we may have for our user communities. Thank you very much. Mizuki

1 0

Problem With Quota Dovecot
by Gter Marcelo 09 Dec '19

09 Dec '19

Hi Dears, I have one problem with Dovecot in My mailserver. Dovecot Quota setting is not working fine. plugin { quota = dict:User quota::file:MAILDIR/dovecot-quota quota_rule = *:storage=1GB } For example if i put the limit in 1GB, i have accounts in my mailbox with size of maildir in 3gb,4gb for exemple and if i running the command doveadm quota get -u ACCOUNT_MY_USER The user with 2GB should be return 100% or some number bigger , but return 45% used only, If i force running one force-resync, the quota-get return the size correct showing more than 100% Someone can Help me ?

2 4

[whishlist] new option for 'doveadm purge'
by Michael Grimm 09 Dec '19

09 Dec '19

Hi, I do store mail in mdbox format of 150m in size (dovecot 2.3.9). Once in a while I do experience mdbox files of smaller size, even after applying 'doveadm purge' and previous expunges by the users. like: -rw------- 1 vmail dovecot 104854595 Feb 9 2019 /var/mail/.maildirs/userX/storage/m.22 -rw------- 1 vmail dovecot 29088478 Mar 8 2019 /var/mail/.maildirs/userX/storage/m.31 -rw------- 1 vmail dovecot 98210890 Mar 20 2019 /var/mail/.maildirs/userX/storage/m.39 (Currently the counter is at file number 129.) Well, I never experienced missing mail or alike, but these "holes" in filesize irritates me, and yes, it is more or less a cosmetic issue. Nevertheless, I do sometimes want to get rid of these "holes" by backing up all mail and re-injecting the backup into a vanilla account of that user. And I used this approach when I wanted to store all mail messages in larger mdbox files; again, rather a cosmetic issue. BUT that takes a very, very long time contrary to the speed of 'doveadm purge'. Unfortunately, that command starts somewhere with more recent mdbox files and never from scratch (oldest mdbox file). Whishlist: Would it be much of an effort to implement an option like: 'doveadm purge -f' and '-f' standing for 'force' or 'from scratch' or 'from the very first message found' or 'you name it'? Thanks in advance and thanks for Dovecot and with kind regards, Michael

2 2

bash script hook lda_mailbox_autocreate for generate mail-crypt user encrypted private key with user password
by uxqex4efpu＠elude.in 09 Dec '19

09 Dec '19

What it is way most best for causing bash script run (as root) of time mailbox created (lda_mailbox_autocreate)? I use dovecot 2.3.4.1 in Debian 10. And I use of mail-crypt-plugin https://doc.dovecot.org/configuration_manual/mail_crypt_plugin/ I setup mail-crypt for requiring user encrypted EC key (mail_crypt_require_encrypted_user_key = yes). I want for passphrase encrypt EC key using client plaintext password. There is credential no stored on server. But for user with use password too bad, I concatenate user plaintext password with random salt. And then string to SHA512() hash and use as decryption key (mail_crypt_private_password) for EC private key. For above I have plugin config > mail_plugins = $mail_plugins mail_crypt > plugin { > mail_crypt_curve = secp256k1 > mail_crypt_require_encrypted_user_key = yes > mail_crypt_save_version = 2 > } And for returning userdb_mail_crypt_private_password, I have sql query > password_query = SELECT username, password, \ > SHA2( CONCAT('%w',salt), 512 ) AS userdb_mail_crypt_private_password \ > FROM virtual_users WHERE username='%u'; But how I generate key of user automatically? Note for generating key of user, I need user password plaintext. I never save plaintext password of user of the server. Also user of note creates in PHP of web of the server. And for security I do not allow PHP exec shell (php.ini disabled_functions). Definitely not leaving PHP doveadm access! For solving subject to generate user key encrypted, I do imap of call of the service 'imap-postlogin' the service likes document "Post-login scripting' write https://doc.dovecot.org/admin_manual/post_login_scripting/ And 'imap-postlogin' execute my custom script with 'script-login' binary https://github.com/dovecot/core/blob/8606e1abb90a1c91357b84bf547a89564d0535… Here it is config for above > service imap { > executable = imap imap-postlogin > } > service imap-postlogin { > executable = script-login /usr/local/bin/generateKeys.sh > unix_listener imap-postlogin { > } > } And generateKeys.sh it is script simple for generating keys with sha256() hash product mysql. Variable of note ${MAIL_CRYPT_PRIVATE_PASSWORD} automatically put of 'userdb_mail_crypt_private_password' return of mysql field of query when documented https://doc.dovecot.org/admin_manual/post_login_scripting/running-surroundi… > Fields returned by userdb lookup with their keys uppercased > (e.g. if userdb returned home, it's stored in HOME). Here generatekeys.sh > #!/bin/bash > if [ `/usr/bin/doveadm mailbox cryptokey list -u "${USER}" -U > /dev/null | wc -l` -lt 2 ]; then > /usr/bin/doveadm -o "plugin/mail_crypt_private_password=${MAIL_CRYPT_PRIVATE_PASSWORD}" mailbox cryptokey generate -u "${USER}" -U > /dev/null > fi > exec "$@" This work! But I want more good. By why execute each login? Possible has generateKeys.sh execute in the times only of dovecot create mailbox (lda_mailbox_autocreate) instead?

2 4

Execute a script from dovecot when authentication fails
by nb 09 Dec '19

09 Dec '19

Hello, My name is Noury, and I’m new here. I’ve been using dovecot IMAP for years, but I want to do now some extra things. I want to call a script from within dovecot, to build a suspicious IP addresses list when authentication fails. I have tried the PostLoginScripting technic. It works fine but it doesn’t suit my needs. The script executes only after a successful login. I want to execute my script only when auth fails. If I can execute a script and check into it if auth failed, I would be nice too. A kind of « PreLoginScript" Is there a way to achieve this? I’m reading now auth.log file, but I would like to have a realtime processing. Thanks in advance. Noury

2 1

Re: How do I set all my mailboxes to "subscribed"
by Aki Tuomi 09 Dec '19

09 Dec '19

2 1

Shared namespace is empty after migration to new Dovecot installation
by Peter Reinhold 09 Dec '19

09 Dec '19

Hi all, I've used most of this weekend finalizing my migration from an old server running Dovecot 2.2.22 to a brand new installation running 2.3.8. In general, the migration was painless, everything just clicked, but checking up on the finer details post migration i've found out that user shared folders does not seem to work anymore, and I simply can't get it to work. The setups are more or less identical, biggest change is probably the addition of a Solr search index, and i've done very little changes in the configuration files. The acl_shared_dict file is being created and updated when I share a folder In the user thats sharing the folder, the dovecot-acl and dovecot-acl-list files are created and look the same. But, the user that should be reading the shared folder can not see it, the Shared namespace is simply empty, which it is not on the old installation, and namespace setup is identical across the two servers. (Except for the CaSiNg of the location of the index and indexpvt) Logging in and doing an IMAP command : A1 LIST "Shared/" "*" yields this on the old server. (I've replaced the sharing users e-mail to user(a)sharer.dk and the reading users to user(a)reader.dk) A1 LIST "Shared/" "*" * LIST (\HasNoChildren) "/" Shared/user(a)sharer.dk A1 OK List completed (0.000 + 0.000 secs). and this on the new A1 LIST "Shared/" "*" A1 OK List completed (0.006 + 0.000 + 0.005 secs). Log output from the new server below (i've only included the events happening during the LIST account) -- New, non-working log start -- Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=no location=maildir:/data/mail/%d/%n/maildir:INDEX=~/maildir/shared/%u:INDEXPVT:~/maildir/shared/%u shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= fts: Indexes disabled for namespace 'Shared/%u/' acl: initializing backend with data: vfile acl: acl username = user(a)reader.dk acl: owner = 0 acl vfile: Global ACLs disabled acl vfile: file /data/mail/reader.dk/user/maildir/dovecot-acl not found acl vfile: file /data/mail/reader.dk/user/maildir/.Junk/dovecot-acl not found acl vfile: file /data/mail/reader.dk/user/maildir/.Trash/dovecot-acl not found acl vfile: file /data/mail/reader.dk/user/maildir/.Sent/dovecot-acl not found auth-master: userdb lookup(user(a)sharer.dk): Started userdb lookup auth-master: conn unix:/var/run/dovecot/auth-userdb: Connecting auth-master: conn unix:/var/run/dovecot/auth-userdb (pid=1636,uid=0): Client connected (fd=16) auth-master: userdb lookup(user(a)sharer.dk): auth USER input: user(a)sharer.dk uid=120 gid=129 home=/data/mail/sharer.dk/user auth-master: userdb lookup(user(a)sharer.dk): Finished userdb lookup (username=user(a)sharer.dk uid=120 gid=129 home=/data/mail/sharer.dk/user) Namespace Shared/: Using permissions from : mode=0700 gid=default -- New, non-working log end -- and here from the old, working installation -- Old, working log start -- Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=no location=maildir:/data/mail/%d/%n/maildir:INDEX=~/Maildir/shared/%u:INDEXPVT=~/Maildir/shared/%u shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= acl: initializing backend with data: vfile acl: acl username = user(a)reader.dk acl: owner = 0 acl vfile: Global ACLs disabled auth input: user(a)sharer.dk uid=118 gid=126 home=/data/mail/sharer.dk/user namespace/default/inbox=yes maildir++: root=/data/mail/sharer.dk/user/maildir, index=/data/mail/sharer.dk/user/Maildir/shared/user(a)sharer.dk, indexpvt=/data/mail/sharer.dk/user/Maildir/shared/user(a)sharer.dk, control=, inbox=/data/mail/sharer.dk/user/maildir, alt= acl: initializing backend with data: vfile acl: acl username = user(a)sharer.dk acl: owner = 1 acl vfile: Global ACLs disabled maildir++: root=/data/mail/sharer.dk/user/maildir, index=/data/mail/reader.dk/user/Maildir/shared/user(a)sharer.dk, indexpvt=/data/mail/reader.dk/user/Maildir/shared/user(a)sharer.dk, control=, inbox=/data/mail/sharer.dk/user/maildir, alt= acl: initializing backend with data: vfile acl: acl username = user(a)reader.dk acl: owner = 0 acl vfile: Global ACLs disabled acl vfile: reading file /data/mail/sharer.dk/user/maildir/dovecot-acl acl: Mailbox not in dovecot-acl-list: Shared/user(a)sharer.dk/Junk acl: Mailbox not in dovecot-acl-list: Shared/user(a)sharer.dk/Trash acl: Mailbox not in dovecot-acl-list: Shared/user(a)sharer.dk/Sent acl: Mailbox not in dovecot-acl-list: Shared/user(a)sharer.dk/Drafts acl: Mailbox not in dovecot-acl-list: Shared/user(a)sharer.dk/Junk acl: Mailbox not in dovecot-acl-list: Shared/user(a)sharer.dk/Trash acl: Mailbox not in dovecot-acl-list: Shared/user(a)sharer.dk/Sent acl: Mailbox not in dovecot-acl-list: Shared/user(a)sharer.dk/Drafts -- Old, working log end -- The two logs are quite different, the new one seems to do user lookups via the auth socket, which the old one does not, and then just stops there. I'm not going to try and speculate more, I hope that someone here can see something from the logs, as I simply do not know how to fix this problem. -- Peter Reinhold

2 2