Sophos Email customers using IP-based mailflow rule connectors must migrate to certificate-based configuration by March 31st. To see if you're affected Click Here.

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

Central Email - Settings for delivery failure notification

Hello,

a customer is migrating from on premise Sophos Email Appliance to Central Email. Some users have Out Of Office autoresponders. When these ones fail to deliver a message, a mail from MAILER-DAEMON@prod.hydra.sophos.com is sent to the user. Is there a setting to edit/filter these emails, if not from Exchange/Outlook?

I found this Sophos Idea, but it is not what I was looking for. The problem is that customer claims that this behavior didn't happen with on premise Sophos email appliance. Am I missing something on Central Email?

Thank you



Added tags
[edited by: Raphael Alganes at 12:10 PM (GMT -7) on 26 May 2023]
Parents
  • Central should not have problems with those OOO mails. The mailer-daemon is the source, if we cannot send this to the destination. You cannot turn this off. 

    Maybe your outlook tries to reply to a address, which does not exists? The old Newsletter issue. 

    __________________________________________________________________________________________________________________

  • Yesterday I connected to the customer's site and checked what he meant.

    The problem is Exchange-related with an annoying chain: OOO replies to the newsletter address, and the delivery fails. Then OOO replies again to mailer-daemon Central address, which rejects the second email. So customer has 2 unwanted emails from Sophos Central.

    I think that in Exchange they can set up some rules to avoid that, it's not Central-related.

    By the way, the idea I linked in the OP is interesting: each customer could have the possibility to customize the domain of the mailer-daemon autoresponse.

  • Its hard to implemented something like that, as there are two different implementation in Central. The SMTP one and the "Email" Implementation. 

    Means, if something is based on a Email, which Central accepted, you can easily implemented what to do with it, based on Customer setups. 

    But if a SMTP transmission based change is involved, its most likely for "all" central email customers - Which makes such implemenations much more complicated to implement in a customer view. 

    __________________________________________________________________________________________________________________

Reply
  • Its hard to implemented something like that, as there are two different implementation in Central. The SMTP one and the "Email" Implementation. 

    Means, if something is based on a Email, which Central accepted, you can easily implemented what to do with it, based on Customer setups. 

    But if a SMTP transmission based change is involved, its most likely for "all" central email customers - Which makes such implemenations much more complicated to implement in a customer view. 

    __________________________________________________________________________________________________________________

Children
No Data