locked
Mails stuck at Edge sync Default-first-site-name to internet RRS feed

  • Question

  • Hi

    I installed edge transport emails receive correctly but doesn't send.it stuck at mailbox and not deliver at edge server.


    thank you.


    • Edited by Milad Plus Thursday, April 16, 2020 6:54 PM
    Sunday, September 2, 2018 6:28 AM

All replies

  • Hi,

    Could you share the entire message in the queue viewer with us? (Information in "Last Error")

    For troubleshooting:

    1. Ensure that the IP set in InternalSMTPServers is correct.
    2. Create a send connector for the Edge Sync in MBX server.

    Set-SendConnector "edgesync - default-first-site-name to internet" -DNSRoutingEnabled $false -DomainSecureEnabled $false -SmartHosts xxx.xxx.xxx.xxx

    3. Check if it is a connector authentication issue. Similar link:

    EdgeSync won't work, Outbound mail getting stuck!

    Regards,

    Manu Meng


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

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, September 3, 2018 3:24 AM
  • Hi

    thank you for reply

    It doesn't have last error field.

    I have one Mailbox server that is in internal smtp.10.0.8.193

    I have a send connector like this already . but its checked MX record associates with recipient domain not smart host.

    MX record in DNS is pointing to Edge transport with higher Priority than the MX record for Mailbox.

    which log I should check?





    You should have the last error field:

    Run the following command, we could get more details.

    Get-queue -Server <MBX Server> | fl 


    Regards,

    Manu Meng


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

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, September 4, 2018 9:32 AM
  • RunspaceId                       : 1870cc08-fa3c-4354-b4cd-0641d8e8d013
    DeliveryType                     : SmtpRelayWithinAdSiteToEdge
    NextHopDomain                    : edgesync - default-first-site-name to internet
    TlsDomain                        :
    NextHopConnector                 : 8e21969d-38f2-4a45-a7d7-85f5e00ca482
    Status                           : Retry
    MessageCount                     : 1
    LastError                        : [{LED=451 4.4.395 Target host responded with error. -> 451 5.7.3 Cannot achieve Exchange Server
                                       authentication};{MSG=};{FQDN=EdgeTransport.ibto.ir};{IP=10.0.16.13};{LRT=9/4/2018 2:11:53 PM}]
    RetryCount                       : 0
    LastRetryTime                    : 9/4/2018 2:11:53 PM
    NextRetryTime                    : 9/4/2018 2:12:53 PM
    FirstRetryTime                   : 9/4/2018 2:11:53 PM
    DeferredMessageCount             : 0
    LockedMessageCount               : 0
    LockedScopes                     :
    MessageCountsPerPriority         : {0, 1, 0, 0}
    IncludeInSlaCount                : 0
    DeferredMessageCountsPerPriority : {0, 1, 0, 0}
    RiskLevel                        : Normal
    OutboundIPPool                   : 0
    NextHopCategory                  : Internal
    IncomingRate                     : 0
    OutgoingRate                     : 0
    Velocity                         : 0
    OverrideSource                   :
    QueueIdentity                    : Exchange\445
    PriorityDescriptions             : {High, Normal, Low, None}
    Identity                         : Exchange\445
    IsValid                          : True
    ObjectState                      : New
    
    RunspaceId                       : 1870cc08-fa3c-4354-b4cd-0641d8e8d013
    DeliveryType                     : Undefined
    NextHopDomain                    : Submission
    TlsDomain                        :
    NextHopConnector                 : 00000000-0000-0000-0000-000000000000
    Status                           : Ready
    MessageCount                     : 0
    LastError                        :
    RetryCount                       : 0
    LastRetryTime                    :
    NextRetryTime                    :
    FirstRetryTime                   :
    DeferredMessageCount             : 0
    LockedMessageCount               : 0
    LockedScopes                     :
    MessageCountsPerPriority         : {0, 0, 0, 0}
    IncludeInSlaCount                : 0
    DeferredMessageCountsPerPriority : {0, 0, 0, 0}
    RiskLevel                        : Normal
    OutboundIPPool                   : 0
    NextHopCategory                  : Internal
    IncomingRate                     : 1
    OutgoingRate                     : 1
    Velocity                         : 0
    OverrideSource                   :
    QueueIdentity                    : Exchange\Submission
    PriorityDescriptions             : {High, Normal, Low, None}
    Identity                         : Exchange\Submission
    IsValid                          : True
    ObjectState                      : New

    I receive Mails successfully but no send

    and I use Wilde card certificate for exchange.

    I set smart host my mail box server


    The smart host should be Edge server's IP or FQDN, not the Mailbox server's.

    Check if you have created all the connectors described in the following article:
    Configure Internet mail flow through Edge Transport servers without using EdgeSync

    Regards,

    Manu Meng


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

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, September 4, 2018 1:51 PM