On Tue, Mar 03, 2009 at 05:30:10PM -0800, Mark Sapiro wrote:
Alan Rubin wrote:
Just curious if the community has a Standard Operating Procedure for
list administrators to notify list owners when there are changes to the
Mailman installation. Maybe like a list of list owners?
Other people may have other ideas. I'm not aware of any Best Current
Practice for this, but what I would do is use bin/list_owners to get
an unduplicated list of all the owners and mail to that list (as To:
or Bcc: recipients). You can use the '-m' option to include moderators.
I tend to daily/hourly cron "list_owners > /etc/mail/mailman-owners"
and have an exim alias generated from that, e.g.,
If I wanted to always include some other addresses (e.g, my RT queue,
my sysadmin's list, my syschanges list), stash those addresses in a
file, and cat 'em in after list_owners has done its business: others may
combine their "always" alias and list_owners output to generate another
alias for mailing
list-change-notify: foo, baa, baz at example.com
list-change: list-change-notify, listowners
Typically, cron-generated (from scripts/database lookups) files *don't*
get included in my revision systems.
``The reasonable man adapts himself to the world: the unreasonable one
persists in trying to adapt the world to himself. Therefore all progress
depends on the unreasonable man.'' (George Bernard Shaw)