One option for you would be to run spamassassin in the global procmailrc
rather than as a milter.  I vaguely remember it will be skipped for users
with a .forward file.  Users who want spam-scanning before the forward can
forward via their own .procmailrc.  (I think /etc/aliases will bypass the
spam scanning also.)

That said, I advise against making spam-scanning optional.  What I've found
is that a user will forward all their mail off somewhere else, the
destination site will run some commercial system (like Barracuda), and that
commercial system will tag my server as being an "open" relay, getting it
blacklisted everywhere else.  After the second time this happened to me, I
stopped giving my users the choice.  If they don't want their spam to be
blocked, they should tell get a new email address and get off my system.
 It may sound harsh, but remember your job is to protect your current
users, not former users.

To make this more palatable to users, I set up spamass-milter with
rejection only at high spam scores (like >10).  Users could optionally
filter at lower scores (eg, >5) via their .procmailrc.  Blocking only
obvious spam makes false positives unlikely (so users don't need to worry),
and not forwarding the worst of the worst was sufficient to stay off spam
lists.

Damian
Author of
http://itg.beckman.illinois.edu/technology_development/software_development/milter_watch/


On Wed, Aug 22, 2012 at 7:54 AM, Dan Schwartz <[email protected]>wrote:

> Hi -
>
> I'm looking for a way to have the milter or spamassassin skip the check if
> end user has a forward file that is directing to a commercial domain that
> does it's own spam filtering.  Has anyone done an expansion of
> the recipient .forward address in a milter and modified the flow if it
> matches?  Is that information even exposed at the milter level?
>
> Thanks - Dan
>
> --
> Dan Schwartz | LTS - Systems and Networking  | Lehigh University |
> [email protected] | (610) 758-5061
>
>
>
> _______________________________________________
> Spamass-milt-list mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/spamass-milt-list
>
>
_______________________________________________
Spamass-milt-list mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/spamass-milt-list

Reply via email to