Rodrigo Severo <[EMAIL PROTECTED]> wrote: > I'm getting a [552] > error on the 21st recipient and beyond, not a 4xx. "552 after RCPT TO" is a special case: it is actually a 4yz temporary error response, even though it starts with a 5! (It was defined this way to reduce problems caused by a small mistake in RFC 821. For an explanation of this, search for the word "incorrectly" in RFC 2821.)
So, I think the behavior I described should still happen for you. To wit (same paragraph as before, with 452 changed to 552): The server rejects the 21st recipient with a 552 response code. The client proceeds to the DATA phase, to complete the current transaction for delivery to recipients 1 through 20, and also queues another transaction using the same message data, for delivery to recipients 21 through N. Is this what you are experiencing? ------------------------------------------------------- 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
