Re: [Asrg] What can we expect MUAs to do?
John Levine <johnl@taugh.com> Tue, 09 February 2010 01:27 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 D421028C1CB for <asrg@core3.amsl.com>; Mon, 8 Feb 2010 17:27:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.828
X-Spam-Level:
X-Spam-Status: No, score=-13.828 tagged_above=-999 required=5 tests=[AWL=-2.629, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3]
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 Gyfih2GDSVeW for <asrg@core3.amsl.com>; Mon, 8 Feb 2010 17:27:55 -0800 (PST)
Received: from gal.iecc.com (l053.n.taugh.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 7572C3A74EE for <asrg@irtf.org>; Mon, 8 Feb 2010 17:27:55 -0800 (PST)
Received: (qmail 17537 invoked from network); 9 Feb 2010 01:28:59 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 9 Feb 2010 01:28:59 -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=jgPf3/UrYF5Uswh8FM0OCTqTdgW7rZ2cawfp6wBUH+4=; b=KXtywTN0HUyBcPT2vkhEJRn105NveYzOJ5YfiMdTE25MlG0HMEKApGovQAV8Fvwk7TfWBPguRUaKP52/mre6NZsmBMuGZpBya2kIiXdHCQ7Lhrdlrn3mn2+OCrWjXcPadTv98w8r448k572vhyDrkCp9NZGJxFfrHOzTJ5vXmEQ=
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=jgPf3/UrYF5Uswh8FM0OCTqTdgW7rZ2cawfp6wBUH+4=; b=K+n+6yynPowX8e5tmiZnnVMq7BDgfWdTQKUhBIcpm+ITk7TKapV5bwyQa8Utohuj44eMGtMhce9HqCbbJrwOHho0GOBF7GAz6uykApXc4WRM6SibceQuHJuz2+g8s4+5LJigfKvQ396+rjAvT0tEpiYZhI4y7zxCd7H1LyglCBY=
Date: Tue, 09 Feb 2010 01:28:58 -0000
Message-ID: <20100209012858.225.qmail@simone.iecc.com>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <C98C919F-98FA-4D32-9CE9-CC26C536273F@blighty.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] What can we expect MUAs to do?
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: Tue, 09 Feb 2010 01:27:57 -0000
>>> * Create and render MIME. >>> (No, you don't get to call yourself an MUA if you can't do that today). Are there still MUAs used by people other than retro-perverse geeks that don't render HTML? Even Alpine does a credible lynx-like character rendering of HTML parts. The reason I ask is that if a MUA knows about HTML, that makes it fairly likely it knows about HTTP, and if it knows about HTTP, that makes an HTTP transaction a plausible way to send the report. (The obvious transaction is HTTP PUT, but I'm not sure how many firewalls and proxies properly support it.) This avoids the routing through strangers problem. R's, John
- [Asrg] What can we expect MUAs to do? John Levine
- Re: [Asrg] What can we expect MUAs to do? Steve Atkins
- Re: [Asrg] What can we expect MUAs to do? Ian Eiloart
- Re: [Asrg] What can we expect MUAs to do? der Mouse
- Re: [Asrg] What can we expect MUAs to do? Steve Atkins
- Re: [Asrg] What can we expect MUAs to do? Chris Lewis
- Re: [Asrg] What can we expect MUAs to do? Steve Atkins
- Re: [Asrg] What can we expect MUAs to do? John Levine