Bug#37078: bts procmail 2

2005-12-28 Thread Justin Pryzby
Included is a second-attempt procmail config file which also handles control bot messages. -- Clear skies, Justin # This handles initial submissions ("Thank you for the problem # report...") and also followups ("Thank you for the additional # information..."). :0 * ^From: [EMAIL PROTECTED] \(Debi

Bug#88722: marked as done (Bugs tagged Fix should not be listed as "Fixed in NMU")

2005-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2005 21:28:57 -0500 with message-id <[EMAIL PROTECTED]> and subject line Private Invite from Sara has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsib

Bug#86922: marked as done (Bugs tagged Fix should not be listed as "Fixed in NMU")

2005-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2005 21:28:57 -0500 with message-id <[EMAIL PROTECTED]> and subject line Private Invite from Sara has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsib

Bug#37078: procmail for bugsubscriptions

2005-12-28 Thread Justin Pryzby
I'm using the included procmail file for subscribing myself to all bugs for which I am the submitter, or on which I have commented. I see 4 problems: It is implemented on the clientside, and it would IMHO be better if debbugs implemented it (but that is known:). It doesn't track control