This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.

--=__Part3F18C6B5.0__=
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

This bug exists on a qmail-1.03 install as well.
>>> On 8/2/2007 at 12:40 PM, in message <46B20919.3050902@ucsc.edu>, John =

Rudd wrote:


The following received header gets RDNS_NONE:

Received: from [69.12.154.165] (HELO mail.rudd.cc)
by some.internal.test.host (CommuniGate Pro SMTP 5.1.11)
with ESMTP id 60056 for jrudd@some.internal.test.domain; Tue, 31 Jul=20
2007 14:05:04 -0700



This is an error in the RDNS_NONE logic. The host in question DOES =
have=20
RDNS. The issue is that CommuniGate Pro doesn't put the RDNS=20
information into the Received header (and the place where it puts the=20
HELO information might instead have the authenticated user, if SMTP-AUTH=20=

was used).


My recommendation is that the logic for RDNS_NONE should be:


if (Received =3D~ /\(CommuniGate Pro SMTP /) {
if (DNS checks are enabled) {
do the DNS check on the IP address, and then decide if it has RDNS
}
else {
don't trigger RDNS_NONE (because you can't know without the DNS=20
check)
}
}
else { # not a CommuniGate Pro MTA
do existing RDNS_NONE logic
}





<=A4#/srv/gw/mvndom/wptemp/43ccc243.qm8

--=__Part3F18C6B5.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML


">


This bug exists on a qmail-1.03 install as well.

>>> On 8/2/2007 at 12:40 PM, in message <46B20919.3050902@=
ucsc.edu>, John Rudd <jrudd@ucsc.edu> wrote:

#050505 1px solid; BACKGROUND-COLOR: #f3f3f3">

The following =
received header gets RDNS_NONE:

Received: from [69.12.154.165] =
(HELO mail.rudd.cc)
   by some.internal.test.host (CommuniGate=
Pro SMTP 5.1.11)
   with ESMTP id 60056 for jrudd@some.intern=
al.test.domain; Tue, 31 Jul
2007 14:05:04 -0700



This is =
an error in the RDNS_NONE logic.  The host in question DOES have =

RDNS.  The issue is that CommuniGate Pro doesn't put the RDNS =

information into the Received header (and the place where it puts the =

HELO information might instead have the authenticated user, if =
SMTP-AUTH
was used).


My recommendation is that the logic =
for RDNS_NONE should be:


if (Received =3D~ /\(CommuniGate Pro =
SMTP /) {
    if (DNS checks are enabled) {
 &nbs=
p;     do the DNS check on the IP address, and then =
decide if it has RDNS
       }
 &n=
bsp;  else {
       don't trigger =
RDNS_NONE (because you can't know without the DNS
check)
 &nbsp=
;     }
    }
else { # not a =
CommuniGate Pro MTA
    do existing RDNS_NONE logic
&n=
bsp;   }









CONFIDENTIALITY NOTICE: This =
e-mail=20
message, including any attachments, is for the sole use of the =
intended=20
recipients(s) and may contain confidential and privileged information=
..=20
Any unauthorized review, use, disclosure, or distribution is =
prohibited.=20
If you are not the intended recipient(s), please contact the sender =
by=20
return e-mail and destroy all copies of the original message. Thank =
you.




--=__Part3F18C6B5.0__=--