On Sun, Oct 22, 2017, at 09:36 AM, Marvin Gülker wrote:
Am 22. October 2017 um 07:49 Uhr -0700 schrieb Mark Sapiro <mark@msapiro.net>:
or you can install the fix at
Thanks. Applying this patch makes it work. Now I've got a different problem, though. I can't get it to connect to Postfix for sending emails it appears. After I created a superuser account using
$ python manage.py createsuperuser
as described on <http://postorius.readthedocs.io/en/latest/setup.html>, I tried to login using this credentials into Postorius. It then reported it sent a confirmation email to me (for an account I created on commandline?!), but Postfix' logs reveal that it didn't; there's not even a sign of an attempted delivery in /var/log/mail.log. I've configured the Postfix configuration in mailman.cfg like this:
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfixas was outlined on <http://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html>.
mailman-suite's settings.py contains:
# Change this when you have a real email backend EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25which was described on <http://docs.list.org/en/latest/config-web.html>.
For completeness, the following is in Postfix' main.cf, but is not the cause of the problem as it affects the incoming direction, whereas I refer to the outgoing one:
transport_maps = hash:/home/mailman/var/data/postfix_lmtp local_recipient_maps = hash:/home/mailman/var/data/postfix_lmtpI failed to locate any kind of logging information about the failed email, so I don't even know where I should start looking for the problem. var/logs/smtp.log is empty in the mailman directory, and likewise is logs/mailmansuite.log in the mailman-suite_project directory.
As Simon mentioned, try using DEBUG=False, if you don't already have
that. With DEBUG=True, you should see emails printed in a emails
directory under mailman-suite_project directory.
This is a confirmation email to verify the email addresses, which happens even if you create an account from command line.
That being said, the enormous number of configuration files to consider and dozens of cross-references to other pages in the docs make the installation guide hard to follow; it also lacks logical structure in my opinion, when it refers to parts of the configuration which are later explained. For someone like me who never programmed a Django application (Ruby dev) this is all pretty cryptic. Especially, that some parts of information are on <http://docs.list.org/en/latest/index.html> whereas other parts are scattered over readthedocs.io makes it very complicated.
There are only two primary configuration files (there are a few more for finer configurations ;-):
mailman.cfg: This is the configuration for the Core engine and can be located any of the places mentioned in 1 or pointed to by environment var MAILMAN_CONFIG_FILE.
settings.py: This is the configuration file for Django under
mailman-suite_projectand controls the frontend (Postorius & Hyperkitty). Django is a huge framework with literally 1000s of options. It would be impossible to copy that information from Django's documentation and keep it updated in our docs. Hence, we have links to appropriate places when needed. Same goes out for the rest of the libraries that we use.
All the settings mentioned in the documentation go to either of these files, except, when configuring web server and mail server. Please open an issue2 if it is not clear where a particular configuration snippet goes and we will fix it.
Hope that helps!
-- Abhilash Raj maxking@asynchronous.in