Yes, we're aware of this problem and have a separate task to support o365 SMTP. Currently I can't recommend using that until we officially introduce this type of notification service.
Well, Matt. I have a problem now. It was working before on the MSP portal's SES. I only changed it because I wanted the emails to route through our 365 service going forward. Now that I realize, after the fact, that this isn't supported (hint hint--it would have been nice to read a blurb about what SMTP relay features are supported and what are not beforehand), I have a broken notification service. Please switch it back from the back end since I cannot do this from my side. Ticket Id : #254044
I have the same problem with SMTP setup, opened ticket #266043 with Tech Support. The help article Nick (support tech) sent, doesn't open, so I'm stuck:
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
Thank you very much for noting us, could you please confirm that the notifications work well now, as they should have been reverted back to our notification service for your MSP account?
Is there any update on this? DMARC is forcing me to check spam folders everyday for my e-mails coming from CBL and I would like to setup a custom SMTP server.
Has anyone else found a work around if DMARC is setup on your domain to avoid junk? Setting up a connector also requires TLS.
As discussed, option box "SSL" does include "TLS" support as well. Seems like the root of the issue is incorrect domain in the "From" field. Added your email to the respective task in order to make our service more clear in terms of setup.
So I see this problem was discussed 10months ago, we use mspbackups as well and have problems with sending notifications as only port 25 works well nothing else. START/TLS 587 or SSL 465 doesn't work till today!!! Tried to use MDaemon and Microsoft relays none of the worked.