Code

Opened 3 years ago

Closed 2 years ago

Last modified 2 years ago

#16763 closed Bug (fixed)

code.djangoproject.com won't stop emailing me (doesn't abide by cc/reporter/etc)

Reported by: (removed) Owned by: nobody
Component: *.djangoproject.com Version:
Severity: Normal Keywords:
Cc: ferringb@… Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

As the summary says, I've long since moved on from django; this includes de-cc'ing myself basically every where I could find.

That said, code.djangoproject.com persists in emailing me. Examples being #17, #3544, #4102, #3529. Basically anywhere I've commented- I get notification. If I uploaded a patch, I get notification. If I cc'd myself, than de-cc'd myself, I get mail. Further kicker is the stupid thing is bound to my email address rather than my user account (hell if I know why), so it's not even picking up my account's email being set to noreply@… (yep, that's rude, but it's been pissing me off for a while now).

I'd be significantly less annoyed if it were just emailing me for tickets I've filed (bugzilla behaviour), but this is /not/ the behaviour I've observed; as said, check the tickets, none of them have me cc'd, couple of them the only thing I ever did was cc myself, than remove it later on.

Still I get mail. Kindly sort it or point out exactly how I'm being stupid and could suppress this myself (procmail wiping it on my side does not fly- I'd sooner set a forward than go that route).

Attachments (0)

Change History (28)

comment:1 follow-up: Changed 3 years ago by jpaulett

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

Does removing your email address from https://code.djangoproject.com/prefs help (I am guessing you probably have already done this)? Unfortunately, I don't have the permissions to dive into Trac to help investigate the issue more.

comment:2 in reply to: ↑ 1 Changed 3 years ago by (removed)

Replying to jpaulett:

Does removing your email address from https://code.djangoproject.com/prefs help (I am guessing you probably have already done this)? Unfortunately, I don't have the permissions to dive into Trac to help investigate the issue more.

Nope; if it did, noreply@… would be getting the mail ;)

Note I really don't think this is trac specific behaviour- possible I'm being crack-adled, but I do not recall seeing trac flagrantly ignore user prefs like this; also note this doesn't much look like your usual trac setup considering user prefs (which includes notification controls) are all buried/non-existant.

comment:3 Changed 3 years ago by aaugustin

  • Component changed from Uncategorized to Djangoproject.com Web site
  • Triage Stage changed from Unreviewed to Accepted

Yes, Trac sends an email for every ticket where you've been involved: added yourself in Cc, left a comment, etc. Indeed, that makes the Cc field useless for unsubscribing — you can only subscribe :)

I think that some contributors rely on this behavior. At least I do — my email filters put emails sent to django-updates in different mailboxes, depending on whether I've been involved on the ticket (e.g. I've left a comment) or not. So it would be best best to provide a way to disable it on a per-user basis.

I suspect there's a custom post-commit hook that sends the email to the address you used to sign up here: https://www.djangoproject.com/accounts/register/
Unfortunately, these configurations aren't available in a public repository; could a core developer confirm?

Apparently, there's no way to change or remove it: https://github.com/django/djangoproject.com/blob/master/django_website/accounts/urls.py
I think an opt-out feature should be added to the website, and the post-commit hook should be updated appropriately.

Version 0, edited 3 years ago by aaugustin (next)

comment:4 Changed 3 years ago by jezdez

I honestly can't find any Trac configuration setting helping for this, but that's the code retrieving the list of recipients:

http://trac.edgewall.org/browser/trunk/trac/ticket/notification.py?rev=10594#L324

So apparently trac stores the email addresses in the ticket database itself, if I understand correctly.

comment:5 Changed 3 years ago by jezdez

FWIW, right now we run Trac with always_notify_updater = true

comment:6 Changed 3 years ago by aaugustin

Yes, my hypothesis was wrong, this is controlled by the always_notify_updater parameter.

I can understand that it's annoying for people who have moved on but are still subscribed to some long standing tickets.

