Re: comments: draft-moore-auto-email-response-04.txt

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Wed, 29 October 2003 16:53 UTC

Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id h9TGrCkT029315 for <ietf-822-bks@above.proper.com>; Wed, 29 Oct 2003 08:53:12 -0800 (PST) (envelope-from owner-ietf-822@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id h9TGrB2B029314 for ietf-822-bks; Wed, 29 Oct 2003 08:53:11 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-822@mail.imc.org using -f
Received: from libertango.oryx.com (libertango.oryx.com [195.30.94.163]) by above.proper.com (8.12.10/8.12.8) with ESMTP id h9TGrAkT029309 for <ietf-822@imc.org>; Wed, 29 Oct 2003 08:53:11 -0800 (PST) (envelope-from arnt@gulbrandsen.priv.no)
Message-Id: <aFVEHUCz4vhfZ1BF7VB9wg.md5@libertango.oryx.com>
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Keith Moore <moore@cs.utk.edu>
Subject: Re: comments: draft-moore-auto-email-response-04.txt
Cc: Markus Stumpf <maex-lists-spam-ietf822@space.net>, IETF RFC-822 list <ietf-822@imc.org>
References: <20031027163534.GA31137@Space.Net> <20031028124408.3d2d7e90.moore@cs.utk.edu> <20031028190429.GN65698@Space.Net> <20031028141836.1d2ade0f.moore@cs.utk.edu>
In-Reply-To: <20031028141836.1d2ade0f.moore@cs.utk.edu>
Content-Type: text/plain; format="flowed"
MIME-Version: 1.0
Date: Wed, 29 Oct 2003 17:57:05 +0100
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>

Keith Moore writes:
> auto-submitted doesn't want to be come a general-purpose message 
> labelling mechanism. arguably we have too many of those already. we 
> could use content-disposition or content-type or 
> content-description....

The example I posted, "auto-submitted: auto-generated; generator=sophos; 
type=antivirus". Where should it go? Is it reasonable in the first 
place? Markus has presented a case that such details are useful - a 
sufficient case?

Content-Type is about the content's format, not about its nature. That 
is to say, it's text/plain rather than text/essay or text/autoresponse.

Content-Description is unstructured human-readable text which IMO makes 
it unusable.

Content-Disposition is about how the receiver should present the 
message, e.g. a suggested filename for a file. I suppose something like 
"type=antivirus" might go here, since the purpose of that is to enable 
appropriate disposition (AKA file in /dev/null).

I've seen X-Mailer and User-Agent, but can't summon much enthusiasm for them.

So if an autoresponder wants to say something about which generator 
auto-generated a message, auto-submitted seems the right place. The 
"type" could go either here or in content-disposition, both seem about 
equally appropriate to me, depending on whether the "type" is seen as 
the type of responder or the type of response.

--Arnt