I have of course activated password login as it was not possible to get the
provider based logins to work (might be but not worth the time for me right
now). Is there any way for an user to request a new password when it is
I presume that the Persona login is removed now. I cannot hide it in my
version or at least I do not know how.
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:
Only listnames(a)domaina.com show up.
Only listnames(a)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.
Just a heads up for those wanting to install Mailman3 on a Centos 7 server, be aware of FirewallD. There are a number of ports and services you have to tell it to allow in order to get Mailman3 functional. More experienced sysadmins might know this but I did not.
Is it possible to customize the look at feel of the web interface at
all? I have some lists that really require that subscription requests
include full name, to make the workload on the moderators, well,
workable in keeping a closed list tight. I've found where the "Your
name (optional)" text is in list_forms.py, but modifying that strikes me
as a poor plan.
Changing that text would be lovely. Actually making that field required
would be seriously awesome.
Is this possible in the current code base (3.2.0) without doing
ill-advised things modifying source code?
Web Administrator, Alpha Psi Omega Grand Cast
etc... etc... etc...
Postorius is not currently exposing non-members management. Our Mailman 2 users are currently using accept_these_nonmembers, hold_these_nonmembers and reject_these_nonmembers. We know that mailman import21 will change these to nonmembers entries in Mailman 3. Since list owners will still want to manage them, we tend to move all of them to members and turn off delivery status for them.
However, we met some difficulties when we try to develop using mailman client.
1) If those non-members addresses already exist as members, we will encounter error when we subscribe for them: urllib.error.HTTPError: HTTP Error 409: b'Member already subscribed'
2) We cannot change the moderation_action: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: moderation_action'
3) We cannot change the preference: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: delivery_status'
Are there any better ways to enable the list owners to manage those previously configured nonmembers' addresses through the web? Otherwise, we probably need to have some manual effort to overcome the above three issues. We know that we can always do the above manually but we got a lot of lists to migrate to Mailman 3.