Facebook
Twitter-
Please be aware: Kaspersky Anti-Virus has been deprecatedWith the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
-
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
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
