Closed Bug 245075 Opened 20 years ago Closed 20 years ago

Need a command-line script to send unsent bugmail

Categories

(Bugzilla :: Email Notifications, defect)

2.17.7
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 2.18

People

(Reporter: justdave, Assigned: justdave)

Details

Attachments

(4 files)

There is a fair bit of evidence that we're still losing bugmail somewhere...
Until those situations are resolved, we still need a command line program to
send it that can be run from cron on a regular basis.  We used to do this with
"processmail rescanall", but processmail went away, and that job is now done
from the web with sanitycheck.cgi.

We have a script we've been using for this at bugzilla.mozilla.org.  We need to
make sure it gets included with Bugzilla.
Attached file sendunsentbugmail.pl
Here's the script we've been using at b.m.o.
Flags: blocking2.18+
Target Milestone: --- → Bugzilla 2.18
Flags: documentation?
Flags: documentation2.18?
RCS file: /cvsroot/mozilla/webtools/bugzilla/contrib/sendunsentbugmail.pl,v
done
Checking in sendunsentbugmail.pl;
/cvsroot/mozilla/webtools/bugzilla/contrib/sendunsentbugmail.pl,v  <-- 
sendunsentbugmail.pl
initial revision: 1.1
done
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
and on the 2.18 branch:

Checking in sendunsentbugmail.pl;
/cvsroot/mozilla/webtools/bugzilla/contrib/sendunsentbugmail.pl,v  <-- 
sendunsentbugmail.pl
new revision: 1.1.2.1; previous revision: 1.1
done
* New section on sendunsentbugmail.pl
* Changed the comment that the rest of the files in Contrib hadn't been updated
since before 2.16 from a sentence to a WARNING, so people would be less likely
to miss it.
* Re-formatted the rest of the patches.xml file to make it congruent with the
formatting we're trying to work towards in the rest of the docs.
Attachment #166016 - Flags: review?(documentation)
Comment on attachment 166016 [details] [diff] [review]
Doc changes for 2.18 and tip

I'm not sure if we should use "USAGE" capitalized. Maybe
<emphasis>Usage</emphasis> or something like that.

Otherwise looks good.
Attachment #166016 - Flags: review?(documentation) → review+
Checking in docs/xml/patches.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/patches.xml,v  <--  patches.xml
new revision: 1.18; previous revision: 1.17
done

Checking in docs/xml/patches.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/patches.xml,v  <--  patches.xml
new revision: 1.17.2.1; previous revision: 1.17
done
Flags: documentation?
Flags: documentation2.18?
Flags: documentation2.18+
Flags: documentation+
The checkin caused the tree to break. I'll commit this to fix it.
Checking in docs/xml/patches.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/patches.xml,v  <--  patches.xml
new revision: 1.20; previous revision: 1.19
done

Checking in docs/xml/patches.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/patches.xml,v  <--  patches.xml
new revision: 1.17.2.3; previous revision: 1.17.2.2
done
Tree is still burning after the fix. Commiting this second fix:

Checking in docs/xml/patches.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/patches.xml,v  <--	patches.xml
new revision: 1.21; previous revision: 1.20
done

Checking in docs/xml/patches.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/patches.xml,v  <--	patches.xml
new revision: 1.17.2.4; previous revision: 1.17.2.3
done
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: