[milters] Archive

Lists Index Date Thread Search

Article: 1732
From: Derek J. Balling
Date: 2007-09-23 09:50:07 -0400
Subject: Re: milter-link problems

Removal...........: milters-request@milter.info?subject=remove
More information..: http://www.milter.info/#Support
--------------------------------------------------------

On Sep 23, 2007, at 9:21 AM, Jim Hermann - UUN Hostmaster wrote:
> Sep 23 08:02:49 host sm-acceptingconnections[16916]: l8ND2OZu016916:
> from=<dwscubaservicem@scubaservice.com>, size=0, class=0, nrcpts=0,
> proto=ESMTP, daemon=MTA, relay=localhost [222.253.62.134] (may be  
> forged)
>
> Sendmail appears to accept the invalid PTR record.  Another example of
> invalid PTR record:
>
> Sep 23 07:51:09 host sm-acceptingconnections[12739]: l8NCp22N012739:
> from=<Amos@rogers.blackberry.net>, size=0, class=0, nrcpts=0,  
> proto=SMTP,
> daemon=MTA, relay=domain.not.configured [69.113.40.86] (may be forged)
>
> In both cases, Sendmail bounced the message for other reasons, not  
> the lack
> of a valid domain name in the PTR.

Sendmail won't bounce a message for lack of a valid domain name in the  
PTR, it's not configured to do that.

Like I said, there's two macro values available, one which is just  
"what's the untrusted PTR" (used in the messages above), and one which  
has the double-resolution turned on.

What happens, essentially, is that if they don't equal each other, it  
adds the "may be forged" qualifier in the received headers.

D



-- Binary/unsupported file stripped by Ecartis --
-- Type: application/pkcs7-signature
-- File: smime.p7s



Lists Index Date Thread Search