Okay, I AM very stupid sometimes. The login problem was due to an commeted backend line for auth. Sorry for that.

Still annoying to hear that the mailman_bundle is deprecated.

Best regards // David

On Sat, Mar 25, 2017 at 8:13 PM, David Krantz <david@krantz.dk> wrote:

Hi.

I have tried and failed to set up mailman 3 using the mailman_bundle. I get the mailman3 server running correctly, but the problem is the extremely sensitive web user interface...

Now when I found this mail list I understand that mailman bundle is depricated and that I must restart from scratch. Is this true? This annoys me quite a lot, can someone responsible within the project please mark the deprecated package as such?

Almost none of the documentation is completely correct. It is useful but very incomplete. The mailman_bundle generated configuration examples for e.g. apache simply is wrong or incomplete. That said I got it running using http only, but when I switched to HTTPS the login simply ceased working. I use password+username as the other solution is quite complicated to get running. I could of course switch to e.g. google login, but that would require at least some documentation on how to do that. So, is there any documentation on how to use mailman 3?

The error I get now is "Please enter a correct username and password. Note that both fields may be case-sensitive." I know that I enter the correct password as it worked before I added HTTPS.

Sorry for the rant, but I am very annoyed by this. I just need a mail list server that works and thought it would be very neat to run mailman3 after running a hoste mailman2 for many years.

Best regards // David

On Sat, Mar 25, 2017 at 10:35 PM, Barry Warsaw <barry@list.org> wrote:

Yes, I'm sorry you went down a dead end with mailman-bundler. I'm trying to purge the world of it so others won't get led astray. I've clobbered the README in the GitLab repo and we may at some point just archive and delete the whole project, but I'm not quite ready to do that yet.

I did get things working with the bundler at last. Quite tricky and I have deactivated archival. But I suspect that I should retrace a bit of that work and upgrade to the latest versions. I miss a few functions from mailman2, especially setting a limit for message size to discourage sending larger files to the list. I also notice that there are no modbits per user that I can reach from the web as admin.

Where did you find out about the bundler? I'd like to make sure we steer people to the current best recommendations:

The documentation can be found on several places. The one that is best formatted is this one. I used a worse formatted version of the same text but right now I cannot find the link.

https://mailman-bundler.readthedocs.io/en/latest/

I notice that you changed the text on the githlab project. Better.

Now I have no idea of how upgrading the different components. I might start from scratch although it probably should be possible to upgrade the parts. The best option is probably to switch to mailman2, but that has disadvantages when handling lists for multiple domains if I am correctly informed and I already have a few domains...

I also found that sending mails manually (telnet to port 25) with no headers other than "Subject:" causes the "Held messages" tab to crash with a 500-error. Log below my signature.

cheers // David

ERROR 2017-03-25 22:54:41,762 base 17632 140529157728000 Internal Server Error: /mailman3/lists/MYLIST.COM.COM/held_messages Traceback (most recent call last): File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/generic.py", line 67, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/utils/decorators.py", line 34, in _wrapper return bound_func(*args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/auth/decorators.py", line 81, in wrapper return fn(*args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/utils/decorators.py", line 30, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/list.py", line 387, in get held_messages = utils.paginate(request, self.mailing_list.held, 20) File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", line 443, in held moderation_reasons=entry['moderation_reasons'], KeyError: u'moderation_reasons'

On 03/25/2017 04:55 PM, Mark Sapiro wrote:

A list's message_size can't currently be set in Postorius. File an issue at <https://gitlab.com/mailman/postorius/issues/new>.

Actually the attribute name is max_message_size, not message_size.

It exists in core and can be set, e.g., from the command line via 'mailman shell', but it needs to be exposed in Postorius.

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