• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Making reverse lookups work

michaellunsford

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 ...
Click to expand...

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?
 
You must log in or register to reply here.

Similar threads

S
tcp-env Still Doing Reverse DNS Lookups with -Rt0
Replies
4
Views
8K
Gustave Stresen-Reuter
G
S
Email Stopped Working after Failed upgrade to 8.1
Replies
1
Views
2K
SpidermonBob
S
Back
Top