Page 1 of 1

TOS6.0.420 (et al) Email Notification Failed

Posted: 29 Jul 2024, 18:50
by Gremlin
(As mentioned elsewhere)

To further investigate I have performed a clean instal of TOS5.1.145 onto a single HDD Traid, followed by update to TOS6.0.420.

With the default configuration ('local') the response is 'Failed to send to ....'

Setup custom config with known good server/addressee/password (as used in TOS5.1) Port 25, Auth None ('--') . This can be saved (where there were problems previously) but still results in 'Failed to send to .....'

I accept that we have previously been through this and thought it had been sorted (previous thread now locked) but it appears to have regressed for me (and some others).

I do note that, for some reason, in the Authorisation box there appears to be a different number of '-' compared to TOS5.1 but you have to look very closely :shock:

Either I am missing something very basic (Something that needs to be changed to enable the default mechanism, which would be unhelpful) or some previous fix has been regressed.

Re: TOS6.0.420 (et al) Email Notification Failed

Posted: 29 Jul 2024, 21:18
by TMeric
Hello, you can visit our official website, contact our online customer service, schedule an appointment with an engineer, and have them remotely troubleshoot the issue for you.

Re: TOS6.0.420 (et al) Email Notification Failed

Posted: 30 Jul 2024, 01:57
by Gremlin
TMeric wrote: 29 Jul 2024, 21:18 Hello, you can visit our official website, contact our online customer service, schedule an appointment with an engineer, and have them remotely troubleshoot the issue for you.
Apart from being impractical at this time (another story) I think I have discovered some of the issues with Notifications.

I was able to establish outgoing notification emails only provided I used TLS/SSL protocols. This maybe why, in some cases, users &/or @TM support do not see an issue.

Also, much to my chagrin, I came to realise that every time a change is made in the dialogue (including adding a cc) 2 things must happen:
a) The password must be re-entered and
b) The authentication mode must be reset
before the change is applied. This may be sensible, but is none too clear.

I am still convinced there is an issue with the default settings (admin address only and using 'local server'). This may revolve around how the authentication is applied (or not). I would be grateful if someone @TMSupport would thoroughly investigate all the settings and advise/fix.

REQUEST: please use "None" or similar for 'Authentication' option in the dialogue. The use of -- is too vague.

Thank you.