Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
actually, your question is not only reasonable, but as well up-to-date to meet the new service-port assignments, made by IANA for RFC conformity ( last updated 18.11.2016=>http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt ), where port 465 has been assigned to the service "urd" ( tcp ) and the service "igmpv3lite" ( upd ).
... is "YES" ( wise/possible and safe ), when you use SMTP-MSA on your server(s) on port 587.
But ( and here comes the culprit... ), if you do that, you have no possible fail back, in case of communication issues between MUA or/and MTA, which could raise support requests due to ( possible ) communications errors from your customers, who use standard settings at their mail - clients ... unfortunately, no mail - client has the standard POP3s- port - setting "465/995", but use instead the POP3 - port - setting "25/110", which will take a looooooong time, untill this changes.
Ill close it then, thank you. We have been using 587 since we started back in 1999. A lot of connection providers in The Netherlands and Belgium close port 25 to outside and don't allow to send mail via port 25 from another provider. Only there port 25 is allowed. A lot others do the opposite and close port 25, only if you send with an email of there own you can use it.
Using 587 solves the problem of both problems.