Separating Lists by Domain
I have successfully setup a second domain with my Mailman3 setup. I also created a list using the second domain. So I have two domains with one list each. The issue I see at this point is all of the lists are shown via Postorius regardless of the list domain used. Is it possible to have only the lists to show that are part of the domain being used to access? For example:
http://domaina.com/postorius/lists/
Only listnames@domaina.com show up.
http://domainb.com/postorius/lists/ Only listnames@domainb.com show up.
Right now both domaina AND domainb lists showup regardless of the domain being used to access Postorius. The same goes for Hyperkitty as well.
Brian
Am Mon, 24 Dec 2018 00:41:43 -0000 schrieb brian@emwd.com:
I have successfully setup a second domain with my Mailman3 setup. I also created a list using the second domain. So I have two domains with one list each. The issue I see at this point is all of the lists are shown via Postorius regardless of the list domain used. Is it possible to have only the lists to show that are part of the domain being used to access? For example:
http://domaina.com/postorius/lists/
Only listnames@domaina.com show up.
http://domainb.com/postorius/lists/ Only listnames@domainb.com show up.
Right now both domaina AND domainb lists showup regardless of the domain being used to access Postorius. The same goes for Hyperkitty as well.
Hi Brian, I once asked a similar question: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
Best regards,
Johannes
On Sun, Dec 23, 2018, at 4:42 PM, brian@emwd.com wrote:
I have successfully setup a second domain with my Mailman3 setup. I also created a list using the second domain. So I have two domains with one list each. The issue I see at this point is all of the lists are shown via Postorius regardless of the list domain used. Is it possible to have only the lists to show that are part of the domain being used to access? For example:
http://domaina.com/postorius/lists/
Only listnames@domaina.com show up.
http://domainb.com/postorius/lists/ Only listnames@domainb.com show up.
Right now both domaina AND domainb lists showup regardless of the domain being used to access Postorius. The same goes for Hyperkitty as well.
You can do that this in Hyperkitty. Setting
FILTER_VHOSTS = Truein Django's settings.py (or settings_local.py, if you are using container images) will filter the lists for the current "Host:" header in the request.
Postorius doesn't have this ability yet, but wouldn't be too much work to add that. Pull requests are welcome :)
Brian
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
You can do that this in Hyperkitty. Setting
FILTER_VHOSTS = Truein Django's settings.py (or settings_local.py, if you are using container images) will filter the lists for the current "Host:" header in the request.
Postorius doesn't have this ability yet, but wouldn't be too much work to add that. Pull requests are welcome :)
Thanks Maxking but that did not work. I added it to the settings_local.py file, restarted the container and the same behavior prevails.
Brian
Abhilash Raj wrote:
FILTER_VHOSTS = Truein Django's settings.py (or settings_local.py, if you are using container images) will filter the lists for the current "Host:" header in the request.
The above setting is incorrect. It should be:
FILTER_VHOST = True
Please see:
http://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyper...
Brian
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:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
Thanks, Brian
On Thu, Jan 3, 2019, at 2:27 PM, brian@emwd.com 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:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
You can file an issue at https://gitlab.com/mailman/postorius/issues
Thanks, Brian
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
On 1/3/19 2:34 PM, Abhilash Raj wrote:
On Thu, Jan 3, 2019, at 2:27 PM, brian@emwd.com 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:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
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.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Abhilash Raj writes:
Is there a way we can get [Postorius updated] where we can separate lists by domain the way Hyperkitty does? Mark Sapiro refers to this in the following post:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
You can file an issue at https://gitlab.com/mailman/postorius/issues
Is this feature GSoC-able, or too small?
Steve
On Thu, Jan 3, 2019, at 8:19 PM, Stephen J. Turnbull wrote:
Abhilash Raj writes:
Is there a way we can get [Postorius updated] where we can separate lists by domain the way Hyperkitty does? Mark Sapiro refers to this in the following post:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
You can file an issue at https://gitlab.com/mailman/postorius/issues
Is this feature GSoC-able, or too small?
It could be a good first issue for a GSoC applicant, too small to be the project itself.
Steve
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
Hi,
Is it possible to have only the lists to show that are part of the domain being used to access?
is there already a solution for this issue? No answers in the thread. On top of that another question: is it possible to add user accounts that can manage lists for one domain but not other domains?
(By looking at the Django models, I think this is not possible. But I might have missed something.)
Sven
On 5/1/20 9:59 AM, Sven Seeberg via Mailman-users wrote:
Is it possible to have only the lists to show that are part of the domain being used to access?
This is the setting
FILTER_VHOST = True.
It causes problems in Postorius and doesn't work well in HyperKitty. See <https://gitlab.com/mailman/postorius/-/issues/394> and <https://gitlab.com/mailman/hyperkitty/-/issues/254>. Both these issues are fixed for the next releases of Postorius and HyperKitty which should be out later this month.
On top of that another question: is it possible to add user accounts that can manage lists for one domain but not other domains?
We already have the concept of domain owner, but implementation of domain owner permissions is not yet done.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (6)
-
Abhilash Raj -
brian＠emwd.com -
Johannes Winter -
Mark Sapiro -
Stephen J. Turnbull -
Sven Seeberg