- dovecot - dovecot.org

script-login help
by Jorge Bastos 14 Feb '15

14 Feb '15

Hi, I'm trying to execute a bash script to update the last login, IP, and protocol on the user's record, but I'm not being able 'cause I think this is only for 2.2.24+ http://dovecot.org/pipermail/dovecot/2014-January/094610.html I'm on 2.2.23, any change/example to make it work here? Thanks in advanced, Jorge Bastos

1 0

curious when certain patches might become part of a release
by Benjamin Connelly 13 Feb '15

13 Feb '15

We ran in to this same problem others discussed in this thread: http://dovecot.org/list/dovecot/2014-November/098927.html and have also applied the patches (31262a892ba7 and 80ed82a93c1a) and it seems to have stopped the panics. We usually just use the FreeBSD ports tree to install software, so I'm looking forward to the time when we can go back to that. Will those patches be part of the next release? Benjamin

3 5

doveadm deduplicate commands
by Kevin Laurie 13 Feb '15

13 Feb '15

Hello, I just migrated my emails from gmail using getmail. In the process I got some emails that have been doubled or tripled How do I run the doveadm command to delete copies of same emails? I tried running the following:- doveadm deduplicate -u user(a)domain.net inbox but I get error:- doveadm(root): Fatal: Unknown argument INBOX Could someone share some way to automatically remove duplicated messages? Thanks Kevin

3 6

Dovecot FTS Sor Error
by Kevin Laurie 13 Feb '15

13 Feb '15

Hi, I have been trying to get fts solr to work for a while. Keep getting the error below(was wondering if this was schema related?) root@mail:/var/log# doveadm index -u user(a)domain.net inbox doveadm(thai(a)sicl.net): Error: fts_solr: Indexing failed: Server Error Below is from the apache solr output log:- Appreciate if someone can confirm the cause of this error. Thanks Kevin 2/13/2015, 11:30:53 PM ERROR SolrCore org.apache.solr.common.SolrException: Exception writing document id 1/3765be2ea8594f54780e00003555fc1a/useri(a)domain.net to the index; possible analysis error. org.apache.solr.common.SolrException: Exception writing document id 1/3765be2ea8594f54780e00003555fc1a/ochi(a)sicl.net to the index; possible analysis error. at org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:168) at org.apache.solr.update.processor.RunUpdateProcessor.processAdd(RunUpdateProcessorFactory.java:69) at org.apache.solr.update.processor.UpdateRequestProcessor.processAdd(UpdateRequestProcessor.java:51) at org.apache.solr.update.processor.DistributedUpdateProcessor.doLocalAdd(DistributedUpdateProcessor.java:926) at org.apache.solr.update.processor.DistributedUpdateProcessor.versionAdd(DistributedUpdateProcessor.java:1080) at org.apache.solr.update.processor.DistributedUpdateProcessor.processAdd(DistributedUpdateProcessor.java:692) at org.apache.solr.update.processor.LogUpdateProcessor.processAdd(LogUpdateProcessorFactory.java:100) at org.apache.solr.handler.loader.XMLLoader.processUpdate(XMLLoader.java:247) at org.apache.solr.handler.loader.XMLLoader.load(XMLLoader.java:174) at org.apache.solr.handler.UpdateRequestHandler$1.load(UpdateRequestHandler.java:99) at org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:74) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135) at org.apache.solr.core.SolrCore.execute(SolrCore.java:1967) at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:777) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:418) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:368) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:953) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1014) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:953) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:698) at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:712) at org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1507) at org.apache.solr.update.DirectUpdateHandler2.addDoc0(DirectUpdateHandler2.java:240) at org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:164) ... 40 more Caused by: java.lang.OutOfMemoryError: Java heap space at org.apache.lucene.index.FreqProxTermsWriterPerField$FreqProxPostingsArray.<init>(FreqProxTermsWriterPerField.java:210) at org.apache.lucene.index.FreqProxTermsWriterPerField$FreqProxPostingsArray.newInstance(FreqProxTermsWriterPerField.java:230) at org.apache.lucene.index.ParallelPostingsArray.grow(ParallelPostingsArray.java:48) at org.apache.lucene.index.TermsHashPerField$PostingsBytesStartArray.grow(TermsHashPerField.java:252) at org.apache.lucene.util.BytesRefHash.add(BytesRefHash.java:292) at org.apache.lucene.index.TermsHashPerField.add(TermsHashPerField.java:151) at org.apache.lucene.index.DefaultIndexingChain$PerField.invert(DefaultIndexingChain.java:659) at org.apache.lucene.index.DefaultIndexingChain.processField(DefaultIndexingChain.java:359) at org.apache.lucene.index.DefaultIndexingChain.processDocument(DefaultIndexingChain.java:318) at org.apache.lucene.index.DocumentsWriterPerThread.updateDocument(DocumentsWriterPerThread.java:239) at org.apache.lucene.index.DocumentsWriter.updateDocument(DocumentsWriter.java:454) at org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1511) at org.apache.solr.update.DirectUpdateHandler2.addDoc0(DirectUpdateHandler2.java:240) at org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:164) at org.apache.solr.update.processor.RunUpdateProcessor.processAdd(RunUpdateProcessorFactory.java:69) at org.apache.solr.update.processor.UpdateRequestProcessor.processAdd(UpdateRequestProcessor.java:51) at org.apache.solr.update.processor.DistributedUpdateProcessor.doLocalAdd(DistributedUpdateProcessor.java:926) at org.apache.solr.update.processor.DistributedUpdateProcessor.versionAdd(DistributedUpdateProcessor.java:1080) at org.apache.solr.update.processor.DistributedUpdateProcessor.processAdd(DistributedUpdateProcessor.java:692) at org.apache.solr.update.processor.LogUpdateProcessor.processAdd(LogUpdateProcessorFactory.java:100) at org.apache.solr.handler.loader.XMLLoader.processUpdate(XMLLoader.java:247) at org.apache.solr.handler.loader.XMLLoader.load(XMLLoader.java:174) at org.apache.solr.handler.UpdateRequestHandler$1.load(UpdateRequestHandler.java:99) at org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:74) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135) at org.apache.solr.core.SolrCore.execute(SolrCore.java:1967) at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:777) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:418) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)

