Rodrigo Severo <[EMAIL PROTECTED]> wrote: > I am not sure Courier is getting the 552 error *imeadiatly after* RCPT > TO. I can't be sure from the mail delivery status message I'm getting.
You can tell by counting the bounces. If all N recipients bounce, the 552 was presumably a response to the DATA command or the data. If only N-20 recipients bounce, you can be sure the 552 was a response to RCPT TO, because there is no other time when a response can affect only a subset of the recipients. > But I bet it is as I get one different UNDELIVERABLE MAIL message per > recipient after the 20th. Yes, you win your bet. > 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. Possibly you could patch it yourself? I haven't looked at the code to know whether this would be easy. ------------------------------------------------------- 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
