>> 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
[X] +1 - Release james 2.2.0RC5 as James 2.2.0
/craig
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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 ans
Noel,
An immediate release of DBCP 1.2.1 based on CVS head sounds OK.
Otherwise we'll get more of those incompatibility bug reports.
I will see what I can do this weekend.
-- Dirk
Noel J. Bergman wrote:
Dirk,
Do we need to immediately issue a DBCP and Pool 1.2.1 with the 1.4
dependencies removed?
