I am using Exim as the MTA. I followed the instructions located at:

https://github.com/maxking/docker-mailman

In particular the "Setting up your MTA"

Are you saying I need to do something with Django because your documentation at github makes no reference to that? Where would I find the settings.py file? I used your image to install Mailman3. FYI I am referencing the "# To be added to Django's settings.py" instructions at

http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required

Abhilash Raj wrote:

On Thu, Dec 20, 2018, at 10:25 AM, brian(a)emwd.com wrote:

...

I am using Exim as the MTA. I followed the instructions located at:

https://github.com/maxking/docker-mailman

In particular the "Setting up your MTA"

Are you saying I need to do something with Django because your documentation at github makes no reference to that? Where would I find the settings.py file? I used your image to install Mailman3. FYI I am referencing the "# To be added to Django's settings.py" instructions at

The documentation at Github does makes reference to it. It might not be in the most visible manner, which I have opened an issue to fix1

...

To configure the mailman-web container to send emails, see these configuration settings. The documentation also mentions about the Django configuration file, settings_local.py (which is imported by settings.py at runtime). 3.

I have opened another issue to make that clear as well. 2

You can add all your Django related settings in /opt/mailman/web/settings_local.py if you using the images and docker-compose.yaml file from the above mentioned repo.

...

http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required

---

Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I am glad this is going to result in getting more clearer documentation.

I have added the following to /opt/mailman/web/settings_local.py

EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = <username> EMAIL_HOST_PASSWORD = <password>

The question I have is where does the username and password come from?

Brian

Thanks. I removed the following from /opt/mailman/web/settings_local.py:

EMAIL_HOST_USER = <username> EMAIL_HOST_PASSWORD = <password>

Do I need to restart mailman and if yes how?>

Thanks again, Brian

Abhilash Raj wrote:

Yes, you do need to restart mailman-web container.

$ docker-compose restart mailman-web

When I added the following to /opt/mailman/web/settings_local.py

EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25

I got network not found error message in the log file when I tried to reset my password. Should EMAIL_HOST be something else besides localhost?

Abhilash Raj wrote:

It should be pointing to Exim running on host, so

EMAIL_HOST = 172.19.199.1

That fixed the network not found error. Thank you for your help there.

Now I am back to the verification error:

"smtplib.SMTPRecipientsRefused: {'brian@emwd.com': (550, b'Verification failed for <postorius@host.name.com>\nUnknown user\nSender verify failed')}"

I am at a lost on how to get exim to allow mail sent from postorius@host.name.com. Obviously host.name.com is the mm3 domain that I am using.

Brian

On Fri, 21 Dec 2018 at 03:25, Abhilash Raj <maxking@asynchronous.in> wrote:

On Thu, Dec 20, 2018, at 4:05 PM, brian@emwd.com wrote:

...

Abhilash Raj wrote:

...

It should be pointing to Exim running on host, so

EMAIL_HOST = 172.19.199.1

That fixed the network not found error. Thank you for your help there.

Now I am back to the verification error:

"smtplib.SMTPRecipientsRefused: {'brian@emwd.com': (550, b'Verification failed for <postorius@host.name.com>\nUnknown user\nSender verify failed')}"

I am at a lost on how to get exim to allow mail sent from postorius@host.name.com. Obviously host.name.com is the mm3 domain that I am using.

A quick search says that Exim is trying to verify that postorius@host.name.com is a real mailbox (which I am assuming it is not), and rejecting the email coming from Postorius.

You probably have

 verify = sender

somewhere in your exim.conf, which is causing this. You can either modify the

DEFAULT_FROM_EMAIL

in your settings_local.py so that it is a real address that Exim can verify, or, you can remove verify = sender from your Exim configuration. 2nd option might not be the best if you want to properly combat spam.

Exim experts would be able to help you better with this.

...

Hi Brian,

In postorius@host.name.com, please change the host.name.com to match the MM3_DOMAINS or whatever it is called in your MACROS. Remember, it has to be a VALID hostname that you will be using for Mailman3 lists. That, coupled with the IPs 172.19.199.x being in relay_from_hosts should let the address to pass verification with Exim.

-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

Hi Abhilash,

Can I use the instructions at https://github.com/maxking/docker-mailman with a MySQL database instead of PostgreSQL? I am looking at the following block in docker-compose.yaml:

database: environment: POSTGRES_DB: mailmandb POSTGRES_USER: mailman POSTGRES_PASSWORD: mailmanpass restart: always image: postgres:9.6-alpine volumes: - /opt/mailman/database:/var/lib/postgresql/data networks: mailman: ipv4_address: 172.19.199.4

I'd like to change those to use MySQL. Maybe you should also add an example on the site for these??

