Exchange 2013 resubmit mails

HI all,
Experiencing issue With Exchange 2013 environment ( 2 servers With cas and mailbox role With DAG)where some of Our emails are beeing resubmitted.
So far cant see any pattern on why or where it sends Message twice to a recepient.
Any idea where i can start to troubleshoot or what that might cause this?
thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi,
Did the recipients receive duplicate emails?
Could you please check message tracking log for related message?
For the issue about the number of messages in Shadow redundancy (under delivery type), I recommend you run the Get-TransportConfig | fl shadow* command and post result here for further research.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

Exchange 2013 SMTP Mail Flow from external domains

I have query related to mail flow for incoming mails from external domains from Internet facing site. There are two sites - Site A & Site B. Both have Exchange 2013 CAS servers in NLB and Exchange 2013 Mailbox in individual DAG - say DAG1 in Site
A and DAG2 in Site B. Site A is Internet facing site and site B is not Internet facing.
An incoming Internet mail meant for recipient in Site B will land in Exchange 2013 CAS server in Site A. This CAS Server in Site A will look for the recipient in local Domain Controller and get to know the mailbox database of this recipient is in DAG2 (
in site B ) Will the FET service in EX2013 CAS in Site A make a SMTP connection with FET service of EX2013 CAS in site B which will then make SMTP connection to EX2013 Mailbox server in Site B which is holding the recipient mailbox Active copy for delivery.
OR
EX2013 CAS will send this mail to Ex2013 Mailbox server in site A and the Hub Transport service running in in site A will then make SMTP connection with EX2013 Mailbox server in Site B which is holding the recipient mailbox Active copy
Need clarification on above
Thanks
Parveen

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

How to get a summarized mail traffic report in exchange 2013

Hi all
How to calculate the exchange 2013 SMTP mail traffic in terms of hour,day,month,top senders,largest message and top recipients list . Same time we would like to have those summarized mail traffic report for all the mailbox servers in the form of graphical
view as well as in a csv file ?
Please all of us share your thoughts and possibilities .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

You may calculate hourly email traffic using "Message Tracking Logs and Log Parser".
I would like to refer you on this well explained article that will assist you step-wise to implement in your working environment : http://exchangeserverpro.com/calculate-hourly-email-traffic-using-message-tracking-log-parser/
Moreover, if you wish to achieve this goal automatically, you may also consider on this automated application (http://www.exchangereports.net/) that provides a deep-view of email traffic report in real time at
granular level.

Mail can't reconnect to Exchange 2013

My company has recently upgraded to Exchange 2013.
Mail connects OK with the new server and everything seems fine; however, if I leave my Mac, when I come back, Mail reconnects automatically to iCloud and gMail, but it remains "forever" (over 20 minutes) trying to reconnect to Exchange.
I've learned the trick of switching my WiFi off and and then on again which makes Mail connect instantaneously to Exchange, but this is a workaround. This happens with all WiFis, so it doesn't seem to be a problem with a specific WiFi network.
Has anyone experienced the same problem?

Back up all data.
Unlock the Network preference pane, if necessary, by clicking the lock icon in the lower left corner and entering your password. Cllck Advanced, open the DNS tab, and change the server addresses to the following:
8.8.8.8
8.8.4.4
That's Google DNS. Click OK, then Apply.
Test. Any difference?
Notes:
1. If you lose Internet access after making the above change to your network settings, delete the Google servers in the Network preference pane, then select the TCP/IP tab and click Renew DHCP Lease. That should restore the original DNS settings; otherwise restore them yourself. Remember that you must click Apply in order for any changes to take effect.
2. I don't use Google DNS myself, though I have tested it, and I'm not recommending it or any other DNS provider; the server addresses are offered merely for testing purposes. There may be privacy and technical issues involved in using that service, which you should investigate personally before you decide whether to keep the settings. Other public DNS services exist.

Exchange 2013 sp1 smtp NTLM auth for child domain users

i have exchange organization with exchange 2007 sp 3 & exchange 2013 sp1.
there are all users in Exchange 2013 server (mail flow is through Exchange 2013 server)
i have single forest, 2 site (site1, site2), root domain root.local and 1 child domain ch.root.local
DC for child domain is located in site2 (dc.ch.root.local)
multirole exchange 2013 server is installed in root domain.
i am traing to configure smtp receive connector with NTLM auth and have one problem.
when user in child domain try send email through this receive connector i see in log
<,AUTH NTLM,
>,334 <authentication response>,
*,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
*,CH\user1,authenticated
*,,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
*,,"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 192.168.1.15:465"
but authentication is succesfull for users from root domain.
why do it can be?
Thanks.

thanks for link
at smtp receive logs (Hub transport role) i've found the next:
Client Proxy EXMAIL2013,08D134DAF6CE1C51,49,192.168.1.15:465,
*,NT AUTHORITY\SYSTEM,authenticated
>,235 <authentication response>,
<,XPROXY SID=08D130D354F520D1 IP=192.168.1.21 PORT=57085 DOMAIN=[192.168.1.21] CAPABILITIES=0 SECID=Uy0xxx...
*,,Error while looking up SamAccountName chuser: The user name or password is incorrect.\r\n
*,None,Set Session Permissions
>,250 XProxy accepted but user identity could not be obtained,

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

New exchange 2013 setup

my existing 2010 environment:
EXCH1 - datacenter 1
EXCH2 - datacenter 2
DAG, both Internet Facing.
Today I installed 3 Exchange 2013 CAS/Mail servers.
EXCH3 - datacenter 1
EXCH4 - datacenter 2
EXCH5 - DR site
I haven't setup mailboxes or anything yet, just external and internal URL's, a wildcard cert and internally OWA successfully proxy's via 2013 then redirect back to 2010 OWA as it should. All 3 2013 servers setup identical... :-)
However, and here is the problem - when EXCH5 is turned on users get prompted for the EXCH5 server cert, when I turn EXCH5 off they do not get prompted.
Any ideas where I should look?
info update -------------------------------------------
while the cert prompt is for the exch5 server cert when I view the cert its actually the correct wildcard public cert I'm using and want.
I have verified that all the virtual directories (via EAC) have the correct internal and external URL's and that the cert is bound to the SMTP and IIS services. One other clue, when I try to launch ecp from exch5 it redirects and logs me into OWA.
Not doing this on any other exch server.
open to suggestions :-)