1 0

[SOLVED] Thunderbird client certification validation fails with same profile but changed IMAP server software (Re: It works for two SMTP servers and cyrus-imap, why not Dovecot?)
by Daniel Dickinson 13 Feb '15

13 Feb '15

In hopes that searching may turn up the solution for others: The reason client certificate validation was failing in Thunderbird when it had previously succeeded with other servers (both IMAP and SMTP) is precisely that: the client and profile where the same ones used to connect to the server who's hostname hadn't changed, and email addresses and usernames were the same, and Thunderbird can't handle that. Keeping your existing Thunderbird profile when switching the IMAP server software running on the hosting server doesn't work even if you change all the configs that should matter (rename old accounts out of the way, replace the server they are supposed to be contacting with blank, and so on) and create new accounts within the same profile. The workaround for this bug in Thunderbird is to move the old profile out of the way and start fresh. The apparent cause of failure (invalid cert messages and other messages that make it look like it's a configuration or certificate/CA file issue) actually has nothing to do with the actual issue and is a major red herring. Sorry for the noise, back to regular scheduled program... Regards, Daniel On 2015-02-12 6:29 AM, Daniel Curran-Dickinson wrote: > Ok, the patch doesn't actually fix the bug. It appeared to do so in > that after running the server with the patch applied client certificate > validation succeeded, however, it appears this bug is actually > intermittent as, even with the patched package, the server is now > complaining that the client has not provided a valid SSL certificate. > > This is definitely not true as the certificates, and in general > verification of the same client-side certificates work, even with the > same Thunderbird client, with postfix, exim, and cyrus-imapd. > > In short dovecot has some bug that causes verification of certificates > presented by the client to fail, however the bug is not easy to debug as > sometimes config changes work, but later, running the same config, > things fail again. > > There appears to be some sort of caching even across client and server > restarts that is coming into play and confusing the issue. > > Anyone know of SSL caching issues with Window 8.1, particular > Thunderbird on that platform? > > Also why is this bug only affecting dovecot? There is some strangeness > going on here, and, from web searching for the same issue, it appears > others have run into the same issue and had no success in resolving it, > despite also doing everything according to documentation. > > With dovecot 2.2.9 from Ubuntu (i.e. not patched version): > The relevant config bits from dovecot -n are: > > auth_mechanisms = login plain digest-md5 cram-md5 > auth_ssl_require_client_cert = yes > ssl = required > ssl_ca = </path/to/ca.pem > ssl_cert = </path/to/cert.pem > ssl_key = </path/to/key.pem > ssl_protocols = !SSLv2 !SSLv3 > ssl_require_crl = no (yes or no makes no difference) > ssl_verify_client_cert = yes > > Oddly this doesn't appear in dovecot -n, though set > > disable_plaintext_auth = yes > > Client fails whether configured for encrypted passwords or not > Client fails whether using ssl = yes (imaps) on 993 or STARTTLS on 143 > > And yes I have followed the correct ordering of the CA followed by CRL > (and tried without CRL as well). > > In addition I have tried CA + intermediate and CA + crl + intermediate + > crl for startssl.com certificates as well as the above test with > self-signed CA (root CA + crl or just root CA). > > I have also just confirmed (by connecting and sending mail on port 587 > with STARTTLS and SSL required, with client certificate validation > required by postfix) that using the same certificate, same client, same > mail server, that SMTP AUTH + verification of client certificates succeeds. > > Since I've had the same client using the same certificates work with all > three of postfix (SMTP), exim (SMTP), and cyrus-imapd (IMAP), there is > not doubt that there is an issue with dovecot's handling of this scenario. > > I know I'm harping on this 'it works elsewhere' theme, but this bug has > been ignored for ages because of the assumption that user is doing > something wrong, and that is simply not the case, or if it is, dovecot > is very, very bad at indicating what the actual problem is. > > Line-ending are *nix line endings. > > Anything else that you want to suggest along with how to make dovecot > report what the actual problem is if there is some other magic formulae > to invoke? > > If I've missed something it's by no means obvious or explained clearly > anywhere. > > Regards, > > Daniel > > On 2015-02-11 2:33 AM, Daniel Dickinson wrote: >> Hi all, >> >> As I reported earlier (with a typo in the work [BUG]) client >> certification validation *does not* work even if you do everything >> exactly according to all documentation and attempts at helpful advice. >> >> I have seen this issue with both startssl.com and self-signed >> certificates, and based on what I've seen from searching the web, this >> is a problem that has gotten little attention because most people don't >> bother, but are more than willing to give out useless advice on how to >> make it work. >> >> Furthermore the issue does NOT occur with the cyrus-imap mail server, so >> it is definitely a server-side issue. >> >> The actual issue is that the code for calling OpenSSL that constructs >> the client certificate validation is in fact WRONG. >> >> I don't have a perfect patch as I was mostly interested in getting it >> working for my needs and didn't bother with constructing the list of CA >> names to send to the client, preferring to let OpenSSL handle all that >> sort of thing. >> >> What it comes down to is that the code, which probably worked at one >> point, was not correctly updated at some point and since then client >> side certificate validation has been BROKEN. >> >> I have patched against 2.2.9, however I have seen this problem in the >> versions in both Debian Wheezy and Debian Jessie as well. >> >> As you will see from the patch (which is an attachment as people tend to >> complain that patches get mangled when you inline them, and even if I >> have a good client I've gotten heck because the receiver didn't. >> >> Regards, >> >> Daniel >> >

1 0

Howto NTML
by Mark Foley 13 Feb '15

13 Feb '15

Has anyone gotten NTLM working with Dovecot and Outlook? I have a Samba4 domain controller / active directory running just fine on Linux Slackware64 14.1. PLAIN authenticiation works just fine if I create /etc/passwd accounts for the domain users. I've tried for over two weeks to get NTLM working from Outlook 2007 on a domain workstation without success. I end up with various permission errors and ultimately procmail won't deliver if I "adjust" mailbox folder permissions too liberally. Also it seems I have to log in each time in Outlook. If someone has made this work, I'd be very interesting in seeing the doveconf -n output, the permissions on the mailbox directories, the nsswitch.conf, and anything else you had to tweak to get this working. I'd really love to have AD authentication working on this setup! --Mark

2 2

examples of shared shared-mailboxes.db
by Kevin Laurie 13 Feb '15

13 Feb '15

Hello, I need help. i am trying to configure shared in boxes. I need to create a dictionary for shared inbox. how does 1 write shared-mailboxes.db dictionary? any example for the syntax/config? thanks kevin Below is part of the config i am trying to achieve:- plugin { acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db }

2 4

Enabling mod-sequences
by Luca Bertoncello 13 Feb '15

13 Feb '15

Hi list! I have Dovecot 1.2.9 from Ubuntu repositories on my server. Now I installed Horde and it give me sometimes the error "Mailbox does not support mod-sequences". Well, I must say, that I didn't know these mod-sequences, but I can' know all... Well, the question now is: how can I enable the support of the mod-sequences on the mailboxes of my Server? I searched in the Dovecot-Wiki, but I didn't found anything... Thanks a lot for your help Luca Bertoncello (lucabert(a)lucabert.de)

2 2

Dovecot dsync not replicating ".dovecot.sieve -> .sieve/managesieve.sieve" / setactive
by Martin Štefany 12 Feb '15

12 Feb '15

Hello, I've ran into problem with Dovecot and dsync replication. Everything works perfectly, including replication of sieve scripts, except fact that if user activates the 'managesieve' ruleset (I'm using currently Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2" host, by creating symlink ".dovecot.sieve -> .sieve/managesieve.sieve". I've also tried to use 'replication_full_sync_interval', but symlink is not created anyway. I found 2 references already for this problem, but none came to any conclusion: http://dovecot.org/pipermail/dovecot/2014-June/096650.html http://www.dovecot.org/list/dovecot/2014-September/097857.html Here is the output from 'doveconf -n' from both hosts for reference :: mail1 :: # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-123.20.1.el7.x86_64 x86_64 CentOS Linux release 7.0.1406 (Core) auth_cache_size = 5 M auth_debug = yes auth_default_realm = example.com auth_gssapi_hostname = mail.example.com auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = plain gssapi auth_realms = example.com auth_verbose = yes doveadm_password = <secret> lmtp_save_to_detail_mailbox = yes mail_debug = yes mail_location = maildir:~/Maildir mail_plugins = " fts fts_lucene notify quota replication virtual zlib" 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 All { auto = create special_use = \All } 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 Templates { auto = subscribe } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf.ext driver = ldap } plugin { fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. mail_replica = tcps:mail2.example.com:10993 quota = maildir:User quota quota_rule = *:storage=4GB quota_rule2 = Trash:storage=+50MB sieve = ~/.dovecot.sieve sieve_after = /srv/sieve/after.d/ sieve_before = /srv/sieve/before.d/ sieve_default = /srv/sieve/default.d/dovecot.sieve sieve_dir = ~/.sieve sieve_global_dir = /srv/sieve/ zlib_save = gz zlib_save_level = 9 } postmaster_address = postmaster(a)example.com protocols = imap lmtp sieve service aggregator { fifo_listener replication-notify-fifo { group = vmail mode = 0660 user = vmail } unix_listener replication-notify { group = vmail mode = 0660 user = vmail } } service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service doveadm { inet_listener { port = 10993 ssl = yes } } service imap-login { inet_listener imaps { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = vmail mode = 0660 user = vmail } } ssl_ca = </etc/ipa/ca.crt ssl_cert = </etc/pki/tls/certs/dovecot.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ECDSA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA ssl_client_ca_file = /etc/ipa/ca.crt ssl_client_cert = </etc/pki/tls/certs/dovecot.pem ssl_client_key = </etc/pki/tls/private/dovecot.key ssl_key = </etc/pki/tls/private/dovecot.key ssl_parameters_regenerate = 1 weeks ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap override_fields = gid=vmail home=/srv/vmail/example.com/%n } verbose_ssl = yes protocol lmtp { mail_plugins = " fts fts_lucene notify quota replication virtual zlib sieve" } protocol imap { mail_plugins = " fts fts_lucene notify quota replication virtual zlib imap_quota imap_zlib" } mail2 :: # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-123.20.1.el7.x86_64 x86_64 CentOS Linux release 7.0.1406 (Core) auth_cache_size = 5 M auth_debug = yes auth_default_realm = example.com auth_gssapi_hostname = mail.example.com auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = plain gssapi auth_realms = example.com auth_verbose = yes doveadm_password = <secret> lmtp_save_to_detail_mailbox = yes mail_debug = yes mail_location = maildir:~/Maildir mail_plugins = " fts fts_lucene notify quota replication virtual zlib" 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 All { auto = create special_use = \All } 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 Templates { auto = subscribe } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf.ext driver = ldap } plugin { fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. mail_replica = tcps:mail1.example.com:10993 quota = maildir:User quota quota_rule = *:storage=4GB quota_rule2 = Trash:storage=+50MB sieve = ~/.dovecot.sieve sieve_after = /srv/sieve/after.d/ sieve_before = /srv/sieve/before.d/ sieve_default = /srv/sieve/default.d/dovecot.sieve sieve_dir = ~/.sieve sieve_global_dir = /srv/sieve/ zlib_save = gz zlib_save_level = 9 } postmaster_address = postmaster(a)example.com protocols = imap lmtp sieve service aggregator { fifo_listener replication-notify-fifo { group = vmail mode = 0660 user = vmail } unix_listener replication-notify { group = vmail mode = 0660 user = vmail } } service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service doveadm { inet_listener { port = 10993 ssl = yes } } service imap-login { inet_listener imaps { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = vmail mode = 0660 user = vmail } } ssl_ca = </etc/ipa/ca.crt ssl_cert = </etc/pki/tls/certs/dovecot.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ECDSA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA ssl_client_ca_file = /etc/ipa/ca.crt ssl_client_cert = </etc/pki/tls/certs/dovecot.pem ssl_client_key = </etc/pki/tls/private/dovecot.key ssl_key = </etc/pki/tls/private/dovecot.key ssl_parameters_regenerate = 1 weeks ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap override_fields = gid=vmail home=/srv/vmail/example.com/%n } verbose_ssl = yes protocol lmtp { mail_plugins = " fts fts_lucene notify quota replication virtual zlib sieve" } protocol imap { mail_plugins = " fts fts_lucene notify quota replication virtual zlib imap_quota imap_zlib" } And reference directory structure :: [root@mail1 ~]# tree -a /srv /srv ├── sieve │ ├── after.d │ ├── before.d │ │ ├── spam.sieve │ │ └── spam.svbin │ └── default.d └── vmail └── example.com └── <user> ├── .dovecot.lda-dupes ├── .dovecot.sieve -> .sieve/managesieve.sieve ├── .dovecot.svbin ├── Maildir │ ├── .All │ │ ├── cur │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── .Archives │ │ ├── cur │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── cur │ ├── dovecot.index.cache │ ├── dovecot.index.log │ ├── dovecot.index.thread │ ├── dovecot-keywords │ ├── dovecot.mailbox.log │ ├── dovecot-uidlist │ ├── dovecot-uidvalidity │ ├── dovecot-uidvalidity.54dbb6f0 │ ├── .Drafts │ │ ├── cur │ │ ├── dovecot.index.cache │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── .Junk │ │ ├── cur │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── lucene-indexes │ │ ├── _k.cfs │ │ ├── segments_17 │ │ └── segments.gen │ ├── maildirfolder │ ├── maildirsize │ ├── new │ ├── .Sent │ │ ├── cur │ │ ├── dovecot.index.cache │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── subscriptions │ ├── .Templates │ │ ├── cur │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── tmp │ └── .Trash │ ├── cur │ ├── dovecot.index.log │ ├── dovecot-uidlist │ ├── maildirfolder │ ├── new │ └── tmp └── .sieve ├── managesieve.sieve └── tmp [root@mail2 ~]# tree -a /srv /srv ├── sieve │ ├── after.d │ ├── before.d │ │ ├── spam.sieve │ │ └── spam.svbin │ └── default.d └── vmail └── example.com └── <user> ├── Maildir │ ├── .All │ │ ├── cur │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── .Archives │ │ ├── cur │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── cur │ ├── dovecot.index.cache │ ├── dovecot.index.log │ ├── dovecot-keywords │ ├── dovecot.mailbox.log │ ├── dovecot-uidlist │ ├── dovecot-uidvalidity │ ├── dovecot-uidvalidity.54dbb6f5 │ ├── .Drafts │ │ ├── cur │ │ ├── dovecot.index.cache │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── .Junk │ │ ├── cur │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── lucene-indexes │ │ ├── _k.cfs │ │ ├── segments_17 │ │ └── segments.gen │ ├── maildirfolder │ ├── maildirsize │ ├── new │ ├── .Sent │ │ ├── cur │ │ ├── dovecot.index.cache │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── subscriptions │ ├── .Templates │ │ ├── cur │ │ ├── dovecot.index.log │ │ ├── dovecot-uidlist │ │ ├── maildirfolder │ │ ├── new │ │ └── tmp │ ├── tmp │ └── .Trash │ ├── cur │ ├── dovecot.index.log │ ├── dovecot-uidlist │ ├── maildirfolder │ ├── new │ └── tmp └── .sieve ├── managesieve.sieve └── tmp Thanks a lot for Dovecot anyway! ;) Martin

2 2

[Patch] Allow for more than one recipient_delimiter (a la postfix 2.11)
by Lennart Weller 12 Feb '15

12 Feb '15

Hey everyone, as my previous emails apparently got stuck in a spam filter I'll try this again. The patches attached here allow for more than one recipient delimiter in the address. Which is allowed in postfix since version 2.11. E.g. lhw+postfix(a)ring0.de would be equal to lhw-postfix(a)ring0.de if configured that way. Same as postfix only the first discovered delimiter is taken into account and the priority is first to last in the list. Lennart

1 0