_M
PS: I'm sure that certain "tweaks" could easily be added to the process to help also... such as anything explicitly white-listed passing through immediately and so forth. An example might be if a corp used their product names and IDs in special rules in Message Sniffer, then that rule group's code might be used to white-rule any messages to the sales department for immediate transit.
At 11:04 AM 9/6/2003 -0700, you wrote:
> A feature that delays incoming mail from unfamiliar (new) source IPs would > allow heuristic tests (like Message Sniffer) and rbls time to add coding > for the messages before processing them. That is, if the connecting IP is > unknown then Declude could park the message in a folder for some amount of > time (perhaps a day, a half day? user defined). When the time period is up > then Declude would process the message as if it were new and if it passed > all the tests it would be put in the spool for normal delivery.
What about that new client you just got that gets hundreds of legit messages per day. The IPs of the senders will be unknown to you. Are you going to hold all of those?
John Tolmachoff MCSE CSSA Engineer/Consultant eServices For You www.eservicesforyou.com
---
[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.
--- [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.
