Re: [Asrg] Re: RMX Records

Troy Rollo <asrg@troy.rollo.name> Wed, 05 March 2003 04:35 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 XAA22010 for <asrg-archive@odin.ietf.org>; Tue, 4 Mar 2003 23:35:09 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h254jvc11324 for asrg-archive@odin.ietf.org; Tue, 4 Mar 2003 23:45:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h254jv511320 for <asrg-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 23:45:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21997; Tue, 4 Mar 2003 23:34:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h254j1511291; Tue, 4 Mar 2003 23:45:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h254i3511255 for <asrg@optimus.ietf.org>; Tue, 4 Mar 2003 23:44:03 -0500
Received: from corvu.com.au (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21976 for <Asrg@ietf.org>; Tue, 4 Mar 2003 23:32:43 -0500 (EST)
Received: from milat.troy.rollo.name (milat.corvu.com.au [203.33.110.33]) by corvu.com.au (8.8.5/8.8.5) with ESMTP id OAA08215; Wed, 5 Mar 2003 14:34:39 +1000 (EST)
Message-Id: <5.1.0.14.2.20030305152123.03289950@pop3.corvu.com.au>
X-Mailer: QUALCOMM Windows Eudora Version 5.1
To: "Derek J. Balling" <dredd@megacity.org>
From: Troy Rollo <asrg@troy.rollo.name>
Subject: Re: [Asrg] Re: RMX Records
Cc: Asrg <Asrg@ietf.org>
In-Reply-To: <1577B1AF-4EC1-11D7-9842-000A27AF5202@megacity.org>
References: <5.1.0.14.2.20030305150933.01de28c0@pop3.corvu.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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, 05 Mar 2003 15:34:37 +1100

At 11:15 PM 03/04/2003 -0500, Derek J. Balling wrote:

>On Tuesday, March 4, 2003, at 11:10 PM, Troy Rollo wrote:
>>This breaks automated forwarding.
>
>Couple solutions to that, most of which are documented pretty well in 
>Gordon's proposal ( http://www.pan-am.ca/draft-ietf-asrg-dsprotocol-00.txt ).

Actually it says "Another document will identify similar problems and 
solutions, including mail forwarding services and the Null Sender envelope 
(MAIL FROM:<>)."

The problem is that this approach assumes that the only significant reason 
mail with a given domain can come from a location not in a pre-authorised 
set is that it's spam. I would submit that there are many more common 
reasons for mail coming from an unexpected source - forwarding just being 
an immediately obvious one.

Even for forwarding, authorising the re-sending host at the receiving end 
requires at its best that the user provide this information (perhaps by 
means of some web based form) to the receiving ISP, and assumes that:

         (1) The user can get it right.
         (2) The user has access to all of the relevant information.
         (3) That the user knows within a reasonably short period (
             or preferably in advance) when the information changes.

None of these is a particularly good assumption.
--
Troy Rollo			Chairmain, CAUBE.AU
asrg@troy.rollo.name		Executive Director, iCAUCE

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