locked
250 2.1.5 RESOLVER.OOF.IntToExt; handled internal OOF addressed to external recipient RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    can someone explain to me why this is being dropped?

    STATUS
    Office 365 used one of your organization's connectors to send the message to an external address. Here are the details:

    Connector name: Outbound to <obfuscated>
    External address: recipient@domain.com
    Destination IP: 1.1.1.1
    Destination smart host: hybridmail.domain.com     
    MORE INFORMATION
    You can view your organization's connector settings on the connectors page.


    MESSAGE EVENTS
    DATE (UTC) EVENT DETAIL

    07/06/2018 14:56:09 Receive Message received by: EXCHONLINESERVER

    07/06/2018 14:56:09 Receive Message received by: EXCHONLINESERVER using TLS1.2 with AES256

    07/06/2018 14:56:10 Send external Message sent to hybridmail.domain.com at 1.1.1.1 using TLS1.2 with AES256

    07/06/2018 14:56:10 Spam Diagnostics



    ADDITIONAL PROPERTIES
    Message ID: <MID.PROD.OUTLOOK.COM>
    Message size: 13 KB
    From IP: 1.1.1.1
    To IP:

    1.1.1.1

    Thursday, June 7, 2018 3:17 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    the above message track info is immediately followed with this

    Automatic reply: tewst
    Sender: sender@domain.com
    Recipient: recipient@domain.com
    Received Not processed Not delivered
    STATUS
    Unfortunately, we aren't able to provide an analysis for this message at this time. 
    MORE INFORMATION
    You can review the Message Events table below for details about the status of this message.
    MESSAGE EVENTS
    DATE (UTC) EVENT DETAIL

    07/06/2018 14:56:09 Receive Message received by: EXCHONLINE

    07/06/2018 14:56:09 Receive Message received by: LEXCHONLINE using TLS1.2 with AES256

    07/06/2018 14:56:09 Drop Reason: [{LED=250 2.1.5 RESOLVER.OOF.IntToExt; handled internal OOF addressed to external recipient};{MSG=};{FQDN=};{IP=};{LRT=}]

    07/06/2018 14:56:09 Drop Reason: [{LED=250 2.1.5 RESOLVER.OOF.IntToExt; handled internal OOF addressed to external recipient};{MSG=};{FQDN=};{IP=};{LRT=}]

    07/06/2018 14:56:09 Spam Diagnostics

    ADDITIONAL PROPERTIES
    Message ID: <MID@PROD.OUTLOOK.COM>
    Message size: 9 KB
    From IP: 1.1.1.1
    To IP:

    Thursday, June 7, 2018 3:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Could you please tell us more details about the issue symptom? 

    From the error message, it should be an OOF issue. And we could check if there are some corrupted inbox rules which cause the OOF message double submission. 

    Similar link for reference: Inbox Rule error.

    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.

    • Edited by Manu Meng Tuesday, June 12, 2018 9:28 AM
    Tuesday, June 12, 2018 9:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    hi

    this issue occurs for everyone not just one user so I don't think its a corrupt inbox rule

    I have set the remote domain to allow autoforward and autoreply and the ooftype of externallegacy

    we are in a co-existence period at the moment

    our exchange is hybrid 365 and these messages occur whenever an OOF is set. sometimes they are received others not. from the message trace it looks like it is the exchange resolver dropping these messages. can this be configured to ignore the behaviour

    Tuesday, June 12, 2018 10:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    hi

    this issue occurs for everyone not just one user so I don't think its a corrupt inbox rule

    I have set the remote domain to allow autoforward and autoreply and the ooftype of externallegacy

    we are in a co-existence period at the moment

    our exchange is hybrid 365 and these messages occur whenever an OOF is set. sometimes they are received others not. from the message trace it looks like it is the exchange resolver dropping these messages. can this be configured to ignore the behaviour

    Could you post the message tracing log here?

    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, June 19, 2018 8:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm having this same issue. Any ideas here? I've checked connectors and transport rules but that doesn't appear to be the issue.
    Tuesday, July 17, 2018 3:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm having the same problem

    [{LED=250 2.1.5 RESOLVER.OOF.IntToExt; handled internal OOF addressed to external
                              recipient};{MSG=};{FQDN=};{IP=};{LRT=}]

    It's occurring in O365 and also I can replicate this issue on our on-prem Exchange 2016 server which is in hybrid mode.  I've tried changing the remotedomain policies

    What do you get if you run this

    Get-RemoteDomain | Format-List -Property id, runspaceid, domainname, allowedooftype, autoreplyenabled

    I've tried the AllowedOOFType on multiple different settings for each remote domain but getting nowhere...

    In the message tracking log I'm also getting 

    SourceContext           : BlockInternalOofToExternalUser

    and googling this reveals virtually nothing... about two results.  I'm really struggling on this one :-s

    Thursday, July 19, 2018 9:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    We have exactly same issue.

    However OOF messages are properly delivered to our Exchange OnPremise but not to senders outside of our organization. We also have hybrid.

    Have you managed to resolve this issue? Could you please tell us how?

    Best regards,

    AD

    Thursday, August 29, 2019 9:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Same issue here. Any resolution or additional documentation for this?
    Thursday, October 3, 2019 6:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi! We are seeing the same issue right now. Did you ever get a resolution on this?
    Tuesday, May 19, 2020 5:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As per my observation, the reason of dropping the mail is the hybrid mail connector is not supporting TLS 1.2 in this case. The direct evidence is checking the message tracking Detailed event: "Receive" which shows that the message has been captured with TLS 1.2 version:

    "Message received by: <Servername> using TLS1.2 with AES256".

    The point where the message getting Dropped is in the event: "Send External" where it is getting picked as TLS 1.2 is not getting detected to pick up the mail.

    Verify by sending mails from Office 365 to Office 365 mailboxes and the OOF will work over there, but it will not work On-prem to O365 and vice versa due to connector TLS 1.2 version support problem.

    Let me know the outcome.

    Thanks,

    Abhishek Mukherjee

    Monday, July 13, 2020 7:09 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    As per my observation, the reason of dropping the mail is the hybrid mail connector is not supporting TLS 1.2 in this case. The direct evidence is checking the message tracking Detailed event: "Receive" which shows that the message has been captured with TLS 1.2 version:

    "Message received by: <Servername> using TLS1.2 with AES256".

    The point where the message getting Dropped is in the event: "Send External" where it is getting picked as TLS 1.2 is not getting detected to pick up the mail.

    Verify by sending mails from Office 365 to Office 365 mailboxes and the OOF will work over there, but it will not work On-prem to O365 and vice versa due to connector TLS 1.2 version support problem.

    Let me know the outcome.

    Thanks,

    Abhishek Mukherjee

    Monday, July 13, 2020 7:10 AM