Couldn't you do this in your .forward?
Over-rides the global .procmailrc file and looks for a local one in
the users home directory.
On Fri, 4 Oct 2002 listuser(_at_)neo(_dot_)pittstate(_dot_)edu wrote:
At 14:46 2002-10-03 -0600, LuKreme did say:
I have a /etc/procmailrc that runs al incoming mail through some virus
filters and spamassassin. I have a user account that does not want the
mail run through the spamassassin script (don't ask me).
Don't blame someone for wanting more control over their OWN email.
Is there a way to exclude that account from /etc/procmailrc?
I use /etc/procmailrc to INCLUDERC other specific filters. This isn't
critical, but it certainly keeps it tidy.
You could maintain a config file with lines starting with usernames and
username option option option
Or, you could make use of unix groups.
# obtain list of groups
#or, via a standalone file
#GROUPS=`grep ^"$LOGNAME " /etc/procmailrc/user_options.dat
# if user is a member of the MAIL_NOSPAM group, subject them to filtering
* GROUPS ?? [ ]MAIL_NOSPAM\>
# or, you could roll out your filter here.
# (repeat as necessary for other types of filters)
I actually want to do a similar thing. I just haven't gotten to the point
of implementation so I haven't yet asked for help. Since we're on the
topic already though.... :) I'm planning on breaking down my Sendmail
access list into separate parts. I've already written a script to rebuild
it with the aide of cidrexpand and some other nifty options. I'm planning
on using an assortment of organzied text files to house domains/netblocks
I'm planning on having an entry for. One of the big uses of this is for
SPAMFRIEND users (or the 8.12.6 syntax). I'm planning on having a simple
text file of userids that are SPAMFRIEND's. This way they can be used
from multiple daemons. My script will provide all the neccessary syntax
for the access list when it gets built. The text file can now also be
used as a local whitelist from Spamassassin and from within Procmail for
some other filtering I'm doing there (SA is tied to MIMEDefang at
present). My question is, what's the easiest way to use that whitelist
from within procmail? Would that be your example above? The list will be
short. We don't many users that don't want filtered mail, especially
after we tell them exactly how much spam in the previous week they had
filtered. That usually makes a good impression. :)
Any tips would be gladly accepted. I haven't yet implemented this. I'm
testing SA but getting ready to roll out email anti-virus first.
procmail mailing list
Jamie Ostrowski -- Skypoint Communications
Unix System Administrator
procmail mailing list