Our relay server only accepts connections with Basic Authentication in combination with TLS,
or Integrated Windows Authentication (SBS 2008 server).
I can see I can specify a username + password for email notifications (running 4.1),
but it seems it doesn't support TLS. It also does not seem to support the
'Integrated Windows Authentication'.
I could be wrong though.
Is there a work-around, or will this feature be added to a newer release ?
1. Reconfigure you mail server to allow mail from the IP address of your Veeam server to be accepted.
2. Assuming you receive mail from the Internet, there must be something that's accepting non-TLS mail, perhaps a Internet Gateway or firewall. Configure your Veeam server to use this host to relay mail
3. Install stunnel on you Veeam server and point Veeam to it. Stunnel is a SSL/TLS proxy. You can configure it to listen, unencrypted on a local socket on the Veeam server, tell Veeam to use this local socket as the "mail server", and stunnel will create a TLS connection to the mail server. I recently helped a friend set this up to support some legacy scanners that sent scans as PDF's via email but didn't support TLS. Works great and it's free.
I've been trying to do option 3 but getting Unable to connect to the Remote Server Error, even though going to the Local Host.
I've seen another post that this could relate to allowing Veeam processes through AV on the server.
I'm tryng to get this setup to forward emails to Office 365. A guide on this would be a great help, knowing how many companies are moving to Office 365.
I don't see why I should have to install a 3rd party tool to make this compatible with Office 365.
I'd like this raised so that it can be considered for a future version or patch release please.