November 2018 - dovecot

Re: The SSL certificate of repo.dovecot.org has expired.
by Tuomi, Aki 10 Nov '18

10 Nov '18

Yes. Sorry about this.Sent from my Samsung Galaxy smartphone. -------- Original message --------From: Masaki Nemoto <itml(a)ma3ki.net> Date: 11/11/2018 10:00 (GMT+02:00) To: dovecot(a)dovecot.org Subject: The SSL certificate of repo.dovecot.org has expired. HiThe SSL certificate of https://repo.dovecot.org has expired.Do you have plans to update it?

2 1

after reboot listen(*, 995) failed: Address already in use/listen(*, 993) failed: Address already in use
by Robert Kudyba 09 Nov '18

09 Nov '18

This is still happening after a reboot, Fedora 28. Restarting dovecot fixes the problem. Does anyone know if it could be related to this bug report? *https://bugzilla.redhat.com/show_bug.cgi?id=103401#c130 <https://bugzilla.redhat.com/show_bug.cgi?id=103401#c130> * and suggested work around to add ports to /proc/sys/net/ipv4/ip_local_reserved_ports? Nov 8 12:21:41 ourdomain dovecot[1386]: Error: service(pop3-login): listen(*, 995) failed: Address already in use Nov 8 12:21:41 ourdomain dovecot[1386]: Error: service(pop3-login): listen(::, 995) failed: Address already in use Nov 8 12:21:41 ourdomain dovecot[1386]: Error: service(imap-login): listen(*, 993) failed: Address already in use Nov 8 12:21:41 ourdomain dovecot[1386]: Error: service(imap-login): listen(::, 993) failed: Address already in use dovecot --version 2.2.36 (1f10bfa63) dovecot -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # OS: Linux 4.18.16-200.fc28.x86_64 x86_64 Fedora release 28 (Twenty Eight) # Hostname: ourdomain.com auth_debug = yes debug_log_path = /var/log/dovecot-debug.log mail_debug = yes 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 } ssl = required ssl_cert = </etc/letsencrypt/live/ourdomain.com/fullchain.pem ssl_cipher_list = PROFILE=SYSTEM ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol imap { mail_location = mbox:~/mail:INBOX=/var/mail/%u

3 2

Strange log message with dovecot-2.3.3
by Christian Pélissier 08 Nov '18

08 Nov '18

Hi, # dovecot --version 2.3.3 (dcead646b) # doveinfo Nombre d'utilisateurs : 1151 Sockets IMAP : 4356 Process dovecot/imap : 4357 Process dovecot/imap-login : 1339 Process dovecot/pop3 : 0 Process dovecot/pop3-login : 0 Process dovecot/auth : 1 Process dovecot/auth -w : 2 Process dovecot/anvil : 1 Process dovecot/log : 1 Process dovecot/config : 1 Process dovecot/stats : 1 Since I am using dovecot 2.3.X I got the following messages /var/log/dovecot-20180930:Sep 28 17:33:38 balcha dovecot: master: Warning: service(stats): client_limit (1000) reached, client connections are being dropped Users complain the system became slow. I happen when dovecot/imap process grows above 1000. With 2.2.X no default were defined (#default_client_limit = 1000) and I have no such log and no performance problems. With 2.3.3 I first increase default_client_limit to 4096 but the following message come again when dovecot/imap grow above 4096 ====== Nov 6 12:09:12 balcha dovecot: master: Warning: service(stats): client_limit (4096) reached, client connections are being dropped Nov 6 12:09:25 balcha dovecot: imap: Error: net_connect_unix(/var/run/dovecot//stats-writer) failed: Resource temporarily unavailable ... many same lines as above ====== Now 8192 solve my problem default_client_limit = 8192 I don't understand why the first Warning is related to service(stats) instead of service(imap) and why the socket stats-writer became temporarily unavailable # ls -l /var/run/dovecot/stats-writer srw-rw---- 1 root dovecot 0 Nov 8 02:44 /var/run/dovecot/stats-writer PS. # dovecot --version 2.3.3 (dcead646b) # dovecot -n # 2.3.3 (dcead646b): /usr/local/dovecot-2.3.3/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.3 (f018bbab) # OS: Linux 2.6.32-696.30.1.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.9 (Santiago) # Hostname: balcha.onera base_dir = /var/run/dovecot/ default_client_limit = 8192 <<< default with dovecot 2.2.X changed to 4096 then 8192 disable_plaintext_auth = no listen = * mail_location = maildir:~/Maildir:INDEX=~/Maildir:CONTROL=~/Maildir mail_plugins = quota 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 passdb { args = %s driver = pam } plugin { quota = maildir:User quota quota_grace = 6%% quota_rule = ?:storage=6G quota_rule2 = Trash:storage=+5%% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster(a)onera.fr quota_full_tempfail = yes rejection_reason = Votre message à <%t> est mis en attente; raison : %n% r rejection_subject = Message (Objet: %s) mis en attente de livraison service anvil { client_limit = 4299 } service auth { client_limit = 5320 } service imap-login { client_limit = 8192 process_limit = 4096 } service imap { process_limit = 8192 } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = root mode = 0666 user = root } user = root } ssl_cert = </usr/local/dovecot/etc/certs/dovecot.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local1 userdb { driver = passwd } protocol lda { mail_plugins = quota sieve } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_reuse_xuidl = yes } -- Christian Pélissier ONERA DSI/ISR BP72 92322 Chatillon CEDEX  34419

