• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

7.5.4 and SpamAssessin: domain block failed

R

Rosemarie

Guest
I apologize for any wrong phrase due to not being a native speaker.
Besides I tried to find an answer for my question by searching through FAQ and forum, without success. Possibly my question is too simple?

I was told to block spam from a complete domain by putting a * in front of the @ (sample *@mgcc.com.my) when adding the address to the black list.

Today I noticed that it seems not to work that way, again several mails went trough instead of being blocked as spam.

The hotline of Plesk in Germany told me that no leading sign is necessary in front of the @, but in that case the pattern is not accepted. Comment: "Some fields are empty or contain in improper value."

Any advice is appreciated. Thank you in advance!
 
You must log in or register to reply here.
Back
Top