Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )
Hi everyone,
one of our servers that was running a mailman2 instance just crashed this afternoon, so we decided to take the leap and migrate to 3, and I have to say it worked pretty well, the lists seem to be back.
What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list.
The lists are operated for a smallish university and all the professors need to be allowed to send to the students list, without being member of that list. That was possible with mailman2 by just whitelisting the university domain.
Also, in the past we allowed all members of the all-students list to post to any of the dorm-lists (this is mainly used for party announcements so it is not a must have), but I wanted to ask anyways, if there was a chance to allow this feature again.
According to the docs, the accept_these_nonmembers option exists (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/l...), but none of my lists have that set after the migration - the field is not even there when accessing the REST API.
Do I need to enable something? Has that feature been added just recently, and we are missing out (since we are using the apt packages from ubuntu)?
Thanks in advance, Patrick
On 9/8/21 3:39 PM, Patrick Brückner wrote:
Hi everyone,
one of our servers that was running a mailman2 instance just crashed this afternoon, so we decided to take the leap and migrate to 3, and I have to say it worked pretty well, the lists seem to be back.
What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list.
The lists are operated for a smallish university and all the professors need to be allowed to send to the students list, without being member of that list. That was possible with mailman2 by just whitelisting the university domain.
Also, in the past we allowed all members of the all-students list to post to any of the dorm-lists (this is mainly used for party announcements so it is not a must have), but I wanted to ask anyways, if there was a chance to allow this feature again.
According to the docs, the accept_these_nonmembers option exists (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/l...), but none of my lists have that set after the migration - the field is not even there when accessing the REST API.
Do I need to enable something? Has that feature been added just recently, and we are missing out (since we are using the apt packages from ubuntu)?
You are probably on an old version of Mailman which didn't expose the values in API and also Postorius didn't expose it in UI.
You can install a new version manually by downloading new debs from Debian unstable repos (I don't know if Ubuntu just copies the ones from Debian or has their own packaging, I think it is former) that have newer built debs.
On your version, you probably would be able to set the accept_these_nonmembers using the command line using
mailman withlist -l test@example.com
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
The variable 'm' is the test@example.com mailing list
>>> m.accept_these_nonmembers
['*.example.com']
>>> m.accept_these_nonmembers = [r'*.example.com']
>>> commit()
>>> quit()
-- thanks, Abhilash Raj (maxking)
On 9/8/21 3:39 PM, Patrick Brückner wrote:
What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list.
As Abhilash said, Mailman 3 accepts regexps in accept_these_nonmembers for whitelisting domains. Currently Mailman 3 does not support whitelisting the members of another list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Am 16.09.21 um 01:13 schrieb Mark Sapiro:
On 9/8/21 3:39 PM, Patrick Brückner wrote:
What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list.
As Abhilash said, Mailman 3 accepts regexps in accept_these_nonmembers for whitelisting domains. Currently Mailman 3 does not support whitelisting the members of another list.
Is this still true in the current version? I have been using this quite extensively with mailman2, so loosing it is the one major drawback of the migration.
Johannes
On 1/8/23 01:37, Johannes Rohr wrote:
Am 16.09.21 um 01:13 schrieb Mark Sapiro:
Currently Mailman 3 does not support whitelisting the members of another list.
Is this still true in the current version? I have been using this quite extensively with mailman2, so loosing it is the one major drawback of the migration.
Yes it is still true. This is https://gitlab.com/mailman/mailman/-/issues/794
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Am 09.01.23 um 06:30 schrieb Mark Sapiro:
On 1/8/23 01:37, Johannes Rohr wrote:
Am 16.09.21 um 01:13 schrieb Mark Sapiro:
Currently Mailman 3 does not support whitelisting the members of another list.
Is this still true in the current version? I have been using this quite extensively with mailman2, so loosing it is the one major drawback of the migration.
Yes it is still true. This is https://gitlab.com/mailman/mailman/-/issues/794
Thanks! I assume, there is a reason why this cannot be easily implemented, else it would have been. Asking because I know a number of people would make extensive use of this in MM2.
Johannes
On 1/9/23 05:31, Johannes Rohr wrote:
Thanks! I assume, there is a reason why this cannot be easily implemented, else it would have been. Asking because I know a number of people would make extensive use of this in MM2.
The actual implementation is probably not difficult, but it's more than
just handling things like @list_id in *_these_nonmembers. It also
requires developing appropriate unit tests, updating REST and mailman import21 to accept the syntax and documentation updates at least for
Postorius Settings -> Message Acceptance -> * these non-members. That
adds up to a significant amount of work.
I recognize it's a significant regression for some, but we are a small, all volunteer project and can't do everything. A well crafted merge request would certainly be accepted.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Am 10.01.23 um 00:53 schrieb Mark Sapiro:
I recognize it's a significant regression for some, but we are a small, all volunteer project and can't do everything. A well crafted merge request would certainly be accepted.
You are doing incredibly valuable work, and I sincerely apologize for being a total layman who just whines and doesn't have the skills to contribute any code!
I could only explore options for organising a bounty on this. But I have no idea what amount of funding would be required realistically, or I could start nagging other Mailman users who have python skills.
Cheers,
Johannes
participants (4)
-
Abhilash Raj -
Johannes Rohr -
Mark Sapiro -
Patrick Brückner