• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Problem with reverse DNS (SMTP Banner)

It's most relevant theme, I think, so I will add my additional info here.

I have Plesk on panel.host.com with one Shared IP (let's say 51.58.33.40 with PTR panel.host.com, this IP used by Plesk and most domains is hosted on this IP)
Also I have few dedicated IPs on this server (let's say 62.21.13.1, 62.21.13.2, 62.21.13.3, 62.21.13.4)
Plesk is configured to send mail from domain IP (as spamhaus wanted The Spamhaus Project - Frequently Asked Questions (FAQ))

Every dedicated IP attached to some client and they points (PTR) to, for example:
62.21.13.1 - > mail.somedomain1.com
62.21.13.2 - > mail.anotherdomain2.com
62.21.13.3 - > onemoredomain3.com
62.21.13.4 - > lastdomain4.com

Plesk is used by somedomain1.com and anotherdomain2.com ONLY for mail service (websites somedomain1.com and anotherdomain2.com located on additional server, so PTR for 62.21.13.1 and 62.21.13.2 can only point to mail.somedomain1.com or mail.anotherdomain2.com, this two hosts is used as MX)

My dedicated IPs were listed by Spamhaus CSS list. Why? Because SMTP Banner (panel.host.com) is not equal to IPs PTR
So I discussed this with Spamhaus support and we decided to try another option - "Send from domain IP addresses and use domain names in SMTP greeting"
Also the said:
1699016706920.png


But after some time my Shared IP were listed by Spamhaus XBL or similar. Why? Because they saw a lot of connection from ONE ip with different HELO
For now I'm trying to use next scenario:
- Plesk is configured to send mail from domain IP (as spamhaus wanted The Spamhaus Project - Frequently Asked Questions (FAQ))
- postfix config is changed to use custom HELO for Dedicated IPs
IMHO, the only thing I need in Plesk if this scenario is correct (but looks like it's the best one to match Spamhaus and similar blacklists requirements) - the option on domain level to override HELO.
p.s. One more thing I want so much too :) is to host multiple sites under one subscription with "no hosting", this is needed to sell mail only service
 
...
So I discussed this with Spamhaus support and we decided to try another option - "Send from domain IP addresses and use domain names in SMTP greeting"
No way this will work. I wonder why they told you that. It will create exactly the problem that you are trying to solve, because now you'll have different domain names in the HELO greeting with the same IP address.

But after some time my Shared IP were listed by Spamhaus XBL or similar. Why? Because they saw a lot of connection from ONE ip with different HELO
Yes, that's exactly the problem.

For now I'm trying to use next scenario:
- Plesk is configured to send mail from domain IP (as spamhaus wanted The Spamhaus Project - Frequently Asked Questions (FAQ))
- postfix config is changed to use custom HELO for Dedicated IPs
IMHO, the only thing I need in Plesk if this scenario is correct (but looks like it's the best one to match Spamhaus and similar blacklists requirements) - the option on domain level to override HELO.
Sounds like a good idea.
 
No way this will work. I wonder why they told you that. It will create exactly the problem that you are trying to solve, because now you'll have different domain names in the HELO greeting with the same IP address.
As I mentioned, they have CSS list (https://www.spamhaus.org/css/) and I was listed because my HELO is not equal with PTR, but in current state you can make HELO the same as PTR only using this "bad" option
 
Back
Top