Smtp Port
Luca Iknokinok
An SMTP port is a communication endpoint that handles information transfers from one server to another. While SMTP (Simple Mail Transfer Protocol) guarantees most emails are being sent on the web, a port makes sure the right email data is going to the right place.
Port 587 is the default port for SMTP submission on the modern web. While you can use other ports for submission (more on those next), you should always start with port 587 as the default and only use a different port if circumstances dictate (like your host blocking port 587 for some reason).
If port 587 is blocked for some reason, port 2525 is a common alternative. Again, this is not an officially recognized SMTP port, but it is commonly used and supported by most providers.
Finally, while port 25 is commonly used for SMTP relay, you should not use it when setting up an email client or WordPress website because most ISPs and cloud hosting providers block port 25.
Some ports transmit encrypted messages, while other ports remain open for all types of traffic. The port you use may be determined by the security standards of your organization, or by the sensitive contents of the messages you send.
Choosing the right SMTP port also helps ensure you have a strong deliverability. SMTP is the most used protocol by mail servers to communicate with one another, but that doesn't mean they're all interchangeable. Some ISPs may block certain ports, like port 25 to defend against spam, and default to another port, like port 587 that supports encryption.
The first port, port 25, was implemented as the primary message transmission channel to help mitigate against attacks like man-in-the-middle. It came out of a 1982 request from the University of Southernn California to the Internet Engineering Task Force (IETF) who are the overlords of all protocols that control movement across the internet.
In most cases, modern SMTP email clients (Microsoft Outlook, Mail, Thunderbird, etc.) shouldn't use this port. It is traditionally blocked by residential ISPs and Cloud Hosting Providers, to curb the amount of spam that is relayed from compromised computers or servers. Unless you're specifically managing a mail server, you should have no traffic traversing this port on your computer or server.
In December of 1998, after port 25 started to get spammy, R. Gellens and J. Klensin submitted RFC 2476 in support of adding a new specification for internet email communications. The RFC proposed a split of the traditional message submission and message relay concept.
Port 587 is the default mail submission port. When an email client or outgoing server is submitting an email to be routed by a proper mail server, it should always use SMTP port 587 as the default port.
Because port 465 was once recognized by IANA as valid, there may be legacy systems that are only capable of using this connection method. Typically, you will use this port only if your application demands it. A quick Google search, and you'll find many consumer Inbox Service Providers' (ISPs) articles that suggest port 465 as the recommended setup. However, we do not recommend it, as it is not RFC compliant.Interestingly, port 465 was never published as an official SMTP transmission or submission channel by the IETF. Instead, the Internet Assigned Numbers Authority (IANA), who maintains much of the core internet infrastructure, registered port 465 for SMTPS. The purpose was to establish a port for SMTP to operate using Secure Sockets Layer (SSL). SSL is commonly used for encrypting communications over the internet.
The ports typically used for POP are TCP ports 110 and 995, and for IMAP are TCP ports 143 and 993, for insecure and secure sessions respectively. They were each good at doing different things, like reflecting the state of an email back to the server (whether it was read, flagged, or marked as junk), or for preserving a copy of the message on a local machine for easy offline access. The latest version of POP, POP3, can be used with or without an SMTP.
Use for non-encrypted connections. Still thought of as the standard SMTP port, most residential ISPs and hosting providers block port 25 due to heavy spam traffic.
Use as the default port for unencrypted webpages. Port 80 is used to send and receive web-based communications and HTML data and allows HTML data to remain in plain text, vs. Port 443 where it would be encrypted.
Use as an alternate if port 587 is blocked. Mailgun provides an alternate in port 2525 for situations when standard ports are blocked. Most ESPs support port 2525.
Different ports are reserved for different types of protocols and their associated functions, and port numbers help you identify these standardized ports. Web browsing, for example, uses ports 80 and 443. Port numbers 21 and 20 are used for FTP. And ports 25, 487, and 2525 handle SMTP.
Way back in 1982, the Internet Engineering Task Force (IETF) published what would become a landmark document, named Request for Comments (RFC) 821. In it, the IETF established port 25 as the standard or default channel for transmitting email over the internet.
Back in the 90s, the IANA began exploring a new method of encrypting or securing email over SMTP, which was called SMTPS. The intent was that SMTP email would be sent securely via standard encryption methods of the time, which were implicit Transport Layer Security (implicit TLS) and Secure Sockets Layer (SSL).
However, there was never a Request for Comments, so the IETF never signed on to this approach or officially endorsed this port. Eventually, other methods of sending encrypted mail (like STARTTLS) grew popular, so the IETF ended up making port 587 the standardized encryption protocol. The IANA changed their tune, removing port 465 from their registry, then later reinstating it for certain cases.
Why mention port 465 at all, then? Well, some legacy equipment and applications still use the port as the default for SMTP. Notably, some older Microsoft applications still do not support STARTTLS, which is why 465 hangs around in those programs.
The intent of establishing this port was to split the duties of mail submission from message relay. Mail submission would now happen over the more modern port 587, while mail relay would route through the older and less secure port 25.
A few hosting providers and upstream networks block this port. Google Compute Engine has changed its sending rules a few times, previously blocking port 587 for outgoing emails, and port 25 is always blocked.
Port 2525 has come to be the de facto alternative for modern SMTP use when port 587 is blocked. This is true even though neither the IETF nor IANA have granted it official status. Port 2525 is also considered a secure port, one that generally supports TLS encryption.
In computer networking, a port is a logical address that identifies a specific network service. When a computer program wants to communicate with a network service, it sends a message to the appropriate port on the destination computer.
The default port for SMTP servers is port 25, but many servers use other ports as well, such as 587, 465 or 2525. In the context of SMTP, ports are used to identify the service at the mailer server that is responsible for handling email messages.
When an SMTP server receives a message, it looks at the port number in order to determine how to handle the message. For example, if a message is sent to port 25, the server will know to process it as an incoming email message.
Some email servers may still be using port 465 to support older mail clients that implemented SMTPS before. So, unless you need to maintain legacy email applications across a large enterprise, for example, you should not be using port 465 to send emails with SMTP.
If you're using a GoDaddy account, follow these instructions to reconfigure your GoDaddy account to use POP. If using POP doesn't resolve your issue, or you need to have IMAP enabled (it's disabled by default), contact GoDaddy support.
Mostly posting this for info in case someone ever has this issue too and also in case it can be changed. I kept having an error about port 1025 being already used and finally looked into it. It turns out that the Synology Drive client (which people with a Synology NAS are likely to be using) uses that port, so they conflict.
From what I understand Explicit SSL/TLS is how STARTTLS works, it asks the server on an unsecured connection if TLS is supported and if it is, it continues with an encrypted connection.Implicit TLS however is secure from the begining of the connection to the end, it is never unsecure.
Although this [STARTTLS] mechanism has been deployed, an alternatemechanism where TLS is negotiated immediately at connection start on aseparate port (referred to in this document as "Implicit TLS") hasbeen deployed more successfully. To encourage more widespread use ofTLS and to also encourage greater consistency regarding how TLS isused, this specification now recommends the use of Implicit TLS forPOP, IMAP, SMTP Submission, and all other protocols used between anMUA and an MSP.
There is no real difference in protocol here, but administrators of larger sites likely want different policies for receiving mail from other domains vs receiving mail from own customers that is likely going out to other domains, and that's why two different ports exist: it allows firewall rules to distinguish easily.
Port 465 is an SSL-only variant of port 25, but this is already handled fine with opportunistic encryption negotiated through the STARTTLS response to the EHLO command, and the STARTTLS command, which is faster than trying port 465 first, running into a timeout and then trying port 25.
Server-to-server transfers use opportunistic encryption and likely fall back to unencrypted transmission if that fails -- end-to-end security is provided by encrypting the mail itself, because even with encrypted connections between servers, the mail is processed on each server.
df19127ead