[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: |
Sun, 03 Aug 2014 18:09:40 -0400 |
>I wondering, if in doing this, you might consider a new nmh command that would
>parse message headers. I suppose that there a dozens of scripts out that there
>do some of this. I'm guessing that they are mostly all ad hoc, and buggy.
That command already exists, sort of. ap(1) does basic address parsing, and
you could use fmttest(1) to do more complicated stuff.
--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 <=
- 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, 2014/08/04
- 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