Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Office 365 Migrated mailboxes not receiving External mail

Posted on 2014-09-18
6
Medium Priority
?
6,465 Views
Last Modified: 2014-09-19
After setting up Exchange Online (Office 365) with Exchange 2010 SP3 Hybrid, my migrated remote mailboxes will not receive external email. They can receive email from other Online, cloud users. All the mailboxes created in Office 365 can receive external email. In doing a mail trace, -EventID 'DSN' the Source shows 'Routing'. I eventually get 'Delivery is Delayed' message. Any thoughts?
0
Comment
Question by:Anthony K O365
  • 3
  • 3
6 Comments
 
LVL 45

Expert Comment

by:Vasil Michev (MVP)
ID: 40330812
Where is you MX pointing at? If it points on-prem, check if they receive emails from on-prem users - if not, the issue is with the connector, most likely the certificate.

Also, try sending directly to the user@domain.onmicrosoft.com address.
0
 

Author Comment

by:Anthony K O365
ID: 40331223
MX record is point to our On prem Exchange. Migrated users (Online) can not receive email from On Prem senders nor Internet senders. However, they can receive email when using their user@domain.onmicrosoft.com address.

You stated the issue may be with the connector. Do you mean the Receive connector at Exchange Online, or the Sender Connector On Prem? The settings for Inbound connector at O365 is: Sender Domain=*, Security=Require TLS=No, Sender IP= same IP being used for Webmail.Domain.org (therefore, no certificate required) We are using Wild Card Certs On prem. Must it also be used Online?
0
 
LVL 45

Expert Comment

by:Vasil Michev (MVP)
ID: 40331330
OK, definitely an issue with the connector then. Have you traced the email from both on-prem and EO? Post the results here and also any NDRs you might have gotten. Also, the connector settings (you can even rerun the HCW to recreate them, which might as well fix the issue).

Just in case, also double-check the targetaddress attribute for any of the migrated mailboxes, it might not be correctly populated.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:Anthony K O365
ID: 40331483
The only NDR is the standard Delivery Delay every 4 hours. From On Prem trace, message just sits in the queue . The mail trace at EO shows nothing being received. The TargetAddress at On Prem shows user@domain.mail.onmicrosoft.com . I have rerun HCW a few times. Same results.
0
 
LVL 45

Accepted Solution

by:
Vasil Michev (MVP) earned 2000 total points
ID: 40332030
Can you check the SMTP logs to get the exact error details? The issue is definitely with your on-prem servers, we just need to find out exactly what is causing it.

Here's a similar issue on the community forums: http://community.office365.com/en-us/f/156/t/223336.aspx
0
 

Author Closing Comment

by:Anthony K O365
ID: 40333511
You are correct! The issue was with our On Prem network. The smtp protocol logs shows 4.2.2. error message...Delayed. The issue was that our firewall was not allowing SMTP Traffic to any of Microsoft's Online IP's. A Telnet test revealed this.  For migrated users to receive email I place this MX record  "MyDomain.mail-onmicrosoft-com.mail.protection.outlook.com"  as a smart host in my Send connector and had our Network team allow Microsoft's Online IP's in the firewall. See link below. Migrated users are now receiving External emails.


http://technet.microsoft.com/library/hh373144.aspx
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microsoft Office Picture Manager was included in Office 2003, 2007, and 2010, but not in Office 2013. Users had hopes that it would be in Office 2016/Office 365, but it is not. Fortunately, the same zero-cost technique that works to install it with …
Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
Have you created a query with information for a calendar? ... and then, abra-cadabra, the calendar is done?! I am going to show you how to make that happen. Visualize your data!  ... really see it To use the code to create a calendar from a q…
This lesson discusses how to use a Mainform + Subforms in Microsoft Access to find and enter data for payments on orders. The sample data comes from a custom shop that builds and sells movable storage structures that are delivered to your property. …
Suggested Courses

581 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question