Exchange 2013 - Duplicate Message Detection

Hi,
I am trying to resend an email from my spam firewall but it is not reaching the user. The duplication detection on the server is not allowing me to resend. If I go back older than a month I was able to successfully resend from the spam firewall.
How do I temporally disable the duplicate message detection on Exchange 2013 server?
I found this from someone else for 2013 but I did not have this path in my registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server_Name>\Public-<GUID>
Thank you

Hi,
After some search, I think we can adjust the expiration time of duplicate message detection. And the minimum value is 1 hour, so we don't need to wait several days.
The registry setting is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server Name>\<Private/Public-Guid>\Track Duplicates
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server Name>\<Private/Public-Guid>\Background Cleanup
please refer to these articles:
http://msexchangeguru.com/2013/04/22/transport/
http://technet.microsoft.com/en-us/library/dd577073(v=exchg.80).aspx

Similar Messages

Exchange 2013 SP1: messages still stuck in Drafts folder

Hello!
The second question on Exchange 2013SP1 that I asked when I was working with Exchange 2013:
New lab setup: a Windows 2012R2 DC (server1) + Exchange 2013SP1 (server2). Exchange 2013SP1 installation completed successfully. I created three mailboxes: [email protected], [email protected], [email protected]
Now when I'm trying to send a message (from user1 to user, for example) it gets stuck in the Drafts folder.
I manually set up my DNS server in ECP:
as described here: http://thoughtsofanidlemind.com/2013/03/25/exchange-2013-dns-stuck-messages - but the problem persists.
And this problem
"On every single installation / that I’ve done of Exch 2013 in multiple labs, when set as a single mailbox server, messages have never been able to leave the “drafts” folder. Not a single instance where it worked correctly. Messages
leaving a mailbox, destined to the exact same server do not route, let alone use any send-connector to leave the organization.
Now, take it to the next step, and install a second mailbox server. The very second that services finish installing, and AD replication (if using multiple sites) settles down, mail-flow on the first server starts working absolutely flawlessly. Whatever
changes are done to AD from the second mailbox server being installed in regards to mailflow, it completely resolves the issues of the first server holding onto the messages."
...is exactly the same as mine...but in Exchange 2013 SP1 ( Messages leaving a mailbox, destined to the exact same server do not route).
Can anybody from MS tell me if it's a bug or by design??? I've NEVER had an Exchange installation without this issue...
Thank you in advance,
Michael

Hi,
I have never come across such a situation in my labs(all roles install in a single server), and there is no Microsoft documentation mentioned this issue.
In addition, Microsoft does not oppose the Exchange installed on a single server(although not recommend).
I recommend you check if all the exchange services are running, and try to restart Exchange Mailbox Transport Submission & Exchange Mailbox Assistants services.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Disable duplicate message detection

Hi Folks
there is a way to disable duplicate message detection feature?
I need to deliver emails with same MessageID and Date.
Thanks in advance
Luca

Hi Luca,
We can create the Disable All Duplicate Detection registry entry to disable duplicate detection on a Mailbox server. It enables any message to be delivered to a recipient with a duplicate message ID. It is recommend that you make
this change only on Mailbox servers that contain Journal mailboxes and no other mailboxes.
The ParametersPrivate subkey in registry to disable duplicate detection for mailboxes:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/MSExchangeIS/ParametersPrivate
If the ParametersPrivate registry subkey does not exist, follow these steps:
a. On the Edit menu, point to New, and then click Key.
b. Type ParametersPrivate, and then press ENTER.
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type Disable All Duplicate Detection, and then press ENTER.
5. On the Edit menu, click Modify.
6. Type 1, and then click OK.
For more information about it, please refer to:
http://support.microsoft.com/kb/975990/en-us
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 - Duplicate Binding for EWS

