- dovecot - dovecot.org

Problems to configure IMAP Quota
by Jacques Belin 13 Sep '17

13 Sep '17

Hello, We manage a mail server using Dovecot under Debian. Since a long time, we run nightly a script permitting to display the storage usage of each user on the webmail, using internal calls. The usage on each mailbox is stored in a Mysql database. For several reasons, we would now want to use the IMAP quota feature, not only to let users have the quota displayed from their Mail clients. But testing that features, I encounter two problems : 1) It seems that when we use the sql dict, a map contaning the patern "priv/quota/limit/messages" is mandatory. Not specifying it in dovecot-dict-sql.conf.ext issues an error. As we are interested only by the storage size and don't want to process the number of messages, how to get rid of it ? 2) We store the storage value in kilobytes. But the plugin seems to only accept storage in bytes, Is there any way to let know to dovecot that the value stored in the database is in kilobytes ? (of course, I tried to put "size/1024" in the value_field field of the map. It works, but generate a lot of error lines in the dovecot log as it create a syntaxly incorrect MySQL uodate request...) Jacques. -- The last man connected to the Interet was browsing some old WebSites. "You have new mail" appeared on the screen... --------------------------- adapted from a short Fredric Brown's story

3 3

concering dovecot logging
by Rajesh M 13 Sep '17

13 Sep '17

hi had a question concerning dovecot lda logging. deliver_log_format = From:<%f>-<%e> :: Subject:<%s> :: Status:<%$> :: MsgID:<%m> :: Size<%p> :: vSize<%w> am getting %e ie envelope sender as MAILER-DAEMON in the logs Sep 11 08:35:50 lda(noc(a)xxx.com): Info: sieve: From:<bmmsro0612(a)xxx.co.in>-<MAILER-DAEMON> :: Subject:<Fw: ccccccn> :: Status:<forwarded to <nocforward(a)yyyyy.com>> :: MsgID:<<OFBECDF3FA.57B3772C-ON65258198.00111392-65258198.00111394(a)xxx.co.in>> :: Size<12497> :: vSize<12687> what could be the reason ? thanks, rajesh

2 1

Problem w/ Dovecot authentication against AD
by Garry Glendown 13 Sep '17

13 Sep '17

Hi, I had to start using Dovecot on a machine as the new OS does not come with Cyrus IMAP anymore. After multiple problems, I managed to get everything working, including LDAP authentication against the (old) Novell LDAP server. Anyway, the authentication is supposed to be migrated to the new Windows AD. For other tools, I successfully migrated the config to use AD, but somehow Dovecot does not work as it should. I've been going back and forth, trying everything I could think of, but still can't get it to work. Here's the excerpt from the config file: hosts = 10.10.10.210 uris = ldap://10.10.10.210:389 dn = cn=Administrator,cn=Users,dc=srv,dc=SLD,dc=net dnpass = PASSWORD tls = no debug_level = -1 auth_bind = yes ldap_version = 3 base = DC=srv,dc=SLD,dc=net deref = never scope = subtree user_attrs = sAMAccountName=user user_filter = (&(sAMAccountName=%n)(objectclass=person)) pass_attrs = sAMAccountName=user pass_filter = (&(sAMAccountName=%n)(objectclass=person)) iterate_attrs = mail=user iterate_filter = (objectclass=person) default_pass_scheme = PLAIN The problem might be caused by the referal-info sent by the AD, which I can see both in the results dovecot gets (checked with tcpdump), as well as in ldapsearch ... apart from the actual search result, I always get three additional results: # refldap://DomainDnsZones.srv.SLD.net/DC=DomainDnsZones,DC=srv,DC=SLD,DC=net # refldap://ForestDnsZones.srv.SLD.net/DC=ForestDnsZones,DC=srv,DC=SLD,DC=net # refldap://srv.SLD.net/CN=Configuration,DC=srv,DC=SLD,DC=net >From what I can see in the pcap as well as some of the logs, dovecot binds to the AD, sends out the LDAP query correctly, gets the lookup result with the user queried plus the above three referrals, then unbinds from the (named) bind, attempts a simple bind without dn/dnpass (multiple times), and finally sends three additional search requests under the search bases cn=Configuration,DC=srv,DC=SLD,DC=net DC=ForestDnsZones,DC=srv,DC=SLD,DC=net DC=DomainDnsZones,DC=srv,DC=SLD,DC=net These three requests are denied by the AD as they are not permitted without a successful prior bind. Dovecot then fails the auth process. Is there a way to stop Dovecot from using the referals? Openldap seems to have an option to disable referals, but Dovecot does not allow that option in its LDAP config, and having the option set in the global ldap.conf doesn't seem to help any, either. Is there possibly a way to disable the referal information on the AD side? Thanks, Garry -- PGP Fingerprint: A79F A33F 5B13 BEB7 A51D 274F F99C 3AE2 4BCB 7015

3 3

Re: Dovecot and Letsencrypt certs
by Daniel Miller 13 Sep '17

13 Sep '17

And remove that "postfix reload" command - Postfix doesn't require explicit reloading. It'll pickup the changed cert automagically. Daniel On 9/12/2017 9:26 AM, Daniel Miller wrote: > What's wrong with using a certbot "post-hook" script such as: > > #!/bin/bash > echo "Letsencrypt renewal hook running..." > echo "RENEWED_DOMAINS=$RENEWED_DOMAINS" > echo "RENEWED_LINEAGE=$RENEWED_LINEAGE" > > if grep --quiet "your.email.domain" <<< "$RENEWED_DOMAINS"; then > /usr/local/sbin/dovecot reload > /usr/sbin/postfix reload > fi > > Daniel > > On 9/11/2017 1:57 PM, Joseph Tam wrote: >> <master(a)remort.net> writes: >> >>> "writing a script to check the certs" - there is no need to write any >>> scripts. As one mentioned, it's done by a hook to certbot. Please read >>> the manuals for LE or certbot. The issue you have is quite common and >>> of course certbot designed to do it for you. >> >> Won't work, of course, if you employ the least-privilege security >> principle >> and run the certbot as a non-privileged user. You'll need a script with >> administrator privileges to detect cert renewals and restart the >> service. >> >> I can't willy-nilly restart dovecot to pick up renewed certs without >> webmail disruptions. (My webmail uses persistent IMAP sessions.) >> All users get dumped and need to re-authenticate. If a user happens to >> be drafting a message that took 2 hours to compose, I will surely hear >> about it. I should probably install a IMAP proxy to isolate the effects >> of restarts. Most mail readers cope with restarts just fine, though. >> >> Joseph Tam <jtam.home(a)gmail.com>

3 3

Re: Dovecot and Letsencrypt certs
by Joseph Tam 13 Sep '17

13 Sep '17

On Tue, 12 Sep 2017, dovecot-request(a)dovecot.org wrote: > What's wrong with using a certbot "post-hook" script such as: > > #!/bin/bash > echo "Letsencrypt renewal hook running..." > echo "RENEWED_DOMAINS=$RENEWED_DOMAINS" > echo "RENEWED_LINEAGE=$RENEWED_LINEAGE" > > if grep --quiet "your.email.domain" <<< "$RENEWED_DOMAINS"; then > ??? /usr/local/sbin/dovecot reload > ?? /usr/sbin/postfix reload > fi Nothing, if you let your certbot run as root. (I'm assuming that's how these hooks work -- it's called after cert renewal using the same credentials as the certbot.) If you use privilege separation, and run the certbot as a regular user process, this won't work. You might have this scenario if, for example using the context of web serving, you serve many virtual sites with different owners, and you don't want give each owner administrative access. Joseph Tam <jtam.home(a)gmail.com>

2 1

Dynamic host with password plugin
by Jorge Bastos 12 Sep '17

12 Sep '17

Howdy, I’m making my multi-server instalation ready, but I’m facing just one small issue, that is with password plugin. So, in config.inc.php of it I have: config['password_db_dsn'] = 'mysql://webmail:bdkddddddz@192.168.69.222/postfix'; but, as I’m using in roundcube’s config.inc.php “dynamic” host: $config['default_host'] = 'mail.%s'; Can I have in the password plugin config.inc.php the same variable? (I can use same user/password/db on both servers for password change) Thanks in advanced,

1 0

Re: Dovecot and Letsencrypt certs
by Joseph Tam 12 Sep '17

12 Sep '17

<master(a)remort.net> writes: > "writing a script to check the certs" - there is no need to write any > scripts. As one mentioned, it's done by a hook to certbot. Please read > the manuals for LE or certbot. The issue you have is quite common and > of course certbot designed to do it for you. Won't work, of course, if you employ the least-privilege security principle and run the certbot as a non-privileged user. You'll need a script with administrator privileges to detect cert renewals and restart the service. I can't willy-nilly restart dovecot to pick up renewed certs without webmail disruptions. (My webmail uses persistent IMAP sessions.) All users get dumped and need to re-authenticate. If a user happens to be drafting a message that took 2 hours to compose, I will surely hear about it. I should probably install a IMAP proxy to isolate the effects of restarts. Most mail readers cope with restarts just fine, though. Joseph Tam <jtam.home(a)gmail.com>

2 1

RE: dovecot Digest, Vol 173, Issue 28 (INTERNAL)
by Arvid.Eikas＠telenor.com 12 Sep '17

12 Sep '17

Hi, I enabled rawlog. Everything seems to be OK but the dovecot-log shows a fatal error and core dump. (created a core file) Arvid Rawlog in <<< STAT >>> <<< LIST >>> <<< UIDL 1 >>> <<< UIDL >>> <<< QUIT >>> Rawlog out <<< +OK Logged in. >>> <<< +OK 22 17589388 >>> <<< +OK 22 messages: 1 6725 ¨¨¨¨¨¨ 22 17387080 . >>> <<< +OK 1 1504264023.M267772P16598V0000000000000027I00000000046A5436.nsmx2.nsc.no,S=6571 >>> <<< +OK 1 1504264023.M267772P16598V0000000000000027I00000000046A5436.nsmx2.nsc.no,S=6571 ........ 22 1505125157.M901211P7821V0000000000000027I00000000046A340F.nsmx2.nsc.no,S=17164095 . >>> <<< +OK Logging out. >>> DOVECOT LOG Sep 12 11:40:56 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read finished A [88.89.118.45] Sep 12 11:40:56 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write session ticket A [88.89.118.45] Sep 12 11:40:56 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [88.89.118.45] Sep 12 11:40:56 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write finished A [88.89.118.45] Sep 12 11:40:56 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [88.89.118.45] Sep 12 11:40:56 pop3-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [88.89.118.45] Sep 12 11:40:56 pop3-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [88.89.118.45] Sep 12 11:40:56 pop3-login: Info: Login: user=<viboge>, method=PLAIN, rip=88.89.118.45, lip=148.123.160.116, mpid=18250, TLS, session=<nR4H1/pYvc1YWXYt> Sep 12 11:40:56 pop3(viboge) Session-ID nR4H1/pYvc1YWXYt RemoteIP 88.89.118.45 Maildir /var/nextmail/nfs2.flex14/49/79/841 Info: Disconnected: Logged out top=0/0, retr=0/0, del=0/22, size=17589388, totalread=32, totalsent=2181, uidl=22/50a23327 Sep 12 11:40:56 pop3-login: Debug: SSL alert: close notify [88.89.118.45] Sep 12 11:40:56 pop3-login: Error: ENGINE_finish, bad functional reference count Sep 12 11:40:56 pop3-login: Fatal: master: service(pop3-login): child 18247 killed with signal 6 (core dumped) -----Original Message----- From: Aki Tuomi [mailto:aki.tuomi@dovecot.fi] Sent: 12. september 2017 08:37 To: dovecot(a)dovecot.org; Eikås Arvid Subject: Re: dovecot Digest, Vol 173, Issue 28 (INTERNAL) ~$ openssl s_client -connect 192.168.122.14:110 -starttls pop3 CONNECTED(00000003) <snip/> Verify return code: 10 (certificate has expired) --- +OK Dovecot ready. USER testuser1 +OK PASS pass +OK Logged in. LIST +OK 11 messages: 1 14 2 14 3 14 4 14 5 14 6 14 7 14 8 14 9 14 10 14 11 14 . QUIT DONE and no crash occurs. Using Dovecot v2.2.32 (dfbe293) Aki On 12.09.2017 09:33, Arvid.Eikas(a)telenor.com wrote: > Hi, > > It is quite easy. > I use a client (thunderbird or windows live mail) set it up to use starttls on standard port 110. Logon and just do a list on the mailbox. The fatal error occurred when I logoff. > > Arvid > > -----Original Message----- > From: dovecot [mailto:dovecot-bounces@dovecot.org] On Behalf Of > dovecot-request(a)dovecot.org > Sent: 11. september 2017 14:57 > To: dovecot(a)dovecot.org > Subject: dovecot Digest, Vol 173, Issue 28 > > Send dovecot mailing list submissions to > dovecot(a)dovecot.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://dovecot.org/mailman/listinfo/dovecot > or, via email, send a message with subject or body 'help' to > dovecot-request(a)dovecot.org > > You can reach the person managing the list at > dovecot-owner(a)dovecot.org > > When replying, please edit your Subject line so it is more specific than "Re: Contents of dovecot digest..." > > > Today's Topics: > > 1. Re: pop3-login core dump when using TLSSTART on version > dovecot-2.2.32 (INTERNAL) (Aki Tuomi) > 2. Re: Per-user quota (passwd) (Evgeniy Korneechev) > 3. Re: Per-user quota (passwd) (Aki Tuomi) > 4. Re: Is it possible to disable pipelining in imapc? (Nagy, > Attila) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 11 Sep 2017 13:57:19 +0300 > From: Aki Tuomi <aki.tuomi(a)dovecot.fi> > To: dovecot(a)dovecot.org > Subject: Re: pop3-login core dump when using TLSSTART on version > dovecot-2.2.32 (INTERNAL) > Message-ID: <cd450054-53c4-2f84-eba7-7ce602c26892(a)dovecot.fi> > Content-Type: text/plain; charset=utf-8 > > Can you outline the exact steps you perform to get this? > > Aki > > On 11.09.2017 13:42, Arvid.Eikas(a)telenor.com wrote: >> Hi, >> >> I switched back to 2.2.27 with the same config that I am using for 2.2.32 and it work fine. >> >> Sep 11 11:49:37 imap-login: Info: Login: user=<viboge>, method=PLAIN, >> rip=88.89.118.45, lip=148.123.160.116, mpid=18709, TLS, >> session=<v7o22OZYrsdYWXYt> Sep 11 11:49:40 imap(mailuser) Session-ID >> v7o22OZYrsdYWXYt RemoteIP 88.89.118.45 Maildir >> /var/nextmail/nfs2.flex14/49/79/841 Info: Logged out in=4518 >> out=273720 deleted 0 expunged 0 trashed 0 Sep 11 11:49:40 imap-login: >> Debug: SSL alert: close notify [88.89.118.45] >> >> How could I proceed? Any clue? It is quite annoying to see this entry in the log for each session. >> >> Arvid >> >> >> >> >> -----Original Message----- >> From: Aki Tuomi [mailto:aki.tuomi@dovecot.fi] >> Sent: 11. september 2017 09:18 >> To: Eik?s Arvid; dovecot(a)dovecot.org >> Subject: Re: pop3-login core dump when using TLSSTART on version >> dovecot-2.2.32 (INTERNAL) >> >> Hi! >> >> I tried to reproduce this problem with dovecot-2.2.32 and OpenSSL 1.0.1k and was not able to. I enabled -DREF_CHECK on OpenSSL, but to no avail, the process did not crash. Is there something else you've done? >> >> Aki >> >> >> On 11.09.2017 08:07, Arvid.Eikas(a)telenor.com wrote: >>> Hi, >>> >>> Here is the gdb output. >>> >>> Arvid >>> >>> GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7 Copyright (C) >>> 2013 Free Software Foundation, Inc. >>> License GPLv3+: GNU GPL version 3 or later >>> <http://gnu.org/licenses/gpl.html> >>> This is free software: you are free to change and redistribute it. >>> There is NO WARRANTY, to the extent permitted by law. Type "show copying" >>> and "show warranty" for details. >>> This GDB was configured as "x86_64-redhat-linux-gnu". >>> For bug reporting instructions, please see: >>> <http://www.gnu.org/software/gdb/bugs/>... >>> Reading symbols from /local/misc/mail/dovecot-32/libexec/dovecot/pop3-login...done. >>> [New LWP 15894] >>> Core was generated by `dovecot-test/pop3-login'. >>> Program terminated with signal 6, Aborted. >>> #0 0x00007ff0bd9cf1d7 in raise () from /lib64/libc.so.6 Missing >>> separate debuginfos, use: debuginfo-install >>> glibc-2.17-157.el7_3.1.x86_64 >>> (gdb) bt full >>> #0 0x00007ff0bd9cf1d7 in raise () from /lib64/libc.so.6 No symbol >>> table info available. >>> #1 0x00007ff0bd9d08c8 in abort () from /lib64/libc.so.6 No symbol >>> table info available. >>> #2 0x00007ff0bd3c0f2f in engine_unlocked_finish (e=0x1c51c60, unlock_for_handlers=1) at eng_init.c:115 >>> to_return = 1 >>> #3 0x00007ff0bd3c1064 in ENGINE_finish (e=0x1c51c60) at eng_init.c:150 >>> to_return = 1 >>> #4 0x00007ff0be0f9300 in ssl_proxy_deinit () from >>> /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 >>> No symbol table info available. >>> #5 0x00007ff0be0f4472 in main_deinit () from >>> /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 >>> No symbol table info available. >>> #6 0x00007ff0be0f479f in login_binary_run () from >>> /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 >>> No symbol table info available. >>> #7 0x00000000004032da in main (argc=1, argv=0x7ffe3059f3f8) at >>> client.c:356 No locals. >>> >>> >>> >>> -----Original Message----- >>> From: Aki Tuomi [mailto:aki.tuomi@dovecot.fi] >>> Sent: 8. september 2017 14:08 >>> To: Eik?s Arvid; dovecot(a)dovecot.org >>> Subject: Re: pop3-login core dump when using TLSSTART on version >>> dovecot-2.2.32 (OPEN) >>> >>> I assume you mean STARTTLS. Can you provide gdb /path/to/bin /path/to/core and provide output of bt full? >>> >>> Aki >>> >>> >>> On 08.09.2017 15:01, Arvid.Eikas(a)telenor.com wrote: >>>> Hi, >>>> >>>> Pop3-login are CORE-dumping when I log on with TLSSTART, I believe the same will happen with imap-logon to, but I have not tested it yet. >>>> The TLS session is coming up and it works fine until I log off, then it's core dump. Open sslvesrion is openssl-1.0.2k. >>>> We ran dovecot-2.2.27 before we upgraded to dovecote-2.2.32, and >>>> that seems to work fine. (not core dumping) >>>> >>>> >>>> Arvid >>>> >>>> >>>> LOG >>>> Sep 05 14:27:34 pop3-login: Debug: SSL: elliptic curve secp384r1 >>>> will be used for ECDH and ECDHE key exchanges Sep 05 14:30:30 pop3-login: >>>> Debug: SSL: elliptic curve secp384r1 will be used for ECDH and >>>> ECDHE key exchanges Sep 05 14:30:30 pop3-login: Debug: SSL: >>>> elliptic curve >>>> secp384r1 will be used for ECDH and ECDHE key exchanges Sep 05 >>>> 14:30:42 pop3-login: Debug: SSL: elliptic curve secp384r1 will be >>>> used for ECDH and ECDHE key exchanges Sep 05 14:30:42 pop3-login: Debug: >>>> SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key >>>> exchanges Sep 05 14:30:50 pop3-login: Info: Login: user=<tstrand>, >>>> method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=18361, secured, >>>> session=<65m8ZXBYtpN/AAAB> Sep 05 14:30:50 pop3-login: Error: >>>> ENGINE_finish, bad functional reference count Sep 05 14:30:50 >>>> pop3-login: Fatal: master: service(pop3-login): child 18359 killed >>>> with signal 6 (core dumped) >>>> >>>> >>>> >>>> >>>> >>>> >>>> From ./crypto/engine/eng_init.c >>>> >>>> ......... >>>> int engine_unlocked_finish(ENGINE *e, int unlock_for_handlers) { >>>> int to_return = 1; >>>> >>>> /* >>>> * Reduce the functional reference count here so if it's the terminating >>>> * case, we can release the lock safely and call the finish() handler >>>> * without risk of a race. We get a race if we leave the count until >>>> * after and something else is calling "finish" at the same time - >>>> * there's a chance that both threads will together take the count from 2 >>>> * to 0 without either calling finish(). >>>> */ >>>> e->funct_ref--; >>>> engine_ref_debug(e, 1, -1); >>>> if ((e->funct_ref == 0) && e->finish) { >>>> if (unlock_for_handlers) >>>> CRYPTO_w_unlock(CRYPTO_LOCK_ENGINE); >>>> to_return = e->finish(e); >>>> if (unlock_for_handlers) >>>> CRYPTO_w_lock(CRYPTO_LOCK_ENGINE); >>>> if (!to_return) >>>> return 0; >>>> } >>>> #ifdef REF_CHECK >>>> if (e->funct_ref < 0) { >>>> fprintf(stderr, "ENGINE_finish, bad functional reference count\n"); >>>> abort(); >>>> >>>> ......... >>>> >>>> /* The API (locked) version of "finish" */ int ENGINE_finish(ENGINE >>>> *e) { >>>> int to_return = 1; >>>> >>>> if (e == NULL) { >>>> ENGINEerr(ENGINE_F_ENGINE_FINISH, ERR_R_PASSED_NULL_PARAMETER); >>>> return 0; >>>> } >>>> CRYPTO_w_lock(CRYPTO_LOCK_ENGINE); >>>> to_return = engine_unlocked_finish(e, 1); >>>> CRYPTO_w_unlock(CRYPTO_LOCK_ENGINE); >>>> if (!to_return) { >>>> ENGINEerr(ENGINE_F_ENGINE_FINISH, ENGINE_R_FINISH_FAILED); >>>> return 0; >>>> } >>>> return to_return; >>>> } > > > ------------------------------ > > Message: 2 > Date: Mon, 11 Sep 2017 14:48:47 +0300 (MSK) > From: Evgeniy Korneechev <ekorneechev(a)altlinux.org> > To: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Cc: dovecot <dovecot(a)dovecot.org> > Subject: Re: Per-user quota (passwd) > Message-ID: > <2046000051.747964.1505130527842.JavaMail.zimbra(a)remotesystems.ru> > Content-Type: text/plain; charset=utf-8 > > Hi. > But there is one problem... > > protocol lda { > mail_plugins = " quota autocreate sieve quota" > plugin { > quota = dict:user::file:/var/vmail/glu_vrem/%u/.quotausage > } > } > protocol imap { > mail_plugins = " quota autocreate autocreate imap_quota" > plugin { > autocreate = INBOX > autocreate2 = Sent > autocreate3 = Trash > autocreate4 = Drafts > autocreate5 = Junk > autosubscribe = INBOX > autosubscribe2 = Sent > autosubscribe3 = Trash > autosubscribe4 = Drafts > autosubscribe5 = Junk > quota = dict:user::file:/var/vmail/glu_vrem/%u/.quotausage > } > } > >> Users with non-standard quota in passwd-file: >>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/admin >>>>>>>> i strator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/home >>>>>>>> / DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >> Others from passwd. > > > Files ".quotausage" are created in different directories: > /var/vmail/glu_vrem/administrator\DOM/.quotausage > /var/vmail/glu_vrem/administrator(a)email.dom/.quotausage > And must in the folder "/var/vmail/glu_vrem/administrator" > > How fix it? > > > ----- ???????? ????????? ----- >> ??: "Evgeniy Korneechev" <ekorneechev(a)altlinux.org> >> ????: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >> ?????: "dovecot" <dovecot(a)dovecot.org> >> ????????????: ???????, 30 ???? 2017 ? 10:39:16 >> ????: Re: Per-user quota (passwd) >> Our solution: >> userdb { >> args = /etc/imap.passwd >> driver = passwd-file >> override_fields = home=/var/vmail/glu_vrem/%u } userdb { driver = >> passwd override_fields = home=/var/vmail/glu_vrem/%u } >> >> Users with non-standard quota in passwd-file: >>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/admin >>>>>>>> i strator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/home >>>>>>>> / DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >> Others from passwd. >> >> Its works! Thanks. >> >> >> ----- ???????? ????????? ----- >>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>> ????: "dovecot" <dovecot(a)dovecot.org> >>> ????????????: ???????, 29 ???? 2017 ? 14:40:44 >>> ????: Re: Per-user quota (passwd) >>> Oh you have multiple db's, I missed that. >>> >>> Remove auth_username_format, and instead >>> >>> userdb { >>> args = /etc/imap.passwd username_format=%Ln driver = passwd-file >>> override_fields = home=/var/vmail/glu_vrem/%u } >>> >>> On 29.06.2017 14:35, Evgeniy Korneechev wrote: >>>> with auth_username_format = %Ln: >>>> >>>> Jun 28 14:43:41 auth: Debug: master in: USER 1 iivanov.ia(a)example.com >>>> service=lda >>>> Jun 28 14:43:41 auth-worker(18369): Debug: passwd(iivanov.ia): >>>> lookup Jun 28 14:43:41 auth-worker(18369): Info: passwd(iivanov.ia): >>>> unknown user - trying the next userdb Jun 28 14:43:41 >>>> auth-worker(18369): Debug: sql(iivanov.ia): SELECT email as user, >>>> maildir as home, CONCAT('maildir:', maildir, '/Maildir') as mail, >>>> uid, gid, \ >>>> CONCAT('*:storage=', quota, 'B') AS quota_rule, CONCAT(maildir, '/.sieve') as >>>> sieve FROM mail_user WHERE (login = 'iivanov.ia' OR email = >>>> 'iivanov.ia') Jun 28 14:43:41 auth-worker(18369): Info: >>>> sql(iivanov.ia): unknown user >>>> >>>> Maybe %Lu? >>>> >>>> ----- ???????? ????????? ----- >>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>> ????????????: ???????, 29 ???? 2017 ? 14:10:07 >>>>> ????: Re: Per-user quota (passwd) >>>>> Yes. >>>>> >>>>> Aki >>>>> >>>>> On 29.06.2017 14:07, Evgeniy Korneechev wrote: >>>>>> And if such a user: >>>>>> email (from AD) = ivanov.ia(a)example.com login (from AD), %n = >>>>>> iivanov %d = DOM %u = iivanov@DOM >>>>>> >>>>>> ? >>>>>> >>>>>> ----- ???????? ????????? ----- >>>>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>>>> ????????????: ???????, 29 ???? 2017 ? 13:59:05 >>>>>>> ????: Re: Per-user quota (passwd) or use, as I indicated before, >>>>>>> auth_username_format = %Ln >>>>>>> >>>>>>> Aki >>>>>>> >>>>>>> >>>>>>> On 29.06.2017 13:58, Evgeniy Korneechev wrote: >>>>>>>> Hi! >>>>>>>> workaround: >>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/admin >>>>>>>> i strator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/home >>>>>>>> / DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>> >>>>>>>> But this is not a solution for 1000 users ... >>>>>>>> Maybe is there extra field "userdb_mail=administrator(a)email.dom" >>>>>>>> for email to passwd-file? >>>>>>>> >>>>>>>> ----- ???????? ????????? ----- >>>>>>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>>>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>>>>>> ????????????: ?????, 28 ???? 2017 ? 12:40:48 >>>>>>>>> ????: Re: Per-user quota (passwd) On 28.06.2017 12:36, Aki >>>>>>>>> Tuomi wrote: >>>>>>>>>> On 28.06.2017 12:25, Evgeniy Korneechev wrote: >>>>>>>>>>> Hello! >>>>>>>>>>> We have passwd=pam, userdb=passwd. >>>>>>>>>>> passdb { >>>>>>>>>>> driver = pam #server was entered domain Active Directory } >>>>>>>>>>> userdb { >>>>>>>>>>> driver = passwd >>>>>>>>>>> override_fields = home=/var/vmail/glu_vrem/%u } >>>>>>>>>>> >>>>>>>>>>> How can i use per-user quota? Only passwd-file? >>>>>>>>>>> >>>>>>>>>>> I tried: >>>>>>>>>>> userdb { >>>>>>>>>>> args = /etc/imap.passwd >>>>>>>>>>> driver = passwd-file >>>>>>>>>>> override_fields = home=/var/vmail/glu_vrem/%u } >>>>>>>>>>> /etc/imap.passwd: >>>>>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/ad >>>>>>>>>>> m inistrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>>>>> >>>>>>>>>>> Authentication and quota - now OK. But doesn't work sending >>>>>>>>>>> and receiving mail... >>>>>>>>>>> postfix say 'Unknown user'... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Turn on auth_debug and auth_verbose and see what it says. >>>>>>>>>>> >>>>>>>>>>> Aki >>>>>>>>> Also you can set auth_username_format = %Ln to force usernames >>>>>>>>> into lowercase without domain. >>>>>>>>> >>>>>>>>> Aki >> -- >> WBR, Korneechev Evgeniy >> BaseALT/ALTLinux Team > -- > WBR, Korneechev Evgeniy > BaseALT/ALTLinux Team > > > ------------------------------ > > Message: 3 > Date: Mon, 11 Sep 2017 14:51:13 +0300 > From: Aki Tuomi <aki.tuomi(a)dovecot.fi> > To: dovecot(a)dovecot.org > Subject: Re: Per-user quota (passwd) > Message-ID: <7e86447f-10e6-51a3-ce8a-3c4c8261bac1(a)dovecot.fi> > Content-Type: text/plain; charset=utf-8 > > Hi! > Just so you know, autocreate/autosubscribe is deprecated, you should > use > > namespace { > mailbox INBOX { > auto = subscribe > } > } > > can you run > > doveadm user administrator(a)email.dom > > to verify that mail_home gets set correctly? > > Aki > > On 11.09.2017 14:48, Evgeniy Korneechev wrote: >> Hi. >> But there is one problem... >> >> protocol lda { >> mail_plugins = " quota autocreate sieve quota" >> plugin { >> quota = dict:user::file:/var/vmail/glu_vrem/%u/.quotausage >> } >> } >> protocol imap { >> mail_plugins = " quota autocreate autocreate imap_quota" >> plugin { >> autocreate = INBOX >> autocreate2 = Sent >> autocreate3 = Trash >> autocreate4 = Drafts >> autocreate5 = Junk >> autosubscribe = INBOX >> autosubscribe2 = Sent >> autosubscribe3 = Trash >> autosubscribe4 = Drafts >> autosubscribe5 = Junk >> quota = dict:user::file:/var/vmail/glu_vrem/%u/.quotausage >> } >> } >> >>> Users with non-standard quota in passwd-file: >>>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/admi >>>>>>>>> nistrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/hom >>>>>>>>> e/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>> Others from passwd. >> >> Files ".quotausage" are created in different directories: >> /var/vmail/glu_vrem/administrator\DOM/.quotausage >> /var/vmail/glu_vrem/administrator(a)email.dom/.quotausage >> And must in the folder "/var/vmail/glu_vrem/administrator" >> >> How fix it? >> >> >> ----- ???????? ????????? ----- >>> ??: "Evgeniy Korneechev" <ekorneechev(a)altlinux.org> >>> ????: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>> ?????: "dovecot" <dovecot(a)dovecot.org> >>> ????????????: ???????, 30 ???? 2017 ? 10:39:16 >>> ????: Re: Per-user quota (passwd) >>> Our solution: >>> userdb { >>> args = /etc/imap.passwd >>> driver = passwd-file >>> override_fields = home=/var/vmail/glu_vrem/%u } userdb { driver = >>> passwd override_fields = home=/var/vmail/glu_vrem/%u } >>> >>> Users with non-standard quota in passwd-file: >>>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/admi >>>>>>>>> nistrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/hom >>>>>>>>> e/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>> Others from passwd. >>> >>> Its works! Thanks. >>> >>> >>> ----- ???????? ????????? ----- >>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>> ????????????: ???????, 29 ???? 2017 ? 14:40:44 >>>> ????: Re: Per-user quota (passwd) >>>> Oh you have multiple db's, I missed that. >>>> >>>> Remove auth_username_format, and instead >>>> >>>> userdb { >>>> args = /etc/imap.passwd username_format=%Ln driver = passwd-file >>>> override_fields = home=/var/vmail/glu_vrem/%u } >>>> >>>> On 29.06.2017 14:35, Evgeniy Korneechev wrote: >>>>> with auth_username_format = %Ln: >>>>> >>>>> Jun 28 14:43:41 auth: Debug: master in: USER 1 iivanov.ia(a)example.com >>>>> service=lda >>>>> Jun 28 14:43:41 auth-worker(18369): Debug: passwd(iivanov.ia): >>>>> lookup Jun 28 14:43:41 auth-worker(18369): Info: >>>>> passwd(iivanov.ia): unknown user - trying the next userdb Jun 28 >>>>> 14:43:41 auth-worker(18369): Debug: sql(iivanov.ia): SELECT email >>>>> as user, maildir as home, CONCAT('maildir:', maildir, '/Maildir') >>>>> as mail, uid, gid, \ >>>>> CONCAT('*:storage=', quota, 'B') AS quota_rule, CONCAT(maildir, '/.sieve') as >>>>> sieve FROM mail_user WHERE (login = 'iivanov.ia' OR email = >>>>> 'iivanov.ia') Jun 28 14:43:41 auth-worker(18369): Info: >>>>> sql(iivanov.ia): unknown user >>>>> >>>>> Maybe %Lu? >>>>> >>>>> ----- ???????? ????????? ----- >>>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>>> ????????????: ???????, 29 ???? 2017 ? 14:10:07 >>>>>> ????: Re: Per-user quota (passwd) Yes. >>>>>> >>>>>> Aki >>>>>> >>>>>> On 29.06.2017 14:07, Evgeniy Korneechev wrote: >>>>>>> And if such a user: >>>>>>> email (from AD) = ivanov.ia(a)example.com login (from AD), %n = >>>>>>> iivanov %d = DOM %u = iivanov@DOM >>>>>>> >>>>>>> ? >>>>>>> >>>>>>> ----- ???????? ????????? ----- >>>>>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>>>>> ????????????: ???????, 29 ???? 2017 ? 13:59:05 >>>>>>>> ????: Re: Per-user quota (passwd) or use, as I indicated >>>>>>>> before, auth_username_format = %Ln >>>>>>>> >>>>>>>> Aki >>>>>>>> >>>>>>>> >>>>>>>> On 29.06.2017 13:58, Evgeniy Korneechev wrote: >>>>>>>>> Hi! >>>>>>>>> workaround: >>>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/admi >>>>>>>>> nistrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/hom >>>>>>>>> e/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>>> >>>>>>>>> But this is not a solution for 1000 users ... >>>>>>>>> Maybe is there extra field >>>>>>>>> "userdb_mail=administrator(a)email.dom" for email to passwd-file? >>>>>>>>> >>>>>>>>> ----- ???????? ????????? ----- >>>>>>>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>>>>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>>>>>>> ????????????: ?????, 28 ???? 2017 ? 12:40:48 >>>>>>>>>> ????: Re: Per-user quota (passwd) On 28.06.2017 12:36, Aki >>>>>>>>>> Tuomi wrote: >>>>>>>>>>> On 28.06.2017 12:25, Evgeniy Korneechev wrote: >>>>>>>>>>>> Hello! >>>>>>>>>>>> We have passwd=pam, userdb=passwd. >>>>>>>>>>>> passdb { >>>>>>>>>>>> driver = pam #server was entered domain Active Directory >>>>>>>>>>>> } userdb { >>>>>>>>>>>> driver = passwd >>>>>>>>>>>> override_fields = home=/var/vmail/glu_vrem/%u } >>>>>>>>>>>> >>>>>>>>>>>> How can i use per-user quota? Only passwd-file? >>>>>>>>>>>> >>>>>>>>>>>> I tried: >>>>>>>>>>>> userdb { >>>>>>>>>>>> args = /etc/imap.passwd >>>>>>>>>>>> driver = passwd-file >>>>>>>>>>>> override_fields = home=/var/vmail/glu_vrem/%u } >>>>>>>>>>>> /etc/imap.passwd: >>>>>>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/a >>>>>>>>>>>> dministrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>>>>>> >>>>>>>>>>>> Authentication and quota - now OK. But doesn't work sending >>>>>>>>>>>> and receiving mail... >>>>>>>>>>>> postfix say 'Unknown user'... >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Turn on auth_debug and auth_verbose and see what it says. >>>>>>>>>>>> >>>>>>>>>>>> Aki >>>>>>>>>> Also you can set auth_username_format = %Ln to force >>>>>>>>>> usernames into lowercase without domain. >>>>>>>>>> >>>>>>>>>> Aki >>> -- >>> WBR, Korneechev Evgeniy >>> BaseALT/ALTLinux Team > > > ------------------------------ > > Message: 4 > Date: Mon, 11 Sep 2017 14:56:28 +0200 > From: "Nagy, Attila" <bra(a)fsn.hu> > To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, dovecot(a)dovecot.org > Subject: Re: Is it possible to disable pipelining in imapc? > Message-ID: <a6ced659-fa75-60c9-01f7-bfb36e826466(a)fsn.hu> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 09/11/2017 12:12 PM, Aki Tuomi wrote: >> Is there some reason you can't use normal proxy instead of imap backend? >> That is,return proxy, host=imap_backend, port=1430? There seems to be >> no pipeline setting currently for imapc in v2.2. >> > Yes, because it's a dumb IMAP server, which doesn't implement a lot of > things, like SEARCH, FETCH BODYSTRUCTURE and similar. > Dovecot is used as a smart proxy, which makes it possible to use it as > a fully featured IMAP server. > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > https://dovecot.org/mailman/listinfo/dovecot > > ------------------------------ > > End of dovecot Digest, Vol 173, Issue 28 > ****************************************

