none
Exchange Server 2013 has no mail flow after installing anti-spam agents

    Question

  • I just spent an hour typing a detailed description of my problem and your site will not allow me to send it to you.

    I really need help if anyone will.

    My description included links to the TechNet pages I used, and this site is rejecting. After I deleted them, it still rejects my messages.

    Seems I can't even ask a question.


    • Edited by CJProffitt Tuesday, December 19, 2017 7:48 PM Typo
    Tuesday, December 19, 2017 7:03 PM

All replies

  • Hi,

    Sorry for any inconvenience.

    Do you enable Anti-Spam feature on Exchange mailbox sever role as described in this link (including Step3: Specify the internal SMTP servers in your organization)?

    To troubleshooting your question, I want to check:
    1. Does it occur on internal or external mail flow?
    2. Any NDR or error returns back?

    Please check the status of Transport service on each Mailbox server, then view the transport agent by Get-TransportAgent.

    Also, open Queue Viewer (under Exchange Toolbox) to check the Last Error.

    Regards,
    Allen Wang


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, December 20, 2017 11:21 AM
    Moderator
  • Thanks for your reply,

    All mail flow to the 2013 server mailbox located in it's database. I am trying to migrate from 2007sp3.

    Below is the narrative I tried to enter yesterday.

    I am currently trying to ultimately upgrade exchange 2007sp3 to 2016, but am now trying to get exchange 2013sp1 to run along side of 2007. I was following a blog on TechNet social to get to exchange 2013:

    <your site will not allow me to include the TechNet link>

    I had both running and a test mailbox able to send and receive from exchange users, and external smtp addresses. I was at the step of testing the functionality and it seemed to be working.

    Then I ran the installation script to install the anti-spam agents when everything failed. Procedure says to restart the transport service but I rebooted the machine and then I could not get powershell to connect, nor the admin webpage. This is the procedure I used to install anti spam scripts:

    <your site will not allow me to include the TechNet link>

    The old server (2007) is currently running anti-spam protection, the new one will need it too. Probably should have waited until the final version in hind sight.

    1. I then scrapped the virtual machine that exchange 2013 was installed on and began again of which exchange 2013 is running on WS2008R2 operating system.
    2. I then performed a setup in recovery mode to restore the server and managed to get the services running again:
    3. The database located in 2013 would not mount, so I performed a PS mount-database command, it created a new database with a notice that "component files were missing, create new database?". I executed the command and new database exists and is mounted by 2013, I re-added the test mailbox.
    4. Active-Sync on 2013 works to connect mobile device to old server mailbox database.
    5. OWA on 2013 works to connect to test mailbox, but no inbound mail, no sent items, everything attempted to be sent is in draft folder
    6. Calendar events can be added and edited for test mailbox on 2013 server.
    7. Currently, there are 5 receive connectors that are installed on 2013 server, all of which are default, I did not install them separately and there were no send connectors. I did install an outbound send connector destined to '*' and SMTP using dns mx record for delivery.

    Windows app log shows errors in transport service stating no route can be found to the outbound send connector.

    Attempts to send mail from the test mailbox installed on the 2013 server are saved in draft folder.

    Any ideas? Please help.

    Thanks,
    CJ

    Wednesday, December 20, 2017 7:13 PM
  • To answer your question about the TechNet procedure for anti-spam.

    No.

    The article I used was:

    https://technet.microsoft.com/en-us/library/bb201691(v=exchg.150).aspx

    And the blog for the migration process was:

    https://blogs.technet.microsoft.com/meamcs/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration/

    Which was working fine until I strayed from the path and tried to enable anti-spam!

    Thanks for your help!CJ

    Wednesday, December 20, 2017 7:37 PM
  • One last thing, yes I did step three to add smtp servers that are omitted in senderid filtering.

    Currently, it only has the local host IP address (127.0.0.1).

    That is the function of this entry right? SMTP servers listed are bypassed in sender id filtering?

    Wednesday, December 20, 2017 7:43 PM
  • Hello?

    BTW, the TechNet article I used seems to be the same as the one you referred to  but not as comlete.

    Have you had a chance to look over the details I have added Alan?

    Is using the loopback address the same as the assigned ip address of the server in this case?

    Thanks,

    CJ

    Thursday, December 21, 2017 5:47 PM
  • Troubleshooting:

    1. ALL MAILFLOW PERIOD.

    2 Yes, NDR for every attempt except for outbound which messages just go to the Draft folder in OWA.

    Thursday, December 21, 2017 5:49 PM
  • Thanks for your update.

    I notice that the mail flow works fine after install Exchange 2013 to Exchange 2007 environment, and issue arise after install Anti-Spam feature.

    Please run Get-TransportAgent to list agent, then disable all anti-spam agent (for example: Content Filter agent, Sender ID agent, Sender Filter agent, RecipientFilter agent) and test the mail flow.

    Regards,
    Allen Wang


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, December 25, 2017 7:27 AM
    Moderator
  • OK. Thanks!
    I disabled each individual agent but when the "Get-TransportAgent" command is run I get everything is still enabled. BTW, the agents are enabled on the legacy server (2007 server). Here is the response:

    [PS] C:\Windows\system32>get-transportagent

    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

    But as for example when I get individual agents:

    [PS] C:\Windows\system32>Get-ContentFilterConfig


    RunspaceId                                          : 2fd1d4d2-eabc-4778-825e-a5c8296d97a2
    Name                                                   : ContentFilterConfig
    RejectionResponse                                 : Message rejected as spam by Content Filtering.
    OutlookEmailPostmarkValidationEnabled  : True
    BypassedRecipients                                : {}
    QuarantineMailbox                                 : Administrator<at>lsscpa.com
    SCLRejectThreshold                                : 4
    SCLRejectEnabled                                   : True
    SCLDeleteThreshold                                : 9
    SCLDeleteEnabled                                   : False
    SCLQuarantineThreshold                         : 3
    SCLQuarantineEnabled                            : False
    BypassedSenders                                   : {}
    BypassedSenderDomains                         : {}
    Enabled                                                 : False
    ExternalMailEnabled                                : True
    InternalMailEnabled                                 : False
    AdminDisplayName                                  :
    ExchangeVersion                                     : 0.1 (8.0.535.0)
    DistinguishedName                                : CN=ContentFilterConfig,CN=Message     
                Hygiene,CN=Transport Settings,CN=First Organization,CN=Microsoft
                Exchange,CN=Services,CN=Configuration,DC=lsacpa,DC=local
    Identity                                                 : ContentFilterConfig
    Guid                                                     : 709d7653-73b9-4489-824c-429994645f40
    ObjectCategory                            : lsacpa.local/Configuration/Schema/ms-Exch-Message-
                                                      Hygiene-Content-Filter-Config
    ObjectClass                                            : {top, msExchAgent,
                                       msExchMessageHygieneContentFilterConfig}
    WhenChanged                                       : 12/22/2017 12:15:10 AM
    WhenCreated                                         : 10/24/2010 10:42:02 PM
    WhenChangedUTC                                  : 12/22/2017 6:15:10 AM
    WhenCreatedUTC                                   : 10/25/2010 3:42:02 AM
    OrganizationId                                       :
    OriginatingServer                                    : behemoth.lsacpa.local
    IsValid                                                    : True
    ObjectState                                            : Unchanged

    The test-mail-flow command for the mailbox on the 2013 server FAILS:

    [PS] C:\Windows\system32>test-mailflow -targetemailaddress tanked<at>lsscpa.com

    RunspaceId         : 2fd1d4d2-eabc-4778-825e-a5c8296d97a2
    TestMailflowResult : *FAILURE*
    MessageLatencyTime : 00:00:00
    IsRemoteTest       : True
    Identity           :
    IsValid            : True
    ObjectState        : New

    All other mailboxes exist on the legacy server.

    Note, there is no system mailbox on the 2013 server.

    Finally, FYI, here is the get-exchangeserver command:
    The name of the legacy server is BEASTY
    The name of the exch 2013 server is Pucker

    [PS] C:\Windows\system32>get-exchangeserver -status | format-list


    RunspaceId                      : 2fd1d4d2-eabc-4778-825e-a5c8296d97a2
    Name                            : BEASTY
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\Mailbox
    Domain                          : lsacpa.local
    Edition                         : Standard
    ExchangeLegacyDN                : /o=First Organization/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=BEASTY
    ExchangeLegacyServerRole        : 0
    Fqdn                            : BEASTY.lsacpa.local
    CustomerFeedbackEnabled         :
    InternetWebProxy                :
    IsHubTransportServer            : True
    IsClientAccessServer            : True
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : False
    IsE15OrLater                    : False
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : False
    IsFrontendTransportServer       : False
    NetworkAddress                  : {ncacn_vns_spp:BEASTY, netbios:BEASTY, ncacn_np:BEASTY, ncacn_spx:BEASTY,
                                      ncacn_ip_tcp:BEASTY.lsacpa.local, ncalrpc:BEASTY}
    OrganizationalUnit              : lsacpa.local/BEASTY
    AdminDisplayVersion             : Version 8.3 (Build 83.6)
    Site                            : lsacpa.local/Configuration/Sites/Default-First-Site-Name
    ServerRole                      : Mailbox, ClientAccess, HubTransport
    ErrorReportingEnabled           : True
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    :
    StaticExcludedDomainControllers : {}
    MonitoringGroup                 :
    WorkloadManagementPolicy        :
    CurrentDomainControllers        : {behemoth.lsacpa.local}
    CurrentGlobalCatalogs           : {behemoth.lsacpa.local}
    CurrentConfigDomainController   : behemoth.lsacpa.local
    ProductID                       : 90554-351-4743296-05214
    IsExchangeTrialEdition          : False
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 00:00:00
    Identity                        : BEASTY
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=BEASTY,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                      Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lsacpa,DC=local
    Guid                            : 308ce95e-7a89-40e9-a1e2-f67b75cf1e6f
    ObjectCategory                  : lsacpa.local/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 11/18/2017 12:02:54 AM
    WhenCreated                     : 10/24/2010 10:45:37 PM
    WhenChangedUTC                  : 11/18/2017 6:02:54 AM
    WhenCreatedUTC                  : 10/25/2010 3:45:37 AM
    OrganizationId                  :
    OriginatingServer               : behemoth.lsacpa.local
    ObjectState                     : Unchanged

    RunspaceId                      : 2fd1d4d2-eabc-4778-825e-a5c8296d97a2
    Name                            : Pucker
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\V15\Mailbox
    Domain                          : lsacpa.local
    Edition                         : Standard
    ExchangeLegacyDN                : /o=First Organization/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Pucker
    ExchangeLegacyServerRole        : 0
    Fqdn                            : PUCKER.lsacpa.local
    CustomerFeedbackEnabled         : True
    InternetWebProxy                :
    IsHubTransportServer            : True
    IsClientAccessServer            : True
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : True
    IsE15OrLater                    : True
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : True
    IsFrontendTransportServer       : True
    NetworkAddress                  : {ncacn_vns_spp:Pucker, netbios:Pucker, ncacn_np:Pucker, ncacn_spx:Pucker,
                                      ncacn_ip_tcp:PUCKER.lsacpa.local, ncalrpc:Pucker}
    OrganizationalUnit              : lsacpa.local/Pucker
    AdminDisplayVersion             : Version 15.0 (Build 847.32)
    Site                            : lsacpa.local/Configuration/Sites/Default-First-Site-Name
    ServerRole                      : Mailbox, ClientAccess
    ErrorReportingEnabled           : False
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    : behemoth.lsacpa.local
    StaticExcludedDomainControllers : {beasty.lsacpa.local}
    MonitoringGroup                 :
    WorkloadManagementPolicy        : DefaultWorkloadManagementPolicy_15.0.825.0
    CurrentDomainControllers        : {behemoth.lsacpa.local}
    CurrentGlobalCatalogs           : {behemoth.lsacpa.local}
    CurrentConfigDomainController   : behemoth.lsacpa.local
    ProductID                       : 02064-004-0074037-02600
    IsExchangeTrialEdition          : False
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 00:00:00
    Identity                        : Pucker
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=Pucker,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                      Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lsacpa,DC=local
    Guid                            : ecfbaa1f-f84b-4041-8c50-d683bf20ca13
    ObjectCategory                  : lsacpa.local/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 12/19/2017 12:25:51 PM
    WhenCreated                     : 11/23/2017 11:57:57 PM
    WhenChangedUTC                  : 12/19/2017 6:25:51 PM
    WhenCreatedUTC                  : 11/24/2017 5:57:57 AM
    OrganizationId                  :
    OriginatingServer               : behemoth.lsacpa.local
    ObjectState                     : Unchanged

    Thank you again,
    CJ

    Tuesday, December 26, 2017 5:14 AM
  • Please note that the runspace ID for both servers is identical, if that is supposed to be...
    Tuesday, December 26, 2017 5:25 AM
  • Hi,

    Based on my experience, I recommend to check the DNS server on each Exchange server if the message stuck in Draft folder.

    Regards,
    Allen Wang


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, December 27, 2017 10:01 AM
    Moderator
  • Um,

    The legacy exchange server works fine, no mail flow problems. Just the 2013 server. Both use the same DNS server, each has a defined MX record.

    Thursday, December 28, 2017 6:07 AM
  • It would be nice if the "Test-Mailflow" command would actually give some diagnostic info instead of just stating "FAILURE".

    Thursday, December 28, 2017 6:10 AM