WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#9208 closed defect (bug) (invalid)

TRAC mail misconfigured by you

Reported by: jidanni Owned by: matt
Milestone: Priority: normal
Severity: normal Version:
Component: WordPress.org site Keywords:
Focuses: Cc:

Description

Please compare bugs #9183 and #9185.
I am the reporter on both.

For the former, I got email notification of other people's changes, for the
latter I got none.

The only difference is that the former was closed.

I conclude that you :-), have misconfigured TRAC.

If not, then please add me to the Cc on all of
http://core.trac.wordpress.org/query?reporter=jidanni

Change History (10)

comment:1 @DD326 years ago

  • Component changed from General to WordPress.org
  • Milestone 2.8 deleted
  • Owner changed from anonymous to matt

Feel free to add yourself as CC if you please, But don't expect someone else to d it for you.

Check your spam box, I've always gotten the emails, Some people however have complained that they dont get them in the past.

comment:2 @jidanni6 years ago

  • Cc jidanni@… added

Kindly check your logs to see that you ever sent it!

You will find that you didn't.

I'm sure that you keep mail logs.

Just check for this one bug.

You only sent a message that I created the bug, I already knew that!

But even in my spambox there is no message about your reply.

OK, I'll add myself to the CC: below.

But there are 57 other bugs that I am the reporter of.

Which would mean clicking till next Tuesday! So of course I'm feeling bad.

comment:3 @jidanni6 years ago

But some changes do get sent to me, like the one DD32 just made to #8927, even with no Cc.

So there is a fine line of what will trigger a mail and what won't... for those in charge to please explore.

comment:4 @mrmist6 years ago

Just subscribe to the trac mailing list. Then you get mostly everything.

comment:5 @westi6 years ago

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

Please read the Notification section on the front page.

"If you would like to receive notification when a ticket you have submitted or are interested in changes then please configure your email address in trac after you have logged in by going to the settings page.

If you then add your user name to the cc on a ticket you will be notified of changes on the ticket."

That does work.

comment:6 @Viper007Bond6 years ago

I can indeed confirm it works. I get e-mails about any changes to tickets I created or have left a comment on, and I've never CC'ed myself.

comment:7 @jidanni6 years ago

The boilerplate should also say what will happen if one doesn't also
click CC when submitting bugs: some mails will get sent, but others
not. As to which others, well, it would be nice if the administrator
could check the logs to see if e.g., each mail sent to the mailing
list also had a copy sent to the reporter, and exactly which types of
replies don't get sent.

comment:8 @jidanni6 years ago

Matt, in http://trac.edgewall.org/ticket/8094

TTP> Comment(by ebray):
TTP>  I suspect this is a configuration issue.  See TracIni#notification-section
TTP>  Do you have always_notify_reporter enabled?

All I know is I see it mentioned in
https://core.trac.wordpress.org/wiki/TracIni

always_notify_reporter 	 Always send notifications to any address in the reporter field 

see also
https://core.trac.wordpress.org/wiki/TracNotification
https://core.trac.wordpress.org/wiki/TracLogging

Maybe that is the key to the problem. However it doesn't explain the "sometimes yes, sometimes no" behavior.

comment:9 @westi6 years ago

  • Cc bazza added

I don't see why you raised a ticket on trac when as already explained here if you follow the instructions on the wiki it works fine for everyone else.

I have CC'd bazza to get him to look at this but AFAIK trac is configured fine.

comment:10 @jidanni6 years ago

Well, without being on the CC list, sometimes this Trac sends the reporter notifications, and sometimes not.

As a mere user, I can't tell what the factor is causing the difference.

Yes, a workaround is to always add oneself to the CC: list.

However it would be best to figure out what is causing it.

Note: See TracTickets for help on using tickets.