September 2016 - dovecot

Setting hostdomain
by Arie Peterson 25 Sep '16

25 Sep '16

Hi all, Preparing for a replication setup, I read (at the bottom of <http://wiki2.dovecot.org/Replication>) that `dovecot --hostdomain` should give a different output on the two servers. This is not the case for me: both give "localhost". I'm trying to change my configuration to set the hostdomain to another value, but I can't find how to do this. I tried: • setting the environment variable DOVECOT_HOSTDOMAIN=mydomain in /etc/default/dovecot (which is read by the init script); • adding the line import_environment = TZ DOVECOT_HOSTDOMAIN=mydomain to dovecot.conf; • the combination of both of the above. However, after restarting dovecot none of these changes seem to have any effect: `dovecot --hostdomain` still returns "localhost". This is with dovecot version 2.2.13. How should one change this setting? Thanks, Arie

2 2

fail to compile with openssl-1.1.x
by A. Schulze 25 Sep '16

25 Sep '16

Hi again, now I get compile errors. Is openssl-1.1.xy supported? iostream-openssl.c: In function 'openssl_iostream_verify_client_cert': iostream-openssl.c:118:37: error: dereferencing pointer to incomplete type subject = X509_get_subject_name(ctx->current_cert); ^ iostream-openssl.c:127:37: error: dereferencing pointer to incomplete type X509_verify_cert_error_string(ctx->error), certname)); Andreas ^

2 1

configure fail if libssl is named libssl-opt
by A. Schulze 25 Sep '16

25 Sep '16

Hello, I try to build dovecot with my own version of openssl. It's compiled in a way the libraries can coexist without symbol conflict with the real OpenSSL in /usr: They are named libssl-opt and libcrypto-opt. Now configure fail to find my libssl-opt: CFLAGS="..." CXXFLAGS="..." CPPFLAGS="..." LDFLAGS="..." SSL_LIBS='-lssl-opt -lcrypto-opt' ./configure ... --with-ssl=openssl ... checking for SSL_read in -lssl... no configure: error: Can't build with OpenSSL: libssl not found Is there an other way to tell configure the ssl libraries have other names? Andreas

1 1

Proxy IMAP/POP
by Luis Miguel Flores dos Santos 25 Sep '16

25 Sep '16

Hello, I'm try configure dovecot to proxy imap and pop but I can't, follow my configurations: dovecot version = 2.2.10 My configuration: dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.18.35 x86_64 CentOS Linux release 7.2.1511 (Core) auth_mechanisms = plain login auth_username_format = %n disable_plaintext_auth = no mail_location = maildir:~/Maildir mbox_write_locks = fcntl 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 } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } grep -v '^ *$#.*$\?$' dovecot-sql.conf driver = mysql connect = "host=127.0.0.1 dbname=mail user=root password=PASS" password_query = SELECT NULL AS password, 'Y' as nopassword, host, destuser, 'Y' AS proxy FROM proxy WHERE user = '%u' /var/log/maillog: RHDOVECOT dovecot: auth: Fatal: Unknown database driver 'mysql' **OBS: I followed this wiki: http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy and installed dovecot-mysql.x86_64, My server is a CentOS Linux release 7.2.1511 (Core) Anyone can help me? Thanks. -------- Atenciosamente, Luis Miguel

2 1

dovecot-2.2.18 / net_listen_unix(...) failed: Value too large for defined data type
by Christophe Bricout 25 Sep '16

25 Sep '16

Dear All, SUMMARY: Dovecot shows an issue when "localstatedir" path is too long The issue exists also with dovecot-2.2.25 CONFIGURATION: The configure options are: ./configure --prefix=${TARGET_DIR} \ --sysconfdir=${TARGET_DIR}/cfg \ --localstatedir=${TARGET_DIR}/var \ --with-ssl=openssl \ --with-sqlite \ --disable-shared RESULTS: When executing dovecot (as root), the followin message appears: Error: service(dict): net_listen_unix(/<user>/localbin/minnowboard-turbot-applications/1.0/linux/x86_64-linux/localbin/dovecot/2.2.18/linux/x86_64-linux/var/run/dovecot/dict) failed: Value too large for defined data type Error: service(config): net_listen_unix(<user>/localbin/minnowboard-turbot-applications/1.0/linux/x86_64-linux/localbin/dovecot/2.2.18/linux/x86_64-linux/var/run/dovecot/config) failed: Value too large for defined data type --- WORKAROUND: The problem is solved by defining shorten localstatedir or using base_dir = /var/run/dovecot. It seems the path lengh causing a such issue. Path Lengh > 127 Available for additional experiments Best Regards

