# DigitalOcean + Siteground Email via port 465 won’t work (2525 will work)

**URL:** https://meta.discourse.org/t/digitalocean-siteground-email-via-port-465-won-t-work-2525-will-work/125067
**Category:** Self-hosting
**Created:** [6 augustus 2019 om 23:38 UTC](https://meta.discourse.org/t/digitalocean-siteground-email-via-port-465-won-t-work-2525-will-work/125067 "2019-08-06T23:38:38Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![PackElend](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/packelend/32/95294_2.png) [@PackElend](https://meta.discourse.org/u/PackElend)
#### Post date: [6 augustus 2019 om 23:38 UTC](https://meta.discourse.org/t/digitalocean-siteground-email-via-port-465-won-t-work-2525-will-work/125067/1 "2019-08-06T23:38:38Z")

</div>

Hello,  
I started a discourse droplet on digital ocean, what is basically the discourse docker image.  
It worked well until I reached the registration step

> We sent an activation mail to \*\* `admin.discourse@ourdomain.coop`\*\*

but the email never arrived

```plaintext
tail -f /var/discourse/shared/standalone/log/rails/production.log
Sent mail to admin.discourse@ourdomain.coop (61113.9ms)
Job exception: Net::ReadTimeout

```

so I check if I can send an email via telnet, what worked well but only if using `AUTH PLAIN` as described on [Using Telnet with an SMTP Server – That's Geeky](https://www.thatsgeeky.com/2011/01/using-telnet-with-an-smtp-server/)  
then it turned out there is a bug as described in  
[https://stackoverflow.com/questions/42272644/why-do-i-get-done-after-auth-login-command](https://stackoverflow.com/questions/42272644/why-do-i-get-done-after-auth-login-command)

First I changed to port 2525 and I got the email _[Discourse] Confirm your new account_ so I rebuild the app with new password verifying via [https://www.base64encode.net/](https://www.base64encode.net/) but once again `Job exception: Net::ReadTimeout`  
so I changed again to 2525 but no email arrives but

```plaintext
tail -f /var/discourse/shared/standalone/log/rails/production.log
Sent mail to admin.discourse@ourdomain.coop (61113.9ms)

```

without `Job exception: Net::ReadTimeout`

I’M LOST HERE

 ![grafik](https://global.discourse-cdn.com/meta/original/3X/8/6/86c362b7cdd3d06ff788c984d0bdc7f0664ce765.png)

```plaintext
DISCOURSE_SMTP_ADDRESS: itm13.siteground.biz
DISCOURSE_SMTP_PORT: 465
DISCOURSE_SMTP_USER_NAME: admin.discourse@ourdomain.coop
DISCOURSE_SMTP_PASSWORD: MyPassword

```

```plaintext
DISCOURSE_SMTP_ADDRESS: mail.ourdomain.coop 
DISCOURSE_SMTP_PORT: 2525
DISCOURSE_SMTP_USER_NAME: admin.discourse@ourdomain.coop
DISCOURSE_SMTP_PASSWORD: MyPassword

```

no parenthesis, Quotation marketc. used!

---

<div class="post-metadata">

### Author: ![PackElend](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/packelend/32/95294_2.png) [@PackElend](https://meta.discourse.org/u/PackElend)
#### Post date: [7 augustus 2019 om 00:11 UTC](https://meta.discourse.org/t/digitalocean-siteground-email-via-port-465-won-t-work-2525-will-work/125067/2 "2019-08-07T00:11:05Z")

</div>

`swaks --to myemail@ourdomain.coop--from admin.discourse@ourdomain.coop --server itm13.siteground.biz --auth LOGIN --auth-user admin.discourse@ourdomain.coop -tls`

`swaks --to myemail@gmail.com--from admin.discourse@ourdomain.coop --server itm13.siteground.biz --auth LOGIN --auth-user admin.discourse@ourdomain.coop -tls`

works

I have just noticed, that the emails send from (that very only time) comes from a different sender than in app.yml set. It is the old hostname, not the new one I’m using for testing, although I’ve been working with the new one only.