Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct SMTP port number #318

Merged
merged 1 commit into from
Nov 4, 2014
Merged

Conversation

mikeashley
Copy link
Contributor

Port 587 for smtp does not appear to match the mailserver configuration and leads to incorrect autoconfiguration. Changed to 465 and tested with Icedove.

@neuhaus
Copy link
Member

neuhaus commented Nov 4, 2014

I don't agree with this pull request. Port 587 is correct, it is the submission port, designed for authorized mail clients (RFC 6409)

Wikipedia states at https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol

"Although some servers support port 465 for legacy secure SMTP in violation of the specifications, it is preferable to use standard ports and standard ESMTP commands according to RFC 3207 if a secure session needs to be used between the client and the server."

@mikeashley
Copy link
Contributor Author

When deploying on Debian 7, postfix listens on 465, not 587. Roundcube is configured to submit to 465 as well. Are you suggesting changing the configuration of postfix and roundcube instead? Is this a Debian-only problem?

@lukecyca
Copy link
Contributor

lukecyca commented Nov 4, 2014

This PR makes sovereign consistent with itself (using port 465 throughout), so it's merge-able.

I agree that 587 is more correct and that we should switch to it. @neuhaus, could open an issue to that effect (and submit a pull request if you are inclined).

lukecyca added a commit that referenced this pull request Nov 4, 2014
Correct SMTP port number in mail autoconfig
@lukecyca lukecyca merged commit 05a37b8 into sovereign:master Nov 4, 2014
@mikeashley mikeashley deleted the fixes/autoconfig branch November 7, 2014 01:08
@taoeffect
Copy link

I closed our corresponding issue in Empress because STARTTLS is less secure that SSL/TLS, and apparently it's "required"? for 587 (or that's the purpose of that port).

The "correct" answer in that serverfault link is bunk. He's looking at it from the perspective of server-to-server communication which is crappily secured atm, but for client-to-server communication STARTTLS does nothing.

So, I recommend closing this issue here as well.

@taoeffect
Copy link

Updated comment above to add this link re port 587 and STARTTLS: https://stackoverflow.com/questions/15796530/what-is-the-difference-between-ports-465-and-587

@neuhaus
Copy link
Member

neuhaus commented Nov 15, 2014

  1. the roundcube connection is on the loopback interface so even if it's not encrypted, there's no issue
  2. server-to-server SMTP always uses port 25, that's not what this issue is about
  3. clients should be configured to force TLS on. If STARTTLS gets stripped by an active attacker on port 587, it will get noticed right away.
  4. port 465 is deprecated

@neuhaus
Copy link
Member

neuhaus commented Nov 15, 2014

I'll open a separate issue about this so this issue can be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants