<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<p>Hi,</p>
<p>First of all - thanks so much for the help! Much appreciated. Some thoughts, below.</p>
<p>1) I can ask at spamassassin, but it seems like my spamassassin settings aren't being used. Does amavis somehow take this over, or should the spamassassin settings really work? Sounds like a dumb question I know, but I have tried changing the settings and they don't seem to be used (and I'm restarting spamassassin and amavis both ... :-().</p>
<p>2) You are correct - it's because my IP is a dynamic IP, provided by Verizion FIOS. They have added all their IP's to the blacklist. I just have a backup mail server (at my brother's house), that forwards email to me when my main server goes down. But I don't want the email blocked just because it came from FIOS (in fact, one of the failing RBL checks just says it's a Verizon IP, which I already know ... :-)).</p>
<p>3) Sorry, just trying to understand your last comment (about internal and trusted networks). Will the previous relays be checked, just the last one is skipped? And can I use a machine name (FQDN), or do I have to enter the IP address (it's dynamic, so name would be nice). I will check the reference you mention, just not sure my spamassassin settings are being used ... :-(</p>
<p>Thanks again!</p>
<p>... Russell</p>
<p> </p>
<p>On 2012-12-30 02:42, Cedric Knight wrote:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<pre>Hi Russell
On 30/12/12 05:21, R. Morris wrote:</pre>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">Hi, This may be a dumb question (and likely is, sorry!), but I haven't been able to figure out how to get it working, so ...</blockquote>
<pre>Well, I hope this isn't a dumb answer. It does sound like a
SpamAssassin issue maybe best dealt with at <a href="mailto:users@spamassassin.apache.org">users@spamassassin.apache.org</a>.</pre>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">I have a working setup with Postfix + Amavis-new. Works quite well, except for one thing - if email goes through my backup MX (mail server), then it is flagged as spam (due to RBL checks). I can disable all checking based on this IP, but I really only want to disable RBL / DNSBL checks for this IP, and let the other checks proceed as usual.</blockquote>
<pre>Which RBL checks, and why is your backup MX on an RBL? Maybe it's just
a list of dynamic or consumer IPs, but maybe it's associated with a
previous exploit.</pre>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">Is there an easy way to do this? I have tried changing the Spamassassin setting itself (both trusted networks and skip_rbl_checks), but neither one seems to work.</blockquote>
<pre>trusted_networks should work if you use it correctly. If you really
want to disable RBL checks altogether, put the following line in your
amavis configuration (it has the same effect as skip_rbl_checks would if
you weren't using amavis):
$sa_local_tests_only = 1;
But for the behaviour you want, in your SpamAssassin local.cf add two lines
internal_networks 10.0.0.1
trusted_networks 10.0.0.1
replacing 10.0.0.1 with the IPv4 address of the machine you don't want
checked for RBLs. Then reload amavis. This should mean the "last
external" RBL checks will be carried out for the address that connects
to your backup, and SA still scores on content and headers.
See "man Mail::SpamAssassin::Conf" for more.
HTH
C
</pre>
</blockquote>
<p> </p>
<p> </p>
<div> </div>
</body></html>