1. IETF 66 EAI WG Testing Report
TWNIC

2. Outline
Introduction
Downgrade
Scenarios
Mailing List
POP3
Issue

3. Introduction Base on sendmail Trial System
Sendmail complier with Milter (8.13.6)
Mimedefang for address/header rewrite (2.56)
Most coding by perl (string process) in Mimedefang
Trial System
eai1.twnic.tw EAI SMTP (RH9.0, pam + mysql)
eai2.twnic.tw EAI SMTP (RH7.3, pam + mysql)
downgrade.twnic.tw Original Sendmail version
Test by using ‘telnet’ command

4. Architecture Envelope From/To & Header downgrade
Envelope To possible upgrade by eai1 to transfer punycode local part to UTF8
eai1
downgrade.twnic.tw
台網中心.tw (xn--fiq43lrrlz83a.tw)
twnic.net.tw
(All domain are same server)
Only downgrade Trace Field
eai2

5. Reference draft-ietf-eai-framework-00.txt
draft-ietf-eai-utf8headers-00.txt
draft-ietf-eai-scenarios-01.txt
draft-ietf-eai-smtpext-00.txt
draft-ietf-eai-mailinglist-00.txt
draft-ietf-eai-pop-00.txt
draft-ietf-eai-downgrade-01.txt

6. Downgrade -Envelope Downgrade (eai1 to downgrade)
Sender EAI-aware to Destination not EAI-aware
Downgrade Envelope From/To
MAIL FROM: EAI-Parameter=ATOMIC
RCPT TO: EAI-Parameter=ALT-ADDRESS
ATOMIC:  (xn--)
ALD-ADDRESS: to replace address by ALT-ADDRESS

7. Downgrade -Header 8bit Header (UTF8) SHOULD downgrade with MIME
UTF-8 information MUST NOT appear in Received fields
Trace Field (Received) ‘for’ clauses downgraded with punycode
Add Header:
I- 1.0;downgraded by EHLO (PTR [IP])

8. Downgrade -Sample (eai1 to downgraade) - SMTP negotiation (telnet from eai2 to eai1)

9. Downgrade (outlook express view)

10. Downgrade (Openwebmail view)

11. Mailing List Base on sendmail mailing list function
Format maximum 3 columns
EAI-Parameter with ‘{‘ ‘}’
Comments with ‘(‘ ‘)’ in 2822

12. Scenarios A, B and C are i18mail users
X,Y and Z are original ascii user
L is i18n-aware
LA is non-i18n-aware
S is Sent success
R is Reply Success
Linux ‘mail’ command for EAI to reply
Outlook Express for non-EAI to reply

13. Scenario for Draft in TWNIC EAI trial -From EAIB
B,C
B,C,
X,Z L LA
L,LA,B,Y
L->L,LA A S R

14. Scenario for Draft in TWNIC EAI trial – From non-EAI (downgraded)B
B,C
B,C,
X,Z L LA
L,LA
L->L,LA X S R -

15. Other Scenarios A to B , relay by non-EAI MTA
eai1 ->downgrade -> eai2
Once downgrade , all downgrade
X to Y , relay by EAI MTA
downgrade -> eai1 -> downgrade

16. EAI POP3 TWNIC design a simple i18n-aware POP3 service
The POP3 service was developed with PERL language
Our key point
‘CAPA’ responses ‘UTF8’ , the MUA can login with UTF8 or punycode (also implement MIME, but we think it is better using punycode). Different encoding map to the same mailbox
‘CAPA’ don’t response ‘UTF8’ , login as punycode, and MDA store mail as punycode mailbox name

17. EAI POP3 Screen Shot

18. Issue 1
May addr-spec change ? Should we have to use ESMTP argument (such as eai-parameter) ?
Make sense MSG from/to regards as envelope from/to between both EAI MTA
Easy to implement in mailing list and parser, not confused in other symbols (‘,’ ‘:’ ‘#’ ‘;’ ‘|’ ‘&’…)
Some MUA (Outlook) can input and keep ‘{‘ ‘}’ information in address book, and transmit ‘<addr {eai-parameter}>’ it to MTA, if EAI MTA is known
When relaying, POSSIBLE ESMTP arguments (Ex: SIZE,AUTH,NOTIFY ) do not pass to next relay EAI MTA, cause EAI-Parameter MAYBE lose the argument.
Broken the addr-spec is not a good idea
Any opinion or method is welcome, we need more comment for our trail

19. Issue 2
Recommend: alt-separator for mailing list is same to ‘utf8header’
List-* MAY appear alt-separator before REQUEST-URI (Query String)
List-Id: “Testing \(TWNIC EAI TESTBED\) ”
Can be null
List-Subscribe:
Using in List-* and URI ‘mailto’

20. Issue 3 EAI-Parameter replaces Envelope From, and some consideration
Alt-address can be assign to another domain name that is different host from original mail address?
EAI need more detail describe conflicts with other extensions (DSN/MDN/AUTH…etc) and services
EAI need to take care SPAM issue under ALT-ADDRESS

21. Issue 4
SPF will check Sender from MTA, EAI-parameter is possible confused
Is EAI-parameter restricted to MTA domain ?
If not restrict, we don’t know how to setup SPF

22. Issue 5
Issue in DKIM
EAI is possible to change Envelope From/To and Message From/To, this action causes ‘h=‘ clause verify failure
EAI-Downgraded-From/EAI-Downgraded-To (or other downgrade header) is in need for DKIM
Whether downgrade header or not, when transmits to destination MTA via MSP, DKIM can’t sign before this
Some small issue in ‘c=relaxed/simple’ when downgrade causes folding/non-folding