Link to home
Start Free TrialLog in
Avatar of jhyiesla
jhyieslaFlag for United States of America

asked on

Issue with email forwarding to Verizon cell as text with Office 365

For years our help desk has been alerting us to high priority tickets by sending an email to a distribution group in Exchange and then that's been forwarded to an email address associated with our cell phone carrier.  We've discovered recently that changes Verizon has made with their Spam filtering is causing this to be blocked so we're not getting text messages from them.

After much testing Verizon has confirmed that we suspected. They have a couple of possible solution, but we're not sure they're even possible. One of them is to reconfigure Office 365 in this situation to remove any of the forwarding headers so that it makes a new clean email to the cell phone email address. Before moving to Office 365, Exchange would accept the email from the help desk to the group and then send it out from the group to the group member, which is a contact with the cell phone email address in it.  What Office 365 does is to keep the original sender and then forward it out. We originally had a problem with the relay aspects of this, but I fixed that in our email filtering system by allowing that as a relay. I tested this back in January and it worked fine. So Verizon has made a change since then that is causing this. Since this change is something global for all customers to help hold down on phone spam, they're not going to change anything on their side.

So, is what they're suggesting even possible?  Can I have Office 365 basically make a new email without all of the forwarding header info to send to the cell phone email address?
SOLUTION
Avatar of HAVARD7979
HAVARD7979
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jhyiesla

ASKER

We thought about doing that exact thing, but it does come with other issues for us. I'd rather solve it in Office 365, but that is an option.
have you  tried sending it to the @vzwpix.com  within 365 so it comes through as a message and not a email?
No, but I'm not sure that would fix the issue. We're currently sending it to an internal distribution group and that group always has one member, but that changes with the person on-call.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
We figured it out ourselves in a way that we could continue to use our established processes.