[Bug 889635] Re: Per-list configurable message headers for digests

Mark Sapiro mark at msapiro.net
Sun Nov 13 00:41:28 CET 2011


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 mailman-users at python.org 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.

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/889635

Title:
  Per-list configurable message headers for digests

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions


More information about the Mailman-coders mailing list