- dovecot - dovecot.org

TLS handshake issue
by John Oliver 18 Mar '16

18 Mar '16

dovecot-2.0.9 on CentOS 6.7 The system in question is not connected to the Internet, so I can't copy-and-paste. I have to type anything required :-( Brand-new out-of-the-box install with a really minimal dovecot.conf including: service imap-login { inet_listener imaps { address = 192.168.1.10 port = 143 ssl = yes } } ssl_cert=</etc/pki/tls/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_key =</etc/pki/tls/private/dovecot.pem That's very, very similar to an existing dovecot server on an old VM I need to replace. Certs are self-signed, I know that's a horrible thing to do, but right now we don't have any choice. I'm connecting with Apple Mail 8.2 running on OS X 10.10.5, another thing we have no choice about :-/ The Apple Mail just sits there stupidly. It's "Connection Doctor" just helpfully reports that it can't establish a connection. I can use 'openssl s_client -showcerts -connect mail:143' and see what I expect to see. The dovecot log with lots of verbosity enabled tells me: imap-login: Info: Disconnected (no auth attempts): rip=192.168.1.200, lip=192.168.1.10, TLS handshaking: Disconnected auth: Debug: auth client connected (pid=21006) imap-login: Warning: SSL: where=0x10, ret=1: before/accept initialization [192.168.1.200] imap-login: Warning: SSL: where=0x2001, ret=1: before/accept initialization [192.168.1.200] imap-login: Warning: SSL: where=0x2002, ret=1: SSLv2/v3 read client hello A [192.168.1.200] And that's it... those lines get repeated every minute that Mail is running. I'm not seeing anything in any logs that even hints at what it's unhappy about, or any way to increase verbosity any more. Any hints appreciated! -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * ***********************************************************************

4 5

Dovecot LDA with OpenSMTPD
by Eric Kom 18 Mar '16

18 Mar '16

Good day, Can any one help on how to get Dovecot LDA work with OpenSMTPD?

2 1

VS: Re: VS: Re: TLS handshake issue
by Aki Tuomi 18 Mar '16

18 Mar '16

Most applications would expect to see nonencrypted imap reply in 143 and would use starttls to engage ssl ---Aki TuomiDovecot oy-------- Alkuperäinen viesti --------Lähettäjä: John Oliver <joliver(a)john-oliver.net> Päivämäärä: 17.3.2016 21.45 (GMT+02:00) Saaja: dovecot(a)dovecot.org Aihe: Re: VS: Re: TLS handshake issue On Thu, Mar 17, 2016 at 08:38:55PM +0200, Aki Tuomi wrote: > openssl s_client -connect host:143 -starttls imap Why? 'openssl' works just fine, it shows me the certificate and the IMAP banner, and I can log in and list mail. -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * ***********************************************************************

1 0

Released Pigeonhole v0.4.13 for Dovecot v2.2.22.
by Stephan Bosch 18 Mar '16

18 Mar '16

Hello Dovecot users, Here is the final v0.4.13 release of Pigeonhole for Dovecot v2.2.22. Nothing changed since the RC. Changelog v0.4.13: * redirect action: Added the list-id header to the duplicate ID for mail loop prevention. This means that the message sent directly to the user and the message coming through the mailing list itself are treated as different messages by the loop detection of the redirect command, even though their Message-ID may be identical. * Changed the Sieve number type to uint64_t, which means that Sieve numbers can now technically range up to 2^64. Some other Sieve implementation allowed this, making this change necessary for successful migration. + Implemented the sieve_implicit_extensions setting. The extensions listed in this setting do not need to be enabled explicitly using the Sieve "require" command. This behavior directkly violates the standard, but can be necessary for compatibility with some existing implementations of Sieve. Do not use this setting unless you really need to! - redirect action: Made mail loop detection more robust by forcibly adding a Message-ID header if it is missing. - Prevent logging a useless "script not found" error message for LDAP scripts for which the entry exists but no attribute containing a script. This is not necessarily an error. - extprograms plugin: Changed the communication channel between parent and child process for a directly forked program from a socketpair to a double pipe. Linux does not support /dev/stdin, /dev/stdout and friends for sockets. For some shell program authors this may be confusing, so that is why it is changed. When using the script service, these device nodes are still not usable though. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.13.ta… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.13.ta… 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

