provide filtered log access via web

[Yaseppochi]

... and queuefile summary data, too!
Suggested interface: new toplevel menu item for a
TROUBLESHOOTING page. The page would contain query
boxes for (a) logfiles and (b) queue summaries.
The LOG QUERY would have a checkbox (not radio button)
interface listing the available logs. Filters would
include (a) timestamp range (b) general Python regexp
at least.
The QUEUE QUERY would have a checkbox listing the
queues. Rather than have filters (at least at first)
the QUEUE QUERY might just provide age distributions,
say < 1 hour, < 5 hours, < 1 day, > 1 day for each
requested queue.
I'm of two minds as to whether an interface to access
data about individual messages would be useful. The
thing is, generally to do anything useful about the
queues you need shell and privileged access to the host.
It might be useful to have a MiniFAQ on this page that
just points to the MFAQs on the FAQWizard.

[http://sourceforge.net/tracker/index.php?func=detail&aid=1192175&group_id=103&atid=350103]

[Yaseppochi (yaseppochi)]

As pointed out by Brad Knowles, Mailman can't unilaterally
provide access to MTA queues. That will depend on the
privileges the host gives to the list admins. It would be
useful on the troubleshooting page to point to FAQs that
help the list admins provide the MTA admins with the info
they need to troubleshoot problems on the MTA side. For
newbie list+MTA admins, pointers to the MTA mailing lists.

[Mark Sapiro (msapiro)]

How would access to the TROUBLESHOOTING page be controlled?
I can see many (most?, all?) hosting providers not wanting
to allow e.g. a list admin to access even Mailman logs since
these logs contain entries for the entire site. Some logs
but not all can be filtered by list so possibly just a list
password could be used to access list specific entries, but
in general, I think we might need a new sitewide
TROUBLESHOOTING page password.