Migrating mailboxes Exchange 2010 to 365, e-mail delivery failed

We are currently in a hybrid configuration with 2010 and 365. I have migrated one mail box to test, but now when I try to e-mail from that box to internal and external users I get this undeliverable message:
Generating server: BY2PR05MB630.namprd05.prod.outlook.com
[email protected]
Remote Server returned '< #5.7.0 smtp;550 5.7.0 Proxy session setup failed on Frontend with '554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain'>'
[email protected]
Remote Server returned '< #5.7.0 smtp;550 5.7.0 Proxy session setup failed on Frontend with '554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain'>'
Original message headers:
Received: from BY2PR05MB631.namprd05.prod.outlook.com (10.141.218.20) by
 BY2PR05MB630.namprd05.prod.outlook.com (10.141.218.13) with Microsoft SMTP
 Server (TLS) id 15.0.921.12; Tue, 22 Apr 2014 17:46:14 +0000
Received: from BY2PR05MB631.namprd05.prod.outlook.com ([127.0.0.1]) by
 BY2PR05MB631.namprd05.prod.outlook.com ([10.141.218.20]) with Microsoft SMTP
 Server id 15.00.0921.000; Tue, 22 Apr 2014 17:46:13 +0000
Content-Type: multipart/mixed;
            boundary="_000_10047ccea0ec4ac6b152ab717cee271fBY2PR05MB631namprd05pro_"
From: User <[email protected]
>
To: user <[email protected]>
Subject: FW: SRX614042290246126ID -
Thread-Topic: SRX614042290246126ID -
Thread-Index: Ac9eUriGOe4zLpjESEeTsp1IfSBH8AAAAict
Date: Tue, 22 Apr 2014 17:46:13 +0000
Message-ID: <[email protected]ok.com>
References: <[email protected]>
In-Reply-To: <[email protected]>
X-MS-Has-Attach:
X-MS-Exchange-Inbox-Rules-Loop: [email protected]
X-MS-TNEF-Correlator: <[email protected]ok.com>
x-ms-exchange-parent-message-id: <[email protected]>
auto-submitted: auto-generated
x-ms-exchange-generated-message-source: Mailbox Rules Agent
x-forefront-antispam-report: SFV:SKI;SFS:;DIR:INB;SFP:;SCL:-1;SRVR:BY2PR05MB630;H:BY2PR05MB631.namprd05.prod.outlook.com;FPR:;LANG:en;
MIME-Version: 1.0
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-OriginatorOrg: achievesd.org
X-OrganizationHeadersPreserved: BY2PR05MB630.namprd05.prod.outlook.com

Also, since you have tried that for your test environment, how you are proceeding the hybrid migration ?
You can get better help by using
exchange server deployment assistant for hybrid deployment migration which auto configure the all setup according to our exchange environment.
Moreover, here is another appreciable
resource which can be a good approach to proceed migration from exchange 2010 to office 365.

