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

jhyiesla used Ask the Experts™
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?
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
that has to be an exchange issue I have a forwarding set up in gmail and my ISP and they still work fine.

Matches: from:(
Do this: Forward to
 and I have a forwarding set up through hostmonster forwards to

you could set up the gmail account just to forward the msg to the group.  
note I am using pix and not text
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  within 365 so it comes through as a message and not a email?
Announcing the Winners!

The results are in for the 15th Annual Expert Awards! Congratulations to the winners, and thank you to everyone who participated in the nominations. We are so grateful for the valuable contributions experts make on a daily basis. Click to read more about this year’s recipients!

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.
We solved the issue.  What it turned out to be was that the return-path was pointing to the real sender and not the distribution list. Verizon was happy to accept a message sent directly from the senders domain to my cell email, but not when it was in a forwarding header. I changed the attribute in the distribution list for reportToOriginator to not set (it was TRUE) and I changed reportToOwner to True.  The owner is a member of my domain. Now when the help desk sends one we send it out to Verizon with a return path of one of our "users" instead of their domain and it works fine.
We figured it out ourselves in a way that we could continue to use our established processes.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial