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

Previous Next

Packages: gnus, emacs;

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 #239 received at 51733 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 51733 <at> debbugs.gnu.org, rpluim <at> gmail.com
Subject: Re: bug#51733: 27.1; Detect impossible email addresses better
Date: Wed, 19 Jan 2022 15:06:30 +0200
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: Robert Pluim <rpluim <at> gmail.com>,  51733 <at> debbugs.gnu.org
> Date: Wed, 19 Jan 2022 14:02:56 +0100
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Is that expectation reasonable?  I can show you many email addresses
> > that violate that.
> 
> It depends on what you mean.  There are no valid email addresses that
> have non-ASCII name parts -- when we're talking wire format (RFC2047
> etc), which is what that function is parsing.
> 
> But displayed email addresses may have any characters, of course.

I _am_ talking about the displayed format.  It would be better if
textsec supported those as well, because they are ubiquitous in
Emacs.  E.g., what if someone sends me a citation from someone else's
email, and I want to textsec-check that citation?  Chances are the
citation will not include RFC2047 encoded addresses.




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.