Hi,

I've spent the past few days reading up on the Hybrid mode facility and I got the Remote connectivity facility running okay after a few blips. I also managed to get the wizard to run through until I get to the last bit about

HCW8064 -
The HCW has completed, but was not able to perform the OAuth portion of your Hybrid configuration. If you need features that rely on OAuthhttps://technet.microsoft.com/library/dn497703(v=exchg.150).aspx, you can try running the HCW again or manually configure OAuth using these manual stepshttps://technet.microsoft.com/library/dn594521(v=exchg.150).aspx.
https://support.microsoft.com/kb/3089172

It says its not important so I carried on.

I am a bit confused though about what it can and cant do.

I am in a school by the way.

I have Azure syncing with O365 and all the students and staff are listed. When I look at the mailboxes on the O365 tab there aren't any... when I try and logon it doesn't work. I thought the beauty of this was that it offered a single point of access to your mailbox.

I have tried to move a user (I will be keeping the majority on my premises) which comes up with the error.

Data migrated:                        
Migration rate:                        
Error:                        MigrationRecipientNotFoundException: A recipient wasn‎'t found for "boysboarding@*********.co.uk" on the target. Create a recipient of the appropriate type for this migration on the target and try again.

So I tried again but this time I assigned a license in the admin console. This allows me to logon to office 365 but with an empty mailbox?? I know there are mail items in there when I login on my premises. if I try and migrate the users mailbox I get

Migration rate:                        
Error:                        InvalidRecipientTypeException: Unsupported recipient type ‎'Mailbox‎' provided. Only ‎'Mailuser‎' is supported for this migration type.

Its taken me ages to even get to this stage and now I am stuck

Dear Microsoft Community,

I have an issue and am in dear need of help:

Exchange 2013 CU11

Sent Mails get stuck in Drafts folder when sent from OWA
In Outlook they go to the Sent Mail folder but do not reach the Queue.
Only Users from Particular Databases at random times apparently are affected and only sporadically and for short periods of time (1-2 hours) after which everything stars working fine again.
If I move a Mailbox to one of the affected Databases the user starts exhibiting the Issue. Also if I move Mailbox to a database without problems the issue stops.
All databases are affected at random unrelated to the server they are on. There is one server where the Issue occurs more often than on the others.
It matters not if Mails are sent to external or internal addresses.
Only outgoing mails affected Incoming works fine.

Issue appeared immediately after an unexpected restart of the servers related to a storage outage.
I have correlated the issue with an Event:
Does anyone know what the MailSubmissionWatermarksProbe is about?
========================================================================

Log Name:      Microsoft-Exchange-ManagedAvailability/Monitoring
Source:        Microsoft-Exchange-ManagedAvailability
Date:          4/20/2016 3:52:12 PM
Event ID:      4
Task Category: Monitoring
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      S1EX2k13
Description:
Watermarks for one or more database(s) have been below the age threshold of 01:00:00 for last 02:00:00.

 Last Reported Database: Database1 
 Last Event Counter: 378203086 : 4/20/2016 1:39:33 PM 
 Watermark(s): MailboxTransportSubmissionAssistant : 377652258 : 4/20/2016 7:58:03 AM 
 Exception: Watermarks are behind for database 'Database1' 

 Diagnostic Command: Invoke-MonitoringProbe -Identity 'EventAssistants\MailSubmissionWatermarksProbe\Database1' -Server S1EX2k13 

 Command to get all unhealthy watermarks monitors: Get-ServerHealth -Identity 'S1EX2k13' -HealthSet 'EventAssistants' | ?{$_.Name -match 'MailSubmissionWatermarksMonitor' -and $_.AlertValue -ne 'Healthy'}

========================================================================
Also the submission service restarts about once or twice per hour on all servers.
========================================================================

Event ID:      7031
Computer:      S1EX2k13
Description:
The Microsoft Exchange Mailbox Transport Submission service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

========================================================================

DNS is fine and configured correctly. 
There is no Backpreasure.
There is enough space.
No performance issues.
I've been unable to corelate any other Event to the issue.

LG,


Alex D

Dear Forum Users,

I have a problem with Mail server Exchange 2013 that running with both CAS and MB. The power cut off make machine accidentally shutdown, and After starting up machine, Mail server is not able to Send/Received email. not working both internal and external. Please kindly advise me about idea of problem that possible happen, i never meet this problem before. thank you in Advance. 

Regards,

SAM

Sokneang SAM

Hi Guys,

Some confusion in RPC Client Access Server & Client Access Server.

How to Work RPC Client Access Server

Satish Chaturvedi Mob-9990806001

Hello,

the problem happens after you update to CU9 from CU8: authenticated emails from computer running WSUS and File Server Resource Manager (that autenticate using the computer account) are not running anymore. Before they was running.

This is the debug of the SMTP conversation AT THE CU8 -- RUNNING

2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,0,10.0.0.2:25,10.0.0.1:51258,+,,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,1,10.0.0.2:25,10.0.0.1:51258,*,None,Set Session Permissions
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,2,10.0.0.2:25,10.0.0.1:51258,>,"220 ITMILEX999.contoso.com Microsoft ESMTP MAIL Service ready at Tue, 23 Jun 2015 08:11:38 +0200",
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,3,10.0.0.2:25,10.0.0.1:51258,<,EHLO ITMILDC999,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,4,10.0.0.2:25,10.0.0.1:51258,*,None,Set Session Permissions
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,5,10.0.0.2:25,10.0.0.1:51258,>,250-ITMILEX999.contoso.com Hello [10.0.0.1],
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,6,10.0.0.2:25,10.0.0.1:51258,>,250-SIZE,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,7,10.0.0.2:25,10.0.0.1:51258,>,250-PIPELINING,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,8,10.0.0.2:25,10.0.0.1:51258,>,250-DSN,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,9,10.0.0.2:25,10.0.0.1:51258,>,250-ENHANCEDSTATUSCODES,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,10,10.0.0.2:25,10.0.0.1:51258,>,250-AUTH NTLM,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,11,10.0.0.2:25,10.0.0.1:51258,>,250-8BITMIME,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,12,10.0.0.2:25,10.0.0.1:51258,>,250-BINARYMIME,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,13,10.0.0.2:25,10.0.0.1:51258,>,250 CHUNKING,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,14,10.0.0.2:25,10.0.0.1:51258,<,AUTH ntlm,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,15,10.0.0.2:25,10.0.0.1:51258,>,334 <authentication response>,
2015-06-23T06:11:39.481Z,ITMILEX999\Internal,08D27B82C2B20D7C,16,10.0.0.2:25,10.0.0.1:51258,*,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
2015-06-23T06:11:39.481Z,ITMILEX999\Internal,08D27B82C2B20D7C,17,10.0.0.2:25,10.0.0.1:51258,*,CONTOSO\ITMILDC999$,authenticated
2015-06-23T06:11:39.513Z,ITMILEX999\Internal,08D27B82C2B20D7C,18,10.0.0.2:25,10.0.0.1:51258,*,,Proxy session was successfully set up. Outbound session will now be proxied
2015-06-23T06:11:39.513Z,ITMILEX999\Internal,08D27B82C2B20D7C,19,10.0.0.2:25,10.0.0.1:51258,>,235 2.7.0 Authentication successful,
2015-06-23T06:11:39.763Z,ITMILEX999\Internal,08D27B82C2B20D7C,20,10.0.0.2:25,10.0.0.1:51258,-,,Local

This is the debug after upgrading to CU9 -- BROKEN

2015-06-23T07:34:12.165Z,ITMILEX999\Internal,08D27B9E1BAF1B57,0,10.0.0.2:25,10.0.0.1:51489,+,,
2015-06-23T07:34:12.165Z,ITMILEX999\Internal,08D27B9E1BAF1B57,1,10.0.0.2:25,10.0.0.1:51489,*,None,Set Session Permissions
2015-06-23T07:34:12.196Z,ITMILEX999\Internal,08D27B9E1BAF1B57,2,10.0.0.2:25,10.0.0.1:51489,>,"220 ITMILEX999.contoso.com Microsoft ESMTP MAIL Service ready at Tue, 23 Jun 2015 09:34:11 +0200",
2015-06-23T07:34:12.462Z,ITMILEX999\Internal,08D27B9E1BAF1B57,3,10.0.0.2:25,10.0.0.1:51489,<,EHLO ITMILDC999,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,4,10.0.0.2:25,10.0.0.1:51489,*,None,Set Session Permissions
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,5,10.0.0.2:25,10.0.0.1:51489,>,250-ITMILEX999.contoso.com Hello [10.0.0.1],
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,6,10.0.0.2:25,10.0.0.1:51489,>,250-SIZE,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,7,10.0.0.2:25,10.0.0.1:51489,>,250-PIPELINING,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,8,10.0.0.2:25,10.0.0.1:51489,>,250-DSN,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,9,10.0.0.2:25,10.0.0.1:51489,>,250-ENHANCEDSTATUSCODES,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,10,10.0.0.2:25,10.0.0.1:51489,>,250-AUTH NTLM,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,11,10.0.0.2:25,10.0.0.1:51489,>,250-8BITMIME,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,12,10.0.0.2:25,10.0.0.1:51489,>,250-BINARYMIME,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,13,10.0.0.2:25,10.0.0.1:51489,>,250 CHUNKING,
2015-06-23T07:34:12.744Z,ITMILEX999\Internal,08D27B9E1BAF1B57,14,10.0.0.2:25,10.0.0.1:51489,<,AUTH ntlm,
2015-06-23T07:34:12.791Z,ITMILEX999\Internal,08D27B9E1BAF1B57,15,10.0.0.2:25,10.0.0.1:51489,>,334 <authentication response>,
2015-06-23T07:34:13.682Z,ITMILEX999\Internal,08D27B9E1BAF1B57,16,10.0.0.2:25,10.0.0.1:51489,*,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
2015-06-23T07:34:13.682Z,ITMILEX999\Internal,08D27B9E1BAF1B57,17,10.0.0.2:25,10.0.0.1:51489,*,CONTOSO\ITMILDC999$,authenticated
2015-06-23T07:34:26.949Z,ITMILEX999\Internal,08D27B9E1BAF1B57,18,10.0.0.2:25,10.0.0.1:51489,*,,Setting up client proxy session failed with error: 535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user
2015-06-23T07:34:26.949Z,ITMILEX999\Internal,08D27B9E1BAF1B57,19,10.0.0.2:25,10.0.0.1:51489,*,,"Setting up client proxy session failed with error: 451 4.4.0 Primary target IP address responded with: ""535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 10.0.0.2:465"
2015-06-23T07:34:26.949Z,ITMILEX999\Internal,08D27B9E1BAF1B57,20,10.0.0.2:25,10.0.0.1:51489,*,None,Set Session Permissions
2015-06-23T07:34:26.965Z,ITMILEX999\Internal,08D27B9E1BAF1B57,21,10.0.0.2:25,10.0.0.1:51489,*,Tarpit for '0.00:00:05' due to '535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user',
2015-06-23T07:34:32.282Z,ITMILEX999\Internal,08D27B9E1BAF1B57,22,10.0.0.2:25,10.0.0.1:51489,>,535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user,
2015-06-23T07:34:32.314Z,ITMILEX999\Internal,08D27B9E1BAF1B57,23,10.0.0.2:25,10.0.0.1:51489,<MAIL FROM:<FSRM @ contoso.com>,
2015-06-23T07:34:32.314Z,ITMILEX999\Internal,08D27B9E1BAF1B57,24,10.0.0.2:25,10.0.0.1:51489,*,Tarpit for '0.00:00:05' due to '530 5.7.1 Client was not authenticated',
2015-06-23T07:34:37.334Z,ITMILEX999\Internal,08D27B9E1BAF1B57,25,10.0.0.2:25,10.0.0.1:51489,>,530 5.7.1 Client was not authenticated,
2015-06-23T07:34:37.334Z,ITMILEX999\Internal,08D27B9E1BAF1B57,26,10.0.0.2:25,10.0.0.1:51489,-,,Local

Ciao,

Luca

Hi, please can you let me know how you have protected against the "Autodiscover Enumeration Vulnerability".  My current thoughts are around using an irule on an F5 LTM but am unsure if there is a smarter way?

many thanks

T

Tul Golan

Hello,

I changed the ssl ucc cert provider from godaddy to comodo and installed the new cert. All services are asigned to the new cert. Almost all emails on the receive connector work fine.

But the samsung printer and hrs.de seem to have problems negoatiating tls.

Patch level is CU11

checktls.com works with no errors.

Receive connector log shows this:

0:57214,+,,
1:57214,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2:57214,>,"220 Mail1.XXXXXXXX.com Microsoft ESMTP MAIL Service ready at Sat, 30 Apr 2016 15:18:59 +0200",
3:57214,<,EHLO SEC001599DDC76E,
4:57214,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
5:57214,>,250-Mail1.XXXXXXXX.com Hello [192.168.1.202],
6:57214,>,250-SIZE,
7:57214,>,250-PIPELINING,
8:57214,>,250-DSN,
9:57214,>,250-ENHANCEDSTATUSCODES,
10:57214,>,250-STARTTLS,
11:57214,>,250-X-ANONYMOUSTLS,
12:57214,>,250-X-EXPS GSSAPI NTLM,
13:57214,>,250-8BITMIME,
14:57214,>,250-BINARYMIME,
15:57214,>,250-CHUNKING,
16:57214,>,250-XEXCH50,
17:57214,>,250-XRDST,
18:57214,>,250 XSHADOWREQUEST,
19:57214,<,STARTTLS ,
20:57214,>,220 2.0.0 SMTP server ready,
21:57214,*,,Sending certificate
22:57214,*,"CN=mail.XXXXXXXX.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated",Certificate subject
23:57214,*,"CN=COMODO RSA Domain Validation Secure Server CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB",Certificate issuer name
24:57214,*,69BXXXXXXXXDE03,Certificate serial number
25:57214,*,043XXXXXXXX5E1A,Certificate thumbprint
26:57214,*,mail.XXXXXXXX.com;autodiscover.XXXXXXXX.com;mail1.XXXXXXXX.com;mail3.XXXXXXXX.com,Certificate alternate names
27:57214,*,,TLS negotiation failed with error BadBindings
28:57214,-,,Local

Hi all.

I am migrating a customer infrastructure from Exchange 2007 to Exchange 2013. The problem is about read receipts with send on behalf mail, that work differently in Exchange 2007 and Exchange 2013.

Let's suppose that user X sends on behalf of user Y.

In Exchange 2007 the read receipts arrive in user Y mailbox. In Exchange 2013 the read receipts arrive in user X mailbox (and this is a big problem for the customer).

I'm trying to change the Disposition-Notification-To header with a transport rule, but I always receive an error (You cant set header Disposition-Notification-To with value). I cannot create an Outlook rule without adding something specific in the message object or body (and it is not possible for the customer). I have not Transport Edge role in my infrastructure

Has anyone found a solution for this kinf of problems?

Thanks!
Lu

Hi,

I have a bit of a situation, hoping to reach out as google isn't getting me anywhere on this topic.

