passbolt_api icon indicating copy to clipboard operation
passbolt_api copied to clipboard

We should be able to know if the email configuration cease to work

Open altairis-noe opened this issue 2 years ago • 7 comments

We should be able to know if the email configuration cease to work

  • Passbolt Version: 3.8.3
  • Platform and Target: -- 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.

altairis-noe avatar Jan 04 '23 13:01 altairis-noe

Hello,

We have some ideas to improve email notification issues reporting via cron job logs.

  • Docker: we log stdout and stderr of all cron processes to stdout to users will see email sent X and any error on the terminal which is stored by default on docker logs

  • VM and other installations: we will log errors on /var/log/passbolt/cron-error.log and stdout on /var/log/passbolt/cron.log We will rotate the log files same as with passbolt-error.

Ref. PB-21635

stripthis avatar Jan 04 '23 14:01 stripthis

@altairis-noe would that work or you had something else in mind?

stripthis avatar Jan 04 '23 14:01 stripthis

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.

altairis-noe avatar Jan 04 '23 15:01 altairis-noe

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.

stripthis avatar Jan 04 '23 15:01 stripthis

In this case, the cron-error.log seems a decent solution. Maybe, consider an alert in the passbolt interface when there are errors in that log ?

altairis-noe avatar Jan 05 '23 08:01 altairis-noe

@altairis-noe good idea, we could build a web view of server/cron errors logs at least.

stripthis avatar Jan 05 '23 09:01 stripthis

@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 :)

gmougenel avatar Jan 05 '23 11:01 gmougenel