Hi,
According to your description, it’s wildcard certificate in your environment. And I recommend you check the Outlook provider configuration: get-outlookprovider |fl identity, CertPrincipalName
Additionally, I’d like to confirm the name in the security alert.
If you have any question, please feel free to let me know.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Exchange 2013 - Delivery Groups, Routable DAGs and Delivery Queues

Hey Team,
I am trying to better understand Exchange 2013 Delivery Groups and Boundaries. I think I have it almost figured out, I reviewed this article here which helped clear it up for me:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-mail-flow-part2.html
I need to understand the difference between and exchange 2013 delivery and how a delivery is group is different from the way that Exchange 2010 routed mail.
For some reason I am just not getting the differences between 2013 and 2010 in terms of message delivery.
Thanks,
Robert
Robert

Hi,
In Exchange 2013 there are only two roles, while five roles in Exchange 2010. There is difference between Exchange 2010 and Exchange 2013 on mail delivery.
The following articles can help you to understand the difference of mail delivery between Exchange 2010 and Exchange 2013.
Mail routing (For Exchange 2013)
http://technet.microsoft.com/en-gb/library/aa998825(v=exchg.150).aspx
Understanding Message Routing (For Exchange 2010)
http://technet.microsoft.com/en-gb/library/aa998825(v=exchg.141).aspx
Hope this is helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

What is new in Exchange 2013 Mail Recall

As we all know that there are limitation in mail recall in Exchange, is there anything new in Exhange 2013 in mail recall ? It has always been a client-side operation, will it ever be a server-side operation ? Anybody with an idea ?
Message recall is not successful if one or more of the following conditions are true:
•The recipient is not using Outlook.
•The recipient is not logged on to the mail service provider.
•The recipient is using Cached Exchange Mode and is working offline.
•The original message is moved from the Inbox. This can occur when rules are used.
•The original message is opened first and marked as read. This can occur when the message is displayed in the Preview Pane or Reading Pane.

It has always been a client-side operation, will it ever be a server-side operation ?
It is more of an administrative task, but you can still use Search-Mailbox to purge unwanted items from the server. Mail recall it is still an Outlook-side action only, you may find some 3thd party plugin to recall message from OWA.
Bruce Jourdain de Coutance - Consultant MVP Exchange http://blog.brucejdc.fr

Establish mail flow from Exchange 2007 to Exchange 2013

