On Wed, 07 May 1997 09:58:30 EDT, you said:
> --> Error description:
> Error-For:  [log in to unmask]
> Error-Code: 3
> Error-Text: 553 <@CNSIBM.ALBANY.EDU:[log in to unmask]>...
>         Source routed envelope sender rejected (See RFC 822, section 6.2.7)
>
> Error-End:  One error reported

Plenty of blame to go around here.

Citing RFC1123, section 5.2.19:

      5.2.19  Explicit Source Routes: RFC-822 Section 6.2.7

         Internet host software SHOULD NOT create an RFC-822 header
         containing an address with an explicit source route, but MUST
         accept such headers for compatibility with earlier systems.

In other words, you shouldn't be generating them, but they are explicitly
required to accept them.

RFC1123, section 5.2.6 says this:

         A receiver-SMTP MUST accept the explicit source route syntax in
         the envelope, but it MAY implement the relay function as
         defined in section 3.6 of RFC-821.  If it does not implement
         the relay function, it SHOULD attempt to deliver the message
         directly to the host to the right of the right-most "@" sign.

This, in combination with section 5.2.19, basically says that you *must*
accept an address of the form @dom1.com:[log in to unmask], but that you are
totally within your rights to just toss the [log in to unmask]:' and keep going.

I've cc'ed [log in to unmask] on this...

--
                                Valdis Kletnieks
                                Computer Systems Senior Engineer
                                Virginia Tech