OOF external not delivered

 Issue:

Although out of office is set to internal and external it is not sent to external emails.

Reasons:

Smart host issue, that blocks the OOF message.

Solution 

Created new send connector with the mx record:
>New-SendConnector -Name "to Internet" -Usage "Internet" -SourceTransportServers "EX01-2016" -AddressSpaces ("SMTP:*;1") -IsScopedConnector $False -UseExternalDNSServersEnabled $false 

Then through ECP > Mail Flow > Send Connectors 
Deactivated the smart host send connector and activated the new MX record connector.

Made sure mail flow works and tested OOF, it worked.

Other information: 

- Checked the setting for OOF by 
             Get-RemoteDomain | fl DomainName,AllowedOOFType,AutoReplyEnabled,AutoForwardEnabled
      Get-MailboxAutoReplyConfiguration -Identity "mailbox" | fl
      Get-CASMailbox -Identity <User> | fl EmailAddresses, Ews*
      Get-OrganizationConfig | fl Ews*
>> All configured correct 
- Checked EWS virtual directories >> configured correct 
- Found nothing in queue viewer nothing in get message tracking log 
- Made sure External emails sent and received correctly. 


Comments

Post a Comment

Popular posts from this blog

Exchange setup error: the attribute () points to an invalid DN or a deleted object

 Issue: we closed the last exchange server on Prem, and run a script to delete the AD remnant, when we try to download Exchange Mangement tools we get the following error: The well-known object entry B:32:A1C2016C84D003458132789127B84:CN=Exchange Servers\0ADEL:b2360aad-5e45-40ae-a52a-22397689104a,CN=Deleted Objects,DC=contoso,DC=lab on the otherWellKnownObjects attribute in the container object CN=Configuration,DC=contoso,DC=lab  points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task. Cause: After deletion of ADSI remnants of exchange server, some attribute transferred to deleted object container but is still added to  otherWellKnownObjects  attribute. Solution: 1 . Log on a Domain Controller with Domain Admin permissions 2 . Run ldp.exe -- the LDAP GUI pops up 3 . Click on the Connection menu item and choose the "Connect" item . Leave everything as it is. DO NOT ENTER THE SERVER. Click OK The right side panel populates with dom...
Read more

After March24 SU Search issue in Outlook (cached mode)

  Issue: After installing the Security Update, some of the customers have issue with Search in Outlook (cached mode). Error message: "We're having trouble fetching results from the server..." when performing Outlook search.  Reason:  Issue with the SU. Solution : There is no direct solution but there is a workaround: 1) Use OWA or Outlook online mode if possible. 2) Disable server assisted search by creating following registry key: Path: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Search • Value name: DisableServerAssistedSearch • Value type: REG_DWORD • Value: 1
Read more

Outlook on prem prompts for O365 Password

  Issue: In an Exchange on prem environment Outlook prompts for O365 Password trying to connect to exchange online or Office365. and is not connecting after that. Cause: Moder authentication was enabled Solution: First, we thought of postponing the O365 request, by adding registry Dword (ExcludeExplicitO365Endpoint) this will tell Outlook to postpone the O365 Autodiscover request to the last. 1- Open Registry Editor 2- Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Office\<x.0>\Outlook\AutoDiscover 3- 3- 3- Create new Dword : ExcludeExplicitO365Endpoint  value 1  but this didn't solve the issue  so we decided to disable Modern authentication 1- Open Registry Editor 2- Navigate to: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\<x.0>\Common\Identity   3- Create Dword: EnableADAL value 0 DisableAADWAM  value 1 DisableADALatopWAMOverride  value 1 then the Prompt stopped and outlook connected to On-prem Autodiscover 
Read more