[Asrg] Reverse DNS
gep2@terabites.com Wed, 18 June 2003 18:46 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20733 for <asrg-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:46:37 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5IIkAo30880 for asrg-archive@odin.ietf.org; Wed, 18 Jun 2003 14:46:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ShXB-0006pv-VU for asrg-web-archive@optimus.ietf.org; Wed, 18 Jun 2003 14:19:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19737; Wed, 18 Jun 2003 14:19:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ShUu-0007fr-00; Wed, 18 Jun 2003 14:17:28 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ShUt-0007fo-00; Wed, 18 Jun 2003 14:17:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Sh8E-0005Ym-3P; Wed, 18 Jun 2003 13:54:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Sgkf-0004AJ-Id for asrg@optimus.ietf.org; Wed, 18 Jun 2003 13:29:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17406 for <asrg@ietf.org>; Wed, 18 Jun 2003 13:29:37 -0400 (EDT)
From: gep2@terabites.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SgiO-00071p-00 for asrg@ietf.org; Wed, 18 Jun 2003 13:27:20 -0400
Received: from h007.c000.snv.cp.net ([209.228.32.71] helo=c000.snv.cp.net) by ietf-mx with smtp (Exim 4.12) id 19SgiN-00071k-00 for asrg@ietf.org; Wed, 18 Jun 2003 13:27:19 -0400
Received: (cpmta 10149 invoked from network); 18 Jun 2003 10:29:36 -0700
Received: from 12.239.18.238 (HELO WinProxy.anywhere) by smtp.terabites.com (209.228.32.71) with SMTP; 18 Jun 2003 10:29:36 -0700
X-Sent: 18 Jun 2003 17:29:36 GMT
Received: from 192.168.0.30 by 192.168.0.1 (WinProxy); Wed, 18 Jun 2003 12:29:05 -0600
Received: from 192.168.0.240 (unverified [192.168.0.240]) by nts1.terabites.com (EMWAC SMTPRS 0.83) with SMTP id <B0000024073@nts1.terabites.com>; Wed, 18 Jun 2003 12:56:04 -0500
Message-ID: <B0000024073@nts1.terabites.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
To: asrg@ietf.org
X-Mailer: SPRY Mail Version: 04.00.06.17
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Reverse DNS
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Wed, 18 Jun 2003 12:56:04 -0500
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
> We are presently requiring reverse DNS for IP addresses of MTA's which connect to our MX (with exceptions, which are dwindling). This has nothing to do with the MAIL FROM domain, it simply means that if you connect to us, your IP address must have a name, and that name must map back to your IP address. What you suggest above is exactly the sort of next step we're looking for; namely, a DNS RR which tells the world that a particular host name has been designated as an MTA (outgoing at least). There are a number of us advanced/small users with home offices who presently run our own outgoing SMTP mail server, behind a router using NAT. Not all (valid, legitimate!) outgoing SMTP servers have fixed/permanent IP addresses. Likewise, since I have a "residential" type high speed connection, I have *very* limited abilities (and that only because of my own domain names, but I don't have my own Net-accessible DNS server in any case) to manipulate the DNS records associated with those domains. I suspect that a fair number of other consultant-type users are in a similar boat to myself on points like this. It's the needs of some of us 'advanced/small' users which the spf folks seem willing to totally ignore. Gordon Peterson http://personal.terabites.com/ 1977-2002 Twenty-fifth anniversary year of Local Area Networking! Support the Anti-SPAM Amendment! Join at http://www.cauce.org/ 12/19/98: Partisan Republicans scornfully ignore the voters they "represent". 12/09/00: the date the Republican Party took down democracy in America. _______________________________________________ Asrg mailing list Asrg@ietf.org https://www1.ietf.org/mailman/listinfo/asrg
- [Asrg] Reverse DNS gep2
- Re: [Asrg] Reverse DNS Steven F Siirila
- RE: [Asrg] Reverse DNS Jason Steiner
- Re: [Asrg] Reverse DNS Benjamin Geer
- [Asrg] Re: Reverse DNS gep2
- [Asrg] Re: Reverse DNS Selby Hatch
- Re: [Asrg] Reverse DNS Yakov Shafranovich
- Re: [Asrg] Re: Reverse DNS Yakov Shafranovich
- Re: [Asrg] Re: Reverse DNS Selby Hatch
- Re: [Asrg] Reverse DNS gep2
- Re: [Asrg] Reverse DNS Jim Bauer
- Re: [Asrg] Re: Reverse DNS Yakov Shafranovich