> Another issue in that is the choice to send mail over IPv6. This has > well-known risks of running into more draconian filtering than sticking > with IPv4, and the operators of the mailing lists system have clearly > NOT considered those risks or their mitigation.
> Mailing list managers should not assume anything about the > state of messages that come in. Especially if there is a trivial action > that they can take to make sure that the message they send out does not > break something. I receive digests from [mailop]. Header of last digest hasn't DKIM. The envelope-from is <mailop-bounces @ mailop.org>, the mailop.org domain currently hasn't SPF. With sending mail via IPv6, it's a recipe for disaster. ~ $ dig +short mailop.org txt ~ $ > In this case, said trivial action is removing / renaming the incoming > DKIM-Signature header. And adding one for the mailop.org domain. _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
