Project

General

Profile

Bug #10325

System/Advanced/Notifications/E-Mail - SMTP Notification E-Mail auth password Unexpected Bahaviour

Added by Mr B 7 months ago. Updated 7 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
Notifications
Target version:
-
Start date:
03/09/2020
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.4.4-p3
Affected Architecture:

Description

Hi,
In System/Advanced/Notifications/E-Mail - SMTP Notification E-Mail auth password, if i wish to CHANGE the password i do the following.

Generate a NEW app password (this is a gsuite domain gmail account) and put it in the Notification E-Mail auth password section & confirm section.

I then select "Test SMTP Settings" and an email is successfully sent so i then go down to the "Save" button at the bottom of the page and click it.

However, if i then click on say the System Turnables tab and then come back to the Notification tab and select "Test SMTP Settings" once more i get an authentication error message due to old password still being in use.

Trying the new password and test again works.

I have found this is because clicking "Test SMTP Settings" refreshes the page to display the result banner and at that point must revert the passwords in the Notification E-Mail auth password section & confirm section to what they were.

There is a message under the "Test SMTP Settings" which states:-

"A test notification will be sent even if the service is marked as disabled. The last SAVED values will be used, not necessarily the values entered here."

But that isn't how it works either; as mentioned the problem is that clicking "Test SMTP Settings" seems to revert the password to the old one despite using the NEW one for the test when the screen refreshes and advises you of the test result.

Then as you are completely unaware and have (probably) had a valid test you click "Save" finally, but it then just saves the old password.

History

#1 Updated by Manuel Piovan 7 months ago

i think it's a duplicate of https://redmine.pfsense.org/issues/9684
and it is already been corrected with https://github.com/pfsense/pfsense/pull/4079
work ok on my 2.5.0 and 2.4.5rc
wait for 2.4.5 to be released

#2 Updated by Mr B 7 months ago

Ok, will wait for 2.4.5

That case sounds similar but im not 100% but if it works on yours as expected at those releases i'll hang off and test again at 2.4.5,

Thanks

#3 Updated by Jim Pingle 7 months ago

  • Status changed from New to Feedback

Also available in: Atom PDF