I have unMenu Version 1.4 Revision: 223 installed on unRaid 4.5.6

 

I have ssmtp configured for my gmail account and has worked fine for over 12 months.

 

I recently changed my gmail password so needed to change my password for for ssmpt in unMenu, I did the following.

 

1) Selected - Config View/Edit > mail-ssmtp package

2) Clicked the "Edit" button

3) Made the required change for PACKAGE_VARIABLE Mail Password||vAUTH_PASS=

4) Saved it

 

Now, I used the test email package and it failed authentication, so I looked at file I just edited again, hmm...the edit had not stuck, my old password was still there, so I repeated the process, same thing.

 

I also tested using /usr/local/etc/ssmtp# echo -e "subject: a test of email"|ssmtp -d root - same result.

 

I then repeated the process but this time I restarted unMenu , and the password change does appear to have stuck this time, but upon testing it still fails authentication, I tried various other combinations same result.

 

So, I decide to look at the ssmtp.conf file at "/usr/local/etc/ and the password is still set at my old password, even though the unMenu has the new one there (eventually).

 

I edited the ssmtp.conf using vi and added my new password, everything worked straight away.

 

All of this doesn't seem right, and it might be a possible bug, so I thought I'd post here.

 

Also, what is the latest version of unMenu? When I try to download it I get the following:

 

Upon checking:

 

Available files on current release list:

myMain_local.conf :Revision: 182  Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)

 

Upon trying to install:

 

Downloading myMain_local.conf

rev $Revision: 182 $ $Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)$

Local myMain_local.conf file exists, /tmp/unmenu_tmp/myMain_local.conf not installed.  You will need to delete the local file first before the new will be installed.

 

I have unMenu Version 1.4 Revision: 223 installed on unRaid 4.5.6

 

I have ssmtp configured for my gmail account and has worked fine for over 12 months.

 

I recently changed my gmail password so needed to change my password for for ssmpt in unMenu, I did the following.

 

1) Selected - Config View/Edit > mail-ssmtp package

2) Clicked the "Edit" button

3) Made the required change for PACKAGE_VARIABLE Mail Password||vAUTH_PASS=

4) Saved it

 

Now, I used the test email package and it failed authentication, so I looked at file I just edited again, hmm...the edit had not stuck, my old password was still there, so I repeated the process, same thing.

 

I also tested using /usr/local/etc/ssmtp# echo -e "subject: a test of email"|ssmtp -d root - same result.

 

I then repeated the process but this time I restarted unMenu , and the password change does appear to have stuck this time, but upon testing it still fails authentication, I tried various other combinations same result.

 

So, I decide to look at the ssmtp.conf file at "/usr/local/etc/ and the password is still set at my old password, even though the unMenu has the new one there (eventually).

 

I edited the ssmtp.conf using vi and added my new password, everything worked straight away.

 

All of this doesn't seem right, and it might be a possible bug, so I thought I'd post here.

 

Also, what is the latest version of unMenu? When I try to download it I get the following:

 

Upon checking:

 

Available files on current release list:

myMain_local.conf :Revision: 182  Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)

 

Upon trying to install:

 

Downloading myMain_local.conf

rev $Revision: 182 $ $Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)$

Local myMain_local.conf file exists, /tmp/unmenu_tmp/myMain_local.conf not installed.  You will need to delete the local file first before the new will be installed.

 

I'll check it out when I get a free moment, but to get the new password in place you must ALSO press the "Re-install with new values" button after saving the newly edited config variables.  Otherwise, the new values will not get used until you reboot.

 

Joe L.

Thanks Joe.

 

I'll try the process again, although I thought I had done the "Re-install with new values" at some point, as I tried various combinations out to try and diagnose the problem, but may have missed a step.