Totally agree with the last comment! The minimum is to have an answer, yes, no, maybe, when, next release?....! We are facing the same issue, banned anytime from many mail providers. My company is losing money during a "blacklisted" period. Please, answer and help us !
The option seems to be there in mail configuration but not cover cases of SMTP banner mismatch
Again, please, Help !

I find it totally unacceptable that a company THAT IS GETTING LICENCE REVENUE FROM ITS CLIENTS doesn't even take the time to acknowledge said clients when they are mentioning that their own clients are experiencing higher and higher number of issues because of Plesk issues - namely the PTR not matching the SMTP Banner when using a server for multiple clients!!!
Just shows the kind of care they have for their clients... I have read first about this issue being mentioned back in 2015 - https://talk.plesk.com/threads/plesk-12-smtp-banner-mismatch-critical-to-fix.331370/- we are now in September 2017 and Hotmail and Gmail are systematically blocking emails cos' of that mistmatch! No issue about IP rep, DMARC & Domain Key and SPF perfectly set! JUST THAT @@@ PTR / BANNER ISSUE!!!
PLEASE FIX - else next time I change server I'll switch for a company that DO CARE!

Has this been fixed now, or not???

Dito - impacting my clients on my server! each has a different IP address! ALL should be able to have their own SMTP banner - outlook.com is blocking emails beacuse of this!!! PLEASE FIX!

Please fix, having problems with outlook.com because of this.

Please fix, this should be obligatory on a multi ip system.

its a big trouble for multiple domain setups - please correct it.

It is urgent, please Plesk move on with this request.

server name: example.com
hostname: host.example.com
RDNS: host.example.com
HELO record: example.com

Now I see that plesk implemented "Send from domain IP addresses and use domain names in SMTP greeting" under outgoing mail mode in the server mail setting.

But I need the smtp greeting to be sent from hostname.example.com, not from the domain name.

Big issues myself now Plesk 12.5 and still not fixed? My postfix crapped on last update and had to switch back to qmail.

@PleskStaff: Is this issue still not solved? Or am I missing something? 135 Votes should be enough to see that this is important...

Has anyone tried this?
https://www.digitaldaemon.com/FreeBSD/qmail/index.html

Problem still exist or is ther e solution?

thx Alexander

Same problem. Fix it pls

I agree with the very first comment on this thread: When an IP has a default domain, that domain should be used in the SMTP banner in place of the hostname. I see no reason why Plesk should not add a corresponding IP-Section to Postfix' master.cf

I would be interested in someone commenting with an example of what he/she wants to acomplish. Now comments are talking about RDNS, which most often cannot be managed by Plesk but needs to be managed by your ISP

Can someone explain in detail what needs to be done?

Somebody wrote a workaround? I'm thinking in programming a cronjob with redes the mast.cf file created by plesk and change HELO name to main server name of the IP is the main IP. This should fix the problem from Plesk. Or someone has another idea?

@Tozz We do not want the domain name, but the host name. The case also in Ideall Reverse DNS is the name and then it will come with multiple IP addresses per mail server to send to recipients who püfen the Reverse DNS / PTR.

To fix the problem with shipping on the domain IP address, we bnötigen in Plesk DNS template the possibility PTR create entries that end not only to <domain>, but give us the opportunity here to use the Reverse DNS. In the second step must take the Helo Domain Name Hello RDNS come (postfix / main.cf). and already it works well with multiple domains per mail server. I will reply to the developers only in German, in English because you have not understood it, or want to understand.

I believe in Odin lack of understanding of the issue. If I have understood everything correctly, it goes firstly to the Reverse DNS mismatch and secondly, the problem goes DNS or the PTR record does not resolve when you use the IP domain of the reverse.

In principle both is very easy to solve by Plesk.
To fix the problem with the Reverse DNS mismatch, it requires only the possibility in DNS Template another A and AAAA create entry which then refers to the reverse DNS entry. What is currently not possible, as more and <domain> is specified for the A or AAAA DNS entry in Plesk template. Here there is no possibility an A or AAAA entry to create the looks for example: mx.rdns.xxx. Since Plesk always <domain> is specified it comes naturally to this reverse DNS mismatch.
Try it for yourself: Put under / var / named / run-root / var the A and AAAA records and IP RDNS on and you will see, there is no DNA mismatch more. It is only available while Plesk nothing fundamental to denDNS template settings changes will not last. Because every time Plesk upgrade to standard DNS etc. entries will be lost.
The rest is just as easy, but here can indeed times a Plesk developers contact me. But I answer only in German. :)