Re: [Asrg] seeking comments on new RMX article

Daniel Feenberg <feenberg@nber.org> Tue, 06 May 2003 11:52 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 HAA15843 for <asrg-archive@odin.ietf.org>; Tue, 6 May 2003 07:52:20 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46C0m715088 for asrg-archive@odin.ietf.org; Tue, 6 May 2003 08:00:48 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46C0m815085 for <asrg-web-archive@optimus.ietf.org>; Tue, 6 May 2003 08:00:48 -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 HAA15822; Tue, 6 May 2003 07:51:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D119-0005H3-00; Tue, 06 May 2003 07:53:55 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19D119-0005Gx-00; Tue, 06 May 2003 07:53:55 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46BwO814890; Tue, 6 May 2003 07:58:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46BuG814786 for <asrg@optimus.ietf.org>; Tue, 6 May 2003 07:56:16 -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 HAA15534 for <asrg@ietf.org>; Tue, 6 May 2003 07:47:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D0wW-0005DQ-00 for asrg@ietf.org; Tue, 06 May 2003 07:49:08 -0400
Received: from nber13.nber.org ([207.113.108.238]) by ietf-mx with esmtp (Exim 4.12) id 19D0wQ-0005Bf-00 for asrg@ietf.org; Tue, 06 May 2003 07:49:03 -0400
Received: from nber13.nber.org (localhost.nber.org [127.0.0.1]) by nber13.nber.org (8.12.3/8.12.3) with ESMTP id h46BjWf4079702 for <asrg@ietf.org.KAV>; Tue, 6 May 2003 07:45:32 -0400 (EDT)
Received: (from root@localhost) by nber13.nber.org (8.12.3/8.12.3/Submit) id h46BjWNf079701 for asrg@ietf.org.KAV; Tue, 6 May 2003 07:45:32 -0400 (EDT)
Received: from nber5.nber.org (nber5.nber.org [207.113.108.99]) by nber13.nber.org (8.12.3/8.12.3) with ESMTP id h46BjVf5079693; Tue, 6 May 2003 07:45:32 -0400 (EDT)
From: Daniel Feenberg <feenberg@nber.org>
To: Scott Nelson <scott@spamwolf.com>
cc: asrg@ietf.org
Subject: Re: [Asrg] seeking comments on new RMX article
In-Reply-To: <aT5vaIe86J8qbrFBE02@x>
Message-ID: <Pine.GSO.4.10.10305060734430.13081-100000@nber5.nber.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
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: Tue, 06 May 2003 07:44:52 -0400


On Tue, 6 May 2003, Scott Nelson wrote:

> 
> rDNS does not support multiple domains.
> with rDNS, if you have two vanity domains you need two IP addresses.
> if you run an email service you might host hundreds of domains
> per IP.  So, yes, if you're one of those people it's a lot simpler,
> because you couldn't support rDNS at all.
> 

Is this right? Is there some reason many different MAIL FROM: host
names couldn't point to a single SMTP host? 

I think the receiving host looks up the domain name of the FROM address to
check that the connecting host is among the RMX records returned. It
doesn't look up the connecting host to see if the FROM address is listed.

Why has Vixie's similar proposal gotten no discussion here? He wanted to
overload existing MX records with the same information. In effect, 
receivers would accept mail only from hosts with MX records matching the
MAIL FROM address. If a sending domain wished to send from a host but
not receive mail to it, the MX record could be given a very low priority.
A minor advantage here is that BIND doesn't need to be changed. A larger
advantage is that many sites already send and receive from the same host,
so there is a "start up capital" of many millions of pre-configured
sites.

If the "very low priority" is specified in the standard, then there isn't
even any difficulty telling if an MX record is specifically for
verification purposes or not.



_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg