Mailing List Archive

[Bug 2724] Email Address Internationalization Support Bug Report
https://bugs.exim.org/show_bug.cgi?id=2724

--- Comment #1 from Jeremy Harris <jgh146exb@wizmail.org> ---
If you don't make the bug report easy to read, by using a meaningful title
and by actually putting details in the description, it is very likely to not
be attended to. Why should we bother?

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2724] Email Address Internationalization Support Bug Report [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2724

Graeme Fowler <graeme@graemef.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |graeme@graemef.net

--- Comment #2 from Graeme Fowler <graeme@graemef.net> ---
From the PDF:

"Exim is a widely used open source mail server that provides an MSA and MTA. We
installed it on a test host and configured it with several EAI addresses in IDN
domains. Exim provides both Phase 1 and Phase 2 EAI support and passed most
tests.

Exim’s developers consider an EAI message to be one with UTF-8 envelope
addresses and an ASCII message to be one without UTF-8 envelope addresses, even
if the message’s headers include UTF-8. While we disagree with their
interpretation, we think it is unlikely to cause problems in practice since
messages with ASCII envelopes and UTF-8 headers are uncommon.

Exim does not provide a POP or IMAP server. It is typically used with the
Dovecot or Cyrus IMAP/POP servers neither of which currently has EAI support."

I do tend toward's Jeremy's viewpoint however: if the bug report is not itself
clear, and requires extra legwork on behalf of the small maint and dev team,
this is not an optimal way to report a bug.

There is nothing technical in the PDF report to work with, simply the above
statement that interpretations differ.

If you'd like to offer more technical detail, please feel free otherwise this
is likely to be closed as INVALID.

--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug 2724] Email Address Internationalization Support Bug Report [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2724

--- Comment #3 from Simon Arlott <bugzilla.exim.simon@arlott.org> ---
There's some more detail in the Excel spreadsheet linked from the PDF but it
doesn't explain why (with reference to an RFC) each of the test cases that
failed should behave differently.

There is a PDF with a link* to standards and other PDF/Excel files with test
cases but there's no attempt to link the two together.

* All of the URLs are plaintext, not links...


"EAI-MTA-005 FAIL Trace information includes domain in U-label form"

This is not required by RFC 6531:

> When an SMTPUTF8-aware SMTP server adds a trace field to a message
> that was or will be transmitted with the SMTPUTF8 parameter included
> in the MAIL commands, that server SHOULD use the U-label form for
> internationalized domain names in the new trace field.

The A-label should be sufficient to identify the domain.


"EAI-MTA-006 FAIL Trace information indicates SMTPUTF8 protocol
Protocol is misspelled UTF8ESMTPS"

This is not required by RFC 6531:

> The protocol value of the 'WITH' clause when this extension is used
> is one of the SMTPUTF8 values specified in the "IANA Considerations"
> section of this document.

No "MUST" or "SHOULD" here. Exim has an extra "E" because EHLO was used.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2724] Email Address Internationalization Support Bug Report [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2724

--- Comment #4 from Simon Arlott <bugzilla.exim.simon@arlott.org> ---
"EAI-MTA-007 FAIL EAI reverse path values are transmitted to SMTPUTF8
server A-labels in MAIL FROM johnl@xn--5nq051n.services.net"

This is not required by RFC 6531:

> It MAY transmit the domain parts of mailbox names within
> SMTP commands or the message header as A-labels or U-labels
> [RFC5890]. The presence of the SMTPUTF8 extension does not change
> the server-relaying behaviors described in RFC 5321.

I think the test should be re-run with the correct setting of
"utf8_downconvert" because the documentation implies that Exim can use
U-labels.


"EAI-MTA-013 FAIL EAI messages sent to non-SMTPUTF8 server are rejected
Message sent anyway"

This refers to non-ASCII local parts so it's probably a bug but there's no
evidence (Exim log file) to prove it.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
Re: [Bug 2724] Email Address Internationalization Support Bug Report [ In reply to ]
On Mon, 3 May 2021, admin--- via Exim-dev wrote:

> https://bugs.exim.org/show_bug.cgi?id=2724
>
> Graeme Fowler <graeme@graemef.net> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |graeme@graemef.net
>
> --- Comment #2 from Graeme Fowler <graeme@graemef.net> ---
>> From the PDF:
>
> "Exim is a widely used open source mail server that provides an MSA and MTA. We
> installed it on a test host and configured it with several EAI addresses in IDN
> domains. Exim provides both Phase 1 and Phase 2 EAI support and passed most
> tests.
>
> Exim???s developers consider an EAI message to be one with UTF-8 envelope
> addresses and an ASCII message to be one without UTF-8 envelope addresses, even
> if the message???s headers include UTF-8. While we disagree with their
> interpretation, we think it is unlikely to cause problems in practice since
> messages with ASCII envelopes and UTF-8 headers are uncommon.
>
> Exim does not provide a POP or IMAP server. It is typically used with the
> Dovecot or Cyrus IMAP/POP servers neither of which currently has EAI support."

That text (or similar) appears in both attachment 1379 "Exim.pdf" and the
linked document "UASG030-en-digital.pdf". While UASG030-en-digital.pdf has
little detail, the attachment does at least list the tests that failed:
MSA Tests Failed
1. EAI messages sent to non-SMTPUTF8 server are rejected or transformed
MTA Tests Failed
1. Trace information includes domain in U-label form
2. Trace information indicates SMTPUTF8 protocol
3. EAI reverse path values are transmitted to SMTPUTF8 server
4. EAI messages sent to non-SMTPUTF8 server are rejected

These tests are described in UASG021B-en-digital-EAI-Pilot-Test-Cases.xlsx

I am not convinced that rejecting or transforming mail is better
than relaying it to a non-SMTPUTF8 server.


I see that John Levine contributed the EAI test software
https://github.com/jrlevine/eaitesttools
and mentioned exim in the equivalent fetchmail bug
https://gitlab.com/fetchmail/fetchmail/-/issues/14

> I do tend toward's Jeremy's viewpoint however: if the bug report is not itself
> clear, and requires extra legwork on behalf of the small maint and dev team,
> this is not an optimal way to report a bug.
>
> There is nothing technical in the PDF report to work with, simply the above
> statement that interpretations differ.
>
> If you'd like to offer more technical detail, please feel free otherwise this
> is likely to be closed as INVALID.

--
Andrew C. Aitchison Kendal, UK
andrew@aitchison.me.uk

--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2724] Email Address Internationalization Support Bug Report [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2724

Arkadiusz Miskiewicz <arekm@maven.pl> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |arekm@maven.pl

--- Comment #5 from Arkadiusz Miskiewicz <arekm@maven.pl> ---
I guess these are the tests
https://github.com/jrlevine/eaitesttools

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2724] Email Address Internationalization Support Bug Report [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2724

--- Comment #6 from Simon Arlott <bugzilla.exim.simon@arlott.org> ---
(In reply to Simon Arlott from comment #4)
> "EAI-MTA-013 FAIL EAI messages sent to non-SMTPUTF8 server are rejected
> Message sent anyway"
>
> This refers to non-ASCII local parts so it's probably a bug but there's no
> evidence (Exim log file) to prove it.

On 03/05/2021 20:26, Andrew C Aitchison via Exim-dev wrote:
> I am not convinced that rejecting or transforming mail is better
> than relaying it to a non-SMTPUTF8 server.

Yes, it's kind of like how Exim relays 8BITMIME without any transformation.

There is no way to transform a non-ASCII local part, so the simplest action
(other than rejecting) is to attempt to deliver it and let the remote server
reject it if it's unable to handle it.

I don't see a test case for "given a non-ASCII local part when SMTPUTF8 not
advertised".

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2724] Email Address Internationalization Support Bug Report [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2724

John Levine <exim@m.jl.ly> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |LATER
Status|NEW |RESOLVED
CC| |exim@m.jl.ly

--- Comment #7 from John Levine <exim@m.jl.ly> ---
I ran the tests, I'll send separate tickets for the bugs that are worth fixing.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##