|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: Don't add domainname to 'To: Undisclosed-Recipient:;'
From: Russ Allbery (rra
stanford.edu)Date: Wed Jun 14 2000 - 15:15:55 CDT
- Next message: Russ Allbery: "Re: dnscache"
- Previous message: Jim Holthaus: "Re: UPPER case virtual domain -RETRACTION-"
- Next in thread: Russ Allbery: "Re: Don't add domainname to 'To: Undisclosed-Recipient:;'"
- Maybe reply: Russ Allbery: "Re: Don't add domainname to 'To: Undisclosed-Recipient:;'"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
laurens van alphen (craxx) <alphen
craxx.nl> writes:
>> Shouldn't Undisclosed-Recipient be in a comment? As in
>> (Undisclosed-Recipient)
> Dunno, it probably SHOULD (as in RFC, but there's a real world).
Nope. Undisclosed-Recipient:; is a perfectly valid RFC 822 address. It's
an empty address group, containing no recipients, that's named
"Undisclosed-Recipient". It's a convenient way of denoting a mailbox that
doesn't actually deliver mail anywhere.
(Undisclosed-Recipipent) is *not* a valid RFC 822 address and would be a
violation of the standard, since the To header is required to contain at
least one mailbox.
-- Russ Allbery (rrastanford.edu) <http://www.eyrie.org/~eagle/>
- Next message: Russ Allbery: "Re: dnscache"
- Previous message: Jim Holthaus: "Re: UPPER case virtual domain -RETRACTION-"
- Next in thread: Russ Allbery: "Re: Don't add domainname to 'To: Undisclosed-Recipient:;'"
- Maybe reply: Russ Allbery: "Re: Don't add domainname to 'To: Undisclosed-Recipient:;'"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]