March 2018 - dovecot - dovecot.org

dovecot caching decisions
by Sivathmican Sivakumaran 21 Mar '18

21 Mar '18

Hello guys, Should the following configuration: mail_cache_fields = flags,imap.body,imap.bodystructure mail_always_cache_fields = imap.body,imap.bodystructure have an effect on the following command? doveadm index -u bob INBOX It seems to have no effect for some reason. Regards, Siva

1 0

pylori error in dovecot log
by ＠lbutlr 21 Mar '18

21 Mar '18

I am getting the following in my /var/log/dovecot: Error: sieve: Execution of script /usr/lib/dovecot/sieve/report-spam.sieve failed Error: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/Razor.pm in @INC (you may need to install the Mail::SpamAssassin::Plugin::Razor module) (@INC contains: /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/site_perl/mach/5.24 /usr/local/lib/perl5/5.24/mach /usr/local/lib/perl5/5.24) at (eval 44) line 1. Error: program `/usr/lib/dovecot/sieve/sa-learn-spam.sh' was forcibly terminated with signal 15 Error: sieve: pipe action: failed to pipe message to program `sa-learn-spam.sh': refer to server log for more information. [2018-03-19 12:52:51] Info: sieve: left message in mailbox 'Junk'

2 4

Compiling from sources and security contexts (dovecot_selinux)
by TraxOnDaRocks 20 Mar '18

20 Mar '18