2 1

RE: dovecot Digest, Vol 173, Issue 28 (INTERNAL)
by Arvid.Eikas＠telenor.com 12 Sep '17

12 Sep '17

Hi, It is quite easy. I use a client (thunderbird or windows live mail) set it up to use starttls on standard port 110. Logon and just do a list on the mailbox. The fatal error occurred when I logoff. Arvid -----Original Message----- From: dovecot [mailto:dovecot-bounces@dovecot.org] On Behalf Of dovecot-request(a)dovecot.org Sent: 11. september 2017 14:57 To: dovecot(a)dovecot.org Subject: dovecot Digest, Vol 173, Issue 28 Send dovecot mailing list submissions to dovecot(a)dovecot.org To subscribe or unsubscribe via the World Wide Web, visit https://dovecot.org/mailman/listinfo/dovecot or, via email, send a message with subject or body 'help' to dovecot-request(a)dovecot.org You can reach the person managing the list at dovecot-owner(a)dovecot.org When replying, please edit your Subject line so it is more specific than "Re: Contents of dovecot digest..." Today's Topics: 1. Re: pop3-login core dump when using TLSSTART on version dovecot-2.2.32 (INTERNAL) (Aki Tuomi) 2. Re: Per-user quota (passwd) (Evgeniy Korneechev) 3. Re: Per-user quota (passwd) (Aki Tuomi) 4. Re: Is it possible to disable pipelining in imapc? (Nagy, Attila) ---------------------------------------------------------------------- Message: 1 Date: Mon, 11 Sep 2017 13:57:19 +0300 From: Aki Tuomi <aki.tuomi(a)dovecot.fi> To: dovecot(a)dovecot.org Subject: Re: pop3-login core dump when using TLSSTART on version dovecot-2.2.32 (INTERNAL) Message-ID: <cd450054-53c4-2f84-eba7-7ce602c26892(a)dovecot.fi> Content-Type: text/plain; charset=utf-8 Can you outline the exact steps you perform to get this? Aki On 11.09.2017 13:42, Arvid.Eikas(a)telenor.com wrote: > Hi, > > I switched back to 2.2.27 with the same config that I am using for 2.2.32 and it work fine. > > Sep 11 11:49:37 imap-login: Info: Login: user=<viboge>, method=PLAIN, > rip=88.89.118.45, lip=148.123.160.116, mpid=18709, TLS, > session=<v7o22OZYrsdYWXYt> Sep 11 11:49:40 imap(mailuser) Session-ID > v7o22OZYrsdYWXYt RemoteIP 88.89.118.45 Maildir > /var/nextmail/nfs2.flex14/49/79/841 Info: Logged out in=4518 > out=273720 deleted 0 expunged 0 trashed 0 Sep 11 11:49:40 imap-login: > Debug: SSL alert: close notify [88.89.118.45] > > How could I proceed? Any clue? It is quite annoying to see this entry in the log for each session. > > Arvid > > > > > -----Original Message----- > From: Aki Tuomi [mailto:aki.tuomi@dovecot.fi] > Sent: 11. september 2017 09:18 > To: Eik?s Arvid; dovecot(a)dovecot.org > Subject: Re: pop3-login core dump when using TLSSTART on version > dovecot-2.2.32 (INTERNAL) > > Hi! > > I tried to reproduce this problem with dovecot-2.2.32 and OpenSSL 1.0.1k and was not able to. I enabled -DREF_CHECK on OpenSSL, but to no avail, the process did not crash. Is there something else you've done? > > Aki > > > On 11.09.2017 08:07, Arvid.Eikas(a)telenor.com wrote: >> Hi, >> >> Here is the gdb output. >> >> Arvid >> >> GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7 Copyright (C) >> 2013 Free Software Foundation, Inc. >> License GPLv3+: GNU GPL version 3 or later >> <http://gnu.org/licenses/gpl.html> >> This is free software: you are free to change and redistribute it. >> There is NO WARRANTY, to the extent permitted by law. Type "show copying" >> and "show warranty" for details. >> This GDB was configured as "x86_64-redhat-linux-gnu". >> For bug reporting instructions, please see: >> <http://www.gnu.org/software/gdb/bugs/>... >> Reading symbols from /local/misc/mail/dovecot-32/libexec/dovecot/pop3-login...done. >> [New LWP 15894] >> Core was generated by `dovecot-test/pop3-login'. >> Program terminated with signal 6, Aborted. >> #0 0x00007ff0bd9cf1d7 in raise () from /lib64/libc.so.6 Missing >> separate debuginfos, use: debuginfo-install >> glibc-2.17-157.el7_3.1.x86_64 >> (gdb) bt full >> #0 0x00007ff0bd9cf1d7 in raise () from /lib64/libc.so.6 No symbol >> table info available. >> #1 0x00007ff0bd9d08c8 in abort () from /lib64/libc.so.6 No symbol >> table info available. >> #2 0x00007ff0bd3c0f2f in engine_unlocked_finish (e=0x1c51c60, unlock_for_handlers=1) at eng_init.c:115 >> to_return = 1 >> #3 0x00007ff0bd3c1064 in ENGINE_finish (e=0x1c51c60) at eng_init.c:150 >> to_return = 1 >> #4 0x00007ff0be0f9300 in ssl_proxy_deinit () from >> /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 >> No symbol table info available. >> #5 0x00007ff0be0f4472 in main_deinit () from >> /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 >> No symbol table info available. >> #6 0x00007ff0be0f479f in login_binary_run () from >> /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 >> No symbol table info available. >> #7 0x00000000004032da in main (argc=1, argv=0x7ffe3059f3f8) at >> client.c:356 No locals. >> >> >> >> -----Original Message----- >> From: Aki Tuomi [mailto:aki.tuomi@dovecot.fi] >> Sent: 8. september 2017 14:08 >> To: Eik?s Arvid; dovecot(a)dovecot.org >> Subject: Re: pop3-login core dump when using TLSSTART on version >> dovecot-2.2.32 (OPEN) >> >> I assume you mean STARTTLS. Can you provide gdb /path/to/bin /path/to/core and provide output of bt full? >> >> Aki >> >> >> On 08.09.2017 15:01, Arvid.Eikas(a)telenor.com wrote: >>> Hi, >>> >>> Pop3-login are CORE-dumping when I log on with TLSSTART, I believe the same will happen with imap-logon to, but I have not tested it yet. >>> The TLS session is coming up and it works fine until I log off, then it's core dump. Open sslvesrion is openssl-1.0.2k. >>> We ran dovecot-2.2.27 before we upgraded to dovecote-2.2.32, and >>> that seems to work fine. (not core dumping) >>> >>> >>> Arvid >>> >>> >>> LOG >>> Sep 05 14:27:34 pop3-login: Debug: SSL: elliptic curve secp384r1 >>> will be used for ECDH and ECDHE key exchanges Sep 05 14:30:30 pop3-login: >>> Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE >>> key exchanges Sep 05 14:30:30 pop3-login: Debug: SSL: elliptic curve >>> secp384r1 will be used for ECDH and ECDHE key exchanges Sep 05 >>> 14:30:42 pop3-login: Debug: SSL: elliptic curve secp384r1 will be >>> used for ECDH and ECDHE key exchanges Sep 05 14:30:42 pop3-login: Debug: >>> SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key >>> exchanges Sep 05 14:30:50 pop3-login: Info: Login: user=<tstrand>, >>> method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=18361, secured, >>> session=<65m8ZXBYtpN/AAAB> Sep 05 14:30:50 pop3-login: Error: >>> ENGINE_finish, bad functional reference count Sep 05 14:30:50 >>> pop3-login: Fatal: master: service(pop3-login): child 18359 killed >>> with signal 6 (core dumped) >>> >>> >>> >>> >>> >>> >>> From ./crypto/engine/eng_init.c >>> >>> ......... >>> int engine_unlocked_finish(ENGINE *e, int unlock_for_handlers) { >>> int to_return = 1; >>> >>> /* >>> * Reduce the functional reference count here so if it's the terminating >>> * case, we can release the lock safely and call the finish() handler >>> * without risk of a race. We get a race if we leave the count until >>> * after and something else is calling "finish" at the same time - >>> * there's a chance that both threads will together take the count from 2 >>> * to 0 without either calling finish(). >>> */ >>> e->funct_ref--; >>> engine_ref_debug(e, 1, -1); >>> if ((e->funct_ref == 0) && e->finish) { >>> if (unlock_for_handlers) >>> CRYPTO_w_unlock(CRYPTO_LOCK_ENGINE); >>> to_return = e->finish(e); >>> if (unlock_for_handlers) >>> CRYPTO_w_lock(CRYPTO_LOCK_ENGINE); >>> if (!to_return) >>> return 0; >>> } >>> #ifdef REF_CHECK >>> if (e->funct_ref < 0) { >>> fprintf(stderr, "ENGINE_finish, bad functional reference count\n"); >>> abort(); >>> >>> ......... >>> >>> /* The API (locked) version of "finish" */ int ENGINE_finish(ENGINE >>> *e) { >>> int to_return = 1; >>> >>> if (e == NULL) { >>> ENGINEerr(ENGINE_F_ENGINE_FINISH, ERR_R_PASSED_NULL_PARAMETER); >>> return 0; >>> } >>> CRYPTO_w_lock(CRYPTO_LOCK_ENGINE); >>> to_return = engine_unlocked_finish(e, 1); >>> CRYPTO_w_unlock(CRYPTO_LOCK_ENGINE); >>> if (!to_return) { >>> ENGINEerr(ENGINE_F_ENGINE_FINISH, ENGINE_R_FINISH_FAILED); >>> return 0; >>> } >>> return to_return; >>> } > ------------------------------ Message: 2 Date: Mon, 11 Sep 2017 14:48:47 +0300 (MSK) From: Evgeniy Korneechev <ekorneechev(a)altlinux.org> To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Cc: dovecot <dovecot(a)dovecot.org> Subject: Re: Per-user quota (passwd) Message-ID: <2046000051.747964.1505130527842.JavaMail.zimbra(a)remotesystems.ru> Content-Type: text/plain; charset=utf-8 Hi. But there is one problem... protocol lda { mail_plugins = " quota autocreate sieve quota" plugin { quota = dict:user::file:/var/vmail/glu_vrem/%u/.quotausage } } protocol imap { mail_plugins = " quota autocreate autocreate imap_quota" plugin { autocreate = INBOX autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autocreate5 = Junk autosubscribe = INBOX autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts autosubscribe5 = Junk quota = dict:user::file:/var/vmail/glu_vrem/%u/.quotausage } } > Users with non-standard quota in passwd-file: >>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/admini >>>>>>> strator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/home/ >>>>>>> DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir > > Others from passwd. Files ".quotausage" are created in different directories: /var/vmail/glu_vrem/administrator\DOM/.quotausage /var/vmail/glu_vrem/administrator(a)email.dom/.quotausage And must in the folder "/var/vmail/glu_vrem/administrator" How fix it? ----- ???????? ????????? ----- > ??: "Evgeniy Korneechev" <ekorneechev(a)altlinux.org> > ????: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> > ?????: "dovecot" <dovecot(a)dovecot.org> > ????????????: ???????, 30 ???? 2017 ? 10:39:16 > ????: Re: Per-user quota (passwd) > Our solution: > userdb { > args = /etc/imap.passwd > driver = passwd-file > override_fields = home=/var/vmail/glu_vrem/%u } userdb { driver = > passwd override_fields = home=/var/vmail/glu_vrem/%u } > > Users with non-standard quota in passwd-file: >>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/admini >>>>>>> strator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/home/ >>>>>>> DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir > > Others from passwd. > > Its works! Thanks. > > > ----- ???????? ????????? ----- >> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >> ????: "dovecot" <dovecot(a)dovecot.org> >> ????????????: ???????, 29 ???? 2017 ? 14:40:44 >> ????: Re: Per-user quota (passwd) > >> Oh you have multiple db's, I missed that. >> >> Remove auth_username_format, and instead >> >> userdb { >> args = /etc/imap.passwd username_format=%Ln driver = passwd-file >> override_fields = home=/var/vmail/glu_vrem/%u } >> >> On 29.06.2017 14:35, Evgeniy Korneechev wrote: >>> with auth_username_format = %Ln: >>> >>> Jun 28 14:43:41 auth: Debug: master in: USER 1 iivanov.ia(a)example.com >>> service=lda >>> Jun 28 14:43:41 auth-worker(18369): Debug: passwd(iivanov.ia): >>> lookup Jun 28 14:43:41 auth-worker(18369): Info: passwd(iivanov.ia): >>> unknown user - trying the next userdb Jun 28 14:43:41 >>> auth-worker(18369): Debug: sql(iivanov.ia): SELECT email as user, >>> maildir as home, CONCAT('maildir:', maildir, '/Maildir') as mail, >>> uid, gid, \ >>> CONCAT('*:storage=', quota, 'B') AS quota_rule, CONCAT(maildir, '/.sieve') as >>> sieve FROM mail_user WHERE (login = 'iivanov.ia' OR email = >>> 'iivanov.ia') Jun 28 14:43:41 auth-worker(18369): Info: >>> sql(iivanov.ia): unknown user >>> >>> Maybe %Lu? >>> >>> ----- ???????? ????????? ----- >>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>> ????????????: ???????, 29 ???? 2017 ? 14:10:07 >>>> ????: Re: Per-user quota (passwd) >>>> Yes. >>>> >>>> Aki >>>> >>>> On 29.06.2017 14:07, Evgeniy Korneechev wrote: >>>>> And if such a user: >>>>> email (from AD) = ivanov.ia(a)example.com login (from AD), %n = >>>>> iivanov %d = DOM %u = iivanov@DOM >>>>> >>>>> ? >>>>> >>>>> ----- ???????? ????????? ----- >>>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>>> ????????????: ???????, 29 ???? 2017 ? 13:59:05 >>>>>> ????: Re: Per-user quota (passwd) or use, as I indicated before, >>>>>> auth_username_format = %Ln >>>>>> >>>>>> Aki >>>>>> >>>>>> >>>>>> On 29.06.2017 13:58, Evgeniy Korneechev wrote: >>>>>>> Hi! >>>>>>> workaround: >>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/admini >>>>>>> strator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/home/ >>>>>>> DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>> >>>>>>> But this is not a solution for 1000 users ... >>>>>>> Maybe is there extra field "userdb_mail=administrator(a)email.dom" >>>>>>> for email to passwd-file? >>>>>>> >>>>>>> ----- ???????? ????????? ----- >>>>>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>>>>> ????????????: ?????, 28 ???? 2017 ? 12:40:48 >>>>>>>> ????: Re: Per-user quota (passwd) On 28.06.2017 12:36, Aki >>>>>>>> Tuomi wrote: >>>>>>>>> On 28.06.2017 12:25, Evgeniy Korneechev wrote: >>>>>>>>>> Hello! >>>>>>>>>> We have passwd=pam, userdb=passwd. >>>>>>>>>> passdb { >>>>>>>>>> driver = pam #server was entered domain Active Directory } >>>>>>>>>> userdb { >>>>>>>>>> driver = passwd >>>>>>>>>> override_fields = home=/var/vmail/glu_vrem/%u } >>>>>>>>>> >>>>>>>>>> How can i use per-user quota? Only passwd-file? >>>>>>>>>> >>>>>>>>>> I tried: >>>>>>>>>> userdb { >>>>>>>>>> args = /etc/imap.passwd >>>>>>>>>> driver = passwd-file >>>>>>>>>> override_fields = home=/var/vmail/glu_vrem/%u } >>>>>>>>>> /etc/imap.passwd: >>>>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/adm >>>>>>>>>> inistrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>>>> >>>>>>>>>> Authentication and quota - now OK. But doesn't work sending >>>>>>>>>> and receiving mail... >>>>>>>>>> postfix say 'Unknown user'... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Turn on auth_debug and auth_verbose and see what it says. >>>>>>>>>> >>>>>>>>>> Aki >>>>>>>> Also you can set auth_username_format = %Ln to force usernames >>>>>>>> into lowercase without domain. >>>>>>>> >> >>>>>> Aki > > -- > WBR, Korneechev Evgeniy > BaseALT/ALTLinux Team -- WBR, Korneechev Evgeniy BaseALT/ALTLinux Team ------------------------------ Message: 3 Date: Mon, 11 Sep 2017 14:51:13 +0300 From: Aki Tuomi <aki.tuomi(a)dovecot.fi> To: dovecot(a)dovecot.org Subject: Re: Per-user quota (passwd) Message-ID: <7e86447f-10e6-51a3-ce8a-3c4c8261bac1(a)dovecot.fi> Content-Type: text/plain; charset=utf-8 Hi! Just so you know, autocreate/autosubscribe is deprecated, you should use namespace { mailbox INBOX { auto = subscribe } } can you run doveadm user administrator(a)email.dom to verify that mail_home gets set correctly? Aki On 11.09.2017 14:48, Evgeniy Korneechev wrote: > Hi. > But there is one problem... > > protocol lda { > mail_plugins = " quota autocreate sieve quota" > plugin { > quota = dict:user::file:/var/vmail/glu_vrem/%u/.quotausage > } > } > protocol imap { > mail_plugins = " quota autocreate autocreate imap_quota" > plugin { > autocreate = INBOX > autocreate2 = Sent > autocreate3 = Trash > autocreate4 = Drafts > autocreate5 = Junk > autosubscribe = INBOX > autosubscribe2 = Sent > autosubscribe3 = Trash > autosubscribe4 = Drafts > autosubscribe5 = Junk > quota = dict:user::file:/var/vmail/glu_vrem/%u/.quotausage > } > } > >> Users with non-standard quota in passwd-file: >>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/home/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >> Others from passwd. > > > Files ".quotausage" are created in different directories: > /var/vmail/glu_vrem/administrator\DOM/.quotausage > /var/vmail/glu_vrem/administrator(a)email.dom/.quotausage > And must in the folder "/var/vmail/glu_vrem/administrator" > > How fix it? > > > ----- ???????? ????????? ----- >> ??: "Evgeniy Korneechev" <ekorneechev(a)altlinux.org> >> ????: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >> ?????: "dovecot" <dovecot(a)dovecot.org> >> ????????????: ???????, 30 ???? 2017 ? 10:39:16 >> ????: Re: Per-user quota (passwd) >> Our solution: >> userdb { >> args = /etc/imap.passwd >> driver = passwd-file >> override_fields = home=/var/vmail/glu_vrem/%u >> } >> userdb { >> driver = passwd >> override_fields = home=/var/vmail/glu_vrem/%u >> } >> >> Users with non-standard quota in passwd-file: >>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/home/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >> Others from passwd. >> >> Its works! Thanks. >> >> >> ----- ???????? ????????? ----- >>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>> ????: "dovecot" <dovecot(a)dovecot.org> >>> ????????????: ???????, 29 ???? 2017 ? 14:40:44 >>> ????: Re: Per-user quota (passwd) >>> Oh you have multiple db's, I missed that. >>> >>> Remove auth_username_format, and instead >>> >>> userdb { >>> args = /etc/imap.passwd username_format=%Ln >>> driver = passwd-file >>> override_fields = home=/var/vmail/glu_vrem/%u >>> } >>> >>> On 29.06.2017 14:35, Evgeniy Korneechev wrote: >>>> with auth_username_format = %Ln: >>>> >>>> Jun 28 14:43:41 auth: Debug: master in: USER 1 iivanov.ia(a)example.com >>>> service=lda >>>> Jun 28 14:43:41 auth-worker(18369): Debug: passwd(iivanov.ia): lookup >>>> Jun 28 14:43:41 auth-worker(18369): Info: passwd(iivanov.ia): unknown user - >>>> trying the next userdb >>>> Jun 28 14:43:41 auth-worker(18369): Debug: sql(iivanov.ia): SELECT email as >>>> user, maildir as home, CONCAT('maildir:', maildir, '/Maildir') as mail, uid, >>>> gid, \ >>>> CONCAT('*:storage=', quota, 'B') AS quota_rule, CONCAT(maildir, '/.sieve') as >>>> sieve FROM mail_user WHERE (login = 'iivanov.ia' OR email = 'iivanov.ia') >>>> Jun 28 14:43:41 auth-worker(18369): Info: sql(iivanov.ia): unknown user >>>> >>>> Maybe %Lu? >>>> >>>> ----- ???????? ????????? ----- >>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>> ????????????: ???????, 29 ???? 2017 ? 14:10:07 >>>>> ????: Re: Per-user quota (passwd) >>>>> Yes. >>>>> >>>>> Aki >>>>> >>>>> On 29.06.2017 14:07, Evgeniy Korneechev wrote: >>>>>> And if such a user: >>>>>> email (from AD) = ivanov.ia(a)example.com >>>>>> login (from AD), %n = iivanov >>>>>> %d = DOM >>>>>> %u = iivanov@DOM >>>>>> >>>>>> ? >>>>>> >>>>>> ----- ???????? ????????? ----- >>>>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>>>> ????????????: ???????, 29 ???? 2017 ? 13:59:05 >>>>>>> ????: Re: Per-user quota (passwd) >>>>>>> or use, as I indicated before, auth_username_format = %Ln >>>>>>> >>>>>>> Aki >>>>>>> >>>>>>> >>>>>>> On 29.06.2017 13:58, Evgeniy Korneechev wrote: >>>>>>>> Hi! >>>>>>>> workaround: >>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>> administrator@email.dom:*:95400500:95400513:Administrator:/home/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>> userdb_mail=maildir:/var/vmail/glu_vrem/administrator/Maildir >>>>>>>> >>>>>>>> But this is not a solution for 1000 users ... >>>>>>>> Maybe is there extra field "userdb_mail=administrator(a)email.dom" for email to >>>>>>>> passwd-file? >>>>>>>> >>>>>>>> ----- ???????? ????????? ----- >>>>>>>>> ??: "Aki Tuomi" <aki.tuomi(a)dovecot.fi> >>>>>>>>> ????: "dovecot" <dovecot(a)dovecot.org> >>>>>>>>> ????????????: ?????, 28 ???? 2017 ? 12:40:48 >>>>>>>>> ????: Re: Per-user quota (passwd) >>>>>>>>> On 28.06.2017 12:36, Aki Tuomi wrote: >>>>>>>>>> On 28.06.2017 12:25, Evgeniy Korneechev wrote: >>>>>>>>>>> Hello! >>>>>>>>>>> We have passwd=pam, userdb=passwd. >>>>>>>>>>> passdb { >>>>>>>>>>> driver = pam #server was entered domain Active Directory >>>>>>>>>>> } >>>>>>>>>>> userdb { >>>>>>>>>>> driver = passwd >>>>>>>>>>> override_fields = home=/var/vmail/glu_vrem/%u >>>>>>>>>>> } >>>>>>>>>>> >>>>>>>>>>> How can i use per-user quota? Only passwd-file? >>>>>>>>>>> >>>>>>>>>>> I tried: >>>>>>>>>>> userdb { >>>>>>>>>>> args = /etc/imap.passwd >>>>>>>>>>> driver = passwd-file >>>>>>>>>>> override_fields = home=/var/vmail/glu_vrem/%u >>>>>>>>>>> } >>>>>>>>>>> /etc/imap.passwd: >>>>>>>>>>> administrator:*:95400500:95400513:Administrator:/home/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G >>>>>>>>>>> >>>>>>>>>>> Authentication and quota - now OK. But doesn't work sending and receiving >>>>>>>>>>> mail... >>>>>>>>>>> postfix say 'Unknown user'... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Turn on auth_debug and auth_verbose and see what it says. >>>>>>>>>>> >>>>>>>>>>> Aki >>>>>>>>> Also you can set auth_username_format = %Ln to force usernames into >>>>>>>>> lowercase without domain. >>>>>>>>> >>>>>>>>> Aki >> -- >> WBR, Korneechev Evgeniy >> BaseALT/ALTLinux Team ------------------------------ Message: 4 Date: Mon, 11 Sep 2017 14:56:28 +0200 From: "Nagy, Attila" <bra(a)fsn.hu> To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, dovecot(a)dovecot.org Subject: Re: Is it possible to disable pipelining in imapc? Message-ID: <a6ced659-fa75-60c9-01f7-bfb36e826466(a)fsn.hu> Content-Type: text/plain; charset=utf-8; format=flowed On 09/11/2017 12:12 PM, Aki Tuomi wrote: > Is there some reason you can't use normal proxy instead of imap backend? > That is,return proxy, host=imap_backend, port=1430? There seems to be no > pipeline setting currently for imapc in v2.2. > Yes, because it's a dumb IMAP server, which doesn't implement a lot of things, like SEARCH, FETCH BODYSTRUCTURE and similar. Dovecot is used as a smart proxy, which makes it possible to use it as a fully featured IMAP server. ------------------------------ Subject: Digest Footer _______________________________________________ dovecot mailing list dovecot(a)dovecot.org https://dovecot.org/mailman/listinfo/dovecot ------------------------------ End of dovecot Digest, Vol 173, Issue 28 ****************************************

