-
-
Notifications
You must be signed in to change notification settings - Fork 829
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
Error when replying to a post wile the e-mail configuration is wrong #1808
Labels
Comments
This is very much related to several other tickets, the combination of which should make this obsolete:
|
The same applies to #1769. Do we want to have both on the milestone? |
Seems to me that now that we have queuing for notifications, as well as a test email config button in #2004, this can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Current Behavior
We have a running instance of Flarum where we configured an e-mail address with it's SMTP server and password. Our client changed the password of this e-mail account and suddenly there was an error showing up most of the time when someone tried to reply to a discussion. The error didn't tell anything in particular as the server just responded with status code 500 and "internal server error" as message.
When we figured out that this was related to the change of password, we updated the password in the administration interface and all was working fine again.
Now the thing is that when this error happens, first the Composer component is loading for a wile (the time it takes for the SMTP request to timeout) and then the GUI would behave as if the reply was not taken in account. When you reload the page, you can see that the reply was actually posted and saved to the DB.
Expected Behavior
For the end user, who is posting a reply, this error does not matter and his reply should be posted to the thread like normal.
I have no idea how the problem could be reported to admins, but it definitely should be reported as all outgoing e-mails are not working.
Environment
The text was updated successfully, but these errors were encountered: