# SMTPAuthenticationError From Discourse-Doctor On New Install

**URL:** <https://meta.discourse.org/t/smtpauthenticationerror-from-discourse-doctor-on-new-install/232030>\
**Category:** Self-hosting\
**Created:** [July 5, 2022, 10:47pm UTC](https://meta.discourse.org/t/smtpauthenticationerror-from-discourse-doctor-on-new-install/232030 "2022-07-05T22:47:10Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![linux4me](https://avatars.discourse-cdn.com/v4/letter/l/48db29/32.png) [@linux4me](https://meta.discourse.org/u/linux4me)\
**Post date:** [July 6, 2022, 4:11pm UTC](https://meta.discourse.org/t/smtpauthenticationerror-from-discourse-doctor-on-new-install/232030/4 "2022-07-06T16:11:45Z")

</div>

This is what I get for being in a hurry.

I reset the `DISCOURSE_SMTP_USER_NAME` and `DISCOURSE_SMTP_PASSWORD` to the original account that gave me the SMTP authentication error, and after destroying the app, when I ran `./launcher start app` I got the following error:

> found unknown escape character while parsing a quoted scalar at line 67 column 28 -e LANG=en\_US.UTF-8  
> YAML syntax error. Please check your containers/\*.yml config files.

Sure enough, there was an `\` in the password I didn’t notice yesterday.

To confirm, I used the new account’s email address, changed the account’s password to the failing account’s password without the `\`, saved it in the app.yml, and re-start the app without the error message recurring. The email test with discourse-doctor worked. Then, I created a new password with a slew of special characters but not the `#` or the `\` and repeated the test. It worked too.

In summary, it looks like special characters are okay in the app.yml `DISCOURSE_SMTP_PASSWORD` field, with the exception of the number sign `#`, the backslash `\`, and probably the double quote `"`?

---

_[View the full topic](https://meta.discourse.org/t/smtpauthenticationerror-from-discourse-doctor-on-new-install/232030)._
