Title Email notifictations not received for rietveld review
Priority bug Status resolved
Superseder Nosy List abarnert, berker.peksag, dmalcolm, loewis, tshepang
Assigned To Topics

Created on 2012-03-14.00:08:20 by dmalcolm, last changed 2018-06-12.18:26:11 by berker.peksag.

msg2391 (view) Author: dmalcolm Date: 2012-03-14.00:08:20
dmalcolm isnt on the nosy of:
despite being on the nosy of
msg2426 (view) Author: loewis Date: 2012-04-02.16:07:26
That's not actually true: dmalcolm *is* in the CC list of (at PyCon, we checked the Reviewer's list, which is a separate list of users in Rietveld that (I think) are the ones who made reviews).

I created issue 14477 to further experiment.
msg2427 (view) Author: loewis Date: 2012-04-02.16:10:17
dmalcolm: can you please report whether you received the email from Rietveld, titled "Rietveld test issue (issue14477)" and posted a minute ago?
msg2428 (view) Author: dmalcolm Date: 2012-04-02.16:19:13
On Mon, 2012-04-02 at 16:10 +0000, Martin v. Löwis wrote:
> Martin v. Löwis <> added the comment:
> dmalcolm: can you please report whether you received the email from Rietveld, titled "Rietveld test issue (issue14477)" and posted a minute ago?

No: I did receive two emails from the *bug tracker* [1], both with
  "[issue14477] Rietveld test issue"
(the first signifying the issue was opened, the second with:
  "keywords: +patch
  Added file:"

However, I don't seem to have received an email from Rietveld: not with
the title you describe above.

[1] both have
From: =?utf-8?q?Martin_v=2E_L=C3=B6wis?= <>
but are Reply-To:Python tracker <>
msg3000 (view) Author: abarnert Date: 2016-02-02.02:22:27
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 <>" instead of "Developer Name <>", so it doesn't have this problem.
msg3486 (view) Author: berker.peksag Date: 2018-06-12.18:26:11
The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance.

Closing this issue.
Date User Action Args
2018-06-12 18:26:11berker.peksagsetstatus: chatting -> resolved
nosy: + berker.peksag
messages: + msg3486
2016-02-02 02:22:28abarnertsetnosy: + abarnert
messages: + msg3000
2012-04-02 16:19:13dmalcolmsetmessages: + msg2428
2012-04-02 16:10:17loewissetmessages: + msg2427
2012-04-02 16:07:26loewissetstatus: unread -> chatting
nosy: + loewis
messages: + msg2426
2012-03-14 20:46:19tshepangsetnosy: + tshepang
2012-03-14 00:08:20dmalcolmcreate