List of "site admin" commands in Mailman 3.1 docker-mailman
I am new to all of Python, Django, Docker, Docker-compose and everything else used by docker-mailman. I have managed to get a webinterface of Mailman 3.1, I installed using Docker and Docker-Compose from github.com/maxking/docker-mailman, but my config is still bogues (probably just my Apache-config).
I'm quite confused about Mailman 3 documentation regarding those commands the site admin would do in Mailman 2 like list_members, config_list -o etc.)., and I have been trying to figure out what documentation regards the development of Mailman 3, what regards the final version 3.1 and what I am supposed to do regarding Docker.
Should I enter the container using "docker exec -it mailman-web bash" and run "python" in order to get a python prompt, and from there run commands like those documented at mailman.readthedocs.io/en/latest/src/mailman/commands/docs/control.html ?.
Where do I define the what was previously known as the site admin user and site admin e-mail?
On another note: Is it a setting in the mailman-users@mailman3.org list setup that make each of my postings to the list come back with the note "This sender failed our fraud detection checks and may not be who they appear to be."?
Thanks Henrik Rasmussen
Hi Henrik,
On Jul 17, 2017, at 02:55 PM, Henrik Rasmussen wrote:
- Should I enter the container using "docker exec -it mailman-web bash" and run "python" in order to get a python prompt, and from there run commands like those documented at mailman.readthedocs.io/en/latest/src/mailman/commands/docs/control.html ?.
In Mailman 3, there's a command called mailman which has many subcommands.
if you type mailman --help, it will give you some sense of the commands
available to you. E.g. whereas in Mailman 2 you'd use list_lists at the
prompt, in Mailman 3 you would use mailman lists. You can get help on the
subcommand with mailman lists --help of course.
- Where do I define the what was previously known as the site admin user and site admin e-mail?
There's no real equivalent of the site list or site admin password in Mailman
3. There is a site_owner address you can configure in your mailman.cfg
file, but it's really just a fallback in a few cases where Mailman otherwise
can't reach a human.
On another note: Is it a setting in the mailman-users@mailman3.org list setup that make each of my postings to the list come back with the note "This sender failed our fraud detection checks and may not be who they appear to be."?
It's not something in Mailman. Possibly in the toolchain on mailman3.org?
-Barry
Hi Henrik,
On Mon, Jul 17, 2017, at 07:55 AM, Henrik Rasmussen wrote:
I am new to all of Python, Django, Docker, Docker-compose and everything else used by docker-mailman. I have managed to get a webinterface of Mailman 3.1, I installed using Docker and Docker-Compose from github.com/maxking/docker-mailman, but my config is still bogues (probably just my Apache-config).
I'm quite confused about Mailman 3 documentation regarding those commands the site admin would do in Mailman 2 like list_members, config_list -o etc.)., and I have been trying to figure out what documentation regards the development of Mailman 3, what regards the final version 3.1 and what I am supposed to do regarding Docker.
- Should I enter the container using "docker exec -it mailman-web bash" and run "python" in order to get a python prompt, and from there run commands like those documented at mailman.readthedocs.io/en/latest/src/mailman/commands/docs/control.html ?.
Just to add to what Barry mentioned, the in docker command above, you
should
enter the mailman-core container instead of the mailman-web
container if
you are looking for the command line options of Mailman Core.
so it should be something like:
$ docker exec -it mailman-core bash-- thanks, Abhilash Raj
On 07/17/2017 07:55 AM, Henrik Rasmussen wrote:
On another note: Is it a setting in the mailman-users@mailman3.org list setup that make each of my postings to the list come back with the note "This sender failed our fraud detection checks and may not be who they appear to be."?
I suspect this is something in the MTA/MDA chain between the lists.mailman3.org server and you. I suspect that something in that path doesn't like the fact that your original message's DKIM signature has been broken by such things as subject prefixing and addition of the list's msg_footer.
When your message reaches my server at msapiro.net, it sees
Authentication-Results: sbh16.songbird.com; dkim=pass (1024-bit key; unprotected) header.d=mailman3.org header.i=@mailman3.org header.b=QBeM9elY; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=alumni.onmicrosoft.com header.i=@alumni.onmicrosoft.com header.b=GeTpYnXK; dkim-atps=neutral
I.e., the list's DKIM sig is valid but your original sig is not, even though it was valid when received by the list
Authentication-Results: mail.mailman3.org; dkim=pass reason="1024-bit key; unprotected key" header.d=alumni.onmicrosoft.com header.i=@alumni.onmicrosoft.com header.b=GeTpYnXK; dkim-atps=neutral
If my suspicion is correct, you should be seeing the same thing with other people's posts such as this reply and your posts to other lists. If you don't then my suspicion about DKIM is not the reason and it is something else or the conditions are more complex.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Abhilash Raj -
Barry Warsaw -
Henrik Rasmussen -
Mark Sapiro