Avaya IP Office VM to email issues

[chadphoneguy]

We've had some issues with a handful of customers lately with Avaya IP Office that have embedded VM and use VM to email that has stopped working now that most email providers are blocking 3rd party apps to crack down on email spamming. We used a work around called "app passwords" with 2 party verification and it generates a long code for a password for the SMTP email password. It worked on 1 customer and still works today for them. But now since then, we've tried to duplicate that with several other customers that are having the same issues and cannot make it work.
Have any Avaya IP Office techs here found any work arounds to this issue with Avaya IP Office since the email providers are now blocking 3rd party apps? Avaya tech support through our authorized Avaya distributor has been no help. It's been on several different releases, 9.1, 10.1 and 11.1. The release doesn't seem to matter. We've even upgraded one to a higher release on the same level with no luck. Interested if anyone else is having issues lately with this?

 

[jerrymac]

I ended up switching to using a domain I created just for services related email thru a DDNS provider that offered basic email services. I just set up the email address to somehow reflect the users company name along with a PBX designation in it, that way I had full control of both the PBX side and server side of things.

So far so good and no more headaches for now. Customers don't seem to really care as long as they are getting their message notifications but between Microsoft and Google their stand alone email services are getting impossible to deal with at times and some of the older systems don't play well with the newer security requirements.

 

[Kibbs308]

hMail loaded locally works great, have no issues with it at all.

 

[Shaun E]

We use Google Workspace for email and just use their SMTP Relay service with the IP address the IPO is on whitelisted (it's a static IP).

Then the IPO is just configured to relay to smtp-relay.gmail.com on port 587. No authentication required and works just fine.

 

[eaglepromopro]

I use

relay.appriver.com

or

8.31.233.167

The EMAIL FROM ADDRESS is a problem sometimes. It wont accept it so I just use one with xxxxx@COX.NET and it seems to accept anything from COX.NET