SOP for notifying list owners
Hello,
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?
Regards,
Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 5111 Fax: +61 (08) 8999 7493 e-Mail: alan.rubin@nt.gov.au
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.
If this is a 'large' list, you could easily make a Mailman list and pipe the output of bin/list_owners into bin/sync_members to keep the list current.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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., "listowners :include:/etc/mail/mailman-owners"
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 (e.g.: list-change-notify: foo, baa, baz@example.com listowners: :include:/etc/mail/mailman-owners 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)
On 3/3/2009 7:30 PM, Mark Sapiro wrote:
If this is a 'large' list, you could easily make a Mailman list and pipe the output of bin/list_owners into bin/sync_members to keep the list current.
Might this be an idea for a ""virtual (dynamic) list that is a list of all the list owners? Say something for a future version of Mailman?
Grant. . . .
participants (4)
-
Adam McGreggor -
Alan Rubin -
Grant Taylor -
Mark Sapiro