[Mimedefang] Auto-whitelist for users [SPAM ASSASSIN]

[Albert E. Whale]

"David F. Skoll" wrote:

> On Mon, 6 Jan 2003, Albert E. Whale wrote:
>
> > I'm not trying to rain upon your business op, (this is Still America,
> > right?) but doesn't the To: field hold the ~?
>
> The "~" means "current user's home directory".
>

Agreed, especially if you are hosting multiple domains.  But that should be
easily solved.

>
> By the time procmail executes, we know the user is local, and we know
> the user identity.  In MIMEDefang, the address "foo at mydomain.net"
> might not even be local -- there's no (easy) way for MIMEDefang to
> tell.  And even it it is local, the "foo" part might be for a local
> user called "bar", because of aliasing.
>
> Per-user decisions are easiest left to procmail.  A good compromise is
> to have MIMEDefang add an X-Spam-Score header, and then leave it up
> to individual procmail scripts to dispose of the mail.  You can supply
> canned procmail scripts for a few pre-configured ways to handle the spam.
>

My intent is to combine the SPAM Assassin information along with the exist
Junkfilter configuration.  It may be easier to determine the 'Parent' Local
User (if it exists) and then post filter the result through the Whitelist.
The Alternative is to run BOTH Filters on the SPAM and determine if there is
a hit in the Junkfilter (Procmail based) based white list.

Comments?

BTW, Please do keep up the Great job! Where would MiLTER be today without
MIMEDefang?


--
Albert E. Whale - CISSP
http://www.abs-comptech.com
----------------------------------------------------------------------
ABS Computer Technology, Inc. - ESM, Computer & Networking Specialists
Sr. Security, Network, and Systems Consultant
Board of Directors - InfraGard - Pittsburgh, PA