Trouble getting vnd.dovecot.filter and filter visible/usable...
by Tolbert, Joshua P 17 Mar '16

17 Mar '16

Hello, I’m trying to make vnd.dovecot.filter available both globally and for users through sieve, but I haven’t had much luck getting things to work right. Sieve scripts won’t validate and vnd.dovecot.filter never shows up in the managesieve capability list. I’ve spent lots of time looking for where problems could be, but I’m out of ideas…So I’m asking you guys. In the protocol lmtp section, I’m defining mail_plugins = $mail_plugins sieve, however I’ve tried it without $mail_plugins too…No luck that way either. Any help/advice would be much appreciated. Thanks! Cheers, Josh

2 2

VS: Re: TLS handshake issue
by Aki Tuomi 17 Mar '16

17 Mar '16

openssl s_client -connect host:143 -starttls imap ---Aki TuomiDovecot oy-------- Alkuperäinen viesti --------Lähettäjä: John Oliver <joliver(a)john-oliver.net> Päivämäärä: 17.3.2016 20.11 (GMT+02:00) Saaja: dovecot(a)dovecot.org Aihe: Re: TLS handshake issue On Thu, Mar 17, 2016 at 08:30:32PM +0300, Andrey Fesenko wrote: > May be use -starttls imap or 993 port and more logs verbose_ssl=yes I am using verbose_ssl = yes Dovecot is currently working with SSL on 143, and I'm trying to not change current client config. As for '-starttls', in what context? -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * ***********************************************************************

2 1

Looking for way to monitor dsync, confirm it is or isn't running
by Rich Wales 17 Mar '16

17 Mar '16

I am syncing two Dovecot sites using the dsync function. I would like to be able to run some sort of periodic health check to confirm that dsync is (or is not) running properly between the two sites, and alert me if dsync is failing or lagging excessively. Does anyone know of a tool to do this? (If possible, something I can set up to run periodically in Nagios?) Thanks for any suggestions. Rich Wales richw(a)richw.org

2 3

Xi has a new home
by Stephan Bosch 17 Mar '16

17 Mar '16

Hi, The automatic package builder Xi has moved to system within the Dovecot infrastructure. This also means that the repositories are available at a new host name: xi.dovecot.fi. The old host name still works and is a CNAME pointing to the new venue. I expect the old domain to be active for years to come. So, there is no need to update your /etc/apt/sources.list right away. Still, it is a good idea to do so. I've updated the wiki accordingly. Regards, Stephan.

4 5

Re: spamc during dovecot-smtp delivery?
by madduck＠madduck.net 17 Mar '16

17 Mar '16

