Email & Spam
This page should really be all about email processing.
These days, however, spam processing is what email is
all about.
On my machines, I see about 90-95% spam.
This page isn't sorted out yet, it was a big enough
section from New Items, and a hot enough
topic to make notes about.
There are also a good selection of email-oriented items in the
Email and News
section of my software page.
Instant summary ... you really want a combination of tools
and strategies
working for you to cut down the spam.
- You need to keep your email addresses from ever getting onto spam
lists ... so they never spam you.
- Must reduce volume of incomming spam and connections to your mail
servers so they and your bandwidth can survive the load.
- Try to sort out valid email transmitters from invalid ones.
- -- All the above is really important, because it is relatively
cheap and reserves your bandwidth.
The steps below cost you bandwidth,
memory, storage, CPU time, etc --
Relatively Cheap -- the spam load is so high that even
the cheap part can bring systems down.
- Look at the content (body) of emails which get through the above
layer, classify them as spam or not.
- Safe valid emails and spam.
- Verify spam/ham to train trainable things.
- Provide access to spam emails so users can verify they are spam,
and pull out the (it always happens) ham message from spam.
- You can use contrib/cidrexpand to allow netblocks in /etc/mail/access.
This performs an expansion in the access file, not a compact
runtime based check. Watch your diskspace on the /etc/mail/access
partition.
If you want to know why these are dead, good places to check are
DNS Based Black/Block Lists
and
SlashDot.
Bolo's Home Page
Last Modified:
Fri Apr 26 10:52:46 CDT 2013
Bolo (Josef Burger)
<bolo@cs.wisc.edu>