[ http://issues.apache.org/jira/browse/JAMES-296?page=all ]
Soren Hilmer resolved JAMES-296:
Resolution: Fixed
James does not handle Source Routing
Key: JAMES-296
URL: http
The backend system (apparently it must have a few years on it's back)
uses addresses like: @YYY.XXX.DK:[EMAIL PROTECTED]
Now James hickups at this issuing:
ERROR smtpserver: Error parsing sender address:
@YYY.XXX.DK:[EMAIL PROTECTED]: No local-part (user account) found at position 1
So to
After reading some more RFC-2821 (and a conversation with a co-worker of
mine), we can only see that a 550 response is permitted for source routing in
relation to RCPT TO commands.
We get the source route in a MAIL FROM command. The specific sections (3.3 and
4.1.1.2) does not mention a 550
:
-
Key: JAMES-296
Summary: James does not handle Source Routing
Type: Bug
Status: Open
Priority: Major
Project: James
Components:
Mailet API
Fix Fors:
2.2.1
Versions:
2.2.0RC5
Assignee: Soren Hilmer
Reporter: Soren Hilmer
The backend system (apparently it must have a few years on it's back)
uses addresses like: @YYY.XXX.DK:[EMAIL PROTECTED]
Now James hickups at this issuing:
ERROR smtpserver: Error parsing sender address:
@YYY.XXX.DK:[EMAIL PROTECTED]: No local-part (user account) found at position 1
So to
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:[EMAIL PROTECTED]
ie. the old RFC-821 source route style.
Now James hickups at this
