summaryrefslogtreecommitdiff
path: root/cron/disabled
Commit message (Collapse)AuthorAgeFilesLines
* Jon Parise's patch to improve the usage() output for the command linebwarsaw2002-10-211-2/+6
| | | | | | and cron scripts. When code/status == 0, there's no error (it's likely --help output) so send that to stdout. Otherwise, it's an error and the output goes to stderr.
* Added a -f / --force switch to force notifications to members who havebwarsaw2002-08-091-11/+18
| | | | already been notified within the bounce_you_are_disabled_warnings_interval.
* Add options to also send disabled notifications for users who havebwarsaw2002-05-281-43/+96
| | | | | | | | been disabled by themselves, the list owner, or for unknown (legacy) reasons. By default we only notify `bounce disabled' members, but you could now do notifications for any other reason. Also, fix the -l/--listname option parsing.
* Backing out the last two patches. This wasn't the right place to makebwarsaw2002-05-091-9/+2
| | | | this change.
* main(): Rework the resetting of a member's bounce info, since thebwarsaw2002-05-091-4/+6
| | | | setBounceInfo() call must be made with the list lock acquired.
* main(): If the member's bounce info is old-style, simply reset it.bwarsaw2002-05-071-0/+5
| | | | It's totally useless to us.
* Update copyright years.bwarsaw2002-03-161-1/+1
|
* main(): Add a sweep & cull step before sending disabled notifications.bwarsaw2002-01-291-1/+30
| | | | | | | Here, we're looking for members who are not yet disabled, but who have a bounce score >= the threshold. This can happen if the list owner lowers the threshold. There's no sense in waiting until another bounce is received on the member before we disable them.
* New cron script to search for disabled-by-bounce memberships and sendbwarsaw2001-12-271-0/+116
re-enable reminders when they're due.