- dovecot - dovecot.org

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

error Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=)
by Poliman - Serwis 05 Nov '18

05 Nov '18

I have a problem for specific mailbox. In mail.err file I see a lot: Nov 2 07:41:17 s1 dovecot: imap(artur(a)example.pl): Error: unlink(/var/vmail/example.pl/artur/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Nov 2 07:41:17 s1 dovecot: imap(artur(a)example.pl): Error: Corrupted index cache file /var/vmail/example.pl/artur/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 2356 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=) Nov 2 07:41:19 s1 dovecot: imap(artur(a)example.pl): Error: unlink(/var/vmail/example.pl/artur/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Nov 2 07:41:19 s1 dovecot: imap(artur(a)example.pl): Error: Corrupted index cache file /var/vmail/example.pl/artur/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 2431 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=) Nov 2 07:41:21 s1 dovecot: imap(artur(a)example.pl): Error: unlink(/var/vmail/example.pl/artur/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Nov 2 07:41:21 s1 dovecot: imap(artur(a)example.pl): Error: Corrupted index cache file /var/vmail/example.pl/artur/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 2552 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=) Nov 2 07:41:21 s1 dovecot: imap(artur(a)example.pl): Error: unlink(/var/vmail/example.pl/artur/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Nov 2 07:41:21 s1 dovecot: imap(artur(a)example.pl): Error: Corrupted index cache file /var/vmail/example.pl/artur/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 2605 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=) Nov 2 07:41:24 s1 dovecot: imap(artur(a)example.pl): Error: unlink(/var/vmail/example.pl/artur/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Nov 2 07:41:24 s1 dovecot: imap(artur(a)example.pl): Error: Corrupted index cache file /var/vmail/example.pl/artur/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 2717 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=) I have many mailboxes on the server and each of them work perfectly except this one. -- *Pozdrawiam / Best Regards* *Piotr Bracha*

2 3

doveconf error upon boot up
by Jerry 31 Oct '18

31 Oct '18

FreeBSD 11.1-RELEASE-p9 amd64 doveconf # 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1 (d9bc6dfe) # OS: FreeBSD 11.1-RELEASE-p9 amd64 zfs # Hostname: localhost I can send the entire output if necessary. Error message upon boot up: doveconf: error: t_readlink(/var/run/dovecot/dovecot.conf) failed: readlink() failed: No such file or directory Starting dovecot. Dovecot appears to start correctly There is a link in the "/var/run/dovecot directory for dovecot.conf" lrwx------ 1 root wheel 35B 2018-04-10 10:21:52 EDT dovecot.conf@-> /usr/local/etc/dovecot/dovecot.conf This error message has only started since the update to the latest version of dovecot. I am assuming it is just a harmless error message; however, I would like to confirm that hypothesis. -- Jerry

3 4

OCSP Stapling and Certificate Transparency
by Felipe Gasper 31 Oct '18

31 Oct '18

Hi, For CAs that do not include a signed certificate timestamp in their newly-issued certificates, does Dovecot support either OCSP stapling or the Certificate Transparency TLS extension? If the TLS extension is supported, how does the admin configure the timestamp for each certificate? I’m wondering if any MUAs will follow Google’s lead and insist on CT. Thank you! -Felipe Gasper Mississauga, Ontario

4 3

Copying from a previous Dovecot server
by Peter Lindgren 31 Oct '18

31 Oct '18

Hello! I have installed a new dovecot server on a new server, using imap and Maildir. The old Maildirs are accessible on a mounted disk. I have tried to copy a few folders manually, by first creating the folder on the new server through the a-mail client, and then copying the contents of the cur folder from the old to the new. Works fine, but is a manual process. I'm looking for a way to script this. Is it safe to copy a template folder to a new folder, and then copy the cur folder contents? The files that Dovecot creates in an empty folder have different contents, will Dovecot update them when the user retrieves the mails in that folder? Or, can I just make a symlink to the old Maildir somewhere? Peter -- Peter Lindgren peter(a)norrskenkonsult.com 0703-393940

2 1

[dovecot quota-status] error "Invalid character in path"
by k675154＠keit.eu 31 Oct '18

31 Oct '18

Hello, I'm using using: - dovecot 2.3.3 (dcead646b) - postfix 3.3.1 - dovecot "quota = maildir:User quota" I'm facing the error: "quota-status: Error: quota-status: Client sent invalid recipient address: Invalid character in path" This occurred with this e-mail address: "John Smith"@keit.eu Well I know it is not a conventional address but it is normally perfectly authorized. When I disable quota check, I can received correctly the incoming e-mail. So is there a mean to enable quota check with this kind of e-mail address ? Thanks

2 1

Dovecot submission announces CHUNKING but backend Postfix does not support it
by Michael Goth 30 Oct '18

30 Oct '18

Hello, I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix backend server. Dovecot announces CHUNKING, but the Postfix backend does not support (or announce) it. HELO from Postfix: 220 backend.mydomain.com ESMTP Postfix (Ubuntu) ehlo test 250-backend.mydomain.com 250-PIPELINING 250-SIZE 104857600 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN HELO from Dovecot proxy: 220 proxy.mydomain.com Dovecot ready. ehlo test 250-proxy.mydomain.com 250-8BITMIME 250-AUTH PLAIN LOGIN 250-BURL imap 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-SIZE 250-STARTTLS 250 PIPELINING When a client sends BDAT, Postfix closes the connection. Here's a log snippet from Postfix: < MAIL FROM:<user(a)mydomain.com> > 250 2.1.0 Ok < RCPT TO:<some(a)recipient.com> > 250 2.1.5 Ok < BDAT 114098 LAST > 502 5.5.2 Error: command not recognized < Content-Type: multipart/alternative; boundary=Apple-Mail-55D35F74-2EB7-4B3B-A607-E421DD71C07A > 221 2.7.0 Error: I can break rules, too. Goodbye. Apple Mail seems to ignore the fact that Postfix does not understand BDAT and Postfix does not like that :-) From a quick glance at the code it seems CHUNKING is always added to the capabilities and that's not configurable. Is this a bug or am I doing something wrong? Thanks, Michael

4 7