What's the scope of wildcards for whitelists/blacklists?

Kent Brockman

Well-Known Member
PartnerNOC
Jan 20, 2008
1,272
63
178
Buenos Aires, Argentina
cPanel Access Level
Root Administrator
As per the docs at Spam Filters - Version 72 Documentation - cPanel Documentation, you specify what wildcards can be used. That's ok.

But will it work to whitelist something like *@paypal.*?
Cause I need to whitelist, i.e., use cases like *@paypal.com, *@paypal.com.ar and *@paypal.es. Should it work or I need to add it one by one?

Thanks in advance.
 

cPanelLauren

Product Owner
Staff member
Nov 14, 2017
13,296
1,271
313
Houston
Hi @Kent Brockman


*@paypal is usable to whitelist this is noted in the documentation you linked as well:

Note:

When you add addresses to the whitelist, use * as a wildcard to represent multiple characters and ? to represent a single-character wildcard. The following examples demonstrate how to properly use wildcards in the whitelist:

 

Kent Brockman

Well-Known Member
PartnerNOC
Jan 20, 2008
1,272
63
178
Buenos Aires, Argentina
cPanel Access Level
Root Administrator
Hello Lauren. It's not completely or explicitly defined. I'm talking about putting the asterisk both at the beginning and at the end of the string, like in *@paypal.* , while the documentation talks about putting it only at the beginning.
So, should it work? Have you tested it?
 

cPanelLauren

Product Owner
Staff member
Nov 14, 2017
13,296
1,271
313
Houston
Hi @Kent Brockman

It appears to work, I tested this from a domain that for all purposes should have been flagged as spam and got the following:

Code:
2019-04-16 13:41:26 1hGT1K-000940-4R H=mtestserverhostname (centos6.11-78-0-11.tld) [IPREMOVED]:34967 Warning: "SpamAssassin as MYUSER detected message as NOT spam (-90.3)"
The same message sent without the whitelist rule added comes up as definite spam:

Code:
2019-04-16 13:44:37 1hGT4O-00098w-Se H=mytestserverhostname (centos6.11-78-0-11.tld) [IPREMOVED]:55602 Warning: "SpamAssassin as myuser detected message as spam (10.5)"