Hi there,
on our Exchange 2013 server we find that Outlook and OWA are both working fine. Mac users can't connect. This seems to be related to the following error [sorry for the Dutch language]:
Basically it complains that an endpoint is already bound to the URI.
WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/34026242
Exception: System.ServiceModel.ServiceActivationException: De service /EWS/exchange.asmx kan niet worden geactiveerd als gevolg van een uitzondering tijdens de compilatie. Het uitzonderingsbericht is: Er is reeds een bindingsexemplaar gekoppeld aan luister-URI
https://bilbo.ourdomain.loc:444/EWS/Exchange.asmx/http. Als twee eindpunten dezelfde LuisterURI willen delen, moeten ze ook hetzelfde bindingsobjectexemplaar delen. De twee conflicterende eindpunten zijn opgegeven in AddServiceEndpoint()-aanroepen, in een
configuratiebestand, of in een combinatie van AddServiceEndpoint() en configuratiebestand. . ---> System.InvalidOperationException: Er is reeds een bindingsexemplaar gekoppeld aan luister-URI https://bilbo.ourdomain.loc:444/EWS/Exchange.asmx/http. Als twee
eindpunten dezelfde LuisterURI willen delen, moeten ze ook hetzelfde bindingsobjectexemplaar delen. De twee conflicterende eindpunten zijn opgegeven in AddServiceEndpoint()-aanroepen, in een configuratiebestand, of in een combinatie van AddServiceEndpoint()
en configuratiebestand.
bij System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
bij System.ServiceModel.ServiceHostBase.InitializeRuntime()
bij System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
bij System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
bij System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity)
bij System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
--- Einde van intern uitzonderingsstackpad ---
bij System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
bij System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity)
Process Name: w3wp
Process ID: 8320
The IIS Manager has two sites ('Default Web Site', 'Exchange Back End').
For the Default Site only the bindings *:80, *:443, 127.0.0.1:80, 127.0.0.1:443 are enabled.
For the Exchange Back End only the bindings *:81, *:444 are enabled
There are no other sites.
I have tried searching the config files by doing:
PS C:\inetpub> Get-ChildItem . -include *.config -rec | select-string -pattern "444"
This does give files under C:\inetpub\history and C:\inetpub\temp but I don't know [given the history/temp] names if I should look further here.
I have also looked at
PS C:\windows\system32\inetsrv> Get-ChildItem . -include *.config -rec | select-string -pattern "444"
This returns only a single line in config\applicationHost.config which matches what I see in the IIS Manager GUI.
Where else can I search to find the duplicate binding?
Eljakim

Okay, after a couple of nights of trouble shooting I found the solution.
In the web.config file under Exchange\ClientAccess\exchweb\ews somehow the following information had appeared:
<services>
<service name="Microsoft.Exchange.Services.Wcf.EWSService" behaviorConfiguration="EWSServiceBehavior">

<endpoint address="http" behaviorConfiguration="MultiReceive" binding="webHttpBinding" bindingConfiguration="EWSStreamingNegotiateHttpBinding" name="Https" contract="Microsoft.Exchange.Services.Wcf.IEWSStreamingContract" />
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="webHttpBinding" bindingConfiguration="EWSStreamingNegotiateHttpsBinding" name="Http" contract="Microsoft.Exchange.Services.Wcf.IEWSStreamingContract" />
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="EWSAnonymousHttpBinding" name="Https" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" />
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="EWSAnonymousHttpsBinding" name="Http" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" />
<endpoint binding="customBinding" bindingConfiguration="EWSWSSecurityHttpBinding" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" address="http" />
<endpoint binding="customBinding" bindingConfiguration="EWSWSSecurityHttpsBinding" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" address="http" />
</service>
<service name="Microsoft.Exchange.UM.ClientAccess.UMWebService" behaviorConfiguration="UMServiceBehavior">
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="UMLegacyHttpBinding" contract="Microsoft.Exchange.Services.Wcf.IUM12LegacyContract" />
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="UMLegacyHttpsBinding" contract="Microsoft.Exchange.Services.Wcf.IUM12LegacyContract" />
</service>
</services>
The endpoint addresses are wrong in this file. I compared the endpoints to a config on another server and fixed the issue by changing the services to:
<services>
<service name="Microsoft.Exchange.Services.Wcf.EWSService" behaviorConfiguration="EWSServiceBehavior">

