At 01:09 PM 1/2/02, Gregory Hicks wrote:

> > Date: Wed, 02 Jan 2002 12:51:42 -0500
> > From: Daniel Senie <[EMAIL PROTECTED]>
> >
> > At 12:33 PM 1/2/02, Gregory Hicks wrote:
> > > > From: "Fred G Guiliano" <[EMAIL PROTECTED]>
> > > > Date: Wed, 2 Jan 2002 11:03:03 -0500
> > > >
> > > > Hi All,
> > > >
> > > > I see at the the qualcomm site this particular explanation of the
> > > > following error:
>[...snip...]
>
> > >Although qpopper may allow you to turn the check off (and no, I don't
> > >know the option, but it is in the docs or the config options), it
> > >seems to me - and this is a 'hostmaster' and 'postmaster' speaking -
> > >that if you cannot reverse look up one of your own hosts, you *might*
> > >have a DNS config issue...  That should be solved...
> >
> > Think "travelling user." You'll never have control over everything.
>
>Daniel:
>
>Even a traveling user *should* reverse lookup - even if they come from
>some unrelated ISP.  Or am I not understanding the"Travelling user"
>issue?

Yes, everyone SHOULD have INADDR. However, not everyone does.


>If some hotel room doesn't reverse lookup then THEY have a DNS issue
>that should be corrected.  I've made it a practice to tell these people
>what problems I, and my users, are experiencing.  Sometimes, they fix
>the issue, sometimes not.  Major chains seem to react well though.

While that's all fine, the question is whether there's any merit in filling 
logs on the mail server with information about 3rd parties who lack INADDR. 
My argument is that it's not worthwhile.

What's worse, is that many people run qpopper from inetd or xinetd, often 
with TCP Wrappers. Wrappers does a DNS lookup for its checks (or at least 
can be set up that way).

I have an Internet Draft which I've been working on, intended to be a BCP, 
that says everyone SHOULD implement INADDR, but at the same time it says 
use of INADDR as a part of any "security" check should be strongly discouraged.
-----------------------------------------------------------------
Daniel Senie                                        [EMAIL PROTECTED]
Amaranth Networks Inc.                    http://www.amaranth.com

Reply via email to