My list has been switched from public to private archives, but they are still visible
Can anyone help with this?
I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now)
https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogress...
Am I misunderstanding what a private archive is?
Is something wrong with my setup (which is hosted)?
Thank you.
Paul Arenson writes:
I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now)
Yes, I can see it, and the posts. I think there was a bug that you can see that private lists are present even if you are not a subscriber. However the posts themselves were private. This is not that bug, it's something else.
Am I misunderstanding what a private archive is?
No (except for the bug mentioned above, which probably will be fixed -- the logic is nontrivial, since admins need access to the list of lists, but maybe not private lists they're not owners of, even if they're not subscribers).
Is something wrong with my setup (which is hosted)?
Don't know yet. Some configuration changes require a server restart. I don't know offhand if this is one. It's worth a try if you can do that.
On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote:
Can anyone help with this?
I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now)
This change takes a bit of time to sync up Hyperkitty. THere is a daily cron job which syncs this information from Mailman Core.
I have made a change which should fix this problem and the process would become synchronous.
You can run python manage.py runjobs --daily command to force sync
that information.
https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogress...
Am I misunderstanding what a private archive is?
Not really, your expectation is right.
Is something wrong with my setup (which is hosted)?
Thank you.
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/
-- thanks, Abhilash Raj (maxking)
I am having a very similar issue. Here is what I have found:
There are basically three archive settings we can select via the postorious web front end for archives. These can be found in: Settings > Archiving and they are: Public archives Private archives Do not archive this list
In the Django administrative interface we can find those same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists > Mailing List object(x) > Archive policy: never private public
I’m not sure which of the two takes precedence. My guess is postorius since that is a list owner accessible setting and the Django administrative interface would typically not be accessible to list owners. We have noticed the following odd behavior, not sure if it is a bug. For existing lists with private archives, when switching to “Do not archive this list” in postorious, the desired effect of no longer archiving the list is instantaneous. However, after the daily cron job that syncs with Mailman Core happens, the existing archives now become publicly accessible. Is this behavior based on the assumption that the list will no longer be archived and will therefore be purged?
Enrique
On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking@asynchronous.in> wrote:
On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote:
Can anyone help with this?
I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now)
This change takes a bit of time to sync up Hyperkitty. THere is a daily cron job which syncs this information from Mailman Core.
I have made a change which should fix this problem and the process would become synchronous.
You can run
python manage.py runjobs --dailycommand to force sync that information.https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.tokyo...
Am I misunderstanding what a private archive is?
Not really, your expectation is right.
Is something wrong with my setup (which is hosted)?
Thank you.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote:
I am having a very similar issue. Here is what I have found:
There are basically three archive settings we can select via the postorious web front end for archives. These can be found in: Settings
Archiving and they are: Public archives Private archives Do not archive this list
This is interface of Mailman to set the archives.
Mailing List object(x) > Archive policy: never
In the Django administrative interface we can find those same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists private public
This is basically a hotline to the database. You can change these values, but they would be overriden with the values that are in Mailman Core on the daily cron job run.
I would suggest not to tinker with values there since you could leave database in a corrupted state. Since there is an ORM layer there, chances are less but still a possibility :)
I’m not sure which of the two takes precedence. My guess is postorius since that is a list owner accessible setting and the Django administrative interface would typically not be accessible to list owners. We have noticed the following odd behavior, not sure if it is a bug. For existing lists with private archives, when switching to “Do not archive this list” in postorious, the desired effect of no longer archiving the list is instantaneous. However, after the daily cron job that syncs with Mailman Core happens, the existing archives now become publicly accessible. Is this behavior based on the assumption that the list will no longer be archived and will therefore be purged?
Source of truth is Mailman Core's database. Postorius is a front-end to change that and owners have permissions to do that.
Hyperkitty only syncs back that information daily. I have a fix in the master which makes such that this information is synced synchronously and is available immediately to Hyperkitty.
For now, you could either run the "python manage.py runjobs --daily" or wait for a day if that is possible.
Enrique
On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking@asynchronous.in> wrote:
On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote:
Can anyone help with this?
I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now)
This change takes a bit of time to sync up Hyperkitty. THere is a daily cron job which syncs this information from Mailman Core.
I have made a change which should fix this problem and the process would become synchronous.
You can run
python manage.py runjobs --dailycommand to force sync that information.https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.tokyo...
Am I misunderstanding what a private archive is?
Not really, your expectation is right.
Is something wrong with my setup (which is hosted)?
Thank you.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
-- thanks, Abhilash Raj (maxking)
Thank you Abhilash, I appreciate your prompt response. What about the once private archives becoming public after setting a list to “Do not archive this list”? Regards, Enrique
On Sep 19, 2019, at 1:38 PM, Abhilash Raj <maxking@asynchronous.in<mailto:maxking@asynchronous.in>> wrote:
On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote: I am having a very similar issue. Here is what I have found:
There are basically three archive settings we can select via the postorious web front end for archives. These can be found in: Settings Archiving and they are: Public archives Private archives Do not archive this list
This is interface of Mailman to set the archives.
In the Django administrative interface we can find those same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists Mailing List object(x) > Archive policy: never private public
This is basically a hotline to the database. You can change these values, but they would be overriden with the values that are in Mailman Core on the daily cron job run.
I would suggest not to tinker with values there since you could leave database in a corrupted state. Since there is an ORM layer there, chances are less but still a possibility :)
I’m not sure which of the two takes precedence. My guess is postorius since that is a list owner accessible setting and the Django administrative interface would typically not be accessible to list owners. We have noticed the following odd behavior, not sure if it is a bug. For existing lists with private archives, when switching to “Do not archive this list” in postorious, the desired effect of no longer archiving the list is instantaneous. However, after the daily cron job that syncs with Mailman Core happens, the existing archives now become publicly accessible. Is this behavior based on the assumption that the list will no longer be archived and will therefore be purged?
Source of truth is Mailman Core's database. Postorius is a front-end to change that and owners have permissions to do that.
Hyperkitty only syncs back that information daily. I have a fix in the master which makes such that this information is synced synchronously and is available immediately to Hyperkitty.
For now, you could either run the "python manage.py runjobs --daily" or wait for a day if that is possible.
Enrique
On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking@asynchronous.in<mailto:maxking@asynchronous.in>> wrote:
On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: Can anyone help with this?
I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now)
This change takes a bit of time to sync up Hyperkitty. THere is a daily cron job which syncs this information from Mailman Core.
I have made a change which should fix this problem and the process would become synchronous.
You can run python manage.py runjobs --daily command to force sync
that information.
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.tokyo...
Am I misunderstanding what a private archive is?
Not really, your expectation is right.
Is something wrong with my setup (which is hosted)?
Thank you.
Mailman-users mailing list -- mailman-users@mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
On Thu, Sep 19, 2019, at 11:42 AM, Enrique Terrazas wrote:
Thank you Abhilash, I appreciate your prompt response. What about the once private archives becoming public after setting a list to “Do not archive this list”?
Is this something you are observing?
It is most definitely a bug, Hyperkitty should leave the archive in whatever previous state they were in before the "Do not archive this list" setting was added.
My suspicion is that when Do Not archive list setting is enforced, Hyperkitty sets the default visibility, which I think is Public.
Can you file a but at gitlab.com/mailman/hyperkitty/issues ?
Regards, Enrique
On Sep 19, 2019, at 1:38 PM, Abhilash Raj <maxking@asynchronous.in> wrote:
On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote:
I am having a very similar issue. Here is what I have found:
There are basically three archive settings we can select via the postorious web front end for archives. These can be found in: Settings
Archiving and they are: Public archives Private archives Do not archive this list
This is interface of Mailman to set the archives.
In the Django administrative interface we can find those same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists
Mailing List object(x) > Archive policy: never private public
This is basically a hotline to the database. You can change these values, but they would be overriden with the values that are in Mailman Core on the daily cron job run.
I would suggest not to tinker with values there since you could leave database in a corrupted state. Since there is an ORM layer there, chances are less but still a possibility :)
I’m not sure which of the two takes precedence. My guess is postorius since that is a list owner accessible setting and the Django administrative interface would typically not be accessible to list owners. We have noticed the following odd behavior, not sure if it is a bug. For existing lists with private archives, when switching to “Do not archive this list” in postorious, the desired effect of no longer archiving the list is instantaneous. However, after the daily cron job that syncs with Mailman Core happens, the existing archives now become publicly accessible. Is this behavior based on the assumption that the list will no longer be archived and will therefore be purged?
Source of truth is Mailman Core's database. Postorius is a front-end to change that and owners have permissions to do that.
Hyperkitty only syncs back that information daily. I have a fix in the master which makes such that this information is synced synchronously and is available immediately to Hyperkitty.
For now, you could either run the "python manage.py runjobs --daily" or wait for a day if that is possible.
Enrique
On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking@asynchronous.in> wrote:
On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote:
Can anyone help with this?
I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now)
This change takes a bit of time to sync up Hyperkitty. THere is a daily cron job which syncs this information from Mailman Core.
I have made a change which should fix this problem and the process would become synchronous.
You can run
python manage.py runjobs --dailycommand to force sync that information.https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.tokyo...
Am I misunderstanding what a private archive is?
Not really, your expectation is right.
Is something wrong with my setup (which is hosted)?
Thank you.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
-- thanks, Abhilash Raj (maxking)
Thanks Steve and Abhilash. Whatever you did worked even though I am on hosting run by Brian C. (Which is why I can’t run any python things or restart servers)
I just tried and it is working fine, which was a pleasant surprise.
So Mailman issues that you fix affect even self hosted and hosting service versions of the programs? If so, pretty cool.
Thanks, again.
Paul
On Thu, Sep 19, 2019, at 8:10 PM, Paul Arenson wrote:
Thanks Steve and Abhilash. Whatever you did worked even though I am on hosting run by Brian C. (Which is why I can’t run any python things or restart servers)
I just tried and it is working fine, which was a pleasant surprise.
It was just a daily cron job, which syncs the change in setting you just made one day ago. Wasn't really a bugfix.
So Mailman issues that you fix affect even self hosted and hosting service versions of the programs? If so, pretty cool.
Thanks, again.
Paul
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/
-- thanks, Abhilash Raj (maxking)
participantes (4)
-
Abhilash Raj -
Enrique Terrazas -
Paul Arenson -
Stephen J. Turnbull