March 2016 - dovecot - dovecot.org

Re: Setting up public mailboxes - user not found
by Marti Markov 20 Mar '16

20 Mar '16

Hey, I actually went with the method suggested by Steffen Kaiser of creating a separate userdb because I use LDAP and I have an OU which contains all the public mailboxes and was just easier. I setup the userdb like so: userdb { args = /etc/dovecot/dovecot-ldap-shared_mailboxes.conf.ext driver = ldap override_fields = mail=maildir:/home/vmail/Public/.%n } Now when I send an email to office3(a)xxx.com I don’t get any errors and it delivers the message to the office3(a)xxx.com: root@mail:~# ls /home/vmail/Public/.office3/new/ 1458427035.M781836P21781.mail.xxx.com,S=2571,W=2630 1458427705.M750112P23338.mail.xxx.com,S=2501,W=2559 But from any mail client I try I don’t seem to be able to list anything in the Public directory. Am I missing something in the configuration? Here is the public namespace configuration: namespace { list = yes location = maildir:/home/vmail/Public:INDEXPVT=~/Maildir/Public prefix = Public/ separator = / subscriptions = yes type = public } > On 17 Mar 2016, at 08:35, Burckhard Schmidt <bschmidt(a)cms.hu-berlin.de> wrote: > > hello Marti, > > Am 17.03.2016 um 06:18 schrieb Marti Markov: >> First of all thanks for the reply Burckhard. >> When you say: >>> You can use a "normal" user who has a sieve script: > > Normal user that's an account with one or more email aliasses. > So this "user" can receive emails like any other user. This I called "normal" user. But this ist not of interest in our case. > So you don't get an "user not found". > > Next you will add an appropriate email alias to the account if necessary (our accounts are cryptic). > > Now you have an account/user and you can write a sieve script for that user to deliver all emails into one public folder or into different folders. Public subfolders are possible too, if you like or are able to distinguish incomming emails. > > In your case it is not necessary to have an user/account "office3". This name you would only use in that sieve script with "fileinto". > > Regards! > > Burckhard > >> what would that user be in my case? office3? Because I don’t really see how it will solve the problem of getting the error 550 user not found when making the LDAP search. >> >>> On 10 Mar 2016, at 08:50, Burckhard Schmidt <bschmidt(a)cms.hu-berlin.de> wrote: >>> >>> Am 09.03.2016 um 20:02 schrieb Marti Markov: >>>> Hi all, >>>> >>>> This is the first time I use the dovecot mail list so I’m sorry if I forget something. >>>> >>>> My problem is that for some reason I can get public mailboxes to work. I have setup the directory Public, the folders and the cur,tmp and new folder in them: >>>> >>>> Public >>>> | >>>> |- .office3 >>>> | >>>> |- cur >>>> |- tmp >>>> |- new >>>> |- dovecot-acl >>>> >>>> >>>> Here is my dovecot conf: >>>> >>> >>>> namespace { >>>> list = yes >>>> location = maildir:/home/vmail/xxx.com/Public:INDEXPVT=~/Maildir/Public >>>> prefix = Public/ >>>> separator = / >>>> subscriptions = yes >>>> type = public >>>> } >>> >>> You can use a "normal" user who has a sieve script: >>> require ... >>> any filter if necessary >>> fileinto "Public"; >>> discard; >>> ... >>> >>> "Public" is your prefix >>> I have several subfolder so I use: fileinto "Public/subfolder1"; >>> >>> You would have >>> /home/vmail/xxx.com/Public/subfolder1 >>> with cur new tmp >>> and a file "dovecot-acl" containing anyone lrs >>> >>> -- >>> Burckhard Schmidt >> > > > -- > Mit freundlichen Grüßen --- Burckhard Schmidt > > Abteilung Systemsoftware und Kommunikation > ZE Computer- und Medienservice der Humboldt-Universität zu Berlin > Postanschrift: Unter den Linden 6, 10099 Berlin > Standort: Rudower Chaussee 26; 12489 Berlin > Tel.: +49-30-2093-70058 Fax: +49-30-2093-70199 > Mail: bschmidt(a)cms.hu-berlin.de <mailto:bschmidt@cms.hu-berlin.de>

1 0

dovecot-sieve in ports?
by unknown＠example.com 20 Mar '16

20 Mar '16

