Problem/Motivation

Reading the documentation I bump in to this:
Mail servers listen for new mail on TCP/IP numbered "ports", and while these can be whatever the administrator determines, the standard values are:

  • 25 : Internet-wide email transmission by default in cleartext but can upgrade to TLS when both sides support it;
  • 465 : A version of port 25 for which SSL is enabled from the beginning. Now deprecated in favour of port 587 and the use of "STARTTLS";
  • 587 : "Mail submission" - used for clients talking to a "smarthost server (e.g. the ISP server) for queueing and/or forwarding.
  1. It says 465 is deprecated in favour of port 587 and the use of STARTTLS, when is this going to happen?
  2. And what if switching to TLS is giving me a `504 Gateway Time-out - The server didn't respond in time`?

Comments

zebda created an issue. See original summary.

zebda’s picture

zebda commented
Issue summary: View changes
gennadiy’s picture

gennadiy commented

Just SMTP (Drupal 7 only) works with 587 TLS, but now I'm trying to find the right set of modules/configurations to send HTML emails.

imclean’s picture

imclean commented

Port 465 isn't deprecated, in fact implicit TLS should be used for SMTP submission as it's more secure than connecting in plain text then optionally negotiating encryption.

Port 465 uses TLS, even though SSL is often mentioned in conjunction with that port.

imclean’s picture

imclean commented

To answer point 2 in the issue summary, it usually means that port isn't open on the server you're trying to connect to. Select TLS or no encryption and set the port to 587 to check.

@gennadiy, there are a number of SMTP related modules.

bluegeek9’s picture

bluegeek9 commented
Status: Active » Fixed

This issue appears to be fixed. There has not been an update for two years.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.