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 > mime-digest messages?
This is a consequence of the way in which DMARC mitigations are applied to outgoing messages. The modifications to the From:, Reply-To: and Cc: headers are not applied to the message that is archived, sent in digests or gated to usenet. This is generally a good thing, but is problematic in that non-DMARC Reply-To: munging is also deferred. A simple, but possibly unsatisfactory solution is to put the following two lines in mm_cfg.py GLOBAL_PIPELINE.remove('ToDigest') GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('ToOutgoing'), 'ToDigest') This will cause the message to not be added to the digests until after the header munging has occurred, but also means any DMARC actions to munge the From: or wrap the message will be applied to the digested message which may be undesirable. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better 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