<endpoint address="s" behaviorConfiguration="MultiReceive" binding="webHttpBinding" bindingConfiguration="EWSStreamingNegotiateHttpsBinding" name="Https" contract="Microsoft.Exchange.Services.Wcf.IEWSStreamingContract"/>
<endpoint address="s" behaviorConfiguration="MultiReceive" binding="webHttpBinding" bindingConfiguration="EWSStreamingNegotiateHttpBinding" name="Http" contract="Microsoft.Exchange.Services.Wcf.IEWSStreamingContract"/>
<endpoint address="" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="EWSAnonymousHttpsBinding" name="Https" contract="Microsoft.Exchange.Services.Wcf.IEWSContract"/>
<endpoint address="" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="EWSAnonymousHttpBinding" name="Http" contract="Microsoft.Exchange.Services.Wcf.IEWSContract"/>
<endpoint binding="customBinding" bindingConfiguration="EWSWSSecurityHttpBinding" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" address="wssecurity"/>
<endpoint binding="customBinding" bindingConfiguration="EWSWSSecurityHttpsBinding" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" address="wssecurity"/>
</service>
<service name="Microsoft.Exchange.UM.ClientAccess.UMWebService" behaviorConfiguration="UMServiceBehavior">
<endpoint address="" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="UMLegacyHttpsBinding" contract="Microsoft.Exchange.Services.Wcf.IUM12LegacyContract"/>
<endpoint address="" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="UMLegacyHttpBinding" contract="Microsoft.Exchange.Services.Wcf.IUM12LegacyContract"/>
</service>
</services>

Exchange 2013 - Some messages net being delivered with shared SMTP Address Space

Hi
I am having a problem with some internal messages intermittently not being delivered. When I go to the Exchange ECP -->Mail Flow -->Delivery Reports I can see the following error with the message:
Submitted
2013-03-07 11:36 AM EXCHANGE
The message was submitted to exchange.******.local.
Pending
2013-03-07 11:36 AM exchange.******.local
Message was received by exchange.******.local from Exchange.******.local.
Failed
2013-03-07 11:36 AM exchange.********.local
The domain name in the email address is incorrect. Check the address.
554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain
However, usually just waiting a few minutes and then sending to the same recipient, the message will be delivered:
Submitted
2013-03-07 11:41 AM EXCHANGE
The message was submitted to exchange.******.local.
Pending
2013-03-07 11:41 AM exchange.******.local
Message was received by exchange.******.local from Exchange.******.local.
2013-03-07 11:41 AM exchange.******.local
The message has been transferred from exchange.******.local to Exchange.******.local.
Delivered
2013-03-07 11:41 AM exchange.******.local
The message was successfully delivered.
I have setup an Accepted Domain as Internal Relay, with a Send Connector to deliver any mails if the user is not found in Exchange server.

Hi All
I had this issue as well.
Here is the solution i used to fix this once for all:
My Environment:
AD server with private and public NICs
Exchange Server with Private and Public NICs
Used a dummy domain (Not owned by me) (ex: corp.com) on Private Network.
Created accepted domains for the domains that i own on exchange server.
Issue Cause:
When an external user (Gmail, hotmail.. etc) sends an email to my accepted domain, as the MX record is pointed to my exchange server on the public IP, the mail flows till my exchange server. Now the transport service on the CAS, hand's over the email to
Transport Service on the Mail box server. There it goes to the categorizer. Here the DNS look up happens and the next SMTP send service will either hand over the mail to the Mail box or send a Non delivery report stating that a mail box, domain name is not
found with in itself.
The issue here is caused by our private DNS where it fails to resolve the internal dummy domain that i used because the resources on the DNS server was completely utilized my memory ballooning in VMware. Ignore the ballooning thing if you do not understand.
Resolution:
I created an entry in the C:\Windows\System32\Drivers\etc\hosts file of the exchange server as below:
mail01.corp.com 192.168.80.132 .i.e., <host name of the exchange server>.<domain prefix>.<domain suffix> <Private IP address of the exchange server>
I change the secondary DNS on the Private NIC of the exchange server to itself .i.e., 192.168.80.132 and forced it look within itself when the primary DNS does not respond at times.
Now my exchange server is absolutely stable. It worked for me !
Hope this post helps you fix the issue or at least help you think a bit ahead.
To understand more about your scenario, i would suggest you look up the logs at C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs (if you have not changed the default drectory while instalation) and Frontend Connectivity logs and Mailbox
connectivity logs. I am sure those logs will help you understand whats going wrong behind the scenes.