I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.
Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

Was this question answered. We're in the same situation now as we're upgrading to Exchange 2013 from 2007. The latest CU certainly helped. Initially the test mailboxes on Exchange 2013 couldn't email each other - This was resolved with CU7 and
using "Custom Settings" - manually entered IPs for DNS in the Exchange Admin Center "DNS Lookups".
Issue at the moment Test mailboxes on Exchange 2013 cannot email mailboxes on 2007 or visa-versa and mail from external sources queues on the 2007 box.
Any assistance will be greatly appreciated.

Cannot send mail from Exchange 2013 to Exchange 2007

I have an
Exchange 2007server with all roles in the same server (Version:
08.03.0327.001 ) on a Windows 2008 R2 server. I have now installed two Exchange 2013 servers both with CAS and MBX roles on Windows 2012 servers
(full patched). There is also a DAG between the new servers. All mail goes through a BorderWare besides the internal mail.
I can send mail from both environments to the Internet. I can also send internal mail from Exchange 2007 to Exchange 2013.But the problem is that I am unable to send from Exchange 2013 to Exchange 2007. I've debugged, but not solved the problem and there are
few articles on the Internet.
Any suggestions?

These two sentences are in conflict : "I can also send
internal mail
from Exchange
2007 to
Exchange 2013. But
the problem is
that I am unable
to send from Exchange
2007 to
Exchange 2013. "
Can you describe what is your real problem? Flow from E2007->E2013? Or vice versa?
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

How can I script out automatic mail profile connection to Exchange 2013

We use a program called Desktop Authority 9.1 that is a fully featured kixstart based logon user profile customization tool. It does a full gamout of things like map drives, folder redirection, import registry edits, run silent application installers,
and of course create the Outlook profile.
There's no issues with this tool creating an outlook profile internally to mail.domain.com, and even detecting laptops and configuring it for outlook anywhere to webm.domain.com and cached mode.
Issue I'm having is trying to roll out Exchange 2013. This tool simply does not seem to create the mail profile. On a test computer I have the hosts file pointed to the new 2013 server from these names: webm, mail, autodiscover. At log
on I simply get an error "The name cannot be resolved. The name cannot be matched to a name in the address list." When you click OK you get a little confusing dialog box with the exchange server name: mail and the mailbox: windows
user ID.
So I tried to do this manually in the Mail (32-bit) control panel applet. It doesnt matter if I put in mail, mail.domain.com, webm, webm.domain.com, email (the netbios name of exchange 2013), etc.. I get the same error. I went into More settings
> Connection > connect to microsoft exchange using HTTP and in the proxy settings I have webm.domain.com, connect SSL Only, only connect to proxy servers that have the name: msstd:webm.domain.com, and the rest is checked and NTLM Authentication is checked.
I simply CANNOT manually create an outlook profile at all. I can surely delete this one, start outlook, click next through the wizard taking all the default options and get Outlook configured that way (via Autodiscover service), but I need a way to
do it manually so I can have Desktop Authority do it manually. Why? Two major reasons:
1. If our end users are greeted with an Outlook startup wizard every time they go to a different computer, and have to click next through it, our help desk is going to be overwhelmed with "what is this outlook startup wizzard?" questions.
2. Desktop Authority also attaches additional mailboxes. We need the outlook profile passed through DA's scripting so different users departmental voice mailboxes are attached in their outlook. IE) Mailbox VM_FAX_Accounting is attached
to all of the accounting associates Outlook.

