Wildcard usage in Manage Spammers for Domains

leighton@mail.com

I have received a large number of messages addressed from contact@xyz.com or contact@xyz.net where xyz is any one of many domain names. Is there a way to block them all with a wildcard definition such as:

contact@*.com or contact@*.net

Sorin G.

Hello,

 

Thanks for the feedback, however this has already been done.

There is a impressive domain ban list as well.

leighton@mail.com

3 hours ago, Sorin G. said:

Thanks for the feedback, however this has already been done.

There is a impressive domain ban list as well.

Built in? If it is, it must not be working.

Sorin G.

Hello,

 

My apologies I misunderstood what you really meant.

The product requires a proper domain to add the spammer to the list, wildcards can be used on the username.

I have forwarded this feature request to our devs.

leighton@mail.com

21 minutes ago, Sorin G. said:

The product requires a proper domain to add the spammer to the list, wildcards can be used on the username.

I have forwarded this feature request to our devs.

 

Now we're on the same page. Thanks.

leighton@mail.com

A related topic is the constraints of the "Internationalization" code in an email address. I'm not sure what the IETF guidelines say, but I noticed that some codes don't work i.e. "sast@sast.local" seems to be an illegal address according to BDIS "Manage Spammers". What constraints are being used in determining the eligibility of an email address?