RE: [Asrg] C/R Interworking Framework
"Peter Kay" <peter@titankey.com> Sat, 07 June 2003 04:27 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 AAA23961 for <asrg-archive@odin.ietf.org>; Sat, 7 Jun 2003 00:27:40 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h574REp25600 for asrg-archive@odin.ietf.org; Sat, 7 Jun 2003 00:27:14 -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 h574REB25597 for <asrg-web-archive@optimus.ietf.org>; Sat, 7 Jun 2003 00:27:14 -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 AAA23952; Sat, 7 Jun 2003 00:27:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OVGW-0001DO-00; Sat, 07 Jun 2003 00:25:16 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19OVGV-0001DL-00; Sat, 07 Jun 2003 00:25:15 -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 h574Q6B25572; Sat, 7 Jun 2003 00:26:06 -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 h574PKB25550 for <asrg@optimus.ietf.org>; Sat, 7 Jun 2003 00:25:20 -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 AAA23947 for <asrg@ietf.org>; Sat, 7 Jun 2003 00:25:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OVEg-0001DB-00 for asrg@ietf.org; Sat, 07 Jun 2003 00:23:22 -0400
Received: from imail.centuryc.net ([216.30.168.20] helo=isp-appsvr01.centuryc.com) by ietf-mx with esmtp (Exim 4.12) id 19OVEf-0001Cx-00 for asrg@ietf.org; Sat, 07 Jun 2003 00:23:21 -0400
Received: from cybercominc.com [66.91.134.126] by isp-appsvr01.centuryc.com (SMTPD32-7.14) id A96A464009E; Fri, 06 Jun 2003 18:26:18 -1000
Received: from a66b91n134client123.hawaii.rr.com (66.91.134.123) by cybercominc-zzt with SMTP; Sat, 07 Jun 2003 04:29:30 GMT
X-Titankey-e_id: <39c573a1-d495-45ce-9235-9cae797e33ee>
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: RE: [Asrg] C/R Interworking Framework
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Message-ID: <DD198B5D07F04347B7266A3F35C42B0B0D8C11@io.cybercom.local>
Thread-Topic: [Asrg] C/R Interworking Framework
Thread-Index: AcMsV5pTm43GnNrmTHCfkHLoEJHQqAAVS6nQ
From: Peter Kay <peter@titankey.com>
To: Scott Nelson <scott@spamwolf.com>, asrg@ietf.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h574PLB25551
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: Fri, 06 Jun 2003 18:24:52 -1000
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
I agree, a challenge can be seen as a DSN or a new message. My point is that in either case, the MAIL FROM or REPLYTO should be consistent with the challenger's email address, otherwise 2 C/R systems will challenge each other's challenge. > -----Original Message----- > From: Scott Nelson [mailto:scott@spamwolf.com] > Sent: Friday, June 06, 2003 7:09 AM > To: asrg@ietf.org > Subject: Re: [Asrg] C/R Interworking Framework > > > At 03:22 PM 6/5/03 -0400, Kee Hinckley wrote: > >At 10:52 AM -0400 6/5/03, Yakov Shafranovich wrote: > >>The "FROM" field is the one that will get C/R checked, since that is > >>the mailbox that sent the email. Additionally, the "MAIL FROM" > >>addresses that is used in SMTP is not intended to this purpose, > >>rather it indicates a mailbox to which errors should be sent to. It > >>is perfectly legal and sometimes even recommended in RFC > 2821 to use > >><> for the MAIL FROM. > > > >Are you advocating that C/R systems send mail to the From: address > >rather than MAIL FROM? That strikes me as exceedingly wrong. MAIL > >FROM is for notification of delivery problems--and that's exactly > >what C/R is. Furthermore, we've seen on this list what happens when > >a C/R system sends to From: instead of MAIL FROM--everyone who posts > >to the list gets challenged by the person who forgot to > whitelist the > >mailing list. This is the "On Vacation" message problem all over > >again. > > > > There are basically two choices; > Envelope from a.k.a. MAIL FROM, and > Reply-To: (or From: if there's no Reply-To:) > > > If you view a challenge as a DSN then envelope from is the proper > choice. I'd even go so far as to format the challenge as an > RFC 1894 compliant DSN. (This has the interesting side effect > that challenging a mailing list is likely to unsubscribe you > automatically) And like any DSN, I recommend including the > message-id in the In-Reply-To: and Reference: headers. > > If however, you view a challenge as a new message, > then sending it to the Reply-To: (or From: if there is no Reply-To:) > is the more logical choice. > > Personally I feel that challenges are DSNs, so envelope from > is the right choice, but I can see the "new message" > point of view too. > > > Scott Nelson <scott@spamwolf.com> > > _______________________________________________ > Asrg mailing list > Asrg@ietf.org > https://www1.ietf.org/mailman/listinfo/asrg > > > _______________________________________________ Asrg mailing list Asrg@ietf.org https://www1.ietf.org/mailman/listinfo/asrg
- RE: [Asrg] C/R Interworking Framework Eric Dean
- RE: [Asrg] C/R Interworking Framework Yakov Shafranovich
- RE: [Asrg] C/R Interworking Framework Eric Dean
- RE: [Asrg] C/R Interworking Framework Yakov Shafranovich
- Re: [Asrg] C/R Interworking Framework John Fenley
- RE: [Asrg] C/R Interworking Framework Peter Kay
- Re: [Asrg] C/R Interworking Framework Yakov Shafranovich
- Re: [Asrg] C/R Interworking Framework Vernon Schryver
- RE: [Asrg] C/R Interworking Framework Eric Dean
- Re: [Asrg] C/R Interworking Framework Yakov Shafranovich
- Re: [Asrg] C/R Interworking Framework Vernon Schryver
- RE: [Asrg] C/R Interworking Framework Peter Kay
- Re: [Asrg] C/R Interworking Framework Yakov Shafranovich
- Re: [Asrg] C/R Interworking Framework Vernon Schryver
- Re: [Asrg] C/R Interworking Framework Dave Aronson
- Re: [Asrg] C/R Interworking Framework Yakov Shafranovich
- Re: [Asrg] C/R Interworking Framework Yakov Shafranovich
- Re: [Asrg] C/R Interworking Framework Vernon Schryver
- Re: [Asrg] C/R Interworking Framework Yakov Shafranovich
- Re: [Asrg] C/R Interworking Framework Kee Hinckley
- Re: [Asrg] C/R Interworking Framework Scott Nelson
- RE: [Asrg] C/R Interworking Framework Peter Kay
- RE: [Asrg] C/R Interworking Framework Peter Kay
- RE: [Asrg] C/R Interworking Framework Scott Nelson
- RE: [Asrg] C/R Interworking Framework Peter Kay
- RE: [Asrg] C/R Interworking Framework Yakov Shafranovich
- Re: [Asrg] C/R Interworking Framework Rob Cameron
- RE: [Asrg] C/R Interworking Framework Peter Kay
- Re: [Asrg] C/R Interworking Framework Yakov Shafranovich
- Re: [Asrg] C/R Interworking Framework Art Pollard
- RE: [Asrg] C/R Interworking Framework Peter Kay
- Re: [Asrg] C/R Interworking Framework Yakov Shafranovich
- RE: [Asrg] C/R Interworking Framework Eric D. Williams
- RE: [Asrg] C/R Interworking Framework Yakov Shafranovich
- RE: [Asrg] C/R Interworking Framework Art Pollard
- RE: [Asrg] C/R Interworking Framework Art Pollard
- RE: [Asrg] C/R Interworking Framework Eric D. Williams
- RE: [Asrg] C/R Interworking Framework Yakov Shafranovich