On 4/11/23 09:36, Andreas Schamanek wrote:
I have a working full installation of mailman3, postorius and hyperkitty (on Debian 11). Now I wanted to host the archive of a remote list, and I am wondering how to do this properly.
After I found no documentation and no posting I simply created a list in mailman3 with only 1 dummy member. The list address is subscribed to the actual remote list. So, messages arrive and are archived. But that's not optimal because hyperkitty thinks it's a normal list where it should be read-only and do not allow subscriptions etc.
What's the proper way to set up a hyperkitty-only list?
There really isn't one as HyperKitty is intended to archive Mailman lists, however, it is possible to have a list in HyperKitty without a corresponding Mailman list. Thus, in your case you could just remove the Mailman 3 list you created and leave the HyperKitty list.
Then you have an issue with posts, so you can keep sending the posts to be archived to the prior list address, but arrange for the incoming MTA to pipe mail to that address to a process. That process would do the following.
Add a Unix From_ line at the beginning of the message and write the result to a temp file.
Invoke a command like
django-admin hyperkitty_import --no-sync-mailman --since 1990-01-01
-l list@example.com /path/to/the/tempfile
where list@example.com is the actual HyperKitty list.
This will archive the message. The addition of a Unix From_ line is to make the message file look like a mbox.
Since there is no Mailman list, attempts to post or reply directly from HyperKitty will fail, although such attempts using email software will probably succeed in archiving the mail, and mail directly to that list address will be archived, but such messages won't go to the remote list.
This may not be any better than what you're currently doing.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan