After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 742578 - IDN: From: address not converted to punycode
IDN: From: address not converted to punycode
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.16.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks: 742579
 
 
Reported: 2015-01-08 11:42 UTC by noel
Modified: 2021-05-19 12:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description noel 2015-01-08 11:42:35 UTC
Hello,

sending to IDN (more info and testcases see https://wiki.debian.org/IDN ) domains works (see #486018 horray and thanks!;))  but configuring Evolution (3.12.9) with a IDN domain as From:/Sender: fails because the domain part is send with the non-ASCII letters and not converted to punycode:

Message-ID: <1420717065.17069.0.camel@köthe.de>
Subject: test from =?ISO-8859-1?Q?k=F6the=2Ede?=
From: =?ISO-8859-1?Q?No=EBl_K=F6the?= <noel@köthe.de>
To: noel@köthe.de
Date: Thu, 08 Jan 2015 12:37:45 +0100
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.12.9-1+b1 
...

A correct From: sender needs to be converted to punycode. E.g. where the client is configured with noel@köthe.de as email address:

Return-Path: <noel@xn--kthe-5qa.de>
...
From: =?utf-8?Q?No=C3=ABl_K=C3=B6the?= <noel@xn--kthe-5qa.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: =?utf-8?Q?Test_k=C3=B6the.de?=
Message-Id: <449FEB3C-AAA3-43EF-9C15-E48A05A246F1@xn--kthe-5qa.de>
Date: Thu, 8 Jan 2015 12:00:46 +0100
To: =?utf-8?Q?No=C3=ABl_K=C3=B6the?= <noel@xn--kthe-5qa.de>
X-Mailer: iPhone Mail (12B440)
X-Evolution-Source: 0

Would be great if I could send email with my IDN domain to push IDN forward.;)

Thank you.
Comment 1 Milan Crha 2015-02-12 13:57:13 UTC
Thanks for a bug report. We are talking about message source, that is something, what can each client interpret differently. What is the problem to have this left in the message as such? The SMTP transport doesn't use the message source for sending, but rather a list of recipients provided by the caller, the same as the From address. Did you send by a different transport than through SMTP, or what the error was that you received?
Comment 2 noel 2015-07-12 12:41:01 UTC
With 3.16.3 I can use the above mentioned From: address with umlaut but some recipients who tries to reply to the email results in errors because it is not punycode.
I will try to test it with different other clients to describe their behaviour.
Comment 3 noel 2015-07-12 12:50:12 UTC
Return-Path: <noel@xn--kthe-5qa.de>
...
Message-ID: <1436705238.16044.23.camel@köthe.de>
Subject: test
From: =?ISO-8859-1?Q?No=EBl_K=F6the?= <noel@köthe.de>
To: test@köthe.de
X-Mailer: Evolution 3.16.3-1 

The return-path is correctly converted but the From: has an UTF-8 character and replying to this results in some problems (char encoding of the name is in ISO-8859-1).
Comment 4 Milan Crha 2015-07-13 19:30:24 UTC
Well, first of all, the domain name should be UTF-8, it's the Linux system encoding and the one used in the libraries evolution uses. The second thing, my understanding was that the encoded domain names should be used only on the wire, the message itself should be left as the user wrote it, making the client responsible for the right encoding of the domain part of the email address when replying to the message. Transforming also all From/To/Cc/Bcc in the message before sending doesn't feel right at all.
Comment 5 André Klapper 2021-05-19 12:28:26 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new bug report ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.