Ok I found another way to get autodiscover to work..
In Group Policy go to User Configuration > Administrative Templates > Microsoft Office 2010 (and 2013 in my case) > Miscellaneous > Suppress recommended settings dialog > Change to ENABLED.
Now go to User Configuration > Administrative Templates > Microsoft Outlook 2010 (and 2013 in my case) > Account Settings > Exchange > Automatically configure profile based on Active Directory Primary SMTP address > Change to ENABLED.
Now for the shared mailboxes, I guess when we plan to migrate a department, their shared mailbox MUST be migrated from 2007 to 2013 on the same evening, and then we must go into that shared mailbox and ensure each individual user has "Full access
permissions" to it.
Now in Desktop Authority we publish this reg file:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover\RedirectServers]
"autodiscover-s.outlook.com"=hex(0):
"autodiscover.outlook.com"=hex(0):
"autodiscover.domain.com"=""
[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover\RedirectServers]
"autodiscover-s.outlook.com"=hex(0):
"autodiscover.outlook.com"=hex(0):
"autodiscover.domain.com"=""
[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover\RedirectServers]
"autodiscover-s.outlook.com"=hex(0):
"autodiscover.outlook.com"=hex(0):
"autodiscover.domain.com"=""
Why that? Well it turns out further testing when I added full permission to a new 2013 test shared mailbox, yet another nag screen was presented in Outlook which states "Allow this website to configure [email protected] server settings? autodiscover.domain.com/autodiscover/autodiscover.xml
- Your account was redirected to this website for settings. You should only allow settings from sources you know and trust. (Allow) (Cancel). If end users see this, you can bet our helpdesk calls will be out of control. We undergo security
awareness training and they will question ANYTHING resulting in redirect or dialog boxes asking about trust, and really that's a good thing.
That registry should I think handle Outlook 2007, 2010, 2013, and we will just have to maintain it for future versions.
We maybe have, I dont know less than 5 Outlook 2007 installs and they are on spare laptops, so If I want to cover it all I just have to download the Office 2007 ADMX templates for Group Policy so I can change those two settings above as well.
The other way I thought was to use powershell and script something out to pull from Exchange the GUID, append the @domain.com and put that into a variable that our Desktop Authority application can plug in at startup. But thats a little too much custom
programming whereas I think using GPO's and documented registry keys may be a better fit.
I just have to do testing to figure out what's going to happen to the users profile if it already exists on 2007, then its migrated to 2013. Will it be deleted? Will they lose all of their signatures? I know for many on network
PC's they will be going from direct mapi connection to Cached mode. Is that a good thing? I would imagine less load on the server and network once the mail is downloaded.
We would plan on a slow migration on a departmental basis. Luckily our departments have their own user OU's so applying this group policy can be done in the same manor.

Querying Exchange 2013 Mail server for email items using c# and Exchange Web Services

