Re: [Asrg] C/R Interworking Framework

Dave Aronson <dja2003@hotpop.com> Thu, 05 June 2003 13:13 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 JAA23618 for <asrg-archive@odin.ietf.org>; Thu, 5 Jun 2003 09:13:18 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h55DCpT02931 for asrg-archive@odin.ietf.org; Thu, 5 Jun 2003 09:12:51 -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 h55DCpB02928 for <asrg-web-archive@optimus.ietf.org>; Thu, 5 Jun 2003 09:12:51 -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 JAA23579; Thu, 5 Jun 2003 09:12:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NuW8-0006fp-00; Thu, 05 Jun 2003 09:10:56 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NuW8-0006fk-00; Thu, 05 Jun 2003 09:10:56 -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 h55D51B01635; Thu, 5 Jun 2003 09:05:01 -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 h55D4EB01579 for <asrg@optimus.ietf.org>; Thu, 5 Jun 2003 09:04: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 JAA23218 for <asrg@ietf.org>; Thu, 5 Jun 2003 09:04:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NuNn-0006bL-00 for asrg@ietf.org; Thu, 05 Jun 2003 09:02:19 -0400
Received: from mail15.speakeasy.net ([216.254.0.215] helo=mail.speakeasy.net) by ietf-mx with esmtp (Exim 4.12) id 19NuNn-0006bI-00 for asrg@ietf.org; Thu, 05 Jun 2003 09:02:19 -0400
Received: (qmail 22749 invoked from network); 5 Jun 2003 13:04:10 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196]) (envelope-sender <dja2003@hotpop.com>) by mail15.speakeasy.net (qmail-ldap-1.03) with SMTP for <peter@titankey.com>; 5 Jun 2003 13:04:10 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Peter Kay <peter@titankey.com>
Subject: Re: [Asrg] C/R Interworking Framework
User-Agent: KMail/1.5
References: <DD198B5D07F04347B7266A3F35C42B0B0FD01E@io.cybercom.local>
In-Reply-To: <DD198B5D07F04347B7266A3F35C42B0B0FD01E@io.cybercom.local>
Cc: asrg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306050906.41885.dja2003@hotpop.com>
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: Thu, 05 Jun 2003 09:06:41 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

"Peter Kay" <peter@titankey.com> wrote:

 > 2. The recipient does not have me on their whitelist, so they send a
 > challenge. But because their "FROM" address in the MAIL command is
 > NOT the sender's address, TTK doesn't have that address on its
 > whitelist so it sends a challenge to the challenge.
 >
 > End result is that the TTK user never sees the recipients challenge
 > and the recipient never gets the email.  So what ends up happening is
 > the recipient has to go through their quarantine folder and pull out
 > the email.  The TTK user never gets the email because the challenge
 > was killed in the MAIL command.
 >
 > So, to me, C/R systems need to at least use their end-users email
 > address on the MAIL  FROM address in the mail command.

Using a Reply-To could throw a bit of a monkey-wrench into this.  Perhaps 
the protocol should specify sending to the Reply-To (if present), and if 
that verifies, then consider the From verified as well.

Also, many people have Lots And Lots of addresses.  I can think of three 
addies offhand of mine that lots of people get email from, not counting 
the temporaries, and sometimes I forget to switch addies when sending to 
certain people.  Perhaps the protocol could also say, "I might also send 
you email later under the following addresses", and whitelist them too, 
possibly with the whole C/R process repeated for each.

Something tells me there are problems with these ideas, but there's too 
much blood in my coffee stream to figure them out at the moment.  |-)

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info

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