• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Best practice (and current) anti-spam practices in Plesk

exceedis

New Pleskian
I have Plesk 12 (haven't upgraded to 12.5 yet) on 2008 R2. I want to know if there are some obvious things to do to reduce spam that I haven't done yet. Currently I have SpamAssassin enabled and use three different DNS blacklists. MailEnable seams to complain if I use four or more. I chose these based on some research online as to popularity and their approach. I haven't done anything else. I'm not looking to achieve Gmail level cleanliness of the inbox, but I'd like to get as close as possible with the free approach. I only host for family and a few small clients as a value-add service to other things I do. What practices do you use?
 
Thanks IgorG. I have read that document. I also employ DKIM and SPF DNS settings for my own domains, but haven't enabled filtering for inbound email. These methods require the cooperation of the other end of the chain. Research hasn't given me the confidence to start denying inbound mail yet. But I'd love to hear the results of people who have.
 
Back
Top