The discussion revolves around resolving a ‘Job exception: wrong authentication type none’ error when configuring Discourse to send emails without SMTP authentication. Dan_G initially faced the issue despite setting DISCOURSE_SMTP_AUTHENTICATION: none, but resolved it by removing the username and password settings from app.yml, as they are unnecessary for unauthenticated SMTP. elijah suggests replacing these values with empty strings "" as an alternative, though Dan_G clarifies that removing the keys entirely is sufficient, as YAML behavior mirrors JSON in this context. anthony-o seeks clarification on the exact steps, referencing a related thread where the solution did not work.
I have the error in the title of this post when Discourse tries to send emails (so I couldn’t complete my initial setup). I do not want discourse to try to authenticate at all against the SMTP service so I set this setting in my app.yml:
DISCOURSE_SMTP_AUTHENTICATION: none
Why is it still trying to authenticate?
I fixed my issue. I removed “required” settings like username and password that make no sense in an unauthenticated context and rebuilt. It now works just fine!
On my config, which also uses unauthenticated email, I “removed” by replacing with a double quoted empty string: ""
I don’t know if that is more or less than needed, since I don’t have a strong sense of YML. But I know that trick works in a lot of computer contexts for “zero length string”.
Removing keys in YAML has the same effect as removing them in JSON. It’s up to the code that reads the data to decide what it wants to do with them. I found someone on the forum that removed the keys so I did likewise.
Could you explain what you did exactly? Because I think I’ve tried your solution without any success like I explain here.