2 1

Moving emails tagged as spam to the Junk folder
by Mika Leppänen 12 Sep '17

12 Sep '17

I am running Ubuntu 16.04. I am following this guide: https://wiki2.dovecot.org/HowTo/AntispamWithSieve. At the end when I try to compile the .sieve files, I get this error: sievec(root): Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib/dovecot/modules/sieve. Does anyone know about this? I have dovecot-sieve installed and I'm using Postfix and Spamassassin. -- Mika Leppänen -- mika.leppanen(a)iki.fi

3 2

Re: Share Website certificate with SSL/STL Dovecot IMAP and Postifix SMTP
by Joseph Tam 11 Sep '17

11 Sep '17

Marco Marco writes writes: > I've bought a certificate from the authority for my website to use to > access in https mode. > > Is it possible to share the same pairs to authenticate the emails sent > by postfix and Dovecot in order to avoid that client as Hotmail.it or > Gmail intercept these as Spam? By "same pairs", I assume you mean key and certificate. Yes, just as long as you use the same Subject for all your services (e.g. "mail.yourdomain.com") or you have purchased a wildcard certificate e.g. "*.yourdomain.com" to authenticate "webmail.yourdomain.com", "imap.yourdomain.com", "smtp.yourdomain.com", etc.) Certificates do not authenticate services or protocols, but server names (typically). Joseph Tam <jtam.home(a)gmail.com>

1 0

Returning error response to the client from passdb (with dict protocol)
by Nagy, Attila 11 Sep '17

11 Sep '17

Hi, When using a passdb with (UNIX socket) dict protocol, I can return a JSON with fields. When I want to deny the user, I can send a JSON like this: {"fail":true} which yields (on POP) a friendly -ERR [AUTH] Authentication failed. Is it possible to return the response text itself? I want to tell the user why the authentication has failed.

1 0

Fail2ban 'Password mismatch' regex
by James Brown 11 Sep '17

11 Sep '17

I have turned on 'auth_debug_passwords=yes’ in dovecot.conf. I’m trying to get Fail2ban to detect this log line: Sep 11 15:52:49 mail dovecot[54239]: auth-worker(10094): sql(user(a)bordo.com.au <mailto:user@bordo.com.au>,::1,<L2xqieNYeM4AAAAAAAAAAAAAAAAAAAAB>): Password mismatch (given password: 2) I’ve added it as the last line of my dovecot filter regex: failregex = ^%(__prefix_line)s(%(__pam_auth)s($dovecot:auth$)?:)?\s+authentication failure; logname=\S* uid=\S* euid=\S* tty=dovecot ruser=\S* rhost=<HOST>(\s+user=\S*)?\s*$ ^%(__prefix_line)s(pop3|imap)-login: (Info: )?(Aborted login|Disconnected)(: Inactivity)? $((auth failed, \d+ attempts)( in \d+ secs)?|tried to use (disabled|disallo$ ^%(__prefix_line)s(Info|dovecot: auth\(default$|auth-worker$\d+$): pam$\S+,<HOST>$: pam_authenticate failed: (User not known to the underlying authentication$ ^%(__prefix_line)s(auth|auth-worker$\d+$): (pam|passwd-file)$\S+,<HOST>$: unknown user\s*$ ^%(__prefix_line)s(auth|auth-worker$\d+$): Info: ldap$\S*,<HOST>,\S*$: invalid credentials\s*$ ^%(__prefix_line)sauth: Info: sql$\S+,<HOST>$: (Password mismatch|unknown user)( $(SHA1 of given password: [0-9a-f]{5,40}|given password: \w*)$)?$ Have spent ages googling and trying different variations. Does anyone have a fail2ban regex that would work on the above Dovecot log line? (Running latest versions of Dovecot and fail2ban) Many thanks, James.

3 5

Is it possible to disable pipelining in imapc?
by Nagy, Attila 11 Sep '17

11 Sep '17

Hi, I've a broken IMAP server, which doesn't support pipelining and fails on dovecot's attempt to do this ([C] is dovecot's imapc, [S] is the IMAP server): [C] 24 LOGIN "user" "pass" [S] 23 OK [C] 25 SELECT "INBOX" [C] 23 UID FETCH 2 (INTERNALDATE) [S] 25 OK [S] 23 BAD No mailbox selected Sadly, fixing the server would be a hard task, turning off pipelining in dovecot's imapc (which already supports many workarounds for different servers) could be easy... ... except I can see no place to do this in imapc (only in pop3c and imap proxy, which I guess doesn't apply here). If I'm right, may I ask for a knob for such dumb servers? Thanks,

3 13

Per-user quota (passwd)
by Evgeniy Korneechev 11 Sep '17

11 Sep '17