Mail 4.1, Exchange, and Duplicate messages in inbox

Using Snow Leopard and Mail 4.1 to access an exchange account and a gmail account. The problem ONLY occurs in the Exchange account. My messages are all duplicating. Only in Mail are they duplicating. I've checked Outlook Web Access and Outlook on my windows machine - no duplicates there. Didn't start out this way, and the problem came once before, stopped, and now it has returned. If I delete one copy of the message, both messages get deleted. Is there someway to rebuild the mail inbox? or resync?
Also, tried creating a new folder on the exchange server, copying all messages from inbox to the new folder, then moving back. In the temp/new folder, the messages were single. After copying back to Inbox - they doubled again. And again, only in Mail. The msgs remain single in Outlook, OWA, iPhone, Blackberry.
UPDATE: I highlighted the exchange mailbox and went to MAILBOX > REBUILD. Erased everything but only in Mail. The messages are still on the Exchange server and can be seen by OWA, Outlook, iphone and blackberry. New messages are going to the Mail Exchange inbox but old messages are gone. Any way to get them back?
Message was edited by: Atlantax

FromBone wrote:
Thanks V.K.! So there is no chance for me to re upload all the messages from my mac to my yahoo inbox.
nope.
May I ask yahoo to that?
you can ask but they won't say anything different.
I could never have known that the default setting on mac's mail would be "remove copy from server after retrieving a message".
now, that's a valid point. this is not exactly advertised and mail setup assistant does not tell you anything about it. you can voice your concern to apple about this issue here
http://www.apple.com/feedback/macosx.html
I wish apple had some kind of a solution for this.
there isn't anything you can do now. it's not up to apple at this point. you just can't upload messages to a POP email server. it does not matter what email client or what operating system you are using.
Thanks again

Exchange 2013 - Your Message was deleted without being Read

Scenario:
Email gets sent to a shared mailbox with a read receipt called for e.g.
[email protected] and everything goes into [email protected] goes into another shared mailbox called
[email protected] The user who has access to
[email protected] delete the e-mail without being read and the sender receives an email back saying you:
From: JOE Smith on behalf of [email protected]
Your message was deleted without being read on Monday, July 14, 2014 8:36:58 AM
Is there a way just to target [email protected] from not sending anything at all?

You could use transport rule to delete if read receipt is coming from mailbox2 or any other recipient with on behalf of...
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2013 SP1 Readiness Checks: No Exchange 2007 server detected

Hi there,
We are planning to upgrade our current Exchange 2007 server with the new Exchange 2013 SP1. I have been following Exchange Server Deployment Assistant to assist me with this task. Only schema update (setup /PrepareSchema) had been done so
far. I didn’t run setup /PrepareAD command manually because I wasn’t sure if I need to provide ‘Organisation Name’ with it or not?! I have installed all of the prerequisites as noted in the Microsoft documentation.
Now, I am a bit confuse with the ‘Readiness Checks’ page during graphical user installation of Exchange 2013 SP1 setup on Windows 2012 R2. Windows 2012 R2 server has all available updates applied.
===
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
===
I get the message why setup wants to run preparation for the Ex2013 with the ‘Setup /PrepareAD’. But, why ‘No Exchange 2010 server role have been detected in this topology’?! Ok, in my case setup doesn’t detect Exchange 2007 server. Is that ok to proceed
with the installation or something else needs to be done first?
Thanks in advance.

