individual User spamassassin settings during lmtp delivery

Romeo Benzoni romeo at benzoni.org
Mon Jan 19 10:46:11 EST 2004


Start Header!
On Mon, 2004-01-19 at 16:24, James A. Pattie wrote:
> Start Header!
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Rob Siemborski wrote:
> | On Mon, 19 Jan 2004, Romeo Benzoni wrote:
> |
> |
> |>So my specific questions are:
> |>
> |>1. is my approach wide of the mark or are there better, smarter
> |>solutions to achieve this?  (I've read about people doing this using a
> |>deliver wrapper which calls spamassassin and then deliver. but I don't
> |>like this kind of "fork and exec orgies")
> |
> |
> | Implementing the spam sieve extension is probably a better way of doing
> | this (rather than wedging it into deliver() directly).
> 
> Or you could use MailScanner to scan the e-mails as they come into the box and
> then the delivering instance of your mta (sendmail, exim, etc.) just does normal
> ltmp.  MailScanner attempts to be pretty resource friendly as it scans bunches
> of e-mails at a time (if they are available) rather than forking off multiple
> spamassassin instances, etc.

for now I'll do virus and spamassassin processing during smtp stage, but
at the smtp stage I'll have no clue what local users this message gets
to. so I can't load individual spam rules on a per user basis. I'll have
a preforked spamassassassin process which does not need forking on every
message. so me intention was to move the spamassassin stuff from the
smtp stage to the lmtp stage. Implementing this stuff on [S|L]MTP proxy
is another solution. there is one provided with spamassassin but I don't
know how well tested and stable it is. third possible implementation was
the sieve spam draft mentioned by rob.

> 
> If you are wanting individual spamassassin rules, then going the MailScanner way
> will have more setup, but it also provides virus scanning to boot. :)
> 
> www.mailscanner.info
> 
> - --
> James A. Pattie
> james at pcxperience.com
> 
> Linux   SysAdmin / Systems Programmer
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFAC/aztUXjwPIRLVERAsqEAKDmQJcnqgjjSydKZ6hJ2NrNT6l1SgCfacsi
> dMUD5Ftbvx2Tau1rFQKGGD0=
> =xL98
> -----END PGP SIGNATURE-----

It got by with 0 of 285 points.




More information about the Info-cyrus mailing list