kaih(_at_)khms(_dot_)westfalen(_dot_)de (Kai Henningsen) writes:
fw(_at_)deneb(_dot_)enyo(_dot_)de (Florian Weimer) wrote on 02.12.01 in
<871yidh4mk(_dot_)fsf(_at_)deneb(_dot_)enyo(_dot_)de>:
The source routing syntax in RFC 2822 differs considerably from
RFC 822. Is this intentional?
It does? How?
RFC 822 route-addr: <@host1(_at_)host2:user(_at_)target>
This is incorrect. The rule specified in RFC 822 gives:
RFC 822 route-addr: <@host1,@host2:user(_at_)target>
<@host1,,@host2:user(_at_)target>
Specifically, a route is defined as
route = 1#("@" domain) ":" ; path-relative
I suspect you're misinterpreting the #. # specifies a list of elements,
each separated by one or more commas. And whitespace may also appear.
RFC 2822 obs-angle-addr: <@host1(_at_)host2:user(_at_)target>
<@host1,@host2:user(_at_)target>
<@host1 @host2:user(_at_)target>
<@host1,,@host2:user(_at_)target>
This unfortunately, does look to be a correct reading of the production:
obs-domain-list = "@" domain *(*(CFWS / "," ) [CFWS] "@" domain)
I believe this rule should be something like:
obs-domain-list = "@" domain *([CFWS] "," *(CFWS / ",") "@" domain)
Ned