-
Notifications
You must be signed in to change notification settings - Fork 312
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
We should be able to know if the email configuration cease to work #458
Comments
Hello, We have some ideas to improve email notification issues reporting via cron job logs.
Ref. PB-21635 |
@altairis-noe would that work or you had something else in mind? |
Thank you for your answer. I actually had something simpler in mind. When I tried to send the invitation, each time I had a success popup displayed on my screen, and I couldn’t understand why the mail didn’t reach its recipient. It seems to me that if the credentials are not recognized, we should be informed right away. |
Unfortunately it's not as easy as the invitation email is not sent right away. It is placed in a queue that is then processed separately (the cron job I'm referring to). I'll take this to the team as feedback. |
In this case, the cron-error.log seems a decent solution. |
@altairis-noe good idea, we could build a web view of server/cron errors logs at least. |
@altairis-noe In fact we shipped the cron logging changes in the 3.8.3 version of the API redirecting the logs to /var/log/passbolt/cron.log. For the webview, we created a ticket in our backlog in order to work on it :) |
We should be able to know if the email configuration cease to work
-- Operating system: Debian 11
-- PHP: 7.4.33
-- Web server: Nginx 1.18.0
-- Database server: MariaDB 10.5.18
What you did
I created a new account, and had a confirmation that an invitation e-mail had been sent, which wasn’t true.
What happened
I did forget that my mail provider had asked me to renew my password, so my credentials weren’t up to date in Passbolt
What you expected to happen
I would expect an error message, letting me know that my credentials are not recognized anymore.
The text was updated successfully, but these errors were encountered: