smorytko@gmail.com writes:

Is there a way to optionally cause the Subject line to display with the text body and as a summary at the top of the digest?

It will always appear in the summary, I believe. Unless someone at your site has changed the configuration for mime_digest_keep_headers and/or plain_digest_keep_headers, it is already included, and should be displayed in the individual messages. I suspect this is a user agent (mail client) problem.

Again I'm wondering if this is a web front-end function, a MM3 core function, or perhaps both? I ask because if it's not a MM3 core function I'll need to ask our developer for an Empathy modification.

The digest message is a core function. When a message arrives for a digest-able list, Mailman core will add that to a separate mailbox, signalling the digest runner. The digest runner then decides if it's time and if so, reads the mailbox and assembles and sends the digest message. Digest creation and distribution is therefore entirely done by Mailman core.

Display is another matter. As with all received mail, the Harvard Law applies:

Under the most rigorously controlled conditions of pressure,
temperature, volume, humidity, and other variables the [mail
client] will do as it damn well pleases.

Digest display is notoriously awful in common consumer mail clients. Many frustrated admins simply turn off the feature to quiet their subscribers.

Below is an example from an Empathy-base list

The web interface doesn't matter. As far as I know it is impossible for the archive interfaces (Empathy, HyperKitty, etc) to view digests, because they receive each post individually and have no way to know the digesting schedule, so they can't calculate one either. That's certainly true of HyperKitty.

So I assume you are viewing the digest in your own mail client?

There are two possibilities.

1. Your mail client is refusing to display the headers in the digested messages even though they are present. I think this is more likely; the digest header configuration is rarely if ever changed.

2. The list is configured not to keep any headers. If you have access to the Mailman configuration files, the defaults are in the [digests] section of schema.cfg, and local changes, if any, are in the [digests] section of mailman.cfg. (Local changes completely override the configuration in schema.py.) If you don't, you'll have to ask the admin to check.

Here are the schema.cfg defaults from a fairly fresh update of the Mailman sources (I doubt these lines have changed since being written):

[digests] # Headers which should be kept in both RFC 1153 (plain) and MIME digests. RFC # 1153 also specifies these headers in this exact order, so order matters. # These are space separated and case insensitive. mime_digest_keep_headers: Date From To Cc Subject Message-ID Keywords In-Reply-To References Content-Type MIME-Version Content-Transfer-Encoding Precedence Reply-To Message List-Post

plain_digest_keep_headers: Message Date From Subject To Cc Message-ID Keywords Content-Type

("Space separated" includes newlines and tabs.) As you can see, Subject is in both.

Steve