On 3/12/20 4:56 PM, Quanah Gibson-Mount wrote:

What permissions do I need to access Django?  I made myself a server owner from the python console, but that didn't do it.

I believe you have to be a superuser which is created as part of the installation of mailman-core, postorius, and hyperkitty. Please see:

https://docs.mailman3.org/en/latest/config-web.html

-- Please let me know if you need further assistance.

Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com

-- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase

EMWD's Community Forums http://discourse.emwd.com/

The Django Admin Interface is better, but it also does not give a full picture of a member, as it does not show the lists that member is a member of. MM2 had that feature, which was very useful. When I heard of MM3 supporting ‘users’ as opposed to ’subscribers’, I was expecting an interface that was ‘user’ centered, both at the user level and at the admin level. As a site admin I don’t have a way to get a comprehensive view of a user account (attached email addresses, subscribed lists, etc.).

Yours,

Allan Hansen hansen@rc.org

On Mar 13, 2020, at 8:50 , Quanah Gibson-Mount <quanah@symas.com> wrote:

--On Friday, March 13, 2020 9:41 AM -0700 Abhilash Raj <maxking@asynchronous.in> wrote:

...

dump_json is a documentation helper method which doesn't do much except calling the URL and dumping the returned json in a pretty-printed fashion.

https://mailman.readthedocs.io/en/latest/src/mailman/docs/documentation.h tml

The point is more that the documentation at this URL:

<https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/usermanager....>

makes repeated use of the dump_list function, and while it shows you a variety of bits to import, it doesn't include the bits necessary to make use of dump_list, so if one is going off the documentation, all they get is errors.

But really, the documentation needs to be updated further to point out the the Django ADMIN INTERFACE as the best way to do user management, and not the python shell.

--Quanah

--

Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

---

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/

You log on to the member’s account using the admin password. Then one of the options is to list all the accounts.

I think that the site admin (in own account) and a member (ditto) should be able to do this easily in the Postorious interface. I had expected that.

Yours,

Allan Hansen hansen@rc.org

On Mar 13, 2020, at 11:26 , Brian Carpenter <brian_carpenter@emwd.com> wrote:

On 3/13/20 1:02 PM, Allan Hansen wrote:

...

The Django Admin Interface is better, but it also does not give a full picture of a member, as it does not show the lists that member is a member of. MM2 had that feature, which was very useful. When I heard of MM3 supporting ‘users’ as opposed to ’subscribers’, I was expecting an interface that was ‘user’ centered, both at the user level and at the admin level. As a site admin I don’t have a way to get a comprehensive view of a user account (attached email addresses, subscribed lists, etc.).

Hi Allan,

What feature in MM2 allowed the function to see what lists a member was subscribed to? For some reason my mind is coming up empty.

Your above comments is something we will be considering seriously as we continue to develop Affinity.

-- Please let me know if you need further assistance.

Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com

-- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase

EMWD's Community Forums http://discourse.emwd.com/

---

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/

On 3/14/20 5:03 AM, Stephen J. Turnbull wrote:

The bundled administrative interface*is* Postorius. The Mailman shell is basically a quick hack (sorry Abhilash; if you want to call it a masterwork and say the speed of development is testimony to your skills, I won't deny it;-) to give more convenient access to internals to experienced Mailman hackers. More administrative features is something we plan to work on, but the Mailman project will focus on Postorius for the forseeable future.

I do think List Admins would want an interface to help "manage" a user account on behalf of a user then what is currently available in Postorius. I see this come up with my Mailman 2 clients frequently. For instance, a mm2 list member asked their list admin to subscribe them to a list topic to limit the amount of messages they receive. The list admin was new and open up a ticket to find out how they do that in which I replied showing them how they as a list admin, can go in and change options on behalf of a list member. I don't see this functionality built into Mailman 3 nowhere near the extent that Mailman 2 has.

Last night a Mailman 3 client wanted to know how they can add a real name to a list member. I said you can't, not as list admin. I directed them to instead of unsubscribe the member and mass subscribe them so they can include a real name along with the email address of the list member.

For alternatives to Postorius and the Mailman shell, Brian Carpenter (follow Allan's subthread) is working on a new management UI (using PHP), and I believe there's a working node.js API "out there somewhere". Please be very considerate of Brian's time; he and EMWD constitute a bulwark of the Mailman ecosystem and will be even busier with the UI project. But do pass on your suggestions to him as well as to us, he's indicated he's open to that.

There were some very good suggestions that were brought out in this thread and I had already passed them on to my developer. My approach with Affinity is definite leaning very heavy on the needs of list admins atm.

-- Please let me know if you need further assistance.

Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com

-- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase

EMWD's Community Forums http://discourse.emwd.com/

--On Saturday, March 14, 2020 7:03 PM +0900 "Stephen J. Turnbull" <turnbull.stephen.fw@u.tsukuba.ac.jp> wrote:

For alternatives to Postorius and the Mailman shell, Brian Carpenter (follow Allan's subthread) is working on a new management UI (using PHP), and I believe there's a working node.js API "out there somewhere". Please be very considerate of Brian's time; he and EMWD constitute a bulwark of the Mailman ecosystem and will be even busier with the UI project. But do pass on your suggestions to him as well as to us, he's indicated he's open to that.

Thanks Steve,

Generally I just found the mailman shell examples in the documentation lacking, as:

• it used functions not available without loading additional modules not listed in the documentation

• the steps to find accounts is lacking, since they don't work for email addresses that are not yet verified

• I could find no documentation on what fields are available in the user object, so I was unable to find the account via other methods, including the actual username created by mailman3 (which seems odd, wouldn't this be a standard way to find users..?)

The Django UI is the only thing that let me find the miscreated user and delete it.

Hopefully the bug I filed about github user integration being badly broken will receive some priority, given the bug causes new accounts to incorrectly be created for existing users.

--Quanah

--

Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>