Andrew Barnert added the comment: I suspect this is caused by either #554, #553 and its various dups/associates, or (if it's not caused by one of those two) #562.
My money is on #554. Rietveld messages use the developer's address for From. That makes it look like a forged message. That means it's guaranteed to be bounced if the developer is on a DMARC=reject domain, and quarantined if the developer is on a DMARC=quarantine domain, and that it will probably be marked as spam if the developer is on any of the major (and therefore heavily-forged) public hosting domains. Everything else from Python's servers, including bug tracker nosy messages, uses "Developer Name <repo...@bugs.python.org>" instead of "Developer Name <develo...@developer.address.example.com>", so it doesn't have this problem. ---------- nosy: +abarnert _______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue439> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org https://mail.python.org/mailman/listinfo/tracker-discuss