On Fri, 21 Dec 2018 at 03:25, Abhilash Raj <maxking@asynchronous.in> wrote:

On Thu, Dec 20, 2018, at 4:05 PM, brian@emwd.com wrote:

...

Abhilash Raj wrote:

...

It should be pointing to Exim running on host, so

EMAIL_HOST = 172.19.199.1

That fixed the network not found error. Thank you for your help there.

Now I am back to the verification error:

"smtplib.SMTPRecipientsRefused: {'brian@emwd.com': (550, b'Verification failed for <postorius@host.name.com>\nUnknown user\nSender verify failed')}"

I am at a lost on how to get exim to allow mail sent from postorius@host.name.com. Obviously host.name.com is the mm3 domain that I am using.

A quick search says that Exim is trying to verify that postorius@host.name.com is a real mailbox (which I am assuming it is not), and rejecting the email coming from Postorius.

You probably have

 verify = sender

somewhere in your exim.conf, which is causing this. You can either modify the

DEFAULT_FROM_EMAIL

in your settings_local.py so that it is a real address that Exim can verify, or, you can remove verify = sender from your Exim configuration. 2nd option might not be the best if you want to properly combat spam.

Exim experts would be able to help you better with this.

...

Brian

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- thanks, Abhilash Raj (maxking)

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

Abhilash Raj writes:

Exim experts would be able to help you better with this.

I'm the one who set up the original sample Exim .conf, because (a) I didn't want to migrate all my bots to Postfix, and (b) the one-real- host .conf turned out to be trivial. I'm an Exim expert only for my own configuration, which is a (pre-global-warming) glacially-moving target. I've never seen anything like the problems described here, sorry. Can't help.

Since it's looking like we don't have any real Exim experts hanging around here, perhaps we should move the sample containers and other default configs to assume Postfix and document "Exim should work but you're kinda on your own, we'll do what we can but it's limited." At least Mark is maintaining such systems, and they're probably better documented than Exim for the single-real-host configuration, though they would probably run into similar problems with the containerized setup. WDOT?

Steve

-- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull@sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

brian@emwd.com writes:

I think it really is not that complicated in getting exim setup, at least with a Centos system.

I didn't mean to imply that it was. As I wrote elsewhere, it happened to be nearly trivial for me. :-) The question is what we have the expertise to support.

1. Not realizing exim is setup differently depending on the flavor of Linux. For Debian systems, there is a conf.d folder to place the 3 above mention files into. Not for Centos 7. Evidently some of the syntax is different as well.

I think Debian/Ubuntu is different from RHEL/Fedora/Centos for most things that have many configuration options that are actually used, because of the complex, Debian-specific automation.

2. I also did not realize I had some syntax errors in exim.conf that caused exim not to restart. For some reason, the OS did not tell me Exim failed to restart when I used "systemctl restart exim.service". I happen to run "systemctl status exim.service"

That's systemd. I hope somebody else develops expertise in it, since it now seems unavoidable (I avoided it figuring my needs would probably well served by default configuration by the time it became unavoidable ;-).

What I would change in the documentation is to let exim users know to use a valid mail account for posterious to send out messages._

Thanks for these suggestions!

I think all modern MTAs have a sender verify option, so we should make that generic advice, especially since any MX in the system could reject.

Perhaps it is there but it was not apparent to me. I would also mention some more Exim specific settings to modify For example:

"To use Exim4, it should be setup to relay emails from 172.19.199.3 and 172.19.199.2."

I would change the above line to include the actual setting to change in the exim.conf file:

hostlist relay_from_hosts = localhost : 172.19.199.3 : 172.19.199.2 : 172.19.199.1

However the challenge in that is the above setting is for Centos 7.

I think this would be the same for any system using the defaults in the docker images.

I know we don't want to make the documentation too large or unwieldy but I think the above suggestions won't add too much to the weight of the documentation.

Mail is hard and complex, as you know. Size of documentation is unavoidable. Making it useful for troubleshooting is the need, and the hard part.

On Fri, 21 Dec 2018 at 20:19, Abhilash Raj <maxking@asynchronous.in> wrote:

On Fri, Dec 21, 2018, at 4:00 AM, Stephen J. Turnbull wrote:

...

Abhilash Raj writes:

...

Exim experts would be able to help you better with this.

I'm the one who set up the original sample Exim .conf, because (a) I didn't want to migrate all my bots to Postfix, and (b) the one-real- host .conf turned out to be trivial. I'm an Exim expert only for my own configuration, which is a (pre-global-warming) glacially-moving target. I've never seen anything like the problems described here, sorry. Can't help.

Since it's looking like we don't have any real Exim experts hanging around here, perhaps we should move the sample containers and other default configs to assume Postfix and document "Exim should work but you're kinda on your own, we'll do what we can but it's limited." At least Mark is maintaining such systems, and they're probably better documented than Exim for the single-real-host configuration, though they would probably run into similar problems with the containerized setup. WDOT?

