[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 19:30:24 -0400 |
>> Looking at it ... the grammer is not huge. I think it will be easier
>> than the RFC-5322 address parser.
>
>It's not just the bison part, it's all the other code that
>builds the internal Content, etc., structures. That'll have to
>be ported. (I assume that would be the approach.)
Well, all of this pretty much assumes that the code to generate a Content
structure is going to have to be redone from scratch. In general, my
thinking was:
- Slurp in headers via our header parsing routine, build Content structure.
- Parse the address headers, as needed.
- Parse the MIME headers, as needed.
- Assuming a multipart message, find the next content boundary, read in
content headers via our header parsing routines. Parse the MIME headers
as needed.
You get the idea.
--Ken
- Re: [Nmh-workers] Thoughts: header/address parsing, (continued)
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Robert Elz, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Paul Fox, 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, bergman, 2014/08/04
- Re: [Nmh-workers] Thoughts: header/address parsing, Ralph Corderoy, 2014/08/05
- Re: [Nmh-workers] Thoughts: header/address parsing, Jon Fairbairn, 2014/08/04
- Re: [Nmh-workers] Thoughts: header/address parsing, Mike O'Dell, 2014/08/04
Re: [Nmh-workers] Thoughts: header/address parsing, David Levine, 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, Ken Hornstein, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Lyndon Nerenberg, 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, Ken Hornstein, 2014/08/03
Re: [Nmh-workers] Thoughts: header/address parsing, Ralph Corderoy, 2014/08/05
Re: [Nmh-workers] Thoughts: header/address parsing, David Levine, 2014/08/09