Local Bad Senders Domains wildcard domains do not match as expected

Products

• Messaging Gateway

Issue/Introduction

When adding wildcard domains to Messaging Gateway (SMG) Local Bad Sender Domains, the wildcard '*' does not match as expected. For example the "example*.com" pattern does not match "example1.com", "example2.com" etc resulting in mail being accepted from domains that should be blocked.

Cause

For the wildcard domain to be properly interpreted by SMG, the pattern must contain both a local and domain part rather than just a domain part.

Resolution

This issue has been addressed in Messaging Gateway version 10.7.5 and newer.

Workaround

To create a wildcard domain in Local Bad Sender Domains, the wildcard entry will need parts both before and after the '@'. For example, to filter example*.com, the pattern *@example*.com is needed to match as expected.