Different rules based on Queue?

[John Rudd]

Our mail servers do some routing and some local delivery, plus the usual
set up for Mailscanner has scanning being done before list expansion.
The result is that it's hard (perhaps impossible) to do per-user
preferences for spam assassin and per-user bayes databases, because at
the point where MailScanner gets the message there might be mulitple
recipients (so only one of them will determine the results for all of
them), or it might be to someone off campus (who wont have any prefs at
all), or it might be to a list (again, no per-user prefs at all, but
then the list might contain local users).


What I've thought about doing is having 2 mailscanner queues.  One for
pre-(list/multiple-recipient/routing) expansion that just does global
work (virus scanning, general spam assassin scan, etc.), and then one
for per-user spam scanning (with messages inserted into the queue only
after the message has been boiled down to exactly one recipient).  The
first queue would not have per-user spam assassin prefs files, per-user
spam thresholds, nor individual bayes databases.  The second queue
would.

I know there's a way to have mailscanner use multiple queues (but I
haven't played with it at all).  Can each queue have it's own sets of
rules/preferences?  Or can a "rules" file be based upon the queue and
not just the from/to/relay information?

Or would it be easier to just have 2 copies of mailscanner installed,
each with different queues and different configurations?

-------------------------- MailScanner list ----------------------
To leave, send    leave mailscanner    to jiscmail at jiscmail.ac.uk
Before posting, please see the Most Asked Questions at
http://www.mailscanner.biz/maq/     and the archives at
http://www.jiscmail.ac.uk/lists/mailscanner.html