| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
already been notified within the bounce_you_are_disabled_warnings_interval.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
this change.
|
| |
|
|
| |
setBounceInfo() call must be made with the list lock acquired.
|
| |
|
|
| |
It's totally useless to us.
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
|
|
re-enable reminders when they're due.
|