home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!utcsri!newsflash.concordia.ca!garrot.DMI.USherb.CA!uxa.ecn.bgu.edu!mp.cs.niu.edu!linac!uwm.edu!ogicse!network.ucsd.edu!news!manta!usenet
- From: key@blacksea.csc.com (Gerry Key)
- Newsgroups: comp.sys.next.misc
- Subject: NeXTMail: Return Address Parser
- Keywords: NeXTMail Address Parser
- Message-ID: <1992Nov17.180630.2352@nosc.mil>
- Date: 17 Nov 92 18:06:30 GMT
- Article-I.D.: nosc.1992Nov17.180630.2352
- Sender: usenet@nosc.mil (Network News)
- Organization: Naval Ocean Systems Center, San Diego, CA
- Lines: 29
-
- NeXTMail appears to have problems replying to a From-address with imbedded
- newlines. For example, if the From: line of an incoming message appears
- as follows:
-
- From: Joe Schmoe
- <JOE_SCHMOE@SOMEHOST.COM>
-
- because some mailer along the way inserted a newline in a too-long
- address, when NeXTMail responds to such a message you wind up with:
-
- To: Joe Schmoe
-
- I thought RFC 822 specified that mailers were supposed to throw out
- newlines, tabs, and other extraneous characters when creating a To: line
- from a From: line, and to extract only the well formed addresses (i.e., in
- this case, what's in the angle brackets).
-
- We reported this problem to NeXT, but were told no one else had reported
- it and to contact NeXT Technical Support where they would listen to our
- problem for a fee. To me, this is a bug, not a user support problem.
-
- Has anyone (everyone?) else seen this behavior? Is there a work-around?
-
- --Gerry Key
- Computer Sciences Corporation
- San Diego, CA
- Internet: key@csc.com (NeXTMail OK)
- FAX: 619.225.2583
- Voice: 619.225.2504
-