Simon Ser

Add buffered e-mail helpers

3

Not sure this is a good idea yet. Would need to have more use-cases in mind. Some users of the library may want *not* to use a streaming API, for...

Bump line length soft limit to 998 for headers

6

The algorithm mangling long lines is pretty messy. I'd rather not use it when not needed. See https://tools.ietf.org/html/rfc5322#section-2.1.1

Optimize Entity.WriteTo

1

When the charset and `Content-Transfer-Encoding` haven't been modfiied, we can avoid decoding and re-encoding the entity's body. We can just pipe the original message's body. Related to https://github.com/emersion/go-message/issues/84

Optimize Entity.WriteTo when encoding/charset are unchanged

2

Closes: https://github.com/emersion/go-message/issues/86

Add Entity.Reader

1

Add an `Entity.Reader` function which returns an `io.Reader` for the entity. This would allow users to read a header, inspect it and then forward the reader to someone else. Ideally...

Add helpers for `Return-Path` and `Received`. These can contain CFWS, so the parser part will need to use `headerParser`. See https://tools.ietf.org/html/rfc5322#section-3.6.7

It may be necessary to get the parent parts header when handling leaf parts, for instance to know if parts should be appended to each other (`multipart/related`) or if they...

Same as `io.Pipe` but for messages. This would allow to chain message transformations without having to format and parse messages during each step.

Recommend using the nickname as fallback value for USER params

4

This documents a widely implemented practice. This allows clients to discover when this field is set to a meaningful value, and when it's not.

Add hint that MOTD lines may be prefixed with "- "

1

Clients may want to strip that prefix to improve their UI.