Ken Murchison <ken(_at_)oceana(_dot_)com> writes:
2.4.2.3. Addresses
A number of commands call for email addresses, which are also a subset
of strings. These addresses must be compliant with [IMAIL].
Implementations are required to parse as specified by the "mailbox"
definition in section 6.1, not as "address" is specified in that
section. "Group" syntax MUST NOT be used (if multiple addresses are
requierd, use a string-list).
^^^^^^^^
Are you punting on the fact that "mailbox" allows "route"? Or do you
want to restrict "mailbox" to:
mailbox = addr-spec
/ phrase "<" addr-spec ">"
That is the restriction I want. source routes are obsolete, are listed
as obsolete in drums, and I see no reason to allow them.
New text:
A number of commands call for email addresses, which are also a
subset of strings. These addresses must be compliant with
[IMAIL]. Implementations are required to parse as specified by
the "mailbox" definition in section 6.1, with the additional
constraint that the "route" part MUST NOT be used. Note that
the "address" part specified in section 6.1 is not the syntax
part used here: "group" syntax MUST NOT be used (if multiple
addresses are requierd, use a string-list). Implementations
MUST ensure that the addresses are syntactically valid, but need
not ensure that they actually identify an email recipient.