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
View this message in rfc822 format
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: 51733 <at> debbugs.gnu.org
> Date: Wed, 19 Jan 2022 13:54:37 +0100
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> > This is unfortunate. It means, for example, that a simple lazy
> > discovery of suspicious addresses by scanning the email reading buffer
> > with regular expressions will not work, and the feature must instead
> > scan the original mbox buffer.
>
> There's no scanning -- rmail displays the From header, right? So it
> does decoding before displaying the header. It has to do the textsec
> stuff first, too.
Not if textsec is optional, it doesn't.
And I think your mental model of how Rmail presents the email in the
reading buffer is not accurate.
> > Why cannot we lift this restriction? mail-header-parse-address is not
> > the only way to parse email addresses. Or maybe we could encode the
> > email address if the original one causes an error?
>
> There is no reliable way to parse a decoded mail address, and since this
> is a security thing, we don't want to do DWIM and guesses (which is what
> you have to do when composing a valid email address from a string like
> "Fóo, Jr. <foo <at> example.com>").
I think Robert just suggested a way?
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.