Comcast and mail header errors?

[Dan Jenkins]

Ben Scott wrote:

>On 3/20/06, Paul Lussier <p.lussier at comcast.net> wrote:
>  
>
>>Anyone seen the following type of header coming though Comcast's servers?
>>    
>>
>  Hmmm.  Well, yes, grep tells me that I am.  Quite a bit, apparently.
> Never noticed.  Never looked, either.  :)
>  
>
I grepped through my umpteen stored emails and found a number of 
instances. All involving Comcast. Some of the "misconfigured servers" 
included ATT.NET and COMCAST. So, their own servers are sometimes 
"misconfigured" too.

>  As a wild guess, I'd say Comcast is throwing that in when the name
>given in the HELO does not resolve to the IP address of the
>sender-SMTP.
>  
>
That's what I've believed, though I have no apparent reason, now that I 
think about it. ;-)

>>I'd love an explanation as to why Comcast thinks the senders are
>>misconfigured...
>>    
>>
>  Comcast su... err, nevermind.
>
>  Seriously, is there a reason you care, beyond "if something's broken
>it should be fixed"?
>  
>
If someone just SAYS something is broken is not a reason to fix it; it 
has got to really be broken.
Comcast is not near the top of my list of authoritative sources. :-D

-- 
Dan Jenkins (dan at rastech.com)
Rastech Inc., Bedford, NH, USA --- 1-603-206-9951
*** Technical Support for over a Quarter Century