[EMAIL PROTECTED] wrote:
ok - I just wanted to make sure. I really only asked because what I saw in the logs made me think that the error message was sent before the "\r\n.\r\n". I tested by: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
- I had two test servers both setup with james (Sender, Receiver)
- I set the Receiver to a max message size of 7MB
- I set the Sender to a max message size of 0MB (unlimited)
- When I sent a 20MB file from Sender to Receiver I saw the following (very rough times from memory but I can repeat and get more accuruate timings if anyone cares. (I don't really at this point since I really wanted to solve the bounce issue I was having originally).
1. Receiver.smtp.log time 0 - connection accept and message started to be transmited
2. Receiver.smtp.log time 1 minute - message to large (552)
3. Sender.mailet.log time 3 minute - error message 552 message too large
I made an assumption that message #2 on the Receiver generated the error message back to the Receiver; but based on what you said I assume this is informational that an error message will be sent once the message has been completely sent.
However, wouldn't this behavior allow for a denial of service attack? Someone could repeatedly send large files and clog up my bandwidth......
Chris....
-- 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]
