.
FRDCSA | internal codebases | Anti-Spam Console

Anti-Spam Console Architecture Diagram: GIF

Jump to: Project Description | Capabilities

Project Description

Uses a tagged corpus of spam to test accuracy of filter. Install spam-benchmarks-data package on sender machine. Handles all the different things we need to do regularly with spam filtering.

Capabilities

• o /var/lib/myfrdcsa/codebases/internal/antispam-console/doc/automate_spamcop_submissions can be used for a ticket.
• antispam-console in other words, determine if there is a probability that the message is important like that. Also, have passcodes that will ensure the message gets through the spam filtering.
• antispam-console has to help with ensuring that certain mail gets through, like "URGENT - don't do this" when it is legitimate.
• antispam-console make sure do not drop encrypted zip as per Thu Aug 3 17:09:50 CDT 2006 incident.
• antispam-console Write a Plugin for SpamAssassin to catch some of this new mail. Adjust the rules and we should be done for now. We can always build my system out of a plugin. That would save a lot of work.
• antispam-console - In order to determine who is actively cleaning their spam folders, occassionally send a known spam to them and search people's folders for this spam message.
• antispam-console - The rule learner for the system has to learn rules that have a lot of data to substantiate their effectiveness, for instance 50/50. It should also allow me to write additional production rules in Perl, for instance, has met 5 or more rules... etc.
• Would be nice if antispam-console 's filters gave confidence values for their classifications.
• antispam-console - find indications of scams, and actually use nlp to search these outl
• Would there be any benefit to antispam-console to setup honey pot email addresses.
• antispam-console - if we are to use CRM114 - checkout http://crm114.sourceforge.net/CRM114_Mailfilter_HOWTO.txt
• antispam-console - if we are to use CRM114 - checkout http://search.cpan.org/~tvierling/Sendmail-PMilter-0.95/examples/crm114-milter.pl
• Or maybe antispam-console should use IMAP::Client
• antispam-console - to use dbmail, use the Net::IMAP module.
• antispam-console - Certain emails are long and the rules should realize this and not take forever on regular expressions.
• antispam-console should email me if it is running in auto and I need to draft custom rules or something.
• antispam-console - We're going to have to deal soon with Email that contains part ham part spam
• antispam-console should generate debian packages, which are then uploaded into our archive and installed by the different servers - make sure that the process is actually stopped.
• antispam-console possible trick: Depends on what he's doing it might work. I catch most spam based on sender behavior rather than message content. For example, anyone can do this trick. Set your highest MX record (add a new one) to an IP address that doesn't exist. Some spammers spam the highest MX first and it that doesn't work the skip it and move on. I get rid of 120,000 spams a day using that trick.
• antispam-console possible trick: Depends on what he's doing it might work. I catch most spam based on sender behavior rather than message content. For example, anyone can do this trick. Set your
• antispam-console - Keep junk email directories rather then deleting them, as it simplifies retraining from scratch. If you don't want sa-learn to have to wade through them, then move them to a different directory. If you want to use less disk space, then compress them.
• For antispam-console Retrieve and store forwarded spam messages and use these for testing purposes.
• antispam-console should have a "spam accuracy" trace.
• antispam-console, Check out http://terri.zone12.com/doc/academic/crossroads/
• antispam-console should use named entity and noun phrase analysis to improve bayesian results.)
• antispam-console - note If you see the from email address has a name and then the email address doesn't correlate to the name... there will be another person's name, even better the to address has a different email. Anything hitting old email addressed, tag it.
• setanta should use antispam-console (SA) to filter mail.
• antispam-console uses sa-hits, also check out redwall
• antispam-console should use imapassassin, sa-teach
• antispam-console should be sure to whitelist users who are in rbls but shouldn't be.
• antispam-console: in order to develop antispam messages, take a group of related spams, and write s couple of sentences describing what is particular about this message. Then use that to construct expressions.
• antispam-console should spot check outgoing mail to ensure that it is not spam, and if it is, setanta will block that IP or whatever is necessary, and initate the appropriate messages.
• antispam-console needs to schedule the pruning of the database. It also must handle isolating mail that has slipped through the spam network.