On 10/29/18 4:51 PM, Mark Sapiro wrote:
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
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
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
