On Fri, Oct 6, 2017, at 07:51 AM, Dmitry Makovey wrote:
On 10/05/2017 09:32 PM, Abhilash Raj wrote:
services: mailman-core: hostname: mailman-01 domainname: stanford.edu ... environment: ... MM_HOSTNAME: mailman-01.stanford.edu
that solved the issue while keeping the mentioned mailman config. Is that what you've had in mind? I was looking for a quick hack, but still would like to find out proper solution if that isn't the one.
If that is the address that can be used to reach the container from postfix, nothing else is needed. That is the proper solution.
yep. I've used inside container the same hostname that is assigned to public IP. Thanks for confirming appropriateness of this :) Shall I pop some notes someplace for posterity? This is the kind of issue people may step into rolling with docker containers.
I would like to mention here that it would be best if the mailman-core container is not exposed to internet (or, outside of your trusted network).
A note here1 might be a good place to put this information. Pull requests are welcome :)
P.S. Great thanks to you Abhilash for maintaining docker implementation and supporting it's users! :)
:)
-- Abhilash Raj maxking@asynchronous.in