Hello! We have passwd=pam, userdb=passwd. passdb { driver = pam #server was entered domain Active Directory } userdb { driver = passwd override_fields = home=/var/vmail/glu_vrem/%u } How can i use per-user quota? Only passwd-file? I tried: userdb { args = /etc/imap.passwd driver = passwd-file override_fields = home=/var/vmail/glu_vrem/%u } /etc/imap.passwd: administrator:*:95400500:95400513:Administrator:/home/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G Authentication and quota - now OK. But doesn't work sending and receiving mail... postfix say 'Unknown user'... Is there "extra_field" in passwd-file for email? What generally will be advice on quotas in our case? dovecot -n: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.39-std-def-alt0.M80P.1 x86_64 ALT 8.1 Server auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_socket_path = /var/run/dovecot/auth-userdb auth_username_chars = auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot/ debug_log_path = /var/log/dovecot disable_plaintext_auth = no first_valid_gid = 502 first_valid_uid = 502 last_valid_gid = 268999999 last_valid_uid = 268999999 log_path = /var/log/dovecot login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_access_groups = vmail mail_debug = yes mail_gid = 502 mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_plugins = " quota autocreate" mail_privileged_group = vmail mail_uid = 502 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 index ihave duplicate mime foreverypart extracttext imapflags notify mbox_write_locks = fcntl namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { inbox = yes location = prefix = separator = / type = private } passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota_rule = *:storage=5G recipient_delimiter = + sieve = /etc/dovecot/sieves/default.sieve sieve_default = /etc/dovecot/sieves/default.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags sieve_max_redirects = 8 } protocols = imap pop3 lmtp sieve service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } } service imap { process_limit = 1024 vsz_limit = 256 M } service lmtp { unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 110 } } service pop3 { process_limit = 1024 } ssl_ca = </usr/share/ca-certificates/ca-bundle.crt ssl_cert = </etc/dovecot/server.crt ssl_key = # hidden, use -P to show it userdb { driver = passwd override_fields = home=/var/vmail/glu_vrem/%u } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota autocreate sieve" } protocol lda { mail_plugins = " quota autocreate sieve quota" plugin { quota = dict:user::file:/var/vmail/glu_vrem/%n/.quotausage } } protocol imap { mail_plugins = " quota autocreate autocreate imap_quota" plugin { autocreate = INBOX autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autocreate5 = Junk autosubscribe = INBOX autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts autosubscribe5 = Junk quota = dict:user::file:/var/vmail/glu_vrem/%n/.quotausage } } protocol sieve { mail_max_userip_connections = 10 managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } -- WBR, Korneechev Evgeniy BaseALT/ALTLinux Team

2 11

RE: pop3-login core dump when using TLSSTART on version dovecot-2.2.32 (INTERNAL)
by Arvid.Eikas＠telenor.com 11 Sep '17

11 Sep '17

Hi, I switched back to 2.2.27 with the same config that I am using for 2.2.32 and it work fine. Sep 11 11:49:37 imap-login: Info: Login: user=<viboge>, method=PLAIN, rip=88.89.118.45, lip=148.123.160.116, mpid=18709, TLS, session=<v7o22OZYrsdYWXYt> Sep 11 11:49:40 imap(mailuser) Session-ID v7o22OZYrsdYWXYt RemoteIP 88.89.118.45 Maildir /var/nextmail/nfs2.flex14/49/79/841 Info: Logged out in=4518 out=273720 deleted 0 expunged 0 trashed 0 Sep 11 11:49:40 imap-login: Debug: SSL alert: close notify [88.89.118.45] How could I proceed? Any clue? It is quite annoying to see this entry in the log for each session. Arvid -----Original Message----- From: Aki Tuomi [mailto:aki.tuomi@dovecot.fi] Sent: 11. september 2017 09:18 To: Eikås Arvid; dovecot(a)dovecot.org Subject: Re: pop3-login core dump when using TLSSTART on version dovecot-2.2.32 (INTERNAL) Hi! I tried to reproduce this problem with dovecot-2.2.32 and OpenSSL 1.0.1k and was not able to. I enabled -DREF_CHECK on OpenSSL, but to no avail, the process did not crash. Is there something else you've done? Aki On 11.09.2017 08:07, Arvid.Eikas(a)telenor.com wrote: > Hi, > > Here is the gdb output. > > Arvid > > GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7 Copyright (C) 2013 > Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-redhat-linux-gnu". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from /local/misc/mail/dovecot-32/libexec/dovecot/pop3-login...done. > [New LWP 15894] > Core was generated by `dovecot-test/pop3-login'. > Program terminated with signal 6, Aborted. > #0 0x00007ff0bd9cf1d7 in raise () from /lib64/libc.so.6 Missing > separate debuginfos, use: debuginfo-install > glibc-2.17-157.el7_3.1.x86_64 > (gdb) bt full > #0 0x00007ff0bd9cf1d7 in raise () from /lib64/libc.so.6 No symbol > table info available. > #1 0x00007ff0bd9d08c8 in abort () from /lib64/libc.so.6 No symbol > table info available. > #2 0x00007ff0bd3c0f2f in engine_unlocked_finish (e=0x1c51c60, unlock_for_handlers=1) at eng_init.c:115 > to_return = 1 > #3 0x00007ff0bd3c1064 in ENGINE_finish (e=0x1c51c60) at eng_init.c:150 > to_return = 1 > #4 0x00007ff0be0f9300 in ssl_proxy_deinit () from > /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 > No symbol table info available. > #5 0x00007ff0be0f4472 in main_deinit () from > /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 > No symbol table info available. > #6 0x00007ff0be0f479f in login_binary_run () from > /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 > No symbol table info available. > #7 0x00000000004032da in main (argc=1, argv=0x7ffe3059f3f8) at > client.c:356 No locals. > > > > -----Original Message----- > From: Aki Tuomi [mailto:aki.tuomi@dovecot.fi] > Sent: 8. september 2017 14:08 > To: Eikås Arvid; dovecot(a)dovecot.org > Subject: Re: pop3-login core dump when using TLSSTART on version > dovecot-2.2.32 (OPEN) > > I assume you mean STARTTLS. Can you provide gdb /path/to/bin /path/to/core and provide output of bt full? > > Aki > > > On 08.09.2017 15:01, Arvid.Eikas(a)telenor.com wrote: >> Hi, >> >> Pop3-login are CORE-dumping when I log on with TLSSTART, I believe the same will happen with imap-logon to, but I have not tested it yet. >> The TLS session is coming up and it works fine until I log off, then it's core dump. Open sslvesrion is openssl-1.0.2k. >> We ran dovecot-2.2.27 before we upgraded to dovecote-2.2.32, and that >> seems to work fine. (not core dumping) >> >> >> Arvid >> >> >> LOG >> Sep 05 14:27:34 pop3-login: Debug: SSL: elliptic curve secp384r1 will >> be used for ECDH and ECDHE key exchanges Sep 05 14:30:30 pop3-login: >> Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE >> key exchanges Sep 05 14:30:30 pop3-login: Debug: SSL: elliptic curve >> secp384r1 will be used for ECDH and ECDHE key exchanges Sep 05 >> 14:30:42 pop3-login: Debug: SSL: elliptic curve secp384r1 will be >> used for ECDH and ECDHE key exchanges Sep 05 14:30:42 pop3-login: Debug: >> SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key >> exchanges Sep 05 14:30:50 pop3-login: Info: Login: user=<tstrand>, >> method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=18361, secured, >> session=<65m8ZXBYtpN/AAAB> Sep 05 14:30:50 pop3-login: Error: >> ENGINE_finish, bad functional reference count Sep 05 14:30:50 >> pop3-login: Fatal: master: service(pop3-login): child 18359 killed >> with signal 6 (core dumped) >> >> >> >> >> >> >> From ./crypto/engine/eng_init.c >> >> ......... >> int engine_unlocked_finish(ENGINE *e, int unlock_for_handlers) { >> int to_return = 1; >> >> /* >> * Reduce the functional reference count here so if it's the terminating >> * case, we can release the lock safely and call the finish() handler >> * without risk of a race. We get a race if we leave the count until >> * after and something else is calling "finish" at the same time - >> * there's a chance that both threads will together take the count from 2 >> * to 0 without either calling finish(). >> */ >> e->funct_ref--; >> engine_ref_debug(e, 1, -1); >> if ((e->funct_ref == 0) && e->finish) { >> if (unlock_for_handlers) >> CRYPTO_w_unlock(CRYPTO_LOCK_ENGINE); >> to_return = e->finish(e); >> if (unlock_for_handlers) >> CRYPTO_w_lock(CRYPTO_LOCK_ENGINE); >> if (!to_return) >> return 0; >> } >> #ifdef REF_CHECK >> if (e->funct_ref < 0) { >> fprintf(stderr, "ENGINE_finish, bad functional reference count\n"); >> abort(); >> >> ......... >> >> /* The API (locked) version of "finish" */ int ENGINE_finish(ENGINE >> *e) { >> int to_return = 1; >> >> if (e == NULL) { >> ENGINEerr(ENGINE_F_ENGINE_FINISH, ERR_R_PASSED_NULL_PARAMETER); >> return 0; >> } >> CRYPTO_w_lock(CRYPTO_LOCK_ENGINE); >> to_return = engine_unlocked_finish(e, 1); >> CRYPTO_w_unlock(CRYPTO_LOCK_ENGINE); >> if (!to_return) { >> ENGINEerr(ENGINE_F_ENGINE_FINISH, ENGINE_R_FINISH_FAILED); >> return 0; >> } >> return to_return; >> }

2 1

doveadm expunge returns error code 68
by Florian Lohoff 11 Sep '17

11 Sep '17

Hi, i am running basically this from cron: /usr/bin/doveadm -v expunge -u * mailbox INBOX.Spam SENTBEFORE 90d /usr/bin/doveadm -v expunge -u * mailbox INBOX.Trash SENTBEFORE 90d /usr/bin/doveadm -v expunge -u * mailbox INBOX.Junk SENTBEFORE 90d Now i am experiencing that the first line e.g. expunging INBOX.Spam returns the error code 68. No syslog/Output whatsoever. I tried running with -vvv -D which gives me a lot of output (for all mailboxes) but still i am unable to pinpoint the problem. The later 2 commands return "0" as expected. Where does the error return code come from and what does 68 mean? Flo -- Florian Lohoff f(a)zz.de UTF-8 Test: The 🐈 ran after a 🐁, but the 🐁 ran away

2 3

Dovecot and Letsencrypt certs
by ＠lbutlr 11 Sep '17

11 Sep '17

So this morning at 4am I was awoken to my mail clients getting certificate errors for an expired certificate. I hopped on to the server and checked and… no, the LE certs renewed last month and are valid until November. After some moments of confusion I noticed that dovecot had been running since before the renewal, so I did a quick service dovecot restart which fixed everything. Should dovecot check for certs being refreshed? Or is this an artifact of my using symbolic links everywhere to point to the newest LE certs (which are themselves links the dehydrate script creates to point to the newest cert-1502534746.csr etc files? Should I just create a monthly cron to restart dovecot or is there something else? -- Apple broke AppleScripting signatures in Mail.app, so no random signatures.

8 14

RE: pop3-login core dump when using TLSSTART on version dovecot-2.2.32 (INTERNAL)
by Arvid.Eikas＠telenor.com 11 Sep '17

11 Sep '17

Hi, Here is the gdb output. Arvid GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /local/misc/mail/dovecot-32/libexec/dovecot/pop3-login...done. [New LWP 15894] Core was generated by `dovecot-test/pop3-login'. Program terminated with signal 6, Aborted. #0 0x00007ff0bd9cf1d7 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.17-157.el7_3.1.x86_64 (gdb) bt full #0 0x00007ff0bd9cf1d7 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x00007ff0bd9d08c8 in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x00007ff0bd3c0f2f in engine_unlocked_finish (e=0x1c51c60, unlock_for_handlers=1) at eng_init.c:115 to_return = 1 #3 0x00007ff0bd3c1064 in ENGINE_finish (e=0x1c51c60) at eng_init.c:150 to_return = 1 #4 0x00007ff0be0f9300 in ssl_proxy_deinit () from /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #5 0x00007ff0be0f4472 in main_deinit () from /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #6 0x00007ff0be0f479f in login_binary_run () from /local/nextmail/dovecot/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #7 0x00000000004032da in main (argc=1, argv=0x7ffe3059f3f8) at client.c:356 No locals. -----Original Message----- From: Aki Tuomi [mailto:aki.tuomi@dovecot.fi] Sent: 8. september 2017 14:08 To: Eikås Arvid; dovecot(a)dovecot.org Subject: Re: pop3-login core dump when using TLSSTART on version dovecot-2.2.32 (OPEN) I assume you mean STARTTLS. Can you provide gdb /path/to/bin /path/to/core and provide output of bt full? Aki On 08.09.2017 15:01, Arvid.Eikas(a)telenor.com wrote: > Hi, > > Pop3-login are CORE-dumping when I log on with TLSSTART, I believe the same will happen with imap-logon to, but I have not tested it yet. > The TLS session is coming up and it works fine until I log off, then it's core dump. Open sslvesrion is openssl-1.0.2k. > We ran dovecot-2.2.27 before we upgraded to dovecote-2.2.32, and that > seems to work fine. (not core dumping) > > > Arvid > > > LOG > Sep 05 14:27:34 pop3-login: Debug: SSL: elliptic curve secp384r1 will > be used for ECDH and ECDHE key exchanges Sep 05 14:30:30 pop3-login: > Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE > key exchanges Sep 05 14:30:30 pop3-login: Debug: SSL: elliptic curve > secp384r1 will be used for ECDH and ECDHE key exchanges Sep 05 > 14:30:42 pop3-login: Debug: SSL: elliptic curve secp384r1 will be used > for ECDH and ECDHE key exchanges Sep 05 14:30:42 pop3-login: Debug: > SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key > exchanges Sep 05 14:30:50 pop3-login: Info: Login: user=<tstrand>, > method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=18361, secured, > session=<65m8ZXBYtpN/AAAB> Sep 05 14:30:50 pop3-login: Error: > ENGINE_finish, bad functional reference count Sep 05 14:30:50 > pop3-login: Fatal: master: service(pop3-login): child 18359 killed > with signal 6 (core dumped) > > > > > > > From ./crypto/engine/eng_init.c > > ......... > int engine_unlocked_finish(ENGINE *e, int unlock_for_handlers) { > int to_return = 1; > > /* > * Reduce the functional reference count here so if it's the terminating > * case, we can release the lock safely and call the finish() handler > * without risk of a race. We get a race if we leave the count until > * after and something else is calling "finish" at the same time - > * there's a chance that both threads will together take the count from 2 > * to 0 without either calling finish(). > */ > e->funct_ref--; > engine_ref_debug(e, 1, -1); > if ((e->funct_ref == 0) && e->finish) { > if (unlock_for_handlers) > CRYPTO_w_unlock(CRYPTO_LOCK_ENGINE); > to_return = e->finish(e); > if (unlock_for_handlers) > CRYPTO_w_lock(CRYPTO_LOCK_ENGINE); > if (!to_return) > return 0; > } > #ifdef REF_CHECK > if (e->funct_ref < 0) { > fprintf(stderr, "ENGINE_finish, bad functional reference count\n"); > abort(); > > ......... > > /* The API (locked) version of "finish" */ int ENGINE_finish(ENGINE > *e) { > int to_return = 1; > > if (e == NULL) { > ENGINEerr(ENGINE_F_ENGINE_FINISH, ERR_R_PASSED_NULL_PARAMETER); > return 0; > } > CRYPTO_w_lock(CRYPTO_LOCK_ENGINE); > to_return = engine_unlocked_finish(e, 1); > CRYPTO_w_unlock(CRYPTO_LOCK_ENGINE); > if (!to_return) { > ENGINEerr(ENGINE_F_ENGINE_FINISH, ENGINE_R_FINISH_FAILED); > return 0; > } > return to_return; > }

2 1

Share Website certificate with SSL/STL Dovecot IMAP and Postifix SMTP
by Marco Marco 10 Sep '17

10 Sep '17

Hi guys, I've bought a certificate from the authority for my website to use to access in https mode. Is it possible to share the same pairs to authenticate the emails sent by postfix and Dovecot in order to avoid that client as Hotmail.it or Gmail intercept these as Spam? Thank you

2 1

Embeding a path in address extensions
by ＠lbutlr 09 Sep '17

09 Sep '17

I generate bcc backups with the pattern backups+DATE.user.domain.tld(a)myBackupDomain.tld (for example, backups+20170908.kremels.kreme.com(a)myBackupDomain.tld) This puts mail in …/.20170908.kremels.kreme.com/new What I would like to do is get the expansion to generate the following path …/.20170908/.kremels.kreme.com/new Of course the date changes everyday, but it will always be numeric if that helps. dovecot get the mail from postfix: dovecot unix - n n - - pipe flags=DRhu user=vpopmail:vchkpw argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${user}@${nexthop} -m ${extension} -a ${original_recipient} Would it make more sense (or is it even possible) to split the extension in postfix or to do something with sieve? Or is there a character I can use in the extension that tells dovecot to create a path? Even though I am using a maildir structure for the backups, this "account" never accesses the mail via a MUA, only via the command line when an admin has to restore an email, so it would be much easier to deal with this with daily subfolders. Or, maybe I make the admins use an MUA? If so, I should replace most of these .'s with dashes… -- Apple broke AppleScripting signatures in Mail.app, so no random signatures.

1 1

can't get quota working. I use static userdb driver.
by Вадим Бажов 08 Sep '17

08 Sep '17

Hi, people ! Set up global quota according to docs to 2 Mb. Send more than ten Mb on the box. Mail still getting put in the box, no bounces, no error messages in logs, nothing to prevent mail to be delivered in overflooded mailbox. quota settings are: mail_plugins = quota lmtp_rcpt_check_quota = yes quota_full_tempfail = yes protocol lmtp { postmaster_address = postmaster # required mail_plugins = $mail_plugins sieve } protocol lda { mail_plugins = $mail_plugins sieve } protocol imap { mail_plugins = $mail_plugins imap_quota } plugin { quota = maildir:"User quota" quota_rule = *:storage=10M quota_rule3 = INBOX.Trash:storage=+10%% quota_exceeded_message = "552 5.2.2 Mailbox is full" } doveconf -n is attached. # doveadm quota get Quota name Type Value Limit % "User quota" STORAGE 0 10240 0 "User quota" MESSAGE 0 - # doveadm quota get -u vadim Quota name Type Value Limit % "User quota" STORAGE 0 10240 0 "User quota" MESSAGE 0 - # du -sh /var/mail/vadim/ 23M /var/mail/vadim/ I tried to pass quota_rule as an argument to userdb, quota is being parsed, but still doesn't work. I think problem is that dovecot can't (re)calculate the actual quota on disc (cant calculate how disk space mailbox is used), despite the fact that quota limit itself is configured correctly, since dovecot shows it in log and doveconf -n. What I am dong wrong ?

4 8

EOF from net_disconnect(fd)
by Steffan Cline 08 Sep '17

08 Sep '17

I’m working on an OS project from github. There are two parts: Dovecot plugin - https://github.com/st3fan/dovecot-xaps-plugin Daemon written in Go - https://github.com/st3fan/dovecot-xaps-daemon # dovecot --version 2.2.10 Both parts worked fine on CentOS 6 but I recently rebuilt them both for CentOS 7 and have run into some errors. The plugin sends a notification over a socket to the daemon. The daemon then processes the request and returns a message to the plugin. The plugin reads the response then closes the socket and at that point, I’m running into an issue. The daemon reports the following: read unix /tmp/xapsd.sock->@: read: connection reset by peer In reading the Go language docs, it says that it will throw the first error it hits before the EOF from the socket. This led me to think that perhaps the plugin was not sending an EOF when closing the socket. I tried to write an EOF to the socket before the close but no change. Everything works between the plugin and daemon right up until the socket close. Is there a way to monitor the stream through the socket so I can see if the plugin is indeed sending the EOF? Knowing that lets me know if I need to chase down the issue in the Go daemon code. I’m no pro with C but I tried. The snippet from the plugin follows: alarm(1); { if (net_transmit(fd, str_data(req), str_len(req)) < 0) { i_error("write(%s) failed: %m", socket_path); ret = -1; } else { char res[1024]; ret = net_receive(fd, res, sizeof(res)-1); if (ret < 0) { i_error("read(%s) failed: %m", socket_path); } else { res[ret] = '\0'; if (strncmp(res, "OK ", 3) == 0) { ret = 0; } } } } alarm(0); char stx[1]; stx[0]=(char) 4; //stx[1]='\0'; if ( net_transmit(fd, stx, sizeof(stx) ) < 0 ) { i_error("Error writing EOF"); } //string_t *testEOF= t_str_new(2); //str_append(testEOF, (char*) 4); //if ( net_transmit(fd, str_data(testEOF), str_len(testEOF) ) < 0 ) { // i_error("Error writing EOF"); // } //i_close_fd(&fd); net_disconnect(fd); fd=-1; Thank you, Steffan Cline 602-793-0014

3 6

Automatic DB password hash scheme selection
by Kurt Fitzner 08 Sep '17

08 Sep '17

Hi all, Is there a way to get dovecot to recognize arbitrary password hash schemes when looking up a password in a database? I originally set up with #default_pass_scheme = MD5, and I would like to migrate to SHA512. Seeing as the scheme is actually stored in the password column along with the password in the format $_<scheme#>_$_<salt>_$_<passwordhash>_, it seems to me that dovecot should be able to look at the scheme number and simply do the right thing. If this is possible, then migrating passwords over would be much easier, since people will still be able to log in with their old MD5-hashed password and the changer can be set up to hash with the new method. Is this possible currently? Thanks, Kurt

2 2

Hide public mailboxes from some users
by Arie Peterson 08 Sep '17

08 Sep '17

Hi all, I'm trying to set up public mailboxes for a subset of my users. This is on dovecot 2.2.27. I've created a new public namespace, and the new mailboxes indeed show up for everyone. So far so good. Now I want to restrict access: these mailboxes shouldn't be visible at all except to a fixed list of users. This part I can't seem to get working. I've added acl data along these lines: ``` pubbox anyone pubbox/* anyone pubbox user=me(a)example.com lrwstipekxa pubbox/* user=me(a)example.com lrwstipekxa ``` However, other users can still see "pubbox" and its subfolders, although they can't actually view the contents. This is corroborated by some of the output of `doveadm mailbox list`: ``` # doveadm -D mailbox list -u other(a)example.com … doveadm(other(a)example.com): Debug: Namespace : type=public, prefix=pubbox/, sep=/, inbox=no, hidden=no, list=children, subscriptions=no … doveadm(other(a)example.com): Debug: Mailbox 'pubbox/Drafts' matches global ACL pattern 'pubbox/*' doveadm(other(a)example.com): Debug: Mailbox 'pubbox/Drafts' matches global ACL pattern 'pubbox/*' doveadm(other(a)example.com): Debug: acl vfile: reading file /mnt/data/mail/example.com/public/pubbox/mail/Drafts/dovecot-acl doveadm(other(a)example.com): Debug: acl: No lookup right to mailbox: pubbox/Drafts doveadm(other(a)example.com): Debug: Mailbox 'pubbox/Sent' matches global ACL pattern 'pubbox/*' doveadm(other(a)example.com): Debug: Mailbox 'pubbox/Sent' matches global ACL pattern 'pubbox/*' doveadm(other(a)example.com): Debug: acl vfile: reading file /mnt/data/mail/example.com/public/pubbox/mail/Sent/dovecot-acl doveadm(other(a)example.com): Debug: acl: No lookup right to mailbox: pubbox/Sent doveadm(other(a)example.com): Debug: Mailbox 'pubbox' matches global ACL pattern 'pubbox' doveadm(other(a)example.com): Debug: Mailbox 'pubbox' matches global ACL pattern 'pubbox' doveadm(other(a)example.com): Debug: acl vfile: reading file /mnt/data/mail/example.com/public/pubbox/mail/dovecot-acl pubbox pubbox/Drafts pubbox/Sent INBOX ``` Why do these "pubbox/*" mailboxes show up in the `mailbox list` output, even though the debug messages say that the user has no lookup right for them? `doveadm acl rights` seems to confirm that `other(a)example.com` does not have the lookup right for these mailboxes. So why do they show up in their email clients anyway? Thanks for any advice!

1 2

password reset
by ＠lbutlr 08 Sep '17

08 Sep '17

This is off topic, but I am not sure where to go. I have a local user who cannot login because of a forgotten password, so I went to reset her password with sudo passed <user> Which appears to work, asking for a new password and a confirmation. No error occurs (unless I give it unmatched passwords), but the password is not changed. if I try to change the password in the user's account (after su <user>) t requires the old password. running on FreeBSD 11.0 When I try to change the password with sudo, the timestamp on /etc/passwd gets updated but there is nothing logged to anything in /var/log/

4 6

pop3-login core dump when using TLSSTART on version dovecot-2.2.32 (OPEN)
by Arvid.Eikas＠telenor.com 08 Sep '17

08 Sep '17

Hi, Pop3-login are CORE-dumping when I log on with TLSSTART, I believe the same will happen with imap-logon to, but I have not tested it yet. The TLS session is coming up and it works fine until I log off, then it's core dump. Open sslvesrion is openssl-1.0.2k. We ran dovecot-2.2.27 before we upgraded to dovecote-2.2.32, and that seems to work fine. (not core dumping) Arvid LOG Sep 05 14:27:34 pop3-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Sep 05 14:30:30 pop3-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Sep 05 14:30:30 pop3-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Sep 05 14:30:42 pop3-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Sep 05 14:30:42 pop3-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Sep 05 14:30:50 pop3-login: Info: Login: user=<tstrand>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=18361, secured, session=<65m8ZXBYtpN/AAAB> Sep 05 14:30:50 pop3-login: Error: ENGINE_finish, bad functional reference count Sep 05 14:30:50 pop3-login: Fatal: master: service(pop3-login): child 18359 killed with signal 6 (core dumped) >From ./crypto/engine/eng_init.c ......... int engine_unlocked_finish(ENGINE *e, int unlock_for_handlers) { int to_return = 1; /* * Reduce the functional reference count here so if it's the terminating * case, we can release the lock safely and call the finish() handler * without risk of a race. We get a race if we leave the count until * after and something else is calling "finish" at the same time - * there's a chance that both threads will together take the count from 2 * to 0 without either calling finish(). */ e->funct_ref--; engine_ref_debug(e, 1, -1); if ((e->funct_ref == 0) && e->finish) { if (unlock_for_handlers) CRYPTO_w_unlock(CRYPTO_LOCK_ENGINE); to_return = e->finish(e); if (unlock_for_handlers) CRYPTO_w_lock(CRYPTO_LOCK_ENGINE); if (!to_return) return 0; } #ifdef REF_CHECK if (e->funct_ref < 0) { fprintf(stderr, "ENGINE_finish, bad functional reference count\n"); abort(); ......... /* The API (locked) version of "finish" */ int ENGINE_finish(ENGINE *e) { int to_return = 1; if (e == NULL) { ENGINEerr(ENGINE_F_ENGINE_FINISH, ERR_R_PASSED_NULL_PARAMETER); return 0; } CRYPTO_w_lock(CRYPTO_LOCK_ENGINE); to_return = engine_unlocked_finish(e, 1); CRYPTO_w_unlock(CRYPTO_LOCK_ENGINE); if (!to_return) { ENGINEerr(ENGINE_F_ENGINE_FINISH, ENGINE_R_FINISH_FAILED); return 0; } return to_return; }

2 1

Strange SASL issue
by Antoine Nguyen 07 Sep '17

07 Sep '17

Hi all, I've just upgraded my server from debian 8 to debian 9 and I now encounter a strange issue. I'm using prosody (XMPP server), configured to authenticate against dovecot using SASL and a unix socket. This setup was working fine on debian 8. Now, each time I try to connect using my XMPP client, the authentication fails and I see the following error in logs: auth: Error: BUG: Authentication client said it's PID 0 Have you ever heard about this? For information, dovecot version is 2.2.27. Thank you, Antoine Nguyen

4 6

imapc bug (signal 6)
by Ralf Hildebrandt 07 Sep '17

07 Sep '17

Running 2.3.0~alpha0-1~auto+1045, basically as a proxy between MUA and Exchange (IMAP): Sep 7 16:10:32 mproxy dovecot: imap-login: Login: user=<holtgrem>, method=PLAIN, rip=172.16.128.8, lip=141.42.206.11, mpid=61031, TLS, session=<fp3JBZpYop+sEIAI> Sep 7 16:10:32 mproxy dovecot: imap(holtgrem)<fp3JBZpYop+sEIAI>: imapc(exchange-imap.charite.de:993): Connected to 10.32.37.100:993 (local 141.42.206.11:58124) Sep 7 16:10:32 mproxy dovecot: imap(holtgrem)<fp3JBZpYop+sEIAI>: Panic: file mail-index-sync-update.c: line 1056 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index->indexid || map->hdr.indexid == 0) Sep 7 16:10:32 mproxy dovecot: imap(holtgrem)<fp3JBZpYop+sEIAI>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa1c2e) [0x7f059bd4cc2e] -> /usr/lib/dovecot/libdovecot.so.0(+0xa1d1c) [0x7f059bd4cd1c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f059bcdbbce] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x6a0) [0x7f059c0c91c0] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0xf8) [0x7f059c0c01c8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_refresh+0xe) [0x7f059c0d66de] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_index_refresh_force+0x8c) [0x7f059c094e7c] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xab786) [0x7f059c091786] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xabadc) [0x7f059c091adc] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_deinit+0x35) [0x7f059c02f925] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x4b) [0x7f059c0315bb] -> dovecot/imap [holtgrem 172.16.128.8 EXAMINE](cmd_select_full+0x170) [0x55fac9ae2b60] -> dovecot/imap [holtgrem 172.16.128.8 EXAMINE](command_exec+0x5c) [0x55fac9aea39c] -> dovecot/imap [holtgrem 172.16.128.8 EXAMINE](+0x1b822) [0x55fac9ae8822] -> dovecot/imap [holtgrem 172.16.128.8 EXAMINE](+0x1b8ac) [0x55fac9ae88ac] -> dovecot/imap [holtgrem 172.16.128.8 EXAMINE](client_handle_input+0x1e5) [0x55fac9ae8d05] -> dovecot/imap [holtgrem 172.16.128.8 EXAMINE](client_input+0x85) [0x55fac9ae9265] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f059bd63469] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a) [0x7f059bd64c9a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7f059bd63572] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f059bd63788] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f059bce6fe3] -> dovecot/imap [holtgrem 172.16.128.8 EXAMINE](main+0x343) [0x55fac9adb143] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f059b901830] -> dovecot/imap [holtgrem 172.16.128.8 EXAMINE](+0xe323) [0x55fac9adb323] Sep 7 16:10:32 mproxy dovecot: imap(holtgrem)<fp3JBZpYop+sEIAI>: Fatal: master: service(imap): child 61031 killed with signal 6 (core dumped) Sep 7 16:10:33 mproxy dovecot: imap-login: Login: user=<holtgrem>, method=PLAIN, rip=172.16.128.8, lip=141.42.206.11, mpid=61034, TLS, session=<X48IBppYpJ+sEIAI> Sep 7 16:10:33 mproxy dovecot: imap(holtgrem)<X48IBppYpJ+sEIAI>: imapc(exchange-imap.charite.de:993): Connected to 10.32.37.100:993 (local 141.42.206.11:58128) Sep 7 16:10:33 mproxy dovecot: imap-login: Login: user=<holtgrem>, method=PLAIN, rip=172.16.128.8, lip=141.42.206.11, mpid=61036, TLS, session=<0CQPBppYpp+sEIAI> Sep 7 16:10:33 mproxy dovecot: imap(holtgrem)<0CQPBppYpp+sEIAI>: imapc(exchange-imap.charite.de:993): Connected to 10.32.37.100:993 (local 141.42.206.11:58132) Sep 7 16:12:30 mproxy dovecot: imap(holtgrem)<0CQPBppYpp+sEIAI>: Connection closed (EXAMINE finished 28.690 secs ago) in=643 out=101173 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Sep 7 16:12:30 mproxy dovecot: imap(holtgrem)<X48IBppYpJ+sEIAI>: Connection closed (FETCH running for 116.592 + waiting input for 0.001 secs, 0.001 in locks, 28 B in + 64787+2070 B out, state=wait-input) in=105 out=66175 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Sep 7 16:12:35 mproxy dovecot: imap-login: Login: user=<holtgrem>, method=PLAIN, rip=172.16.128.8, lip=141.42.206.11, mpid=61049, TLS, session=<2ZkfDZpYKKCsEIAI> Sep 7 16:12:35 mproxy dovecot: imap(holtgrem)<2ZkfDZpYKKCsEIAI>: imapc(exchange-imap.charite.de:993): Connected to 10.32.37.100:993 (local 141.42.206.11:58160) Sep 7 16:12:36 mproxy dovecot: imap-login: Login: user=<holtgrem>, method=PLAIN, rip=172.16.128.8, lip=141.42.206.11, mpid=61051, TLS, session=<eg9cDZpYLqCsEIAI> Sep 7 16:12:36 mproxy dovecot: imap(holtgrem)<eg9cDZpYLqCsEIAI>: imapc(exchange-imap.charite.de:993): Connected to 10.32.37.100:993 (local 141.42.206.11:58164) Sep 7 16:12:41 mproxy dovecot: imap(holtgrem)<2ZkfDZpYKKCsEIAI>: Error: imapc: Remote server didn't send BODY[] for UID 1 in Calendar/BIH BCU (FETCH replied: FETCH completed.) Sep 7 16:14:19 mproxy dovecot: imap(holtgrem)<2ZkfDZpYKKCsEIAI>: Error: imapc(exchange-imap.charite.de:993): Command '1321 APPEND "INBOX" (\Seen) "29-Aug-2017 11:36:49 +0200" {42176625}' failed with BAD: 1321 Command Argument Error. 11 Sep 7 16:14:19 mproxy dovecot: imap(holtgrem)<2ZkfDZpYKKCsEIAI>: Error: imapc: APPEND failed: Command Argument Error. 11 Sep 7 16:14:19 mproxy dovecot: imap(holtgrem)<2ZkfDZpYKKCsEIAI>: IMAP session state is inconsistent, please relogin. in=42180017 out=220890 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=1 body_bytes=788 Sep 7 16:14:19 mproxy dovecot: imap-login: Login: user=<holtgrem>, method=PLAIN, rip=172.16.128.8, lip=141.42.206.11, mpid=61072, TLS, session=<Aa2IE5pYkKCsEIAI> Sep 7 16:14:19 mproxy dovecot: imap(holtgrem)<Aa2IE5pYkKCsEIAI>: imapc(exchange-imap.charite.de:993): Connected to 10.32.37.100:993 (local 141.42.206.11:58198) Sep 7 16:14:27 mproxy dovecot: imap(holtgrem)<Aa2IE5pYkKCsEIAI>: Connection closed (EXAMINE finished 8.029 secs ago) in=63 out=1372 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Sep 7 16:14:29 mproxy dovecot: imap(holtgrem)<eg9cDZpYLqCsEIAI>: Connection closed (FETCH running for 112.511 + waiting input for 0.001 secs, 0.001 in locks, 28 B in + 127311+2054 B out, state=wait-input) in=105 out=128699 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | https://www.charite.de

1 0

master: Warning: Sent SIGKILL to 511 pop3-login processes
by Luciano Mannucci 07 Sep '17

07 Sep '17

