401 unauthorized returned by api when trying to verify account through email

[zskullz]

What happened?

I configured the smtp settings on my instance running in docker. I created an account but when I get the verification email, and click on it or copy and paste it, the page shows a message "Failed to verify". When inspecting the network calls in dev tools, the request to the api is returning a 401 and the stoat-api log also shows that it is returning a 401.

Addtionally the url in the email appears to be not formatted correctly, it seems like half of the verification code is being left out of the url and added to the next line:

[Dadadah]

Please try adding the broken bottom half to the top working link and removing the =, so your final slug will be fRz_IYg2AJWUGZc9eY-uoPkYujINKixv. This is a known issue due to the email templates in the backend repo.

[carter-reynolds]

Can confirm this issue exists in email clients that render email bodies exactly as they appear in the headers. Yahoo and Gmail seem to not have this problem since the rendered email removes the = and new line, but if you look at the raw message, the = and new line are still there.