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

Kent Brockman

• April 15, 2019 09:01

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

  • April 16, 2019 16:26

  Hi @Kent Brockman *@paypal is usable to whitelist this is noted in the documentation you linked as well: [QUOTE] 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:

  • user@example.com " Whitelists a single email address.
  • *@example.com " Whitelists all of the addresses at example.com.
  • ?ser@example.com " Whitelists a single character in an address at example.com (for example, user@example.com, but not Auser@example.com).

  
  

  0
• 

  Kent Brockman

  • April 16, 2019 16:54

  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?

  0
• 

  cPanelLauren

  • April 16, 2019 17:16

  Hi @Kent Brockman It's not explicitly listed as something that will be recognized but I don't see any indication that it wouldn't work. I have not tested it though.

  0
• 

  Kent Brockman

  • April 16, 2019 17:33

  Maybe nobody thought of such an use case before :-) Can you test it please or reach any of the dev people to confirm for yes or not?

  0
• 

  cPanelLauren

  • April 16, 2019 18:46

  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: 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: 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)"
  

  0
• 

  Kent Brockman

  • April 16, 2019 19:07

  Awesome, thanks a lot for the testing!! Hope you can consider adding the example to the docs for better clarification. Thanks!

  0

Please sign in to leave a comment.