Re: [Mailman-Users] Error in pipermail

2018-10-29 Thread Mark Sapiro
On 10/25/18 12:03 PM, David Gibbs wrote: > I just upgraded from a pretty old version of MM to 2.1.29 and everything > appears to be working OK. > > I noticed the following in my error log though. > > I only have a few lists that archive using the built in functionality. > > Oct 24 07:57:40 2018

Re: [Mailman-Users] mm-handler support

2018-10-29 Thread Mark Sapiro
On 10/25/18 10:00 AM, Grant Taylor via Mailman-Users wrote: > On 10/25/2018 09:22 AM, Mark Sapiro wrote: >> Please make whatever changes you feel are needed and post them here, >> and I will include them in the next release. > > What is the authoritative version / source of mm-handler? The most

Re: [Mailman-Users] Reply-to header not set in mime encoded digest's

2018-10-29 Thread Mark Sapiro
On 10/29/18 12:42 PM, David Gibbs wrote: > > When MM 2.1.29 sends out a mime encoded digest, the individual messages > in the digest don't have the reply-to header set so replies go back to > the list (as with non-digest messages). > > Is there any way to have the reply-to header set correctly on

[Mailman-Users] Reply-to header not set in mime encoded digest's

2018-10-29 Thread David Gibbs
Folks: On my lists, I have reply_goes_to_list set so users reply's default to the list address. When MM 2.1.29 sends out a mime encoded digest, the individual messages in the digest don't have the reply-to header set so replies go back to the list (as with non-digest messages). Is there an