1 / 6

Introduction of Internationalized Email Headers for UTF-8 Support in SMTP Protocol

The update to internationalized email headers introduces a new "i18n-email" header to facilitate UTF-8 encoding in email header fields, enhancing communication across different languages. This change allows UTF-8 headers during transmission when the iEmail SMTP extension is advertised. While RFC 2822 rules for header names remain unchanged, fields such as Subject, Comment, and Keywords can now utilize UTF-8 characters. New syntax guidelines are established for internationalized address specifications, improving the ability to send emails with non-ASCII characters efficiently.

maegan
Download Presentation

Introduction of Internationalized Email Headers for UTF-8 Support in SMTP Protocol

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Internationalized Email Headers Jeff Yeh TWNIC

  2. Change from -00 • Remove content related to SMTP protocol. • Introduce new “i18n-email” header. • <addr-spec> syntax.

  3. Internationalized Email Headers • To allow UTF-8 in email header fields. • UTF-8 headers are permitted in transmission, only when the SMTP extension iEmail is advertised. • New header “i18n-email” is introduced to identify internationalized emails.

  4. Impact to headers • The rules in RFC 2822 for header names are not changed. • <unstructured>, <comment> and <phrase> are allowed to use UTF-8. - ex: Subject, Comment, Keyword … • <date-time>, <msg-id> remains the same definition as in RFC2822. - ex: Date, Message-ID, In-Reply-To and References …

  5. Impact to <addr-spec> mailbox = new-name-addr / new-addr-spec new-name-addr = [display-name] new-angle-addr new-angle-addr = [CFWS] "<" new-addr-spec ">" [CFWS] new-angle-addr =/ obs-angle-addr new-addr-spec = [addr-spec] non-ASCII-addr-spec new-addr-spec =/ addr-spec “Jeff Yeh” <jeff@twnic.net.tw> “Jeff Yeh” <葉士豪@台網中心.tw> “Jeff Yeh” <jeff@twnic.net.tw 葉士豪@台網中心.tw>

  6. Thank you

More Related