[Email-SIG] fixing the current email module
Bill Janssen
janssen at parc.com
Thu Oct 8 22:32:19 CEST 2009
Barry Warsaw <barry at python.org> wrote:
> On Oct 8, 2009, at 3:06 PM, Stephen J. Turnbull wrote:
>
> > Bill Janssen writes:
> >
> >> I should point out that I also store lots of metadata in the
> >> registered
> >> MIME format text/rfc822-headers (defined in RFC 1892), data that
> >> doesn't
> >> necessarily conform to the specific set of headers mentioned in
> >> RFC822.
> >> It would be nice if the header support in the email package would
> >> also
> >> support reading and writing that format.
> >
> > I'm not sure what you're saying here. RFC 822 is inclusive. More or
> > less, if it looks like a header, it is a header, and we need to parse
> > it at least into field name and field body, whether RFC 822 defines
> > more specific syntax for it or not.
>
> The way I read it was that certain RFC 5322 requirements should be
> relaxed in certain cases, e.g. line length limits. If you're mutating
> the model, you wouldn't necessarily (ever? always?) throw an exception
> for long lines.
Yes, that's a good build.
Bill
More information about the Email-SIG
mailing list