On 11/9/24 06:52, Odhiambo Washington via Mailman-users wrote:

I looked at Django Admin and Postorius and I see all my MLs in both.

What you see in Django admin is in the HYPERKITTY section and corresponds to hyperkitty_* tables in the mailmanweb database.

What I am sure about is that I did NOT create my MLs using Django admin UI. I either created them using the CLI or Postorius. Having said that, I did run two tests:

1. Create a ML in Postorius and check whether it appears in Django admin - The list was visible in Django Admin

Because the list you created had the hyperkitty archiver enabled.

2. Create a ML in Django admin and check whether it appears in Postorius - The list was NOT visible in Postrorius

Because it's only in HyperKitty.

3. Create a ML in CLI and check if it appears in both Django admin and Postorius - List is visible in Postorius, but not in Django admin

Becayse this list did not have the hyperkitty archiver enabled.

MariaDB [mailmansuite]> select list_name, list_id from mailinglist where
list_name like 'ulf%';
+-----------+-------------------------------+
| list_name | list_id                       |
+-----------+-------------------------------+
| ulftest2  | ulftest2.lists.kictanet.or.ke |
| ulftest3  | ulftest3.lists.kictanet.or.ke |
+-----------+-------------------------------+

These are only Mailman lists.

The list that I created using Django admin is NOT listed here!

Because it's only in HyperKitty.

MariaDB [mailmansuite]> select list_id, name from hyperkitty_mailinglist
  where list_id like 'ulf%';
+-------------------------------+-------------------------------+
| list_id                       | name                          |
+-------------------------------+-------------------------------+
| ulftest1@lists.kictanet.or.ke | ulftest1@lists.kictanet.or.ke |
| ulftest2.lists.kictanet.or.ke | ulftest2@lists.kictanet.or.ke |
+-------------------------------+-------------------------------+

The list I created using Django admin and the one I created using Postorius are both listed, but the one I created from CLI is not listed.

Because for some reason, the CLI created list does not create the HyperKitty archive until there is a post or until the new_lists_from_mailman job runs even though hyperkitty is enabled.

So there must be some logic behind this. However, I don't know what it is.

The bottom line is you can have lists in HyperKitty that are not in Mailman and vice versa. The only thing you can't do is create a list in HyperKitty via the HyperKitty web UI, but you can use hyperkitty_import to import a mbox for a list which is not in Mailman and will be only in HyperKitty.

Also, while you can create a list in Mailman that isn't in HyperKitty, if the list has hyperkitty enabled it will be created in HyperKitty when the new_lists_from_mailman job runs.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Mark Sapiro wrote:

Lists, not Mailman lists. When you create a list in Postorius or Mailman core, this is a Mailman list. A corresponding HyperKitty list will also be created if hyperkitty is one of the active archivers for the list so you see it in Django. When you create a list in Django, it is only a HyperKitty list and will be visible in HyperKitty, but no Mailman list is created so the list is not in Mailman/Postorius. Thank you (also for Odhiambo) Now remains one question: We have a (internal) Active Directory (AD) Authentication for Mailman3. So everyone who wants to work as an owner nor moderator must be an AD-User. In hyperkitty I am able to assign these list rights directly to AD-Loginnames. With the logic above I have to assign these rights in postorius too by assining the mail address of the users AD-Account? (I see no AD-Data here). Or would it works to assing the mail address of the users AD-Account first an then the allocation will automaticly synced to hyperkitty - maybe using the mail address as key? What would be the best practice for owner/moderator user management? Thank you!

On Mon, Nov 11, 2024 at 3:17 PM Ulf R. <ulf.rapphahn@offis.de> wrote:

Thank you (also for Odhiambo) Now remains one question: We have a (internal) Active Directory (AD) Authentication for Mailman3. So everyone who wants to work as an owner nor moderator must be an AD-User. In hyperkitty I am able to assign these list rights directly to AD-Loginnames. With the logic above I have to assign these rights in postorius too by assining the mail address of the users AD-Account? (I see no AD-Data here). Or would it works to assing the mail address of the users AD-Account first an then the allocation will automaticly synced to hyperkitty - maybe using the mail address as key? What would be the best practice for owner/moderator user management? Thank you!

Hi,

TBH, I am clueless about MM3 integration with LDAP/AD. Google leads me to a feature request: https://gitlab.com/mailman/django-mailman3/-/issues/27 But the Devs have the final say on the available possibilities.

-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]