[Trac] Re: filter own TRAC bug mail
Missing To: headers at the trac I used upped SpamAssassin's score so I didn't need up their threshold to filter. Still not a (SMTP) rule breaker ;-) I hope one day vanilla Trac will offer more than all or none email choices. Yeah, Trac definitely needs a re-write of the notification subsystem, there are many open tickets to address a lot of issues and requests for emails. -- Manu --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: filter own TRAC bug mail
Fortunately TRAC breaks other rules, like missing To: headers, so the above is all I need, at least for the WordPress TRAC. Trac does emit To: headers, it depends on the notification configuration. I agree that the notification documentation is weak and that notification features are too far limited, but I don't see how not emitting To: header can be considered as breaking a rule. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: filter own TRAC bug mail
To be fair, I often want trac to send me acknowledgements as I use email for organization (maybe not the best decision, but that's what I do). Though there's no reason the notification to be mandatory except as a policy decision. Jeff Hammel IRC: jhammel, k0s On Wed, Jan 21, 2009 at 02:51:56AM +0800, jida...@jidanni.org wrote: Gentlemen, the TRAC bug tracker is not as smart as bugzilla. It insists on sending one acknowledgements even for one's own actions. It was me doing the clicking, no acknowledgement needed. But if it was someone else changing/commenting on one of my bugs, well yes, I want mail about it. So to get mail on others' actions on our bugs, but not our own actions, we must make fancy SpamAssassin rules: header __J_TRAC_COMMENT X-Trac-Ticket-URL =~/\#comment/ rawbody __J_TRAC_MY_COMMENT /\+-+\nChanges \(by jidanni\):\n/ meta J_TRAC_OTHERS __J_TRAC_COMMENT !__J_TRAC_MY_COMMENT score J_TRAC_OTHERS -7 Fortunately TRAC breaks other rules, like missing To: headers, so the above is all I need, at least for the WordPress TRAC. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: filter own TRAC bug mail
On Jan 20, 12:51 pm, jida...@jidanni.org wrote: Gentlemen, the TRAC bug tracker is not as smart as bugzilla. It insists on sending one acknowledgements even for one's own actions. It was me doing the clicking, no acknowledgement needed. But if it was someone else changing/commenting on one of my bugs, well yes, I want mail about it. So to get mail on others' actions on our bugs, but not our own actions, we must make fancy SpamAssassin rules: header __J_TRAC_COMMENT X-Trac-Ticket-URL =~/\#comment/ rawbody __J_TRAC_MY_COMMENT /\+-+\nChanges \(by jidanni\):\n/ meta J_TRAC_OTHERS __J_TRAC_COMMENT !__J_TRAC_MY_COMMENT score J_TRAC_OTHERS -7 Fortunately TRAC breaks other rules, like missing To: headers, so the above is all I need, at least for the WordPress TRAC. Actually, it's significantly smarter/better than Bugzilla. Particularly out of the box. That said, your assumption that $USER who edits a ticket shouldn't get a notification is a personal preference, and by extension a flawed assumption. I personally expect to get an e-mail in this scenario. Enjoy Bugzilla, sounds like the tool of choice for you. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: filter own TRAC bug mail
Look at http://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin It works for us. Search this group for nevernotifyupdaterplugin and you will see two posts I made on 12/5/2008 with more details. On Jan 20, 5:02 pm, Jeff Hammel jham...@openplans.org wrote: To be fair, I often want trac to send me acknowledgements as I use email for organization (maybe not the best decision, but that's what I do). Though there's no reason the notification to be mandatory except as a policy decision. Jeff Hammel IRC: jhammel, k0s On Wed, Jan 21, 2009 at 02:51:56AM +0800, jida...@jidanni.org wrote: Gentlemen, the TRAC bug tracker is not as smart as bugzilla. It insists on sending one acknowledgements even for one's own actions. It was me doing the clicking, no acknowledgement needed. But if it was someone else changing/commenting on one of my bugs, well yes, I want mail about it. So to get mail on others' actions on our bugs, but not our own actions, we must make fancy SpamAssassin rules: header __J_TRAC_COMMENT X-Trac-Ticket-URL =~/\#comment/ rawbody __J_TRAC_MY_COMMENT /\+-+\nChanges \(by jidanni\):\n/ meta J_TRAC_OTHERS __J_TRAC_COMMENT !__J_TRAC_MY_COMMENT score J_TRAC_OTHERS -7 Fortunately TRAC breaks other rules, like missing To: headers, so the above is all I need, at least for the WordPress TRAC. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: filter own TRAC bug mail
I see, http://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin is something one must ask each trac maintainer to install, at each trac where we have reported bugs. I will rather just filter the mail myself with my SpamAssassin stanza version 2: header __J_TRAC_COMMENT X-Trac-Ticket-URL =~/\#comment/ rawbody __J_TRAC_MY_COMMENT /\+-+\n(Changes|Comment) \(by jidanni\):\n/m meta J_TRAC_OTHERS __J_TRAC_COMMENT ! __J_TRAC_MY_COMMENT score J_TRAC_OTHERS -7 Missing To: headers at the trac I used upped SpamAssassin's score so I didn't need up their threshold to filter. I hope one day vanilla Trac will offer more than all or none email choices. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
