Any update on this issue?
I had a similar problem with an install that I did a few days ago. It would not send mails to users, but the test mail was delivered.
I did a
./launcher rebuild app
And it started working
Ive run a rebuild multiple times now
Maybe setup again…?
Does the test email functionality work? (Admin > Emails)
If it doesn’t, does your email password have a # in it? As # is used for comments, so you’d have to put your password in single quotes to get around that (IIRC)
Excellent observation. That implies he is not on the absolute latest version. Are you on “tests-passed”? If not then you will have problems with Sparkpost.
Problems with Sparkpost email on install
@Ryan_French needs to stop the container, back up his
app.yml file (if he added any changes from the default), then–as root–delete the
Also delete the container and all images.
docker rm $(docker ps -a -q) docker rmi $(docker images -q)
That was how I was able to fix my problem. Since this has to do with a new install perpetually in lock-out via this (fixed) Sparkpost bug; he cannot check the admin panel, cannot even login to view anything. One can obliterate the entire install without losing that anything (sans any edits to the
After, he can go through the process anew of making the
/var/discourse folder, re-download the app and bootstrap it, launch the container. That way you know for sure the codebase is latest, with the fixed bug.
↑ ↑ what he said.
Thank you so much for connecting the dots here @purldator I was not seeing it and this helped tremendously.
Just did a completely fresh build and still not working
Followed @purldator instructions.
Hmm too bad, that would have described your symptoms perfectly. Perhaps try switching mail providers just to see what happens?
Sure, that’s the next step
Setup and correctly configured Mailgun and still not working @codinghorror
I think a simple “
rake admin:create” would have fixed that issue, wouldn’t it?
If you can’t log in, just create a new admin account via
cd /var/discourse ./launcher enter app rake admin:create
I would still have this very particular, edge-case bug either way and would have affected all users thereafter, however.
Either direction requires the app codebase to be re-downloaded and the app itself rebuilt.
I am the type to scorch the fields first and then re-cultivate. Gets rid of any doubts to the presence of the original pestilence.
*grin* (Much obliged for dispatchin’ that bug, by the way; I be likin’ the cut of yer helm there.)
So unfortunately new users are not being sent emails for activation…
Still not sure why this is not working with Mailgun…
Sorry, we just don’t know, and I can’t think of anything else to try.
just a thought, did you validate your sending domain?
What do you see here:
Does SparkPost have logs that you can check?