[cc'ing the list for posterity] also sprach Tolbert, Joshua P <jtolbert(a)illinois.edu> [2016-03-16 21:46 +0100]: > I’ve been working on a Postfix/Dovecot/sieve mail server migration > (from Sendmail/Dovecot/procmail) and ran in to a similar problem > to one you talked about a while ago on the dovecot mailing lists. > Did you ever find a good solution for running spamc as the > destination user in sieve? If you did, mind sharing? Thanks! I've never had a problem again since upgrading to Debian jessie, but I also think that the problem's solution was installing a NSS cache, because the deadlocks seemed to take place between Spamassassin and libnss-pgsql2. Transport from Postfix to Dovecot is lmtp:unix:private/dovecot-lmtp (no idea how to do that with Sendmail or why you'd want to use Sendmail) and then Dovecot's sieve is configured to run a filter using /etc/dovecot/sieve.before.d: require [ "vnd.dovecot.filter"]; filter "spamc" [ "--no-safe-fallback" ]; which is enabled in conf.d/90-sieve.conf with sieve_before = /etc/dovecot/sieve.before.d sieve_global_extensions = +vnd.dovecot.filter sieve_plugins = sieve_extprograms and in conf.d/90-sieve-extprograms.conf sieve_filter_bin_dir = /etc/dovecot/sieve-filter and then I made a simple symlink from /etc/dovecot/sieve-filter → /usr/bin/spamc Spamassassin starts with --create-prefs --helper-home-dir --allow-tell and the final step is to integrate the mail user database (vmm in my case) with libnss to provide spamassassin with a way to identify home directories. I use libnss-pgsql2. The /etc/nss-pgsql.conf file I use is available here: http://bugs.debian.org/818465 A successful delivery then looks like this: postfix/smtpd[29778]: connect from mail1.smtp.mailserver4.de[62.216.179.241] postfix/smtpd[29778]: 6D2F74024E: client=mail1.smtp.mailserver4.de[62.216.179.241] postfix/cleanup[32593]: 6D2F74024E: message-id=<xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@xxxxxxxxxxxxxxxxxxxxx> postfix/smtpd[29778]: disconnect from mail1.smtp.mailserver4.de[62.216.179.241] dovecot: lmtp(3570): Connect from local spamd[2140]: spamd: connection from localhost [::1]:57032 to port 783, fd 6 spamd[2140]: spamd: setuid to xxxxxxx%yyyyyyyyyy.zz succeeded spamd[2140]: spamd: processing message <xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@xxxxxxxxxxxxxxxxxxxxx> for xxxxxxx%yyyyyyyy.zz:70032 spamd[2140]: spamd: clean message (-1.9/5.0) for xxxxxxx%yyyyyyyy.zz:70032 in 3.0 seconds, 10222 bytes. spamd[2140]: spamd: result: . -1 - BAYES_00,DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE scantime=3.0,size=10222,user=xxxxxxx%yyyyyyyy.zz,uid=70032,required_score=5.0,rhost=localhost,raddr=::1,rport=57032,mid=<xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@xxxxxxxxxxxxxxxxxxxxx>,bayes=0.000000,autolearn=ham autolearn_force=no dovecot: lmtp(3570, xxxxxxx(a)yyyyyyyy.zz) copy from (file): box=INBOX, uid=30613, msgid=<xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@xxxxxxxxxxxxxxxxxxxxx>, size=10945 dovecot: lmtp(3570, xxxxxxx(a)yyyyyyyy.zz) QLZ6IoJ/6lbyDQAARsnb6w: sieve: msgid=<xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@xxxxxxxxxxxxxxxxxxxxx>: stored mail into mailbox 'INBOX' postfix/lmtp[3569]: 6D2F74024E: to=<xxxxxxx(a)yyyyyyyy.zz>, orig_to=<aaaaaa(a)bbbbbbb.zz>, relay=ambassador.madduck.net[private/dovecot-lmtp], delay=5, delays=2/0.02/0.01/3, dsn=2.0.0, status=sent (250 2.0.0 <xxxxxxx(a)yyyyyyyy.zz> QLZ6IoJ/6lbyDQAARsnb6w Saved) dovecot: lmtp(3570): Disconnect from local: Successful quit Hope this helps… -- @martinkrafft | http://madduck.net/ | http://two.sentenc.es/ "the public is wonderfully tolerant. it forgives everything except genius." -- oscar wilde spamtraps: madduck.bogus(a)madduck.net

1 0

subscribe users mailbox with non-valid mutf7 chars
by Matthias Lay 16 Mar '16

16 Mar '16

Hi all, I got a question if its possible to subscribe a mailbox from another user, who contains non mutf7 valid chars in his mailbox path. I have a private namespace which can subscribe to mailboxes of a shared namespace with public/ prefix in this example username in private namespace is johnd public username is "a & p products group" when I try the subscription I get this one: ******************************************** # doveadm mailbox subscribe -u johnd "public/a & p products group/INBOX" doveadm(johnd): Error: Can't public/a & p products group/INBOX mailbox subscribe to: Invalid mailbox name 'public/a & p products group/INBOX': Missing namespace prefix 'public/a &- p products group/' ******************************************** is there a way to work around this? (except for not to use usernames like this) greetz matze

1 1