Email failed to send, but page does not indicate a problem

Description

When I lost power over night, TrueNAS attempted to send an email about the UPS going on Battery. It failed as follows:

[EFAULT] Failed to send email: ('invalid_grant: Bad Request', {'error': 'invalid_grant', 'error_description': 'Bad Request'})

Going to the email config page showed what appeared to be a correct setup:


However, only after I clicked the "Logged In To Gmail" button again did I see that Gmail wanted me to (re-)authorize. At a minimum, the button is misleading.

Session ID: 536b2cc0-4112-ddb5-4870-1fd0b2c62501

Problem/Justification

None

Impact

None

Attachments

2

Activity

Show:

Bug Clerk2 days ago

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Caleblast week

I’m not sure. However, I know that the button showing as “Logged In To Gmail” is wrong. I see a couple issues that need to be addressed.

  1. We need to stop showing Logged In To Gmailif we’re not actually able to successfully log in.

  2. We need to understand what invalid_grant means according to Google’s developer docs and act accordingly. If that error message means we need to re-authenticate then we need to let the user know somehow. Whether that’s a warning alert and changing the button to Log In To Gmail i’m not sure.

Vladimir Vinogradenkolast week
Edited

do we want to mark GMail configuration as invalid once we receive invalid_grant error?

Ievgen Stepanovychlast week

The button simply looks at whether client_id is set in oauth in mail.config.

We can discuss whether we want to clean that when we know that credential has expired or provide some other indication to the UI to do something.

Complete

Details

Assignee

Reporter

Labels

Original estimate

Time remaining

0m

Priority

Katalon Platform

Created last week
Updated 2 days ago
Resolved 2 days ago