However, regular, active contributors are used to this behavior and rely on it, so I'm in favor of the status quo.


For the record, the same discussion happened in Trac's own Trac: http://trac.edgewall.org/ticket/4426 :)

comment:7 Changed 3 years ago by jacob

  • Resolution set to wontfix
  • Status changed from new to closed

ferringb, let me know what email you're receiving messages to (email it to me -- jacob at jacobian dot org -- if you don't want to post it here). I'll manually de-list it from everywhere it appears in Trac. Otherwise there isn't a lot we can do here: Trac doesn't have any sort of global "stop emailing me" feature. I'm really sorry!

comment:8 Changed 3 years ago by RaceCondition

As my similar issue was marked as dupe, please manually remove me from the CC of https://code.djangoproject.com/ticket/16950 as I'm having the same issue.

comment:9 Changed 3 years ago by anonymous

As for "there is no global stop emailing me feature"; there is, user preferences allow it but you need to have a sane server side configuration. Specifically turn always_notify_updater to false, and have people use CC like a sane tracker ;) . Worst case, use the always notify list functionality- could just point that at a mailing list and have people manage their subscription to it via usual mailman UI (basically a variation on commit lists). I rather strongly suggest either way you change the status quo- this auto-spamming means personally I'm rather disinclined to file any issues django wise unless it's intentionally using a crap/null account (which isn't particularly desirable).

Either way, enough lecturing; I'd definitely appreciate it if you prune the username ferringb for both gmail and gentoo.org.

G'luck in the future and such-

comment:10 Changed 3 years ago by anonymous

Sidenote, your captcha challenge also looks to be busted (and no, I'm not filing a bug since I don't want the spam); my last message it complained (oddly momentarily) was marked as spam by the bayesian filter, explicitly requesting I fill out a captcha interface... without providing a captcha. Just saying. ;)

comment:11 Changed 3 years ago by RaceCondition

Why am I getting updates about this issue even though now I'm not even in the CC list??

comment:12 Changed 3 years ago by RaceCondition

it seems that "Remove from CC" doesn't work at all anymore. Is there a solution to this? Effectively, code.djangoproject.com is sending out unwanted/spam emails.

comment:13 Changed 3 years ago by RaceCondition

  • Resolution wontfix deleted
  • Status changed from closed to reopened

comment:14 Changed 3 years ago by aaugustin

  • Resolution set to wontfix
  • Status changed from reopened to closed

The solution is in comment 7 above :)

comment:15 Changed 3 years ago by RaceCondition

Well, unfortunately, Jacob did not reply to my e-mail wherein I asked if it would be possible to remove my e-mail from all tickets.

Also, I don't think this should be a "wontfix" as it's probably just a line to comment out in Trac source code.

comment:16 Changed 2 years ago by jacob

Deleted a bunch of completely off-topic comments. I can manually remove your email from trac, and my personal address is upthread so please contact me there. Please send legal threats to foundation@djangoproject.com.

comment:17 Changed 2 years ago by adrian

Just now seeing this... I've just changed the Trac config to set "always_notify_updater = false". I agree this is/was lame behavior on the part of the ticketing system. People relying on the existing (broken) behavior should add themselves to the "cc" field for tickets they want to follow.

comment:18 Changed 2 years ago by adrian

  • Resolution wontfix deleted
  • Status changed from closed to reopened

comment:19 Changed 2 years ago by adrian

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:20 follow-up: Changed 2 years ago by kmtracey

So now everyone who has been working with this trac for years and gotten used to the behavior of its auto-notifying them of changes to tickets they have commented on has to be re-educated that in order to get updates to tickets they must add themselves to cc list? That seems more broken than the old behavior to me.

comment:21 in reply to: ↑ 20 Changed 2 years ago by ferringb

Replying to kmtracey:

