Bowie Bailey wrote:
> Good catch Alan, I hadn't noticed that. I think you're right about
the ALL_TRUSTED rule -- and, based on the debug output, right about
the internal_networks rule as well.
My comments have been based on settings for 3.04. I'm not sure if
your version wasn't mentioned before or if I just didn't catch it. I
would suggest that you upgrade at least to 3.04 in order to get the
benefit of all the new changes. You would probably want to upgrade
all the way to 3.1 since it has been out for a week or so now without
any major issues being reported.
That would definitely be an issue.
From the beginning of the thread, I noted that I was running 2.6x, but
that may have gotten missed.
I have one production server that's running 3.0.3, and I ran a couple of
quick tests there, and things are behaving as I would expect in this area.
Thus, I upgraded the test server to 3.0.3 (yes, I know that 3.0.4 and
3.1 are out, but I stuck with 3.0.3 for consistency).
It did take one more tweak to add trust to the originating IP address,
in local.cf, but from there, an identical message is coming out being
not tagged as spam, and ALL_TRUSTED is definitely showing up.
Thus, the real "one small thing" I was missing was in running a version
that's consistent with supporting what I want to do.
At this point, I think I pretty much have the mechanics down. From
here, what's necessary is getting all my production servers updated to
3.0x, then getting the various combinations of acceptable return
addresses matched with server names.
Many thanks to all, especially Bowie, who patiently walked me through
this one. I really appreciate it.
Smith
