[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Thoughts: header/address parsing
From: |
Ken Hornstein |
Subject: |
Re: [Nmh-workers] Thoughts: header/address parsing |
Date: |
Mon, 04 Aug 2014 11:50:22 -0400 |
>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.
That program already exists today.
% scan -width 9999 -format '%{x-spam-status}' messages ....
should do what you want, I think.
--Ken
- [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/02
- Re: [Nmh-workers] Thoughts: header/address parsing, Ralph Corderoy, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, norm, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Lyndon Nerenberg, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, norm, 2014/08/04
- Re: [Nmh-workers] Thoughts: header/address parsing,
Ken Hornstein <=
- Re: [Nmh-workers] Thoughts: header/address parsing, Ralph Corderoy, 2014/08/05
- Re: [Nmh-workers] Thoughts: header/address parsing, norm, 2014/08/05
- Re: [Nmh-workers] Thoughts: header/address parsing, Jon Fairbairn, 2014/08/06
- Re: [Nmh-workers] Thoughts: header/address parsing, Ralph Corderoy, 2014/08/06
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/06
- Re: [Nmh-workers] Thoughts: header/address parsing, Lyndon Nerenberg, 2014/08/04
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/04
- Re: [Nmh-workers] Thoughts: header/address parsing, Lyndon Nerenberg, 2014/08/04