Re: [Mailman-Users] removing individual email headers from digest
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 threading. That's not quite true. It's true that the user herself needs the replied-to message ID to thread, but if she replies to a message without the message ID, she breaks threading for everybody else, too. I'm sorry I missed the point about text/plain digests, though. True enough, in that case there's no need for Content-Type. Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] removing individual email headers from digest
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 to the end user.
>
> That would leave intact the Date, From, and Subject lines.
>
> So here's the solution I found by googling (would it work or is better
> way?), and commenting out lines to keep:
>
> main config is loaded is Defaults.py
> above it mm_cfg.py config loaded
> edit
> sudo nano /etc/mailman/mm_cfg.py
> with adding in the end:
>
>
> # removing frustrating headers, 2016 06 04 by OG2K
> #
> PLAIN_DIGEST_KEEP_HEADERS.remove('Message')
> PLAIN_DIGEST_KEEP_HEADERS.remove('Date')
> PLAIN_DIGEST_KEEP_HEADERS.remove('From')
> PLAIN_DIGEST_KEEP_HEADERS.remove('To')
> PLAIN_DIGEST_KEEP_HEADERS.remove('Cc')
> PLAIN_DIGEST_KEEP_HEADERS.remove('Subject')
> PLAIN_DIGEST_KEEP_HEADERS.remove('Message-ID')
> PLAIN_DIGEST_KEEP_HEADERS.remove('Keywords')
> PLAIN_DIGEST_KEEP_HEADERS.remove('Content-Type')
Do you really want to remove them all? Actually, the format of the plain
digest is described in RFC 1153 which says in part
If they exist in the
original message header, the following lines must be retained as-is
in the reconstructed header: Date:, From:, To:, Cc:, Subject:,
Message-ID:, and Keywords:, rearranged to appear in that order.
So the RFC requires those. It also says
All other header lines should be
discarded, especially Received lines.
note that this is a 'should', not 'must' but the only others we include
are the Message: header which is actually just the sequence number of
the message in the digest and Content-Type:. Actually, since this is a
'plain' digest, all non-text/plain parts have been removed anyway, and
depending on the list's content filtering, the content type will be
either text/plain or some multipart/ or message/rfc822 type which is
probably meaningless in the context of a plain text digest.
I'm not sure why we include Content-Type: in plain digests and that
chould be removed, although it could contain potentially useful
information about the original character set of the message (the charset
in the digest is that of the list's preferred language). Steve's point
about Content-Type: is only relevant for MIME digests. The only other
header not required by the RFC is Message:
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 threading.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] removing individual email headers from digest
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 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, you'll > break threading (ie, replies will be treated as new conversations by > many MUAs, and no MUAs will be able to keep late replies "near" the > message they are in-reply-to -- they'll be all jumbled up ). > > > Content-Type as that probably means nothing to the end user. > > Content-Type is essential to most MUAs to present the individual > messages correctly. Standard-conforming MUAs present the "raw" > version of messages, including HTML markup and encoded characters (eg, > foreign languages and emoticons). > > You're welcome to try it and see (as it turns out, most popular MUAs > are anything but standard-conforming, so they may be able to guess > what is meant from the context), but I would do it in the morning and > monitor the list frequently throughout the day for cries of anguish > from the digest subscribers. > > Steve > -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] removing individual email headers from digest
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, you'll break threading (ie, replies will be treated as new conversations by many MUAs, and no MUAs will be able to keep late replies "near" the message they are in-reply-to -- they'll be all jumbled up ). > Content-Type as that probably means nothing to the end user. Content-Type is essential to most MUAs to present the individual messages correctly. Standard-conforming MUAs present the "raw" version of messages, including HTML markup and encoded characters (eg, foreign languages and emoticons). You're welcome to try it and see (as it turns out, most popular MUAs are anything but standard-conforming, so they may be able to guess what is meant from the context), but I would do it in the morning and monitor the list frequently throughout the day for cries of anguish from the digest subscribers. Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
