On Tue, Sep 17, 2019 at 01:45:29PM +0200, Greg Kurz wrote:
> On Tue, 17 Sep 2019 13:00:37 +0200
> Philippe Mathieu-Daudé <phi...@redhat.com> wrote:
> 
> > For some reason your email client escaped incorrectly Daniel's email:
> > 
> >   "Daniel P. Berrangé\" <berra...@redhat.com>
> > 
> 
> The client is stgit's "stg mail" command, and indeed it generates this:
> 
>  "Daniel P. =?utf-8?q?Berrang=C3=A9=22?= <berra...@redhat.com>
>                                    ^^^
>                                 double-quote
> 
> and if I turn the 'é' into a 'e':
> 
>  "Daniel P. Berrange" <berra...@redhat.com>
> 
> This looks like a bug in "stg mail"...

Happy to see that my name is detecting bugs :-)

I should add an emoji to it to really flush out the edge cases...

> > Which makes my email client very unhappy (Thunderbird):
> > 
> > There are non-ASCII characters in the local part of the recipient
> > address "Daniel P. Berrangé <berra...@redhat.com>,
> > qemu-bl...@nongnu.org, qemu-...@nongnu.org, qemu-...@nongnu.org,
> > qemu-s3...@nongnu.org"@d06av23.portsmouth.uk.ibm.com. This is not yet
> > supported. Please change this address and try again.
> > 
> > Neither is MTA:
> > 
> > An error occurred while sending mail. The mail server responded:
> > 5.1.2 The recipient address <qemu-s3...@nongnu.org@d06av22.portsmouth.uk.ibm
> > 5.1.2 .com> is not a valid RFC-5321 address. r28sm2465872wrr.94 - gsmtp.
> >  Please check the message recipient
> > ""qemu-s3...@nongnu.org"@d06av22.portsmouth.uk.ibm.com" and try again.
> 
> Drat... this may prevent recipients starting with Daniel from receiving
> the mails... ie, the sub-lists IIUC. Maybe not worth reposting for that.

Yeah, I wouldn't bother reposting just for that.

> Hopefully, Daniel may catch up on qemu-devel.

Indeed.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

Reply via email to