Hi Brian,
The documentation is spread here and there. I think the project needs a documentation team :-) Anyway, IF the Docker system has creates it's own virtual IP (I guess because I am not familiar with it), then of course you need to let the systems within it to be able to send mail. I am assuming 172.19.199.3 : 172.19.199.2 are IPs upon which the Docker is running, and that those IPs have a way to transact mail with your local IP (probably 127.0.0.1). So if Exim is listening on all interfaces on your server, it will need to accept mail from the Docker IPs. Hence inclusion of those IP on the hosts that can relay mail via your local Exim instance. If the Docker Mailman is already running, you and you haven't added it's IP to those you relay for, it's simple to just check your Exim's mainlog or rejectlog for the IPs being denied and so you can include them. Well, the docker IPs will probably be connecting via the localhost interface.
On Thu, 20 Dec 2018 at 17:33, <brian@emwd.com> wrote:
Ok, since you wrote the documentation and specifically had exim preconfigured, I was hoping for a more definitive answer than "I think". I am not trying to be difficult here but the installation support, both via the documentation and the forum has been less than stellar. I got Discourse up and running with far less hassle than Mailman3 and from what I can see, it is a more feature rich app. The difference: Better documentation AND more helpful answers on their forums.
Would it be easier to try get Mailman3 setup with Postfix than Exim? I only went with Exim because the Docker image was preconfigured to use Exim.
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 ^[^#] :-)