## TL;DR

For "Error sending email: Error: :error:1408F10B:SSL routines:ssl3_get_record:wrong version number": what actually fixes it (verified in the thread): The maintainer fixed a bug with port 587 and simplified the SMTP settings: you no longer need to specify EMAIL_USE_TLS at all. Port 465 always uses TLS; every other port starts plain and upgrades via STARTTLS if the server supports it.

```text
Error sending email: Error: :error:1408F10B:SSL routines:ssl3_get_record:wrong version number
```

## Steps

1. Self-hosted GrowthBook cannot send email: "Error sending email: Error: :error:1408F10B:SSL routines:ssl3_get_record:wrong version number". The config used EMAIL_HOST, EMAIL_PORT 587, with EMAIL_USE_TLS tried both true and false. The error means TLS was attempted against a port expecting a plain connection (or vice versa).

2. What actually fixes it (verified in the thread):

3. The maintainer fixed a bug with port 587 and simplified the SMTP settings: you no longer need to specify EMAIL_USE_TLS at all. Port 465 always uses TLS; every other port starts plain and upgrades via STARTTLS if the server supports it. Pull the latest Docker image and drop the EMAIL_USE_TLS setting, two reporters confirmed email sending worked after the fix.

## When to use

You are seeing this: The situation: Self-hosted GrowthBook cannot send email: "Error sending email: Error: :error:1408F10B:SSL routines:ssl3_get_record:wrong version number". Use this skill when you run into "GrowthBook self-hosted Error sending email SSL routines ssl3_get_record wrong version number".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_tcZP3QOUyF9Rcmq-dV9fNw/versions/skv_lcnNI5qDCYdBtoKOYcSY4A>
- Canonical HTML skill page: <https://vectle.com/skills/skl_tcZP3QOUyF9Rcmq-dV9fNw>
- Current Markdown URL: <https://vectle.com/skills/skl_tcZP3QOUyF9Rcmq-dV9fNw/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://vectle.com/threads/thr_FRHod_xHaPllpevMt_rx2g",
    "https://github.com/growthbook/growthbook/issues/320"
  ]
}
```