On Tue, May 12, 2015 at 3:09 PM Terry Reedy tjre...@udel.edu wrote:
Gmail dumps patch review email in my junk box. The problem seems to be
the spoofed From: header.
Received: from psf.upfronthosting.co.za ([2a01:4f8:131:2480::3])
by mx.google.com with ESMTP id
On Tue, 09 Jun 2015 21:41:23 -, Gregory P. Smith g...@krypto.org wrote:
I *believe* you can get this to happen today in a review if you add the
rep...@bugs.python.org email address to the code review as the issueX
in the subject line will make the tracker turn it into a bug comment.
On Fri, 22 May 2015 08:05:49 +0300, Antti Haapala an...@haapala.name wrote:
There's an issue about this at
http://psf.upfronthosting.co.za/roundup/meta/issue562
I believe the problem is not that of the SPF, but the fact that mail gets
sent using IPv6 from an address that has neither a name
There's an issue about this at
http://psf.upfronthosting.co.za/roundup/meta/issue562
I believe the problem is not that of the SPF, but the fact that mail gets
sent using IPv6 from an address that has neither a name mapping to it nor a
reverse pointer from IP address to name in DNS. See the
SPF only covers the envelope sender, so it should be possible to set
that to something that validates with SPF, keep the RFC822 From: header
as it is, and maybe(?) include a separate Sender: header matching the
envelope address.
David
On Tue, May 12, 2015 at 06:08:30PM -0400, Terry Reedy wrote:
On 12May2015 22:15, David Wilson dw+python-...@hmmz.org wrote:
SPF only covers the envelope sender, so it should be possible to set
that to something that validates with SPF, keep the RFC822 From: header
as it is, and maybe(?) include a separate Sender: header matching the
envelope address.
On Wed, May 13, 2015 at 8:15 AM, David Wilson dw+python-...@hmmz.org wrote:
SPF only covers the envelope sender, so it should be possible to set
that to something that validates with SPF, keep the RFC822 From: header
as it is, and maybe(?) include a separate Sender: header matching the
