Exchange 2013 not delivering all emails

Hi All,
I have a fresh install of Exchange 2013 SP1 with CU5 on Windows Server 2012 R2 and I am having a weird mesage delivery issue. 
Im getting most emails, but some messages I am not getting. They don't show up in my inbox. If i do a Get-MessageTrackingLog, the EventID is listed as FAIL
[PS] C:\Users\Administrator\AppData\Roaming\ClassicShell\Pinned>Get-MessageTrackingLog -MessageSubject "Balance Snapshot" -Start "7/20/2014" | FL
RunspaceId              : 06baa1a8-4732-49df-b00c-0a685d5e75fb
Timestamp               : 7/20/2014 10:43:05 AM
ClientIp                : xxx.xxx.xxx.xxx
ClientHostname          : DC1
ServerIp                : 192.168.0.4
ServerHostname          :
SourceContext           : Sender Id Agent
ConnectorId             : DC1\Default DC1
Source                  : SMTP
EventId                 : FAIL
InternalMessageId       : 1275605286912
MessageId               : <[email protected]>
Recipients              : {[email protected]}
RecipientStatus         : {[{LRT=};{LED=250 2.6.0 <[email protected]>
Queued mail for delivery};{FQDN=};{IP=}]}
TotalBytes              : 0
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : Balance Snapshot: Your Available Balance
Sender                  : [email protected]
ReturnPath              : [email protected]america.com
Directionality          : Incoming
TenantId                :
OriginalClientIp        :
MessageInfo             :
MessageLatency          :
MessageLatencyType      : NoneEventData               : {[DeliveryPriority, Normal], 
I have verbose logging turned on, and its showing the log of the email that is not getting delivered, but no errors. Any ideas?
Brad Nelson MCSE/DCSE/A+/Network+/WCSP

Hi,
From your description, I recommend you disable the Postini anti spam temporarily to determine whether this issue is related to it.
I look forward to your response.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Similar Messages

  • Exchange 2013 not delivering mails to Exchange 2010

    I am upgrading exchange 2010 to exchange 2013 and currently in coexistence.  I cutover the mx to deliver mail to 2013 cas VIP last night and no mail was being received by the 2010 mailboxes, it was all being queued on the 2013 mailbox servers (mailbox
    and cas servers are separate in this deployment.) There are only a few 2013 mailboxes as I have not yet started migrating them.  These 2013 internal mailboxes can not send to exchange 2010 either, but 2010 can send to 2013. 2013 to 2013 mail works
    fine. I have read somewhere about an issue with a receive connector having the same ip range that includes the mailbox servers, but I'm not clear on really which mailbox servers it is alluding to.
    All the exchange 2010 servers are all on the 10.1.1.* network.  Exchange 2013 CAS servers are all on the 10.1.1.* network and the 3 exchange mailbox servers are on 10.1.1.*, 10.1.2.* and 10.30.5.*.  Only 1 AD site.  On one of the 2010 receive
    connectors there is a scope of 10.1.1.0/24  I'm wondering if this is the culprit and by removing it should fix the problem.  Any other ideas would be appreciated.

    Exchange 2013 users are unable to send emails to exchange 2010 users then check your connectors on Exchange 2013 Mailbox server. and yes if you have overlapping of scopes in different connectors then this can happen.
    Kindly mark this as answer if found helpful. Thanks.
    Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

  • Exchange 2013 issues - (new send email Stuck in Drafts not send)

    Exchange 2013 issues - (new send email Stuck in Drafts folder not send)

    I am also having this issue.
    server 2012 VM with exchange 2013. plenty of resources, more than recommended so cannot be a BAck Pressure issue especially as no clients are connected yet.
    In the early stages of setup and testing, mail sent to other mailboxes worked fine in outlook 2007 and OWA but after a few issue that developed and are now resolved, any e-mail send within outlook or OWA just goes straight into the drafts folder.
    I tried, DNS setting changes under roles, on the server, on DNS server, MX DNS records, increased resources, looked at received connectors, changed and even deleted send connectors as this is not required for internal mail. Tried changing authentication
    types but then outlook won't connect to, staying with Basic Auth.
    Have not been able to test inbound e-mail as this is going to replace a production server and is not ready, although I could probably simulate a route from another server and push e-mail to it. Will try tomorrow.
    I have spent about 20 hours trying to figure this out and made probably 40 changes. Change, test, rollback etc. Been searching through loads of forums and technet sites all with no help.
    All services are started, server has been rebooted several times.
    It is also an AD server and has both Exchange roles installed. There is no reason why it should not work. This is so frustrating, we don't have these issues with the now end of life Scalix, or MDaemon or Zimbra. Pity the client wanted a Microsoft solution.
    To be honest there are not a lot of things that cannot be changed in ECP although there is more under exchange powershell however I am not familiar with all the commands yet. I have resorted to watching training videos even though I am a seasoned IT Pro, although
    not so much with exchange it seems.
    I have seen many people have this issue on Exchange 2007, 2010 and 2013. Someone must know how to resolve this or find a work around?
    So far I have an expensive solution the client has purchased that I cannot get running properly.
    Aside from this issue, I really like the new Server 2012 and new Hyper-V.
    I was about to install Exchange Server 2013 on a physical machine due to this f#ckin' issue. But a post for the DNS change has saved my life:
    http://social.technet.microsoft.com/Forums/en-US/exchangeserverpreview/thread/04c0147b-f4e3-4041-a566-310854e71068/ (rafael9908's answer)
    And thanks Jesper Bernle for excellent info provided by your link.

  • Exchange 2013 not receiving emails above 10MB even though MessageReceive Size has been configured

    Exchange 2013 not receiving emails above 10MB even though MessageReceive Size has been configured.
    [PS] C:\Windows\system32>Get-TransportConfig
    AddressBookPolicyRoutingEnabled                             : False
    AnonymousSenderToRecipientRatePerHour                : 1800
    ClearCategories                                            
    : True
    ConvertDisclaimerWrapperToEml                               : False
    DSNConversionMode                                          
    : UseExchangeDSNs
    ExternalDelayDsnEnabled                                     : True
    ExternalDsnDefaultLanguage                                  :
    ExternalDsnLanguageDetectionEnabled                         : True
    ExternalDsnMaxMessageAttachSize                             : 10 MB (10,485,760 bytes)
    ExternalDsnReportingAuthority                               :
    ExternalDsnSendHtml                                        
    : True
    ExternalPostmasterAddress                                   : [email protected]
    GenerateCopyOfDSNFor                                        :
    HygieneSuite                                               
    : Standard
    InternalDelayDsnEnabled                                     : True
    InternalDsnDefaultLanguage                                  :
    InternalDsnLanguageDetectionEnabled                         : True
    InternalDsnMaxMessageAttachSize                             : 10 MB (10,485,760 bytes)
    InternalDsnReportingAuthority                               :
    InternalDsnSendHtml                                        
    : True
    InternalSMTPServers                                        
    : {127.0.0.1}
    JournalingReportNdrTo                                       : <>
    LegacyJournalingMigrationEnabled                            : False
    LegacyArchiveJournalingEnabled                              : False
    LegacyArchiveLiveJournalingEnabled                          : False
    RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
    RedirectDLMessagesForLegacyArchiveJournaling                : False
    MaxDumpsterSizePerDatabase                                  : 18 MB (18,874,368 bytes)
    MaxDumpsterTime                                            
    : 7.00:00:00
    MaxReceiveSize                                             
    : 50 MB (52,428,800 bytes)
    MaxRecipientEnvelopeLimit                                   : 5000
    MaxRetriesForLocalSiteShadow                                : 2
    MaxRetriesForRemoteSiteShadow                               : 4
    MaxSendSize                                                
    : 20 MB (20,971,520 bytes)
    MigrationEnabled                                           
    : False
    OpenDomainRoutingEnabled                                    : False
    RejectMessageOnShadowFailure                                : False
    Rfc2231EncodingEnabled                                      : False
    SafetyNetHoldTime                                          
    : 2.00:00:00
    ShadowHeartbeatFrequency                                    : 00:02:00
    ShadowMessageAutoDiscardInterval                            : 2.00:00:00
    ShadowMessagePreferenceSetting                              : PreferRemote
    ShadowRedundancyEnabled                                     : True
    ShadowResubmitTimeSpan                                      : 03:00:00
    SupervisionTags                                            
    : {Reject, Allow}
    TLSReceiveDomainSecureList                                  : {}
    TLSSendDomainSecureList                                     : {}
    VerifySecureSubmitEnabled                                   : False
    VoicemailJournalingEnabled                                  : True
    HeaderPromotionModeSetting                                  : NoCreate
    Xexch50Enabled                                             
    : True

    hi stephan... lets put in this way... are you sending attachment ...did you checked the max attachment size as mail send size and attachment size are two different things.. please check this for info on different size creteria
    http://technet.microsoft.com/en-us/library/bb124345%28v=exchg.150%29.aspx
    can you please share the output of below three commands... i doubt your receive connector is not configured properly.
    Get-TransportConfig | Format-List -Property MaxReceiveSize, MaxSendSize
    Get-SendConnector | Format-List -Property Identity, MaxMessageSize
    Get-ReceiveConnector | Format-List -Property Identity, MaxMessageSize
    you can also check this link which gives a perfect info on how exchange works for email size... http://rajisubramanian.wordpress.com/2014/01/26/exchange-server-2013-message-size-configuration-detail/
    Mark as useful or answered if my replies helped you solving your query.
    Thanks, Happiness Always
    Jatin
    Skype: jatider2jatin, Email: [email protected]

  • Exchange 2013 not receiving internal and external emails ..

    I have a coexistence of exchange 2007 and exchange 2013 ..2013 mailboxes where able to receive and send mails (internal and external) but suddenly the mail flow has stopped. 
    Mail flow status
    2013 to 2007 = OK
    2013 to internet = OK
    2013 to 2013 = OK
    2007 to 2013 = FAIL
    Internet to 2013 = FAIL 
    incoming internet mails return the NDR below
    Diagnostic information for administrators:
    Generating server: mydomain.com
    [email protected]
    Remote Server returned '< #4.4.7 smtp;400 4.4.7 Message delayed>'
    What could be a possible reason for this? 
    Cheers guys ..
    ..forever is just a minute away*

    Hi Richard,
    Thank you for your question.
    When there is a coexistence of Exchange 2007 and Exchange 2013, external email will be sent and received by Exchange 2013.
    4.4.7 means message expired, message wait time in queue exceeds limit, potentially due to remote server(your Exchange server ) being unavailable.
    If your organization has correct MX record in ISP. We could refer to the following link to check if MX record is correct:
    http://technet.microsoft.com/en-us/library/aa998082(v=exchg.65).aspx
    If we could telnet Exchange server by the following command: telnet mail.domain.com 25
    If there is a receive connector on Exchange 2013 to receive Internet emails, we could create a receive connector to receive message from the Internet by the following link:
    http://technet.microsoft.com/en-us/library/jj657447(v=exchg.150).aspx
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • Outlook Client not showing all emails

    Hi,
    We have signed up for emails on domains.live.com for the domain name kamtress.com 
    We setup Outlook clients in our office using IMAP.
    But the outlook client does not show all emails and also shows lots of copies of sent emails while we would have sent only one.
    Could you please help us out with this issue as to how this can be rectified?
    We use Outlook 2013 on Windows 7.
    Thank you.

    Hi,
    First of all, please make sure your Outlook is fully patched.
    Then, please log on your web mail and check if you can see all your emails. If so, please open your Outlook, go to File > Info > Account Settings > Account Settings > Highlight your Imap account and click
    Change > in the Change Account wizard, check how you set the 'Mail to keep offline' slider. Change it to
    All and then check if you can see all your emails in Outlook now.
    If problem persists, please try to create a new mail profile in Control Panel and set up your IMAP account in the new profile to check if it helps. To configure an email account via IMAP, please refer:
    http://support.microsoft.com/kb/829918/en-us
    Please let me know the result.
    Regards,
    Steve Fan
    TechNet Community Support

  • Not receiving all email to primary Apple ID address since the creation of an alias

    Not receiving all email to primary Apple ID address since the creation of an alias

    All email sent to your iCloud email alias address should be received in your iCloud inbox.  If email is being addressed to your alias when you think it should be addressed to your primary address it may be because the sender replied to an email you inadvertently sent from your alias address.  You might want to confirm that your primary address is set as your default for sending mail.  See "set default address to send from" here: http://help.apple.com/icloud/#/mm6b1a490a.

  • More than 10 email accounts in TB - Not Showing all emails

    Not showing all emails in UNIFIED Inbox Folder
    I HAVE SETUP MORE THAN 10 EMAIL ACCOUNTS IN TB. THEN I SENT A TEST EMAIL TO ALL OF MY EMAIL ACCOUNTS.
    WHEN I CHECK INBOX OF INDIVIDUAL EMAIL ACCOUNT, THERE IS EMAIL AND SHOWING IN INDIVIDUAL INBOX OF ALL EMAIL ACCOUNTS BUT UNFORTUANTELY IT IS NOT SHOWING IN UNIFIED FOLDER of ALL INBOXES. Unified Inbox Folder of all Emails Accounts is only showing few of them.
    PLS ADV.

    Please don't raise multiple threads for the same problem. Follow up at your OP at https://support.mozilla.org/en-US/questions/1003448.
    P.S. Writing ALL CAPS is considered shouting.

  • .Mac account not receiving all emails

    I am not receiving all emails to my main .Mac account. I do receive emails and would never known there was a problem until people started calling to find out why I haven't responded. I have a main .Mac account and two alias accounts, but the address that the emails are being sent to are my main account. Any ideas?

    The junk mailbox is empty. I checked my preferences and disabled it for now to see if that will make a difference. I do have some Rules set up to filter known "sales" emails to delete or change the color but I have not set up any rules to move or filter from friends.

  • Exchange Server 2013: Not Receiving Internet email

    Hello Guys, I have a new Exchange 2013 install and i am having problems receiving internet email. When testing from https://www.testexchangeconnectivity.com it fails at the last step when it tries to send a test email. I get the following response:
    The server returned status code 451 - Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
    Exception details:
    Message: Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
    Type: System.Net.Mail.SmtpException
    Stack trace:
    at System.Net.Mail.DataStopCommand.CheckResponse(SmtpStatusCode statusCode, String serverResponse)
    at System.Net.Mail.DataStopCommand.Send(SmtpConnection conn)
    at System.Net.Mail.SmtpClient.Send(MailMessage message)
    at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()
    Any Suggestions??

    http://gerhardwessels.wordpress.com/2013/05/06/451-4-7-0-temporary-server-error-please-try-again-later-prx2/
    Check the above mentioned settings

  • Out of office replies in Exchange 2013 not working for external recipients

    Hi,
    Few days ago a couple of company workers went to vacation. They set up OOF automatic replies in OWA 2013. However automatic replies are not working for external recipients (outside of company). Internal users (company users) receive OOF notification.
    I'm using smart host in sender connector configuration (SMTP server of internet provider) to deliver emails. Any clues about this problem ? Please find below part of the transaction log. For testing purposes i set up administrator account
    to be on vacation.
    HARED... SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    RECEIVE  SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    DROP     ROUTING 
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    AGENT... AGENT    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    HARED... SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    RECEIVE  SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    AGENT... AGENT    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    TRANSFER ROUTING  [email protected]           
    {[email protected]}             Automatic reply: vacation test
    FAIL     SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test

    Hi Informus,
    Please check if it is allowed in AllowedOOFType of the Remote Domain *
    In Exchange 2013, the only way to see or change the current configuration for automatic replying and forwarding to the Internet is via the Exchange Management Shell (EMS) with PowerShell commands.
    To get the currently configured Remote Domains, use:
    Get-RemoteDomain
    Name                           DomainName                                  
    AllowedOOFType
    Default                        *                                           
    External
    Get-RemoteDomain Default | fl AllowedOOFType, AutoReplyEnabled, AutoForwardEnabled
    AllowedOOFType     : External
    AutoReplyEnabled   : False
    AutoForwardEnabled : False
    To change the settings, use the Set-RemoteDomain command.
    Enable automatic replies
    Set-RemoteDomain -AutoReplyEnabled $true
    Enable automatic forwards
    Set-RemoteDomain –AutoForwardEnabled $true
    Enable OOF for Outlook 2003 and previous (for Exchange 2007 and 2010 support)
    Set-RemoteDomain –AllowedOOFType $ExternalLegacy
    To change all these properties at once, you can use:
    Set-RemoteDomain Default -AutoReplyEnabled $true –AutoForwardEnabled $true –AllowedOOFType $ExternalLegacy
    Note:
    Valid settings for the AllowedOOFType property are:
    External
    This is the default and only allows for the new style OOF messages as introduced in Outlook 2007.
    ExternalLegacy
    This settings allows for both the new style and old style OOF messages and needs to be set if you want to enable external OOF support for Outlook 2003 as well.
    None
    This setting doesn’t allow for the use of OOF messages at all (both internal and external).
    InternalLegacy
    This setting only allows for internal OOF messages to be sent for all Outlook versions.
    Regards,
    Satyajit
    Please “Vote As Helpful”
    if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Migrated Exchange 2013 server - blocking common emails like netflix and amazon?

    We were using Exchange 2010 for years, and recently I upgraded to Exchange 2013 and signed up for Exchange Online Protection over the weekend (all at the same time, upgrade, migration, sign up for EOP, etc.).  Some mail is making it through just fine,
    while a lot of email is being blocked.  EOP says the email was "delivered" but MessageTracking on our exchange box says Event ID: FAIL...
    I'd like to know more about the FAIL ID... how do I find out what made it fail?  I'm guessing it was a transport rule, but when I got to Mail Flow -> Rules - there is NOTHING there.  
    Running "Get-TransportAgent" returns these values:
    I disabled the malware agent manually on my box since I'm using the EOP stuff now... how can I see or edit the rules that are in place if they do not show up as rules in the ECP?
    It's big name companies like amazon, netflix, etc that are getting blocked... I can't see a reason why they would be blocked now on a migrated server and not on my old server... Can anyone provide some insight?  I'd GREATLY appreciate it!

    I would tend to agree with you that you don't need them.
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/security-message-hygiene/anti-spam-and-anti-malware-protection-exchange-2013-part1.html
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • 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.

  • New outlook install not showing all email histories for some users

    Hello,
    I recently installed outlook 2013 on a windows 8 machine connected to exchange. I noticed it is not showing all the email histories for a particular user.  Is there an index that needs to be rebuilt or something?  Some users it shows a
    bunch emails for others it only shows one or two.  Thanks in advance.  

    Hi,
    Do you mean only one particular user couldn't view all messages from Outlook?
    From this sentence "Some users it shows a bunch emails for others it only shows one or two.", it seems that this issue affect some users, not only one.
    If only one user is affected by this problem, you can follow the steps below to check result.
    1. Please check if it displays all mails in OWA.
    2. And please switch between Outlook cached mode and online mode to check result.
    If some users are affected, please check database index status.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 stops receiving external email after about 8 hours

    Hello,
    Just installed 2013 excahnge server 3 days ago. We noticed after the first night that we did not receive any external emails throughout the night.  I could not find anything wrong with receive connectors.  Telnet works internally when this
    happens but NO access from public side testing with telnet.  After I reboot the exchange server everything functions just fine and normal for about 8 hours until it happens again.
    I dont know what to check or look for at this point.  Very new to exchange 2013.  Any kind of advice would be helpful at this time.
    It is not a firewall issue.  Same firewall and set of rules that we use for other/old mail servers.  We only have 1 exchange server that has all roles.
    Lead Pusher

    OK... Did alot of testing and spent some time with Microsoft's support on the phone.
    I believe there is actually two problems going on in this thread.
    1. Exchange 2013 Admins that have changed the default receive connectors are experiencing a conflict on the scope settings. Make sure that none of the receive connectors are using the same ports, and that you have not modified the security settings in anyway
    unless you really know what you are doing.
    If you are unsure of what the settings should be after you have change them, the only suggestion I have right now, (as I have not taken the time to do screen shots or write down all the default settings) is to install Exchange 2013 on a virtual machine and
    look at them, then change back the settings that do not match.
    2. The Malware Agent has a flaw that is causing the the Microsoft Exchange Transport service to endlessly wait on the Malware Agent to process a message that it just can't handle. (Two reboots of the entire server may be needed to clear this, or sometimes
    you can get away with restarting the Microsoft Exchange EdgeSync service.)
    The Microsoft technician had me perform a sequence of steps that highlighted this. To see if this is infact your problem you can perform the following steps.
    A)  Once the Exchange server stops processing messages, figure out the rough time it stopped processing messages.
    B)  Open the event viewer.
    C)  Under "Windows Logs", right click "Application", select "Filter Current Log...", check "Warning" and "Error", then click "OK".
    D) Scroll down the log to the rough time that your Exchange Server stopped processing messages. You are looking for a slew of errors about the same time from "MSExchange Extensibility" (1051), "MSExchange Transport" (9201), "MSExchange
    Transport" (9201), "MSExchange Extensibility" (1056), "MSExchangeTransport" (10003), and "MSExchange Common" (4999).
    It is the "MSExchangeTransport" (10003) that I believe is the real problem. The Microsoft technician agreed. He did not want to spectulate as to exactly what was going on, but it seems to me that since he had me disable the "Malware Agent"
    for now, that it is indeed the problem. 
    E) So.... Open the Exchange Management Console and type "Disable-TransportAgent", followed by enter. It will prompt "Supply values for the following parameters:". Enter "Malware Agent", press enter again. Type "A",
    for yes to all.
    or
    http://technet.microsoft.com/en-us/library/jj150526.aspx"
    F) Go to run, enter "services.msc". On the window that opens, find "Micorosoft Exchange Transport" and restart it.
    I know this is NOT a fix, but a work around that is less than desired as the Malware Agent is a filter to keep unwanted emails out. I highly recommend running some sort of 3rd party spam/Malware filter that has been fully tested to run with Exchange
    2013 if you do this.
    Microsoft is to contact me back once they can figure out why this is happening, and I believe in the end a patch for Exchange 2013 will be produce to correct the problem.
    In the mean time.... don't waste your money on paying Micorosoft for support, as I have already done this.
    For the individuals who say they are not experiencing trouble, I am going to go out on a limb here and say that either you have a 3rd party software program that is filtering the mail before it reaches the Malware Agent, you have disabled the Malware Agent,
    or you are using another mail server to forward email to your Exchange 2013 server. With either of these cases you are much less likely to see this problem.
    One last issue that a few people may be experiencing, is Exchange 2013, running on Server 2012 that is a VM. Several VM setups have a bug with the VM NIC management interface and Windows Server if you are using the same NIC for both. For example Xen
    Server 5.6 and XEN XCP both have this bug. There is an patch for XEN Server 5.6, but so far nothing for Xen XCP.
    I have spent many hours trying to figure my problems with Exchange 2013 and I will not swear that my entire post is correct, but I have gotten very much closer to a stable mail server after much work. If you feel that anything is incorrect, please reply
    back and let me know why, so that we may all benifit.
    P.S. Sorry for the mis-spellings and what not, I am very tired at the moment, and was forced to use explorer, because this site is not liking Chrome at the moment. (Will not let me login)

Maybe you are looking for