"Private archives" aren't private
Hello,
#129 says that private lists are visible in the archive overview only but "archives aren't displayed".
However, I can browse a private list's archives and read the mail text while not logged in. Shouldn't the private archive be hidden from anonymous users?
Simon
On 06/03/2017 11:50 PM, Simon Liebold via Mailman-users wrote:
Hello,
#129 says that private lists are visible in the archive overview only but "archives aren't displayed".
However, I can browse a private list's archives and read the mail text while not logged in. Shouldn't the private archive be hidden from anonymous users?
Simon
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Where are you seeing this behaviour?
What version of Hyperkitty are you using?
Can you check what is stored in the database of Hyperkitty?
python manage.py shell
from hyperkitty.models.mailinglist import MailingList
MailingList.objects.all().values_list('name', 'archive_policy')
If the value for your list is 1 then we have a problem. 2 is for public archives and 0 should never be archived.
It's possible that you changed the archive_policy of a list and the change wasn't reflected in Hyperkitty.
For such a possibly sensitive issue, you should open a hidden issue in Gitlab ;-)
Am 04.06.2017 um 15:55 schrieb Simon Hanna:
Where are you seeing this behaviour?
In my test archive: https://lists.simonliebold.de/hyperkitty/list/simsimmer@lists.simonliebold.d...
What version of Hyperkitty are you using?
Master, commit 4c5eaead.
Can you check what is stored in the database of Hyperkitty?
python manage.py shell from hyperkitty.models.mailinglist import MailingList MailingList.objects.all().values_list('name', 'archive_policy')If the value for your list is 1 then we have a problem. 2 is for public archives and 0 should never be archived.
OK, no problem there:
It's possible that you changed the archive_policy of a list and the change wasn't reflected in Hyperkitty.
Postorius is showing the list's settings as "Private archives" (see screenshot). But apparently this setting doesn't do anything when switching it to "public" and back to "private". It always returns '2L'. Don't know if this is expected.
Postorius is on 52c9c3a5.
For such a possibly sensitive issue, you should open a hidden issue in Gitlab ;-)
The issue is probably my setup.
Simon
On 06/04/2017 07:47 AM, Simon Liebold via Mailman-users wrote:
OK, no problem there:
It's possible that you changed the archive_policy of a list and the change wasn't reflected in Hyperkitty.
Postorius is showing the list's settings as "Private archives" (see screenshot). But apparently this setting doesn't do anything when switching it to "public" and back to "private". It always returns '2L'. Don't know if this is expected.
Just to be sure, if you are just repeating the
MailingList.objects.all().values_list('name', 'archive_policy')
command, you won't be seeing the current value. You have to do either
abort()
or
commit()
to flush the previously retrieved data.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
It's possible that you changed the archive_policy of a list and the change wasn't reflected in Hyperkitty. Postorius is showing the list's settings as "Private archives" (see screenshot). But apparently this setting doesn't do anything when switching it to "public" and back to "private". It always returns '2L'. Don't know if this is expected. Looks like you want to run the Hyperkitty management command "mailman_sync" You could also just grab the MailingList object you want and run "mlist_object.update_from_mailman()" on it.
I couldn't get the command to run, will investigate later...
On Jun 04, 2017, at 05:30 PM, Simon Hanna wrote:
Looks like you want to run the Hyperkitty management command "mailman_sync"
https://gitlab.com/mailman/mailman/issues/329
This idea extends the internal event system into something that can trigger commands externally. Kind of like the reverse of the REST API, i.e. webhooks.
I've targeted this issue to Mailman 3.2.
-Barry
Am 04.06.2017 um 17:30 schrieb Simon Hanna:
Looks like you want to run the Hyperkitty management command "mailman_sync" You could also just grab the MailingList object you want and run "mlist_object.update_from_mailman()" on it.
I couldn't get the command to run, will investigate later...
I am getting errors as well:
mailman-suite/mailman-suite_project$ python manage.py mailman_sync
Traceback (most recent call last):
File "manage.py", line 10, in <module>
execute_from_command_line(sys.argv)
File
"/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 363, in execute_from_command_line
utility.execute()
File
"/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 355, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 205, in fetch_command
klass = load_command_class(app_name, subcommand)
File
"/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 40, in load_command_class
module = import_module('%s.management.commands.%s' % (app_name,
name))
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
import_module
__import__(name)
File
"/opt/mailman/hyperkitty/hyperkitty/management/commands/mailman_sync.py",
line 35, in <module>
class Command(BaseCommand):
File
"/opt/mailman/hyperkitty/hyperkitty/management/commands/mailman_sync.py",
line 37, in Command
option_list = BaseCommand.option_list + (
AttributeError: type object 'BaseCommand' has no attribute 'option_list'
Hi,
I'm having the same problem: changes to the "Archive policy" settings in postorius are not reflected in hyperkitty. Trying to use mailman_sync to fix this gave me the same BaseCommand traceback as above, but "mlist_object.update_from_mailman()" works. So luckily we have a workaround, thanks. But I suspect that there's some misconfiguration or permission problem on our server that's blocking the automatic synchronisation from taking place. Any advice to resolving this would be appreciated. :)
Cheers,
Cyprian
On July 28, 2017 10:55:43 AM GMT+02:00, cyp@trojina.si wrote:
Hi,
I'm having the same problem: changes to the "Archive policy" settings in postorius are not reflected in hyperkitty. Trying to use mailman_sync to fix this gave me the same BaseCommand traceback as above, but "mlist_object.update_from_mailman()" works. So luckily we have a workaround, thanks. But I suspect that there's some misconfiguration or permission problem on our server that's blocking the automatic synchronisation from taking place. Any advice to resolving this would be appreciated. :) It's fixed in master, and just needs a release. https://gitlab.com/mailman/hyperkitty/issues/135 @abompard what's the policy on bug fix releases? If mailman 3 should get adopted, I guess pushing such fixes quickly shows people that even if they encounter bugs, they get fixed right away... Otherwise they would just wait for it to "mature"
cheers Simon
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
On Jul 29, 2017, at 01:33, Simon HANNA simon.hanna@serve-me.info wrote:
@abompard what's the policy on bug fix releases? If mailman 3 should get adopted, I guess pushing such fixes quickly shows people that even if they encounter bugs, they get fixed right away... Otherwise they would just wait for it to "mature"
Project-wise, the policy is that we coordinate major releases, which in this case means the second digit, much like with Python. So 3.0 and 3.1 were coordinated across all the relevant subproject.
Micro/patch releases can happen at any time for subprojects. So if we need to release a Core 3.1.1, we can do that at any time. Of course it means we have to be extremely diligent not to break compatibility. We unfortunately don’t have any good integration tests to enforce this though.
-Barry
settings in postorius are not reflected in hyperkitty.
That's not yet fixed, or is it?
Am 28.07.2017 um 10:55 schrieb cyp@trojina.si:
but "mlist_object.update_from_mailman()" works. So luckily we have a workaround, thanks.
I am unsure where/how to use this workaround. Can anyone explain how I get Hyperkitty to display (and archive for) new lists created via Postorius.
Simon
participants (6)
-
Barry Warsaw -
cyp＠trojina.si -
Mark Sapiro -
Simon HANNA -
Simon Hanna
-
Simon Liebold