I need Exchange guru advice here please. Since we already have Exchange 2007 SP3 RU 10 in our Windows 2008R2 Active Directory domain here I need to be 100% confident that pushing Exchange 2013 SP1 “Install” will not override our existing Ex2007 environment.
That would be a huge disaster!
Microsoft is saying that: “Microsoft Exchange Server 2013 Setup displayed this warning because
no Exchange Server 2010 or Exchange Server 2007 server roles exist in the organization.”
http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Ok, I get the message about if I continue with Exchange Server 2013 installation, I won’t be able to add Exchange 2010 or Exchange 2007 servers to the organization at a future date..., and why would I need to do that anyway?!
Microsoft wording about “some solutions may require the use...” are very confusing since we will require to consider “Coexistence or migration requirements"
Perhaps, before running Exchange 2013 SP1 setup I need to run setup for preparing AD without “Organisation Name” parameter?! Something like this:
setup /PrepareAD /IAcceptExchangeServerLicenseTerms

Exchange 2013 CAS-MBX recipient validation rejects entire message if any of recipients are invalid

Hi,
How can I enable recipient validation work in this design:
2 Exchange 2013 servers with CAS and MAILBOX roles both, DAG and Hardware Load balancer for HTTP and SMTP traffic.
From Exchange documentation:
http://technet.microsoft.com/en-us/library/bb125187%28v=exchg.150%29.aspx
Although the Recipient Filter agent is available on Mailbox servers, you shouldn't configure it. When recipient filtering on a Mailbox server detects one invalid or blocked recipient in a message that contains other valid recipients, the message is rejected.
If you install the anti-spam agents on a Mailbox server, the Recipient Filter agent is enabled by default. However, it isn't configured to block any recipients. For more information, see
Enable Anti-Spam Functionality on Mailbox Servers.
If You have a setup like this:
Install antispam agents:
Identity Enabled Priority
Transport Rule Agent True 1
Malware Agent True 2
Text Messaging Routing Agent True 3
Text Messaging Delivery Agent True 4
Content Filter Agent True 5
Sender Id Agent True 6
Sender Filter Agent True 7
Recipient Filter Agent True 8
Protocol Analysis Agent True 9
Have Recipient validation enabled:
Name Enabled RecipientValidationEnabled---- ------- --------------------------RecipientFilterConfig True True
Have AcceptedDomain AddressBook enabled:
DomainName DomainType AddressBookEnabled
contoso.com Authoritative True
Then You have a situation, where a single invalid recipient on an incoming email message would reject the entire message! I guess this is because the recipient filtering happens on the mailbox server.
So .. HOW? Is it possible without Edge servers? Have I missed something?
I hope this feature isn't "missing by design", because it will be very difficult to explain to the client, that such an expensive product cannot do what any mail server can - reject unknown recipients before taking E-Mail data. There are a lot
of issues with this feature missing (possible DDOS with max attachments, or spoofed sender e-mail address that is a spamtrap, so NDR from Exchange would get You to SBL, etc.).
Sincerely,
Vince

Hello Vince,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

While trying to open the order in co03 or co02, It is not opening and showing the error message as "Inconsistent data : order 107434 16.09.2013, duplicate entry o 0020. is showing ?

Hi,
While trying to open the order in co03, co02, I am getting the below error message : Inconsistent data : order 107434 16.09.2013, duplicate entry o 0020 is showing. Please guide me the way forward.
Regards,
Mastan.

Hi Mastan
The report mentioned by Rajen should clear the inconsistent records.
Please observe that you could have found this by yourself report with a quick note search for this error message or even searching for old threads.
Even a google search points to the solution.
You should do your own research before opening such kind of thread.
BR
Caetano

Exchange 2013 - The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold

Noticed at about noon that no emails had been received all day. Began to investigate and found that the MS Exchange Transport service had been set to deny email submission because it was using too much memory on the server (91%).
The error message makes me think that we may have been getting used by malware or something similar.“The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the
configured threshold.”
There are also several warning messages that list particular IP addresses and say that a connection from that IP was denied because there were already the maximum number of connections (20).
From what I can tell, all of the IP addresses are from Taiwan.
The time period for which some emails may be missing is from close of business yesterday ( 4/3/2014) through about 12:45 today (4/4/2014).
From the time I spent reading and trying to figure out the error, I think we may need to readjust our throttling policies to prevent this from happening.
The exchange server is currently running at 90%+ CPU and 50%+ memory usage the majority of the time, and I’m not sure how to fix it.
Also, I cannot get into EMS I get a access denied message from the destination computer. (Exchange server) I want to get into there to change the throttling policy back to default, since we disabled it.
The Error reads:
The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer <Exchange> returned an 'access denied' error. Change the configuration to allow Kerberos authentication
mechanism to be used or specify one of the authentication mechanism supported by the server. (How do I do this?) To use Kerberos, specify the local computer name as the remote destination. (I'm trying to use EMS while logged into the local Exchange server)
Also verify that the client computer and the destination computer are joined to a domain. (Exchange is on our domain, and the computer trying to connect is the same computer) To use basic, specify the local computer name as the remote destination, specify
Basic authentication and provide user mane and password. Possible authentication mechanisms reported by server.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
I assumed control of this exchange system already in place and I do not have much experience with exchange 2013 or server 2012. I do know 2008, but that doesn't help very much in this situation.
Recent changes to the system:
About three days ago we switch our sessions policy to allow many more connections, and I believe this caused the issue. This is what I changed it to:
Made the registry DWORD (32-bit) "Maximum Allowed Sessions Per User" and modified the value to 1000. Location of registry change @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
I just changed it to 10 from the 1000. I'm hoping this solves this. So far no.
Also, I am not the best in the shell or command line interfaces. Any help would be wonderful!

Hi,
Yes, could be hardware performance issue. Try recycle the Transport process and see if the issue persists.
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 SP1 users not receiving quota warning email message

Hi,
We are on Exchange 2013 SP1 and Exchange 2010 SP3 co-existence mode and currently migrating users from Exchange 2010 to 2013. We have noticed that users are not receiving email message when their mailbox quota warning when its near to maximum limit.
If I log in via OWA it shows the notification (Pop up) that your mailbox is almost full but no message received in email. Most of the users do not log into OWA but only uses Outlook.
It looks like other people are also seeing this similar issue but I am unable to find any solution for it.
How users will know if their mailbox is almost full if they are traveling and only using Mobile phone for emails to send and receive.
Thanks,
Raman

Hi Thanks for your response. Our Quota is set on Database level. I am seeing these event ids as well.
Log Name: Application Source: MSExchangeIS Date: 12/31/2014 10:07:12 PM Event ID: 1077 Task Category: MAPI Level: Warning Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f on database
326f0997-4fe5-4b31-873b-6a3396e7a91c is approaching its storage limit. A notification has been sent to the user. This warning will not be sent again for at least twenty four hours.
========================
Log Name: Application Source: MSExchange Store Driver Submission Date: 12/31/2014 10:07:12 PM Event ID: 1012 Task Category: MSExchangeStoreDriverSubmission Level: Error Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The store
driver failed to submit event 8237691 mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f MDB 326f0997-4fe5-4b31-873b-6a3396e7a91c and couldn't generate an NDR due to exception Microsoft.Exchange.MailboxTransport.StoreDriverCommon.InvalidSenderException at Microsoft.Exchange.MailboxTransport.Shared.SubmissionItem.SubmissionItemUtils.CopySenderTo(SubmissionItemBase
submissionItem, TransportMailItem message) at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.GenerateNdrMailItem() at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.<>c__DisplayClass1.<SubmitNdrForFailedSubmission>b__0()
at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).
Raman

How to disable detection of duplicate messages in Lion Mail?

When Mail in Lion detects duplicate messages in a mailbox, it groups them together and shows the link in the header "x Duplicates", where x is the number of duplicate messages found. When that link is clicked the duplicate messages show in the mailbox separately. But I'd like Mail to stop grouping them together to begin with.
Running OS X 10.7.3 and Mail 5.1