2 1

Re:Self-Signed Certificate issue
by dovecot＠outputservices.com 23 Sep '16

23 Sep '16

Try this: Create a directory and do the following in that directory. Create the file openssl.cnf with the following information: [ req ] default_md = sha2 distinguished_name = req_distinguished_name [ req_distinguished_name ] countryName = US localityName = Boulder organizationName = Your orginizations name here organizationalUnitName = IT Department emailAddress = some email address at your company commonName = "Just a simple statement about the company" [ certauth ] subjectKeyIdentifier = hash authorityKeyIdentifier = keyid:always,issuer:always basicConstraints = CA:true [ client ] basicConstraints = critical,CA:FALSE keyUsage = digitalSignature, keyEncipherment, dataEncipherment extendedKeyUsage = clientAuth Just change the things you need to for you. Then issue the following command. openssl req -config ./openssl.cnf -newkey rsa:2048 -nodes -keyform PEM -keyout dovecot.key -x509 - days 365 -extensions certauth -outform PEM -out dovecot.pem -subj "/C=US/postalCode=00000/ST=state/L=city/streetAddress=some street/O=company name/OU=IT Department/CN=dovecort cert/emailAddress=email(a)yourcompany.com" Just change the C, O, OU, etc for your needs. Then verify the contents via: openssl x509 -noout -in dovecot.pem -subject openssl x509 -noout -in dovecot.pem -issuer openssl x509 -noout -in dovecot.pem -enddate openssl x509 -noout -in dovecot.pem -text This will show what is in the certificate. Now copy the pem & key files to where you want them. Restart dovecot. You may have to change the configuration to use the names just created. Dave Ryan On 09/23/16 11:07, Darryl Baker wrote: > My apologies if this is a repeat but my search of the archive did not turn > it up in the recent past. If this has been covered just point me at the > previous thread, please. > > I am running a small email site which I am moving from uw-imapd and Solaris > to Ubuntu and Dovecot imaps and pop3s. I am trying to use a self-signed > certificate for this site. I am using Thunderbird as the test client. I've > tried both the pre-built snakeoil certificate and building a special one > for dovecot. In /var/log/mail.err I keep getting what I am interpreting as > a missing CA cert. The message is: > > dovecot: imap-login: Error: SSL: Stacked error: error:14094418:SSL > routines:ssl3_read_bytes:tlsv1 alert unknown ca: SSL alert number 48 > > > The certificate was created by: > > openssl req -new -x509 -days 365 -nodes -out /etc/ssl/certs/dovecot.pem > -keyout /etc/ssl/private/dovecot.pem > > > The Dovecot version is 2.2.22 (fe789d2) The Ubuntu version is 16.04 LTS > current patches. > > > *Darryl Baker* > >

1 0

Director keeping IMAP connections alive
by Webert de Souza Lima 23 Sep '16

23 Sep '16

Hello, I have a 2 director - 2 dovecot set up in a cluster. >From time to time I notice high usage of RAM by dovecot process, and analyzing with doveadm who, I see many users with dozens, even hundreds of PIDs. Inspecting those PIDs I see each one of them is an IMAP connection, coming from either director process, and ESTABILISHED. A deeper analysis shows me that there ltos of connections from the same users to BOTH dovecot instances, but as I am using director, this shouldn't happen, right? Ok. The thing is, one of the dovecot instances have only old connections (like 3 days old) and the other dovecot have some old and some newer connections. So, director is redirecting recent connections to the right dovecot, as expected, but it is keeping many of old and unused connections open, consuming resources. output of doveconf -n from dovecot: http://pastebin.com/trMEjeAs output of doveconf -n from director: http://pastebin.com/EUpHYMKY Thanks.

1 1

Broken auth-* sockets.
by ygrishin＠pyramidheadgroup.ca 23 Sep '16

23 Sep '16