I am trying to upgrade an existing application that reads Exchange 2003 using WebDAV. The mail server is to be upgraded to Exchange 2013, so I am checking how I can use EWS.
I have a problem in that although I know the inbox has unread items with attachments, the query I am running against the
FindItems object is returning empty (results.totalCount=0)
Here is my code snippet:
private static void GetAttachments(ExchangeService service)
// Return a single item.
ItemView view = new ItemView(100);
ServicePointManager.ServerCertificateValidationCallback = CertificateValidationCallBack;
ExchangeService service = new ExchangeService(ExchangeVersion.Exchange2010_SP2);// .Exchange2007_SP1);
service.UseDefaultCredentials = true;
service.AutodiscoverUrl("[email protected]", RedirectionUrlValidationCallback);
ItemView view = new ItemView(1);
string querystring = "HasAttachments:true Subject:'ATTACHMENT TEST' Kind:email";
// Find the first email message in the Inbox that has attachments.
// This results in a FindItem operation call to EWS.
FindItemsResults<Item> results = service.FindItems(WellKnownFolderName.Inbox, querystring, view);
//FindItemsResults<Item> results = service.FindItems(WellKnownFolderName.Inbox, new ItemView(50));
if (results.TotalCount > 0)
// looping through all the emails
for (Int16 iDx = 0; iDx < results.TotalCount-1; iDx++)
EmailMessage email = results.Items[iDx] as EmailMessage;
if (email.IsRead == false) {
// Request all the attachments on the email message. This results in a GetItem operation call to EWS.
email.Load(new PropertySet(EmailMessageSchema.Attachments));
foreach (Attachment attachment in email.Attachments)
if (attachment is FileAttachment)
FileAttachment fileAttachment = attachment as FileAttachment;
What I am supposed to be doing is reading all the unread emails in the target inbox (only one Exchange server) and taking the attachments on disk so I can then add them as attachments as new cases on SalesForce.
Where am I going wrong?
Also, this line:
ItemView view = new ItemView(100);
was:
ItemView view = new ItemView(1);
Surely that will only look for one email item, right?

thanks, do you know why I would be getting an error message like 'The specified object was not found in the store'
here is my code:
ServicePointManager.ServerCertificateValidationCallback = CertificateValidationCallBack;
ExchangeService service = new ExchangeService(ExchangeVersion.Exchange2010_SP2);// .Exchange2007_SP1);
service.Url = new Uri("https://sgexc.bocuk.local/EWS/Exchange.asmx");
//creates an object that will represent the desired mailbox
Mailbox mb = new Mailbox(@"[email protected]");
//creates a folder object that will point to inbox folder
FolderId fid = new FolderId(WellKnownFolderName.Inbox, mb);
//this will bind the mailbox you're looking for using your service instance
Folder inbox = Folder.Bind(service, fid);
FindItemsResults<Item> findResults = service.FindItems(new FolderId(WellKnownFolderName.Inbox, new Mailbox("[email protected]")),new ItemView(10));
it's happening on this line:
Folder inbox = Folder.Bind(service, fid);
and if I try to use AutoDiscoverURL then I just see my own inbox.

Large Mail.que database in Exchange 2013

[Background]
Since Exchange 2013 is released, some user may come across the following situations:
The space of disk C is used up.
The transport service stops processing messages.
The Mailbox server is crash.
In this case, the issue can be resolved with checking with the mail.que file which is in the following path on the Mailbox server:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue
[Symptom]
The Mail.que file on all Exchange 2013 servers grows very large and it’s even over 20 GB.
[Cause]
It’s a by design behavior.
Different from the previous Exchange server, Safety Net which has the same function with the Transport dumpster in Exchange 2013 takes up the volume of the mail.que file and
it’s the feature which is responsible for the large size of the mail.que in Exchange 2013.
And here is a reference about the feature Safety Net in Exchange 2013:
http://technet.microsoft.com/en-us/library/jj657495(v=exchg.150).aspx
[Workarounds]
1. Allocate large space for the Exchange 2013 installation or increase the volume for Exchange 2013.
These articles will also provide further detail of size calculating:
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
(See section: “Transport storage requirements”)
2. Moved queue database to another drive by using
Move-DatabasePath
3. Reduce the SafetyNetHoldTime and MessageExpirationTimeouton values to one day (default values are 2 days). And these commands can be in use:
Set-TransportConfig SafetyNetHoldTime 1.00:00:00
Get-TransportService | Set-TransportService -MessageExpirationTimeout 1.00:00:00
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

[Background]
Since Exchange 2013 is released, some user may come across the following situations:
The space of disk C is used up.
The transport service stops processing messages.
The Mailbox server is crash.
In this case, the issue can be resolved with checking with the mail.que file which is in the following path on the Mailbox server:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue
[Symptom]
The Mail.que file on all Exchange 2013 servers grows very large and it’s even over 20 GB.
[Cause]
It’s a by design behavior.
Different from the previous Exchange server, Safety Net which has the same function with the Transport dumpster in Exchange 2013 takes up the volume of the mail.que file and
it’s the feature which is responsible for the large size of the mail.que in Exchange 2013.
And here is a reference about the feature Safety Net in Exchange 2013:
http://technet.microsoft.com/en-us/library/jj657495(v=exchg.150).aspx
[Workarounds]
1. Allocate large space for the Exchange 2013 installation or increase the volume for Exchange 2013.
These articles will also provide further detail of size calculating:
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
(See section: “Transport storage requirements”)
2. Moved queue database to another drive by using
Move-DatabasePath
3. Reduce the SafetyNetHoldTime and MessageExpirationTimeouton values to one day (default values are 2 days). And these commands can be in use:
Set-TransportConfig SafetyNetHoldTime 1.00:00:00
Get-TransportService | Set-TransportService -MessageExpirationTimeout 1.00:00:00
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.
You cant move the queue database with move-databasepath. You have to follow this method:
http://technet.microsoft.com/en-us/library/bb125177(v=exchg.150).aspx
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 to Exchange 2013 mail flow?

We are planning to migrate Exchange 2010 to Exchange 2013.
I understand that we need to upgrade the CAS to 2013 for Internet Facing.
What about mail flow. Currently, Internet mail flows to Exchange 2010 (single site). Can I keep it for sometime after introducing 2013 and do the cutover of HUB once all the mailboxes are moved to 2013? Or I have to get the mail flow to 2013 first.
Also, how does HUB 2010 transfer mail or receive mail from 2013? Does it get from the CAS proxy in 2013 or from HUB?
Thanks!!!

Yes, you can. But my preference is to move the mail routing early in the migration, usually even before moving mailboxes, because I believe it reduces the risk of a service interruption.
I believe it goes through the front-end transport on the CAS, since that is the TCP port 25 service.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013 resubmit mails

Similar Messages

Maybe you are looking for