On Wed, 3 May 2006, Brent Kennedy wrote:
> rules. The issue before here, is that spamassassin doesn't split emails up
> between recipients when a message is sent to multiple people. If one user
> is on the whitelist_to or all_spam_to or some_spam_to list, then everyone
> gets its.
[snip..]
This is TOTALLY dependent upon how you've integrated SA into your mail
system.
If you filter at delivery time (procmail, etc) then you're filtering on
a per-user basis (more CPU overhead, cannot do SMTP-reject, but can do
per-user customizations).
If you filter at the MTA level (sendmail milter, procmail pipe, etc)
then you're doing per-message filtering and cannot easily do per-user
customizations. It is possible to create a MTA system that splits up
messages so to enable per-user customizations but it is either fragile
or can get real complex/ugly.
Stupidly simple example, set your incoming MTA config so that it will
accept at most one recipient per message (EG for sendmail set
MaxRecipientsPerMessage=1). This will force the remote sending MTA to
split the message for you. Easy but fragile, not all MTAs will do
this successfully.
More complex, local layered MTAs, accept the message then split
internally (but if you want to be able to do SMTP-rejects based
upon spam score, it needs to get more complex/ugly ;(.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
