Hey All,
For the past few days, I've been trying to improve the documentation
style for Mailman Core's config options. Internally, Mailman has
all configurations defined in an ini formatted `schema.cfg` file, which
serves as a schema for our `zope.configuration` library. We had that file
simply embedded in the sphinx documentation previously as a wall of text.
I ended up writing a Sphinx (our documentation generator) plugin which
parses the config file and presents the same documentation with more
bells and whistles so it is easier to lookup and link sections and config
options.[1]
The process of doing that was fun and I learnt how to write a simple
sphinx plugin, so yay! It treats the comments above each config option
in the ini file as it's doc and basically generates ReST text that it passes
to Sphinx to parse and convert to the markup format that you see in
browser. You can look at it in the source repo[2] .
Do note that not all sections are documented yet, I am still figuring out what
would be a good way to document template sections like `[plugins.master]`
and other similar sections of that kind.
[1]: https://gnu-mailman--667.org.readthedocs.build/projects/mailman/en/667/src/… ((URL is for the PR,
the main doc seems like is serving the cached version from an older
build).
[2]: https://gitlab.com/mailman/mailman/-/blob/master/_ext/configplugin.py
--
thanks,
Abhilash Raj (maxking)
I recently imported a number of MM2 lists into MM3. Unfortunately, the person had emergency moderation turned on for these lists. Since EM is not exposed to Postorius what can be done to reverse this?
Thanks,
Brian
Hi folks, I spent many hours last night trying to get Mailman 3 up and running. I am using Ubuntu on a Digital Ocean LAMP droplet (so PHP, Apache, Sql, and Postfix are already installed). The LAMP stack works as I have a successful installation of YOURLS going on.
So, I tried to use this guide (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) to install the Mailman3 package and got to the configuration screen (the one with all the DOS-esque GUI). I ran it but it kept saying the DB wasn't installed. Was I supposed to create SQL databases and users before running that and use those usernames/databases in the credentials it asks for? It doesn't seem like that in the way it asks the questions (since it asks to create a password) but I wasn't sure.
Anywho, I tried to remove the package completely and restart but I keep spinning my wheels. So my questions:
1. Does that guide actually work? Did I just foul up the database part?
2. Is there a better way to install mailman3 with some nice step-by-step directions to follow?
3. Is there a way to completely wipe my previous installs without wiping the server? ( I didn't back up...silly I know ). I used apt-get --purge remove to uninstall mailman3 and mailman to start over, did that do the trick?
Sorry for all the questions.
Hi everyone,
I'm running Mailman 3 in maxking's Docker container (tag 0.3). Mailman3
runs really well, thanks for that good job! But I noticed two errors.
1) When a new list is created, Mailman will not notify the list owners
of their new mailing list. I tested it with the default template
"domain:admin:notice:new-list.txt" and my own template (which i copied
in $var_dir/templates/domains/DOMAIN/de/
Any customs templates in $var_dir/templates... aren't sent out, always
the default templates from
/usr/lib/python3/site-packages/mailman/templates/de. I can't find
anything in the logs for that issue.
2) When a post requires an approval and I reject it with a notification
a server error occurs: "An error occurred while processing your request."
The Traceback in mailmanweb.log is:
ERROR 2020-08-01 16:19:19,926 17 django.request Internal Server Error:
/postorius/lists/list.domain.de/held_messages/moderate
Traceback (most recent call last):
File
"/usr/lib/python3.6/site-packages/django/core/handlers/exception.py",
line 34, in inner
response = get_response(request)
File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py",
line 115, in _get_response
response = self.process_exception_by_middleware(e, request)
File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py",
line 113, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File
"/usr/lib/python3.6/site-packages/django/views/decorators/http.py", line
40, in inner
return func(request, *args, **kwargs)
File
"/usr/lib/python3.6/site-packages/django/contrib/auth/decorators.py",
line 21, in _wrapped_view
return view_func(request, *args, **kwargs)
File "/usr/lib/python3.6/site-packages/postorius/auth/decorators.py",
line 60, in wrapper
return fn(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/postorius/views/list.py", line
549, in moderate_held_message
mailing_list.reject_message(msg.request_id, reason=reason)
TypeError: reject_message() got an unexpected keyword argument 'reason'
Thanks a lot for any suggestion.
Greets
Marcel
Mailman Core Version: 3.3.1
Mailman Core API Version: 3.1
Postorius Version 1.3.3
HyperKitty Version 1.3.3
