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 #206 received at 51733 <at> debbugs.gnu.org (full text, mbox):
> From: Robert Pluim <rpluim <at> gmail.com>
> Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, 51733 <at> debbugs.gnu.org
> Date: Wed, 19 Jan 2022 10:21:22 +0100
>
> Eli> Does textsec-email-suspicious-p expect non-ASCII email addresses to be
> Eli> RFC 2047 encoded? If so, it will not work in the Rmail display
> Eli> buffers, where email addresses are shown decoded. For non-ASCII names
> Eli> the function signals an error.
>
> It does? Do you have an example? The following works fine
Here:
(textsec-email-suspicious-p "אבגד <foo <at> bar.com>")
=> (wrong-type-argument stringp nil)
with this backtrace:
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-search("=?" nil)
rfc2047-decode-string(nil)
mail-header-parse-address("אבגד <foo <at> bar.com>" t)
textsec-email-suspicious-p("אבגד <foo <at> bar.com>")
(progn (textsec-email-suspicious-p "אבגד <foo <at> bar.com>"))
eval((progn (textsec-email-suspicious-p "אבגד <foo <at> bar.com>")) t)
elisp--eval-last-sexp(t)
eval-last-sexp(t)
eval-print-last-sexp(nil)
funcall-interactively(eval-print-last-sexp nil)
call-interactively(eval-print-last-sexp nil nil)
command-execute(eval-print-last-sexp)
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.