> Let me clarify my question a bit. When I say "continues to send the > message" I mean the following use case: > 1. james connects to remote server and starts to send a 20MB > (example) > email message > 2. the other server sends a 552 error code after james sends > around 7MB > of the email > - the other server is configured to reject anything larger than 7MB > 3. james continues to send the remaining 13MB > 4. when done sending the 13MB, the 552 error code is > processed by james > and a bounce back to the sending user > is generated (i.e., the email is sent taken off the queue and not > resent to the recipient) > > From what I can tell using some rough tools (ntop), step #3 > in my use > case is occurring. I would have expected james to handle the > error code > when it received it at step #2 and stopped sending the > remaining portion > of the email. > > Is this expected behavior?
I don't think that the 552 could be sent before the "\r\n.\r\n" of the sending client. So the server can say "552 message too large" only after it fully received the message. Imho, this is expected behaviour. We should check the RFC for this, but I think this is correct. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
