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

Making reverse lookups work

michaellunsford

Regular Pleskian
well, this might not be plesk related -- but I don't know where else to post it.

I used to get the "possible break-in attempt" error when logging into SSH. Apparently the ISP has fixed this (for the moment) -- but it'll probably be back tomorrow.

One thing that's still "broke" is email. Any external email addresses receiving mail from my server will show my IP address "may be forged" in their headers.

Received: from server.example.com
(ds209-253.ipowerweb.com [xxx.xxx.xxx.xxx] (may be forged))
by ...com (Xserve/smtpin20/MantshX 4.0) with ESMTP id ...

how do I make the "may be forged" go away?

Are there any other areas I should be looking to fix regarding this reverse lookup thing?
 
Back
Top