[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

Nick Coghlan added the comment: I've migrated this issue over to the new meta-tracker at https://github.com/python/bugs.python.org/issues/10 This is one of several problems with the existing bugs.python.org infrastructure that are leading to it being rehosted elsewhere, and I've tagged the

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

Julien Palard added the comment: Protonmail is now displaying me a huge red banner on b.p.o emails: > email has failed its domain's authentication requirements. It may be spoofed > or improperly forwarded! Adding an SPF entry should be enough, if not going full SPF+DKIM+DMARC. SPF entry ca

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

Tim Tisdall added the comment: Your comment got emailed to me with no DMARC fail, so that's good. But adding a policy would be good. On 11 July 2016 at 16:37, Коренберг Марк wrote: > > Коренберг Марк added the comment: > > Still no progress? you just required to add SPF-recrod to DNS > > --

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

Коренберг Марк added the comment: Still no progress? you just required to add SPF-recrod to DNS -- nosy: +socketpair ___ PSF Meta Tracker

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

Tim Tisdall added the comment: Here's some headers from a recent email sent to me: 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; Authentication-R

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

Skip Montanaro added the comment: FWIW, I have no such problems with bug tracker emails, for this or any other Python-related bug tracker. Gmail seems to always classify them as "ham". -- nosy: +montanaro ___ PSF Meta Tracker

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

Antti Haapala added the comment: The above is true for new comments/bugs as well - they end up in spam: Received-SPF: none (google.com: roundup-ad...@psf.upfronthosting.co.za does not designate permitted sender hosts) client-ip=2a01:4f8:131:2480::3; Except there is 1 more peculiarity which

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

Antti Haapala added the comment: The new comments on the Python bug tracker also go to spam. I investigated the mail further, and there are *several* issues there. First: "Use the same address in the 'From:' header on every bulk mail you send." - the mail I received from meta tracker registrati

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

Robert Fleming added the comment: In reference to my previous comment: "new comment" e-mails from this tracker (psf.upfronthosting.co.za) are *not* being marked as spam. ___ PSF Meta Tracker

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

Robert Fleming added the comment: Gmail is also categorizing non-registration e-mails as spam. Specifically when a new comment is added to a Python bug, Google marks the generated e-mail as spam. (Doing my part to unmark the spam flag...) -- nosy: +fleminra __

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

R David Murray added the comment: Mail is consistently sent from rep...@bugs.python.org, always from the same IP address, 46.4.197.70. 46.4.197.70 resolves to bugs.python.org. So, we are meeting the requirements set forth in the article you link. I've asked about adding SPF records, which I

[Tracker-discuss] [issue562] Gmail (google) marks registration email as spam

New submission from C. P. Burns: Gmail (google) marks registration emails as spam. This occurred when registering for both and . Gmail indicated they were marked as spam because "It is in violation of Google's recommended email sender g