Unitrends and Office365
-
@ajstringham said:
@Dashrender I am not sure about that but if it's on port 25 that would indicate to me it's off by default. FWIW
By your own discoveries and what @scottalanmiller has said - it does not appear the unitrends box even supports it at all. So I'm sure you're right - it's off because it's not there
-
@dashrender Yea, it's just weird because I've been told by the installations technical lead specifically that it works on their system (they use Office365) but again, I believe that they have a relay setup and he may be confusing that. Other senior installers that I've talked to have said they aren't aware of it being supported at this time. shrugs
-
@ajstringham said:
@dashrender Yea, it's just weird because I've been told by the installations technical lead specifically that it works on their system (they use Office365) but again, I believe that they have a relay setup and he may be confusing that. Other senior installers that I've talked to have said they aren't aware of it being supported at this time. shrugs
That's not what you said up above. When you quoted them they very implicitly said that it did not support it. You then changed the words around and said that it did. You've delivered two different messages from them. If they said "relay" then they clearly told you that there was no support.
-
The relay is everything. It's like saying you car can fly.... When you pack it in a crate and put it on an airplane. It's the airplane that flies. The car is cargo.
Unitrends supports the relay, but not Office 365. The relay supports Office 365.
-
@scottalanmiller said:
@ajstringham said:
@dashrender Yea, it's just weird because I've been told by the installations technical lead specifically that it works on their system (they use Office365) but again, I believe that they have a relay setup and he may be confusing that. Other senior installers that I've talked to have said they aren't aware of it being supported at this time. shrugs
That's not what you said up above. When you quoted them they very implicitly said that it did not support it. You then changed the words around and said that it did. You've delivered two different messages from them. If they said "relay" then they clearly told you that there was no support.
The installers themselves (several) confirmed what I was understanding which was that Office365 is not supported at the moment.
The installers technical lead was adamant that it is as he said they are using Office365 native with their internal appliances. He server he posted though for what they use wasn't smtp.office365.com. It was a bunch of subdomains ending in outlook.com so I'm going to assume it's a relay. He also posted in the chain a KB (internal only at this point) article that shows how to change the port from 25 to 587. So far I have not been successful at getting it to work so I feel that kind of confirms my relay theory and that he may be mistaken in his understanding of possibly how it was explained to him or how he interpreted it. FWIW -
@scottalanmiller I understand. But he was saying that changing some settings was supposed to allow you to use Office365 like someone uses their on-premise Exchange, which is confirmed to work natively no problem (on-premise Exchange). That's what I'm saying.
-
Email support has always been an issue. Would not be surprising if they weren't aware of what was or was not working.
We've reported in SW and it was confirmed not to be working. So, in theory, they are aware.
-
@ajstringham said:
@scottalanmiller I understand. But he was saying that changing some settings was supposed to allow you to use Office365 like someone uses their on-premise Exchange, which is confirmed to work natively no problem (on-premise Exchange). That's what I'm saying.
Even on premise doesn't work properly. You have to disable security for it to work. Office 365 just doesn't allow to violate that best practice.
-
@scottalanmiller I've never seen you have to disable security for on-premise Exchange. I would know.
-
@ajstringham said:
@scottalanmiller I've never seen you have to disable security for on-premise Exchange. I would know.
You do. Obviously, as the issue is lacking TLS.
-
@scottalanmiller said:
@ajstringham said:
@scottalanmiller I've never seen you have to disable security for on-premise Exchange. I would know.
You do. Obviously, as the issue is lacking TLS.
That would be an interesting question to bring up among the installations team. I'm going to get some confirmation on this. I'll update back shortly.
-
Scott, what do you mean disable security? Surely Office 365 does not require TLS for email?
Do you mean that the Unitrends can't act as a client of O365 because it can't send via TLS? So the disabling of security in an on premise Exchange setup you mean to say that you have to allow unauthenticated (or at least plain text authentication) for on prem to work? -
As far as Office365 goes:
http://office.microsoft.com/en-us/outlook-help/settings-for-pop-and-imap-access-HA102908389.aspxAs far as on-premise Exchange goes, I've never seen or been told you have to disable security of any kind. That's what's confusing me. Why would on-premise work but not Office365? Something just isn't adding up. Working on getting definite answers now.
-
@ajstringham I bet that it's because the Unitrends box can't do secure POP, only insecure POP. It all hinges on the fact that Unitrends probably doesn't have the features installed to allow TLS connections.
-
@Dashrender said:
@ajstringham I bet that it's because the Unitrends box can't do secure POP, only insecure POP. It all hinges on the fact that Unitrends probably doesn't have the features installed to allow TLS connections.
Unitrends has no reason to use POP. It doesn't receive email. Only sends out reports.
-
@ajstringham said:
@Dashrender said:
@ajstringham I bet that it's because the Unitrends box can't do secure POP, only insecure POP. It all hinges on the fact that Unitrends probably doesn't have the features installed to allow TLS connections.
Unitrends has no reason to use POP. It doesn't receive email. Only sends out reports.
Which leads to something I've never really understood. When using POP/SMTP clients, SMTP is used to send the email to a local(ish) server. Why can't the client send directly to the receiving side? This implies some sort of difference in client SMTP vs Server SMTP.
??
-
@Dashrender said:
Scott, what do you mean disable security? Surely Office 365 does not require TLS for email?
Do you mean that the Unitrends can't act as a client of O365 because it can't send via TLS? So the disabling of security in an on premise Exchange setup you mean to say that you have to allow unauthenticated (or at least plain text authentication) for on prem to work?Office 365 certainly does require TLS. And on premise should always have to. That's been best practice for a long time.
-
@Dashrender said:
Scott, what do you mean disable security? Surely Office 365 does not require TLS for email?
Do you mean that the Unitrends can't act as a client of O365 because it can't send via TLS? So the disabling of security in an on premise Exchange setup you mean to say that you have to allow unauthenticated (or at least plain text authentication) for on prem to work?Yes. For Unitrends only clear text works.
-
@ajstringham said:
As far as Office365 goes:
http://office.microsoft.com/en-us/outlook-help/settings-for-pop-and-imap-access-HA102908389.aspxAs far as on-premise Exchange goes, I've never seen or been told you have to disable security of any kind. That's what's confusing me. Why would on-premise work but not Office365? Something just isn't adding up. Working on getting definite answers now.
@ajstringham said:
As far as Office365 goes:
http://office.microsoft.com/en-us/outlook-help/settings-for-pop-and-imap-access-HA102908389.aspxAs far as on-premise Exchange goes, I've never seen or been told you have to disable security of any kind. That's what's confusing me. Why would on-premise work but not Office365? Something just isn't adding up. Working on getting definite answers now.
Lots of details are left out. You know that TLS isn't supported. So you know that requiring it has to be disabled. So just put two and two together. You already have the answer, just not spelled out.
-
@Dashrender said:
@ajstringham said:
@Dashrender said:
@ajstringham I bet that it's because the Unitrends box can't do secure POP, only insecure POP. It all hinges on the fact that Unitrends probably doesn't have the features installed to allow TLS connections.
Unitrends has no reason to use POP. It doesn't receive email. Only sends out reports.
Which leads to something I've never really understood. When using POP/SMTP clients, SMTP is used to send the email to a local(ish) server. Why can't the client send directly to the receiving side? This implies some sort of difference in client SMTP vs Server SMTP.
??
I don't follow your question. SMTP is SMTP. What is the client and receiving sides in your question?
