RE: [Asrg] C/R Interworking Framework
"Peter Kay" <peter@titankey.com> Mon, 09 June 2003 18:29 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 OAA15712 for <asrg-archive@odin.ietf.org>; Mon, 9 Jun 2003 14:29:59 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h59ITYg25229 for asrg-archive@odin.ietf.org; Mon, 9 Jun 2003 14:29:34 -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 h59ITYB25226 for <asrg-web-archive@optimus.ietf.org>; Mon, 9 Jun 2003 14:29:34 -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 OAA15698; Mon, 9 Jun 2003 14:29:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PRMe-00065n-00; Mon, 09 Jun 2003 14:27:28 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PRMd-00065h-00; Mon, 09 Jun 2003 14:27:27 -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 h59IMTB24736; Mon, 9 Jun 2003 14:22:29 -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 h59IL8B24646 for <asrg@optimus.ietf.org>; Mon, 9 Jun 2003 14:21:08 -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 OAA15249 for <asrg@ietf.org>; Mon, 9 Jun 2003 14:21:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PREV-0005yX-00 for asrg@ietf.org; Mon, 09 Jun 2003 14:19:03 -0400
Received: from imail.centuryc.net ([216.30.168.20] helo=isp-appsvr01.centuryc.com) by ietf-mx with esmtp (Exim 4.12) id 19PREU-0005xq-00 for asrg@ietf.org; Mon, 09 Jun 2003 14:19:02 -0400
Received: from cybercominc.com [66.91.134.126] by isp-appsvr01.centuryc.com (SMTPD32-7.14) id A04018650084; Mon, 09 Jun 2003 08:21:52 -1000
Received: from a66b91n134client123.hawaii.rr.com (66.91.134.123) by cybercominc-zzt with SMTP; Mon, 09 Jun 2003 18:25:10 GMT
X-Titankey-e_id: <ce4caa67-b205-4b48-9af5-42abdcc66464>
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: <DD198B5D07F04347B7266A3F35C42B0B0FD040@io.cybercom.local>
Thread-Topic: [Asrg] C/R Interworking Framework
Thread-Index: AcMtKDgmeAsFqfdLSjCNau8/iL7r/gBixaRg
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 h59IL9B24647
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 08:20:29 -1000
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
> -----Original Message----- > From: Scott Nelson [mailto:scott@spamwolf.com] > > At 06:24 PM 6/6/03 -1000, Peter Kay wrote: > >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. > > > > If you're sending a DSN, then the From: header could be your > address, but the MAIL FROM should probably be <>. That > prevents a lot of bad things from happening. > I think DSN in the CR space is a matter of semantics and definition. I'm not 100% whether a challenge email is a DSN or not, and like I said earlier I can see a case for it ether way. If you're saying that if it's a DSN, then the MAIL FROM s/b <>, then I'll say that challenge emails are not DSNs. > 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. You are correct about that fact that you "could end up challenging a non-existent address". Most spammers use bad addresses. Our system handles mail that is bounced because of non-existent email and this also results in reduced load on the MTS due to more intelligent mailer_daemon handling. Peter _______________________________________________ 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