Mail stuck in Queued mail for delivery 250 2.6.0 for receiving e-mail Exchange 2013


  • Hi all,

    We have a big problem. Some e-mail's from external company's are getting stuck in the exchange server and won't be delivered to the client mailbox. Below the tracking logfile:

    RunspaceId              : 534e619f-4a2f-4921-904b-e7edf15e5473

    Timestamp               : 18-12-2015 10:20:30

    ClientIp                :  client ip

    ClientHostname          : Name mailserver

    ServerIp                : internal ip exchange server

    ServerHostname          :

    SourceContext           : Sender Id Agent

    ConnectorId             : internalhostname\Default hostname

    Source                  : SMTP

    EventId                 : FAIL

    InternalMessageId       : 55834574848

    MessageId               : <20151218092207.34C3C3A05B@*****.nl>

    Recipients              : {}

    RecipientStatus         : {[{LRT=};{LED=250 2.6.0 <20151218092207.60C3B4A05B@*****.nl> Queued mail for delivery};{FQ


    TotalBytes              : 0

    RecipientCount          : 1

    RelatedRecipientAddress :

    Reference               :

    MessageSubject          : subject

    Sender                  : sender@***.nl

    ReturnPath              : sender@***.nl

    Directionality          : Incoming

    TenantId                :

    OriginalClientIp        :

    MessageInfo             :

    MessageLatency          :

    MessageLatencyType      : None

    EventData               : {[DeliveryPriority, Normal]}

    I've tried to disable the contentfilterconfig but with no succes. Does someone can help me with the problem? We run Exchange 2013.

    Thank you

    Friday, December 18, 2015 9:33 AM

All replies

  • Hi 

    Lets try to reproduce the scenario with the below for better troubleshoot 

    1) Enable protocol logging on your connectors

    2) Enable delivery receipt from the affected external domain and try dropping an email to your user and lets collect the NDR message which will give us better information.

    3) Run Get-TransportAgent and see what are the agents that you have 

    Remember to 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 Check out my latest blog posts on Thanks Sathish (MVP)

    Sunday, January 3, 2016 8:50 AM