RE: [Asrg] C/R Interworking Framework

Yakov Shafranovich <research@solidmatrix.com> Mon, 09 June 2003 19:25 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 PAA18494 for <asrg-archive@odin.ietf.org>; Mon, 9 Jun 2003 15:25:21 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h59JOr229591 for asrg-archive@odin.ietf.org; Mon, 9 Jun 2003 15:24:53 -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 h59JOrB29588 for <asrg-web-archive@optimus.ietf.org>; Mon, 9 Jun 2003 15:24:53 -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 PAA18484; Mon, 9 Jun 2003 15:24:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PSEF-0006RR-00; Mon, 09 Jun 2003 15:22:51 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PSEE-0006RN-00; Mon, 09 Jun 2003 15:22:50 -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 h59JNGB29506; Mon, 9 Jun 2003 15:23:16 -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 h59JMuB29470 for <asrg@optimus.ietf.org>; Mon, 9 Jun 2003 15:22:56 -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 PAA18435 for <asrg@ietf.org>; Mon, 9 Jun 2003 15:22:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PSCM-0006RD-00 for asrg@ietf.org; Mon, 09 Jun 2003 15:20:54 -0400
Received: from 000-236-597.area5.spcsdns.net ([68.27.163.124] helo=68.27.163.124 ident=trilluser) by ietf-mx with smtp (Exim 4.12) id 19PSCK-0006R4-00 for asrg@ietf.org; Mon, 09 Jun 2003 15:20:53 -0400
Message-Id: <5.2.0.9.2.20030609151453.00bafef8@std5.imagineis.com>
X-Sender: research@solidmatrix.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
To: Peter Kay <peter@titankey.com>, Scott Nelson <scott@spamwolf.com>, asrg@ietf.org
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: RE: [Asrg] C/R Interworking Framework
In-Reply-To: <DD198B5D07F04347B7266A3F35C42B0B0FD040@io.cybercom.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-MimeHeaders-Plugin-Info: v2.03.00
X-GCMulti: 1
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: Mon, 09 Jun 2003 15:22:32 -0400

At 08:20 AM 6/9/2003 -1000, Peter Kay wrote:

> > -----Original Message-----
> > From: Scott Nelson [mailto:scott@spamwolf.com]
>[...]
> > Setting the MAIL FROM to your address means that you could
> > end up challenging a non-existent address, then the
> > mailer_daemon that bounces the mail back to you. If the C/R
> > system was really broken, it could challenge bounces
> > from a non-existent address endlessly, but in the normal case
> > this is only twice as much work as you need to do.
> >
>
>The MAIL FROM needs to be the address of the challenge sender in order
>to allow CRI systems to interoperate. While some CR systems may inspect
>the header, other systems that bounce the email outright (like ours)
>need to look at the MAIL FROM, for reasons I've mentioned earlier in
>this thread.

This would only be true for C/R systems that interoperate via plain SMTP. I 
don't think it would be a problem to use either an ESMTP extension that is 
defined for DSNs or to define an new ESMTP extension. This way you will get 
around the MAIL FROM<> requirement that is mandated by the RFCs by passing 
the C/R information via such extension.

ALSO, not all C/R systems are using the MAIL FROM <>. Earthlink for 
example, sends out all of its challenges from the same email address 
<automated-response@earthlink.net> (see 
http://www.washingtonpost.com/wp-dyn/articles/A26774-2003Jun6.html).

Yakov


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