Troubleshoot and Delist Cloud Gateway IP Addresses from UCEPROTECT Remote Block List

Available Languages

Download Options

  • PDF     (10.6 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (85.9 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (72.3 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:June 23, 2022
Document ID:217934

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 an identified outbound mail issue for Cisco Secure Email Cloud Gateway customers that involved IP addresses listed by UCEPROTECT, a Remote Block List provider.

Problem

On June 16, 2022, Cisco Secure Email Cloud Gateway customers reported an increase in outbound messages held in delivery queues, along with rejected or bounced messages. After gathering information and troubleshooting, Cisco identified IP addresses within a Cisco-assigned autonomous system number (ASN) that UCEPROTECT had listed. UCEPROTECT provides Remote Block List (RBL) services.

Solution

Partners, email administrators, and customers sometimes use UCEPROTECT information as a source for their blocklisting. In these cases, individual recipients that rely on a UCEPROTECT-based blocklist can reject messages. However, a UCEPROTECT listing has not been observed to cause broad business impact or general email flow issues.

In order to delist from an RBL, UCEPROTECT requires a payment to the organization, unlike other reputable RBL services. Cisco does not recommend that you pay in order to delist, and Cisco does not provide payment if such a listing occurs in the future. Cisco takes this position because UCEPROTECT uses very strict listing policies.

Cisco recommends that its customers do not use the UCEPROTECT blocklist, and advises them to ask their email recipients and partners to do the same.

Note: Cisco does not support the delist payment requirement to UCEPROTECT, nor does it support the delist practices and policies of UCEPROTECT.

For all support-related concerns, contact the Cisco TAC or open a support case online.

Note: Cisco TAC automatically closes open support cases related to the UCEPROTECT RBLs. However, TAC does provide support for other RBL listings. For further assistance, engage your Cisco Customer Experience (CX) team.

Related Information

Cisco Secure Email Gateway Documentation

Secure Email Cloud Gateway Documentation

Cisco Secure Email and Web Manager Documentation

Cisco Secure Product Documentation

Cisco Secure portfolio naming architecture

Other

Cisco Technical Support & Downloads

Revision History

Revision Publish Date Comments
1.0
23-Jun-2022
Initial Release

Contributed by

  • Evangelos Triantis
    Cisco TAC Engineer

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products