- Used Zammad version: 3.2.x
- Used Zammad installation source: (source, package, …) apt-get repo
- Operating system: Ubuntu 18.04
- Browser + version: Any
When using a non-standard port for the web interface, say 8080, all the links in e-mails etc are wrong unless I also update the FQDN under Settings - System - Base. However, the FQDN also seems to be the string that is sent to SMTP under EHLO, and hostname:port is not accepted as EHLO hostname by the SMTP server, nor should it be.
Any ideas how we can work around this - we need to run Zammad on a non-standard port, the links mus tbe correct but the port number should not be used in the SMTP EHLO.
This technically is possible, however, needs some work from your end.
First of all you’ll need to replace the variable for your notification sender with your actualy domain/fqdn of choice.
With changing this, you’ll then be able to add the required port to the FQDN within System -> Base.
You can change the notification sender within E-Mail -> Settings.
Thanks for the info.
Changing the sender doesn’t help, as the problem lies with the FQDN sent in the EHLO, rather than the Envelope Sender address.
However, I worked around this by setting up a reverse proxy. So no solution is needed any longer
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.