I have a lot of "master: Warning: Sent SIGKILL to 511 pop3-login processes" in my log file. Should I worry? (I'm running # 2.2.32 (dfbe293d4)) Thanks to all, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/

1 0

migrate courier to dovecot and forward mail like maildrop does it
by Markus Rosjat 07 Sep '17

07 Sep '17

Hi there, I was wondering what's the way to go if I want to migrate my courier/maildrop setup to dovecot/sieve? Is it even possible or do I need something else? The approach of using maildrop with postfix just hit the fan because I'm to dumb to configure it :( so with maildrop I have a .mailfilter file with cc "!some_email(a)some_domain.tld" and this just works like a charm with courier and maildrop but whats the equivalent in dovecote and the sieve plugin ? regards -- Markus Rosjat fon: +49 351 8107223 mail: rosjat(a)ghweb.de G+H Webservice GbR Gorzolla, Herrmann Königsbrücker Str. 70, 01099 Dresden http://www.ghweb.de fon: +49 351 8107220 fax: +49 351 8107227 Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT

1 0

lda
by dovecotml＠fuckaround.org 07 Sep '17

07 Sep '17

Hi all :) I will try to use /usr/lib/dovecot/deliver instead of postfix. I'd like automatically move email to junk folder. I use debian 9. cat /etc/postfix/master.cf [...] spamassassin unix - n n - - pipe user=debian-spamd argv=/usr/bin/spamc -f -e /usr/lib/dovecot/deliver -f ${sender} -d ${recipient} with this line dovecot works perfectly but only with virtual users, my system has also system users /etc/passwd How to tell dovecot to deliver email also to real system users? Sep 03 17:05:08 auth: Debug: master in: USER 1 test(a)mydomain.org service=lda Sep 03 17:05:08 auth-worker(24749): Debug: passwd(test(a)mydomain.org): lookup Sep 03 17:05:08 auth: Debug: pam(test(a)mydomain.org): passdb doesn't support credential lookups Sep 03 17:05:08 lda(test(a)mydomain.org): Debug: auth USER input: Sep 03 17:05:08 auth: Debug: passwd-file(test(a)mydomain.org): lookup: user=todo(a)fuckaround.org file=/etc/dovecot/users Sep 03 17:05:08 auth: Debug: userdb out: NOTFOUND 1 Sep 03 17:05:08 auth: Debug: auth client connected (pid=24758) Sep 03 17:05:08 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=GIfuUUpY1BCXMEZw lip=192.168.0.2 rip=x.x.x.x lport=993 rport=4308 local_name=imap.mydomain.org Sep 03 17:05:08 auth: Debug: client passdb out: CONT 1 Sep 03 17:05:08 auth: Debug: client in: CONT 1 hfdskjfsdkjdshjkfd== (previous base64 data may contain sensitive data) Sep 03 17:05:08 auth-worker(24749): Debug: pam(user,151.48.70.112,<GIfuUUpY1BCXMEZw>): lookup service=dovecot Sep 03 17:05:08 auth-worker(24749): Debug: pam(user,151.48.70.112,<GIfuUUpY1BCXMEZw>): #1/1 style=1 msg=Password: Sep 03 17:05:09 auth: Debug: client passdb out: OK 1 user=user Sep 03 17:05:09 auth: Debug: master in: REQUEST 2331639809 24758 1 754574397549379543789547 session_pid=24760 request_auth_token thanks for help! Pol

4 4

Improve dovecot logging
by Slobodan Zdravkovic 06 Sep '17

06 Sep '17

In case when user login with pop3 and only download only mail headers (partial download), but not email body, there is nothing in mail.log Is it possible to configure one of the existing dovecot plugins to log actions like TOP and LIST or is it possible to write new plugin for dovecot which can fetch this actions ?

1 0

error while compiling
by Rajesh M 05 Sep '17

05 Sep '17

hello this may not be in the scope of this forum, so am sorry about that i use qmailtoaster with dovecot i am trying to update dovecot to version 2.29, using the source rpm rpmbuild --rebuild --define "dist .qt.el6" dovecot-2.2.29.1-15.qt.src.rpm but getting error as follow. help require to identify the cause please make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/quota' Making check in quota-clone make[3]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/quota-clone' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/quota-clone' Making check in imap-quota make[3]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/imap-quota' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/imap-quota' Making check in pop3-migration make[3]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/pop3-migration' for bin in test-pop3-migration-plugin; do \ if ! ./$bin; then exit 1; fi; \ done pop3 migration get hdr sha1 .......................................... : ok 0 / 1 tests failed make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/pop3-migration' Making check in replication make[3]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/replication' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/replication' Making check in snarf make[3]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/snarf' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/snarf' Making check in stats make[3]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/stats' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/stats' Making check in imap-stats make[3]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/imap-stats' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/imap-stats' Making check in mail-crypt make[3]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/mail-crypt' for bin in test-mail-global-key test-mail-key; do \ if ! env NOUNDEF=1 ./$bin; then exit 1; fi; \ done try_load_keys ........................................................ : ok test_empty_keyset .................................................... : ok 0 / 2 tests failed generate user key .................................................... : ok generate inbox key ................................................... : ok cache reset .......................................................... : ok verify keys .......................................................... : ok test-mail-key.c:429: Assert failed: mail_crypt_get_private_key(t, mcp_old_box_key_id, FALSE, FALSE, &privkey, &error) > 0 test: random seed #2 was 2074645272 test-mail-key(root): Error: mail_crypt_get_private_key(7c9a1039ea2e4fed73e81dd3ffc3fa22ea4a28352939adde7bf8ea858b00fa4f) failed: Cannot decrypt key 7c9a1039ea2e4fed73e81dd3ffc3fa22ea4a28352939adde7bf8ea858b00fa4f: error:100AE081:elliptic curve routines:EC_GROUP_new_by_curve_name:unknown group test-mail-key.c:438: Assert failed: privkey != NULL old keys ............................................................. : FAILED 1 / 5 tests failed make[3]: *** [check-test] Error 1 make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins/mail-crypt' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src/plugins' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.29.1/src' make: *** [check-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.LDWEGt (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.LDWEGt (%check) thanks rajesh

1 0

pam authentication
by Pol Hallen 05 Sep '17

05 Sep '17

Hello all I use debian 9 with dovecot 2.x: real system users and virtual users: almost all works perfectly ;) Virtual users can connect via imap and pop using name + domain name: user00(a)domain1.org, etc. pam (real system users) users can connect via imap and pop ONLY without domain name It's a problem with pam authentication because linux make users authentication with only username (and not with also domain name) but I'd like user full email like test00(a)realdomain.org cat /etc/dovecot/conf.d/auth-passwdfile.conf.ext passdb { driver = passwd-file args = scheme=SHA256 username_format=%u /etc/dovecot/users } userdb { driver = passwd-file args = scheme=SHA256 username_format=%u /etc/dovecot/users } cat /etc/dovecot/conf.d/auth-system.conf.ext passdb { driver = pam } userdb { driver = passwd } inside /etc/dovecot/conf.d/10-auth.conf [...] #auth_username_format = %n is commented because I've multiple domains cat /var/log/dovecot.debug Sep 05 01:49:51 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat Sep 05 01:49:51 auth: Debug: passwd-file /etc/dovecot/users: Read 4 users in 0 secs Sep 05 01:49:51 auth: Debug: auth client connected (pid=23412) Sep 05 01:49:51 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=hjdhgfghhg lip=192.168.1.100 rip=192.168.1.100 lport=143 rport=39356 resp=hsdfhsfddfjk jklsdfkljkdlskfljsdkjlfds== (previous base64 data may contain sensitive data) Sep 05 01:49:51 auth-worker(23414): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Sep 05 01:49:51 auth-worker(23414): Debug: passwd-file /etc/dovecot/users: Read 4 users in 0 secs Sep 05 01:49:51 auth-worker(23414): Debug: pam(test(a)realdomain.org,192.168.1.100,<PitAxGVYvJnAqAFk>): lookup service=dovecot Sep 05 01:49:51 auth-worker(23414): Debug: pam(test(a)realdomain.org,192.168.1.100,<PitAxGVYvJnAqAFk>): #1/1 style=1 msg=Password: Sep 05 01:49:53 auth: Debug: passwd-file(test(a)realdomain.org,192.168.1.100,<PitAxGVYvJnAqAFk>): lookup: user=test(a)realdomain.org file=/etc/dovecot/users Sep 05 01:49:55 auth: Debug: client passdb out: FAIL 1 user=test(a)realdomain.com Sep 05 01:51:15 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Sep 05 01:51:15 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat Sep 05 01:51:15 auth: Debug: passwd-file /etc/dovecot/users: Read 4 users in 0 secs Sep 05 01:51:15 auth: Debug: auth client connected (pid=23461) Sep 05 01:51:26 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=ycnxyWVYQYokInmi lip=192.168.0.2 rip=36.34.121.162 lport=993 rport=35393 Sep 05 0 any idea? thanks for help! Pol -- Pol

3 13

transition from 1.x to 2? What did I break?
by Paul Beard 05 Sep '17

05 Sep '17

It’s been awhile since I set up my dovecot instance (like several years) and my transition from 1.x to 2 seems to have not gone well: all I can see is that authentication is banjaxed and I’m not sure what needs to be done to fix it. # 2.2.32 (dfbe293d4): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.3-STABLE i386 auth_debug = yes auth_mechanisms = plain login listen = *,[::] log_path = /var/log/dovecot.log mail_access_groups = mail mail_location = /var/mail/%u mail_privileged_group = mail 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 { driver = pam } passdb { driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/ssl/certs/dovecot.pem userdb { driver = passwd } userdb { driver = passwd } userdb { driver = passwd } protocol lda { postmaster_address = postmaster@redacted quota_full_tempfail = no } Sep 02 07:54:08 imap-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=192.168.0.1, lip=192.168.0.25, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher, session=<2hS8DDZYyN7AqAAB> Sep 02 07:54:08 auth: Debug: auth client connected (pid=47645) Sep 02 07:54:08 imap-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=192.168.0.1, lip=192.168.0.25, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher, session=<SFK8DDZYyt7AqAAB> Sep 02 07:54:54 auth: Warning: auth client 0 disconnected with 2 pending requests: EOF Sep 02 07:55:19 auth: Debug: auth client connected (pid=47714) Sep 02 07:55:19 imap-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=192.168.0.1, lip=192.168.0.25, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher, session=<WbD0EDZY2N7AqAAB> Sep 02 07:55:19 auth: Debug: auth client connected (pid=47716) Sep 02 07:55:19 imap-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=192.168.0.1, lip=192.168.0.25, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher, session=<1Qb1EDZY2d7AqAAB>

3 3

Mac Os mail error while moving msg in subfolder
by Antonello Cioffi 05 Sep '17

05 Sep '17

Hi all we are experiencing several errors like this: WROTE Sep 05 11:30:57.700 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:mail.uniparthenope.it -- port:993 -- socket:0x6000004b1dc0 -- thread:0x60000127b140 35.156 UID COPY 76543 GARR.Eduroam_tech READ Sep 05 11:30:57.702 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:mail.uniparthenope.it -- port:993 -- socket:0x6000004b1dc0 -- thread:0x60000127b140 35.156 NO [CANNOT] Character not allowed in mailbox name: '.' (0.001 + 0.000 secs). WROTE Sep 05 11:30:57.719 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:mail.uniparthenope.it -- port:993 -- socket:0x6000004b1dc0 -- thread:0x60000127b140 36.156 UID STORE 76543 +FLAGS.SILENT (\Deleted) READ Sep 05 11:30:57.733 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:mail.uniparthenope.it -- port:993 -- socket:0x6000004b1dc0 -- thread:0x60000127b140 * 7776 FETCH (UID 76543 MODSEQ (201448)) 36.156 OK Store completed (0.012 + 0.000 + 0.011 secs). WROTE Sep 05 11:30:57.734 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:mail.uniparthenope.it -- port:993 -- socket:0x6000004b1dc0 -- thread:0x60000127b140 37.156 IDLE READ Sep 05 11:30:57.740 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:mail.uniparthenope.it -- port:993 -- socket:0x6000004b1dc0 -- thread:0x60000127b140 + idling READ Sep 05 11:31:08.857 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:mail.uniparthenope.it -- port:993 -- socket:0x6000004b1dc0 -- thread:0x608001475180 * OK Still here READ Sep 05 11:31:09.369 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:mail.uniparthenope.it -- port:993 -- socket:0x6080006ba580 -- thread:0x608001475180 * OK Still here while a mail client on mac os tries to move a message to a subfolder Dovecot version in use is: 2.2.31 and the configuration extract file is: namespace { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = order = 0 prefix = separator = / subscriptions = yes type = private } namespace { disabled = no hidden = yes ignore_on_failure = no inbox = no list = no location = maildir:~/Maildir/expunged order = 0 prefix = .EXPUNGED/ separator = / subscriptions = yes type = private } all other client like thunderbird, outlook and horde imap web interface work fine. Is there something who could help me? thank you regards -- Dott. Antonello Cioffi Ufficio Servizi Informatici Università degli Studi di Napoli Parthenope Tel. 081/5475292 - Fax. 081/5475180

1 0

AW: problem with shared folders and acls - only able to share INBOX
by Christian Eisert 05 Sep '17

05 Sep '17

Hi, i found the solution for my problem (RTFM) doveadm acl debug => Folder \.Subfolder cannot be accessed => dots in maildir format I added a 'Layout=fs' to the namespace definition. Thanks and cheers Christian -----Ursprüngliche Nachricht----- Von: Christian Eisert [mailto:christian.eisert@gmx.net] Gesendet: Freitag, 1. September 2017 09:36 An: 'dovecot(a)dovecot.org' Betreff: problem with shared folders and acls - only able to share INBOX Hi everybody, I have a problem that I cannot share subfolders of the mailboxes INBOX , e.g. /Sent / Trash etc. but also no self created folders. The ACLs seem to be set right. I have the suspicion that the dictionary ( /var/lib/dovecot/db/shared-mailboxes.db ) is not updated - there are no entries for the sub folders I just cannot find the problem within my configuration. Many thanks for having a look at it. Cheers from Hamburg, Germany, Christian Configuration attached: ---------------------------------------------------------------------------- ---------------------------------- # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-3-amd64 x86_64 Debian 9.1 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes mail_debug = yes mail_gid = vmail mail_home = /var/vmail/mailboxes/%d/%n mail_location = maildir:~/mail:LAYOUT=fs mail_plugins = acl mail_privileged_group = vmail mail_uid = vmail 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 index ihave duplicate mime foreverypart extracttext namespace { hidden = no ignore_on_failure = no inbox = no list = yes location = maildir:%%h/mail:INDEX=%h/shared/%%u:CONTROL=%h/shared/%%u:INDEXPVT=%h/share d/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db antispam_backend = pipe antispam_mail_notspam = learn_ham antispam_mail_sendmail = /usr/bin/rspamc antispam_mail_spam = learn_spam antispam_spam = Spam antispam_trash = Trash quota = maildir:User quota quota_exceeded_message = Benutzer %u hat das Speichervolumen überschritten. / User %u has exhausted allowed storage space. sieve = file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-scr ipt.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imap { port = 143 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.mydomain.org/fullchain.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128 :+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDE A:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { imap_idle_notify_interval = 29 mins mail_max_userip_connections = 20 mail_plugins = acl quota imap_quota antispam imap_acl } protocol lmtp { mail_plugins = acl sieve postmaster_address = postmaster(a)mydomain.org } ---------------------------------------------------------------------------- ----------------------------------

1 0

questions concerning dovecot
by Rajesh M 04 Sep '17

04 Sep '17

hello all had some basic questions 1) what is the logic behind the numbering of files in the conf.d folder ... is this to define the sequence of execution of the config files ? 2) Concerning global scripts, is the default.sieve, before i understand that they get executed when the user does not have his private sieve script. are sieve_before, sieve_after and sieve_global_path all globalscripts ? thanks rajesh

2 1

Failed to repair mdbox index / wrong dbox version
by Peer Heinlein 04 Sep '17

04 Sep '17

After a filesystem crash dovecot isn't able to repair some of the m-Files. That's okay in general -- but I wonder why he's complaining about "wrong dsync version" if I execute "doveadm force-resync" locally: doveadm(user(a)mailbox.org): Warning: mdbox /mail-mailbox/mailbox.org/1846405//mdbox/storage: rebuilding indexes doveadm(user(a)mailbox.org): Error: Corrupted dbox file /xxxx//mdbox/storage/m.340 (around offset=154): Invalid dbox version I would accept every log that it's too broken to be repaired, but "Invalid dbox version"? Maybe it's somewhere else a bug that this m-file couldn't be repaired? # 2.2.32 (dfbe293): /etc/dovecot/dovecot.conf # Object storage plugin version 2.2.32 (afd3ef1) # Pigeonhole version 0.4.20 (11e3001) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.9 with mdbox/zlib. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

1 0

v2.2.32 released
by Timo Sirainen 04 Sep '17

04 Sep '17

https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig Two more fixes since rc2. And repeating: There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level line is logged every time when successfully connected to the remote server. This includes local/remote IP/port, which can be useful for matching against external logs. * config: Log a warning if plugin { key=no } is used explicitly. v2.3 will support "no" properly in plugin settings, but for now any value at all for a boolean plugin setting is treated as "yes", even if it's written as explicit "no". This change will now warn that it most likely won't work as intended. + Various optimizations to avoid accessing files/directories when it's not necessary. Especially avoid accessing mail root directories when INDEX directories point to a different filesystem. + mail_location can now include ITERINDEX parameter. This tells Dovecot to perform mailbox listing from the INDEX path instead of from the mail root path. It's mainly useful when the INDEX storage is on a faster storage. + mail_location can now include VOLATILEDIR=<path> parameter. This is used for creating lock files and in future potentially other files that don't need to exist permanently. The path could point to tmpfs for example. This is especially useful to avoid creating lock files to NFS or other remote filesystems. For example: mail_location=sdbox:~/sdbox:VOLATILEDIR=/tmp/volatile/%2.256Nu/%u + mail_location's LISTINDEX=<path> can now contain a full path. This allows storing mailbox list index to a different storage than the rest of the indexes, for example to tmpfs. + mail_location can now include NO-NOSELECT parameter. This automatically deletes any \NoSelect mailboxes that have no children. These mailboxes are sometimes confusing to users. + mail_location can now include BROKENCHAR=<char> parameter. This can be useful with imapc to access mailbox names that aren't valid mUTF-7 charset from remote servers. + If mailbox_list_index_very_dirty_syncs=yes, the list index is no longer refreshed against filesystem when listing mailboxes. This allows the mailbox listing to be done entirely by only reading the mailbox list index. + Added mailbox_list_index_include_inbox setting to control whether INBOX's STATUS information should be cached in the mailbox list index. The default is "no", but it may be useful to change it to "yes", especially if LISTINDEX points to tmpfs. + userdb can return chdir=<path>, which override mail_home for the chdir location. This can be useful to avoid accessing home directory on login. + userdb can return postlogin=<socket> to specify per-user imap/pop3 postlogin socket path. + cassandra: Add support for result paging by adding page_size=<n> parameter to the connect setting. + dsync/imapc, pop3-migration plugin: Strip also trailing tabs from headers when matching mails. This helps with migrations from Zimbra. + imap_logout_format supports now %{appended} and %{autoexpunged} + virtual plugin: Optimize IDLE to use mailbox list index for finding out when something has changed. + Added apparmor plugin. See https://wiki2.dovecot.org/Plugins/Apparmor - virtual plugin: A lot of fixes. In many cases it was also working very inefficiently or even incorrectly. - imap: NOTIFY parameter parsing was incorrectly "fixed" in v2.2.31. It was actually (mostly) working in previous versions, but broken in v2.2.31. - Modseq tracking didn't always work correctly. This could have caused imap unhibernation to fail or IMAP QRESYNC/CONDSTORE extensions to not work perfectly. - mdbox: "Inconsistency in map index" wasn't fixed automatically - dict-ldap: %variable values used in the LDAP filter weren't escaped. - quota=count: quota_warning = -storage=.. was never executed (try #2). v2.2.31 fixed it for -messages, but not for -storage. - imapc: >= 32 kB mail bodies were supposed to be cached for subsequent FETCHes, but weren't. - quota-status service didn't support recipient_delimiter - acl: Don't access dovecot-acl-list files with acl_globals_only=yes - mail_location: If INDEX dir is set, mailbox deletion deletes its childrens' indexes. For example if "box" is deleted, "box/child" index directory was deleted as well (but mails were preserved). - director: v2.2.31 caused rapid reconnection loops to directors that were down.

2 1

Commands loging to mail log
by Slobodan Zdravkovic 04 Sep '17

04 Sep '17

Hi, In case when user login with pop3 and only download only mail headers (partial download), but not email body, there is nothing in mail.log Is it possible to configure one of the existing dovecot plugins to log actions like TOP and LIST or is it possible to write new plugin for dovecot which can fetch this actions ? Thank you and regards,

1 0

Mixed Autehtnication and password schemes
by Raymond Sellars 04 Sep '17

04 Sep '17

Hi Looking for some confirmation/direction on how to achieve the following. We have a requirement to support both SASL PLAIN and DIGEST-MD5 authentication (certification reasons). In addition to this we have an application (webmail) that utilises a master password pattern for access, as the contain web portal provides the necessary authentication. I have access to users passwords in PLAIN text and looking to utilise the dict lookup mechanism for passwords. Problem #1 https://wiki2.dovecot.org/Authentication/MultipleDatabases - "Currently the fallback works only with the PLAIN authentication mechanism." The above not suggests I can't use DIGEST-MD5 with master password configuration, if using more than one passdb setup. I don't understand why there would be a restriction as the password validation should just fall through irrespective. Problem #2 How do I enforce some kind of account access policy Currently we're backing the authentication with an Identity and Authentication system. I would like to block IMAP access if a user's account is locked out, expired, or inactive. Similarly if there are too many IMAP attempts with the incorrect password I would like the account system wide to be locked out. With Dict lookup I don't seem a mechanism to keep the IDM system aware of login attempt/failures, since it pulls the plaintext password and validates internally. Is this possible? As a worse case does Dovecot implement any type of account access policies? Out IT security reviewers are hot on account policies, i.e. lockouts, expiries, and back off attempts. Thanks Raymond Solution Architect - Orion Health

2 4

Pigeonhole 0.4.20 source archive based on v. 0.4.20-rc1?
by Markus Schönhaber 02 Sep '17

02 Sep '17

Hi, looking at the source archive of pigeonhole 0.4.20 <https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.20.t…> I noticed that the contained ChangeLog mentions v0.4.20.rc1 as first entry and pigeonhole-version.h defines git revision 7cd71ba as version where I'd expect 4a55e6c. This is probably no big deal. But since Makefile.in and install-sh also differ (see attached diff) from the patch contained in <http://xi.rename-it.nl/debian.new/pool/jessie-rc-auto/dovecot-2.2/dovecot_2…> I thought I'd ask whether this is something without importance or something which should be changed. -- Regards mks

2 2

mail_log_events and dsync
by manu＠netbsd.org 02 Sep '17

02 Sep '17

Hello mail_log_events is handy to track what happened to a given message. Unfortunatly, it seems dsync activity is not captured. This causes messages to appear or vanish without a log trace. Did I miss a setting to get it? How should I track how something went wrong with dsync? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu(a)netbsd.org

1 0

RE: General IMAP question
by Joseph Tam 02 Sep '17

02 Sep '17

