| |||||||||||||||||||||||||||||||
|
>> Despite my REJECT on body_checks (soft_bounce is no, have checked >> that), some servers are still retrying every 5 minutes resending >> messages that were REJECTED. And as most of my rules are for blocking >> audio/video content for saving bandwith, i'm having bandwith problems >> because of that. Instead of receiving once and rejecting and message >> got bounced, seems some servers are retrying no matter of the REJECT. >> >> So, that's why i'm looking for somehow breaking RFC and closing the >> connection as soon as possible. In that case, i would acchieve the >> bandwith saving, i think, because i wouldnt need to receive the whole >> message (with attachments) for sending the REJECT only at the end of >> the session ..... >> >> > Is there a reason that you have not set the max message size to a value > that accomplishes the same goal? When a remote server connects and > issues the ehlo command, it will immediately be able to determine the > maximum allowed message size without sending any other data. - The > ultimate bandwidth saver. > OP is talking about clients that don't understand that 5xx is a REJECT and is not a temporary failure. hoping that they will check the SIZE argument in a EHLO response line is extremely optimistic.
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com