> I tested by: > > - 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......
This behaviour simply double the bandwith used: once to receive the message, once to send the bounce. You can configure james to avoid creating the bounce or to create the bounce with no message attached. The important thing is to not have loops, and you should not have loops: if you have message loopings that provide us more informations! > Chris.... Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
