mailman.git/cron/disabled, branch master The GNU Mailing List manager. https://git.neuromancer.sk/mailman.git/atom/cron/disabled?h=master 2006-05-13T02:49:48Z Move all cron scripts to the new Mailman.bin package layout and complete the 2006-05-13T02:49:48Z bwarsaw 2006-05-13T02:49:48Z urn:sha1:590b6ebb628babc60fe282d133391dee155434ca conversion to optparse style option parsing. Remove mailpasswds as password reminders will go away for MM2.2. - fixed misspelling of propagate in loginit.initialize call in cron/disabled. 2006-05-09T18:46:45Z msapiro 2006-05-09T18:46:45Z urn:sha1:a85372821451461a59dff62886438cebaea56b12 (should the cron scripts propagate log messages to stderr?) - updated scripts/* scripts to use new logging rather than stderr writes. - Fixes to further remove the old Syslog from bin and cron scripts. Note that 2006-04-24T03:55:29Z bwarsaw 2006-04-24T03:55:29Z urn:sha1:155748d1c28457ce49dd6f67df24cd01285438a4 I didn't update cron/mailpasswds because that is going away. cron/disabled and cron/gate_news are only minimally tested. - Instead of using the RotatingFileHandler for our logs, use our own ReopenableFileHandler, which only minimally derives from FileHandler and implements a reopen() method. I think it's generally better to leave file rotation to external tools such as logrotate. - Remove some Python 2.1 compatibility stuff. - Ignore .mo files in messages/vi/LC_MESSAGES back porting from 2.1.6 2005-08-28T05:47:08Z tkikuchi 2005-08-28T05:47:08Z urn:sha1:737468981aa2f191ce243b063418a3bc878b9832 FSF office has moved. chdcking in for MAIN branch. 2005-08-27T01:54:05Z tkikuchi 2005-08-27T01:54:05Z urn:sha1:2a6084d03b96f87af153b663cf3dd4776e7e37fb main(): If we get NotAMemberError when sending the next notification, 2003-08-18T02:56:07Z bwarsaw 2003-08-18T02:56:07Z urn:sha1:aa36f578e9146afba2504db07770538817927919 log this and delete the member. Jon Parise's patch to improve the usage() output for the command line 2002-10-21T22:36:58Z bwarsaw 2002-10-21T22:36:58Z urn:sha1:17da8273eb61687e1eb7c1e068613036fc1f3f46 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 have 2002-08-09T21:32:20Z bwarsaw 2002-08-09T21:32:20Z urn:sha1:8457f099c3a43d5edb572fe9e4e3ccff04633a20 already been notified within the bounce_you_are_disabled_warnings_interval. Add options to also send disabled notifications for users who have 2002-05-28T03:12:41Z bwarsaw 2002-05-28T03:12:41Z urn:sha1:9f00a6babbe6b751da15296a546ef9382a607fca 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 make 2002-05-09T15:06:13Z bwarsaw 2002-05-09T15:06:13Z urn:sha1:ae7ca842a8768ccc4da17d82218f2bc1e698169f this change.