Benny Pedersen wrote:
On Thu, June 26, 2008 04:40, Matt Kettler wrote:
I'll attempt to do so. Didn't realize you disliked it.
its like asking 2 times for the same answer and wonder why no answer
Well then set a Reply-to header to point to the list when you post
here... That's what the header's for, and your MUA is the only RFC
compliant spot that header should be generated.
I'm SA interpreted the Received header as meaning that athena.apache.org
found no reverse-lookup the host, and that 206.46.173.3 is a host with
no reverse DNS claiming to be vms173003pub.verizon.net. At least, that's
how I'd read that header.. the FM_FAKE_HELO_VERIZON is likely an early
rule trying to detect hosts using verizon helo's that aren't really
verizon hosts.
well i asked if you know reverse dns patterns olso for verizon net or if
verizon olso know there trouble ?, few years i have seen spam from verizon
but not more then from others, it could nice to know atleast for me if
thay use smtp auth and or what there outgoing host is for this if any,
maybe you use smtp auth now on this msg here ?
if so that fake helo should not be fake :=)
Well, it shouldn't be fake, because 206.46.173.3 really is
vms173003pub.verizon.net.
However, it would appear that athena.apache.orgdidn't get an answer to
its PTR querry.. either that or the headers generated by
athena.apache.org are just broken.
