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 ^[^#] :-)