At 09:19 PM 12/4/2005, Chad wrote:
Evenin!
I have been reading on relays, and such. I am in a situation where a
user on my system sends mail to AOL, but AOL blocks email from dynamic
IP's (at least all of them I've ever used). So in order to get the
mail to the AOL user, I have setup my MTA (postfix) to relay email
through my ISP's mail server.
So far so good, it seems anyway (it's not quite been a full day yet,
but things seem to be working fine). But, now in my email headers,
Spam Assassin is running the FORGED_RCVD_HELO against messages sent
from me. I'm AWL of course, but this is still confusing. I don't
understand what's happening I guess.
First I'd have to ask.. why do you even care? This rule scores less than
0.2 points in SA 3.1.0.
The rule is strictly informational, and all it means is that neither of the
following is true:
1) HELO string didn't match the hostname of the PTR record (aka
reverse DNS lookup) of the connecting IP.
-and-
2) the A record look up of the HELO string did not match the
connecting IP.
In the SA 3.1.0 mass-checks this rule matched more nonspam than it matched
spam. Nobody should take it as any serious indicator of spam.
