Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Full RFC822 compatibility
From:
Jacob Palme QZ <[log in to unmask]>
Reply To:
Jacob Palme QZ
Date:
07 Apr 87 10:36 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
If you intend to write an RFC822 parser, please, please take
the advice of everyone who has done so until now:
 
Do not write a parser which accepts only what is specified in
RFC822 exactly and nothing else. Rather, write a parser which
accepts and tries to understand everything which remotely looks
like RFC822! Otherwise you will get into endless trouble.
 
Example of illegal RFC822 things you should accept:
 
John Smith <JS@HOST>
should correctly be
"John Smith" <JS@HOST>
 
Message-ID: <AAA&BBB@CCC>
should correctly be
Message-ID: <"AAA6BBB"@CCC>
 
Message-ID: <AAA@BBB> (From my perfect mailer)
should correctly be
Message-ID: <AAA@BBB>
 
etc. etc.
 
And please do accept things, even if they are on different lines.
Thus you should accept:
To:     "a very very very very very very very very very long name"
        <AAA@BBB>
Even though the name is split on several lines.
 
I could give you unlimited more examples.

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV