websavers
Regular Pleskian
- Server operating system version
- AlmaLinux 9.8
- Plesk version and microupdate number
- Plesk Obsidian 18.0.78 Update #4
A customer had an issue with greylisting blocking hellosign.com. The customer added *@hellosign.com to their email account's Spam Filter whitelist, thinking that would help (fair).
When I went looking at the greylisting config, I was surprised to find the Spam Filter whitelist entry really is added to the greylisting white list for that user:
The only problem is it doesn't work. I suspect it's because the greylisting whitelist works by server name and not email address. If I'm right about this, it seems like this would be an easy fix. When Plesk is adding the entry to the greylist white list, simply replace the "@" with "." so in the example above, *@hellosign.com would become *.hellosign.com and therefore match hellosign's server subdomains.
When I went looking at the greylisting config, I was surprised to find the Spam Filter whitelist entry really is added to the greylisting white list for that user:
I didn't realize that white list function affected the greylist, so that's kinda neat.# plesk bin grey_listing --info-mailname <email>
Grey listing configuration for <email>
User's black list:
User's white list:
*@hellosign.com
The only problem is it doesn't work. I suspect it's because the greylisting whitelist works by server name and not email address. If I'm right about this, it seems like this would be an easy fix. When Plesk is adding the entry to the greylist white list, simply replace the "@" with "." so in the example above, *@hellosign.com would become *.hellosign.com and therefore match hellosign's server subdomains.