It looks like an SSL mismatch. Zammad tries to auto detect and configure SSL/STARTTLS automatically. Looks like that didn’t work. I recall having a similar issue, but we have a mail relay internally (on the same protected subnet as Zammad), so I just whitelisted our Zammad IP on that and sent the message to that to be relayed on port 25.
Yes, I checked their certificate and there are some issues with it.
Unfortunately I don’t expect them to fix that soon, I reported it and wait for response.
And I also don’t expect them to be able to quickly whitelist my stack, they aren’t the best admins …
To get Zammad working, at least for getting on with the tests, it would be great to be able to apply some workaround in the zammad-docker-compose-stack.
I can send mails via the swaks test tool from docker (port 25, no auth).
Their exchange admin is a bit uncooperative: he doesn’t check his logs and blames my part of the setup …
Zammad-email does not work, I don’t see details, only a “501 5.5.4 Invalid domain name” coming from the exchange server (which I interpret as “non-authed clients aren’t allowed to relay”).
premise exchange in this case.
Yes, I know. Their admin is a bit … passive. Doesn’t check logs and blames docker/linux/zammad/…/my part of the setup without proof.
Sorry to hear - I’m afraid we can’t help you on that muscle fight.
You need Basic Auth or Login for Zammad. That’s something every experienced Exchange admin can setup for you within minutes. Even just for one application.