Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Voicemail to email with Office365 working?

Status
Not open for further replies.

jayjr1105

IS-IT--Management
Jan 14, 2014
619
US
I have about 5 or so clients setup with this. I create a shared mailbox called Avaya@customername.com, create a receive connector with the client's IP address so it allows the Avaya to relay the messages without authentication. I setup the IPO with customername-com.mail.protection.outlook.com, port 25 and avaya@customername.com

This has worked for 3 or so clients. Now this week, two brand new clients will not work with this setup. I've logged into the clients sites that are still working and mirrored the settings. What gives? Anyone setup VM to Email with 365 lately?

Edit: This may be related to version 11 or higher. The clients where this is working are all on 10.1 or under.
 
You entered the external IP that the IPO/VM PRo is using to connect to O365 ?
What happens if you try to send an e-mail through telnet from the clients network?

It is also recommended to add an SPF record so e-mails don't get marked as spam.

"Trying is the first step to failure..." - Homer
 
we have ha so mch trouble getting office 365 to work reliably with IP office that we generaly recomend the customer has a local mail relay on site (this can be built on a reaspberry Pi for less than £50 if necesary).



Do things on the cheap & it will cost you dear
 
Same here! As we have a Windows server we just used the built in SMTP server.


SMTP
 
We typically can get office365 to work but if not I just suggest creating a new free gmail account. I have not ever had an issue getting a gmail account to work. Relays are fine but its just one more thing that can fail.

The truth is just an excuse for lack of imagination.
 
Gmail is my fallback. It's bulletproof until google decides to mess with less secure apps or make it mandatory, etc.
 
office365 works but not sure why you would want to use it without authentication.
I could never make it work with port 25 though

I use port 587 (then it uses TLS) and the sending name has to match the authentication name otherwise they will reject the sending of emails.

set this up this way since end of 2016 (I think) and so far no problems

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
Westi do you have notes or a KB on this. I would love to try your method. When you say sending name has to match, which type of user are you creating in 365? Something unlicensed like a shared mailbox?

Thanks in advance.
 
There's several reasons to not use authentication.

Usually you would have a relay setup for your office anyway since you have printers etc that you wanna send e-mails from.
Using a connector doesn't need O365 licenses and you can send from any e-mail address.

You can still use TLS with port 25.

[URL unfurl="true"]https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3[/url]

"Trying is the first step to failure..." - Homer
 
I have a combination of things setup from that best practices site with the exception of the SPF record which I have no control over (It's a french company with locations in the states). I have a receive connector, a shared mailbox (avaya@customer.com), an unlicensed user (avaya@customer.com), Port 25 STARTTLS used WITH user authentication. I have a reboot scheduled tonight so I'll see on Monday.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top