"Scott Techlist" <techlist06(a)msws.org> writes: > How will the IMAP account behave with the current mail_location setting below? > > mail_location = mbox:~/mail:INBOX=/var/mail/%u > > That is, where will the IMAP account's mail "go"? Right now it goes to > /var/mail/[localusername]. Maybe incorrectly, I assumed IMAP required > Maildir format? How are folders handled with this setting?. The one > IMAP account would be used for spamassassin training, it would need 2 > shared/public folders ("spam", "ham"). IMAP is a protocol: it does not dictate the storage format. You're free to use whatever format dovecot supplies a backend for, including mbox or maildir. What your mail_location specifies is that the INBOX is a mbox (not maildir) formatted file located at /var/mail/[localusername]. Other mailboxes are located in ~[localusername]/mail/* (also mbox formatted). If the IMAP account requires 2 externally supplied mailboxes or folders (spam, ham) accessible via IMAP, you'll either have to copy them into the IMAP user's mail/ folder, or setup special name spaces that maps to the mailboxes' path. The mailboxes need appropriate file permissions so that the IMAP user can access it. Joseph Tam <jtam.home(a)gmail.com>

1 0

Sync mailservera!
by nlekkas＠gmail.com 02 Sep '17

02 Sep '17

Hello to all ! I have two servers using dovecot and want to sync them with doveasm ...... I am using usersb as user backend ....database Can anyone help me config them... Is there any use guide about it ? Thans in advance for the help ! Nick

4 4

RE: General IMAP question
by Scott Techlist 01 Sep '17

01 Sep '17

Software is Centos7, Dovecot 2.2.10 >Use that single mailbox with IMAP, others stay to POP Thanks, I considered that and looked up the ways to restrict IMAP access. But: How will the IMAP account behave with the current mail_location setting below? mail_location = mbox:~/mail:INBOX=/var/mail/%u That is, where will the IMAP account's mail "go"? Right now it goes to /var/mail/[localusername]. Maybe incorrectly, I assumed IMAP required Maildir format? How are folders handled with this setting?. The one IMAP account would be used for spamassassin training, it would need 2 shared/public folders ("spam", "ham").

3 2

problem with shared folders and acls - only able to share INBOX
by Christian Eisert 01 Sep '17

01 Sep '17

Hi everybody, I have a problem that I cannot share subfolders of the mailboxes INBOX , e.g. /Sent / Trash etc. but also no self created folders. The ACLs seem to be set right. I have the suspicion that the dictionary ( /var/lib/dovecot/db/shared-mailboxes.db ) is not updated - there are no entries for the sub folders I just cannot find the problem within my configuration. Many thanks for having a look at it. Cheers from Hamburg, Germany, Christian Configuration attached: ---------------------------------------------------------------------------- ---------------------------------- # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-3-amd64 x86_64 Debian 9.1 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes mail_debug = yes mail_gid = vmail mail_home = /var/vmail/mailboxes/%d/%n mail_location = maildir:~/mail:LAYOUT=fs mail_plugins = acl mail_privileged_group = vmail mail_uid = vmail 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 index ihave duplicate mime foreverypart extracttext namespace { hidden = no ignore_on_failure = no inbox = no list = yes location = maildir:%%h/mail:INDEX=%h/shared/%%u:CONTROL=%h/shared/%%u:INDEXPVT=%h/share d/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db antispam_backend = pipe antispam_mail_notspam = learn_ham antispam_mail_sendmail = /usr/bin/rspamc antispam_mail_spam = learn_spam antispam_spam = Spam antispam_trash = Trash quota = maildir:User quota quota_exceeded_message = Benutzer %u hat das Speichervolumen überschritten. / User %u has exhausted allowed storage space. sieve = file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-scr ipt.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imap { port = 143 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.mydomain.org/fullchain.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128 :+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDE A:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { imap_idle_notify_interval = 29 mins mail_max_userip_connections = 20 mail_plugins = acl quota imap_quota antispam imap_acl } protocol lmtp { mail_plugins = acl sieve postmaster_address = postmaster(a)mydomain.org } ---------------------------------------------------------------------------- ----------------------------------

1 0

Re: General IMAP question
by Joseph Tam 01 Sep '17

01 Sep '17

"Scott Techlist" <techlist06(a)msws.org> writes: > Currently my POP users have a max mbox size but that is how much it > will store before they "come get it". I ensure they have at least one > device set to delete from the server periodically (i.e. 1 week). So > users with multiple devices get their mail duplciated on their devices > and at least one devices keeps the server emptied so their mbox does > not hit any limits. Traditionally, POP was a store and forward protocol. The client would download all the message in INBOX, them empty the mailbox. Nowadays, many POP users configure their clients to "Leave on server mode", which essentially accumulate on the server. The client may or may not also keep a cached copy. > As I understand it, when using IMAP, the user's messages are > perpetually stored on the server. IMAP is oriented as a remote mail service (client fetches and manipulate mail data on a remote server), so yes, messages are meant to remain on the server until deleted. There are probably some clients that cache local copies, but the remote server is considered canonical, so that local copies are deleted if the remote copies disappear. > How do other's deal with this? Am I misunderstanding something? As > popular as it seems to be, these seem like big hurdles to overcome. > Appreciate some help for a IMAP noob. What problem are you trying to solve? Is there a particularly compelling reason for you to move to IMAP (if not, stay with POP3)? You want to curtail space usage by users? You want to force users to retain client side copies of the messages? (Mind you, you'll still could have the same problem with POP -- there's nothing you can do to enforce the client to download/delete messages. Whether you use IMAP or POP3, you'll probably need some client side set up.) Joseph Tam <jtam.home(a)gmail.com>

1 0

RE: Iterate All Dovecot Users !
by Nick Lekkas 31 Aug '17

31 Aug '17

Hi Thomas ! So simple.... But you save my ass ..... And yes it works ! Thanks a lot ! Really ! I appreciate it ! Thanks Nick -----Original Message----- From: Thomas Reifferscheid [mailto:thomas@reifferscheid.org] Sent: Thursday, August 31, 2017 10:49 PM To: nlekkas(a)gmail.com Subject: Re: Iterate All Dovecot Users ! Am 31.08.2017 um 18:18 schrieb Nick Lekkas: > Hello to all ! > > I am trying to write a script that iterate all users that are created in > dovecot and postfix .... > Is there any way ..? > Hi Nick for user in $(doveadm user -u '*'); do echo $user; done Thomas __________ Information from ESET Endpoint Antivirus, version of detection engine 16008 (20170831) __________ The message was checked by ESET Endpoint Antivirus. part000.txt - is OK http://www.eset.com __________ Information from ESET Endpoint Antivirus, version of detection engine 16008 (20170831) __________ The message was checked by ESET Endpoint Antivirus. Email message - is OK http://www.eset.com

1 0

Iterate All Dovecot Users !
by Nick Lekkas 31 Aug '17

31 Aug '17

Hello to all ! I am trying to write a script that iterate all users that are created in dovecot and postfix .... Is there any way ..? Thanks in advance for your time ! Nick __________ Information from ESET Endpoint Antivirus, version of detection engine 16007 (20170831) __________ The message was checked by ESET Endpoint Antivirus. Email message - is OK http://www.eset.com

2 1

General IMAP question
by Scott Techlist 31 Aug '17

31 Aug '17

My server is a limited space mailserver set up to filter spam. Most of it's mail is passed on ot an exchange server so it is not stored locally. I have a handful of pop accounts that are stored locally. For years I've used mbox type mailboxes that I'm familiar with and can access on the server when needed using the old mailx program. They use a variety of clinets, typically Outlook and smartphones. I'm considering changing to IMAP because I need a single IMAP mailbox for an unrelated reason. But I am concerned about user storage issues at least.. Currently my POP users have a max mbox size but that is how much it will store before they "come get it". I ensure they have at least one device set to delete from the server periodically (i.e. 1 week). So users with multiple devices get their mail duplciated on their devices and at least one devices keeps the server emptied so their mbox does not hit any limits. As I understand it, when using IMAP, the user's messages are perpetually stored on the server. So if the user is not moving their messages from their inbox to some other place (e.g. a different Outlook pst file), that all the messages will remain on the server. All messages are "synced" in the user's inbox or other user created folders. Is that right? This would pretty quickly cripple those normal non-computer types that have years of emails in their inboxes. And I don't have the storage space to allow storing years of their mail. I also understand if they exceed their storage limit, mail starts bouncing which is what's I'd expect. At first I started googling how to expire the old mail, but then realized that won't work because if I delete on the server, I understand that will delete on their devices, too. How do other's deal with this? Am I misunderstanding something? As popular as it seems to be, these seem like big hurdles to overcome. Appreciate some help for a IMAP noob. Thanks, Scott

2 1

Strange folders
by Marti Markov 31 Aug '17

31 Aug '17

Hi all, I’ve been experiencing the “magical” creation of random folders on my mail server. I managed to catch the creation of one last night. Here is the log: Aug 30 01:38:13 mail dovecot: imap(f.lastName(a)domain.com): Debug: Namespace : /home/vmail/domain.com/f.lastName/Maildir/.wkkwgfrubwioniohkcyqttugdtdabuyn doesn't exist yet, using default permissions Aug 30 01:38:13 mail dovecot: imap(f.lastName(a)domain.com): Debug: Namespace : Using permissions from /home/vmail/domain.com/f.lastName/Maildir: mode=0700 gid=default Aug 30 01:38:13 mail dovecot: imap(f.lastName(a)domain.com): Debug: acl vfile: file /home/vmail/domain.com/f.lastName/Maildir/.wkkwgfrubwioniohkcyqttugdtdabuyn/dovecot-acl not found I have substituted only the username and the domain name. The folder name is as it was created: wkkwgfrubwioniohkcyqttugdtdabuyn There has been no activity logged on the exim4 side at that time. What would be the best course of action to determine what is happening?

2 1

Segmentation fault with doveadm search
by Stefán Tamás 30 Aug '17

30 Aug '17

Hi, We have a Ubuntu 14.04 server with dovecot 2.2.9 If I try to run /usr/bin/doveadm search -u email(a)exmaple.com mailbox Junk savedbefore 30d It will dump a core file. We have a similar config on an other server and there is no problem there. Any ideas how to prevent the core dump? root@triws2:~# gdb --args doveadm search -u email(a)example.com mailbox Junk savedbefore 30d Reading symbols from doveadm...Reading symbols from /usr/lib/debug//usr/bin/doveadm...done. done. (gdb) run Starting program: /usr/bin/doveadm search -u email(a)example.com mailbox Junk savedbefore 30d Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) where #0 0x0000000000000000 in ?? () #1 0x00007ffff76ef1b5 in mailbox_get_metadata (box=box@entry=0x5555557e1c70, items=items@entry=MAILBOX_METADATA_GUID, metadata_r=metadata_r@entry=0x7fffffffe2f0) at mail-storage.c:1544 #2 0x0000555555570918 in cmd_search_box (info=<optimized out>, ctx=0x5555557c8230) at doveadm-mail-search.c:28 #3 cmd_search_run (ctx=0x5555557c8230, user=<optimized out>) at doveadm-mail-search.c:58 #4 0x0000555555569b5b in doveadm_mail_next_user (ctx=0x5555557c8230, input=<optimized out>, error_r=0x7fffffffe3f8) at doveadm-mail.c:314 #5 0x000055555556a8ac in doveadm_mail_cmd (argv=0x5555557c33b0, argc=7, cmd=0x5555557c7408) at doveadm-mail.c:525 #6 doveadm_mail_try_run (cmd_name=<optimized out>, argc=7, argv=0x5555557c3398) at doveadm-mail.c:617 #7 0x00005555555696d4 in main (argc=7, argv=0x5555557c3398) at doveadm.c:398 Üdvözlettel Stefán Tamás --------------------------------- domain > email > web >>> siker Numex Informatika Kft. Mobil: +36 20 956 0233, Tel: +36 1 205 3915 http://numex.hu

2 6

Proper way to enable plugin for some users
by Ian Bobbitt 29 Aug '17

29 Aug '17

What's the best way to enable a plugin (in this case, mail_log) for only some users? I have this as a field returned in my sql user_query that seems to be doing the job: if(debug_log != 0 and '%s' = 'imap', 'listescape acl notify replication mail_log', 'listescape acl notify replication') as mail_plugins But it feels clunky and error prone having to replicate the entire list of plugins in my userdb. Is this the best way to do it, or is there something I should be doing differently? OS: CentOS 7 Dovecot: 2.2.31, GF RPMs

1 0

unexpected delivery location
by lists 29 Aug '17

29 Aug '17

Hi, We're running dovecot 2.2.13, virtual users, with postfix. We have an olddomain and a new domainname. To 'translate' *@olddomain into *@newdomain, I have configured: > cat /etc/postfix/canonical > @olddomain.com @newdomain.com While this seems to work, lately we have noticed that dovecot occasionally creates mailboxes for non-existent users, like: > /var/vmail/...username > /var/vmail/20username This only seems to be happening for mails sent to *olddomain* Looking at the source of these mails, they are indeed sent to 20username(a)olddomain.com and ...username(a)olddomain.com Mail headers sample: > Delivered-To: 20username(a)newdomain.com > Received: from server1.newdomain.com (server2.newdomain.com [x.y.z.q]) > by server3.newdomain.com (Postfix) with ESMTPS id 067B4812CF29E > for <20username(a)olddomain.com>; Thu, 13 Jul 2017 19:05:02 +0200 (CEST) Why doesn't the emailadress 20username(a)newdomain.com in the above generate an error, but instead are delivered to a newly created mailbox? My feeling is that something is wrong with the way I created the alias for olddomain -> newdomain with the canonical-file . Does that make sense? Our goal is to accept *(a)olddomain.com like it was sent to *(a)newdomain.com, including delivery failures for nonexistent mailboxes like 20username We configured postfix like: > canonical_maps = hash:/etc/postfix/canonical > virtual_alias_maps = ldap:/etc/postfix/ad-mailboxes.cf, ldap:/etc/postfix/ad-groups.cf > virtual_uid_maps = static:5000 > virtual_gid_maps = static:5000 > virtual_transport = dovecot Verified that this config works for newdomain, using: > root@mail:/etc/postfix# postmap -q alias(a)newdomain.com ldap:/etc/postfix/ad-mailboxes.cf > userid(a)newdomain.com > root@mail:/etc/postfix# postmap -q alias(a)olddomain.com ldap:/etc/postfix/ad-mailboxes.cf > root@mail:/etc/postfix# olddomain gives no result. Then, from master.cf: > dovecot unix - n n - - pipe > flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/dovecot-lda -f ${sender} -a ${recipient} -d ${user}@${nexthop} Finally, the mail location as defined in dovecot: > mail_location = maildir:/var/vmail/%Ln/Maildir:LAYOUT=fs:DIRNAME=mAildir So, can anyone explain why for mails to olddomain, dovecot creates new mailboxes, instead of simply generating an error?

3 6

dovecot-2.2.32/src/doveadm/doveadm-mail-fetch.c: 4 * suspicious expression ?
by David Binderman 29 Aug '17

29 Aug '17

Hello there, dovecot-2.2.32/src/doveadm/doveadm-mail-fetch.c:130]: (style) Suspicious condition (assignment + comparison); Clarify expression with parentheses. Source code is if ((ret = doveadm_print_istream(input) < 0)) Maybe better code if ((ret = doveadm_print_istream(input)) < 0) Some duplicates: [dovecot-2.2.32/src/doveadm/doveadm-mail-fetch.c:220]: (style) Suspicious condition (assignment + comparison); Clarify expression with parentheses. [dovecot-2.2.32/src/doveadm/doveadm-mail-fetch.c:237]: (style) Suspicious condition (assignment + comparison); Clarify expression with parentheses. [dovecot-2.2.32/src/doveadm/doveadm-mail-fetch.c:261]: (style) Suspicious condition (assignment + comparison); Clarify expression with parentheses. Regards David Binderman

2 2

vacation problem with SRS
by Kacper Guzik 28 Aug '17

28 Aug '17

Hi i have similiar problem like here: http://www.iredmail.org/forum/topic11833-iredmail-support-vocation-respone-… email send : from : web123(a)gmail.com to : jacka(a)mail.com vocation sent back from : jacka(a)mail.com to : srs0=hmc8=v7=gmail.com=web123(a)mail.com postsrsd changing return-path from web123(a)gmail.com to srs0=hmc8=v7= gmail.com=web123(a)mail.com this is no problem for me but sieve: Vacation's messages are always addressed to the Return-Path address it is possible some how change this ugly to header to normal? I can't find anything on dovecot mailing lists

2 7

[PATCH] Add support for lower TLS version than default
by Sebastian Andrzej Siewior 27 Aug '17

27 Aug '17

The openssl library in Debian unstable (targeting Buster) supports TLS1.2 by default. The library itself supports also TLS1.1 and TLS1.0. If the admin decides to also support TLS1.[01] users he can then enable the lower protocol version in case the users can't update their system. Signed-off-by: Sebastian Andrzej Siewior <sebastian(a)breakpoint.cc> --- src/config/all-settings.c | 1 + src/lib-master/master-service-ssl-settings.c | 2 ++ src/lib-master/master-service-ssl-settings.h | 1 + src/login-common/ssl-proxy-openssl.c | 15 ++++++++++++++- 4 files changed, 18 insertions(+), 1 deletion(-) --- a/src/config/all-settings.c +++ b/src/config/all-settings.c @@ -308,6 +308,7 @@ struct master_service_ssl_settings { const char *ssl_cert_username_field; const char *ssl_crypto_device; const char *ssl_options; + const char *ssl_lowest_version; bool ssl_verify_client_cert; bool ssl_require_crl; --- a/src/lib-master/master-service-ssl-settings.c +++ b/src/lib-master/master-service-ssl-settings.c @@ -26,6 +26,7 @@ static const struct setting_define maste DEF(SET_STR, ssl_protocols), DEF(SET_STR, ssl_cert_username_field), DEF(SET_STR, ssl_crypto_device), + DEF(SET_STR, ssl_lowest_version), DEF(SET_BOOL, ssl_verify_client_cert), DEF(SET_BOOL, ssl_require_crl), DEF(SET_BOOL, verbose_ssl), @@ -54,6 +55,7 @@ static const struct master_service_ssl_s .ssl_protocols = "!SSLv3", #endif .ssl_cert_username_field = "commonName", + .ssl_lowest_version = NULL, .ssl_crypto_device = "", .ssl_verify_client_cert = FALSE, .ssl_require_crl = TRUE, --- a/src/lib-master/master-service-ssl-settings.h +++ b/src/lib-master/master-service-ssl-settings.h @@ -16,6 +16,7 @@ struct master_service_ssl_settings { const char *ssl_cert_username_field; const char *ssl_crypto_device; const char *ssl_options; + const char *ssl_lowest_version; bool ssl_verify_client_cert; bool ssl_require_crl; --- a/src/login-common/ssl-proxy-openssl.c +++ b/src/login-common/ssl-proxy-openssl.c @@ -1302,7 +1302,20 @@ ssl_server_context_init(const struct log if (ctx->prefer_server_ciphers) SSL_CTX_set_options(ssl_ctx, SSL_OP_CIPHER_SERVER_PREFERENCE); SSL_CTX_set_options(ssl_ctx, openssl_get_protocol_options(ctx->protocols)); - +#if OPENSSL_VERSION_NUMBER >= 0x10100000 + if (ssl_set->ssl_lowest_version) { + if (!strcmp(ssl_set->ssl_lowest_version, "TLS1.0")) + SSL_CTX_set_min_proto_version(ssl_ctx, TLS1_VERSION); + else if (!strcmp(ssl_set->ssl_lowest_version, "TLS1.1")) + SSL_CTX_set_min_proto_version(ssl_ctx, TLS1_1_VERSION); + else if (!strcmp(ssl_set->ssl_lowest_version, "TLS1.2")) + SSL_CTX_set_min_proto_version(ssl_ctx, TLS1_2_VERSION); + else + i_fatal("TLS min version: '%s' is invalid. Only " + "'TLS1.0' and 'TLS1.1' is supported", + ssl_set->ssl_lowest_version); + } +#endif if (ctx->pri.cert != NULL && *ctx->pri.cert != '\0' && ssl_proxy_ctx_use_certificate_chain(ctx->ctx, ctx->pri.cert) != 1) { i_fatal("Can't load ssl_cert: %s",

3 6

Debian packages for 2.2.32?
by Harald Leithner 27 Aug '17

27 Aug '17

Hi, It seams that IX didn't Motive Themen Version change. Thx Harald -- Diese Nachricht wurde von meinem Mobiltelefon gesendet.

3 6

Released Pigeonhole v0.4.20 for Dovecot v2.2.32.
by Stephan Bosch 27 Aug '17

27 Aug '17

Hello Dovecot users, Here's the definitive 0.4.20 release. There were no changes since the release candidate. Changelog v0.4.20: + Made the retention period for redirect duplicate identifiers configurable. For accounts that perform many redirects, the lda-dupes database could grow to impractical sizes. Changed the default retention period from 24 to 12 hours. - sieve-filter: Fixed memory leak: forgot to clean up script binary at end of execution. Normally, this would merely be an inconsequential memory leak. However, when the script comes from an LDAP storage, this would cause io leak warnings. - managesieve-login: Fixed handling of AUTHENTICATE command. A second authenticate command would be parsed wrong. This problem was caused by changes in the previous release. - LDA Sieve plugin: Fixed minor memory leak caused by not cleaning up the sieve_discard script. The release is available as follows: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.20.t… https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.20.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

Re: a bit further along - OpenSSL - Re: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!
by Joseph Tam 27 Aug '17

27 Aug '17

Aki Tuomi <aki.tuomi(a)dovecot.fi> writes: > > I simulated your compile arguments as best as I could, and compared the libtool > > command in my compile logs with your's. > > > > (mine) > > Mine: -lssl -lcrypto -lrt -lnsl -lsocket -lsendfile > > > > (your's) > > -lcrypto -lrt -lnsl -lsocket -lsendfile -lcrypt > > > > You're missing "-lssl" but have a spurious "-lcrypt". Probably all your missing symbols are > > actually in libssl.so. > > OpenSSL usually requires both libssl and libcrypto, the -lcrypt probably is for > crypt() Makes sense. So the OP can confirm this is the problem by manually running the libtool command but adding "-lssl", and if that works, then something screwed up Makefile or other build files. Joseph Tam <jtam.home(a)gmail.com>

1 0

[SUMMARY] trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!
by Jerry Kemp 26 Aug '17

26 Aug '17

I'm done. Good to go. Good compile + new binaries all built against the latest OpenSSL libraries. Big thank you to James, Joseph Tam and Aki Tuomi who game me pointers and kept me in the right direction. ........................................................................ These are the settings that made everything work for me. First, needed a current, up-to-date version of OpenSSL in place. Generally pretty easy task. I discovered that OpenSSL will not create shared libraries on Solaris using GNU make. No problem, everything worked just fine using the system /usr/ccs/bin/make . Back to Dovecot. Environmental variables - this is what I needed for my system. Although I'm a Sys V guy, never cared for the /opt thing, and ended up adopting /Applications from NeXT . setenv CPPFLAGS "-I/Applications/openssl-1.0.2l.32/include -I/Applications/openssl-1.0.2l.32/include/openssl" setenv LDFLAGS "-L/Applications/openssl-1.0.2l.32/lib" setenv SSL_CFLAGS "-I/Applications/openssl-1.0.2l.32/include -I/Applications/openssl-1.0.2l.32/include/openssl" setenv SSL_LIBS "-R/Applications/openssl-1.0.2l.32/lib -L/Applications/openssl-1.0.2l.32/lib" setenv LIBS "-lcrypto -lssl" setenv LD_LIBRARY_PATH "/Applications/openssl-1.0.2l.32/lib:/usr/lib:/usr/local/lib:/usr/xpg4/lib:/usr/openwin/lib:/usr/dt/lib" ........................................................................ Config statement: ./configure \ --prefix=/Applications/dovecot-2.2.32.32 \ --with-ssl=openssl \ --with-ssldir=/Applications/dovecot-2.2.32.31/certs ........................................................................ From there, it was run "make" then wait for the compile to finish. It had been a while since I did a fresh Dovecot compile, and in the past, I had just used the system provided OpenSSL install. This took a bit more work. Hope this can help out someone else in the future. Thank you, Jerry

1 0

dovecot: config: Error: BUG: Config client connection sent too much data
by Tony 26 Aug '17

26 Aug '17

Hello, Today I started noticing a very odd Dovecot error in the mail logs across 2 replicated Dovecot hosts via dsync. I have searched the Dovecot archives, Google, back tracked, downgraded Dovecot to earlier versions from earlier this year and ruled everything out I could think of to no avail. There really are not any helpful reports with what I am specifically seeing. The strange thing is only vmail(a)domain.net is repeatedly shown in the log. The error looks like this. *Aug 24 22:46:02 orbitron dovecot: config: Error: BUG: Config client connection sent too much data****Aug 24 22:46:02 orbitron dovecot: doveadm(vmail@domain.net@domain.net@domain.net@domain.net@domain.net@domain.net@domain.net@domain.net@domain.net): Fatal: Error reading configuration: read(/var/run/dovecot/config) failed: read(size=8192) failed: Connection reset by peer*** $ dovecot --version 2.2.31 (65cde28) Dovecot #1: Linux kernel 4.9.36-x86_64 Dovecot #2: Linux kernel 4.12.8-x86_64 Here are the latest Dovecot updates performed this year. [2017-04-29 14:45] [ALPM] upgraded dovecot (2.2.28-2 -> 2.2.28-3) [2017-05-02 23:05] [ALPM] upgraded dovecot (2.2.28-3 -> 2.2.29.1-1) [2017-06-11 17:20] [ALPM] upgraded dovecot (2.2.29.1-1 -> 2.2.30.2-1) [2017-06-30 22:46] [ALPM] upgraded dovecot (2.2.30.2-1 -> 2.2.31-1) When Dovecot was last updated back on June 30, I did `systemctl daemon-reload` but never actually restarted the Dovecot daemon until what seems like today. The only thing I did today was edit /etc/dovecot/conf.d/10-auth.conf by simply enabling "*auth_username_format = %Lu*" which was commented out before I enabled it. That is the /*only*/ thing that I tested. After I was done testing I went back and commented out the same thing so it reads "*#auth_username_format = %Lu*" and of course restarted Dovecot. I really doubt this has anything to do with what I am reporting as auth is not the problem in this case. Thank You, Tony

2 4

Re: a bit further along - OpenSSL - Re: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!
by Joseph Tam 26 Aug '17

26 Aug '17

Jerry Kemp <dovecot(a)oryx.us> wrote: > same ENV variable setup and configure statement as originally used, but again, :( > ended up failing here: > .......................................................................... > libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes > -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 > -Wbad-function-cast -fno-builtin-strftime > -I/Applications/openssl-1.0.2l.32/include > -I/Applications/openssl-1.0.2l.32/include/openssl -o .libs/test-http-client > test-http-client.o -L/Applications/openssl-1.0.2l.32/lib ./.libs/libhttp.a > ../lib-dns/.libs/libdns.a ../lib-ssl-iostream/.libs/libssl_iostream.a > ../lib-master/.libs/libmaster.a ../lib-settings/.libs/libsettings.a > ../lib-test/.libs/libtest.a ../lib/.libs/liblib.a > ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so -lcrypto -lrt -lnsl > -lsocket -lsendfile -lcrypt -R/Applications/dovecot-2.2.31.32/lib/dovecot I simulated your compile arguments as best as I could, and compared the libtool command in my compile logs with your's. (mine) Mine: -lssl -lcrypto -lrt -lnsl -lsocket -lsendfile (your's) -lcrypto -lrt -lnsl -lsocket -lsendfile -lcrypt You're missing "-lssl" but have a spurious "-lcrypt". Probably all your missing symbols are actually in libssl.so. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!
by Joseph Tam 26 Aug '17

26 Aug '17

I would also check where the "... is not portable!" messaage is generated. If it's done by the configure script, you can look at the test to give you a hint as to why this message was generated. For my setup, I did much the same as you but didn't have to set the SSL_CFLAGS, SSL_LIBS environment variables, nor did I set the --with-ssldir configure option (although your setup may need it). Maybe check output of file /Applications/openssl-1.0.2l.32/lib/libssl.so.1.0.0 just to make sure your library's arhitecture matches your expectation. > # ./configure \ > --prefix=/Applications/dovecot-2.2.31.32 \ > --with-ssl=openssl \ > --with-ssldir=/Applications/dovecot-2.2.31.32/certs \ > --with-storages=mbox,maildir,imapc,pop3c I believe "--with-storages" option is now obsolete: all the storage backends are built, whether you ask for it or not. Joseph Tam <jtam.home(a)gmail.com>

2 2

trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!
by Jerry Kemp 26 Aug '17

26 Aug '17

