Olivier,
> > If you are referring to SpamAssassin per-recipient options,
> > that is not possible with the current paradigm of amavisd
> > (and current versions of SpamAssassin), as amavisd calls
> > SpamAssassin once per message (not once per recipient),
> > so in multi-recipient messages there would be no way
> > to tell which options to load.
>
> But something like whitelist_from is a per recipient data that applies
> differently for each recipient of a multi-recipients message.
Well, yes, which is why you can't currently use user-specific
rules and settings for SpamAssassin.
> So in the same way, I assume that the ok_languages could apply per
> recipient: let the SA plugin determine the list of languages used in a
> multi-recipients message and apply the list of valid language per
> recipient when computing the score.
Right, same thing here.
Here is my request-for-enhancement:
Bug 5357
RFE: split scan process into two parts for efficient
multi-recipient handling
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5357
Mark
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
