On 16 Oct 2016, at 18:08, Ruga wrote:
From: "Dianne Skoll <d...@roaringpenguin.com>" <unrela...@spammer.org>
In my servers, the above string is not RFC compliant,
Are you writing your own RFC's? That's cool: the IETF could do with some
competition. Where are you publishing them and accepting comments?
The IETF's RFC5322 includes this ABNF ultimately specifying the From
header:
local-part = dot-atom / quoted-string / obs-local-part
domain = dot-atom / domain-literal / obs-domain
domain-literal = [CFWS] "[" *([FWS] dtext) [FWS] "]" [CFWS]
dtext = %d33-90 / ; Printable US-ASCII
%d94-126 / ; characters not including
obs-dtext ; "[", "]", or "\"
qtext = %d33 / ; Printable US-ASCII
%d35-91 / ; characters not including
%d93-126 / ; "\" or the quote character
obs-qtext
quoted-pair = ("\" (VCHAR / WSP)) / obs-qp
qcontent = qtext / quoted-pair
quoted-string = [CFWS]
DQUOTE *([FWS] qcontent) [FWS] DQUOTE
[CFWS]
word = atom / quoted-string
phrase = 1*word / obs-phrase
display-name = phrase
angle-addr = [CFWS] "<" addr-spec ">" [CFWS] /
obs-angle-addr
name-addr = [display-name] angle-addr
addr-spec = local-part "@" domain
mailbox = name-addr / addr-spec
mailbox-list = (mailbox *("," mailbox)) / obs-mbox-list
from = "From:" mailbox-list CRLF
It seems to me that Dianne's example is entirely legal as a From header,
essentially because you can put almost anything inside a quoted-string.
You'll note that I've left out all the still-legal 'obs-*' component
specs because you do not need them in this case. Note that RFC5322 did
not expand what is allowed in a From header.
