• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Bypass RBL (Whitelist)

R

rvdmeer

Guest
I would like to start with blocking dynamisch IP addressen. The only problem is that we have several business customers who are using our outgoing SMTP server. Is there a way we can somehow bypass the RBL?

(like whitelisting the domain or allowing an IP address?)

Thanks!
 
One possible suggestion - setup a second SMTP running on a different port (submission port maybe), then modify that config file (example: /etc/xinetd.d/smtp_additional) to not run the rblsmtpd module. Then have just those customers reconfigure their email clients to use that port.
 
Thanks for your reply...

We already desided what to do. We will place another server in front of our plesk server running postfix. Repoint all the MX records to that server and leaf the qmail(plesk) server without any rbl security.

When mail is found to be clear by postfix it will relay to our qmail server.

With this setup customers are able to use the outgoing mail server (plesk/qmail) without having problems with RBL.
 
Back
Top