A great document on helping with this problem is:
http://www.postfix.org/BACKSCATTER_README.html
This certainly can help, but my tests have shown that SA catches pretty
much all of this type of backscatter, anyway. In fact, most of the
messages caught by this method would end up with an SA
[...] I should be able to get around that by
setting @lookup_sql_dsn to undef and leaving @storage_sql_dsn set.
This also didn't work, but I found a way around it. It appears that
with @storage_sql_dsn set, an undef value for @lookup_sql_dsn will cause
amavisd to abort when attempting to look
Hmm, this says the score is zero, which indicates to me that that
message was scanned (by what? - nothing? I dunno). How did you
disable spam scanning? To disable spam scanning try:
@bypass_spam_checks_maps = (1);
You may also desire:
@bypass_virus_checks_maps = (1);
I had tried @local_domains_maps = (); without luck. Alas, your
suggestion also does not appear to have worked.
By the way, I'm running 2.6.0-rc1, not -pre1 as stated earlier.
Ah, found it. The policy defined in the sql policy table for the
servers in the DMZ was overriding the settings in
Is there a way to configure amavisd to completely ignore X-Spam-*
headers that may have previously been applied by an earlier pass through
amavisd on a different host? I realize that this could be a Very Bad
Thing, but here's my problem:
We send mail to several customer domains across private
