<div dir="ltr">Hi Dave,<div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 4, 2015 at 2:58 PM, Dave Cooper <span dir="ltr"><<a href="mailto:david.cooper@genworks.com" target="_blank">david.cooper@genworks.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div><div>This article claims that mailman "supports standards needed to avoid this problem:"<span></span></div><div><br></div><a href="https://sites.google.com/site/oauthgoog/mlistsdkim" target="_blank">https://sites.google.com/site/oauthgoog/mlistsdkim</a><span class="HOEnZb"><font color="#888888"><br><br><div><br></div></font></span></blockquote><div><br></div><div>Ok, but that system requires our domain to be trusted by Google. Since we're currently rate limited, I don't think we're in a position to ask for this trust.... To me it seems like it's better to generate mails which have validating DKIM signatures by stopping to rewrite subject and body.</div><div><br></div><div>However, it seems like something we'll need to announce. Bringing it up here so people get a chance to react to that. Also, if others have experience to the contrary, it'd of course be great to hear that this isn't a solution, if it isn't.... (Mark's remark that we can't modify the body either seems like a remark to that extent.)</div><div><br></div><div><br></div></div>-- <br><div class="gmail_signature"><div dir="ltr">Bye,<div><br></div><div>Erik.</div><div><br></div><div><a href="http://efficito.com/" target="_blank">http://efficito.com</a> -- Hosted accounting and ERP.</div><div>Robust and Flexible. No vendor lock-in.</div></div></div>
</div></div>