GNU bug report logs - #51733
27.1; Detect impossible email addresses better

Previous Next

Full log

Message #305 received at 51733 <at> debbugs.gnu.org (full text, mbox):

From: Robert Pluĭm <rpluim <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 51733 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#51733: 27.1; Detect impossible email addresses better
Date: Wed, 19 Jan 2022 15:10:11 +0100

>>>>> On Wed, 19 Jan 2022 15:00:04 +0100, Lars Ingebrigtsen <larsi <at> gnus.org> said:

    Lars> Robert "=?utf-8?Q?Plu=C4=ADm?=" <rpluim <at> gmail.com> writes:
    >> I canʼt recall if this is allowed by the standards or not offhand, but
    >> as youʼre probably well aware, the major email providers allow you to
    >> use UTF-8 characters directly in the display name of email adresses,
    >> without using RFC 2047 encoding. In fact, the last time I did any
    >> testing of this, Gmail *replaced* RFC 2047 encoded non-ASCII
    >> characters with their UTF-8 encoding.

    Lars> Gmail expects you to type in characters representing your name -- they
    Lars> don't expose the wire format.  Why should they?

    Lars> And your address arrived as (wire format):

    Lars> Robert =?us-ascii?Q?=3D=3Futf-8=3FQ=3FPlu=3DC4=3DADm=3F=3D?=

    Lars> which displays as

    Lars> Robert =?utf-8?Q?Plu=C4=ADm?=

    Lars> 😀

Double fun. Iʼd manually rfc2047 encoded that before sending it, so
either gnus or Gmail encoded it again :-)

Iʼve turned off the gnus rfc 2047 for this message, let's see what
happens.

Robert
-- 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.