dovecot: imap Error: read : Broken pipe
Carl St-Laurent
stlauca at a3d-concept.com
Wed Nov 7 07:02:12 EET 2018
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 at dovecot.org wrote:
> Send dovecot mailing list submissions to
> dovecot at 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 at dovecot.org
>
> You can reach the person managing the list at
> dovecot-owner at 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 at virtual-machine.org>
> To: dovecot at dovecot.org
> Subject: imap authentication - shadow vs mysql
> Message-ID: <13e143d52fb2f094a285306ccbdec990 at 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 at monksofcool.net>
> To: dovecot at dovecot.org
> Subject: Re: imap authentication - shadow vs mysql
> Message-ID: <m2k1lrek2k.fsf at 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 at open-xchange.com>
> To: Mart Pirita <sysadmin at e-positive.ee>, dovecot at dovecot.org
> Subject: Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)):
> auth-client-connection.c:338
> Message-ID: <750544780.12327.1541439735168 at appsuite.open-xchange.com>
> Content-Type: text/plain; charset=UTF-8
>
>> On November 3, 2018 at 9:41 AM Mart Pirita <sysadmin at 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 at e-positive.ee
>> > > <mailto:sysadmin at 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 at a3d-concept.com>
> To: dovecot at dovecot.org
> Subject: dovecot: imap Error: read : Broken pipe
> Message-ID: <1700cf4385e77a60415db96fa1c586ac at 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 at felipegasper.com>
> To: Dovecot Mailing List <dovecot at dovecot.org>
> Subject: Re: dovecot: imap Error: read : Broken pipe
> Message-ID: <AAAEBE0C-AF9E-41A4-9BB4-668667E2531D at felipegasper.com>
> Content-Type: text/plain; charset=utf-8
>
>
>> On Nov 5, 2018, at 6:19 PM, Carl St-Laurent <stlauca at 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 at open-xchange.com>
> To: Dovecot Mailing List <dovecot at dovecot.org>, Carl St-Laurent
> <stlauca at a3d-concept.com>
> Subject: Re: dovecot: imap Error: read : Broken pipe
> Message-ID: <2a43ea13-d043-fd45-119c-0e3e1b8d29cd at 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 at 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 at e-positive.ee>
> To: dovecot at dovecot.org
> Subject: Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)):
> auth-client-connection.c:338
> Message-ID: <c2cc829e-c66a-73b9-2968-194e8add49ab at 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 at 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 at e-positive.ee
>>>>> <mailto:sysadmin at 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 at open-xchange.com>
> To: Mart Pirita <sysadmin at e-positive.ee>, dovecot at dovecot.org
> Subject: Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)):
> auth-client-connection.c:338
> Message-ID: <4baea373-fbc3-e850-044c-d174c3a8c65b at 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 at 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 at e-positive.ee
>>>>>> <mailto:sysadmin at 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 at dovecot.org
> https://dovecot.org/mailman/listinfo/dovecot
>
> ------------------------------
>
> End of dovecot Digest, Vol 187, Issue 7
> ***************************************
More information about the dovecot
mailing list