To disable automatic grouping of duplicate messages, quit Mail then run this command in Terminal:
     defaults write com.apple.mail AlwaysShowDuplicates -bool true
To revert to the default setting, run this command:
     defaults write com.apple.mail AlwaysShowDuplicates -bool false
or simply delete the setting altogether with this command:
     defaults delete com.apple.mail AlwaysShowDuplicates
If you want to see how Mail behaves with this setting enabled, but without modifying your preference file, start Mail from Terminal with this command:
     /Applications/Mail.app/Contents/MacOS/Mail -AlwaysShowDuplicates YES
I learned of Mail's modifiability (is that a word?) from here:
     http://hints.macworld.com/article.php?story=2004101603285984
and here:
     http://erikslab.com/2007/07/16/os-x-mailapp-logging/
I found the AlwaysShowDuplicates option by looking for interesting words similar to 'duplicates' in the Mail executable like this:
          strings /Applications/Mail.app/Contents/MacOS/Mail | grep -i duplicat

How to ENABLE detection of duplicate messages in Mavericks Mail?

Hello,
There was a good discussion of how to disable detection of duplicate messages in Lion mail - https://discussions.apple.com/message/18265121#18265121
but unfortunately nothing seems to work to turn them ON in Mavericks.
In Lion or Mt. Lion I do see duplicate messages - but in Mavericks I do not - but I want to see if there are duplicates for a variety of reasons.
In the post referenced above none of the command line suggestions seem to make a difference. My mail perference settings are idential on each system, be it Lion, Mr. Lion or Mavericks. Settings as follows:
Please note 'include related messages' seems to make no difference either way.
Can anyone please tell me how to display duplicates in Mavericks. Thank you very much in advance.
E.

