[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Thoughts: header/address parsing

From: Lyndon Nerenberg
Subject: Re: [Nmh-workers] Thoughts: header/address parsing
Date: Mon, 4 Aug 2014 15:22:52 -0700

On Aug 4, 2014, at 8:34 AM, address@hidden wrote:

> One example: Get the effective content part of an 'X-Spam-Status" header. (By
> "effective" I mean after unraveling line continuations etc) as part of script
> that classifies Email. Yes, I know, I could workaround, here, by assuming that
> this header and its content almost always, probably always, has a canonical
> form, and that the mis-classifications because of the very occasional
> occurrence of this canonical form, elsewhere in a file, will not do much harm.

So how would the output from this look?  Presumably you would have to tag the 
structured content in a way that would make it easy for the consumers to pick 
off the bits they are interested in.  How would you handle multi-valued field 
content (e.g. multiple recipients in To:)?  Multiple headers (e.g. Received)?


Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

reply via email to

[Prev in Thread] Current Thread [Next in Thread]