Support / KnowledgeBase

 
Search the KnowledgeBase Search

Disabling RBL spam protection

  • Applies to: (dv) 3.5, (dv) 4.0

  • Difficulty: Easy

  • Time needed: 10 minutes

  • Tools needed: Plesk administrator access

 
  • Applies to: (dv) 4.0
    • Difficulty: Easy
    • Time Needed: 10
    • Tools Required: Plesk administrator access
  • Applies to: (dv) 3.5
    • Difficulty: Easy
    • Time Needed: 10
    • Tools Required: Plesk administrator access

Overview

RBL, short for Realtime Blackhole List, is a list of IP addresses whose owners refuse to stop the proliferation of spam. The RBL usually lists server IP addresses from ISPs whose customers are responsible for the spam and from ISPs whose servers are hijacked for spam relay.

If you choose to use RBL's on your server, please limit the number of lists you query. This will impact the performance of your mail server.

Instructions

  1. Log into your Plesk Server Administration Panel, see Figure 1:

    plesk10_defaultscreen
    Figure 1: Server Administration Panel

  2. From the left navigation menu, click on Settings.
  3. Click on Mail Server Settings.
  4. Uncheck the box labelled Switch on spam protection based on DNS blackhole lists, see Figure 2:

    DV4 RBL.jpg
    Figure 2.

  5. Click OK to save.

End of Life Warning

This service has a pending End of Life. Please move to a current service as soon as possible. For more information, please see: (dv) Dedicated-Virtual 4.0: Migration Information.

  1. Log into your Plesk Control Panel.
  2. Choose Server from the left panel.
  3. Click on Mail under the Services section, see Figure 1:

    898_1
    Figure 1.

  4. Uncheck the box, if checked, next to Switch on spam protection based on DNS blackhole lists. You can optionally "blank out" any servers listed, but you might want to keep those for future use, should you wish to re-enable this service. See Figure 2:

    898_2
    Figure 2.

  5. Click OK at the bottom right to save your changes.

User Comments

No visitor comments posted. Post a comment
Fields marked with an asterisk(*) are required. Comment on this article
Fill out the form below if you would like to comment on this article.
 
 
 

(code is not case-sensitive)
 
Submit
 
 

Continue