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 don't *think* we currently publish, but per the linked doc, that shouldn't be *necessary* to satisfy google. We have a suspicion that they are marked as spam because spammers fake from addresses and send messages to the tracker, which automatically sends back the registration email (since it hasn't seen that email address before), and the from address recipient marks the message as spam...which information then makes its way into one or more pattern recognition databases. At this point I'm not sure there's much we can do about it, though I would be in favor of eliminating the auto-registration response (ie: generate a registration email only if registration is requested via the web interface, not implicitly via email). But I'm not at all sure that fixing that now would have any affect on whatever database it is that has the registration emails marked as "likely spam". If I'm right about the above, though, it means that google's bounce email is...well, lying is probably to strong a term, but misrepresenting, at least...the reason the email is being marked as spam. ---------- nosy: +r.david.murray status: unread -> chatting _______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue562> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org https://mail.python.org/mailman/listinfo/tracker-discuss
