From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <stark(at)mit(dot)edu> |
Cc: | Justin Clift <justin(at)postgresql(dot)org>, PostgreSQL www <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: No SPF record for postgresql.org? |
Date: | 2016-10-16 19:52:19 |
Message-ID: | 25430.1476647539@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Greg Stark <stark(at)mit(dot)edu> writes:
> 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.
No, I think you're confusing it with DKIM. SPF checks to see whether
the sending machine is an authorized IP address for the domain of the
envelope FROM address --- which'd be the list itself. For example,
the whine I'm getting about this message is
Received-SPF: none (sss.pgh.pa.us: domain of postgresql.org does not provide an SPF record) client-ip=217.196.149.56; envelope-from=sss(dot)pgh(dot)pa(dot)us(at)postgresql(dot)org; helo=malur.postgresql.org;
The original sender having been stark(at)mit(dot)edu doesn't enter into it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-10-16 19:54:28 | Re: No SPF record for postgresql.org? |
Previous Message | Magnus Hagander | 2016-10-16 19:39:09 | Re: No SPF record for postgresql.org? |