So now everyone who has been working with this trac for years and gotten used to the behavior of its auto-notifying them of changes to tickets they have commented on has to be re-educated that in order to get updates to tickets they must add themselves to cc list? That seems more broken than the old behavior to me.

Not an answer you'll like, but frankly you'll get used to it and it's far more powerful having that setting off. Couple of years back I was fairly active with django- even then, the behaviour was proving worthless since (like all other sites) I was using CC's to track what I cared about- which could, and did change; simplest example, I cared fairly heavily about template engine speed, thus was tracking a lot of tickets for that. Switched to jinja, was happy, thus no longer cared about the templating tickets, nor wanted that email- yet it persisted in mailing, screwing up my signal/noise tracking of the project. That sort of behaviour for folks tracking multiple projects makes one rather disinclined to interact w/ djangos trac. As is, there are some things I still would be interested in tracking, but w/ the proceeding behaviour my option was only to just level a full on ban of all incoming django mail to suppress the noise (tracking a ticket or two wasn't worth the noise specifically).

CC being abided by gives you far more power than the broken previous behaviour, and like it or not, it /was/ spamming. Definitely well intentioned spam, but spam none the less. I realize it may be a pita in for the minority who were relying on it, but for everyone else (who used CC correctly, if in doubt look at people manipulating CC on tickets) it was an ongoing annoyance.

Either way, thank you Adrian for correcting the setting; also pardon the level of ass-hattery ultimately deployed trying to force people to abide by standards- unfortunately pissed off folks a fair bit more than was the intent.

comment:22 Changed 2 years ago by lukeplant

There is also the fact that I'm emailed personally about tickets where I've not commented at all, but simply done some trac-gardening, sometimes via the bulk modification plugin (like when we added some new fields a while back). I read django-updates anyway, but it goes into a different folder compared to tickets I really care about, so the current behaviour of Trac has meant the signal-to-noise for this feature has gone down for me. I think I can get used to adding myself to the CC field instead.

comment:23 Changed 2 years ago by julien

For what it's worth, I personally subscribe to the RSS feeds of the tickets I'm interested in instead of adding myself to the CC field. One advantage is that I can subscribe/unsubscribe without adding noise to the ticket and without notifying other CC'ed users. The RSS feed link is available at the bottom of each ticket, or simply by adding '?format=rss' to the ticket url.

comment:24 Changed 2 years ago by kmtracey

Please notice I did not say one way or the other which way I myself would prefer. I'm on the fence about that, since I too get a lot of non-auto-filtered emails as a result of making some trivial change to a ticket in which I really have not much interest. But we have a community of hundreds of people who have been used to how trac has auto-mailed them for the last several years, and we just turned that off with no notice, because of one very vocal and rude complainer. That seems wrong.

comment:25 Changed 2 years ago by aaugustin

I absolutely agree with Karen. Announcing the change to django-developers would mitigate the problem, wouldn't it?

comment:26 Changed 2 years ago by kmtracey

Better would be to get some feedback from the community on preferred behavior before making the change, or since that is too late, before making it "final".

comment:27 Changed 2 years ago by ferringb

Just a thought; If people are that concerned, send out notification of the change, collect the list of people who want notification for stuff they've touched /ever/, and adrian/jacob levels a bit of sql foo against the trac db to add those folks into the cc of the tickets they've touched. That's fairly easy to do.

Via that, people who're concerned about notifications get them; Note I strongly suggest an explicit opt-in- else you're going to generate a shit ton of cc modifications, followed up by people like me going through and pruning themselves from far too many bugs....

This just leaves the folk who were using the different routing pathway to do local sorting; not much really can be done there however.

comment:28 Changed 2 years ago by lukeplant

I don't think we should alter the CC fields. Rather, we should just send an email along the lines of "this is your last email from Django's Trac if you do nothing" to all people who might unexpectedly stop getting emails. To limit the number of people on this email, we can:

1) only include open tickets in our reckoning

2) only include people who haven't also explicitly added themselves to CC for all the tickets they've contributed to.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.