Re: Problems of Internationalized Mail Address eXtensions (IMAX)

Hi Paul,

----- Original Message -----
From: "Paul Hoffman / IMC" <[email protected]>
> And you don't have to. IMAA-ACE works with no changes to the MTA.
> IMAX forces changes, including changing the maximum line lengths for
> the MAIL FROM and RCPT TO commands. That's pretty non-trivial.


if you think that changing the max line lengths is to big, I will take it
out.  Just thought that it would also be a good time to upgrade that part,
especially due to the use of Punycode infact! ;-)
It really isn't a "MUST".

> >How would an ESMTP extension with an ACE fallback (i.e., IMAX) involve
> >bouncing or dropping mail?
>
> The second paragraph of section 2.3 sure sounds like it would bounce
> things instead of doing an ACE fallback.


This describes the situation today!  That is, an IDN/IMA-unaware client
tries to send out a to/from a multilingual address.  It has nothing to do
with the IMAX architecture.  I just hoped that it was clear to people about
this reality and not shy away from it.  If you think it is actually more
confusing, I will take away the description.

> >Punycode decoding is not optional if the MTA wants to support
> >non-ASCII.
>
> Where in the IMAA document does it say that? I believe you are
> completely wrong here.

Yes it does say that support for ACE (to be updated to Punycode in -01 or
when the RFC is out, as I said I wrote this 2 years ago...) is mandatory.
ACE and UTF8 is mandatory.  Please refer to last paragraph of section 2.2.

Edmon