Re: [Asrg] We don't need no stinkin IMAP or POP, was Adding a spam button to MUAs

John Levine <johnl@taugh.com> Sat, 06 February 2010 20:08 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 718D03A6803 for <asrg@core3.amsl.com>; Sat, 6 Feb 2010 12:08:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -19.05
X-Spam-Level:
X-Spam-Status: No, score=-19.05 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_HI=-8, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31OUgG61E4if for <asrg@core3.amsl.com>; Sat, 6 Feb 2010 12:08:27 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 469163A6C42 for <asrg@irtf.org>; Sat, 6 Feb 2010 12:08:27 -0800 (PST)
Received: (qmail 50515 invoked from network); 6 Feb 2010 20:09:21 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 6 Feb 2010 20:09:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k1002; olt=johnl@user.iecc.com; bh=kfg1vUciQluzkT+4jr7Nk8c6BBv4k628skj1Xah0mik=; b=R7dGTsYbPNEJTsVX+d/QuLCjovN1jxJGHDI94WEc36OgIPyjPTKfjhiJE7Gvo7qMPzNk66UlFGs1iFLjGEVnd0RwTOl9Ev3I9RIjL0Ai35bdvgGgvEWze6USyuCtr4gCBkSDk2TCN+PMOs6JhKAMwtayJmc47b60yLMVQK9qehU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k1002; bh=kfg1vUciQluzkT+4jr7Nk8c6BBv4k628skj1Xah0mik=; b=OzIw8XDpbnEtdeNsubkWz9A681KFJKjSdTw+Fz+hQu9eE6L58fNJa/g9lr4sfUmBt+epL7CzT6aHJ728Dg2cyXnJ9E4wZExo2u30ZW/W8i3LxPQvkONT3gb3M9AwMyXfYS0qILPgmQQlApEbkiXKdKf4ex2Pm+qSxZ1iUFlTbL0=
Date: 6 Feb 2010 20:09:21 -0000
Message-ID: <20100206200921.7841.qmail@simone.iecc.com>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4B6DC663.5080900@nortel.com>
Organization:
Cc:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] We don't need no stinkin IMAP or POP, was Adding a spam button to MUAs
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Feb 2010 20:08:28 -0000

>> Their POP and IMAP servers have thousands of different names, one for
>> each hosting customer.
>
>They've already got the thousands of different names.  Adding a second 
>to the DNS provisioning mechanism won't be that hard.

In case it wasn't clear, each customer sets up his own DNS and CNAME.
This means that if the mail provider adds this feature, they have to
contact several thousand resellers and get them all to update their
DNS.  I would characterize that as hard.

> And it allows for having per-customer selections.

Heck, a header added by the MDA allows per-message selections.

>I still think it a more general solution than hacking the MTA/MDA.

Could you explain why?  It strikes me as kludgy and fragile:

* It depends on two mail pickup schemes which, while popular, are not
  universal

* It depends on the MUA remembering the path of each message, which it
  need not do now for POP.

* It depends on the POP or IMAP server having a known name, which it
  doesn't now.  For example if I'm using your POP server, I might have
  my own CNAME or A record pointing at it that you don't even know
  about.

R's,
John