Josh,
> I posted this one the sf.net bugtracker, but saw that
hasn't been used
> in a long time, so apologies for the potential
cross-post
>
> I have a setup with postfix 2.3.6, amavis 2.4.1, and
spamassassin 3.2.3.
> Mail is scanned by amavis normally, and the quarantine
method is bsmtp
> to local files (which are later processed into a
database using the
> amavisnewsql plugin for squirrelmail).
Btw, newer versions of amavisd-new can quarantine to SQL
directly.
> I am in the process of allowing users to either recieve
their
> quarantined email in the database, or to have it just
tagged and later
> filtered into a normal mailbox. I achieve this by
setting the spam kill
> level to 999 on mailbox users, thereby not quarantining
their mail via
> bsmtp.
>
> The problem is when an email is sent to multiple users,
one or more of
> which use the normal bsmtp quarantine. Amavis marks the
email as spam,
> then because at least one user has a kill level under
the level of the
> spam email, the email gets quarantined
Yes, the mail gets quarantined.
> and not forwarded on via smtp to the mailbox user.
No, quarantining a mail does not automatically disable
passing it on to
recipient. Recipients with kill level above the spam score
should still
be receiving it, only those recipients with a low kill level
will not
receive it. The mail does get quarantined, but that is
beside the point,
there is only one quarantining action per message, not one
per-recipient.
> The spam ends up showing up in their (still accessible)
database-based
> quarantine
Yes. But quarantine is not supposed to be directly
accessible to recipients,
because quarantine is per-message, not per-recipient.
> instead of their spam mailbox.
in addition to, not instead.
> Is it possible to split out email for multiple
recipients before
> quarantining?
Delivery (passing) is split as needed. Only the quarantining
isn't split.
You are misusing quarantining. What you want is to
_pass_all_ mail
($final_spam_destiny = D_PASS), but let mail for recipients
where
spam score exceeds kill level (or tag2 level) to be diverted
to a
dedicated mailbox (or wherever needed). On the amavisd side
you can
tag such spam mail either by adding address extensions or by
insering
a spam tag header field, then let MTA reroute such spam mail
(based on
address extension (best) or on header checks) to wherever
needed:
perhaps to a recipient's dedicated spam subfolder, or
through alias
and pipe to some program to store it somewhere, e.g. to
SQL.
This way a true per-recipient handling will be honoured.
Mark
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and
a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
AMaViS-user lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/
|
