Hi Claus,
On Fri, 1 Sep 2017 23:33:56 +0200 Claus-Justus Heine via Mailman-users <mailman-users@mailman3.org> wrote:
First: thanks for all those development work, I am aware of the fact that this is free software and most of the development probably happened in someones spare-time.
I have some problems:
- I tried to install mailman v3. "Read the (non) docs" was of little help, but I got to some partly success following the commands in the scripts in the docker image at
If you can point out what were the few things that you think were missing in the docs but you were able to figure out using the scripts in container image, it would help us improve the documentation.
You can send them here or open an issue on Gitlab project1.
Things seemed to work out, I generated a test-list "Playground" and now I am just in the progress to click through all the configuration options in the the postorius Web-GUI. So far so good
Now I read the "Message Acceptance" tab AND here is the problem:
Seemingly, at some point in the deep dungeons of the source code the "Acceptable aliases" Text-Box is not interpreted correctly.
Specifically, at the start it contains the string
[]
When then changing something int the "Message Acceptance" tab, an error shows up in the web-page (but no-where in the logs)
"An error occured: []"
and the bogus [] is restored. I tried to dig into the source code, and well, the data source of the text-field is an array or list of acceptable email-adresses. But seemingly finally at some point in the source code an empty list is not converted to the empty string, but to the string [].
I can get rid of the error message "An error occured: []" by inserting an email-at '@' at just some place in the input box, this yields (clicking "Save changes" again and againg ...):
[u"[u'@']"] [u'[u\'[u"[u\\\'@\\\']"]\']'] [u'[u\'[u\\\'[u\\\\\\\'[u"[u\\\\\\\\\\\\\\\'@\\\\\\\\\\\\\\\']"]\\\\\\\']\\\']\']']
and so on.
Unfortunately, I did not find the location of this bug, although I was finally able to add some "foobar" string to the already bogus web-output.
Any help would be appreciated.
BTW:
- where is the bug-tracker for mailman3?
- The documentation is really, well, close to non existent. Personally, I think the name of the URL "read-the-docs" is almost cynical.
Guess I give up on it, it just does not seem to be ready for production.
This was (following the docker stuff at githb) with
Pythong3: mailman==3.1.0 mailman-hyperkitty==1.1.0
Python2: mailmanclient==3.1.0 postorius==1.1.0 hyperkitty==1.1.1 django-mailman3==1.1.0
Here I realize a slight version difference between the hyperkitty stuff. But this is a bug in postorius. So what.
Thanks for any help, cheers
Claus
-- thanks, Abhilash Raj