Re: header inventory

Mark E. Mallett wrote:
> On Thu, Mar 11, 2004 at 11:42:23AM +1000, Laird Breyer wrote:
...

> One thing I would like to see (that I mentioned on the main list a
> while back) is version/locus information.  Each filter would supply a
> tuple that uniquely identifies the filter and its location in the
> delivery chain.  (None of the examples posted so far do this, although
> one might be able to infer some of it by the header location in
> relation to other added headers-- however I don't think people
> mentioned where they were adding the headers.)  Required information
> might include:
> 
>    - filter name and version

Filter name Yes. But version is really important ?

>    - server name/IP information
>    - delivery address or other key

What to you meant by delivered address ? Recipients ? I'm not sure this 
is a good idea. As if you add this, you can reveal BCCs, at least at 
current version of SMTP protocol. And what about an alias resolving to 
some thousand recipients ???

On the other hand, what seems to me very important is to add the Message 
ID of the message in order to someone be able to look for it at log 
files generated by the filter.

Also, I'm not sure showing the reasons the message was classed as being 
spam is important or even desirable. For the mail server admin, yes, but 
not necessarily for end user. This may be an option, not a requirement.

Otherwise, the structure proposed below (similar to what is already used 
for other headers : content-type, content-disposition and so) seems a 
good idea.

> 
> (Note that multiple filters can be invoked at the same server so the
> delivery address might be used to further identify the filter stage).
> 
> Beyond that identifying information, there could be specific data
> produced by the filter.  An obvious format would simply be
> keyword=value pairs, with some keywords having specific registered
> meanings, some of which would be the version/stage information above.
> 
> e.g.:
> 
> Filtered-By:   filter=spam-pie version=3.14159 ipv4=10.0.0.1
> 	host=mx.example.com [email protected]
> 	thumbs=down
> 	problem="No To Line"
> 	problem="html-only"
> 	Score=12
> 
> One could encapsulate a reasonable amount of information in this sort
> of header, while optionally still adding other X- headers as well,
> perhaps with a requirement that those other headers be added directly
> above (or below) the standard "Filtered-By" header.
> 
> mm
> 
> 



-- 
  ---------------------------------------------------------------
  Jose Marcio MARTINS DA CRUZ           Tel. :(33) 01.40.51.93.41
  Ecole des Mines de Paris              http://j-chkmail.ensmp.fr
  60, bd Saint Michel                http://www.ensmp.fr/~martins
  75272 - PARIS CEDEX 06      mailto:[email protected]