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

appliance email bounce back

We had to replace the Sophos 1100 box Wed. due to issues. If went bad Friday, so we changed the Exchange (2007) connectors to have messages come in straight to Exchange. Changed everything back when replacement unit was put in. 98% of incoming messages go through fine now, but around 2% are coming back to sender with "undeliverable 530 530 5.7.1 client was not authenticated".  Looked on Net and most common opinion was to set default connector on Exchange to accept anonymous hosts. Changed that. BAD idea, lots of spam. Had to change it back. I do not see the messages that are rejected coming across the log files on the Sophos appliance. Could the appliance be blocking these messages and leaving no trace?

:4984


This thread was automatically locked due to age.
  • Sender Genotype service provides the message blocking from known bad senders.  This can be configured at the MTA level or in the policy.  If running in the policy the message is accepted and scanned against Sophos known list of bad senders and discarded when detection is made.  This also records that information in the system maillog which are accessible in the search area of the UI.  The maillogs record all incoming connections.  You may need to refine your search parameters to locate the message(s).  Please note that the appliance only stores 30days of messages on board. To retain more maillog information you must either enable the syslog service or backup service which allows backups of system and maillogs.

    :6605