1 0

MailLog plugin distinguish between simultaneous logins
by azurit＠pobox.sk 07 Nov '18

07 Nov '18

Hi, is it, somehow, possible to distinguish between multiple simultaneous logins in MailLog plugin? For example, which login deleted which message. Is that p[lugin able to log e.g. session ID? azur

2 3

Dovecot mail-crypt plugin
by Anushka Uditha Bandara 07 Nov '18

07 Nov '18

I configured an email solution using dovecot and postfix and it is working fine. Now I am working for mail encryption. Is it enough to set below configurations on dovecot for mail encryption. Because dovecot wiki is little bit confusing to me. "mail_plugins = $mail_plugins mail_crypt mail_attribute_dict = file:%h/Maildir/dovecot-attributes plugin { mail_crypt_curve = <some curve you like> mail_crypt_save_version = 2 }" I am stuck in here. Thank you in advance, Anushka Bandara

2 9

LMTP with many aliases and replication
by Sean Greenslade 07 Nov '18

07 Nov '18

Hi, all. I'm currently in the process of rethinking / tinkering with my personal mail server. I've hit a few stumbling blocks that make me think I may be approaching this problem from the wrong angle. I have a large number of email addresses across several domains that all alias to the same inbox. In my current setup, postfix handles the aliases and dumps them all into a single "receiving" maildir, which gets processed by a custom python script to sort into one of several destination maildirs handled by dovecot. In evaluating this system, I'd like to move to using sieve for this sorting step, so (according to the docs) I need to use LMTP. This is my first stumble. Since I use so many aliases, my IMAP login username is not my email address. In fact, I have several IMAP usernames with different passwords pointing to the same maildir so that my phone can use a different password than my PC. The dovecot documentation was not very clear on how to make LMTP use a different userdb. I eventually found through some trial and error and some hints from other list threads that I could wrap a second userdb {} section with a protocol lmtp {} section, which seems to do the trick. I'd like to edit the wiki to include this helpful tidbit, but I find it odd that this isn't mentioned anywhere in the documentation for LMTP. Is it actually an intended feature? My second stumble is with the replicator plugin. I'd like to run two identical dovecot servers that replicate their mailboxes across each other. Since there are a large number of alias "accounts" that all feed into one IMAP account, the logical place to put the replication would be the IMAP account. But the way the replicator plugin seems to work, the trigger for synchronous replication on mail receipt fires on the LMTP "account" that received that particular message. Is there any way within dovecot to specify a different replication account to be triggered for sync? Like a userdb extra field or something? I'm trying to avoid needing external scripts if at all possible. I'm interested to hear people's thought / suggestions, especially if anyone has a better way of architecting this system. In case it's relevant, I'm running Arch Linux / Dovecot 2.3.3. Thanks, --Sean

1 0

Re: dovecot: imap Error: read : Broken pipe
by Carl St-Laurent 07 Nov '18

07 Nov '18

I forgot to mention that if I transfer the mail to my Gmail or Outlook address I can download the attachments without any problem. More over I've completely removed the firewall server from the equation, I plugged the adsl line directly into the mail server and the problem is still there, so my guess is that the firewall isn't the problem here. I'll do the pcaps for Aki Thanks for your help On 06/11/2018 02:20, dovecot-request(a)dovecot.org wrote: > 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. imap authentication - shadow vs mysql (Konra Wawryn) > 2. Re: imap authentication - shadow vs mysql (Ralph Seichter) > 3. Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)): > auth-client-connection.c:338 (Michael Slusarz) > 4. dovecot: imap Error: read : Broken pipe (Carl St-Laurent) > 5. Re: dovecot: imap Error: read : Broken pipe (Felipe Gasper) > 6. Re: dovecot: imap Error: read : Broken pipe (Aki Tuomi) > 7. Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)): > auth-client-connection.c:338 (Mart Pirita) > 8. Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)): > auth-client-connection.c:338 (Aki Tuomi) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 05 Nov 2018 13:45:48 +0100 > From: Konra Wawryn <konrad.wawryn(a)virtual-machine.org> > To: dovecot(a)dovecot.org > Subject: imap authentication - shadow vs mysql > Message-ID: <13e143d52fb2f094a285306ccbdec990(a)virtual-machine.org> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Hi, > > I`m looking for some opinions about authentication process for the > systems with more than 1000 E-mail accounts. > Maybe some one could advise me what is the best authentication method. > > At the moment I`m storing all passwords in my /etc/passwd. My IMAP > server is growing and I`m planning to build new host, my question is: > what is the best authentication model for IMAP server ? Do I need to > store all user/passwords in mysql or maybe in LDAP ? > > I`m searching for some solution which will help me to scale my system > in > the future. > > > Maybe some one could advice me ? > > > Greetings > > Konrad > > > ------------------------------ > > Message: 2 > Date: Mon, 05 Nov 2018 14:21:39 +0100 > From: Ralph Seichter <m16+dovecot(a)monksofcool.net> > To: dovecot(a)dovecot.org > Subject: Re: imap authentication - shadow vs mysql > Message-ID: <m2k1lrek2k.fsf(a)argon.seichter.de> > Content-Type: text/plain > > * Konra Wawryn: > >> I`m searching for some solution which will help me to scale my system >> in the future. > > You provided very little information about your requirements, and "to > scale" is just as vague a term. Hence, I recommend an LDAP server, > because it works in many scenarios, can accommodate thousands of users, > and is basically the default solution for this type of write-seldom- > read-often type of user data storage. > > As for MySQL, I would personally not use it for authentication unless I > had no other option. > > -Ralph > > > ------------------------------ > > Message: 3 > Date: Mon, 5 Nov 2018 10:42:14 -0700 (MST) > From: Michael Slusarz <michael.slusarz(a)open-xchange.com> > To: Mart Pirita <sysadmin(a)e-positive.ee>, dovecot(a)dovecot.org > Subject: Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)): > auth-client-connection.c:338 > Message-ID: <750544780.12327.1541439735168(a)appsuite.open-xchange.com> > Content-Type: text/plain; charset=UTF-8 > >> On November 3, 2018 at 9:41 AM Mart Pirita <sysadmin(a)e-positive.ee> >> wrote: >> >> >> Hi, >> >> >> But this harmless is spamming logs, so how to disable it: >> >> grep auth-client-connection.c:338 maillog | wc -l >> ?? 1259 > > If using something like rsyslog, it is trivial to filter out unwanted > entries. > > michael > > >> Aki Tuomi wrote: >> > > On 03 November 2018 at 12:12 Mart Pirita < sysadmin(a)e-positive.ee >> > > <mailto:sysadmin@e-positive.ee>> wrote: >> > > >> > > >> > > Hi, >> > > >> > > >> > > Noticed with latest v2.3.3 some new warning in logs, for example: >> > > >> > > dovecot: auth: Warning: Event 0x80a6fc0 leaked (parent=(nil)): >> > > auth-client-connection.c:338: 1 Time(s) >> > > dovecot: auth: Warning: Event 0x80aa1c8 leaked (parent=(nil)): >> > > auth-client-connection.c:338: 1 Time(s) >> > > dovecot: auth: Warning: Event 0x80aa718 leaked (parent=(nil)): >> > > auth-client-connection.c:338: 1 Time(s) >> > > dovecot: auth: Warning: Event 0x80adac0 leaked (parent=(nil)): >> > > auth-client-connection.c:338: 1 Time(s) >> > > dovecot: auth: Warning: Event 0x80b6c38 leaked (parent=(nil)): >> > > auth-client-connection.c:338: 1 Time(s) >> > > dovecot: auth: Warning: Event 0x80c0e00 leaked (parent=(nil)): >> > > auth-client-connection.c:338: 1 Time(s) >> > > dovecot: auth: Warning: auth client 0 disconnected with 1 pending >> > > requests: EOF: 12 Time(s) >> > > >> > > >> > > What are they? >> > > >> > > >> > > -- >> > > Mart >> > >> > Hi! It's harmless event leak. This is a known issue to us. > > > ------------------------------ > > Message: 4 > Date: Mon, 05 Nov 2018 18:19:26 -0500 > From: Carl St-Laurent <stlauca(a)a3d-concept.com> > To: dovecot(a)dovecot.org > Subject: dovecot: imap Error: read : Broken pipe > Message-ID: <1700cf4385e77a60415db96fa1c586ac(a)a3d-concept.com> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Hi everyone, > > I'm trying to find a solution for this bug who appears 2 months ago : > > dovecot: imap(%USER%): Error: read(<binary stream of mailbox INBOX UID > (%d)>) failed: Broken pipe (FETCH BINARY[2] for mailbox INBOX UID (%d) > > Where %USER% is the unix user and %d the UID of the mailbox. > > This error appears each time a user tries to download an attachment > from > one of his emails. Whether with RoundCube or Thunderbird via VPN or > not. > I thought that it was related to my firewall but no. Furthermore the > problem isn't present when users are at the office. Upload speed from > our ADSL connection is pretty slow about 1mpbs, I thought maybe it was > related but it was working fine since 2 years. So I'm really short of > ideas. > > Anyone could help me please ? > > Best regards, > Carl > > > # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.16 (fed8554) > # OS: Linux 4.9.0-7-amd64 x86_64 Debian 9.5 > auth_mechanisms = plain login > disable_plaintext_auth = no > mail_location = maildir:~/Maildir > namespace inbox { > inbox = yes > location = > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > mailbox Junk { > auto = subscribe > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > auto = subscribe > special_use = \Trash > } > prefix = > } > passdb { > driver = pam > } > plugin { > sieve = file:~/sieve;active=~/.dovecot.sieve > sieve_after = /etc/dovecot/sieve-after > } > protocols = imap imap > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > } > service imap-login { > inet_listener imap { > port = 0 > } > inet_listener imaps { > port = 993 > ssl = yes > } > } > ssl = required > ssl_ca = </etc/ssl/mail/****.pem > ssl_cert = </etc/ssl/mail/****.pem > ssl_key = # hidden, use -P to show it > userdb { > driver = passwd > } > protocol lmtp { > mail_plugins = sieve > } > protocol lda { > mail_plugins = sieve > } > > > ------------------------------ > > Message: 5 > Date: Mon, 5 Nov 2018 19:28:45 -0500 > From: Felipe Gasper <felipe(a)felipegasper.com> > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Re: dovecot: imap Error: read : Broken pipe > Message-ID: <AAAEBE0C-AF9E-41A4-9BB4-668667E2531D(a)felipegasper.com> > Content-Type: text/plain; charset=utf-8 > > >> On Nov 5, 2018, at 6:19 PM, Carl St-Laurent <stlauca(a)a3d-concept.com> >> wrote: >> >> Hi everyone, >> >> I'm trying to find a solution for this bug who appears 2 months ago : >> >> dovecot: imap(%USER%): Error: read(<binary stream of mailbox INBOX UID >> (%d)>) failed: Broken pipe (FETCH BINARY[2] for mailbox INBOX UID (%d) > > That looks a bit goofy ? read() should never produce EPIPE, AFAIK? > > -F > > ------------------------------ > > Message: 6 > Date: Tue, 6 Nov 2018 08:30:54 +0200 > From: Aki Tuomi <aki.tuomi(a)open-xchange.com> > To: Dovecot Mailing List <dovecot(a)dovecot.org>, Carl St-Laurent > <stlauca(a)a3d-concept.com> > Subject: Re: dovecot: imap Error: read : Broken pipe > Message-ID: <2a43ea13-d043-fd45-119c-0e3e1b8d29cd(a)open-xchange.com> > Content-Type: text/plain; charset=utf-8 > > > On 6.11.2018 2.28, Felipe Gasper wrote: >>> On Nov 5, 2018, at 6:19 PM, Carl St-Laurent <stlauca(a)a3d-concept.com> >>> wrote: >>> >>> Hi everyone, >>> >>> I'm trying to find a solution for this bug who appears 2 months ago : >>> >>> dovecot: imap(%USER%): Error: read(<binary stream of mailbox INBOX >>> UID (%d)>) failed: Broken pipe (FETCH BINARY[2] for mailbox INBOX UID >>> (%d) >> That looks a bit goofy ? read() should never produce EPIPE, AFAIK? >> >> -F > > It is bit strange that you are not experiencing this problem at the > office, but only from remote location(s). This does turn the pointing > finger towards firewall (despite what you said). Can you take pcaps > from > this, since it seems to be reproducible and send them to me privately? > > Aki > > > > ------------------------------ > > Message: 7 > Date: Tue, 6 Nov 2018 08:57:23 +0200 > From: Mart Pirita <sysadmin(a)e-positive.ee> > To: dovecot(a)dovecot.org > Subject: Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)): > auth-client-connection.c:338 > Message-ID: <c2cc829e-c66a-73b9-2968-194e8add49ab(a)e-positive.ee> > Content-Type: text/plain; charset=windows-1252 > > Hi, > > > I'm not using rsyslog and instead of hiding, this event leak should be > fixed. > > > > Michael Slusarz wrote: >>> On November 3, 2018 at 9:41 AM Mart Pirita <sysadmin(a)e-positive.ee> >>> wrote: >>> >>> >>> Hi, >>> >>> >>> But this harmless is spamming logs, so how to disable it: >>> >>> grep auth-client-connection.c:338 maillog | wc -l >>> ?? 1259 >> If using something like rsyslog, it is trivial to filter out unwanted >> entries. >> >> michael >> >> >>> Aki Tuomi wrote: >>>>> On 03 November 2018 at 12:12 Mart Pirita < sysadmin(a)e-positive.ee >>>>> <mailto:sysadmin@e-positive.ee>> wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> >>>>> Noticed with latest v2.3.3 some new warning in logs, for example: >>>>> >>>>> dovecot: auth: Warning: Event 0x80a6fc0 leaked (parent=(nil)): >>>>> auth-client-connection.c:338: 1 Time(s) >>>>> dovecot: auth: Warning: Event 0x80aa1c8 leaked (parent=(nil)): >>>>> auth-client-connection.c:338: 1 Time(s) >>>>> dovecot: auth: Warning: Event 0x80aa718 leaked (parent=(nil)): >>>>> auth-client-connection.c:338: 1 Time(s) >>>>> dovecot: auth: Warning: Event 0x80adac0 leaked (parent=(nil)): >>>>> auth-client-connection.c:338: 1 Time(s) >>>>> dovecot: auth: Warning: Event 0x80b6c38 leaked (parent=(nil)): >>>>> auth-client-connection.c:338: 1 Time(s) >>>>> dovecot: auth: Warning: Event 0x80c0e00 leaked (parent=(nil)): >>>>> auth-client-connection.c:338: 1 Time(s) >>>>> dovecot: auth: Warning: auth client 0 disconnected with 1 pending >>>>> requests: EOF: 12 Time(s) >>>>> >>>>> >>>>> What are they? >>>>> >>>>> >>>>> -- >>>>> Mart >>>> Hi! It's harmless event leak. This is a known issue to us. > > > -- > Mart > > > > > ------------------------------ > > Message: 8 > Date: Tue, 6 Nov 2018 09:20:22 +0200 > From: Aki Tuomi <aki.tuomi(a)open-xchange.com> > To: Mart Pirita <sysadmin(a)e-positive.ee>, dovecot(a)dovecot.org > Subject: Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)): > auth-client-connection.c:338 > Message-ID: <4baea373-fbc3-e850-044c-d174c3a8c65b(a)open-xchange.com> > Content-Type: text/plain; charset=windows-1252 > > It will be fixed. > > Aki > > On 6.11.2018 8.57, Mart Pirita wrote: >> Hi, >> >> >> I'm not using rsyslog and instead of hiding, this event leak should be >> fixed. >> >> >> >> Michael Slusarz wrote: >>>> On November 3, 2018 at 9:41 AM Mart Pirita <sysadmin(a)e-positive.ee> >>>> wrote: >>>> >>>> >>>> Hi, >>>> >>>> >>>> But this harmless is spamming logs, so how to disable it: >>>> >>>> grep auth-client-connection.c:338 maillog | wc -l >>>> ?? 1259 >>> If using something like rsyslog, it is trivial to filter out unwanted >>> entries. >>> >>> michael >>> >>> >>>> Aki Tuomi wrote: >>>>>> On 03 November 2018 at 12:12 Mart Pirita < sysadmin(a)e-positive.ee >>>>>> <mailto:sysadmin@e-positive.ee>> wrote: >>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> >>>>>> Noticed with latest v2.3.3 some new warning in logs, for example: >>>>>> >>>>>> dovecot: auth: Warning: Event 0x80a6fc0 leaked (parent=(nil)): >>>>>> auth-client-connection.c:338: 1 Time(s) >>>>>> dovecot: auth: Warning: Event 0x80aa1c8 leaked (parent=(nil)): >>>>>> auth-client-connection.c:338: 1 Time(s) >>>>>> dovecot: auth: Warning: Event 0x80aa718 leaked (parent=(nil)): >>>>>> auth-client-connection.c:338: 1 Time(s) >>>>>> dovecot: auth: Warning: Event 0x80adac0 leaked (parent=(nil)): >>>>>> auth-client-connection.c:338: 1 Time(s) >>>>>> dovecot: auth: Warning: Event 0x80b6c38 leaked (parent=(nil)): >>>>>> auth-client-connection.c:338: 1 Time(s) >>>>>> dovecot: auth: Warning: Event 0x80c0e00 leaked (parent=(nil)): >>>>>> auth-client-connection.c:338: 1 Time(s) >>>>>> dovecot: auth: Warning: auth client 0 disconnected with 1 pending >>>>>> requests: EOF: 12 Time(s) >>>>>> >>>>>> >>>>>> What are they? >>>>>> >>>>>> >>>>>> -- >>>>>> Mart >>>>> Hi! It's harmless event leak. This is a known issue to us. >> > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > https://dovecot.org/mailman/listinfo/dovecot > > ------------------------------ > > End of dovecot Digest, Vol 187, Issue 7 > ***************************************

1 0

dovecot: imap Error: read : Broken pipe
by Carl St-Laurent 06 Nov '18

06 Nov '18

Hi everyone, I'm trying to find a solution for this bug who appears 2 months ago : dovecot: imap(%USER%): Error: read(<binary stream of mailbox INBOX UID (%d)>) failed: Broken pipe (FETCH BINARY[2] for mailbox INBOX UID (%d) Where %USER% is the unix user and %d the UID of the mailbox. This error appears each time a user tries to download an attachment from one of his emails. Whether with RoundCube or Thunderbird via VPN or not. I thought that it was related to my firewall but no. Furthermore the problem isn't present when users are at the office. Upload speed from our ADSL connection is pretty slow about 1mpbs, I thought maybe it was related but it was working fine since 2 years. So I'm really short of ideas. Anyone could help me please ? Best regards, Carl # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-7-amd64 x86_64 Debian 9.5 auth_mechanisms = plain login disable_plaintext_auth = no mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after } protocols = imap imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } ssl = required ssl_ca = </etc/ssl/mail/****.pem ssl_cert = </etc/ssl/mail/****.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol lmtp { mail_plugins = sieve } protocol lda { mail_plugins = sieve }

3 2

imap authentication - shadow vs mysql
by Konra Wawryn 05 Nov '18

05 Nov '18

Hi, I`m looking for some opinions about authentication process for the systems with more than 1000 E-mail accounts. Maybe some one could advise me what is the best authentication method. At the moment I`m storing all passwords in my /etc/passwd. My IMAP server is growing and I`m planning to build new host, my question is: what is the best authentication model for IMAP server ? Do I need to store all user/passwords in mysql or maybe in LDAP ? I`m searching for some solution which will help me to scale my system in the future. Maybe some one could advice me ? Greetings Konrad

2 1

errors in mail.err related with ssl
by Poliman - Serwis 05 Nov '18

05 Nov '18

Hi. I have in mail.err file lines like below: Nov 5 08:40:00 s1 dovecot: imap-login: Error: SSL: Stacked error: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request Nov 5 08:40:00 s1 dovecot: imap-login: Error: SSL: Stacked error: error:1408A10B:SSL routines:ssl3_get_client_hello:wrong version number Nov 5 08:40:05 s1 dovecot: pop3-login: Error: SSL: Stacked error: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol Nov 5 08:43:07 s1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher Nov 5 08:53:31 s1 dovecot: pop3-login: Error: SSL: Stacked error: error:14094085:SSL routines:ssl3_read_bytes:ccs received early What do the above mean? I suppose that somebody tries connect but uses too old/weak ssl version. -- *Pozdrawiam / Best Regards* *Piotr Bracha*

2 4