> For the complete documentation index, see [llms.txt](https://learn.sitecove.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.sitecove.com/how-to-guides/web-hosting/email-hosting-and-management/how-to-prevent-spam-with-email-filters.md). # How to Prevent Spam with Email Filters #### Introduction Spam emails can clutter your inbox, pose security risks, and reduce productivity. By setting up email filters, you can automatically detect and block unwanted messages before they reach your inbox. This guide will walk you through configuring spam filters in both cPanel and Plesk to help prevent spam effectively. *** #### Setting Up Spam Filters in cPanel #### Step 1: Access the Spam Filters Tool 1. Log in to **cPanel**. 2. Navigate to the **Email** section and click on **Spam Filters**. #### Step 2: Enable Spam Filtering 1. Locate the **SpamAssassin** section. 2. Click the toggle to enable **Spam Filters**. 3. Once enabled, cPanel will begin filtering spam automatically. #### Step 3: Adjust Spam Threshold Settings 1. Click on **Spam Threshold Score**. 2. Lower scores make the filter stricter (default is 5; setting it to 3 is more aggressive). 3. Save changes to apply the new threshold. #### Step 4: Auto-Delete Spam (Optional) 1. Toggle **Auto-Delete Spam** to enable automatic deletion of spam emails. 2. Be cautious with this setting to avoid false positives. #### Step 5: Create Custom Email Filters 1. Navigate to **Email Filters** in cPanel. 2. Click **Create a New Filter** and set up rules based on sender, subject, or keywords. 3. Define the action (e.g., move to Junk folder or delete). 4. Click **Save** to activate the filter. *** #### Setting Up Spam Filters in Plesk #### Step 1: Access Spam Filter Settings 1. Log in to **Plesk**. 2. Go to **Mail** and select your email account. 3. Click **Spam Filter**. #### Step 2: Enable Spam Filtering 1. Check the box to enable spam filtering for the selected email account. 2. Click **Apply** to save changes. #### Step 3: Adjust Sensitivity Levels 1. Set the spam sensitivity level (lower values mean stricter filtering). 2. Recommended values: 5 for balanced filtering, 3 for stricter filtering. #### Step 4: Configure Actions for Spam Messages 1. Choose to either **move spam to the Spam folder** or **delete it automatically**. 2. Click **Apply** to finalize your changes. #### Step 5: Whitelist and Blacklist Senders 1. Add trusted senders to the **Whitelist** to ensure their emails always arrive. 2. Add known spammers to the **Blacklist** to block their messages. 3. Click **Apply** to save these lists. *** #### Additional Tips to Prevent Spam * Use **strong passwords** to prevent email account hacks. * Never click on suspicious links in spam emails. * Use **CAPTCHAs** on contact forms to reduce spam submissions. * Report spam emails to improve filtering accuracy. *** #### Conclusion Setting up spam filters in cPanel or Plesk is an effective way to reduce unwanted emails and keep your inbox clean. By enabling spam detection, adjusting sensitivity settings, and configuring custom filters, you can significantly decrease the number of spam messages you receive. If you continue to experience spam issues, consider contacting your hosting provider for additional assistance. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://learn.sitecove.com/how-to-guides/web-hosting/email-hosting-and-management/how-to-prevent-spam-with-email-filters.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.