-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐞 [Bug]: Change mail config validator on taiga #3343
Comments
Use validation used in discourse solution. Remove the condition applying validation to just discourse. |
Work in Progress (WIP):utils created to validate SMTP (email, apiKey, username), faced an error .. investigating.. |
Work Completed:
|
Work Completed:
|
verified on devnet now user names are allowed so user can use api keys or user name normally passwords is allowed more than 50 characters |
after deploying 2 taigas did not recieve any mails on the mail I used in the setup is this related ? |
we mentioned here that taiga part is blocked on threefoldtech/tf-images#293 |
Okay, thanks for clarifying. |
Is there an existing issue for this?
which package/s did you face the problem with?
Dashboard
What happened?
The same issue is happing to the taiga, and also check all of the other application stmp.
Steps To Reproduce
No response
which network/s did you face the problem on?
Dev
version
448a213
Twin ID/s
No response
Node ID/s
No response
Farm ID/s
No response
Contract ID/s
No response
Relevant screenshots/screen records
#2152 (comment)
Relevant log output
.
The text was updated successfully, but these errors were encountered: