Mark Sapiro writes:
> Of course, you are free to remove any headers you don't want, but this
> makes your digest non-compliant and Steve's point about Message-ID: and
> threading in exploded digests is valid although without References: or
> In-Reply-To:, Message-ID: alone is not to useful for
On 03/08/2017 10:11 AM, Jim Dory wrote:
>
> The fields of each collected message that seem appropriate for removal
> would be the "To:" line, since that is in the digest header, the
> Message-ID: line since that means nothing to the end user, and the
> Content-Type as that probably means nothing t
cool - things I didn't know about. Thanks Steve./jim
On Wed, Mar 8, 2017 at 9:05 PM, Stephen J. Turnbull <
turnbull.stephen...@u.tsukuba.ac.jp> wrote:
> Jim Dory writes:
>
> Warnings:
>
> > Message-ID: line since that means nothing to the end user, and the
>
> If you have any digest subscrib
Jim Dory writes:
Warnings:
> Message-ID: line since that means nothing to the end user, and the
If you have any digest subscribers with decent MUAs who are exploding
the digest into individual messages, or treating it as a folder, and
therefore would be able to respond to individual messages, y
I got a request from a user that seemed to make sense: removing unnecessary
email headers at the top of each message in a digest. So I googled it, but
before implementing it wanted to make sure it was correct and wouldn't
cause other issues by presenting it here for comment.
The fields of each col
