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?
Chris....
[EMAIL PROTECTED] wrote:
I have another question though. I was able to setup my test environment to test out the bounceProcessor (which works correctly). I can see in the logs when a message is rejected by the other server. However, James continues to send the message.
Should James stop sending the message when it receives an error message back from the other email server?
It depends on the type of message it receive from the remote server: there are permanent errors and transient errors. E.g: a connection problem will be retried a number of times before a final failure.
Stefano
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.8 - Release Date: 5/10/2005
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
