Should Mailman provide periodic activity summaries to list owners?
A quick search didn't find anything, so I'll do a more careful check and if there's nothing I'll add a tracker RFE and a short wiki page of the imagined feature, probably on Monday. Unfortunately, I can't volunteer to implement at this time.
Details:
I noticed that we've been getting a lot of posts from users who are being quite diligent about following up on their own issues, to the extent of their knowledge and accesses, but for one reason or another are not using the logs.
Would it be desirable and feasible to send a periodic (options: daily, weekly, monthly, never) activity summary to list owners (similar to the tracker summaries that many trackers send to associated mailing lists)?
If someone's list is having problems, then they could get access via the admin interface, which would simply wrap the text report which would be generated for mailing in an HTML PRE element, making for trivial implementation (once the report itself is implemented, of course).
Something like
Week of May 17-23, 2009
44 incoming messages processed (42 posts, 2 other)
1 message automatically discarded 2 messages held (1 non-member, 1 spam filter) of which 2 messages were approved 41 messages distributed to members 2 weekly digests produced (maximum size reached 1 time(s)) 20 SMTP errors occurred of which 18 posts handled normally by bounce processing 2 subscription requests (probable backscatter)
Abstract of discarded messages
From: hormel@163.com To: resident@whitehouse.gov Subject: We cannot transfer $1 million to you without account information Message-ID: abc@fbi.cia.nsa
Abstract of held messages not configured.
Abstract of SMTP errors not configured.
There's already a script, "mmdsr" knocking about that does this. There's a version at http://www.opensource.apple.com/source/mailman/mailman-126.1/mailman/contrib..., but I'm not sure whether it's the latest version
--On 22 May 2009 13:27:35 +0900 "Stephen J. Turnbull" stephen@xemacs.org wrote:
A quick search didn't find anything, so I'll do a more careful check and if there's nothing I'll add a tracker RFE and a short wiki page of the imagined feature, probably on Monday. Unfortunately, I can't volunteer to implement at this time.
Details:
I noticed that we've been getting a lot of posts from users who are being quite diligent about following up on their own issues, to the extent of their knowledge and accesses, but for one reason or another are not using the logs.
Would it be desirable and feasible to send a periodic (options: daily, weekly, monthly, never) activity summary to list owners (similar to the tracker summaries that many trackers send to associated mailing lists)?
If someone's list is having problems, then they could get access via the admin interface, which would simply wrap the text report which would be generated for mailing in an HTML PRE element, making for trivial implementation (once the report itself is implemented, of course).
Something like
Week of May 17-23, 2009
44 incoming messages processed (42 posts, 2 other)
1 message automatically discarded 2 messages held (1 non-member, 1 spam filter) of which 2 messages were approved 41 messages distributed to members 2 weekly digests produced (maximum size reached 1 time(s)) 20 SMTP errors occurred of which 18 posts handled normally by bounce processing 2 subscription requests (probable backscatter)
Abstract of discarded messages
From: hormel@163.com To: resident@whitehouse.gov Subject: We cannot transfer $1 million to you without account information Message-ID: abc@fbi.cia.nsa
Abstract of held messages not configured.
Abstract of SMTP errors not configured.
Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/iane%40sussex.a c.uk
Security Policy: http://wiki.list.org/x/QIA9
-- Ian Eiloart IT Services, University of Sussex 01273-873148 x3148 For new support requests, see http://www.sussex.ac.uk/its/help/
Ian Eiloart writes:
There's already a script, "mmdsr" knocking about that does this. There's a version at http://www.opensource.apple.com/source/mailman/mailman-126.1/mailman/contrib...,
Sure, but that script requires being mailman in a shell on the host. The people I'm worried about mostly don't have those privileges, and for debugging an urgent problem you'd want it available on-demand.
Stephen J. Turnbullwrote:
Ian Eiloart writes:
There's already a script, "mmdsr" knocking about that does this. There's a version at http://www.opensource.apple.com/source/mailman/mailman-126.1/mailman/contrib...,
The latest version can be found at http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/files/head%3A/contri....
Sure, but that script requires being mailman in a shell on the host. The people I'm worried about mostly don't have those privileges, and for debugging an urgent problem you'd want it available on-demand.
I don't think it would be too difficult to refactor mmdsr as a python script that could be run on demand through a CGI or to run it via cron as it is currently designed and cache the output to be served by a CGI.
The real issue is that mmdsr is a global report. Stephen appears to be thinking more of a list specific report for list owners.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, May 22, 2009 at 07:16:20AM -0700, Mark Sapiro wrote:
The real issue is that mmdsr is a global report. Stephen appears to be thinking more of a list specific report for list owners.
My mailman stats script accepts an arguement, which if specified will run for that arguement, assuming it to be a listname; if no arguement (or 'ALL', it runs through the whole lot)
It's something I cobbled together in bash; but doesn't seem to be in my public code repo at the mo.
-- "The lamps are going out all over Europe; we shall not see them lit again in our lifetime." (Attrib. Edward Grey, 1914)
On Fri, May 22, 2009 at 01:27:35PM +0900, Stephen J. Turnbull wrote:
Would it be desirable and feasible to send a periodic (options: daily, weekly, monthly, never) activity summary to list owners (similar to the tracker summaries that many trackers send to associated mailing lists)?
There's also the bounce-analysis branch I have on Launchpad, which adds the message-ID to Mailman's internal logs in various places and adds a bounce-stats script that correlates the Mailman and Postfix logs to produce some statistics.
It would be better if Mailman tracked these statistics internally, but my employer needed the feature in Mailman 2.1 and I didn't want to make our Mailman branch diverge even further.
--amk
On May 25, 2009, at 9:22 PM, A.M. Kuchling wrote:
On Fri, May 22, 2009 at 01:27:35PM +0900, Stephen J. Turnbull wrote:
Would it be desirable and feasible to send a periodic (options:
daily, weekly, monthly, never) activity summary to list owners (similar to the tracker summaries that many trackers send to associated mailing lists)?There's also the bounce-analysis branch I have on Launchpad, which adds the message-ID to Mailman's internal logs in various places and adds a bounce-stats script that correlates the Mailman and Postfix logs to produce some statistics.
When Andrew told me about this, I thought it was such a good idea, I
fixed MM3's log writing call sites to do the same. :)
-Barry
On May 22, 2009, at 12:27 AM, Stephen J. Turnbull wrote:
Would it be desirable and feasible to send a periodic (options: daily, weekly, monthly, never) activity summary to list owners (similar to the tracker summaries that many trackers send to associated mailing lists)?
If someone's list is having problems, then they could get access via the admin interface, which would simply wrap the text report which would be generated for mailing in an HTML PRE element, making for trivial implementation (once the report itself is implemented, of course).
My plan is to collect this information in Mailman 3, making it
available via the web ui and admin REST interface. Adding an email
reporting infrastructure would not be difficult, once the basic
information is being collected. We write much of this to the log
files (with more consistent formatting in MM3), but I'd also like to
write it to a database table. That last bit isn't implemented yet.
-Barry
participants (6)
-
A.M. Kuchling -
Adam McGreggor -
Barry Warsaw -
Ian Eiloart -
Mark Sapiro -
Stephen J. Turnbull