Hello. I am migrating my servers to Ubuntu and have been having an issue with Dovecot authenticator service. Exim is set up to use dovecot-auth, anticipating the question whether exim binary was compiled with support of Dovecot authenticator, it was: --- # exim -bV Exim version 4.86_2 #1 built 05-Apr-2016 12:21:41 Copyright (c) University of Cambridge, 1995 - 2015 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2015 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_messages Content_Scanning DKIM Old_Demime DNSSEC PRDR OCSP Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa tls Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /etc/exim4/exim4.conf --- The problem is sockets Dovecot creates are somehow broken. Exim reports something like: --- 2016-09-21 14:45:26 dovecot_plain authenticator failed for *** ([***]) [***]: 435 Unable to authenticate at present: authentication socket connection error 2016-09-21 14:45:26 dovecot_login authenticator failed for *** ([***]) [***]: 435 Unable to authenticate at present: authentication socket connection error --- and I initially thought it was wrong permissions for the socket, triple checked and they are 100% right. More than that, I temporarily chmodded it "rw" for the world as follows: --- # ls -l /var/dovecot/auth-* srw-rw-rw- 1 Debian-exim root 0 Aug 17 21:20 /var/dovecot/auth-client srw------- 1 dovecot root 0 Aug 17 21:20 /var/dovecot/auth-login srw-rw-rw- 1 Debian-exim root 0 Aug 17 21:20 /var/dovecot/auth-master -rw------- 1 root root 32 Aug 15 19:35 /var/dovecot/auth-token-secret.dat srw-rw-rw- 1 dovecot root 0 Aug 17 21:20 /var/dovecot/auth-userdb srw------- 1 dovecot root 0 Aug 17 21:20 /var/dovecot/auth-worker --- and Exim reports the same problem. What makes me think that it's Dovecot's and not Exim's problem? The fact that the socket is really broken, on the server where it's not working: --- # socat - UNIX-CONNECT:/var/dovecot/auth-client 2016/09/22 17:58:27 socat[15192] E connect(5, AF=1 "/var/dovecot/auth-client", 26): Connection refused --- on the server where it is working (version 2.2.13 is installed there), precisely same command: --- # socat - UNIX-CONNECT:/var/dovecot/auth-client VERSION 1 1 MECH PLAIN plaintext MECH LOGIN plaintext MECH CRAM-MD5 dictionary active MECH DIGEST-MD5 dictionary active mutual-auth MECH APOP private dictionary active SPID 535 CUID 880 COOKIE 0311e84ed191fb63334819b1fc3bf2e3 DONE --- with a different result!!! The system: --- uname -a Linux *** 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 2016 i686 i686 i686 GNU/Linux --- Doveconf: --- # dovecot -n # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-38-generic i686 Ubuntu 16.04.1 LTS ext3 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 digest-md5 apop debug_log_path = /var/log/dovecot-debug.log default_internal_user = dovenull disable_plaintext_auth = no first_valid_uid = 114 log_path = /var/log/dovecot.log login_greeting = IMAP/POP3 server is ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_location = maildir:/var/mail/exim/%d/%n mail_log_prefix = "%Us(%u): " 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 } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service auth { unix_listener auth-client { mode = 0660 user = Debian-exim } unix_listener auth-master { mode = 0600 user = Debian-exim } user = root } service imap-login { chroot = login client_limit = 8 inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 10143 } process_limit = 8 process_min_avail = 5 service_count = 1 user = dovenull vsz_limit = 64 M } service imap { drop_priv_before_exec = yes process_limit = 64 vsz_limit = 2 G } service pop3-login { chroot = login client_limit = 8 inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 10110 } process_limit = 8 process_min_avail = 5 service_count = 1 user = dovenull vsz_limit = 64 M } service pop3 { drop_priv_before_exec = yes process_limit = 64 vsz_limit = 2 G } ssl = no ssl_cert = </etc/dovecot/ssl/server.crt ssl_cipher_list = ALL:!LOW:!SSLv2 ssl_key = </etc/dovecot/ssl/server.key userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol lda { auth_socket_path = /var/dovecot/auth-master info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log postmaster_address = postmaster@*** } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } --- Sounds like a broken Dovecot install, doesn't it? Looks like not the case: --- # apt-get check Reading package lists... Done Building dependency tree Reading state information... Done --- What else to check?

2 2

Logging of custom mail headers
by Francesco Fiore 22 Sep '16

22 Sep '16

Hi, I need to configure Dovecot to log some custom mail headers. I red the documentation of the mail_log plugin but I didn't found which field I've to use as value for mail_log_fields parameter. So, I red the plugin code but in mail-log-plugin.c there're defined only "from" and "subject" fields that match some email header. I found three alternatives: 1. use the mail_filter plugin (spawning a new process, ecc.) 2. coding a new plugin using the notify plugin 3. propose a patch to the mail_log plugin that use a new configuration parameter (es. mail_log_headers) and log the specified mail headers Which is the better solution for you? Thanks in advance Francesco

1 1

Sieve vacation won't send second reply after timeout interval.
by David Williams 21 Sep '16

21 Sep '16

Hi I solved this by updating to Dovecot 2.2.24 David

1 0