As a quick update, the following command DOES in fact show the duplicates in the mail folder:
defaults write com.apple.mail AlwaysShowDuplicates -bool true
So, if there are two exact messages (one sent to me at [email protected] and one forwarded to that email address and sent to me at [email protected], BOTH will show up as separate messages.
But to be clear, what I want to see is a single message with the '1 Duplicate' indicated in the message header.
Any way to do that in Mavericks?
Again, thanks in advance.

Exchange 2013 Messages Stuck in Queue

Hello,
I have an Exchange 2013 on-prem serer. I'm noticing that certain messages get stuck in the queue. They report back errors of "451 4.4.0 SMTPSEND.SuspiciousRemoteServerError; remote server disconnected abruptly; retry will be delayed".
It seems to be random. I've sent messages to a domain I've seen with messages stuck, and mine work. When I log the send connector it really doesn't show me much. Can anyone give me some leads?
2014-10-13T14:41:42.162Z,Internet Outbound,08D1B4FCB0EBBB8A,10,10.10.0.30:19282,152.163.0.67:25,>,EHLO mail.mydomain.com,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,11,10.10.0.30:19282,152.163.0.67:25,<,250-mtaig-aak04.mx.aol.com,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,12,10.10.0.30:19282,152.163.0.67:25,<,250-STARTTLS,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,13,10.10.0.30:19282,152.163.0.67:25,<,250 DSN,
2014-10-13T14:41:42.193Z,Internet Outbound,08D1B4FCB0EBBB8A,14,10.10.0.30:19282,152.163.0.67:25,>,STARTTLS,
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,15,10.10.0.30:19282,152.163.0.67:25,<,220 2.0.0 Ready to start TLS,
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,16,10.10.0.30:19282,152.163.0.67:25,*,,Sending certificate
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,17,10.10.0.30:19282,152.163.0.67:25,*,"CN=mail.mydomain.com, OU=Domain Control Validated",Certificate subject
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B2FCB0ENBB8A,18,10.10.0.30:19286,152.163.0.67:25,*,"CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O=""GoDaddy.com, Inc."", L=Scottsdale, S=Arizona,
C=US",Certificate issuer name
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB3A,19,10.10.0.30:19282,152.163.0.67:25,*,0828F6C11RF919,Certificate serial number
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,20,10.10.0.30:19282,152.163.0.67:25,*,D752EC6829000606559BDC63320D9F222227E773,Certificate thumbprint
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,21,10.10.0.30:19282,152.163.0.67:25,*,mail.mydomain.com;www.mail.sigwnet.com;autodiscover.mydomain.com,Certificate alternate names
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCB0EB3B8A,22,10.10.0.30:19282,152.163.0.67:25,*,,Received certificate
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCA0EBBB8A,23,10.10.0.30:19282,152.163.0.67:25,*,43A8A13BC1098814A88CF13AEDEF1A1E64D62DA8,Certificate thumbprint
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCB0EBBB8A,24,10.10.0.30:19282,152.163.0.67:25,>,EHLO mail.mydomain.com,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBA8A,25,10.10.0.30:19282,152.163.0.67:25,<,250-mtaig-aak04.mx.aol.com,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1A4FCB0EBBB8A,26,10.10.0.30:19282,152.163.0.67:25,<,250 DSN,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBB8A,27,10.10.0.30:19282,152.163.0.67:25,*,,sending message with RecordId 29532195127522 and InternetMessageId <[email protected]>
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBB8A,28,10.10.0.30:19282,152.163.0.67:25,>,MAIL FROM:<[email protected]>,
2014-10-13T14:41:42.505Z,Internet Outbound,08D1B4FCB0EBBB8A,29,10.10.0.30:19282,152.163.0.67:25,<,250 2.1.0 Ok,
2014-10-13T14:41:42.505Z,Internet Outbound,08D1B4FCB0EBBB8A,30,10.10.0.30:19282,152.163.0.67:25,>,RCPT TO:<[email protected]>,
2014-10-13T14:41:42.552Z,Internet Outbound,08D1B4FCB0EBBB8A,31,10.10.0.30:19282,152.163.0.67:25,<,250 2.1.5 Ok,
2014-10-13T14:41:42.552Z,Internet Outbound,08D1B4FCB0EBBB8A,32,10.10.0.30:19282,152.163.0.67:25,>,DATA,
2014-10-13T14:41:42.583Z,Internet Outbound,08D1B4FCB0EBBB8A,33,10.10.0.30:19282,152.163.0.67:25,<,354 End data with <CR><LF>.<CR><LF>,
2014-10-13T14:41:45.688Z,Internet Outbound,08D1B4FCB0EBBB8A,34,10.10.0.30:19282,152.163.0.67:25,<,250 2.0.0 Ok: queued as 8A7497000009F,
2014-10-13T14:41:45.688Z,Internet Outbound,08D1B4FCB0EBBB8A,35,10.10.0.30:19282,152.163.0.67:25,>,QUIT,
2014-10-13T14:41:45.719Z,Internet Outbound,08D1B4FCB0EBBB8A,36,10.10.0.30:19282,152.163.0.67:25,<,221 2.0.0 Bye,
2014-10-13T14:41:45.719Z,Internet Outbound,08D1B4FCB0EBBB8A,37,10.10.0.30:19282,152.163.0.67:25,-,,Local
2014-10-13T14:42:01.132Z,Internet Outbound,08D1B4FCB0EBBB88,27,10.10.0.30:19263,74.208.5.21:25,*,,"HandleError has encountered a suspicious connection reset from a remote, non-mailbox transport server (will retry in 00:10:00)."
2014-10-13T14:42:01.132Z,Internet Outbound,08D1B4FCB0EBBB88,28,10.10.0.30:19263,74.208.5.21:25,-,,Remote

Hi rmicha9682,
Agree with Gareth, it seems to be a firewall issue.
I have seen this issue caused by the SMTP Fixup protocol when using TLS encryption.
I recommend you try disabling SMTP Fixup and check if any helps.
The following article for your reference:
http://support.microsoft.com/kb/320027/en-us
Best regards,
Niko Cheng
TechNet Community Support

Exchange 2013 - Duplicate Message Detection

Similar Messages

Maybe you are looking for