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: > 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 > m1si26039166wjy.52.2015.05.12.00.20.38 > for <tjre...@udel.edu>; > Tue, 12 May 2015 00:20:38 -0700 (PDT) > Received-SPF: softfail (google.com: domain of transitioning > storch...@gmail.com does not designate 2a01:4f8:131:2480::3 as permitted > sender) client-ip=2a01:4f8:131:2480::3; > > Tracker reviews are the only false positives in my junk list. Otherwise, I > might stop reviewing. Verizon does not even deliver mail that fails its junk > test, so I would not be surprised if there are people who simply do not get > emailed reviews. > > Tracker posts are sent from Person Name <rep...@bugs.python.org> > Perhaps reviews could come 'from' Person Name <rev...@bugs.python.org> > > Even direct tracker posts just get a neutral score. > Received-SPF: neutral (google.com: 2a01:4f8:131:2480::3 is neither permitted > nor denied by best guess record for domain of > roundup-ad...@psf.upfronthosting.co.za) client-ip=2a01:4f8:131:2480::3; > > SPF is Sender Policy Framework > https://en.wikipedia.org/wiki/Sender_Policy_Framework > > Checkins mail, for instance, gets an SPF 'pass' because python.org > designates mail.python.org as a permitted sender. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
