Feature Request: Accept Office365 domains as SMTP server

[carlo.van.orsouw]

Hi everybody,

i recently upgraded one of our clients from exchange to office365. Normally all internal status, alerts and scanning mails go through the internal mail server relay..

Since Exchange is being dismantled.. i need another way to accomplish this. Since most providers quit relayservices i have to use the relay server from Office365. This works for most cases.

The only thing is that Veeam in the latest version is not accepting my mx record domain name that is supposed to be used as the SMTP address in clients.

This name is in the following form: domainname-com.mail.protection.outlook.com

Veeam is not accepting this as an SMTP server, but i don't know why.. is it the length or the dash in the name.. Or does it only accept IP addresses.. For now i Pinged the domain name and entered that IP address in the SMTP field.. This works but is not the way i want it..

I assume that more and more people are going to use this way of relaying emails. And since many other systems just accept the format i also assume that it is not that big of a problem to accept such domainnames.

Kind regards,

Carlo van Orsouw
IT Performance Group
The Netherlands

[Tondas]

Hello,
i use office365 account for notification for few months without problems.

https://www.dropbox.com/s/qbyi6bg7dgiy3 ... P.png?dl=0

Tonda Strnad

[foggy]

Carlo, what do you mean by not accepting, do you see any error message while trying to test connection?

[carlo.van.orsouw]

Hello,
i use office365 account for notification for few months without problems.

https://www.dropbox.com/s/qbyi6bg7dgiy3 ... P.png?dl=0

Tonda Strnad

Thanks for your response.. i tried my relay server (without login that is) not the short mailserver name. But that is probably a good alternative..

I use the relay server for all my alerting.. it is normally simple and easy to configure.

kind regards,

Carlo

[carlo.van.orsouw]

Carlo, what do you mean by not accepting, do you see any error message while trying to test connection?

Yeah, kind of..

i think it doesn't accept the dash (-) in the relayserver name.. it is the MX server name..

and it is in this form: domainname-com.mail.protection.outlook.com

this is not accepted right now..

[foggy]

I've brought this up with QC, we'll see whether this is a UI issue of not accepting the dash in the name.

[foggy]

Dash seems to be ok in this field. Doesn't this case look similar (or does your server name have A record in DNS?)?

Probably, contacting technical support for a closer look is required here.

[Eamonn Deering]

Running into a similar issue for outlook.com to an outlook.ie account.
An Azure VM running Veeam B&R 9.5 SP2

Using Veeam GUI (General Options, E-Mail Settings, advance) with auth, SSL and port 587 (also failing on 25) it won't send emails through
smtp-mail.outlook.com or its IP4 address

but it does work for
smtp.office365.com

Using powershell (new-object Net.Mail.MailMessage and new-object Net.Mail.SmtpClient) to sent through smtp-mail.outlook.com on the same server works fine.