What a snaky individual you have turned out to be.
So, nothing I have tried modifying the Yaml is allowing this to load properly at the HA Startup. Very Frustrating. I assume that there is not a clear issue with my Yaml since no one noted this but if you can point to one please let me know. I did try changing the encryption as well as the port but no success
[quote=“Shesakillatwo, post:76, topic:635961”]
This is not helping the OP.
Please do not drift the thread.
I can’t tell you if your yaml is broken but I can tell you that your encryption and port settings are “different” from what we’d usually see.
Maybe if you could pleas tell us who your ISP and mail service are we can look an see if they have any restrictions that might be effecting you.
I know that a couple of ISP changed their mail hosts to use Google’s back end system, which means that they now use Open Authentication, so you need to change some of the default security setting in order to be able to log in the way that you are doing here.
Does your mail provider mention needing an “app password” in any of its documentation?
A little trick that you can use is to try to connect to your mail server using software like Outlook or Thunderbird. This will create a profile on your computer that will contain the correct port and security settings that you can use to compare with what you have in HA.
At the very least it will confirm if these settings are correct and thus that the problem is with HA, and not your log in.
My ISP is Spectrum but it is formally charter.net. Spectrum bought them opr took them over about 6-8 years ago. The email is still a charter.net email. Again, with the original yaml I posted this SMTP service worked fine for a year. Any thoughts please share them but I am gonna play with some variations of settings.
what happens if you try to connect from the commandline?
telnet smtp.xxxxxxxx.net 25
So, for now I am fixed. After messing with this for the past 3 days I put everything back where it started and only changed this line inserting the actual password and not referencing my secrets file:
password: "abcdefghij" #secret! outgoingsmtp_pw
The Secrets file does contain the correct password and has not changed in a year so I have no idea why this now works???
Has anything else using the secret file gone haywire?
No, that is actually the only thing in my secrets file.
Out of interest, have you tried using\not using single or double quotes around your password in the secret file?
When I added the actual password to my Configuration.yaml file I put it in Double quotes and it worked. The password as it appears in my secrets.yaml is not in any quotes.