On Aug 18, 2021, at 1:00 PM, bob B <bader@cchmc.org> wrote:
Thanks,
but if I put SMTP_HOST: 172.25.0.1 in the docker.yaml, and then down and up (docker-compose down, docker-compose up -d) the images then container grab a new IP range, (like 172.26.0.X). but my smtphost is 172.25.0.1, so that would break again, correct?
That is correct.
What should i put for SMTP_HOST: XXXXX in doicker.yaml to keep this from happening?
You can grab a static subnet and assign it to your compose file. This is what old version of the docker-compose.yaml used to do, see this for example
https://github.com/maxking/docker-mailman/blob/v0.3.11/docker-compose.yaml#L...
You probably don’t need to assign static IPs to each container like in the compose file above, since all you need the gateway address to be static to reach SMTP_HOST.
And are you saying my /opt/mailman/core/mailman-extra.cfg should be
# cat /opt/mailman/core/mailman-extra.cfg # mailman-extra.cfg
[mailman] # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: XXXX@XXXX.XXXXX
That is correct!
-- thanks, Abhilash Raj (maxking)