This is a discussion on Re: [courier-users] Re: MAXRCPT per domain within the Courier-Imap forums, part of the Mail Servers and Related category; Trev wrote: >Rodrigo Severo <rodrigo.lists@fabricadeideias.com> wrote: > > > >>I'm getting ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Trev wrote:
>Rodrigo Severo <rodrigo.lists@fabricadeideias.com> 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. > > After seeing the relevant RFC 2821, I see that the behaviour you described should happen to me. >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? > Sadly not. Courier is treating the 552 error as a permanent error AFAICT. 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. But I bet it is as I get one different UNDELIVERABLE MAIL message per recipient after the 20th. 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. Is this the reason Courier doesn't treat a 552 error as 452 after RCPT TO? Or does it? 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 courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users |