Help request, almost got it going, but ....
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
https://github.com/maxking/docker-mailman
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
-- Claus-Justus Heine himself@claus-justus-heine.de http://www.claus-justus-heine.de/
Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de
On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote:
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
[]
See <https://gitlab.com/mailman/postorius/issues/58>.
In order to set things on this page, you need to clear the Acceptable aliases box before submitting changes. You can't actually set Acceptable aliases via Postorius until this is fixed.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Oh well.
Am 01.09.2017 um 23:44 schrieb Mark Sapiro:
On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote:
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
[]
there they talk about fancy "uni-code thinks" (email addresses?) where the task is to convert a new-line separated text-field into an array. Oops.
Kind thanks anyway.
In order to set things on this page, you need to clear the Acceptable aliases box before submitting changes. You can't actually set Acceptable aliases via Postorius until this is fixed.
The issue seems not to be overly active. I thought -- coming from Mailman v2 -- that the configuration of acceptable submitters to an email list (e.g. keep everyone moderated?) would be a central and prominent and important configuration issue. Seems not to be a central point. Mmmh.
Thanks
Claus
-- Claus-Justus Heine himself@claus-justus-heine.de http://www.claus-justus-heine.de/
Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de
On 09/01/2017 04:20 PM, Claus-Justus Heine via Mailman-users wrote:
The issue seems not to be overly active. I thought -- coming from Mailman v2 -- that the configuration of acceptable submitters to an email list (e.g. keep everyone moderated?) would be a central and prominent and important configuration issue. Seems not to be a central point. Mmmh.
Acceptable aliases corresponds directly to MM 2.1 Privacy options... -> Recipient filters -> acceptable_aliases. It has nothing to do with submitters. It is a list of other addresses that can be in the To: or Cc: of a post to avoid and "implicit destination" hold if the list posting address is not there.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Am 02.09.2017 um 01:57 schrieb Mark Sapiro:
On 09/01/2017 04:20 PM, Claus-Justus Heine via Mailman-users wrote:
The issue seems not to be overly active. I thought -- coming from Mailman v2 -- that the configuration of acceptable submitters to an email list (e.g. keep everyone moderated?) would be a central and prominent and important configuration issue. Seems not to be a central point. Mmmh.
Acceptable aliases corresponds directly to MM 2.1 Privacy options... -> Recipient filters -> acceptable_aliases. It has nothing to do with submitters. It is a list of other addresses that can be in the To: or Cc: of a post to avoid and "implicit destination" hold if the list posting address is not there.
However, the point here is that this bug makes the entire configuration tab unusable. I could live WITHOUT acceptable_aliases. This bug spoils the possibility to set ANY message acceptance settings _easily_. Of course, I can work around:
- delete the text field for acceptable aliases before hitting submit
- insert a fance @ character there, and give a damn about the fancy stuff mailman3 does with this
However, the possibility to make an entire mailing list moderated -- ALL POSTS -- is a central point. Or not?
If this is so complicated then one option might be to remove the entire "acceptable aliases" field. It does not work anyway, and spoils other useful things (read: all other settings in the "Message Acceptance" tab)
The point is not so much what this particular setting is for, but: it is broken for more than a year now and spoils other useful settings in the configuration dialog that it is located at.
The "Message Acceptance" dialog is a central point IMHO. You make have another opinion about that.
Cheers
Claus
-- Claus-Justus Heine himself@claus-justus-heine.de http://www.claus-justus-heine.de/
Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de
I think I found the bug; I have posted a comment to the issue mentioned by Mark
https://gitlab.com/mailman/postorius/issues/58
Regards
Claus
Am 02.09.2017 um 01:20 schrieb Claus-Justus Heine via Mailman-users:
Oh well.
Am 01.09.2017 um 23:44 schrieb Mark Sapiro:
On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote:
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
[]
there they talk about fancy "uni-code thinks" (email addresses?) where the task is to convert a new-line separated text-field into an array. Oops.
Kind thanks anyway.
In order to set things on this page, you need to clear the Acceptable aliases box before submitting changes. You can't actually set Acceptable aliases via Postorius until this is fixed.
The issue seems not to be overly active. I thought -- coming from Mailman v2 -- that the configuration of acceptable submitters to an email list (e.g. keep everyone moderated?) would be a central and prominent and important configuration issue. Seems not to be a central point. Mmmh.
Thanks
Claus
-- Claus-Justus Heine himself@claus-justus-heine.de http://www.claus-justus-heine.de/
Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de
I have fixed the bug on forks of mailman-core, postorius and mailman-client.
C
Am 02.09.2017 um 14:36 schrieb Claus-Justus Heine via Mailman-users:
I think I found the bug; I have posted a comment to the issue mentioned by Mark
https://gitlab.com/mailman/postorius/issues/58
Regards
Claus
Am 02.09.2017 um 01:20 schrieb Claus-Justus Heine via Mailman-users:
Oh well.
Am 01.09.2017 um 23:44 schrieb Mark Sapiro:
On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote:
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
[]
there they talk about fancy "uni-code thinks" (email addresses?) where the task is to convert a new-line separated text-field into an array. Oops.
Kind thanks anyway.
In order to set things on this page, you need to clear the Acceptable aliases box before submitting changes. You can't actually set Acceptable aliases via Postorius until this is fixed.
The issue seems not to be overly active. I thought -- coming from Mailman v2 -- that the configuration of acceptable submitters to an email list (e.g. keep everyone moderated?) would be a central and prominent and important configuration issue. Seems not to be a central point. Mmmh.
Thanks
Claus
-- Claus-Justus Heine himself@claus-justus-heine.de http://www.claus-justus-heine.de/
Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de
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
participants (3)
-
Abhilash Raj -
Claus-Justus Heine -
Mark Sapiro