# portmaster mail/dovecot-sieve ===>>> The dependency for mail/dovecot seems to be handled by dovecot2-2.2.22 ===>>> Initial dependency check complete for mail/dovecot-sieve ===>>> Starting build for mail/dovecot-sieve <<<=== ===>>> All dependencies are up to date ===> Cleaning for dovecot-sieve-1.2+0.1.19_2 ===>>> Waiting on fetch & checksum for mail/dovecot-sieve <<<=== ===> License LGPL21 accepted by the user ===> dovecot-sieve-1.2+0.1.19_2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by dovecot-sieve-1.2+0.1.19_2 for building ===> dovecot-1.2.17_6 conflicts with installed package(s): dovecot2-2.2.22 Sooo… Is dovecot-sieve for dovecot 1.x only? Or is the ports tree wonky? -- 2+2=5 for sufficiently large values of 2.

3 2

v2.2.22 released
by Timo Sirainen 19 Mar '16

19 Mar '16

http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz.sig + Added doveadm HTTP API: See http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP + virtual plugin: Mailbox filtering can now be done based on the mailbox metadata. See http://wiki2.dovecot.org/Plugins/Virtual + stats: Added doveadm stats reset to reset global stats. + stats: Added authentication statistics if auth_stats=yes. + dsync, imapc, pop3c & pop3-migration: Many optimizations, improvements and error handling fixes. + doveadm: Most commands now stop soon after SIGINT/SIGTERM. - auth: Auth caching was done too aggressively when %variables were used in default_fields, override_fields or LDAP pass/user_attrs. userdb result_* were also ignored when user was found from cache. - imap: Fixed various assert-crashes caused v2.2.20+. Some of them caught actual hangs or otherwise unwanted behavior towards IMAP clients. - Expunges were forgotten in some situations, for example when pipelining multiple IMAP MOVE commands. - quota: Per-namespaces quota were broken for dict and count backends in v2.2.20+ - fts-solr: Search queries were using OR instead of AND as the separator for multi-token search queries in v2.2.20+. - Single instance storage support wasn't really working in v2.2.16+ - dbox: POP3 message ordering wasn't working correctly. - virtual plugin: Fixed crashes related to backend mailbox deletions.

3 2

lmtp timeout, locks and crashes
by Tom Sommer 19 Mar '16

19 Mar '16

I'm seeing some problems on accounts which get a lot of spam (like, a lot). I get these errors: Mar 15 10:43:49 lmtp(12390): Error: Timeout (29s) while waiting for lock for transaction log file /var/spool/mail/dovecot/xxxx/xxxx/dovecot.list.index.log (WRITE lock held by pid 12193) --- Mar 15 10:43:49 lmtp(12034): Error: Transaction log file /var/spool/mail/dovecot/xxxxx/xxxx/dovecot.list.index.log: marked corrupted --- Mar 15 10:43:49 lmtp(12391): Error: Transaction log /var/spool/mail/dovecot/xxxx/xxxx/dovecot.list.index.log: duplicate transaction log sequence (3) ---- Mar 15 10:43:59 lmtp(xxxx(a)xxxx.dk): Error: Timeout (29s) while waiting for lock for transaction log file /var/spool/mail/dovecot/xxxx/xxxx/dovecot.list.index.log ---- Mar 15 10:43:51 lmtp(12294): Panic: file mail-transaction-log-file.c: line 104 (mail_transaction_log_file_free): assertion failed: (!file->locked) Mar 15 10:43:51 lmtp(12294): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x30d567e07a] -> /usr/lib/dovecot/libdovecot.so.0 [0x30d567e0e6] -> /usr/lib/dovecot/libdovecot.so.0 [0x30d567d4ac] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x30d5299ca7] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_logs_clean+0x28) [0x30d529b698] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_view_close+0x49) [0x30d529a7e9] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x30d5293c03] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_index_refresh_later+0x92) [0x30d525af62] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x30d52589eb] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x30d5259217] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x54) [0x30d52352c4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit+0x16) [0x30d5235386] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_user_autoexpunge+0x1f8) [0x30d522a9b8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_user_unref+0x2a) [0x30d523a16a] -> dovecot/lmtp [DATA 172.17.165.14] [0x40696b] -> dovecot/lmtp [DATA 172.17.165.14] [0x406bd6] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x49) [0x30d5690579] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xdc) [0x30d5691c3c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xa9) [0x30d56906b9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x30d56909e8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x30d562e533] -> dovecot/lmtp [DATA 172.17.165.14](main+0x15c) [0x404c8c] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x36aea1d9f4] -> dovecot/lmtp [DATA 172.17.165.14] [0x404a79] ---- The data is stored on NFS, with single-node access. mmap_disable is set to 'yes' Anyone know how to solve this? or can share some insights. Running dovecot 2.2.21 (5345f22) -- Tom Sommer

4 9

poppassd
by Adrian Minta 19 Mar '16

19 Mar '16

Hello, does anyone of you knows a poppassd implementation compatible with dovecot mysql or ldap backends ? -- Best regards, Adrian Minta

1 0

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