Re: UTF-8 error email from freeuk (Clara)

Hello Charles and guys,

Sorry for not responding, things have changed in my system. What I can
share is that when I applied the patch it did not help, I have seen the
error afterwards. Setup was Courier + getmail on Ubuntu 20.
In the meantime our system setup changed and mail handling has moved off
this box so I cannot run any further tests but I hope my late input will
help you in some way.

Regards,
/Tamás

Matthias Andree <[email protected]> ezt írta (időpont: 2021. nov. 30.,
K, 17:57):

> Am 04.11.21 um 17:33 schrieb Brian D:
> > I have been using getmail without problems for many years.
> >
> > Currently I'm using getmail 4.54.0
> > with Python 2.7.5
> > on openSUSE 11.1 (x86_64)
> >
> > Recently emails (undated) have been arriving from freeuk? saying my email
> > program doesn't support UTF-8. the email enclosed with these messages is
> > from various email lists I have been subscribed from for years.
> >
> > Has clara blacklisted getmail as a result of the faulty fork?
> >
> > and sample email :
> >
> > ----------------------
> > Return-Path: <unknown>
> > X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
> > planet4.dyndns.org
> > X-Spam-Level: *
> > X-Spam-Status: No, score=1.4 required=5.0
> > tests=AWL,BAYES_00,FH_FROMEML_NOTLD,
> >       HTML_MESSAGE,MISSING_DATE,MISSING_HEADERS,MISSING_MID autolearn=no
> >       version=3.2.5
> > Delivered-To: unknown
> > Received: from pop.freeuk.net (80.168.46.12) by router.ntlworld.nil with
> >    POP3; 04 Nov 2021 14:50:03 -0000
> > From: Mail Delivery Subsystem <postmaster>
> > Subject: Cannot display Unicode content
> > Mime-Version: 1.0
> > Content-Type: multipart/mixed; boundary="=_1796930-1636037403"
> >
> >
> >
> > --=_1796930-1636037403
> > Content-Type: text/plain
> >
> > This E-mail message was determined to be Unicode-formatted
> > but your E-mail reader does not support Unicode E-mail.
> >
> > Please use an E-mail reader that supports POP3 with UTF-8
> > (see https://tools.ietf.org/html/rfc6856.html).
> >
> > This can also happen when the sender's E-mail program does not
> > correctly format the sent message.
> >
> > The original message is included as a separate attachment
> > so that it can be downloaded manually.
> >
> > --=_1796930-1636037403
> [...]
>
> This can happen, for instance, on server-side Courier-IMAPd trying to
> strictly implement RFC-6855 and 6856,
>
> https://datatracker.ietf.org/doc/html/rfc6855
> https://datatracker.ietf.org/doc/html/rfc6856
>
> ...and the client (getmail, or fetchmail FWIW) not sending "ENABLE
> UTF8=ACCEPT" over IMAP, or not sending "UTF8" over POP3.
> There was a similar discussion earlier, in July 2021, under the subject
> "POP3 UTF-8 support" started by Kopornoky Tamas (actually the 2nd a
> carries a forward accent), but I haven't seen Tamas's feedback on
> Charles's earlier attempt at tackling this issue.
>
> last message in my book was Charles's
> [email protected] 2021-08-07T17:31Z
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>