<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">G'day Paul,<br>
<br>
I've had SPF records for the domain for a while. Google state in
their guide for bulk senders that they require DKIM as well as
SPF.<br>
<br>
It should also be noted SPF would also break in the scenario.<br>
<br>
Cheers,<br>
<br>
Adrian<br>
<br>
On 24/04/13 23:28, Paul Dean wrote:<br>
</div>
<blockquote cite="mid:20130424232838.2d58f734@slab3.inthecave.ws"
type="cite">
<pre wrap="">Hi Adrian,
Have you considered spf?
<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Sender_Policy_Framework">http://en.wikipedia.org/wiki/Sender_Policy_Framework</a>
Works well with postfix.
Google has a pref towards spf as their mail checking policies.
--
Thanks
Paul Dean.
"Life is not WHAT you make it, it's WHO you have in it..."
On Wed, 24 Apr 2013 18:29:58 +0800
Adrian Woodley <a class="moz-txt-link-rfc2396E" href="mailto:Adrian@Diskworld.com.au"><Adrian@Diskworld.com.au></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">G'day PLUG,
I run a small not-for-profit ISP (bfb.asn.au) for my volunteer fire brigade, which offers Internet services (namely DNS, email and web hosting) for other volunteer fire brigades. One of the popular services is mailing lists, which use mailman.
Recently gmail started bouncing mail from the server, which has prompted me to implement DKIM. This works really well for mail originating from bfb.asn.au and it's sub-domains, but I'm a little unsure about how I should handing the mailing list.
As far as I can tell, there are two options:
1) prevent mailman from modifying any of the DKIM signed headers. This would include the From, Reply-to and Subject headers, which would prevent the mailing list from easily identifying itself (rather than email being from the original sender).
2) remove all DKIM signing, re-write the From header to be from the mailing list and re-sign the email upon transmission. This would make it potentially more difficult to identify who sent the email originally.
Any thoughts on what the best practise is here?
Cheers,
Adrian
_______________________________________________
PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<a class="moz-txt-link-freetext" href="http://lists.plug.org.au/mailman/listinfo/plug">http://lists.plug.org.au/mailman/listinfo/plug</a>
Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.org.au">committee@plug.org.au</a>
PLUG Membership: <a class="moz-txt-link-freetext" href="http://www.plug.org.au/membership">http://www.plug.org.au/membership</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<a class="moz-txt-link-freetext" href="http://lists.plug.org.au/mailman/listinfo/plug">http://lists.plug.org.au/mailman/listinfo/plug</a>
Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.org.au">committee@plug.org.au</a>
PLUG Membership: <a class="moz-txt-link-freetext" href="http://www.plug.org.au/membership">http://www.plug.org.au/membership</a></pre>
</blockquote>
<br>
</body>
</html>