attempting to compile dovecot 2.2.31 on Sun/Oracle Solaris 10 SPARC. configure goes fine. First sign of problems during compile is with this warning: ............................................... *** libssl_iostream_openssl.so is not portable! ............................................... actual ERRORS - Soon, compile errors out with undefined symbols. Output at bottom of note. ............................................... additional system information. OpenSSL - just prior to dovecot compile attempt, I downloaded and successfully compiled OpenSSL version 1.0.2l (to include a successful "make test" ) in directory /Applications/openssl-1.0.2l.32 , want to link against current code and not mess with system provided SSL stuff in /usr/sfw/* ENV setting and configure command line prior to compile - # setenv CPPFLAGS "-I/Applications/openssl-1.0.2l.32/include -I/Applications/openssl-1.0.2l.32/include/openssl" # setenv LDFLAGS "-L/Applications/openssl-1.0.2l.32/lib" # setenv SSL_CFLAGS "-I/Applications/openssl-1.0.2l.32/include -I/Applications/openssl-1.0.2l.32/include/openssl" # setenv SSL_LIBS "-R/Applications/openssl-1.0.2l.32/lib -L/Applications/openssl-1.0.2l.32/lib" # ./configure \ --prefix=/Applications/dovecot-2.2.31.32 \ --with-ssl=openssl \ --with-ssldir=/Applications/dovecot-2.2.31.32/certs \ --with-storages=mbox,maildir,imapc,pop3c ................................................. What is the .32 stuff I see appended to directories? I did a 32 bit compile of the latest OpenSSL, then , the data shown here is also for a 32 bit dovecot build to link against the 32 bit OpenSSL build. I have been fighting this for a few days, and had also done an identical 64 bit OpenSSL, then dovecot build. The 64 bit dovecot build failed in the same way and place. Additionally, when I did the 64 bit compile, I ended up pulling down a current copy of ZLIB, and doing a 64 bit compile of that library also, and installing it under /Applications then linking against that. the system ZLIB library is/was 32 bit, and if there is a 64 bit version provided by Sun/Oracle, neither myself or the "configure" script could locate it. Not a big detail, ZLIB is an easy compile, just trying to share all relevant data. ................................................. Try again with the latest code. I have been working/fighting 2.2.31 for a couple of days. I see earlier today, dovecot 2.2.32 was released earlier today, so before anyone runs to put on their "*L*" cap and advise me to pull down the latest code, I already did that, and the compile errors out in the same place. ................................................. If your still reading, thank you, just want to provide as many relevant details as possible. Again, symbol errors from compile are at bottom. TIA for any helpful comments or suggestions, Jerry ............................................................... Undefined first referenced symbol in file ERR_clear_error ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_load_error_strings ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so BIO_ctrl_get_write_guarantee ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so EVP_PKEY_free ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_use_PrivateKey ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_get_peer_certificate ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CIPHER_get_bits ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CIPHER_get_name ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so DH_generate_parameters ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so sk_value ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so PEM_X509_INFO_read_bio ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_NAME_oneline ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ERR_get_error_line_data ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_write ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_NAME_get_text_by_NID ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_get_ex_new_index ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_get_error ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ENGINE_init ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ENGINE_free ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so BIO_ctrl_pending ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_INFO_free ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_get_ext_d2i ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_free ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ERR_get_error ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so PEM_read_bio_PrivateKey ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so OPENSSL_add_all_algorithms_noconf ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so BIO_write ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ENGINE_set_default ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_accept ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ASN1_STRING_data ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ASN1_STRING_type ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSLv23_server_method ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_STORE_set_flags ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so sk_pop_free ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_use_PrivateKey ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ERR_error_string_n ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so CRYPTO_set_mem_functions ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so BIO_new_mem_buf ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_get_cert_store ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so CRYPTO_cleanup_all_ex_data ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so GENERAL_NAME_free ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so sk_num ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_NAME_get_entry ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_ctrl ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_free ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_read ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSLv23_client_method ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_alert_type_string_long ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_new ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so PEM_read_bio_X509 ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_new ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ERR_peek_error ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so DH_free ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_NAME_ENTRY_get_data ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so d2i_DHparams ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_load_verify_locations ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_set_bio ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_set_tmp_dh_callback ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so i2d_DHparams ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_NAME_get_index_by_NID ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_set_info_callback ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so sk_push ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_connect ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so BIO_new_bio_pair ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_shutdown ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so RAND_bytes ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so EVP_cleanup ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so OBJ_cleanup ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_verify_cert_error_string ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ASN1_STRING_length ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_STORE_add_crl ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ENGINE_load_builtin_engines ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_set_client_CA_list ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so OBJ_txt2nid ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_use_certificate ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_use_certificate ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_ctrl ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_free ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ENGINE_cleanup ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so sk_new_null ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ERR_peek_last_error ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_get_current_cipher ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_STORE_CTX_get_current_cert ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_get_ex_data_X509_STORE_CTX_idx ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so RSA_generate_key ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_STORE_CTX_get_error ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_state_string_long ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ERR_remove_state ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so BIO_free ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so BIO_read ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_STORE_add_cert ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_alert_desc_string_long ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_get_version ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_get_ex_data ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_set_cipher_list ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_set_ex_data ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_set_cipher_list ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_set_verify ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_STORE_CTX_get_ex_data ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ERR_free_strings ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_NAME_dup ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_CTX_set_tmp_rsa_callback ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so X509_get_subject_name ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so SSL_library_init ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ENGINE_finish ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ENGINE_by_id ../lib-ssl-iostream/.libs/libssl_iostream_openssl.so ld: fatal: symbol referencing errors. No output written to .libs/test-http-client collect2: ld returned 1 exit status *** Error code 1 make: Fatal error: Command failed for target `test-http-client'

2 3

Install still locks up my server
by Marc Perkel 25 Aug '17

25 Aug '17

This is still broken in the 2.2.32. config.guess forks copies till the server dies. Running Centos 6.6 under OpenVZ. On 06/26/17 16:03, Marc Perkel wrote: > > > On 06/26/17 14:42, Timo Sirainen wrote: >> On 26 Jun 2017, at 23.19, Marc Perkel <marc(a)perkel.com> wrote: >>> Ever since 2.26 I haven't been able to upgrade. In fact the install >>> locks up my server. >>> >>> I get into and infinite recursive loop where the config-guess >>> program calls itself until the server locks up from overload. >>> >>> I'm running Centos 6 under OpenVZ. >>> >>> What am I missing? I think there's a serious bug. >>> >>> 31233 pts/3 S 0:00 /bin/sh ./config.guess >>> 31235 pts/3 S 0:00 \_ /bin/sh ./config.guess >>> 31238 pts/3 S 0:00 \_ /bin/sh ./config.guess >>> 31240 pts/3 S 0:00 \_ /bin/sh ./config.guess >> I think I remember seeing this before, but unfortunately can't >> remember what the solution was. Maybe it was something something >> messed up in the OS or in the build directory. Are you compiling from >> the tarballs? So it's the "configure" that fails? Also if you run >> "./config.guess" manually? What's the output if you run "bash -x >> ./config.guess"? >> >> >> > > bash -x ./config.guess > + timestamp=2015-08-20 > ++ sed -e 's,.*/,,' > ++ echo ./config.guess > + me=config.guess > + usage='Usage: ./config.guess [OPTION] > > Output the configuration name of the system `config.guess'\'' is run on. > > Operation modes: > -h, --help print this help, then exit > -t, --time-stamp print date of last modification, then exit > -v, --version print version number, then exit > > Report bugs and patches to <config-patches(a)gnu.org>.' > + version='GNU config.guess (2015-08-20) > > Originally written by Per Bothner. > Copyright 1992-2015 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE.' > + help=' > Try `config.guess --help'\'' for more information.' > + test 0 -gt 0 > + test 0 '!=' 0 > + trap 'exit 1' 1 2 15 > + set_cc_for_build=' > trap "exitcode=\$?; (rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp > 2>/dev/null) && exit \$exitcode" 0 ; > trap "rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp 2>/dev/null; exit 1" 1 > 2 13 15 ; > : ${TMPDIR=/tmp} ; > { tmp=`(umask 077 && mktemp -d "$TMPDIR/cgXXXXXX") 2>/dev/null` && > test -n "$tmp" && test -d "$tmp" ; } || > { test -n "$RANDOM" && tmp=$TMPDIR/cg$$-$RANDOM && (umask 077 && > mkdir $tmp) ; } || > { tmp=$TMPDIR/cg-$$ && (umask 077 && mkdir $tmp) && echo "Warning: > creating insecure temp directory" >&2 ; } || > { echo "$me: cannot create a temporary directory in $TMPDIR" >&2 ; > exit 1 ; } ; > dummy=$tmp/dummy ; > tmpfiles="$dummy.c $dummy.o $dummy.rel $dummy" ; > case $CC_FOR_BUILD,$HOST_CC,$CC in > ,,) echo "int x;" > $dummy.c ; > for c in cc gcc c89 c99 ; do > if ($c -c -o $dummy.o $dummy.c) >/dev/null 2>&1 ; then > CC_FOR_BUILD="$c"; break ; > fi ; > done ; > if test x"$CC_FOR_BUILD" = x ; then > CC_FOR_BUILD=no_compiler_found ; > fi > ;; > ,,*) CC_FOR_BUILD=$CC ;; > ,*,*) CC_FOR_BUILD=$HOST_CC ;; > esac ; set_cc_for_build= ;' > + UNAME_MACHINE=x86_64 > + UNAME_RELEASE=2.6.32-042stab123.3 > + UNAME_SYSTEM=Linux > + UNAME_VERSION='#1 SMP Fri May 5 12:29:05 MSK 2017' > + case "${UNAME_SYSTEM}" in > + LIBC=gnu > + eval trap '"exitcode=\$?;' '(rm' -f '\$tmpfiles' '2>/dev/null;' > rmdir '\$tmp' '2>/dev/null)' '&&' exit '\$exitcode"' 0 ';' trap '"rm' > -f '\$tmpfiles' '2>/dev/null;' rmdir '\$tmp' '2>/dev/null;' exit '1"' > 1 2 13 15 ';' : '${TMPDIR=/tmp}' ';' '{' 'tmp=`(umask' 077 '&&' mktemp > -d '"$TMPDIR/cgXXXXXX")' '2>/dev/null`' '&&' test -n '"$tmp"' '&&' > test -d '"$tmp"' ';' '}' '||' '{' test -n '"$RANDOM"' '&&' > 'tmp=$TMPDIR/cg$$-$RANDOM' '&&' '(umask' 077 '&&' mkdir '$tmp)' ';' > '}' '||' '{' 'tmp=$TMPDIR/cg-$$' '&&' '(umask' 077 '&&' mkdir '$tmp)' > '&&' echo '"Warning:' creating insecure temp 'directory"' '>&2' ';' > '}' '||' '{' echo '"$me:' cannot create a temporary directory in > '$TMPDIR"' '>&2' ';' exit 1 ';' '}' ';' 'dummy=$tmp/dummy' ';' > 'tmpfiles="$dummy.c' '$dummy.o' '$dummy.rel' '$dummy"' ';' case > '$CC_FOR_BUILD,$HOST_CC,$CC' in ',,)' echo '"int' 'x;"' '>' '$dummy.c' > ';' for c in cc gcc c89 c99 ';' do if '($c' -c -o '$dummy.o' > '$dummy.c)' '>/dev/null' '2>&1' ';' then 'CC_FOR_BUILD="$c";' break > ';' fi ';' done ';' if test 'x"$CC_FOR_BUILD"' = x ';' then > CC_FOR_BUILD=no_compiler_found ';' fi ';;' ',,*)' 'CC_FOR_BUILD=$CC' > ';;' ',*,*)' 'CC_FOR_BUILD=$HOST_CC' ';;' esac ';' set_cc_for_build= ';' > ++ trap 'exitcode=$?; (rm -f $tmpfiles 2>/dev/null; rmdir $tmp > 2>/dev/null) && exit $exitcode' 0 > ++ trap 'rm -f $tmpfiles 2>/dev/null; rmdir $tmp 2>/dev/null; exit 1' > 1 2 13 15 > ++ : /tmp > ++ tmp=/tmp/cgpmW24a > ++ test -n /tmp/cgpmW24a > ++ test -d /tmp/cgpmW24a > ++ dummy=/tmp/cgpmW24a/dummy > ++ tmpfiles='/tmp/cgpmW24a/dummy.c /tmp/cgpmW24a/dummy.o > /tmp/cgpmW24a/dummy.rel /tmp/cgpmW24a/dummy' > ++ case $CC_FOR_BUILD,$HOST_CC,$CC in > ++ echo 'int x;' > ++ for c in cc gcc c89 c99 > >

1 0

Dovecot - Postfix Calender Synchronisation
by mca＠caloro.ch 25 Aug '17

25 Aug '17

Hello Together Please witch add-on possibilities exist to synchronize the Calednar with Dovecot and Postfix. Can give me here any a possible direction ? thanks regards Mauri

13 22

Dovecot - Postfix Calender Synchronisation
by Maurizio Caloro 25 Aug '17

25 Aug '17

Hello Together Please witch add-on possibilities exist to synchronize the Calednar with Dovecot and Postfix. Can give me here any a possible direction ? thanks regards Mauri

2 1

socketpair failed: Too many open files on Debian 9
by Patrick Westenberg 25 Aug '17

25 Aug '17

Hi @all, after re-installing one of my two frontends/proxy-servers I get the following error messages after some time (sometimes after 1h, sometimes after 24h): 11:23:55 imap-login: Error: socketpair() failed: Too many open files 11:23:55 imap-login: Error: socketpair() failed: Too many open files 11:23:56 imap-login: Error: socketpair() failed: Too many open files 11:23:56 imap-login: Error: socketpair() failed: Too many open files 11:23:57 imap-login: Error: socketpair() failed: Too many open files 11:26:17 imap-login: Error: socket() failed: Too many open files 11:26:17 imap-login: Error: proxy(post(a)example.com): connect(172.17.1.1, 143) failed: Too many open files (after 0 secs): user=<post(a)example.com>, method=PLAIN, rip=x.x.x.x, lip=x.x.x.x, TLS, session=<FgPWTWhXa8dQjLoi> 11:26:17 imap-login: Error: socketpair() failed: Too many open files 11:26:17 imap-login: Error: proxy: SSL handshake failed to 172.17.1.1:143: user=<post(a)example.com>, method=PLAIN, rip=x.x.x.x, lip=x.x.x.x, TLS, session=<HALWTWhXasdQjLoi> 11:26:17 imap-login: Error: socket() failed: Too many open files 11:26:17 imap-login: Error: proxy(post(a)example.com): connect(172.17.1.1, 143) failed: Too many open files (after 0 secs): user=<post(a)example.com>, method=LOGIN, rip=x.x.x.x, lip=x.x.x.x, TLS, session=<HALWTWhXasdQjLoi> 11:26:17 imap-login: Error: socketpair() failed: Too many open files 11:26:17 imap-login: Error: proxy: SSL handshake failed to 172.17.1.1:143: user=<post(a)example.com>, method=LOGIN, rip=x.x.x.x, lip=x.x.x.x, TLS, session=<FgPWTWhXa8dQjLoi> 11:26:17 imap-login: Error: socket() failed: Too many open files As I switched from KVM to LXC my first idea was that this could be caused by LXC but this even happens with KVM. I tried dovecot 2.2.31 and 2.2.32.rc2. OS is Debian 9. These problems don't occur on my old machine (Debian 7). Any ideas? Regards Patrick # 2.2.32.rc2 (a350120ca): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: Linux 4.4.67-1-pve x86_64 Debian 9.1 auth_mechanisms = plain login director_mail_servers = 172.17.1.1 172.17.1.2 director_servers = 172.17.1.32 172.17.1.3 director_user_expire = 5 mins lmtp_proxy = yes log_path = /var/log/dovecot.log 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 index ihave duplicate mime foreverypart extracttext protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 172.17.1.32 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director process_min_avail = 1 service_count = 0 } service lmtp { inet_listener lmtp { address = 172.17.1.32 port = 24 ssl = yes } process_min_avail = 20 } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } } service pop3-login { executable = pop3-login director } ssl_cert = </etc/ssl/certs/certum_wildcard.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes verbose_proctitle = yes protocol !smtp { passdb { args = proxy=y nopassword=y starttls=any-cert driver = static name = } } protocol smtp { passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql name = } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql name = } } protocol lmtp { auth_socket_path = director-userdb } ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 7978 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 7978 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited ########################### This machine has no problems: # 2.2.18: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.11 auth_mechanisms = plain login director_mail_servers = 172.17.1.1 172.17.1.2 director_servers = 172.17.1.3 172.17.1.32 director_user_expire = 5 mins lmtp_proxy = yes log_path = /var/log/dovecot.log 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 index ihave duplicate protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 172.17.1.3 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director process_min_avail = 1 service_count = 0 } service lmtp { inet_listener lmtp { address = 172.17.1.3 port = 24 ssl = yes } process_min_avail = 20 } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } } service pop3-login { executable = pop3-login director } ssl_cert = </etc/ssl/certs/certum_wildcard.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/certum_wildcard.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 !SSLv2 verbose_proctitle = yes protocol !smtp { passdb { args = proxy=y nopassword=y starttls=any-cert driver = static name = } } protocol smtp { passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql name = } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql name = } } protocol lmtp { auth_socket_path = director-userdb } ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 257548 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 257548 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited

4 5

Error: mdbox .../storage: Duplicate GUID
by Dennis Schridde 24 Aug '17

24 Aug '17

Hi! When I force-resync a mailbox of mine, I see following output: # doveadm force-resync -u $USER $PATH doveadm($USER): Warning: mdbox .../storage: Inconsistency in map index ($X,$Y2 != $X,$Y2) doveadm($USER): Warning: fscking index file .../storage/dovecot.map.index doveadm($USER): Warning: mdbox .../storage: rebuilding indexes doveadm($USER): Error: mdbox .../storage: Duplicate GUID $G in m.$N1:$N2 (size=$N3) and m.$N1:$N2 (size=$N3) doveadm($USER): Warning: fscking index file .../storage/dovecot.map.index doveadm($USER): Warning: mdbox .../storage: Inconsistency in map index ($X,$Y1 != $X,$Y3) doveadm($USER): Warning: fscking index file .../storage/dovecot.map.index doveadm($USER): Warning: fscking index file .../storage/dovecot.map.index Different numbers are represented by different $variables, e.g. $N3 != $M3 and $Y2 != $Y3. How can I fix this? Since the two messages are not the same (they have different sizes), I would expect a cleanup operation to give each message a unique GUID and write both GUIDs into all places where the old GUID was referenced. I am using Dovecot 2.2.31. Please CC me, since I am not on the list. Best regards, Dennis

1 1

dmarc report faild ?
by Maurizio Caloro 24 Aug '17

24 Aug '17

Hello Together Please i have new following Error, from DMARC Report, if i check my domain on example mxtoolbox i dont see any problems. Any from you know this Eror report, what i need to do to fix this issue? C:\folder>nslookup 94.237.32.243 Server: dns204.data.ch Address: 211.232.23.124 Name: wursti.dovecot.fi Address: 94.237.32.243 -- I check also dkim and spif but i don't see the mistake, i dont want that me Mailserver become seriussly mail problems. Regards Mauri <?xml version="1.0" encoding="UTF-8" ?> <feedback> <report_metadata> <org_name></org_name> <email>mreport(a)vmfacility.fr</email> <report_id>caloro.ch:1503564302</report_id> <date_range> <begin>1503477902</begin> <end>1503564302</end> </date_range> </report_metadata> <policy_published> <domain>caloro.ch</domain> <adkim>s</adkim> <aspf>s</aspf> <p>none</p> <sp>none</sp> <pct>100</pct> </policy_published> <record> <row> <source_ip>94.237.32.243</source_ip> <count>1</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>fail</spf> </policy_evaluated> </row> <identifiers> <header_from>caloro.ch</header_from> </identifiers> <auth_results> <spf> <domain>dovecot.org</domain> <result>unknown</result> </spf> <dkim> <domain>caloro.ch</domain> <result>pass</result> </dkim> </auth_results> </record> </feedback>

4 6

dovecot umask for mail boxes
by vadim 24 Aug '17

24 Aug '17

I want to control the mode of newly created boxes. The official documentation here: https://wiki.dovecot.org/SharedMailboxes/Permissions , under Permissions for new mailboxes says this: "When creating a new mailbox, Dovecot copies the permissions from the mailbox root directory. For example with mboxes if you have directories" But it seems to be untrue. I checked it, it soesn't work. I found a topic in mail list archive: https://dovecot.org/list/dovecot/2008-September/033395.html Its recommended to create a 'dovecot-shared' file in each mailbox with proper rights. But how can I do that if mailbox is not exists yet ? Can you provide any working solution to this problem ? -- С уважением, Бажов Вадим, Инженер отдела технической поддержки, Компания «Айдеко» -- Телефоны: +7 (495) 987-32-70; +7 (495) 662-87-34 (тех. поддержка); +7 (343) 220-77-55; Факс: +7 (343) 220-77-85 Электронная почта: Вопросы по приобретению: sales(a)ideco.ru Технические вопросы: support(a)ideco.ru Сайт: http://ideco.ru Форум: http://forum.ideco.ru

2 1

doveadm client not compatible with this server (mixed old and new binaries?)
by Kevin Golding 24 Aug '17

24 Aug '17

I'm getting the error "doveadm(10.0.0.10): Error: ddoveadm client not compatible with this server (mixed old and new binaries?)" on the source server (10.0.05) when trying to sync with a new destination server and I feel the error seems very obvious and self-explanatory except for one small thing - both servers claim to be the same version dovecot -n reports: Source (10.0.0.5): # 2.2.31 (65cde28): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: FreeBSD 11.1-RELEASE-p1 amd64 Destination (10.0.0.10): # 2.2.31 (65cde28): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: FreeBSD 11.1-RELEASE-p1 amd64 The only difference between the two outputs of dovecot -n are the mail_replica host (which are set to each other) and the ssl_cert location (which have their own domain names in the path). Replication is set to use tcp and the ports and passwords match. I was wondering if it's something they may depend on but the ones I'm aware cause most problems in general (libressl-2.5.5 and maridb-client-10.1.26) match. Any pointers that can be offered would be appreciated because I feel I'm missing something obvious. TIA Kevin

2 2

maildir boxes directory mode upon creation
by vadim 24 Aug '17

24 Aug '17

Hello, list ! Dovecot version is 2.2.27, running on Centos 6.7. Postfix is receiving mail and putting it into mailboxes. Dovecot just serves IMAP/POP3 connections to mailboxes. Virtual users are stored in DB. The problem is in directory mode (and thus file mode) for new mailboxes upon it's creation. If I create new record for new mailbox in DB and send mail to it, Postfix will create mailbox properly: Mode is 660, owner is imap:mail in my setup. If I create new record in DB and log in via IMAP for the first time, Dovecot creates mailbox and mode is 600, owner is imap:mail. Postfix cant put mails in tmp or new dirs in mailboxes created by dovecot with mode 600. I need dovecot to create new mailboxes (and files in it) within 660 mode. I tried to play around with "mail_access_groups" and "mail_privileged_group" wih no positive effect. I tried to change value for every "mode=" parameter in dovecot.conf to 660, but no luck. According to the documentation "Dovecot copies the permissions from the mailbox root directory". My mail_location is maildir:/var/mail/%u Rights for /var/mail/ (the root mail dir) are: [root@unknown-external-domain ~]# ls -lha /var/mail/ total 24K drwxrwx--- 5 postfix mail 4,0K Авг 23 14:27 . drwxrwxr-x 6 root root 4,0K Июл 29 12:18 .. drwx------ 6 imap mail 4,0K Авг 23 14:28 Administrator But, as you can see, Administrator's box was created by dovecot with 600 permissions. I am unable to enforce dovecot to create mailboxes with 660 permissions. Output of dovecot -n is in the attachment. Please tell me what's the right way to control mailbox permissions ? -- С уважением, Бажов Вадим, Инженер отдела технической поддержки, Компания «Айдеко» -- Телефоны: +7 (495) 987-32-70; +7 (495) 662-87-34 (тех. поддержка); +7 (343) 220-77-55; Факс: +7 (343) 220-77-85 Электронная почта: Вопросы по приобретению: sales(a)ideco.ru Технические вопросы: support(a)ideco.ru Сайт: http://ideco.ru Форум: http://forum.ideco.ru

2 3

Re: user data transfer when migrating to new server
by Joseph Tam 24 Aug '17

24 Aug '17

voytek(a)sbt.net.au writes: > I've tried imapsync, that seems to work well, but, what options do I have > for doing accounts or domains where I don't know user's password ? It depends on whether you're copying from an existing dovecot you control, but you can use the master password extension user={user}*{masterid}, password={masterppassword} in place of {user}/{userpasswqord} for imapsync to get the job done. Joseph Tam <jtam.home(a)gmail.com>

1 0

store into mailbox 'Junk' aborted
by kenneth topp 23 Aug '17

23 Aug '17

