> To clarify a point though: do you implement a BOUNCE to the domain's > postmaster of the offending server?
We haven't found this useful, since so much spam goes to the "known good" postmaster@ and abuse@ is not as common as it should be. At any rate, we don't BOUNCE the messages that are in question here, but ALERT the sender and direct them to their IT group (and assure them that it's probably not their fault, and that the mail did go through). > It's a bit much for me to chew on though, given a) the processing > power available. I'm not sure that the processing power should be in doubt--or, I should say, if it's that close, you should have Declude running on a dedicated box. > b) the relaxed time frame to deliver the mail SMTP is not a real-time medium, so another few seconds should be alright--depending on the payoff, of course. > c) the relevant worth of the time to implement given the time we > spend on filters Now THAT computes! :) -Sandy --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
