GNU bug report logs - #77866
30.0.50; message.el handling of non-ascii names in addresses

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Al Haji-Ali <abdo.haji.ali <at> gmail.com>
Cc: 77866 <at> debbugs.gnu.org
Subject: Re: bug#77866: 30.0.50;
 message.el handling of non-ascii names in addresses
Date: Thu, 17 Apr 2025 16:19:21 +0300

> From: Al Haji-Ali <abdo.haji.ali <at> gmail.com>
> Date: Thu, 17 Apr 2025 13:54:21 +0100
> 
> 
> This is a bit difficult for me to reproduce as a user in a clean instance of Emacs, since I am seeing it in notmuch, which uses message.el, and I don't know how to use message.el without my setup of notmuch.
> However, I am sure that I've identified the reason for the bug(?) in message.el and I hope my description below is sufficient.
> 
> I have an email with a header field like this:
> CC: "Blanco, Raúl" <blanco <at> test.com>
> 
> with a non-ASCII character in the name. When I call `message-send-mail`, on 29.1 I get an error
> `split-string: Wrong type argument: stringp, nil`
> 
> and on 30.0.50, I get the error
> `Email address can't be parsed`
> 
> The reason is that `message-send-mail` calls `mail-encode-encoded-word-buffer`, which encodes that part of the message as:
> 
> CC: "Blanco, =?utf-8?Q?Ra=C3=BAl=22?= <blanco <at> test.com>
> 
> So that the quotation marks are no longer paired, and `mail-header-parse-addresses` splits the address into two ill-formed ones.

Isn't that because of the comma?  If you change the address to

  "Blanco Raúl" <blanco <at> test.com>

does the problem go away?

Previous Next

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