Mailu/Mailman3 integration terror thread #2
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A home for all the mess. Best keep it under this repo.
Also see https://git.autonomic.zone/coop-cloud/mailu/issues/1.
Current status:
(This helped!)
OK, my current idea is then:
Stand the mailman3 instance up
Add DNS entries for the incoming mail config
Config the shit out of the mailman3 instance to wire up outgoing mail
Test, test, test
RE: "Add DNS entries for the incoming mail config" in https://git.autonomic.zone/coop-cloud/mailman3/issues/2#issuecomment-5712 above:
Was looking at https://github.com/bokysan/docker-postfix for
d0ae866623/compose.yml (L37-L40)
.Potential plan to avoid the additional postfix configuration:
May need to re-work the mailu postfix configuration but maybe that is good too!
OK, added the DNS entries (MX, SPF). Managed to stand-up the mailman3 install also (taken down for now)! However, the REST API connection is not working. That is the next thing to fix. Then I can finally start debugging incoming/outgoing mail.
abra app lists.autonomic.zone deploy
now works!The next step is to wire up the shared network and volumes for mailman-core to be able to speak to the our mailu postfix container (from
02e4559768/mailman-extra.cfg.tmpl (L10)
toa23e9fc40b/compose.yml (L113-L119)
afaiu).For the shared network, I am hoping I can put the core service in the mailman config on the mailu default overlay network and declare it as external from the mailman side.
Annnd for the shared volume, I am not sure, but using this external trick to load the mailman-core postfix mapping generated files into the mailu postfix container will hopefully work.
The final piece of the puzzle is transport_maps/local_recipient_maps/relay_domains overridden in the mailu configured postfix to push stuff over to the mailman LMTP endpoint. I'm looking for ways to hook in via https://github.com/Mailu/Mailu/tree/master/core/postfix/conf.
See https://mailu.io/1.7/faq.html?highlight=override#how-can-i-override-settings.
the mailu side postfix overrides and shared volume (haven't tested this at all):
98c5bbc95f/compose.mailman.yml
the mailman side shared overlay network to get smtp connections from the mailu postfix configuration (also haven't tested this at all):
3266e9ffbc/compose.yml (L12)
To start testing this, we need to (I think!):
abra app lists.autonomic.zone deploy
check what is generated in
/opt/mailman/core/var/data/postfix_lmtp
and take note of the hostname on the mailman stackre-deploy
mail.autonomic.zone
withCOMPOSE_FILE="compose.yml:compose.mailman.yml"
and make sure it comes upDrop into a shell on the mailu side and make the external volume is available in
/opt/mailman/
and the hostnamemailman-core
in pingable. postfix should also have loaded the /overrides/... configuration. Ensure the hostname generated in the/opt/mailman/core/var/data/
files (see step 2) ismailman-core
or some other pingable address (ensures mailu can pass mails to mailman LTMP)Drop into a shell on the mailman side and make sure
$SMTP_NETWORK
in pingable (ensures we can send outgoing mail)Fix the double
/etc/hosts
entryDocument the madness
Revisit if any of this is really bad
Remaining issues:
[2021-05-21 15:45:44 +0000] [48] [ERROR] Can't connect to ('10.0.52.25 192.168.203.47', 8001)
stack rm
'ing and how that works with shared network/volumesI realised that the relay domain is not even needed for our current frankenstein setup. Since we load in the maps, the mailu postfix knows exactly where to pass things (and thats why it was trying port 25 on the incoming relaying at first!). I was reading https://mailu.io/master/webadministration.html#relayed-domains.
I attempted to drop the shared volume and use the relay domain directly but ran into https://github.com/Mailu/Mailu/issues/1815. So, we need the shared volume to tell the mailu postfix that it should use LMTP to do the communication, not SMTP.
2f27f298f9
"solves" the double entry issue on the core/etc/hosts/
side.🙈