Active archivers and archiving and thread question.
Digging into the mailman3 world, and want to check my logic...
We normally don't use archives, so I have "archive policy" set to "Do not archive this list" for our lists. However, the "archives" button is still there on the list info page, and if users go into it, they don't see anything, But they can click "start a new thread" which sends a message to the list, but since archiving is turned off, that message does not show up there. Am I understanding that correctly?
if I have "Active archivers" disabled, that hides that area from the users, correct?
Any reason why these are separated? why have an active archiver, if archiving is turned off -OR- archives are turned on, but no active archiver?
On 3/30/22 11:21, bob B via Mailman-users wrote:
Digging into the mailman3 world, and want to check my logic...
We normally don't use archives, so I have "archive policy" set to "Do not archive this list" for our lists. However, the "archives" button is still there on the list info page, and if users go into it, they don't see anything, But they can click "start a new thread" which sends a message to the list, but since archiving is turned off, that message does not show up there. Am I understanding that correctly?
if I have "Active archivers" disabled, that hides that area from the users, correct?
You need to have hyperkitty unchecked in Active archivers to prevent the Archive button from appearing on the info page. Archive policy = Do not archive this list will prevent HyperKitty from creating an archive for that list. If there is one at, e.g., https://example.com/archives/list/list@example.com/ you can delete it and Archive policy = Do not archive this list will keep it from being recreated.
Any reason why these are separated? why have an active archiver, if archiving is turned off -OR- archives are turned on, but no active archiver?
They probably shouldn't be completely independent. If Archive policy = Do not archive this list, that should probably deactivate any Active archivers for the list, but arguably, one might want to temporarily stop archiving and then restart it without having to remember which archivers were active.
At a minimum, setting Archive policy = Do not archive this list should probably remove the Archive button from the info page.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks, that make sense, Also is there any way to turn that off via command line for a bunch of lists or just in the GUi, I looked at "'mailman shell --details:" but could not find a command to turn it off.
I had archives off on my lists in mailman 2, and when I import they stayed off, but the archiver is enabled.
I have a script that pulls all the list configs
"curl --user *******:******* http://127.0.0.1:##/3.1/lists/"$i"/config | python3 -m json.tool >> ${OUTPUT_DATA_DIR}/listconfigs.txt
Then I look to see if any list has changed this setting "archive_policy": "never", so I know if any list admin has enabled archives...
But is there a setting in the config that shows if the archiver got turned on? I want to know if anyone turns it on after I turn it off
On 3/31/22 04:39, bob B via Mailman-users wrote:
Thanks, that make sense, Also is there any way to turn that off via command line for a bunch of lists or just in the GUi, I looked at "'mailman shell --details:" but could not find a command to turn it off.
I had archives off on my lists in mailman 2, and when I import they stayed off, but the archiver is enabled.
The HyperKitty and Prototype archivers are enabled by default for new and imported lists. To change that, add
[archiver.hyperkitty]
enable: no
[archiver.prototype]
enable: no
to mailman.cfg.
I have a script that pulls all the list configs "curl --user *******:******* http://127.0.0.1:##/3.1/lists/"$i"/config | python3 -m json.tool >> ${OUTPUT_DATA_DIR}/listconfigs.txt
Then I look to see if any list has changed this setting "archive_policy": "never", so I know if any list admin has enabled archives...
But is there a setting in the config that shows if the archiver got turned on? I want to know if anyone turns it on after I turn it off
You can do the following in mailman shell
$ mm/bin/mailman shell
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.
>>>for mlist in getUtility(IListManager):
... print(mlist.display_name)
... print(f' ArchivePolicy was {mlist.archive_policy}')
... if mlist.archive_policy != ArchivePolicy.never:
... mlist.archive_policy = ArchivePolicy.never
... print(' set to ArchivePolicy.never')
... aset = IListArchiverSet(mlist)
... for ar in aset.archivers:
... if ar.is_enabled:
... ar.is_enabled = False
... print(f' Archiver {ar.name} was enabled; set disabled')
...
>>> commit()
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
bob B
-
Mark Sapiro