On 1/3/19 2:34 PM, Abhilash Raj wrote:
On Thu, Jan 3, 2019, at 2:27 PM, firstname.lastname@example.org wrote:
So who manages Postorius? Is that a whole separate application from Mailman 3? Is there a way we can get whoever the developer is to update it where we can separate lists by domain the way Hyperkitty does? Mark Sapiro refers to this in the following post:
You can file an issue at https://gitlab.com/mailman/postorius/issues
Yes, filing a GitLab issue is the best way to get things on the record. It's no guarantee that things will be addressed immediately, but they are there, and merge/pull requests are always welcome.
As far as your question goes, Mailman Core, Postorius and HyperKitty are separate entities and they were mostly developed by separate people/groups and some important players have either overtly or implicitly retired from the project.
Not long ago I write in another context
MM3 is much more complex than MM2.1 and there's a lot that I don't fully understand myself.
There is a basic core engine which does all the work of creating/managing lists and users and receiving and sending mail. It has no web UI per se. It exposes a RESTful API on the host server.
The web management UI is Postorius and it is based on the Django web framework and communicates with core via the REST API. The Archiver is HyperKitty and it is fairly independent. It is also based on the Django web framework. Account creation and web login is via django-allauth.
Postorius, HyperKitty and the core were all developed separately by different people and no one understands all of it.
That said, Abhilash is currently the lead developer for all of Mailman 3 and he's doing a great job. I and a few others are also involved (I'd be more involved if I didn't have Mailman 2.1 to distract me), but we are a small group and things take time.
And as I said, merge/pull requests for GitLab issues are always welcome.