> To: Majordomo-Owner
> From: Majordomo
> Subject: MAJORDOMO ABORT
> MAJORDOMO ABORT
> HOSTILE ADDRESS
> /PN=JIM.JA.FEE/DD.ID=JA.FEE/ADMD=TELECOM.CANADA/C=CA/@resonet.com
> Don't remember seeing this documented anywhere. Can anyone help?
Here's what I could find in rfc822 about this checking address syntax activity:
A mailbox specification comprises a person, system or pro-
cess name reference, a domain-dependent string, and a name-domain
reference. The name reference is optional and is usually used to
indicate the human name of a recipient. The name-domain refer-
ence specifies a sequence of sub-domains. The domain-dependent
[e.g. domain-dependent-string@host.domain]
string is uninterpreted, except by the final sub-domain; the rest
of the mail service merely transmits it as a literal string.
Thus majordomo is not rfc-822 compliant in this respect it seems.
Also from rfc1123: (majordomo is not a transfer agent in this sense
of the below - still this provides some clues as to what is appropriate.)
RFC1123 MAIL -- SMTP & RFC-822 October 1989
5.2.16 RFC-822 Local-part: RFC-822 Section 6.2
The basic mailbox address specification has the form: "local-
part@domain". Here "local-part", sometimes called the "left-
hand side" of the address, is domain-dependent.
A host that is forwarding the message but is not the
destination host implied by the right-hand side "domain" MUST
NOT interpret or modify the "local-part" of the address.
When mail is to be gatewayed from the Internet mail environment
into a foreign mail environment (see Section 5.3.7), routing
information for that foreign environment MAY be embedded within
the "local-part" of the address. The gateway will then
interpret this local part appropriately for the foreign mail
environment.
...
Only the target host (in this case, "relay1") is permitted
to analyze the local-part "user%domain%relay3%relay2".
References:
|
|
