LisaNov2004TutorialT9 < CF

CF Web>CscfSpecific>LisaNovember2004>LisaNov2004TutorialT9 (2007-06-13, LawrenceFolland) (raw view)

---+ LISA 2004 - Combating Spam..., David Skoll

Using MIMEDefang.

A big con is that we can't send back different reply codes to the bad guy.

The multiplexor is to avoid multi-threaded perl - they think it's evil.  It also allows the milter to talk directly to the child processes without going through the multiplexor.

We can implement this in MTAs other than sendmail at the mimedefang process.

Not convinced there's any performance gain in having the filter on a different machine...

There's a difference between CONTINUE and ACCEPT.

defang and the multiplexor must run on a single machine - they share files.

sendmail itself still runs its own checks - but still calls defang stuff without saying it's going to fail anyway.  :(

We can't distinguish between a HELO and an EHLO.

There's some sanity checking - if you issue conflicting codes and errors, it will change the code for you.

David does not recommend trying to implement tarpits or firewalls.

Later versions of defang have an interlock with a virus scanner - it disables action_notify_sender if a virus is detected, for instance.

SURBL lists URLs that are used to sell spam (within the message body).

If the ultimate SMTP recipient server is down, it generates a tempfail.  Also you can increase the load on end machine, and it doesn't cache results (but you can write this yourself).

sendmail 8.13 has throttling - use that instead because it's much more efficient.

(p126)

Issues to consider when using streaming:
   * get an email address, not a local user - breaks on aliases
   * you may not be guaranteed that the user has a local account on the MD machine - so store it in a database
   * can run into scoring issues - it may return the same SA object each time


Tradeoffs with stacking MD and SA milters:
   * increases overhead
   * two config files
   * but if SA milter is well written, MD can use the spamc daemon instead of just calling the SA Perl module - woo hoo!

Look at Spamassassin 3.  Might use tick requests to queue up salearn stuff.

p138 - you can implement SPF with it.  Ugly though.  He uses it for hotmail and yahoo.

Recommends against using RBLs to *reject*.  spamhaus is good.  He recommends also using Perl 5.8 to implement this, says it's better than < .8.

Ideally, you use defang on each secondary MX host.

Uses clamav as well - David likes it.  Go for the daemon version.

-- Main.MikePatterson - 26 Apr 2005

Topic revision: r2 - 2007-06-13 - LawrenceFolland

Information in this area is meant for use by CSCF staff and is not official documentation, but anybody who is interested is welcome to use it if they find it useful.

Other Webs

My links
- People
- CERAS
- WatForm
- Tetherless lab
- Ubuntu Main.HowTo
- eDocs
- RGG NE notes
- RGG
- CS infrastructure
- Grad images

Edit