If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Bugzilla excludes sending me email when I ask it to cc me




17 years ago
3 years ago


(Reporter: gnu, Assigned: justdave)





17 years ago
"Bug 69955 posted

 Email sent to: st.n@gmx.net, dave@intrec.com, jake@acutex.net,
 tara@tequilarista.org, matty@box.net.au Excluding:
 gnu@mozilla-bug.toad.com (change your preferences if you wish not to be

I wish to get email copies of my bugs.  It reports that it's excluding me,
and that I can change this in my preferences.  Well, it IS excluding me,
it isn't sending me an email copy of my bugs report.  I have to write
myself a separate email elsewhere, so I can remember the bug numbers.

Second, I clicked the link for "change your preferences", and it has no
"Stop excluding me from email" setting.  The first setting it had was
the closest to that (I can't go back and get to that link or the ****
browser will erase all this text I'm typing to you, so this is from memory).
But that setting was already set, by default, to appear to not exclude me.

What I think should be done:

  *  If the user asks to be cc'd, SEND THEM EMAIL when the bug is first filed!
CC them on the message that goes to the maintainers...

  *  Don't tell people they can click a link to Change their Preferences
about something that there is no actual preference to change.  Either
change the wording where the link is (to describe the actual preference
setting that you need to alter) or change the wording in the preferences
page to make it clear how to get it to stop excluding you from email.


	John Gilmore

PS:  Oho!  I tried defeating this Exclusion stuff by entering a second email
address that works for me (gnu@mozilla-bug-2.toad.com) into the "Cc" field.
Committing now tells me that this "CC" field is an invalid email address --
is a lie -- because that email address hasn't registered with Bugzilla.
Come on!  It should be possible to CC anybody in the **** world on a
**** bug report, there is no need to get them to come and register at
Bugzilla.  This is getting as bad as all the *%*&%&$& commercial "register
so we can track you and sell your info" sites.  The email system knows
how to get email to any address, you don't need to assign them a password
and a database entry for them to receive *^&^&$% email.

Comment 1

17 years ago
There is a preference to change what e-mail you get.  It's on the e-mail
settings page and the options are:
All qualifying bug except those which I change   <- The one you have
Only those bugs which are listed on the CC line
All qualifying bugs                              <- The one you want

These setting have been reworked for the soon-to-be-realeased version 2.12.  I
don't remember off the top of my head what the new defaults are, but it is more
obvious if you're being excluded from changes you make (a checkbox near the top
of the page).

As for CC'ing ppl w/out bugzilla accounts, it seems like i remember seeing that
one discussed and decided against (too high of a SPAM factor and too much schema
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
FYI, see bug 17464 (which is already fixed and checked in) for the email 
notification preferences.  They've been completely redesigned and the preference 
is much more obvious now.  Bugzilla.mozilla.org will be using the new email 
preferences system the next time they update to the tip.
verif. worksforme
moving to Bugzilla product
reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE
Assignee: tara → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa

Comment 5

3 years ago
Hello friends,

Please help me i have one doubt related to Bugzilla.if i added user in cc list (It showing excluding )
but i am not getting any mail ..so please help me ASAP

Comment 6

3 years ago
shrasti: Please ask on http://www.bugzilla.org/support/ instead. Bugzilla is the wrong place.
You need to log in before you can comment on or make changes to this bug.