We recently gave out a smtp address tied to a distribution group which was accidentally configured to only allow messages if senders were authenticated. A few dozen external customers sent emails which were processed by our email gateway, andsuccessfully delivered to Exchange which was a surprise to me.

Once in the Exchange environment, I can see tracking logs showing its path as below:

RunspaceId              : d6fee167-5fa3-4d58-9354-b10402c9dacf
Timestamp               : 4/29/2016 9:53:34 AM
ClientIp                : 10.10.X.X
ClientHostname          : GATEWAY1
ServerIp                : 10.11.X.X
ServerHostname          : EXCHANGE1
SourceContext           : 08D36FD672846E86;2016-04-29T13:53:34.862Z;0
ConnectorId             : EXCHANGE1\Exchange Connector
Source                  : SMTP
EventId                 : RECEIVE
InternalMessageId       : 13683389
MessageId               : <bb3a65e077043968b99b37d681fc2e48@mail.hotmail.com>
Recipients              : {distribution_list@internal.local}
RecipientStatus         : {}
TotalBytes              : 41037
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : Yadda yadda
Sender                  : externaluser@hotmail.com
ReturnPath              : externaluser@hotmail.com
MessageInfo             : 00A: NTS:
MessageLatency          :
MessageLatencyType      : None
EventData               : {[FirstForestHop, EXCHANGE1.internal.local]}
RunspaceId              : d6fee167-5fa3-4d58-9354-b10402c9dacf


RunspaceId              : d6fee167-5fa3-4d58-9354-b10402c9dacf
Timestamp               : 4/29/2016 9:53:35 AM
ClientIp                :
ClientHostname          : EXCHANGE1
ServerIp                :
ServerHostname          :
SourceContext           :
ConnectorId             :
Source                  : ROUTING
EventId                 : FAIL
InternalMessageId       : 13683389
MessageId               : <bb3a65e077043968b99b37d681fc2e48@mail.hotmail.com>
Recipients              : {distribution_list@internal.local}
RecipientStatus         : {550 5.7.1 RESOLVER.RST.AuthRequired; authentication required}
TotalBytes              : 41037
RecipientCount          : 1
RelatedRecipientAddress :
Reference               : {<34af8566-3405-4204-95d1-b0f0703e8280@internal.local>}
MessageSubject          : Yadda yadda
Sender                  : externaluser@hotmail.com
ReturnPath              : externaluser@hotmail.com
MessageInfo             :
MessageLatency          :
MessageLatencyType      : None
EventData               :

Message tracking doesn't show these items as existing anywhere. I haven't done a discovery search yet, planning on it but not expecting a result. Our gateway doesn't retain mail if it succesfully hands it off to Exchange, which it did.

Have these mails disappeared into thin air? No bounceback went out. No notification to the destination user or receiving user.

If anyone has dealt with anything like this before, please let me know if you found a way to recover these messages.

Thank you,

Hi folks  need some assistance optimizing my <g class="gr_ gr_12 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="12" id="12">spf</g>  record as its failing due to too many DNS lookups

this is the current record.

v=spf1 a mx ptr include:servers.mcsv.net include:spf.mandrillapp.com include:outlook.com include:spf.messaging.microsoft.com include:spf.messagelabs.com -all

And yes <g class="gr_ gr_18 gr-alert gr_tiny gr_spell gr_run_anim ContextualSpelling multiReplace" data-gr-id="18" id="18">i</g> know, a <g class="gr_ gr_21 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="21" id="21">mx</g> and ptr shouldn't be there.

The problem is outlook.com and messaging.microsoft.com. are there more direct entries <g class="gr_ gr_30 gr-alert gr_tiny gr_spell gr_run_anim ContextualSpelling multiReplace" data-gr-id="30" id="30">i</g>  could use, exmaple _spf-b etc... OR are these two even required if all the company does is use office 365 for Archiving, no mail is sending out through Office365.

Hello Everybody,

