trmitche
Member
Being that I work for AO tech support, I realize that I may get razzed for asking a question here. So of course I searched for someone else with this same issue before posting it, but surprisingly, UTFSE did not help me out with this....maybe I missed a relevant thread due to the topic name or something. Anyway....
My ISP, AT&T Yahoo, recently (several months ago actually) started requiring SSL encryption on its SMTP server, which the Elk M1XEP email function apparently does not support. I thought of using Gmail's SMTP server as a work-around, but it seems they also employ SSL. Anyone else run into this issue? If so, how did you get around it? Maybe by using a free email account that does not utilize SSL? Thanks in advance for any assistance.
P.S - When Elk email was working (before the SSL requirement), I also noticed that, if I added or changed an email recipient/message in the XEP email list, email functionality would stop working completely, until I removed all my email account settings from the XEP screen, rebooted the XEP, and then re-populated the settings. I believe this occured when I was on firmware version 1.2.12, which I'm actually still on. I'll try updating to 1.2.14 tonight, but that's all a moot point if I can't get around the SSL issue.
My ISP, AT&T Yahoo, recently (several months ago actually) started requiring SSL encryption on its SMTP server, which the Elk M1XEP email function apparently does not support. I thought of using Gmail's SMTP server as a work-around, but it seems they also employ SSL. Anyone else run into this issue? If so, how did you get around it? Maybe by using a free email account that does not utilize SSL? Thanks in advance for any assistance.
P.S - When Elk email was working (before the SSL requirement), I also noticed that, if I added or changed an email recipient/message in the XEP email list, email functionality would stop working completely, until I removed all my email account settings from the XEP screen, rebooted the XEP, and then re-populated the settings. I believe this occured when I was on firmware version 1.2.12, which I'm actually still on. I'll try updating to 1.2.14 tonight, but that's all a moot point if I can't get around the SSL issue.