On Sun, Oct 16, 2016 at 12:32 PM, Greg Stark <stark@mit.edu> wrote:
On Sun, Oct 16, 2016 at 8:29 PM, Justin Clift <justin@postgresql.org> wrote: > On 16 Oct 2016, at 19:28, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> >> I've been tinkering with setting up SPF-based filtering on my mail >> server, and I was surprised to find out that most of the traffic >> it would want to throw away is Postgres mailing list messages. > > As an extra data point, the lack of SPF and DKIM for postgresql.org > is a bit of a pain when using @postgresql.org email address too. :(
I understand how SPF affects @postgresql.org addresses but I was under the impression that it was no help for mailing list traffic since it's being relayed so the ip address isn't going to match the records for the sending domain anyways. For relayed traffic you need the verify the DKIM signature (which is why it's important that the list not modify the content).
Yes, these are very different problems. DKIM is definitely causing issues with the lists at this point, and we're working on a solution for that.
SPF is a different beast. We have SPF set up for most of our non-postgresql.org domains, but we've been hesitant to touch the actual postgresql.org domain until we have separate out the list namespaces. It *should* be safe, but we just haven't wanted to touch it until we were certain. At least that's my recollection of it, Stefan might have more details.