So far I didn’t manage to get the email notifications to work. Neither with our own Exchange Server which is local or an Gmail account. Preferred way would be Exchange.
For now its pretty unclear where the informations need to be inserted in the config.env .
My first suggestion would be to try using destination ports 587 or 465, in that order; mail servers are often much pickier about port 25 since it’s the transport channel, not just merely a local-user submission channel.
Secondly, will your Exchange server allow that username there to be a domain username? I would expect it to want a mailbox name instead, user@domain.com
As for TLS and STARTTLS, one of those might also be troublesome, more likely the latter.
What errors are you getting on mail-send attempts, and where?
Ok. Next up: the Exchange server may not allow incoming mail to port 25 to leave the mail server, unless it’s been told to, somehow. An authenticated login might be enough, or you may need to whitelist the sending machine’s IP…
This is done to avoid letting machines become spam-repeaters for off-net third parties.
Hi,
so as i also needed another service, i found out that the 587 authenticated login works for our exchange.
As i not needed to whitelist the other machine, I guess we can also delete that from the list of possibilities.
So to clarify: other senders can connect to your exchange via tcp/587 authenticated, and send mail out to the greater Internet… but your Xibo installation cannot?
Yes, thats right. So i think the error when testing with xibo was not the 587 port itself but another setting.
Could it be the cms_smtp_hostname?
Im still not sure if i understood correctly what needs to be inserted there and where i would find out the needed hostname
So far I can see is that you are using O365 with a usermailbox?
If so, please check the following article from Microsoft.Enable or disable SMTP AUTH in Exchange Online | Microsoft Learn
Could be that you need to enable the SMTP authentication for the mailbox and tenant.
One the reasons I just sticked using direct mail is the behavior of SMTP lately from Microsoft. The want to stop supporting this method. #option2 (if choosing this option, just blank the username/password in your config file.
I think it does!
I am not sure if Microsoft is also depreciating SMTP on local exchange server. So it depends on you exchange version. I would say that if you are able to start a telnet session … Did you tried these settings?