Hi, I've just switch from procmail to pigeonhole, and I'm seeing an issue (twice in six hours). I have spamassisn running via postfix milter, and dropping off via main.cf "mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp" The issue is that I get a sequence of these log messages: Aug 21 19:43:59 lmtp(toppk): Debug: Junk: Mailbox opened because: lib-lda delivery Aug 21 19:43:59 lmtp(toppk): Debug: $MAILDIR/Junk: Mailbox opened because: lib-lda delivery Aug 21 19:43:59 lmtp(toppk): Debug: Mailbox <lmtp DATA>: Opened mail UID=1 because: copying Aug 21 19:43:59 lmtp(toppk): Debug: Mailbox <lmtp DATA>: Opened mail UID=1 because: virtual size (Cache file is unusable) Aug 21 19:43:59 lmtp(toppk): Info: YK1SNj9wm1kMaQAAjC58EQ: sieve: msgid=<E1cxyRv-000F7r-E9@tra-vmail-01>: store into mailbox 'Junk' aborted Aug 21 19:43:59 lmtp(toppk): Debug: INBOX: Mailbox opened because: lib-lda delivery Aug 21 19:43:59 lmtp(toppk): Debug: Mailbox <lmtp DATA>: Opened mail UID=1 because: copying Aug 21 19:43:59 lmtp(toppk): Info: YK1SNj9wm1kMaQAAjC58EQ: sieve: msgid=<E1cxyRv-000F7r-E9@tra-vmail-01>: stored mail into mailbox 'INBOX' Aug 21 19:43:59 lmtp(toppk): Info: YK1SNj9wm1kMaQAAjC58EQ: sieve: Execution of script /home/toppk/.dovecot.sieve failed, but implicit keep was successful (user logfile /home/toppk/.dovecot.sieve.log may reveal additional details) and in /home/toppk/.dovecot.sieve.log I get this: sieve: info: started log at Aug 21 19:43:59. error: msgid=<E1cxyRv-000F7r-E9@tra-vmail-01>: failed to store into mailbox '$MAILDIR/Junk': Mailbox doesn't exist: $MAILDIR/Junk. So instead of the email going into mbox /home/toppk/mail/Junk it goes into INBOX (/var/mail/toppk). I'm watching the Junk to see if is removed for even a split second and I don't see that. I'm not sure how to further track this down, or if there is a more optimal configuration (i'd prefer to stay mbox if possible). I was thinking of turning on mailbox_list_index. Below is the full doveadm -n output. Any guidance or suggestions welcome. Ken # 2.2.31 (65cde28): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: Linux 4.12.4-300.fc26.x86_64 x86_64 Fedora release 26 (Twenty Six) auth_debug = yes auth_username_format = %Ln log_path = /var/log/dovecot.log mail_debug = yes 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 index ihave duplicate mime foreverypart extracttext 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 } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_default = /etc/dovecot/sieve/default.sieve } protocols = imap lmtp sieve service auth { unix_listener auth-client { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = mail mode = 0660 user = mail } user = root } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 1024 } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2 ssl_key = # hidden, use -P to show it userdb { driver = passwd } verbose_ssl = yes protocol lmtp { mail_plugins = " sieve" } protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log } protocol sieve { info_log_path = /var/log/dovecot-sieve.log log_path = /var/log/dovecot-sieve-errors.log mail_max_userip_connections = 10 managesieve_implementation_string = Dovecot Pigeonhole managesieve_max_line_length = 65536 }

4 4

imapsieve: failed to read mailbox attribute
by Darac Marjal 23 Aug '17

23 Aug '17

Hello all, Hopefully this is something fairly simple. I've been trying to set up the Sieve Antispam system as detailed at https://wiki2.dovecot.org/HowTo/AntispamWithSieve, but at the moment, whenever I change mailboxes I get the following message logged: Aug 22 09:30:45 remy dovecot: imap(darac(a)darac.org.uk): Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script mailbox attribute and my script does not run when I move files between folders. My sieve files are chmod'ed 0644 and the shell script used to pipe into spamassassin is 0755, so it *should* work, shouldn't it? Is there something I've missed? -- For more information, please reread.

3 4

Patch: acl list from ldap must be possible to have multiple values, that combined in one comma separated list
by DaLiV 23 Aug '17

23 Aug '17

diff to dovecot-2.2.31 hardcoded userdb_acl_groups /as currently not seeing any other fields that need similar way/ in ldap using dynlist - labeledURIObject - some attribute labeledURI :: ldap:///ou=DovecotGroups,dc=DOMAIN,dc=TLD,dc=root?specName?sub?(&(objectclass=posixgroup)(memberuid=XXXXX)) that returns groupnames for each user that he belongs, but as multiple values of same field ... must combine all in one CSV list diff -upbBr src/auth/passdb-ldap.c src/auth/passdb-ldap.c --- src/auth/passdb-ldap.c 2017-06-26 13:29:36.000000000 +0200 +++ src/auth/passdb-ldap.c 2017-08-22 09:56:59.697420441 +0200 @@ -52,13 +52,27 @@ ldap_query_save_result(struct ldap_conne auth_request_set_null_field(auth_request, name); continue; } + if (strcmp(name,"userdb_acl_groups")==0) { + int i = 1; + while (values[i] != NULL) { + strcat(values[0],","); + strcat(values[0],values[i]); + i++; + } + auth_request_log_warning(auth_request,AUTH_SUBSYS_DB, + "Multiple values found for '%s', " + "using combined value '%s'", name, values[0]); + auth_request_set_field(auth_request, name, values[0], + conn->set.default_pass_scheme); + } else { if (values[1] != NULL) { auth_request_log_warning(auth_request, AUTH_SUBSYS_DB, "Multiple values found for '%s', " "using value '%s'", name, values[0]); } auth_request_set_field(auth_request, name, values[0], conn->set.default_pass_scheme); } + } db_ldap_result_iterate_deinit(&ldap_iter); }

2 1

user data transfer when migrating to new server
by voytek＠sbt.net.au 23 Aug '17

23 Aug '17

I;m setting up new server, what are the options for transferring user's mail ? I've tried imapsync, that seems to work well, but, what options do I have for doing accounts or domains where I don't know user's password ? last time I've done, some users had lengthy period of re downloading 'old' mails from new server, is there a way to overcome this ? thanks, V

3 2

v2.2.32 release candidate 2 released
by Timo Sirainen 23 Aug '17

23 Aug '17

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc2.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc2.tar.gz.sig A couple of changes since rc1: + Added apparmor plugin. See https://wiki2.dovecot.org/Plugins/Apparmor - director: v2.2.31 caused rapid reconnection loops to directors that were down. Also this was already in rc1's list of changes, but wasn't actually in rc1 yet: - dict-ldap: %variable values used in the LDAP filter weren't escaped. Plus a few other smaller fixes.

4 3

Re: pop 110/995, imap 143/993 ?
by Joseph Tam 23 Aug '17

23 Aug '17

Robert Wolf wrote: >> else (NOT LOCALHOST) and you can see it says LOGINDISABLED unless you >> have enabled something like cram-md5. > > Hi, > > exactly, this is the reason, why plain-text is still needed. You don't need > encryption for authentication, if you have secure authentication. Without > knowing original password, the MITM cannot generate correct hash for login, so > the connection can be plain-text. You don't need plaintext to use CRAM-MD5: there's no problem have *both* CRAM-MD5 and SSL (it's overkill, but works). And mail data is worth protecting too. > Of cource, if you then download your emails, the MITM can still read these > emails too, if these emails are plain-text (not encrypted using e.g. SMIME or > GPG). But he cannot misuse your login. No argument here about using end-to-end encryption, but protecting mail data and metadata is important too. Don't forget also, it's not just about the privacy (reading) of mail data, but it's also important to guarantee the authenticity of mail data from tampering. By the way, if we assume a hostile network where MITM is possible, then even closing STARTTLS ports will not guarantee confidential transport: the MITM attacker can merely open up a fake plaintext-only service port, then proxy that to the target server. The client must deny non-secured transport to be fully protected. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: pop 110/995, imap 143/993 ?
by Joseph Tam 22 Aug '17

22 Aug '17

Lest anyone think STARTTLS MITM doesn't happen, https://threatpost.com/eff-calls-out-isps-modifying-starttls-encryption-com… Not only for security, I prefer port 993/995 as it's just plain simpler to initiate SSL from the get-go rather than to do some handshaking that gets you to the same point. Joseph Tam <jtam.home(a)gmail.com>

7 10

LMTP and Postfix
by Jerry 22 Aug '17

22 Aug '17

I am setting up a new system that will be using Dovecot with Postifx. I am planning on using LMTP. I read the wiki and and found the settings I need to make in Dovecot and the Postfix main.cf file. However, I saw nothing about the Postfix master.cf file. Do I need to make and changes to it also? Thanks -- Jerry

3 2

Disconnected in APPEND depends on service_count?
by Hajo Locke 22 Aug '17

22 Aug '17

Hello, we have quite odd behaviour of dovecot under new OS. We use dovecot 2.2.18 for years under Ubuntu12 and Ubuntu14. Now we use Ubuntu16 and notice some strange errors. dovecot 2.2.18 is rather old, but runs reliable and we dont need newest features, so we packaged it again on Ubuntu16. For explanation: We use some own patches for dovecot and insert some functions in deb packages, so we want to reuse our code to minimize effort. Under ubuntu16 we see a lot of messages like this on high load servers: Aug 22 08:28:15 hostname dovecot: imap(username): Disconnected in APPEND (1 msgs, 0 secs, 8192/136342 bytes) in=8379 out=830 Aug 22 08:28:16 hostname dovecot: imap(username): Disconnected in APPEND (1 msgs, 0 secs, 8192/136342 bytes) in=8985 out=2931 Aug 22 08:42:58 hostname dovecot: imap(username): Disconnected in APPEND (1 msgs, 29 secs, 13139969/42801634 bytes) in=13140054 out=404 Aug 22 08:43:01 hostname dovecot: imap(username): Disconnected in APPEND (1 msgs, 3 secs, 1286145/42801634 bytes) in=1286230 out=404 Aug 22 08:43:29 hostname dovecot: imap(username): Disconnected in APPEND (1 msgs, 2 secs, 704476/42801634 bytes) in=704561 out=404 Aug 22 08:44:29 hostname dovecot: imap(username): Disconnected in APPEND (1 msgs, 60 secs, 27402241/42801634 bytes) in=27402326 out=404 Aug 22 08:45:30 hostname dovecot: imap(username): Disconnected in APPEND (1 msgs, 3 secs, 1458177/42801634 bytes) in=1458262 out=404 Aug 22 08:46:15 hostname dovecot: imap(username): Disconnected in APPEND (1 msgs, 45 secs, 20594652/42801634 bytes) in=20594737 out=404 Aug 22 08:47:38 hostname dovecot: imap(username): Disconnected in APPEND (1 msgs, 11 secs, 4907009/42801634 bytes) in=4907094 out=404 Error occured after sending a mail, when client tries to save sent mail in sent-messages folder. (mbox) Typically this is a client problem caused by firewall/virusguard or network erros. But we saw that many different users are effected and we could reproduce this behaviour on clean clients. In our logs and systemd journal we had no hints leading to other error-messages, no dovecot message which tells that limit xy was reached. Also no hints for other malfunctioning services. No helpful lines with mail_debug=yes We tried a lot and it seems that changing "service_count = 0" to "service_count = 1" is part of solution. After changing and restarting the behaviour is like expected. old: service imap-login { executable = /usr/lib/dovecot/imap-login process_min_avail = 1 service_count = 0 user = dovecot } new: service imap-login { executable = /usr/lib/dovecot/imap-login process_min_avail = 1 service_count = 1 user = dovecot process_limit = 10000 } service_count switches between number of handled client-connections. i dont see a relation between service_count and the permanent disconnects but it seems to be part of problem. Can anybody explain this behaviour or give some handy tips? Thanks, Hajo

1 0

Re: pop 110/995, imap 143/993 ?
by Robert Wolf 22 Aug '17

22 Aug '17

On Tue, 22 Aug 2017, Ivan Warren wrote: > Le 8/22/2017 à 10:03 AM, Robert Wolf a écrit : > > > > WRONG!!! The email is stored plain-text on the first server and then it can > > be > > sent to other few MX servers over plain-text connection. I.e. encrypted > > connection does not protect emails, but the authentication credentials. > > > > > Indeed. > > Encrypted (SSL/TLS) SMTP/IMAP/POP3 sessions only server 1 purpose : To encrypt > authentication. Once a message is sent through a MTA, there is no guarantee of > privacy whatsoever. > > End to End privacy can only be achieved through actual e-mail signing and > encryption (PGP, S/MIME) (but only the message body is encrypted, not the > headers). Hello Ivan yes, headers are not encrypted in plain-text SMTP, the same way as TCP and IP and DNS Requests are not encrypted. One can only hide behind some anonymization system (TOR, Proxy, VPN for TCP, IP, DNS) or some non-presonal mail system to anonymize mail headers to not be able to connect real persones with mail sender/recipient. Regards, Robert.

1 0

Re: pop 110/995, imap 143/993 ?
by Joseph Tam 22 Aug '17

22 Aug '17

Gary <lists(a)lazygranch.com> writes: > If I read this correctly, starttls will fail due to the MITM attack. > That is the client knows security has been compromised. I'm not sure what you man by "fail". STARTTLS is prone to MITM attacks if a client has not been configured to refuse non-STARTTLS/SSL sessions. For clients that will allow both secured and plaintext session (like most MTAs), an attacker can strip out the server's STARTTLS capability declaration and fool the client into using an unencrypted session. > Using SSL/TLS, the MITM can use SSL stripping. Since most Postifx conf > use "may" for security, the message would go though unencrypted. > Correct??? If it's what I described above, then yes. > Is there something to enable for perfect forward security with starttls? PFS is enabled using a particular choice of encryption algorithms (in particular, use of ephememeral keys algorithms like ECDHE-*), but this happens after SSL initiaton, whether by STARTTLS, or by connection to SSL ports. Joseph Tam <jtam.home(a)gmail.com>

1 0

Domain without certificate
by Andreas Meyer 22 Aug '17

22 Aug '17

Hello! I have a new domain integrated into dovecot but no certificate yet. In dovecot.conf there is ssl = yes and the other domains have certificates configured. How do I exclude this new domain from using SSL? Greetings Andreas

1 1

pop 110/995, imap 143/993 ?
by voytek＠sbt.net.au 21 Aug '17

21 Aug '17

just setting a new Dovecot server to migrate from older system, but, I have a general question: 1. I've set the server with self issued cert, and both pop/imap StartTLS/110/143 SSL/993/995 (apologies if I'm using wrong naming terminology) is there a 'preferred way'? should I tell users to use 143 over 993 ? or 993 over 143? or? my current understanding is that some (MS?) clients might not support StartTLS/143 ? so best to offer both ? I think? some public WiFi block 993/995 but allow 143/110, hence, another advantage for using 143/110 thanks for any advice, V

6 11

Permission denied to access the email file
by ATHANASE Jean-René 21 Aug '17

21 Aug '17

Hi, Dovecot version : 2.2.22 (fe789d2) Operating system : DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" CPU architecture : Linux 4.4.67-1-pve #1 SMP PVE 4.4.67-92 (Fri, 23 Jun 2017 08:22:06 +0200) x86_64 GNU/Linux FIle system : local UID GID Aug 17 11:47:28 azizee dovecot: imap(jra11[*5063*:*5011*]): Debug: Effective uid=5063, gid=5011, home=/var/spool/domaines/vitalnet/jra/ Aug 17 11:47:28 azizee dovecot: imap(jra11[5063:5011]): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/var/spool/domaines/vitalnet/jra/ Aug 17 11:47:28 azizee dovecot: imap(jra11[5063:5011]): Debug: maildir++: root=/var/spool/domaines/vitalnet/jra, index=, indexpvt=, control=, inbox=/var/spool/domaines/vitalnet/jra, alt= Aug 17 11:47:28 azizee dovecot: imap(jra11[5063:5011]): *Error*: open(/var/spool/domaines/vitalnet/jra/cur/1502890181.V704I34050fM371072.azizee:2,) failed: *Permission denied* (euid=*5063*(<unknown>) egid=*5011*(<unknown>) missing +r perm: /var/spool/domaines/vitalnet/jra/cur/1502890181.V704I34050fM371072.azizee:2,) Ldap configuration : user_attrs = uid=user,userPassword=password,homeDirectory=home,uidNumber=uid,gidNumber=gid ll /var/spool/domaines/vitalnet/jra/cur/1502890181.V704I34050fM371072.azizee\:2\, -rw------- 1 5095 5011 438 Aug 16 15:29 /var/spool/domaines/vitalnet/jra/cur/1502890181.V704I34050fM371072.azizee:2, If I set with the command line "chmod g=rw /var/spool/domaines/vitalnet/jra/cur/1502890181.V704I34050fM371072.azizee\:2\,", this file email is treated by Dovecot, per example, i have deleted it. ll /var/spool/domaines/vitalnet/jra/cur/1502890181.V704I34050fM371072.azizee\:2\,ST -rw-rw---- 1 5095 5011 438 Aug 16 15:29 /var/spool/domaines/vitalnet/jra/cur/1502890181.V704I34050fM371072.azizee:2,ST What's the problem of my configuration ? Best regards,

2 1

ot: self certified enduser browser/mail client install?
by voytek＠sbt.net.au 21 Aug '17

21 Aug '17

I have self certified Dovecot as so: ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } in order for end user to avoid webmail warnings or email client warnings, do I make this file /etc/pki/dovecot/certs/dovecot.pem available to users say under httpd://webhost/tld/certificate/dovecot.pem and, tell users to import dovecot.pem (from /etc/pki/dovecot/certs/dovecot.pem) into their PC/browser/mailclient certs? (sorry for dumb Q, but I thought I should ask before I commit some fundamental stuffup)

3 2

Re: is a self signed certificate always invalid the first time
by Joseph Tam 21 Aug '17

21 Aug '17

Michael Felt <michael(a)felt.demon.nl> writes: >> I use acme.sh for all of my LetsEncrypt certs (web & mail), it is >> written in pure shell script, so no python dependencies. >> https://github.com/Neilpang/acme.sh > > Thanks - I might look at that, but as Ralph mentions in his reply - > Let's encrypt certs are only for three months - never ending circus. I wouldn't characterize it as a circus. Once you bootstrap your first certificate and install the cert-renew cron script, it's not something you have to pay a lot of attention to. I have a few LE certs in use, and I don't think about it anymore: it just works. The shorter cert lifetime also helps limit damage if your certificate gets compromised. Joseph Tam <jtam.home(a)gmail.com>

10 14

\Noselect isn't set on namespace prefix mailbox that can't be selected
by David Mandelberg 19 Aug '17

19 Aug '17

Hi, I tried using Nextcloud's Mail app to access my dovecot server (version: 2.2.27 (c0f36b0)), and got an error. The relevant imap log is: C: 3 LIST () "" (*) RETURN (SPECIAL-USE) ... S: * LIST () "/" Archives ... C: 6 STATUS Archives (MESSAGES) S: 6 NO Mailbox isn't selectable (0.000 + 0.000 secs). >> Command 6 took 0.0014 seconds. C: 7 LOGOUT S: * BYE Logging out S: 7 OK Logout completed (0.000 + 0.000 secs). >> Command 7 took 0.0021 seconds. And the relevant part of my dovecot config: namespace archives { disabled = no hidden = no ignore_on_failure = no inbox = no list = yes location = mbox:~/.mbox-archives order = 0 prefix = Archives/ separator = / subscriptions = yes type = private } Since ~/.mbox-archives is a directory, not a regular file, I'd expect dovecot to set the \Noselect attribute on the Archives folder. Is there something I'm missing? I tried using special_use, but that didn't accept \Noselect as an option.

1 0

Re: Dovecot mail_location for fedora
by Joseph Tam 19 Aug '17

19 Aug '17

>> mail_location=~/.mail:INBOX=/var/spool/mail/%Ln > > He should be good now, no idea why a fedora install wouldn't have that Unless I missed something in a previous pst, "~/.mail" is not typical for personal mail folder, but "~/mail" is. Joseph Tam <jtam.home(a)gmail.com>

2 1

Inconsistency in map index
by Webert de Souza Lima 18 Aug '17

18 Aug '17

Hello, The following errors are constantly popping up for 2 accounts. I can't get it fixed, I did doveadm backup to another account, the same happens in the new account. I did doveadm force-resync, the problem persists. I'm using dovecot 2.2. 2017-08-18T11:46:12.472821881Z Aug 18 11:46:12 lmtp(ramon.lacerda(a)alliar.com): Warning: mdbox /srv/dovecot2/mail/alliar.com/ramon.lacerda/storage: Inconsistency in map index (647,6288 != 647,28333584) 2017-08-18T11:46:12.651002372Z Aug 18 11:46:12 lmtp(ramon.lacerda(a)alliar.com): Warning: mdbox /srv/dovecot2/mail/alliar.com/ramon.lacerda/storage: Inconsistency in map index (647,6288 != 647,28333708) 2017-08-18T11:46:12.651059432Z Aug 18 11:46:12 lmtp(ramon.lacerda(a)alliar.com): Warning: fscking index file /srv/dovecot2/index/ alliar.com/ramon.lacerda/storage/dovecot.map.index 2017-08-18T11:46:12.764926940Z Aug 18 11:46:12 lmtp(ramon.lacerda(a)alliar.com): Warning: mdbox /srv/dovecot2/mail/alliar.com/ramon.lacerda/storage: rebuilding indexes Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil*

3 5

Install locks up my server
by Marc Perkel 18 Aug '17

18 Aug '17

Ever since 2.26 I haven't been able to upgrade. In fact the install locks up my server. I get into and infinite recursive loop where the config-guess program calls itself until the server locks up from overload. I'm running Centos 6 under OpenVZ. What am I missing? I think there's a serious bug. 31233 pts/3 S 0:00 /bin/sh ./config.guess 31235 pts/3 S 0:00 \_ /bin/sh ./config.guess 31238 pts/3 S 0:00 \_ /bin/sh ./config.guess 31240 pts/3 S 0:00 \_ /bin/sh ./config.guess 31241 pts/3 S 0:00 \_ /bin/sh ./config.guess 31267 pts/3 S 0:00 \_ /bin/sh ./config.guess 31272 pts/3 S 0:00 \_ /bin/sh ./config.guess 31279 pts/3 S 0:00 \_ /bin/sh ./config.guess 31280 pts/3 S 0:00 \_ /bin/sh ./config.guess 31281 pts/3 S 0:00 \_ /bin/sh ./config.guess 31283 pts/3 S 0:00 \_ /bin/sh ./config.guess 31284 pts/3 S 0:00 \_ /bin/sh ./config.guess 31285 pts/3 S 0:00 \_ /bin/sh ./config.guess 31292 pts/3 S 0:00 \_ /bin/sh ./config.guess 31303 pts/3 S 0:00 \_ /bin/sh ./config.guess 31304 pts/3 S 0:00 \_ /bin/sh ./config.guess 31305 pts/3 S 0:00 \_ /bin/sh ./config.guess 31306 pts/3 S 0:00 \_ /bin/sh ./config.guess 31307 pts/3 S 0:00 \_ /bin/sh ./config.guess 31321 pts/3 S 0:00 \_ /bin/sh ./config.guess 31340 pts/3 S 0:00 \_ /bin/sh ./config.guess 31341 pts/3 S 0:00 \_ /bin/sh ./config.guess 31426 pts/3 S 0:00 \_ /bin/sh ./config.guess 31530 pts/3 S 0:00 \_ /bin/sh ./config.guess

2 4

/var/run/dovecot permission issues
by Matt Simpson 18 Aug '17

18 Aug '17

I have an issue that surfaced when I tried to start using the new metrics service, but it looks like it may be a more generic issue. When I enabled stats and started dovecot, I got the following error in the log: Error: stats: open(/var/run/dovecot/stats-mail) failed: Permission denied /var/run/dovecot/stats-mail did not exist. /var/run/dovecot/ existed, owned by root, which apparently was preventing dovecot from creating stats-mail. On advice from another list subscriber, I changed the ownership of /var/run/dovecot to the dovecot user. This doesn’t help. Apparently /var/run/dovecot is deleted by dovecot when it shuts down, and recreated, with root ownership, when it restarts. stats-mail is created, with root ownership. Is there something I need to change to prevent dovecot from creating this directory owned by root? I was unaware of any problems before trying to enable stats, but the ownership of files in that directory is a mixed bag $ ls -l /var/run/dovecot total 20 srw------- 1 root wheel 0 Aug 17 09:05 anvil srw------- 1 root wheel 0 Aug 17 09:05 anvil-auth-penalty srw------- 1 dovecot wheel 0 Aug 17 09:05 auth-client srw------- 1 dovecot wheel 0 Aug 17 09:05 auth-login srw-rw---- 1 alias qnofiles 0 Aug 17 09:05 auth-master -rw------- 1 root wheel 32 Aug 17 09:05 auth-token-secret.dat srw-rw-rw- 1 dovecot wheel 0 Aug 17 09:05 auth-userdb srw------- 1 dovecot wheel 0 Aug 17 09:05 auth-worker srw------- 1 root wheel 0 Aug 17 09:05 config srw------- 1 root wheel 0 Aug 17 09:05 dict srw------- 1 root wheel 0 Aug 17 09:05 dict-async srw------- 1 root wheel 0 Aug 17 09:05 director-admin srw-rw-rw- 1 root wheel 0 Aug 17 09:05 dns-client srw------- 1 root wheel 0 Aug 17 09:05 doveadm-server lrwx------ 1 root wheel 35 Aug 17 09:05 dovecot.conf -> /usr/local/etc/dovecot/dovecot.conf drwxr-xr-x 2 root wheel 512 Aug 17 09:05 empty srw------- 1 root wheel 0 Aug 17 09:05 imap-hibernate srw------- 1 root wheel 0 Aug 17 09:05 imap-master srw-rw-rw- 1 root wheel 0 Aug 17 09:05 imap-urlauth srw------- 1 dovecot wheel 0 Aug 17 09:05 imap-urlauth-worker srw-rw-rw- 1 root wheel 0 Aug 17 09:05 indexer srw------- 1 dovecot wheel 0 Aug 17 09:05 indexer-worker srw------- 1 root wheel 0 Aug 17 09:05 ipc srw------- 1 root wheel 0 Aug 17 09:05 log-errors drwxr-x--- 2 root dovenull 512 Aug 17 09:05 login srw------- 1 root wheel 0 Aug 17 09:05 master -rw------- 1 root wheel 6 Aug 17 09:05 master.pid srw------- 1 root wheel 0 Aug 17 09:05 replication-notify prw------- 1 root wheel 0 Aug 17 09:05 replication-notify-fifo srw------- 1 dovecot wheel 0 Aug 17 09:05 replicator srw-rw-rw- 1 root wheel 0 Aug 17 09:05 ssl-params srw------- 1 root wheel 0 Aug 17 09:05 stats prw------- 1 root wheel 0 Aug 17 09:05 stats-mail prw------- 1 root wheel 0 Aug 17 09:05 stats-user drwxr-x--- 2 root dovenull 512 Aug 17 09:05 token-login $ doveconf -n # 2.2.31 (65cde28): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: FreeBSD 11.0-RELEASE-p9 amd64 auth_stats = yes auth_verbose = yes default_vsz_limit = 128 M lock_method = flock mail_location = maildir:~/Maildir mail_plugins = " stats" mail_privileged_group = mail 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 index ihave duplicate mime foreverypart extracttext vnd.dovecot.pipe vnd.dovecot.execute namespace inbox { inbox = yes location = prefix = } passdb { args = imap driver = pam } plugin { recipient_delimiter = - sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_bin_dir = /usr/local/lib/dovecot/sieve-pipe sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_pipe_bin_dir = /usr/local/lib/dovecot/sieve-pipe sieve_pipe_exec_timeout = 10s sieve_plugins = sieve_extprograms stats_refresh = 30s } protocols = imap service auth { unix_listener auth-master { group = qnofiles mode = 0660 user = alias } user = root } service imap-login { process_min_avail = 3 vsz_limit = 94 M } ssl_cert = </usr/local/etc/letsencrypt/live/dummy.redhorse.me/fullchain.pem ssl_cipher_list = EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 stats_carbon_name = RedHorseMail stats_carbon_server = [2a04:3542:1000:910:acc1:5bff:fe5e:8c2] syslog_facility = local0 userdb { driver = passwd } verbose_proctitle = yes protocol lda { mail_plugins = " stats sieve" }

4 5

Filter of old Thunderbird installation interferes with lmtp/ Mail delivery / sieve
by Jürgen Gmach 18 Aug '17

18 Aug '17

# 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 4.9.25 i686 Gentoo Base System release 2.2 # pidgeonhole v0.4.3 # Thunderbird 3.0.4 impact ------ Emails, for which the filter applies, gets copied to the desired folder, but get kept in the inbox with deleted flag (in Roundcube you see them grayed out a bit, in Thunderbird they are not shown at all). When the incoming email is from an internal mailing list (mailman), beginning with the user with the buggy Thunderbird all following emails of the internal users are flagged as deleted, but only if the user has a sieve file in their directory - no matter whether it is active or not. After activating detailed logging the user with the "problematic" filter was found quickly. The error is reproducible: - install old Thunderbird version - create filter - write an email, which triggers the filter -> email is flagged deleted but does not get deleted Though, the user does not have a sieve file on our server, the filtering happened in the very same second when the email was delivered to the other colleagues. Both Thunderbird and Pidgeonhole are outdated, so I am unsure if you are even interested in this bug report. Fix --- I made the user to update his Thunderbird version -> no more problems. Anyhow, a single "user interaction" should not be able to effect other mail accounts (ie Thunderbirds filter somehow disturbed the lmtp process). -- Jürgen Gmach . juergen.gmach(a)apis.de . +49 9482 941545 APIS Informationstechnologien GmbH . http://www.apis.de Gewerbepark A 13, 93086 Wörth/Donau . Deutschland Sitz der GmbH: Wörth/Donau, Amtsgericht Regensburg (HRB 6684) Geschäftsführer: Julia Anna Dietz, Jürgen Eilers, Peter Rosenbeck

1 0