GNU bug report logs -
#51733
27.1; Detect impossible email addresses better
Previous Next
Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Date: Wed, 10 Nov 2021 00:29:01 UTC
Severity: wishlist
Found in version 27.1
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #332 received at 51733 <at> debbugs.gnu.org (full text, mbox):
>>>>> On Wed, 19 Jan 2022 15:36:34 +0100, Lars Ingebrigtsen <larsi <at> gnus.org> said:
Lars> Robert Pluim <rpluim <at> gmail.com> writes:
>> Based on the message buffer I have, gnus didnʼt encode it again, so it
>> must have been gmail. Of course that header was ascii-only, so why did
>> they encode again?
Lars> RFC2047 isn't just about ASCII -- it's about a bunch of other unsafe
Lars> characters, like =, which will trigger encoding of (naked) words that
Lars> contain those characters.
>> What did the From: look like on the message you've just replied to?
>> Gnus should not have encoded it, and it contained utf-8 in the display
>> name.
Lars> I included the From in wire format and displayed format already.
From the original message where I rfc2047 encoded it myself, yes. The
one after I didnʼt encode manually, and turned off the gnus encoding.
Looking at the bug archive, for Message-ID: <874k5zolz0.fsf <at> gmail.com>
we have:
From: Robert Pluĭm <rpluim <at> gmail.com>
with no rfc2047 in sight. Gmail is weird, let's go shopping :-)
Robert
--
This bug report was last modified 3 years and 124 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.