MyOn Sunday 14 November 2004 9:17 am, Julian Mehnle wrote:
John Jolet [EMAIL PROTECTED] wrote:
users can see what messages have been rejected by skimming over a list of recently rejected messages once or twice a week (see an example here[1]). This practice has proven to work well for me and my users. :-)
References: 1. http://julian.io.link-m.de/misc/rejected-messages
An excellent report. I'm inspired.
I would agree with that practice, except in this day and age of spoofed addresses and zombies, that bounce is (a) unlikely to be read and (b) unlikely even to go to the right place. I would personally tend to a policy of quietly quarentining and cleaning out the directory of files > 30 days or so...
The beauty of rejecting the message is that you are not responsible for the bounce delivery. If the bounce is not deliverable your quarantine contains useless residue sent by someone or some process wishing harm. If the bounce is deliverable it tells the sender their message contains something they probably didn't know was included, and the bounce is their clue that they have a problem. Meanwhile you take solace knowing that your systems prevented the spread of something bad and your management can be pleased it was done with great economy.
It is the most intelligent way of handling messages you have no intention of delivering while still giving the legitimate sender a second chance to communicate.
dp _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
