Bypass SBRS for Specific Hosts and Continue to Scan for SPAM

Available Languages

Download Options

  • PDF     (4.5 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (82.0 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (67.0 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:November 19, 2020
Document ID:118566

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes how to bypass SBRS for specific hosts and continue to scan for SPAM.

    Symptoms

    • Sender using a public MTA is being rejected due to SBRS reputation score
    • http://senderbase.org shows a SBRS score of "poor" for the sending IP address

    A GREYLIST is useful to bypass SBRS filtering for a specific host, in the case the host name or sending MTA may encompass other senders other than your specific trusted user.  When using this GREYLIST, the mail is still scanned for SPAM which differs from using the ALLOWLIST which bypasses SPAM scanning.

    Procedure

    To setup a GREYLIST in the GUI:

    1. Navigate to GUI >  Mail Policies -> HAT Overview -> Add Sender Group.
    2. Name the group GREYLIST and select an order of "1".
    3. Choose the "ACCEPTED" mail flow policy.
    4. Leave all other settings at their defaults.
    5. Click Submit and Add Senders.
    6. Enter the IP address or hostname of the sender.
    7. Submit this page.
    8. If needed, click Add Sender and keep adding any additional IP addresses.
    9. Commit the changes.
    TAC Authored

    Contributed by Cisco Engineers

    • Ben Robson
      Cisco TAC Engineer
    • Stephan Bayer
      Cisco TAC Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products