Originally, the reason I went with Exim was because the postmap + hash files were hard to generate for Mailman from within the container when the postfix was running on the host. Exim checks existence of certain paths to verify that the Mailing List exists, which was easier to do.

However, now Mailman Core supports regex maps for Postfix, which can be used with containers.

Images already support using Postfix, it is just not the default in setup scripts and documentation. I have opened an issue1 to maybe change that if some initial testing doesn't goes fine.

Hello Maxking,

It is importantest to maintain Exim support :-)

-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

I agree with you.

On Fri, 21 Dec 2018 at 23:21, Abhilash Raj <maxking@asynchronous.in> wrote:

On Fri, Dec 21, 2018, at 12:18 PM, Odhiambo Washington wrote:

On Fri, 21 Dec 2018 at 20:19, Abhilash Raj <maxking@asynchronous.in> wrote:

On Fri, Dec 21, 2018, at 4:00 AM, Stephen J. Turnbull wrote:

...

Abhilash Raj writes:

...

Exim experts would be able to help you better with this.

I'm the one who set up the original sample Exim .conf, because (a) I didn't want to migrate all my bots to Postfix, and (b) the one-real- host .conf turned out to be trivial. I'm an Exim expert only for my own configuration, which is a (pre-global-warming) glacially-moving target. I've never seen anything like the problems described here, sorry. Can't help.

Since it's looking like we don't have any real Exim experts hanging around here, perhaps we should move the sample containers and other default configs to assume Postfix and document "Exim should work but you're kinda on your own, we'll do what we can but it's limited." At least Mark is maintaining such systems, and they're probably better documented than Exim for the single-real-host configuration, though they would probably run into similar problems with the containerized setup. WDOT?

Originally, the reason I went with Exim was because the postmap + hash files were hard to generate for Mailman from within the container when the postfix was running on the host. Exim checks existence of certain paths to verify that the Mailing List exists, which was easier to do.

However, now Mailman Core supports regex maps for Postfix, which can be used with containers.

Images already support using Postfix, it is just not the default in setup scripts and documentation. I have opened an issue1 to maybe change that if some initial testing doesn't goes fine.

Hello Maxking,

It is importantest to maintain Exim support :-)

I didn't mean to say that we are going to stop supporting Exim, it is just that I'll make Postfix default in Container given that most of the Mailman Devs are more comfortable helping out people with Postfix issues, as they use it for their own personal setups.

Switching between default and non-default would be easy and both of them will be supported, to the best my own abilities :)

-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

-- thanks, Abhilash Raj (maxking)

-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

Abhilash Raj writes:

You probably have

 verify = sender

somewhere in your exim.conf, which is causing this.

No, that seems unlikely. This is in the default exim.conf.

You can either modify the

DEFAULT_FROM_EMAIL

in your settings_local.py so that it is a real address that Exim can verify,

He's already modified that, since the default in settings.py is "postorius@localhost.local" (which is a bug: this should default to a mailbox, and the domain should be added automatically if only a mailbox is given).

