IETF Logo Mail Archive

Re: [Asrg] seeking comments on new RMX article

Dave Crocker <dhc@dcrocker.net> Sun, 04 May 2003 21:56 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 RAA07248 for <asrg-archive@odin.ietf.org>; Sun, 4 May 2003 17:56:41 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h44M4N702465 for asrg-archive@odin.ietf.org; Sun, 4 May 2003 18:04:23 -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 h44M4N802462 for <asrg-web-archive@optimus.ietf.org>; Sun, 4 May 2003 18:04:23 -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 RAA07244; Sun, 4 May 2003 17:56:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CRUn-0002WA-00; Sun, 04 May 2003 17:58:09 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CRUI-0002W5-00; Sun, 04 May 2003 17:57:38 -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 h44M1I802392; Sun, 4 May 2003 18:01:18 -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 h44M0O802338 for <asrg@optimus.ietf.org>; Sun, 4 May 2003 18:00:24 -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 RAA07162 for <asrg@ietf.org>; Sun, 4 May 2003 17:52:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CRR1-0002VG-00 for asrg@ietf.org; Sun, 04 May 2003 17:54:15 -0400
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com ident=root) by ietf-mx with esmtp (Exim 4.12) id 19CRQg-0002Un-00 for asrg@ietf.org; Sun, 04 May 2003 17:53:54 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged)) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h44LrcN27133; Sun, 4 May 2003 14:53:38 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <136840390347.20030504144407@brandenburg.com>
To: Alan DeKok <aland@freeradius.org>
CC: asrg@ietf.org
Subject: Re: [Asrg] seeking comments on new RMX article
In-Reply-To: <E19CKoL-0006M3-00@mail.nitros9.org>
References: <E19CKoL-0006M3-00@mail.nitros9.org>
MIME-Version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
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: Sun, 04 May 2003 14:44:07 -0700
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Alan,

AD>   What's important for me is that RMX allows the receiving MTA to
AD> trivially discover that the originating domain has consented to send
AD> mail from that MTA.  Right now, we have *no* way of verifying the
AD> originators consent.

if you find the rmx record, and then you know the posting is through an
authorized MTA.

if you do NOT find the rmx record, you do not know anything.

so, what is the real utility of the rmx record?

that is, what can you safely do, versus not do?



>> For a variety of reasons -- notably for some mobile users -- the
>> originating MTA may well be unable to know the set of valid domains
>> sending from it.  That is, some mobile users must be able to
>> spontaneously post through different MTAs.

AD>   I've heard this before, and I have no idea why it's true.

firewall blockage of outbound port 25.  relatively common.

it means that mobile users often must re-configure their outbound MTA to
be something new and transient.


AD>   Are there NO other methods which a mobile user may use to send mail?

no.


AD> SMTP is only one of many protocols used to send/receive email.

interesting.  i believe there are no others.  ("submit" is simply smtp on
another port.)  which ones are you referring to?

I also believe that if there were others, it would not solve this
problem.



d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>

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

v2.23.0 | Report a Bug | By Email