Hi, installation by prebuilt binaries creates security contexts on each file (as shown here https://linux.die.net/man/8/dovecot_selinux) so that dovecot integrates perfectly in SELinux. I've compiled instead from sources (as described here https://wiki2.dovecot.org/CompilingSource) and i'd like to know how create same security contexts of prebuilt binaries to have an identical behaviour in SELinux. Thank you

1 0

Permissions on /var/log/dovecot
by ＠lbutlr 20 Mar '18

20 Mar '18

/var/log/dovecot exists and has a lot of logging in it, but I get errors (in mail.log) on an always_bcc action in postfix: mail postfix/pipe[13015]: 401cvS0R8BzbSkL: to=<backup+073.kremels-kreme(a)doamin.tld>, relay=dovecot, delay=398058, delays=398045/13/0/0.04, dsn=4.3.0, status=deferred (temporary failure. Command output: Can't open log file /var/log/dovecot: Permission denied ) What should the permissions on /var/log/dovecot be? (they are 640 root:wheel on FreeBSD, identical to mail.log)

5 10

Fwd: Everything works except sending mail
by Armin Tangelder 20 Mar '18

20 Mar '18

Hi people, Version of my beloved Dovecot installation: 2.2.27 (c0f36b0) I moved from a OS X server to a Linux (Ubuntu) Headless server. All fun and good to play around with. Love almost everything. In the combination with Postfix and Dovecot I’m stuck to despair into oblivion. Everything works except I cannot send mail from my (OS X) Outlook client I keep getting: Connection to the server failed or was dropped. Error Code -3253 Nothing More and nothing less. O do not get any other error in a logfile or anything. And I followed almost every installation manual I found. Postfix I can send and receive through telnet. But I just can’t get this to work… The mail doesn’t even reach Postfix queue as I cannot connect to send. I do have a awesome connection receiving my mail though ☺ Anyway: dovecot -n gives this (and I probably don’t see it anymore as I’ve been at this for several days now) # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.13.0-37-generic x86_64 Ubuntu 17.10 auth_mechanisms = plain login auth_realms = formule1.demon.nl login_greeting = Dovecot ready. mail_location = maildir:~/Maildir mail_max_userip_connections = 50 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 { driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl_cert = </etc/ssl/certs/server.crt ssl_key = # hidden, use -P to show it userdb { driver = passwd } Anything useful I would love to see. Any information needed. THNKS… Armin -- Very funny Scotty, now beam down my clothes…

3 2

Accentuated email addresses stored in LDAP
by André Rodier 20 Mar '18

20 Mar '18

Hello everyone, I have successfully set up Dovecot with an LDAP backend, and everything works like a charm, except one small use case. I know it is possible, so if anyone knows a solution, thank you! Basically, I just want to send an email to one of my email address, which contains an accent, i.e. andré(a)homebox.space.... Every other alias works, but not those with accents. They are correctly stored in the LDAP database, using base64. I suspect I would need to use base64 again before the lookup, but I don't know how to do and if it is even possible. My filter is set up as this: filter=(&(objectClass=posixAccount)(|(uid=%n)(mail=%u)(mailLocalAddress=%u))) It works perfectly for any email without accent. Thanks for your help. > Mar 18 22:14:28 homebox dovecot[24636]: auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth > Mar 18 22:14:28 homebox dovecot[24636]: auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth > Mar 18 22:14:28 homebox dovecot[24636]: auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libauthdb_ldap.so > Mar 18 22:14:28 homebox dovecot[24636]: auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat > Mar 18 22:14:28 homebox dovecot[24636]: auth: Debug: LDAP initialization took 7 msecs > Mar 18 22:14:28 homebox dovecot[24636]: auth: Debug: auth client connected (pid=0) > Mar 18 22:14:28 homebox dovecot[24636]: quota-status(andré(a)homebox.space): Debug: Loading modules from directory: /usr/lib/dovecot/modules Mar 18 22:14:28 homebox dovecot[24636]: quota-status(andré(a)homebox.space): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so > Mar 18 22:14:28 homebox dovecot[24636]: auth: Debug: master in: USER 1 andré(a)homebox.space service=quota-status > Mar 18 22:14:28 homebox dovecot[24636]: auth: Debug: ldap(andré(a)homebox.space): user search: base=dc=homebox,dc=space scope=subtree filter=(&(objectClass=posixAccount)(|(uid=andré)(mailLocalAddress=andré(a)homebox.space))) fields=homeDirectory,uidNumber,gidNumber,mail > Mar 18 22:14:28 homebox dovecot[24636]: auth: Debug: ldap(andré(a)homebox.space): no fields returned by the server > Mar 18 22:14:28 homebox dovecot[24636]: auth: ldap(andré(a)homebox.space): unknown user > Mar 18 22:14:28 homebox dovecot[24636]: auth: Debug: userdb out: NOTFOUND 1 > Mar 18 22:14:28 homebox dovecot[24636]: quota-status(andré(a)homebox.space): Debug: auth USER input: > Mar 18 22:14:28 homebox postfix/smtpd[24734]: NOQUEUE: reject: RCPT from smtpfr.rodier.me[164.132.53.161]: 554 5.7.1 <andré(a)homebox.space>: Recipient address rejected: Unknown user; from=<root(a)smtpuk.rodier.me> to=<andré(a)homebox.space> pro > to=ESMTP helo=<smtpuk.rodier.me> > Mar 18 22:14:28 homebox postfix/smtpd[24734]: disconnect from smtpfr.rodier.me[164.132.53.161] ehlo=1 mail=1 rcpt=0/1 data=0/1 rset=1 quit=1 commands=4/6

5 8

Strange "IMAP connection broken (server response)" errors
by Jozsef Kadlecsik 20 Mar '18

20 Mar '18

Hello, We upgraded one of our dovecot servers to debian stretch with dovecot 2.2.27 and since then one of our users has been experiencing random IMAP failures. We enabled raw logging at the server side and it shows normal IMAP commands/responses: 1507292522.222427 * 6 FETCH (FLAGS () BODYSTRUCTURE ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 4645 112 NIL NIL NIL NIL)) 1507292522.222653 00000011 OK Fetch completed (0.006 + 0.000 secs). On the client side the user runs alpine and the corresponding debug lines: IMAP DEBUG 14:22:02.216167: 00000011 FETCH 6 (BODYSTRUCTURE FLAGS) 14:22:02.217396 IMAP 14:22:02 10/6 mm_notify bye: {[127.0.0.1]:1555/imap/user="ha4aa"}INBOX: [CLOSED] IMAP connection broken (server response) 14:22:02.217471 IMAP 14:22:02 10/6 mm_log error: [CLOSED] IMAP connection broken (server response) The "[127.0.0.1]:1555/imap/user="ha4aa" part in the log comes from an socat inserted between the client and the server to check independetly the imap session. According to socat, the server response didn't reach the client!: 00000010 OK Fetch completed (0.005 + 0.000 secs).\r > 2017/10/06 14:22:02.216299 length=40 from=845 to=884 00000011 FETCH 6 (BODYSTRUCTURE FLAGS)\r and here ends the socat log, the server response didn't reach the client. The same alpine package is used against older dovecot servers from debian jessie and works flawlessly. The server and client are both KVM guests and there's no any content filtering software between them. There's no corresponding error in the dovecot log file and dovecot didn't regard the connection broken and detected client close: ... Oct 6 14:19:44 mail2 dovecot: imap(ha4aa): Debug: Mailbox INBOX: Opened mail UID=55244 because: MIME part Oct 6 14:22:02 mail2 dovecot: imap(ha4aa): Connection closed in=797 out=73151 We are out of the ideas what can be the reason for the random lost server responses. Any help is appreciated! Best regards, Jozsef -- E-mail : kadlecsik.jozsef(a)wigner.mta.hu PGP key: http://www.kfki.hu/~kadlec/pgp_public_key.txt Address: Wigner Research Centre for Physics, Hungarian Academy of Sciences H-1525 Budapest 114, POB. 49, Hungary

3 3

Released Pigeonhole v0.4.23 for Dovecot v2.2.35.
by Stephan Bosch 20 Mar '18

20 Mar '18

Hello Dovecot users, Here is a new Pigeonhole release that goes with the new Dovecot v2.2.35 release. This release is not strictly necessary, as previous versions should be usable as well. This release only contains bug fixes. However, considering the rather nasty editheader bug that emerged in the previous release, upgrade is recommended. Changelog v0.4.23: - editheader extension: Corrected the stream position calculations performed while making the modified message available as a stream. Pigeonhole Sieve crashed in LMTP with an assertion panic when the Sieve editheader extension was used before the message was redirected. Experiments indicate that the problem occurred only with LMTP and that LDA is not affected. - fileinto extension: Fix assert panic occurring when fileinto is used without being listed in the require line, while the copy extension is listed there. This is a very old bug. - imapsieve plugin: Do not log an error for messages that disappear concurrently while applying Sieve scripts. This is a further improvement on the imapsieve fix in the previous release (which fixed a panic). This event is now logged as a debug message. The release is available as follows: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.23.t… https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.23.t… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Fts solr and https
by Alex 19 Mar '18

19 Mar '18

Hi, Dovecot 2.2.32-34 FreeBSD 10.4 Solr 7.2.1(Centos 6) When I try to use https to connect to solr, I get error when a self-signed certificate: Mar 3 05:15:47 server dovecot: indexer-worker(email(a)domain.com): Received invalid SSL certificate: self signed certificate: /C=Country/ ST=State/L=Location/O=Organization/OU=Organizational Unit/CN=solr.domain.com Mar 3 05:15:47 server dovecot: indexer-worker(email(a)domain.com): Received invalid SSL certificate: self signed certificate: /C=Country/ ST=State/L=Location/O=Organization/OU=Organizational Unit/CN=solr.domain.com Mar 3 05:15:47 server dovecot: indexer-worker(email(a)domain.com): Error: fts_solr: Indexing failed: SSL handshaking with 1.1.1.1: 8983 failed: read(SSL 1.1.1.1:8983) failed: Received invalid SSL certificate: self signed certificate: /C=Country/ST=State/L=L ocation/O=Organization/OU=Organizational Unit/CN=solr.domain.com (2 attempts in 0.043 secs) Mar 3 05:15:47 server dovecot: indexer-worker(email(a)domain.com): Received invalid SSL certificate: self signed certificate: /C=Country/ ST=State/L=Location/O=Organization/OU=Organizational Unit/CN=solr.domain.com Mar 3 05:15:47 server dovecot: indexer-worker(email(a)domain.com): Received invalid SSL certificate: self signed certificate: /C=Country/ ST=State/L=Location/O=Organization/OU=Organizational Unit/CN=solr.domain.com Mar 3 05:15:47 server dovecot: indexer-worker(email(a)domain.com): Error: fts_solr: Indexing failed: SSL handshaking with 1.1.1.1: 8983 failed: read(SSL 1.1.1.1:8983) failed: Received invalid SSL certificate: self signed certificate: /C=Country/ST=State/L=L ocation/O=Organization/OU=Organizational Unit/CN=solr.domain.com (2 attempts in 0.430 secs) Mar 3 05:15:47 server dovecot: indexer-worker(email(a)domain.com): Error: Mailbox INBOX: Transaction commit failed: FTS transaction commi t failed: backend deinit (attempted to index 1 messages (UIDs 799975..799975)) or error when letsencrypt: Mar 3 01:26:31 server dovecot: indexer-worker(email(a)domain.com): Received invalid SSL certificate: unable to get local issuer certifi cate: /C=US/O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 Mar 3 01:26:31 server dovecot: indexer-worker(email(a)domain.com): Received invalid SSL certificate: unable to get local issuer certifi cate: /C=US/O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 Mar 3 01:26:31 server dovecot: indexer-worker(email(a)domain.com): Error: fts_solr: Indexing failed: SSL handshaking with 1.1.1.1 3:8983 failed: read(SSL 1.1.1.1:8983) failed: Received invalid SSL certificate: unable to get local issuer certificate: /C=US/ O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 (2 attempts in 0.085 secs) Mar 3 01:26:31 server dovecot: indexer-worker(email(a)domain.com): Received invalid SSL certificate: unable to get local issuer certifi cate: /C=US/O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 Mar 3 01:26:31 server dovecot: indexer-worker(email(a)domain.com): Received invalid SSL certificate: unable to get local issuer certifi cate: /C=US/O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 Mar 3 01:26:31 server dovecot: indexer-worker(email(a)domain.com): Error: fts_solr: Indexing failed: SSL handshaking with 1.1.1.1 3:8983 failed: read(SSL 1.1.1.1:8983) failed: Received invalid SSL certificate: unable to get local issuer certificate: /C=US/ O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 (2 attempts in 0.112 secs) Mar 3 01:26:31 server dovecot: indexer-worker(email(a)domain.com): Error: Mailbox INBOX: Transaction commit failed: FTS transaction com mit failed: backend deinit (attempted to index 1 messages (UIDs 104770..104770)) 90-plugins.conf: fts_autoindex=yes fts = solr fts_solr = url=https://login:pass@solr.domain.com:8983/solr/dovecot/ break-imap-search debug curl and other software connect to solr without errors in both cases. Does dovecot have option to disable certificate validation (may be ssl_verify = false etc.) ? Thanks.

2 2

Controlling dovecot caching decisions
by Sivathmican Sivakumaran 19 Mar '18

19 Mar '18

Hello, It looks like the "mail_always_cache_fields" and "mail_never_cache_fields" can be used to control dovecot's caching decisions. I cannot seem to find any documentation regarding how these fields should be used. What are acceptable values for these fields? I am quite new to this so any help would be much appreciated. Regards, Siva

2 2