It seems likely that what needs to be done is to set up a mailbox for Postorius, which can be done in several ways. When does Postorius receive mail? I guess it *sends* mail for the mailbox owner confirmation dialogs on subscription or password reset, but that confirmation is normally done by a web transaction, right? If <postorius> rarely gets mail, the obvious thing to do would be to alias to site owner or postmaster. (It looks like Django doesn't know how to receive mail, so any facility for postorius to receive mail would have to be configured in the MTA.)

If it's not that, then the problem likely has something to do with the containerization, and the MTA getting confused about which host is which.

or, you can remove verify = sender from your Exim configuration.

Don't do this. If you set up a separate Exim router for "postorius" (to do something fancy like a autoreply bot or delivery to /dev/null ;-), you can put the no_verify option in the Requires stanza for it.

Steve

-- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull@sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

On Thu, Dec 20, 2018, at 11:58 AM, Odhiambo Washington wrote:

On Thu, 20 Dec 2018 at 22:41, <brian@emwd.com> wrote:

...

I got the verification failed message fixed with via some offline help with one of our list members. I am now getting the following when I try to reset the password:

ERROR 2018-12-20 19:33:32,762 52 django.request Internal Server Error: /accounts/password/reset/ Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/django/core/handlers/exception.py", line 35, in inner response = get_response(request) File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 128, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 126, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.6/site-packages/django/views/generic/base.py", line 69, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.6/site-packages/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.6/site-packages/allauth/account/views.py", line 103, in post response = self.form_valid(form) File "/usr/local/lib/python3.6/site-packages/allauth/account/views.py", line 644, in form_valid form.save(self.request) File "/usr/local/lib/python3.6/site-packages/allauth/account/forms.py", line 540, in save context) File "/usr/local/lib/python3.6/site-packages/allauth/account/adapter.py", line 137, in send_mail msg.send() File "/usr/local/lib/python3.6/site-packages/django/core/mail/message.py", line 294, in send return self.get_connection(fail_silently).send_messages([self]) File "/usr/local/lib/python3.6/site-packages/django/core/mail/backends/smtp.py", line 103, in send_messages new_conn_created = self.open() File "/usr/local/lib/python3.6/site-packages/django/core/mail/backends/smtp.py", line 63, in open self.connection = self.connection_class(self.host, self.port, **connection_params) File "/usr/local/lib/python3.6/smtplib.py", line 251, in __init__ (code, msg) = self.connect(host, port) File "/usr/local/lib/python3.6/smtplib.py", line 336, in connect self.sock = self._get_socket(host, port, self.timeout) File "/usr/local/lib/python3.6/smtplib.py", line 307, in _get_socket self.source_address) File "/usr/local/lib/python3.6/socket.py", line 724, in create_connection raise err File "/usr/local/lib/python3.6/socket.py", line 713, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused

The above error occurs with the firewall turned off as well.

I am not an expert in this, but whenever at look at the cryptic mailman errors, the last line always defines the error. So I am guessing - mailman is trying to make an LMTP connection to your Exim, but it's refused the connection???

Mailman is trying to make SMTP connection to Exim on 25.

Exim is refusing connections most probably because it is not configured to relay emails from the IPs of the containers. I am not an Exim expert, but it should be fairly easy to search for that in Exim docs.

Is Exim listening on the lmtp port?

wash@lists:~$ telnet localhost 8024 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 FQDN GNU Mailman LMTP runner 2.0

This is Mailman listening on Port 8024, which Exim uses to forward incoming emails.

-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- thanks, Abhilash Raj (maxking)

On Thu, Dec 20, 2018, at 1:23 PM, brian@emwd.com wrote:

Odhiambo Washington wrote:

...

On Thu, 20 Dec 2018 at 22:41, <brian(a)emwd.com> wrote:

...

I got the verification failed message fixed with via some offline help with one of our list members. I am now getting the following when I try to reset the password:

ERROR 2018-12-20 19:33:32,762 52 django.request Internal Server Error: /accounts/password/reset/ Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/django/core/handlers/exception.py", line 35, in inner response = get_response(request) File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 128, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 126, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.6/site-packages/django/views/generic/base.py", line 69, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.6/site-packages/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.6/site-packages/allauth/account/views.py", line 103, in post response = self.form_valid(form) File "/usr/local/lib/python3.6/site-packages/allauth/account/views.py", line 644, in form_valid form.save(self.request) File "/usr/local/lib/python3.6/site-packages/allauth/account/forms.py", line 540, in save context) File "/usr/local/lib/python3.6/site-packages/allauth/account/adapter.py", line 137, in send_mail msg.send() File "/usr/local/lib/python3.6/site-packages/django/core/mail/message.py", line 294, in send return self.get_connection(fail_silently).send_messages([self]) File "/usr/local/lib/python3.6/site-packages/django/core/mail/backends/smtp.py", line 103, in send_messages new_conn_created = self.open() File "/usr/local/lib/python3.6/site-packages/django/core/mail/backends/smtp.py", line 63, in open self.connection = self.connection_class(self.host, self.port, **connection_params) File "/usr/local/lib/python3.6/smtplib.py", line 251, in __init__ (code, msg) = self.connect(host, port) File "/usr/local/lib/python3.6/smtplib.py", line 336, in connect self.sock = self._get_socket(host, port, self.timeout) File "/usr/local/lib/python3.6/smtplib.py", line 307, in _get_socket self.source_address) File "/usr/local/lib/python3.6/socket.py", line 724, in create_connection raise err File "/usr/local/lib/python3.6/socket.py", line 713, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused

The above error occurs with the firewall turned off as well.

I am not an expert in this, but whenever at look at the cryptic mailman errors, the last line always defines the error. So I am guessing - mailman is trying to make an LMTP connection to your Exim, but it's refused the connection??? Is Exim listening on the lmtp port?

wash@lists:~$ telnet localhost 8024 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 FQDN GNU Mailman LMTP runner 2.0

I got this when I used the telnet command:

# telnet localhost 8024 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused

What is localhost here?

Mailman Core is running inside a container, with default IP of 172.19.199.2(if you are using my docker-compose.yaml). It will listen on Port 8024 for LMTP (emails) and Port 8001 for HTTP (REST API).

You should be able to telnet to both of these Ports to verify that Core is indeed up and running.

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- thanks, Abhilash Raj (maxking)