Source Routing

[Soren Hilmer <so...@tietoenator.com>]

Hi,

Okay we just ran into the following at a site, where James is setup as a 
mailprocessing gateway.

The backend system (apparently it must have a few years on it's back) uses 
addresses like:
 @YYY.XXX.DK:zzz@XXX.dk

ie. the old RFC-821 source route style. 

Now James hickups at this issuing: 

ERROR smtpserver: Error parsing sender address:  @YYY.XXX.DK:zzz@XXX.dk: No 
local-part (user account) found at position 1

Which is logical as MailAddress is not designed to handle source routes.

But according to RFC-2821 appendix F.2:

"SMTP servers MUST continue to accept source route syntax as specified
in the main body of this document and in RFC 1123.  They MAY, if
necessary, ignore the routes and utilize only the target domain in
the address.  If they do utilize the source route, the message MUST
be sent to the first domain shown in the address.  In particular, a
server MUST NOT guess at shortcuts within the source route."


So to be compliant James actually MUST accept this syntax ;-(

I propose a fix, where we use the MAY above, that is ignore the routes and 
utilize only the target domain in the address.

If you all agree with me that this is something we should (no must) handle, 
and in the proposed manner. 

I will start working on this fix.


--Søren

-- 
Søren Hilmer, M.Sc.
R&D manager		Phone:	+45 70 27 64 00
TietoEnator IT+ A/S	Fax:	+45 70 27 64 40
Ved Lunden 12		Direct:	+45 87 46 64 57
DK-8230 Åbyhøj		Email:	soren.hilmer <at> tietoenator.com


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

RE: Source Routing

["Noel J. Bergman" <no...@devtech.com>]

> The backend system (apparently it must have a few years on it's back)
> uses addresses like: @YYY.XXX.DK:zzz@XXX.dk

> Now James hickups at this issuing:
> ERROR smtpserver: Error parsing sender address:
>  @YYY.XXX.DK:zzz@XXX.dk: No local-part (user account) found at position 1

> So to be compliant James actually MUST accept this syntax ;-(

Please see RFC 2821 #3.3, #3.7, and most importantly, #4.1.1.3, which makes
it quite clear that we are entitled to reject with a 550 the RCPT TO command
that provided a source route.  If you want to support it by stripping the
source route information, that's fine, but I'm just as comfortable issuing
the 550.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org