Re: [Assp-user] Redlist --> Confusion Gone... I think

Wed, 02 Aug 2006 19:02:34 -0700

It would be nice if the redlist functioned in the way I described it functioning in my post earlier today (I have pasted the redlist portion of the post below).  Of course since it doesn't function like that, to get the same affect, change the default saving location of Bayesian non-spam to 4; by changing it to 4, incoming non-spam email won't get saved to the notspam directory and manually whitelist all senders of list emails or legitimate spam.  Net affect = no corpus pollution.

On another note, email that was tagged as spam by ASSP is removed from the spam directory if the sender is whitelisted; will spam email that has been tagged as notspam be removed from the notspam directory once a report is made to the system that the email is in fact spam (incoming nonspam email being saved to notspam directory is default behavior)?  If so, then you can allow incoming non spam email to be saved in the notspam directory (Of course legitimate spam that has similar qualities to unsolicited spam will corrupt the corpus).  If it isn't true, then allowing incoming non spam email to be saved into the notspam directory will pollute the corpus; emails that are spam that the system believes aren't will end up being saved in the notspam directory and pollute the corpus.

Am I correct in my thinking or am I wrong?

What is pasted below is incorrect

Redlist/NotRedList:


    A red list is a list of senders who send you emails that have the same qualities as unwanted spam; a red list is also a list of sender who send you emails that you will never respond to. If the received email has spam qualities and/or you will not respond to the email, the sender of the email must be redlisted.

    When to redlist:

  • You receive email from a department store informing you about a sale they are having; You receive email every Friday informing you of the weather forcast for the ucoming week.

  1. Condition 1: store sales catalog email → has spam qualities → redlist sender

  2. Condition 2: store sales catalog email → you will not respond to it → redlist sender

  3. Condition 3: store sales catalog email → condition 1 and condition 2 are true → redlist sender

  4. Condition 4: weather forcast email → only condition 2 is true → redlist sender

How to redlist:

  • To redlist a sender, forward as an attachment an email you have received from them to [EMAIL PROTECTED].

  • To remove a sender from the redlist, forward as an attachement an email you have received from them to [EMAIL PROTECTED].


sincerely,

Travis Forghani
IT Administrator
Bowman Enterprises, Inc.

Cell: 919-795-9298
Office: 919-894-3662, Ext. 34

[EMAIL PROTECTED]

This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law.  If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited by law.  If you have received this communication in error, please notify me immediately.


geniusfreak wrote: 
On 8/2/06, Fritz Borgstedt <[EMAIL PROTECTED]> wrote:
  
Questions and Answers for users of ASSP Anti-Spam SMTP Proxy
<[email protected]> schreibt:
    
Though it is sad, i would have liked it to do what we thought it did.
(did that make sense?)
      
What do you think, the redlist/redre should do?

    

Prevent additions to the corpus.

So for instance if i was sent an email from someone on the redlist
ASSP would process the message but not add the processed message to
the spam corpus (if it was determined to be spam).

I'm not married to the idea of the RedList doing this but it would be
nice to have the functionality even if it was in a sort of
NoCorpusList.

P.S. thanks for clearing this up for us.
Kevin

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user


  
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to