I have a situation where all of the common sense solutions have already been applied and now I need to reach out to the community to see if anybody else has experienced this issue.

I have an Exchange domain and Outlook clients. The messages almost always have the correct Sent times, however like the title sayssometimes but not always the Sent fields are different on two different users computers. This nature of this problem rules out all of the regular culprits like NTP not being enabled and Windows Desktop times being different. 

The one thing that has caused this issue in the past is when Outlook is closed before the messages go out of the Outbox into the Exchange server.  All the employees involved already know that and they don'tdeliberatly close Outlook anymore. 

I'm using Outlook 2010 on all the clients and they are all on the same domain! Reviewing headers show that the messages aren't getting stuck in the mail relay process, which involves going to the Exchange Server and being sent out to the internet to get scanned by MxLogic, AKA McAfee Email Security, AKA Intel Email security. This part of the equation is most likely to be the real problem because it is black box as far as what they do to messages. 

Hi all.  I am working on a cross forest (inter forest) migration project.  Basically I need to migrate all AD user and Exchange 2013 mailboxes from the old AD forest (old.com) to new AD forest (new.com) that is also running on Exchange 2013.  Both the old and new AD forest will be using the same SMTP name space.  This is what I've done:

a) Created the accept domain in new Exchange forest (share.com)
b) Created the shared SMTP name space (share.com) and set it as "Internal Relay"
c) Created the Send and Receive Connector on both old and new Exchange environment
d) Ran the Prepare-MoveRequest.ps1 PowerShell script and set the TargetDevlieryDomain to "new_domain.test"
e) Ran the ADMT User Migration wizard to migrate the SIDHistory (I also excluded all msExch attributes, if I don't exclude them, it will corrupted the account created by the Prepare-MoveRequest PowerShell script)

Checked both the user account attributes, the "TargetAddress" attribute on both of them is set to "xxx@new_domain.test"

This is the result:

1.      Email send from TEST (brand new user in new forest) to TEST2 (migrated account) is NOT working
2.      Email send from  TEST2 (migrated account) to TEST (brand new user in new forest) is working
3.       Email send between TEST (brand new user in new forest) and MYSELF (user in old domain) is working
4.      Email from TEST2 (migrated account) to MYSELF (user in old domain) is working
5.      Email from MYSELF (user in old forest) or external emails send to TEST2 (migrated account) IS NOT working. 
6.       Email from external to TEST (new user in new forest) is working 

So my problem is the migrated user account is not able to accept emails from any body.

 I am seeing this error on the email send from the TEST user in the new forest to this migrated user account (they both reside in the new forest).

You aren't authorized to send to this recipient.<br>For more information about this issue see <a href="http://go.microsoft.com/fwlink/?LinkId=389365">DSN code 5.7.1 in Exchange Online</a>.

Looks like the email is received by the new Exchange server in the new forest, then it got passed over to the old Exchange server in the old forest by using the Send Connector I've configured (there is only one Send Connector in the new Exchange forest, which will pass everything to the old Exchange server).  That seems little bit odd as the recipient is in the same Exchange forest, I don't expect it to send the email out to the old Exchange server 

Then I am seeing this error from the returned email that send from my account (in the old Exchange forest) to this migrated user (in the new Exchange forest)

Remote Server returned '554 5.4.6 Hop count exceeded - possible mail loop'

Any suggestions?  Thanks you. 

Earlier this week, my Exchange 2013 environment stopped receiving any external email.  This was very confusing as everything appeared to be running, internal mail was flowing OK, and outgoing mail was OK.

I discovered that the Connection Filtering Agent on my Edge Transport Server was rejecting every connection, and dropping it straight away.  After a bit of digging, I found that I was getting a false positive by the IP Block List Providers I have configured.  When I disabled the first provider, the connections were getting blocked by the second provider, and then by the third.  I checked with Spamhaus' utility (https://www.spamhaus.org/lookup/), and the sender IP (in this case, I was using the Microsoft Remote Connectivity Analyser to test) was not in any of their blacklists.  I didn't check the other providers, but I'm sure it's not listed.

I used the Test-IPBlockListProvider cmdlet against all the Providers I have listed, with the following results:

Provider          ProviderResult   Matched
--------          --------------   -------
SpamHaus          {198.101.242.72}    True
Barracuda Central {198.101.242.72}    True
SpamCop           {198.101.242.72}    True

At the moment, I have the Connection Filtering Agent disabled, and email is coming through OK again, but I'd like to figure out what's going on, so I can enable it again.

Does anyone have any idea why it would start returning false positives for everything out of the blue?  Is the fact that the ProviderResult the same (and not the input IP I provided) relevant?

Hi everyone,

i have problem i cannot receive email from particular domain, i has been checked the log i will post bellow please help me to solve the issue:

14:47:03.950Z,mailserver\Client,08D2F8098021CFCF,1,173.16.200.100:25,153.2.232.136:30659,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2016-04-06T14:47:03.950Z,mailserver\Client,08D2F8098021CFCF,2,173.16.200.100:25,153.2.232.136:30659,>,"220 mailserver.domain.com Microsoft ESMTP MAIL Service ready at Wed, 6 Apr 2016 17:47:03 +0300",
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,3,173.16.200.100:25,153.2.232.136:30659,<,EHLO magma10.ups.com,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,4,173.16.200.100:25,153.2.232.136:30659,>,250-mailserver.domain.com Hello [153.2.232.136],
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,5,173.16.200.100:25,153.2.232.136:30659,>,250-SIZE,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,6,173.16.200.100:25,153.2.232.136:30659,>,250-PIPELINING,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,7,173.16.200.100:25,153.2.232.136:30659,>,250-DSN,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,8,173.16.200.100:25,153.2.232.136:30659,>,250-ENHANCEDSTATUSCODES,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,9,173.16.200.100:25,153.2.232.136:30659,>,250-STARTTLS,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,10,173.16.200.100:25,153.2.232.136:30659,>,250-AUTH NTLM,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,11,173.16.200.100:25,153.2.232.136:30659,>,250-8BITMIME,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,12,173.16.200.100:25,153.2.232.136:30659,>,250-BINARYMIME,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,13,173.16.200.100:25,153.2.232.136:30659,>,250 CHUNKING,
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,14,173.16.200.100:25,153.2.232.136:30659,<,STARTTLS,
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,15,173.16.200.100:25,153.2.232.136:30659,>,220 2.0.0 SMTP server ready,
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,16,173.16.200.100:25,153.2.232.136:30659,*,,Sending certificate
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,17,173.16.200.100:25,153.2.232.136:30659,*,CN=mail.domain.com,Certificate subject
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,18,173.16.200.100:25,153.2.232.136:30659,*,"CN=GeoTrust DV SSL CA - G4, OU=Domain Validated SSL, O=GeoTrust Inc., C=US",Certificate issuer name
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,19,173.16.200.100:25,153.2.232.136:30659,*,02E6E0,Certificate serial number
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,20,173.16.200.100:25,153.2.232.136:30659,*,E790262288D9D92EC4F366FF102B96BA5BD3B0BB,Certificate thumbprint
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,21,173.16.200.100:25,153.2.232.136:30659,*,mail.domain.com;mailserver.domain.com;autodiscover.domain.com,Certificate alternate names
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,22,173.16.200.100:25,153.2.232.136:30659,<,EHLO magma10.ups.com,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,23,173.16.200.100:25,153.2.232.136:30659,*,,TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,24,173.16.200.100:25,153.2.232.136:30659,>,250-mailserver.domain.com Hello [153.2.232.136],
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,25,173.16.200.100:25,153.2.232.136:30659,>,250-SIZE,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,26,173.16.200.100:25,153.2.232.136:30659,>,250-PIPELINING,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,27,173.16.200.100:25,153.2.232.136:30659,>,250-DSN,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,28,173.16.200.100:25,153.2.232.136:30659,>,250-ENHANCEDSTATUSCODES,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,29,173.16.200.100:25,153.2.232.136:30659,>,250-AUTH NTLM LOGIN,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,30,173.16.200.100:25,153.2.232.136:30659,>,250-8BITMIME,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,31,173.16.200.100:25,153.2.232.136:30659,>,250-BINARYMIME,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,32,173.16.200.100:25,153.2.232.136:30659,>,250 CHUNKING,
2016-04-06T14:47:06.618Z,mailserver\Client,08D2F8098021CFCF,33,173.16.200.100:25,153.2.232.136:30659,<,MAIL FROM:<prvs=09018d05a2=aebada@ups.com>,
2016-04-06T14:47:06.618Z,mailserver\Client,08D2F8098021CFCF,34,173.16.200.100:25,153.2.232.136:30659,*,08D2F8098021CFCF;2016-04-06T14:47:03.950Z;1,receiving message
2016-04-06T14:47:06.618Z,mailserver\Client,08D2F8098021CFCF,35,173.16.200.100:25,153.2.232.136:30659,>,250 2.1.0 Sender OK,
2016-04-06T14:47:07.195Z,mailserver\Client,08D2F8098021CFCF,36,173.16.200.100:25,153.2.232.136:30659,<,RCPT TO:<amit@domain.com>,
2016-04-06T14:48:13.060Z,mailserver\Client,08D2F8098021CFCF,37,173.16.200.100:25,153.2.232.136:30659,>,250 2.1.5 Recipient OK,
2016-04-06T14:49:24.229Z,mailserver\Client,08D2F8098021CFD6,0,173.16.200.100:25,50.31.57.60:45926,+,,

Thanks

We have attached transport rule (attached) which doesn't work after Exchange 2013 CU9 upgrade.

Recreated the rule but no luck

SAH

Hi,

I have a problem with NDRs on Exchange 2013. A user received an external email and the sender keeps receiving many NDRs. Since last Wednesday he got about 650 NDRs of that message.

The strange thing about this, is that my user received  the message, but the sender (external one) keeps receiving NDRs of "message exceeded the limit"

My problem here is not related to the message, but about this repeating of the NDR to the sender.

Please Help.

Hello,

I am completing the last phase of a exchange 2007 to 2013 migration, external (and internal) mail is currently routed through our exchange 2007 front NLB cas server.

I have a 2013 sp1 CU10 ip less dag with 3 nodes and all servers running cas/mb roles. We have a external host (vendor) that accepts mail from our external MX records. For smtp redundancy I'm going to:

External > Create another public IP, and route mail to 2 different dag servers from 3rd party gateway (through FW).

Internal > Create 2 dns A records (smtp.domain.com) with 2 different IPs pointing to 2 different host names of my dag servers (round robin). Point all internal apps to smtp.domain.com. My time is limited have not been able to test in lab. Is this a feasible solution?

thanks

Hello,

Our Exchange 2010 server message queue keeps reporting the following error

 The remote pipeline has been stopped. It was running the command 'get-message -ResultSize '1000' - ReturnPageInfo $True -SortOrder '+FromAddress' -server 'myserver.mydomain.loc' -SearchForward $True - BookmarkObject $null .............

hello, 

I am migrating from Exchange 2010 to 2013, everything went smoothly till migration step.

Anytime I start a new migration batch I get error "A valid Migration mailbox could not be found for this organization".

Tried these workarounds:

-Enable-Mailbox -Arbitration -Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136"

 Getting error "The object is read-only because it was created in a version of Exchange later than 1.1 (15.0.0.0)". Current supported version is 1.0 (14.0.0.0)

didn't run : -Set-Mailbox"Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration –Management:$true

because of previous error.

Any suggestion would be great