Hi Mailman Developers, While exploring the codebase and the project ideas further, I also became very interested in the Log Access from the Web UI project idea, and I have some questions.
>From what I can see, Mailman Core writes logs using Python’s logging framework >to files under the configured "log_dir" (typically something like >/var/log/mailman). Since some log messages reference the list FQDN, it seems >that log entries might be scoped for list owners or domain admins by filtering >entries that mention their lists or domains. Should the UI aim to support something like real-time log viewing (similar to tail -f), or is the expectation that administrators would primarily browse recent log entries (e.g. the last N lines or paginated logs)? While thinking about the design, I realized that in some deployments Postorius and Mailman Core may not share the same host or filesystem. Is that a deployment pattern that is commonly seen with Mailman installations? Because of that, I wanted to ask about the intended architectural direction for this feature. Should the initial implementation assume that Postorius can read Mailman log files directly from the filesystem, or would it be preferable for log access to eventually be exposed through Mailman Core itself (for example via the REST API)? I’m also trying to understand the expectations around filtering. Since Mailman logs are not structured and may contain information unrelated to the list being viewed, is the expectation that log scoping will rely primarily on parsing the log text, or is there interest in introducing more explicit identification of lists/domains in log records (for example through structured logging) over time? Another point I was wondering about is the scope of logs this feature should expose. The project description mentions that site admins may want to access information from the MTA or web server as well. Should the initial implementation focus only on Mailman’s own logs, or is there interest in supporting other system logs in the UI as well? Finally, while reviewing the project ideas, I also noticed the Domain Administration project. If the log access project is considered significantly more complex or architecture heavy, would working on the Domain Administration feature be a more suitable project for GSoC? Best regards, Tanmay (pecpo) _______________________________________________ Mailman-Developers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
