CBFalconer wrote:
Frank Heckenbach wrote:
CBFalconer wrote:
Frank Heckenbach wrote:
Emil Jerabek wrote:
This is quite possible, I get all Chuck's posts flagged as spam by SpamAssassin. I don't quite understand the logic involved, but something is apparently broken on either yahoo.com or *.dial-access.att.net, the header is included below for completeness.
Received: from yahoo.com +(25.hartford-02rh16rt-03rh15rt.ct.dial-access.att.net[12.76.130.25]) by worldnet.att.net (mtiwmhc11) with SMTP id <200402240558151110000st6e>; Tue, 24 Feb 2004 05:58:15 +0000 From: CBFalconer cbfalconer@yahoo.com Reply-To: cbfalconer@worldnet.att.net
* 2.6 FAKE_HELO_YAHOO Host HELO did not match rDNS: yahoo.comThis one is the biggest score item, and it seems to refer to the received header quoted (and some others might be as well).
... snip ...
My outgoing mail always has the (legitimate) from address of yahoo.com, with a reply-to: address of worldnet.att.net. It is (usually) physically delivered to att.net.
AFAICS, it's not about the from address, but a strange received header (see above). If you deliver your mail to att.net, there's no yahoo.com host involved during sending, right? So the machine sending the mail to att.net (apparently 25.hartford-02rh16rt-03rh15rt.ct.dial-access.att.net, perhaps your own dialup account) is pretending to be yahoo.com, it seems. But the IP lookup proves this wrong and some spam filters take notice of this (because many spammers use faked hostnames).
I see what you mean, and equally it appears to be out of my control. It smells to me as if the software handling the local mail dial-up creates that line out of my from: address and its own knowledge of the port involved. I don't expect to get anywhere complaining as a customer.
Perhaps if you explain to them the problems with spam filters ... Or else, why don't you use the att.net address as the sender?
Frank