LogSat Software

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Feature request:

I would like to see some sort of rule set that over-rides ALL white lists.  I know this sounds counter intuitive but we have several users that do not want to be filtered and when those users get actual spam, there is usually a long CC list.  ALL the people on the CC list therefore get the messages and suffer due to the one that has elected to be unfiltered.

One thought is if a message has an address on the unfiltered to list AND there are several recipients, the odds are that the message is spam so dropping the message would be low risk.  

Also, as the system administrator, I get all messages to "root".  The root address, in our case should be server messages only and I do not want ANY mail addressed to "root" if it comes from the outside.

Second request:
Our autowhitelist builds up a lot of addresses that will never be sent from again and with a lot of list servers that put huge random strings before the "@" in the address.  Is there a way to prevent these from being entered at all or alternately, some way to keep track of how many times an autowhitlisted entry gets a "hit" so that we can manually prune the list once in a while?

Aren't I just a pain in the arse?

Regards, 

Dan S.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Desperado Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 27 January 2005 Location: United States Status: Offline Points: 1143	Post Options Post Reply Quote Desperado Report Post Thanks(0) Quote Reply Topic: Feature Request(s) Posted: 26 October 2004 at 1:20pm
	Feature request: I would like to see some sort of rule set that over-rides ALL white lists. I know this sounds counter intuitive but we have several users that do not want to be filtered and when those users get actual spam, there is usually a long CC list. ALL the people on the CC list therefore get the messages and suffer due to the one that has elected to be unfiltered. One thought is if a message has an address on the unfiltered to list AND there are several recipients, the odds are that the message is spam so dropping the message would be low risk. Also, as the system administrator, I get all messages to "root". The root address, in our case should be server messages only and I do not want ANY mail addressed to "root" if it comes from the outside. Second request: Our autowhitelist builds up a lot of addresses that will never be sent from again and with a lot of list servers that put huge random strings before the "@" in the address. Is there a way to prevent these from being entered at all or alternately, some way to keep track of how many times an autowhitlisted entry gets a "hit" so that we can manually prune the list once in a while? Aren't I just a pain in the arse? Regards, Dan S.

LogSat Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 25 January 2005 Location: United States Status: Offline Points: 4104	Post Options Post Reply Quote LogSat Report Post Thanks(0) Quote Reply Posted: 01 November 2004 at 11:26pm
	Dan, As you can tell from the delay in responding we've thought about these for a while. We've tried in the past to "limit the damages" when an email arrives that is spam, but is sent to multiple recipients, one of which is whitelisted. Sometimes emails with multiple CC arrive as separate emails, one per recipient, in which case this is a non-issue. The problem occurs when it's a single email with multiple RCPT TO commands, one of which triggers the whitelist filter. Du to the innerworkings of SpamFilter, it's rather complex to take that single email, split it so part can delivered to the one whitelisted user, and quarantined for all others. Doing so would require major changes that will take away development in other areas. A similar answer applies to the autowhitelist. It's optimized for speed to account for the fact that it can grow pretty much. Adding more data than what it has, and updating it everytime it's used will have a toll on performance. We've though about adding a single field for each line with a number showing the amount of times that entry was received, but then we'd have to check every incoming email against it no matter what, and potentianlly updating it very frequently. Again implementing all this would take a lot of work, and the same comment for the previous case applies... Sorry! Roberto F. LogSat Software

LogSat Software

Site Navigation[Skip]

Spam Filter ISP Support Forum

Feature Request(s)