Facebook
Twitter-
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.
Resolved is it safe to close port 465 ?
- Thread starter Linulex
- Start date
U
UFHH01
Guest
Hi Linulex,
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 ).
The definite answer to your question:
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.
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 ).
The definite answer to your question:
... 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. 
Linulex
Silver Pleskian
Hi UFHH01
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.
POP3 ? The 1990s want there protocol back.
regards
Jan
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.
POP3 ? The 1990s want there protocol back.
regards
Jan
Similar threads
