Can we figure out why this was sent to graymail?

[virtualmike]

I forgot to follow-up, but indeed, *.*example.com appears to work whether the From: email address(es) have a subdomain or not. I'm going to use that format for all future entries.

@Sonic staff: please consider updating the text on the Welcomelist Config Page to reflect this. ...thanks!

[syntaxsid1]

We're glad to hear that worked out for you. Thank you for the suggestion. We'll request this from the department that handles this. Thanks for letting us know. Have a great day!

[joemuller]

I forgot to follow-up, but indeed, *.*example.com appears to work whether the From: email address(es) have a subdomain or not. I'm going to use that format for all future entries.

We're going to look at updating the examples to better show how to handle the situation you found, but a recommendation:

*@*example.com would potentially match something like [email protected] and [email protected], but it would also mach [email protected]. If you just want to match example.com and (anything).example.com emails, you'll need to make 2 rules:

*@example.com (star at example dot com)
*@*.example.com (star at star dot example dot com)

I can't remember the specific example, but I've worked with at least one person who accidentally blocked email from a popular domain while trying to block some different variations of a common word in the domain name (right half). You can always try testing out rules with wildcard (*) characters using the Search function in your local email program or Webmail - it's a good sanity-check to see if any legitimate email you've kept around might get marked as spam.

-- Joe M

[virtualmike]

... but it would also mach [email protected].

Thanks, Joe. That thought actually popped into my head as I was falling asleep Saturday evening, and I rationalized that for my purposes, it's fine. The domains that I'm Welcomelisting have low likelihood that a scammer will prefix with a few characters (except maybe amazon.com ).

I agree that others may have different experiences, particularly if they're both Welcomelisting and Blocklisting varioius domains.

Also, if I interpret the current documentation correctly, it appears that if I Welcomelist *.*example.com and I start getting spam from [email protected], I can Unwelcomelist From *.1example.com and leave the Welcomelist entry intact.