OOF messages gets droppend with 250 2.1.5 RESOLVER.OOF.ExtToInt; handled external OOF addressed to internal recipient}

I belive these settings are 'aligned'. We dont have any on-prem mailboxes so all mail is sent to the cloud. We have a custom remote domain entry for gmail with the same settings and there is still the same issue. I belive that if there was a transprot rule causing the issue the message trace events would say that it is due to a transport rule? Ive seen that before on other cases, but might be different for OOF.

I can remove my self from the rule that delivers outbound mail back down to us and see if that changes anything.

Thanks.

Seems like the transport rule is the problem, yes. It work flaslessly when I remove my self from it. I cannot however trace a rejected OOF message on our Proxmox relay, so it must be the rule.

The rule description:

Apply the rule if the recipient is external/internal > notInOrganization and the sender domain is contosoc.com or contoso.onmicrosoft.com, redirect the mesage to the following connector <connector name>.

This is based on a Microsoft article I belive from a time back.

Hi @Joachim Vadseth ,

Thanks for your response!

Since the transport rule is the problem, you can try to modify the condition of the rule to ensure that it does not affect OOF messages. For example, add an exception condition to explicitly exclude OOF messages. You can use the condition MessageTypeMatches to exclude OOF messages.

The following is an example of a command to create or modify a rule in the Exchange Online Management Shell:

# 
New-TransportRule -Name "Exclude OOF Messages" -Conditions @(
    @{Name="MessageTypeMatches"; Value="AutoReply"}
) -Exceptions @(
    @{Name="MessageTypeMatches"; Value="AutoReply"}
) -Action @(
    @{Name="RedirectMessage"; Value="ConnectorName"}
)

Please feel free to contact me for any updates. And if this helps, don't forget to mark it as an answer.

Best,

Jake Zhang

New rule or modify the current one? Since you type 'new-transportrule'..

The current Conditions are :

Conditions : {Microsoft.Exchange.MessagingPolicies.Rules.Tasks.SentToScopePredicate, Microsoft.Exchange.MessagingPolicies.Rules.Tasks.SenderDomainIsPredicate}

Our rule has this conditions:

Conditions : {Microsoft.Exchange.MessagingPolicies.Rules.Tasks.SentToScopePredicate, Microsoft.Exchange.MessagingPolicies.Rules.Tasks.SenderDomainIsPredicate}

Do we just add your conditions in addition to this or?