# BUG Activation Email didn't work/password reset did

**URL:** https://meta.discourse.org/t/bug-activation-email-didnt-work-password-reset-did/72528
**Category:** Site feedback
**Created:** [Octobre 21, 2017, 11:33 UTC](https://meta.discourse.org/t/bug-activation-email-didnt-work-password-reset-did/72528 "2017-10-21T11:33:21Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![SoreGums](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/soregums/32/120608_2.png) [@SoreGums](https://meta.discourse.org/u/SoreGums)
#### Post date: [Octobre 21, 2017, 11:33 UTC](https://meta.discourse.org/t/bug-activation-email-didnt-work-password-reset-did/72528/1 "2017-10-21T11:33:21Z")

</div>

While singing up for an account here on meta  
[https://meta.discourse.org/](https://meta.discourse.org/)

I used GitHub to login,  
Gave a different email address to the one gotten from GH.  
Waited 5mins for the activation email (smashing refresh in gmail)  
Clicked the button to send another activation email, smashed refresh again for a minute.  
Sent an email from my other account on a different domain to the one used here on meta.  
Instantly arrived.  
Smashed refresh again for another 30seconds.

Came back to here to meta and clicked reset password.  
Didn’t have time to click refresh in gmail.  
set a password and now i can post, hence this post 🙂

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [Octobre 21, 2017, 12:13 UTC](https://meta.discourse.org/t/bug-activation-email-didnt-work-password-reset-did/72528/2 "2017-10-21T12:13:03Z")

</div>

> [@SoreGums](#):
>
> Gave a different email address to the one gotten from GH.

What do you mean by this?

---

<div class="post-metadata">

### Author: ![SoreGums](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/soregums/32/120608_2.png) [@SoreGums](https://meta.discourse.org/u/SoreGums)
#### Post date: [Octobre 21, 2017, 12:46 UTC](https://meta.discourse.org/t/bug-activation-email-didnt-work-password-reset-did/72528/3 "2017-10-21T12:46:44Z")

</div>

looks like this server was just slow - [mx-out-04b.sjc1.discourse.org](http://mx-out-04b.sjc1.discourse.org)

got the emails 11mins after they were sent (looked at headers).  
localhost sent the email immediately, then 04b took 11mins to contact google.

whereas server mx-out-04c took a 1 second to contact google.

> [@jomaxro](#):
>
> What do you mean by this?

GH = name@domain  
I changed it to other\_name@domain

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [Octobre 21, 2017, 1:11 UTC](https://meta.discourse.org/t/bug-activation-email-didnt-work-password-reset-did/72528/4 "2017-10-21T13:11:27Z")

</div>

Looks like something for @supermathie to look at on Monday. Can you PM me the full headers of the delayed email?

---

<div class="post-metadata">

### Author: ![SoreGums](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/soregums/32/120608_2.png) [@SoreGums](https://meta.discourse.org/u/SoreGums)
#### Post date: [Octobre 22, 2017, 1:27 UTC](https://meta.discourse.org/t/bug-activation-email-didnt-work-password-reset-did/72528/7 "2017-10-22T13:27:04Z")

</div>

Have sent you a link now 🙂

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [Octobre 23, 2017, 2:59 UTC](https://meta.discourse.org/t/bug-activation-email-didnt-work-password-reset-did/72528/8 "2017-10-23T14:59:56Z")

</div>

Hi Nicholas,

Thanks for bringing this to our attention. Sometimes our outgoing email will error on the first delivery attempt to the downstream server, then succeed on the second. (You don’t see the failed attempts in the message headers, only the success).

We’ll take measures to reduce the occurrence of this and/or make it retry more aggressively.
