Re: [Asrg] Permission-based antispam-antivirus solutions

John Kodis <kodis@mail630.gsfc.nasa.gov> Sat, 21 June 2003 19:30 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 PAA14186 for <asrg-archive@odin.ietf.org>; Sat, 21 Jun 2003 15:30:33 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5LJU5Q26626 for asrg-archive@odin.ietf.org; Sat, 21 Jun 2003 15:30:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19To3p-0006vN-Jg for asrg-web-archive@optimus.ietf.org; Sat, 21 Jun 2003 15:30:05 -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 PAA14179; Sat, 21 Jun 2003 15:30:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19To3o-0000jU-00; Sat, 21 Jun 2003 15:30:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19To3n-0000jR-00; Sat, 21 Jun 2003 15:30:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19To3l-0006tS-Nv; Sat, 21 Jun 2003 15:30:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19To3W-0006t5-BP for asrg@optimus.ietf.org; Sat, 21 Jun 2003 15:29:46 -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 PAA14174 for <asrg@ietf.org>; Sat, 21 Jun 2003 15:29:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19To3V-0000jM-00 for asrg@ietf.org; Sat, 21 Jun 2003 15:29:45 -0400
Received: from mail630.gsfc.nasa.gov ([128.183.190.39]) by ietf-mx with esmtp (Exim 4.12) id 19To3U-0000jJ-00 for asrg@ietf.org; Sat, 21 Jun 2003 15:29:44 -0400
Received: from tux.gsfc.nasa.gov (tux.gsfc.nasa.gov [128.183.191.134]) by mail630.gsfc.nasa.gov (8.12.8/8.12.5) with ESMTP id h5LJTeAV005174 for <asrg@ietf.org>; Sat, 21 Jun 2003 15:29:40 -0400
Received: from tux.gsfc.nasa.gov (localhost.localdomain [127.0.0.1]) by tux.gsfc.nasa.gov (8.12.8/8.12.8) with ESMTP id h5LJTfhv014780 for <asrg@ietf.org>; Sat, 21 Jun 2003 15:29:41 -0400
Received: (from kodis@localhost) by tux.gsfc.nasa.gov (8.12.8/8.12.8/Submit) id h5LJTf4G014778 for asrg@ietf.org; Sat, 21 Jun 2003 15:29:41 -0400
From: John Kodis <kodis@mail630.gsfc.nasa.gov>
To: asrg@ietf.org
Subject: Re: [Asrg] Permission-based antispam-antivirus solutions
Message-ID: <20030621192941.GA14667@tux.gsfc.nasa.gov>
References: <B0000024108@nts1.terabites.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <B0000024108@nts1.terabites.com>
User-Agent: Mutt/1.4.1i
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: Sat, 21 Jun 2003 15:29:41 -0400

On Thu, Jun 19, 2003 at 06:50:36PM -0500, gep2@terabites.com wrote:

> Programmers and sysadmins, and people who started using email before
> MIME was introduced, tend to dislike HTML email.  Other people see
> the ability to use boldface and italics as normal features of any
> text-editing environment (which they consider their MUA to be).

Even so, HTML is the wrong tool for the job.  A better approach is the
text/enriched MIME Content-type described in RFC 1563 at
http://www.faqs.org/rfcs/rfc1563.html 

This provides all the formatting that someone composing a simple email
message is likely to require (and then some), but without the bloat
and security risks inherent in a full HTML rendering engine.  It also
produces mail messages can be rendered well by text-based email
clients such as mutt, and which are still fairly legible even as raw
text due to the lack of "&nbsp;" strings which seem to make up the
bulk of many HTML email messages.

> If you want FULL text-handling features, then you can send LaTeX or
> Word (or whatever) documents as attachments (and thus enable
> attachments) for those people you trust to send you that kind of material.

Exactly right.  This is simply a matter of using the correct tool for
the job at hand.

Unfortunately, restricting email content type seems unlikely to have
any long-term impact on spam, as the spammers will simply adapt their
behavior to whatever content type is most likely to get their message
across.

-- 
John Kodis                                    Goddard Space Flight Center
kodis@mail630.gsfc.nasa.gov                      Greenbelt, Maryland, USA
Phone: 301-286-7376                                     Fax: 301-286-1771

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