# Problem with email on non-default SMTP port

**URL:** <https://meta.discourse.org/t/problem-with-email-on-non-default-smtp-port/44122>\
**Category:** Self-hosting\
**Created:** [May 12, 2016, 2:35pm UTC](https://meta.discourse.org/t/problem-with-email-on-non-default-smtp-port/44122 "2016-05-12T14:35:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)\
**Post date:** [May 12, 2016, 7:40pm UTC](https://meta.discourse.org/t/problem-with-email-on-non-default-smtp-port/44122/2 "2016-05-12T19:40:57Z")

</div>

I’m ignoring all the DNS stuff because that has nothing to do with connecting to a SMTP server hosted by someone else.

I think setting `DISCOURSE_SMTP_ENABLE_START_TLS` to `false` will solve the problem here.

Generally port `465` is `TLS` (otherwise known as SSL) - it doesn’t require the `START_TLS` as it’s already TLS.

You would set `START_TLS` to `true` if you were using port `26` (yes `26` perhaps `25` as well) with Namecheap’s `privateemail.com` service.

Also I believe Namecheap’s SMTP server is responding poorly here - it should be bailing out early and causing an error rather than holding the connection open and not responding - causing a “timeout”.

You would see a `no peer certificate available` or `Secure Renegotiation IS NOT supported` error, if both the server handled this correctly and there more verbose error logging here.

---

_[View the full topic](https://meta.discourse.org/t/problem-with-email-on-non-default-smtp-port/44122)._