Thanks. I did ask over there but got nothing. You are right it is not
clear yet if spf is doing the wrong thing but I will definitely follow
up here and in bugzilla if it is. Thanks for pointing me to trusted
networks setting though. I will look into that and see what I find. At
least now I have a direction because I have been scratching my head on
this one.
Tom
Sidney Markowitz wrote:
Thomas Bolioli wrote, On 7/12/06 6:21 AM:
My issue is why is SA looking at
the original sending host (the self reported IP to boot and not the
actual external IP).
I can't reproduce the problem using the current svn 3.1 branch with a
trusted_networks 192.147.12.5
to simulate what I guess to be your local environment.
This sounds like it might be a configuration problem related to the
trusted_networks configuration option. Please do the following:
Run spamassassin with the -D option to see debugging output, and look at
the lines that begin with "dbg: spf:" to see what is being used for spf
checking.
Ask for help on the sa-users mailing list, not here. The sa-dev mailoing
list is for discussions related to the development of SpamAssassin. Your
question would be appropriate here if SpamAssassin really was doing the
wrong thing when parsing the HELO but it is not clear yet if that is the
case. You should use the sa-users list to figure out if the problem is
on your end or in SpamAssassin, then bring it to us when you can show
that it is a SpamAssassin bug. But if you do that, still don't post it
to this mailing list, instead open up a bug report at
http:/bugzilla.spamassassin.org which will allow us to track the problem.
If you do open a bug report in Bugzilla, please use the "create an
attachment" link there to attach a copy of email that demonstrates the
problem, show us the trusted_networks and internal_networks settings you
are using, and attach the debug log output resulting from running
spamassassin with the -D option on that email.
-- Sidney Markowitz
http://www.sidney.com
