Trev wrote:
Rodrigo Severo <[EMAIL PROTECTED]> wrote:
A client (Courier in this case) SHOULD treat a 552 error after a RCPT TO
command as 452. But the text says SHOULD and not MUST.
I think it would be desirable for Courier to implement the RFC's
suggestion, and treat a RCPT TO response of 552 as a synonym for 452.
It would be very helpful in some situations (such as the one you are
experiencing now) and I don't think it would ever be harmful.
I definitely agree with you.
Possibly you could patch it yourself? I haven't looked at the code to
know whether this would be easy.
I haven't looked at this part of the code for a long time but I don't
think it would be difficult.
The real problem here is that I don't think Sam would accept this patch
so it would be a short lived effort.
Regards,
Rodrigo Severo
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
