Scene: A cafe. One table is occupied by a group of Vikings wearing horned helmets. Whenever the word "spam" is repeated, they begin singing and/or chanting. A man and his wife enter. The man is played by Eric Idle, the wife is played by Graham Chapman (in drag), and the waitress is played by Terry Jones, also in drag.
Man: You sit here, dear. Wife: All right. Man: Morning! Waitress: Morning! Man: Well, what've you got? Waitress: Well, there's egg and bacon; egg sausage and bacon; egg and spam; egg bacon and spam; egg bacon sausage and spam; spam bacon sausage and spam; spam egg spam spam bacon and spam; spam sausage spam spam bacon spam tomato and spam; Vikings: Spam spam spam spam... Waitress: ...spam spam spam egg and spam; spam spam spam spam spam spam baked beans spam spam spam... Vikings: Spam! Lovely spam! Lovely spam! Waitress: ...or Lobster Thermidor a Crevette with a mornay sauce served in a Provencale manner with shallots and aubergines garnished with truffle pate, brandy and with a fried egg on top and spam. Wife: Have you got anything without spam? Waitress: Well, there's spam egg sausage and spam, that's not got much spam in it. Wife: I don't want ANY spam! Man: Why can't she have egg bacon spam and sausage? Wife: THAT'S got spam in it! Man: Hasn't got as much spam in it as spam egg sausage and spam, has it? Vikings: Spam spam spam spam... (Crescendo through next few lines...) Wife: Could you do the egg bacon spam and sausage without the spam then? Waitress: Urgghh! Wife: What do you mean 'Urgghh'? I don't like spam! Vikings: Lovely spam! Wonderful spam! Waitress: Shut up! Vikings: Lovely spam! Wonderful spam! Waitress: Shut up! (Vikings stop) Bloody Vikings! You can't have egg bacon spam and sausage without the spam. Wife: I don't like spam! Man: Sshh, dear, don't cause a fuss. I'll have your spam. I love it. I'm having spam spam spam spam spam spam spam beaked beans spam spam spam and spam! Vikings: Spam spam spam spam. Lovely spam! Wonderful spam! Waitress: Shut up!! Baked beans are off. Man: Well could I have her spam instead of the baked beans then? Waitress: You mean spam spam spam spam spam spam... (but it is too late and the Vikings drown her words) Vikings: Spam spam spam spam. Lovely spam! Wonderful spam! Spam spa-a-a-a-a-am spam spa-a-a-a-a-am spam. Lovely spam! Lovely spam! Lovely spam! Lovely spam! Lovely spam! Spam spam spam spam!
Processing matrix No processing (also doesn’t contribute to spam/nospam collections) Redlist (but does contribute to spam/nospam collections) Doesn’t contribute to whitelist Spam Lover Normal ASSP operation Contributes to whitelist Unfiltered Mail Filtered Mail
When you install ASSP a colony of super-intelligent thermophilus bacteria takes up residence on your CPU and begin reading all your email. They communicate using radio waves directly with the CPU and interface with the ASSP software choosing between spam and nonspam mail.
If you choose to read further this myth will be sadly dispelled, and I take no responsibility for the consequences.
However, you can always refer your users to this slide to prove to them that their email is actually being filtered by super-intelligent bacteria.
ASSP’s primary target audience is mail administrators or system administrators at smallish institutions. If you operate an ISP or a mailhost with a heterogeneous user base, you may not have a good enough consensus about what is considered spam or is not. It should work well with between 1 and 300 client addresses and a mail volume of up to around 100,000 messages per day. Testing has not been done to verify these ranges
ASSP is not for the following:
Individual clients -- ASSP must be installed together with a SMTP server
Domains which receive mail indirectly, for example if you use fetchmail
Addresses of recipients at your site that only receive spam (website spam-bait, ex-employees)
Mail Flow Internet Mail Svr Clients Inbound Outbound Internet ASSP Mail Svr Clients Inbound Outbound Internet ASSP Mail Svr Clients Internet Mail Svr Clients with ASSP Internet Mail Svr ASSP Clients Invalid
Email Flow Internet ASSP GroupWise/ Exchange Clients Inbound Outbound MTA Internet GroupWise/ Exchange Clients MTA ASSP ASSP MTA smtp0 in out spam Not spam white red black grey Bayesian DB Errors 125 25
1999 This is an email that is being sent to the Internet. Th This is an email that is GWIA MTA POA GroupWise Internet
2003 Internet GWIA MTA POA GroupWise sendmail Virtuser table aliases Internet MTA DNS Block List
2004 GWIA MTA POA GroupWise sendmail Virtuser table aliases Internet MTA sendmail SpamAssassin SpamAssassin Internet
2006 GWIA MTA POA GroupWise sendmail Virtuser table aliases Internet MTA ASSP sendmail ASSP spam Not spam white red black grey Bayesian DB Errors sendmail SpamAssassin SpamAssassin Internet
Phase In GWIA MTA POA GroupWise sendmail Virtuser table aliases Internet MTA ASSP sendmail ASSP spam Not spam white red black grey Bayesian DB Errors sendmail SpamAssassin SpamAssassin Internet
Flow with Anti-Virus Internet ASSP Mail Svr Clients Internet ASSP Clients Inbound Outbound Antivirus Mail Svr Antivirus
For example, internet mail needs to connect to ASSP on port 25 (ASSP's listen port), and ASSP can proxy to your mail server on port 125 (or any port you choose) -- ASSP's SMTP Destination. You need to change your mail server to match.
With most client-based filters (POPFile, SpamBayes, SpamAssassin) senders receive NO NOTIFICATION if their mail isn't delivered. With most of these solutions, the user bears full responsibility to VERIFY that no good mail is blocked.
ASSP’s solution to this is that when spam is blocked the SENDER RECEIVES NOTIFICATION, and it does this without generating non-delivery reports that bounce and bounce again because spammers forge their from address.
Issue: Let’s say a client receives a non-delivery report, how can he (not in whitelist) send a message to the organization if he is still not in whitelist? I mean, if the recipient or assp admin does not receive the notification, they will not know that there is a false positive and will not add the unknown client to whitelist...
Solution: Set up an email address and put it in the Spam-Lover Address configuration option. Then modify the spam error message to direct people to "500 Mail appears to be unsolicited (spam) -- please forward this email to firstname.lastname@example.org if you feel this is in error." Any false positives that bounce back to clients will hopefully be reported to the Mail Admin via the spam lover address (they just forward it), assuming they read the rejected email.
Any user can help to improve ASSP’s spam filtering accuracy. Users can use it to add addresses to the whitelist, report spam, or false-positives. To use it, you must have it enabeled in the configuration, and have names set for the addresses. The interface only accepts mail addressed to addresses at any of your localdomains, and only from "Accept All Mail" hosts, or authenticated SMTP connections.
assp-white -- for whitelist additions
assp-spam -- to report spam that got through
assp-notspam -- to report mis-categorized spam
Whitelisting: Assuming that your local-domain is yourdomain.com, to add addresses to the whitelist, you’d create a message to [email_address] . You can either put the addresses in the body of the message, or as recipients of the message. For example, if you wanted to add all the addresses in your address book to the whitelist, create a message to [email_address] and then add your entire address book to the BCC part of the message and click send. Note that no mail will be delivered to any address except [email_address] (and that won't actually be passed to your mail transport). Within a short time you'll receive a response from ASSP showing the results of your mail.
False Negatives: To report a spam that got through, simply forward the mail to [email_address] . It's best to forward it as an attachment, but you can just forward it normally if you must. In a short time you will receive a confirmation.
False Positives: The process is the same to report a miscategorized spam, but send it to [email_address] .
stat.pl Statistics [root@smtp]# perl stat.pl /tmp/m.log As of Mon Jan 22 21:48:46 2007 the mail logfile shows: 0 proxy / smtp connections 253 were dropped for attempted relays (0.0% of total). 31523 messages, 16758 were spam (53.2%) in 65 days for 485.0 messages per day or 257.8 spams per day 1518 additions to / verifications of the whitelist (23.4 per day) 14643 were judged spam by the bayesian filter (87.4% of spam) 2115 were to spam addresses (12.6% of spam) 0 were rejected for executable attachments (0% of spam) 10121 were sent from local clients (68.5% of nonspam) 842 were from whitelisted addresses (5.7% of nonspam) 0 messages were passed to SPAMLOVERs 3802 were ok after a bayesian check (25.8% of nonspam) 1498 addresses are on the whitelist 0 hits on the blacklist 0 resulted in spam (0.0% of Bayesian spam, 0.0% of blacklist hits) 0 resulted in non-spam (0.000% of blacklist hits)