none
Incoming mail getting stuck on Edge Server with 451 4.4.0

    Question

  • 451 4.4.0 smtpsend.suspiciousremoteservererror; remote server disconnected abruptly

    Tried every solution possible but still getting this error. The mail flow has been working fine for a few months.


    • Edited by shaikhNRB Sunday, March 6, 2016 9:54 AM
    Sunday, March 6, 2016 4:42 AM

Answers

  • This issue has been resolved .. the problem was with a Layer 7 firewall rule for P2P traffic.. I had it blocked as soon as i removed the rule the issue went away and has been that way for the last 24 hours.

    I hope this helps someone looking for answers.

    • Marked as answer by shaikhNRB Tuesday, March 15, 2016 4:55 AM
    Tuesday, March 15, 2016 4:52 AM

All replies

  • Incoming mail is stuck in a queue?  Which queue?  Normally incoming mail wouldn't be stuck in a queue, it would be bounced.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Sunday, March 6, 2016 5:25 AM
    Moderator
  • Its new setup exchange server 2013 in your environement. 

    Internal and External Mails stuck in Outbox.

    Can you pls tell me how many CAS/MBX you have in your organization.

    Can You can Test-ServiceHealth all services are running.


    Sunday, March 6, 2016 6:50 AM
  • Ed .. Incoming mail is getting stuck on the Edge Server .. we are having no problems sending any emails.
    Sunday, March 6, 2016 9:48 AM
  • no emails are getting stuck in Outbox .. the emails are getting stuck on the edge server. We had upgraded from exchange 2007 to exchange 2013.

    Test-ServiceHealth comes back with RequiredServicesRunning : True

    • Edited by shaikhNRB Sunday, March 6, 2016 9:53 AM
    Sunday, March 6, 2016 9:49 AM
  • So don't you think that would have been useful for us to know?  Shouldn't you have stated that in your original post?

    Have you tried removing and recreating the edge subscription?  Have you made any changes to your receive connectors that might break the edge connector?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Sunday, March 6, 2016 4:19 PM
    Moderator
  • Ed yes .. i should have put that info in the first post itself.

    I have not made any changes to the connectors. I was also hoping of resolving this without removing and recreating the edge subscription.

    Any incoming messages stuck with 451 4.4.0 error clear up after the mailbox server is restarted.

    Test-EdgeSynchronization comes back with the following


    SyncStatus                  : Normal
    UtcNow                      : 3/6/2016 8:15:31 PM
    Name                        : EDGE
    LeaseHolder                 : Exchange
    LeaseType                   : Option
    FailureDetail               :
    LeaseExpiryUtc              : 3/6/2016 8:45:00 PM
    LastSynchronizedUtc         : 3/6/2016 8:15:00 PM
    TransportServerStatus       : Skipped
    TransportConfigStatus       : Skipped
    AcceptedDomainStatus        : Skipped
    RemoteDomainStatus          : Skipped
    SendConnectorStatus         : Skipped
    MessageClassificationStatus : Skipped
    RecipientStatus             : Skipped
    CredentialRecords           : Number of credentials 3
    CookieRecords               : Number of cookies 2


    • Edited by shaikhNRB Sunday, March 6, 2016 11:26 PM
    Sunday, March 6, 2016 8:19 PM
  • This issue has been resolved .. the problem was with a Layer 7 firewall rule for P2P traffic.. I had it blocked as soon as i removed the rule the issue went away and has been that way for the last 24 hours.

    I hope this helps someone looking for answers.

    • Marked as answer by shaikhNRB Tuesday, March 15, 2016 4:55 AM
    Tuesday, March 15, 2016 4:52 AM