On 11/19/19 8:39 AM, Andy Cravens wrote:
> Mailman 2.1.26. I modified all our lists that did not have munge_from set
> for DMARC compliance. I ran a few tests and was able to send and receive
> email from my test list. Now I’m getting reports that large numbers of
> emails are bouncing and me
Hi,
On 2019/11/20 2:27, Andy Cravens wrote:
I meant to say our default setting for all lists is to set from_is_list to
munge_from. I also realized that some list managers (who’s domain uses DKIM)
have added footers to their mailing list so I’ll have to strip the DKIM headers
no matter wha
On 11/19/19 9:27 AM, Andy Cravens wrote:
>
> I meant to say our default setting for all lists is to set from_is_list to
> munge_from. I also realized that some list managers (who’s domain uses DKIM)
> have added footers to their mailing list so I’ll have to strip the DKIM
> headers no matter w
On Nov 19, 2019, at 9:39 AM, Andy Cravens wrote:
Mailman 2.1.26. I modified all our lists that did not have munge_from set for
DMARC compliance. I ran a few tests and was able to send and receive email
from my test list. Now I’m getting reports that large numbers of emails are
bouncing an
Mailman 2.1.26. I modified all our lists that did not have munge_from set for
DMARC compliance. I ran a few tests and was able to send and receive email
from my test list. Now I’m getting reports that large numbers of emails are
bouncing and members are being unsubscribed. I had someone forw
