On 06/21/2013 03:21 PM, Fabio Sangiovanni wrote:
Il 21/06/13 14:19, Martin Gregorie ha scritto:
Assuming that the copy is sent to a maildir format mailbox you can
periodically run a shell script something this:
for m in maildir/*
do
spamc <$m | rescanned_results_filter
mv $m scanned_dir
done
This could be a second pass through your normal SA system or could
equally be using a differently configured copy of spamd. So, rescanning
the BCCed messages is rather easy. This is basically how I run new and
revised rules against my spam collection.
The more important questions concern what you want to do with the BCCed
mail after its second scan and what you'll do with the results scanning
it the second time.
Martin
I normally already scan the BCCed message *only*. The main submission
channel doesn't have an antispam system on its own; instead, an
out-of-band antispam stack (postfix + amavisd-new + spamassassin) is in
place; it receives BCCed messages and takes care of checks in an
unobtrusive way, just for screening purposes.
What I'm trying to do is to implement uribldns checks against one single
type of header, containing an email address.
Example:
[mail headers]
[...]
X-My-Own-Header: <localp...@domain.tld>
[...]
[mail body]
I need rules to have spamassassin check domain.tld against some URIBL
lists (eg. Spamhaus DBL). Is this even possible?
This is possible against standard headers.
you can see how it's done in 20_dnsbl_tests.cf DNS_FROM_AHBL_RHSBL
Why do you need it to check with your dedicated headers?
BCC shows the original env-sender (unless you're hacking it away)
Make sure you're not violating BL's TOS by hammering mirros with the
wrong type of query.