Similar Messages

  • OWA still lands at Exchange 2010 for users migrated from Exchange 2010 to 2013

    I never had any issues with OWA redirection for a few users that I migrated from Exchange 2010-2013 initially. For users that I am migrating in the past few days, the OWA 2013 is landing on Exchange 2010 despite the mailbox being successfully migrated to
    Exchange 2013.
    Troubleshooting:
    1. I have restarted the IIS Services
    2. I have restarted MSExchangeOWAAppPool.
    3. I have also checked the homeMDB attribute of the 2013 migrated user with the Exchange 2013 database.
    I would really appreciate if anyone could share their experiences on similar issues.

    I have checked it, the migration status is completed. In regard to the namespaces, both CAS 2010 and 2013 are set to mail.domain.com; CAS 2013 is the internet facing. I have also checked the internal access for OWA, it's the same scenario. Migrating them
    back to 2010 and 2013 won't resolve the issue in my case, because the issue persists for every new user that I am migrating.
    I recently found the following when I login with a user who is not effected and then logout:
    1. Login in back with the affected user without closing the browser or clearing the cache, it lands at CAS 2013 OWA.
    2. However, I get the below listed error message when I logout. 
    Your request couldn't be completed.
    Click here to continue working.
    This may have occurred for security reasons or because your session timed out.

  • Migrating From Exchange 2010

    I am in the process of migrating from Exchange 2010 to Exchange 2013.  I have all mailboxes migrated to Exchange 2013 and am ready to eliminate Exchange 2010 in its entirety, but I am unsure about public folders.  We have no public folders other
    than the default ones generated during the Exchange 2010 installation.  I can't find anything in any of the migration guides that explain what I need to do in this case.  Do I need to migrate anything, or can I just uninstall Exchange from the server
    and ignore the default public folders?

    Thanks.  We had one person using Outlook 2003 years ago, but that has since been replaced with Outlook 2010.  I was able to remove the "Calendar" folder that appeared in the Public Folder Manager (took me a while to see the "Delete"
    link) and was able to proceed.  It does not appear that I have caused any problems.

  • Planning a migration from Exchange 2010 to Exchange 2013

    Hello,
    I am planning a migration from Exchange 2010 to Exchange 2013 and I was wondering if there was a good guide on the UM migration. I haven't found one that isn't confusing as heck.

    Hello,
    Is there any update?
    If
    you have any feedback on our support, please click here
    Cara Chen
    TechNet Community Support

  • Migrated to Exchange 2010, Contacts and Calender gone in WP8

    Just migrated to Exchange 2010 from 2003.
    In Outlook Everything looks ok, same with OWA (as far as I can tell.
    Problems is with Windows Phon 8.
    Neither Contacts nor Calendar will synchronize.
    Both are empty on the phones, however Emails synchronize with out any problems
    Any suggestions where to start looking.
    I have tried to delete the accounts on the WP's, and recreate them, with no luck.
    The server is a single server.

    Ok, done that, here is the results:
    RunspaceId                    : 20e39deb-6133-4de1-ad1b-5b982c021f43
    FirstSyncTime                 : 2014-07-30 13:39:00
    LastPolicyUpdateTime          : 2014-07-30 16:11:40
    LastSyncAttemptTime           : 2014-07-30 17:05:08
    LastSuccessSync               : 2014-07-30 17:05:08
    DeviceType                    : WP8
    DeviceID                      : 273D0C36714C16847613DFA08B42FAE1
    DeviceUserAgent               : MSFT-WP/8.0.10517
    DeviceWipeSentTime            :
    DeviceWipeRequestTime         :
    DeviceWipeAckTime             :
    LastPingHeartbeat             :
    RecoveryPassword              : ********
    DeviceModel                   : RM-875_eu_euro1_267
    DeviceImei                    : xxyyzz
    DeviceFriendlyName            : 909
    DeviceOS                      : Windows Phone 8.0.10517
    DeviceOSLanguage              : Swedish
    DevicePhoneNumber             :
    MailboxLogReport              :
    DeviceEnableOutboundSMS       : False
    DeviceMobileOperator          :
    Identity                      : office.company.se/Users/my.self/ExchangeActiveSyncDevices/WP8§273D0C36714C16847613DFA08B42FAE1
    Guid                          : f2ece819-d8a4-48e3-bbf3-e7c663ed297b
    IsRemoteWipeSupported         : True
    Status                        : DeviceOk
    StatusNote                    :
    DeviceAccessState             : Allowed
    DeviceAccessStateReason       : Global
    DeviceAccessControlRule       :
    DevicePolicyApplied           : Default
    DevicePolicyApplicationStatus : PartiallyApplied
    LastDeviceWipeRequestor       :
    DeviceActiveSyncVersion       : 14.1
    NumberOfFoldersSynced         : 6
    SyncStateUpgradeTime          :

  • Exchange 2003 with Windows Server 2012 DC's only. Migrate to Exchange 2010.

    I have the following situation:
    An Exchange 2003 SP2 server in an 2003 FFL and DFL domain with 2 Windows Server 2012 DC's. There are no Windows Server 2003 DC's anymore. Exchange 2003 is still functioning properly, but the eventlog is showing me some errors about LDAP which is unable to
    find an old 2003 DC.
    I know this is not supported, so we want to migrate to Exchange 2010 as soon as possible.
    What is the best way to do this? Will coexsitence still work? Do I have to add an 2003 DC's again?
    Please advice. Thank's in advance!

    Oh thank GOD I found this thread!
    I am facing a similar situation:
    http://social.technet.microsoft.com/Forums/exchange/en-US/9a8bc14b-1a45-4b8b-ac3a-38d63e66a7da/exchange-predeployment-analyzer-exchange-2010-compatibility-check-does-not-recognize-windows?forum=exchangesvrdeploylegacy
    And this is the first post I have seen marked as an answer by a Microsoft Contingent Staff affiliated person.
    Thanks Steve and Simon, you have saved me a bunch of grey hairs.
    C.
    "Time is an illusion, Lunchtime, doubly so..." - Ford Prefect

  • Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

    Hello,
    we are having a problem with a few Outlook 2010 Clients that have two Exchange accounts setup in one profile. One account is connecting to the company's Exchange 2013 Server, the second account is connecting to an external provider's Exchange 2007 infrastructure
    using Outlook Anywhere.
    The companies Exchange 2013 was recently migrated from Exchange 2010 and this is the point where the problem started.
    Some users are no longer able to send using the external Exchange 2007 account. When they try they are receiving an NDR with the following error message:
    #554 5.6.0 STOREDRV.Deliver; Corrupt message content##  from the external provider's servers.
    When I setup a profile containing only the external provider's mailbox everything works fine until I am adding the company's Exchange 2013 back in at which point the same error appears.
    We have no problems using the company's Exchange 2013 servers.
    Does anyone have an idea what causes this and how to resolve it? The external provider is uncooperative in troubleshooting so we are left with the problem.
    Thank you
    Sascha

    Hi,
    The problem should be related to the External Exchange 2007.
    Please refer to this kb below:
    http://support.microsoft.com/kb/2203381/en-us
    This problem occurs when the email message is a multipart/mixed MIME message which contains a text/plain body and an application/applefile body.  If the corresponding body is not a real application/applefile body, the Exchange Server 2007 server considers
    that the email message is invalid. Therefore, it generates the NDR. However, Exchange Server 2010 can deliver this kind of email message successfully.
    To resolve this problem, you should let the External Provider install the following update rollup:
    2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
    Hope this helps.
    Thanks,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • Yosemite mac mail drowning in mail delivery failed messages I didn't send!

    babs bellNov 14, 2014 7:03 PM
    Since upgrading to Yosemite, I am getting hundreds (tens of thousands this week!) emails that read:
    From: Mail Delivery System
    Subject: Mail delivery failed: returning message to sender
    But I didn't send any of the emails! I've spent this entire week deleting them, working on phone with my server who claims to have fixed it (NOT!), and 5 hours on phone support with Apple today. Still happening. There must be a setting that is screwed up in Yosemite, eh? Who can help me? Using Mac Mail on Mac Book Pro. I'm drowning here! GLUG. Thanks!
    Edit

    Did all of that with Apple and they nor my server thought this was the problem, nor did they get it resolved. I'm wondering if there's a rule in Mail preferences that I accidentally deleted that could be the cause. There were two rules and neither made any sense to me but as soon as I deleted the first one, I realized I probably shouldn't have. And there's been a huge problem since...not sure that's why but I must find the resolution. I did have genieo somehow installed so Apple got it uninstalled and did tons of things to my system to clean this and that. BUT the problem remains. If you use mac mail and Yosemite, can you check the two rules that automatically were in the mail preferences window to tell me what rule I deleted? Thank you so very much!

  • "Mail Delivery Failed:returning message to sender" recipients not familiar

    I am getting a "Mail Delivery Failed" message. The address' that failed are to recipients I am not familiar with and have not tried to email. Has my email been hijacked?

    I'm getting the same problem ... only it happens to anyone who sends a message TO me. This only happens on my .mac address --- not other email addresses that I use. It's as if the .mac smtp code is ADDING a bcc to any message sent to me! All the comments to date have been less than encouraging - surely SOMETHING can be done about this! No?

  • Mail delivery failer Command rejected 550 5.7.1

    Product: Officejet 6500A
    OS: Windows XP
    First time installation
    All indications show that the printer connected to ePrintCenter, but still I get an mail delivery failer Command rejected 550 5.7.1
    I tried everything that appears on the forum.
    Please help

    same by me ... no EPRINT is working
    hpeprint.com #<hpeprint.com #5.7.1 smtp;550 5.7.1 Command rejected> #SMTP#

  • Mail delivery failed

    eprint center shows computr connected email address is allowed to send email to printer but when i send email get mail delivery failed  this is a permanent error 550 5.7.1 command

    For those who are experiencing ongoing issues with their web services, you can attempt to try the following steps that may help resolve your problems.
    1.) Completely shut down your printer and restart it
    2.) If you have prints that have not printed, log into ePrint Center (or create an account if you do not have one) and then look for your printer status. If printer status is green but you still have pending jobs, delete the pending jobs one at a time (Starting with the oldest first). There may be a print job stuck in the queue that further restricts other jobs from completing.
    a. If option 1 or 2 above still doesn’t work, removing web services and re-adding web services will cause the printer to reattach to the cloud.
    b. Please note that if you attempt option 3, you will get a new eprint email address (and lose your custom one with no ability to get it back) furthermore, you will need to re-add your printer back to your ePC account.
    I am an HP employee

  • Mail delivery fail but still received mail

    hi
    i keep receiving 2 messages straight after receipt of the original which is readable..
    1st message: mail delivery fail
    2nd message: undeliverable
    i have no problem reading the original message
    regards
    kel

    This is a problem with your recipients ISP not delivering the email, or with Comcast in not sending it once it reaches their mail servers. You should check with your recipients to find out if they use the same ISP, and have them check with the ISP to ask why mail sent from a Comcast account is not being delivered.
    If this affects all your recipients (assuming there are many more than just the two you mentioned), then its a Comcast issue and you should call them and insist they make any necessary changes so everyone can receive email from you. If it only affects those two recipients, they would need to call their ISP and have them make the necessary changes.

  • Thunderbird Issue. Thousands of inbound e-mails from "Mail Delivery Failed" from people to whom I've never attempted to send an e-mail.

    All inbound e-mails are going directly to "TRASH" how do I fix this? I also have has thousands of inbound e-mails from "MAIL DELIVERY FAILED" involving people to whom I have never attempted to send an e-mail. Whats the cure? I have to use Time Warner as an internet connection and there is a duplicate of about half of what I'm getting in inbound traffic on Thunderbird.

    The inbound is Backscatter see http://en.wikipedia.org/wiki/Backscatter_%28email%29
    The trash issue is most likely the SPAM tool that comes with your anti virus program. Try disabling the tool in the anti virus suite and see how you get on.

  • Migrate Exchange 2010 to 2013 External Mail Flow

    Dear All,
    I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
    2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
    The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
    How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
    How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
    Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
    Kindly guide if any thing missing that need to address during start the migration activity.
    Thanks in Advance

    Hi ,
    Sorry for delay.
    Question : Thanks for your valuable response. On
    point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
    Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
    2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
    For mailbox connectivity issue in exchange 2013 :
    1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
    2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
    2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
    needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
    3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
    service is not reaching the proxy server if you have on your network.
    In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
    on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
    4.please share me the output for the below mentioned command.
    get-ClientAccessServer -Identity “server name”  | fl AutodiscoverServiceInternalURI 
    5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
    6.On which operating system version those outlook 2007 clients are installed?
    Please reply me if anything is unclear.
    Thanks & Regards S.Nithyanandham

  • I need help with a migration from Exchange 2010 to 2007

    Hi All,
    I need help migrating mailboxes from a separate forest / domain using exchange 2010 to our Exchange 2007 SP3 servers..  I am following this procedure:
    1. On source server, create a mailbox user, test01.
    2. On target server, run the following command to move the AD account:
    Prepare-MoveRequest.Ps1 -Identity [email protected] -RemoteForestDomainController FQDN.source.com -RemoteForestCredential $Remote -LocalForestDomainController FQDN.target.com -LocalForestCredential $Local -UseLocalObject -Verbose"
    3. Run the ADMT to migrate the password and SID history.
    4. Run the following command to move the mailbox:
    New-MoveRequest -Identity '[email protected]' -RemoteLegacy -RemoteTargetDatabase DB03 -RemoteGlobalCatalog 'GC01.humongousinsurance.com' -RemoteCredential $Cred -TargetDeliveryDomain 'mail.contoso.com'
    (Changed all the details obviously)
    It gets to 95% and shows this error
    01/12/2014 12:47:24 [EX2K10] Fatal error UpdateMovedMailboxPermanentException has occurred.
    Error details: An error occurred while updating a user object after the move operation. --> Active Directory operation failed on DC.DC.COM . This error is not retriable. Additional information: The parameter is incorrect.
    Active directory response: 00000057: LdapErr: DSID-0C090A85, comment: Error in attribute conversion operation, data 0, vece --> The requested attribute does not exist.
       at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.UpdateMovedMailbox(UpdateMovedMailboxOperation op, ADUser remoteRecipientData, String domainController, ReportEntry[]& entries,
    Guid newDatabaseGuid, Guid newArchiveDatabaseGuid, String archiveDomain, ArchiveStatusFlags archiveStatus)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass3c.<Microsoft.Exchange.MailboxReplicationService.IMailbox.UpdateMovedMailbox>b__3b()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.UpdateMovedMailbox(UpdateMovedMailboxOperation op, ADUser remoteRecipientData, String domainController, ReportEntry[]& entries,
    Guid newDatabaseGuid, Guid newArchiveDatabaseGuid, String archiveDomain, ArchiveStatusFlags archiveStatus)
       at Microsoft.Exchange.MailboxReplicationService.RemoteMoveJob.UpdateMovedMailbox()
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.UpdateAD(Object[] wiParams)
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    Error context: --------
    Operation: IMailbox.UpdateMovedMailbox
    OperationSide: Target
    Primary (b5373e49-6a06-41f4-990e-27807c7a57f3)
    01/12/2014 12:47:24 [EX2K10] Relinquishing job.
    Any ideas what i can do about this? 

    Hi,
    From your description, I recommend you follow the steps below for troubleshooting:
    Open the problematic user in AD and check the Email Address. Verify if you can open or edit the x400 address. If no, remove the x400 address and recreate it. If yes, ensure that the name is spelt correctly. After that, continue to move the mailbox and check
    the result.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

Maybe you are looking for