This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XG18 invisible source/hosts entry in XG17.5.MR10 and XG18 GA

Simple Question,

how do i remove a invisible source/hosts entry in email policies?

 

Or can someone help with a correct FQDN entry for this source?
I want to get the Microsoft Team notification mails, they are greylisted in XG.

*.mail.protection.outlook.com



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi juergenb52,

    Could you please let us know if you want to add exception for *.mail.protection.outlook.com under PROTECT > Email > Policies & Exceptions? 

    If yes, you should be able to add wildcard FQDN host by clicking on Add new item > Create new > FQDN Host. Once you add this FQDN you should be able to bypass checks that are listed in Exception.

    Please correct if this is not what you are trying to accomplish?  

    Thanks,

  • Thanks Patel,

    yes this is exactly what i want.

    I tried this way ..

    I added the FQDN Host and opened email/Exception, but you can´t add the new FQDN Host to Sources/host (still invisible).

    and i tried second way

    I added the FQDN Host unter Exception… Soruces/Host.
    Here i can add the FQDN but after i click save the rule is still empty.

    This happens in MR9, MR10 and XG18 GA

  • Maybe something went wrong in your Setup. 

    There is something broken in the database. 

  • I tried this with MR10 clean install and XG18 GA.

    Same behavior...

  • FormerMember
    0 FormerMember in reply to juergenb52

    Hi juergenb52,

    I was able to replicate this issue on both SFOS 17.5 MR 10 and V18. I have reported this issue to the concern team to investigate it further. 

    I will update this thread as soon as more information becomes available. 

    Thanks,

     

Reply
  • FormerMember
    0 FormerMember in reply to juergenb52

    Hi juergenb52,

    I was able to replicate this issue on both SFOS 17.5 MR 10 and V18. I have reported this issue to the concern team to investigate it further. 

    I will update this thread as soon as more information becomes available. 

    Thanks,

     

Children