• 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.

Spam Assassin / Microsoft Exchange Complications

D

ddew

Guest
We have recently acquired a dedicated server which uses the Plesk interface. We purchased the SpamAssassin to go with it. The program we use for mail is Mail Enable. All are installed and running fine. My problem is, my company uses a Microsoft Exchange server, in my MX record I have set the mail to be sent to our internal Exchange Sever, but now we don't have spam protection from Spam Assassin, how can I route the Exchange Server address to go through the Spam Assassin first and then be routed to our internal Exchange Server? All your thoughts and suggestions are appreciated.
 
Back
Top