Being a hosting provider isn’t easy. We get that. There are many unforeseeable occurrences that can put a damper on your service — however, spam email shouldn’t be one of them.
Ways to fight spam email with cPanel & WHM:
We’ve highlighted these add-ons that can be used to combat incoming spam, malware, and viruses on your server and, ultimately, offer your customers a better experience.
- ASSP Deluxe for cPanel
- SpamExperts cPanel Add-on
SpamStopsHere is a unique, multilayer filter system that uses four criteria levels to weed out spam and malicious content, while permitting legitimate email, with a nearly 99.5% success rate. The first layer, the IP Blacklist, flags any email sent from known spam servers. The next layer scans the document for URLs associated with spam. The third layer scans it for strange phrases, rather than keywords, linked to malicious content. Finally, the last layer scans the format of the document for tricks often used by spammers to bypass normal email clients. This robust, dynamic process lessens server load and should make your customers pretty happy.
ASSP Deluxe for cPanel
ASSP (Anti-Spam SMTP Proxy) Deluxe for cPanel is a nifty plugin that eradicates spam email and the easy-to-install widget comes loaded with additional features and customizations. You can set up criterion for custom spam boxes, receive daily email reports, and tinker with a whole host of other automatable functions, cutting a fraction of your workload.
ASSP Deluxe for cPanel>>>
SpamExperts cPanel Add-on
This add-on gives cPanel users one-click access to a wide range of anti-spam solutions packaged within the SpamExperts widget. Not only does SpamExperts’ cPanel add-on protect domains from email-based threats, it enables hosting providers to offer custom spam-fighting tools. Using the SpamExperts plugin, you can increase security for your customers and add value to your business.
SpamExperts cPanel Add-on>>>
Note: These are 3rd party plugins that are not managed or owned by cPanel, L.L.C. Issues that may arise when using these products should be directed to the respective plugin developers.
* This post was originally posted on June 9, 2015, and has been updated for accuracy.