Per-list configurable message headers for digests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Triaged
|
Low
|
Unassigned |
Bug Description
Digest messages are sent out with a partial set of headers for each message.
The list of headers kept for each plain-text digested message is configured by the setting:
PLAIN_DIGEST_
'Message', 'Date', 'From',
'Subject', 'To', 'Cc',
'Message-ID', 'Keywords',
'Content-Type',
]
My users are very perplexed and frustrated by the e-mail headers included in the digest - in particular, the Message-ID and Content-Type are meaningless, and the To header is repetitive. All this "noise" clutters up the content and makes the digest harder to read.
Given that this is a plain-text digest, with the headers listed in the message body, I don't really see an RFC issue here? Yet they can only be configured using a list-wide override in mm_cfg.py
I would be willing to work on this to allow a list admin to override the plain digest headers using the web interface, but want to hear from the development team if this is a patch they would be willing to consider before I invest the time.
thanks.
tags: | added: mailman3 |
Changed in mailman: | |
status: | New → Triaged |
importance: | Undecided → Low |
The format of the plain digest is specified in RFC 1153 <http:// www.rfc- editor. org/rfc/ rfc1153. txt> 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."
The only headers included in the plain digest which are not in that list are Message: and Content-Type:. I can understand that Content-Type is not too useful since the message has been scrubbed to text/plain, but it can retain parameters such as format=flowed which might be useful to some.
I would consider removing Content-Type: from the default list, but only after surveying the <email address hidden> list to see if there are objections.
BTW, In current Mailman, the Defaults.py setting for PLAIN_DIGEST_ KEEP_HEADERS is
PLAIN_DIGEST_ KEEP_HEADERS = [
'Message',
# RFC 1153 headers in order
'Date', 'From', 'To', 'Cc', 'Subject', 'Message-ID', 'Keywords',
'Content-Type',
]
which puts the Subject: in the order specified by the RFC.