A user reports an issue where whitelisted domains like discuss.newrelic.com are appearing in a spam notification despite being allowed, raising questions about whether this is a bug and if wildcard support exists. codinghorror clarifies that wildcarding isn’t supported, but subdomains of whitelisted domains should be allowed. riking notes that only github.com is actively blocking content, while other domains like coreos.com and deis.io are the actual culprits. lisajill finds the error message confusing because it lists whitelisted domains as blocked, suggesting clearer wording—such as specifying “external” domains—would help. Mittineague agrees, and jesus2099 confirms understanding that newrelic.com and its subdomains are allowed if listed, but seeks clarification on the scope of the rule.
There is no wildcard support here. However, it was my understanding that listing the domain automatically allows all subdomains too.
I am also pretty sure that the site itself is not the source of spam, e.g. you do not need to have discuss.newrelic.com in there. Self links are always allowed…
In this case the other domains are likely the issue, eg coreos.com and deis.io
I find it confusing that it lists domains that are allowed; I did not find the error clear in that it was blocking only due to the other domains. Specifically:
That would work so long as the ones that are whitelisted don’t appear. What threw me here was seeing domains that are in the Whitelist listed as ‘blocked’ in the private message.
In the error I quoted the PM should have listed only ‘coreos.com’ and deis.io’ - not our domains.
What was listed in the message should have been the domains the user tried to post over and over in their posts – it is not listing anything except what the user entered.