M1EXP Email Capabilities Update? Still no SSL? Verizon POP uses SSL now...along with most other Emai

G

gatchel

Senior Member
 I noticed that my elk email hasn't been working for the last few days. I logged on to the Verizon account and there they were, 4 notices about the email settings changes that need to be made to continue operation of the POP access. They all require SSL, go figure. SSL has only been gaining popularity for 5 to 10 years or so.
 
Isn't it about time for Elk to get on the ball with an email capabilities update for the M1XEP? It's been talked about for a while now and still nothing.
 
Or maybe just abandon the M1XEP all together and make something that can do more than email 16 messages
 
Fortunately I have an ISY-994i to do the heavy lifting as far as email goes but it was nice to know that the M1 was connected and capable of emailing. (not locked up)
 
Anyone else using Verizon? Check your email capabilities.
 
I know there are a few other possibilities for free email accounts that use POP without SSL but I'd like to use the stuff I am already paying for.
 
Or just setup something like a cheap raspberry pi to act as an mail proxy.  Your Elk would talk to it and then it would, in turn, do the sending/receiving to the rest of the world.  The nice part being the RasPi devices are cheap, low power and once configured, pretty reliable. 
 
I would think you could go even cheaper and do a pogoplug or similar. 
 
I ended up setting up hMailServer on one of my always-on machines for a similar reason; in my case it was a multifunction color laser that didn't support authenticated smtp - same basic problem.
 
You just need something to run stunnel to encrypt/decrypt it for you.  There are versions to run on any platform including DDWRT.
 
wuench said:
You just need something to run stunnel to encrypt/decrypt it for you.  There are versions to run on any platform including DDWRT.
Click to expand...
Not sure that'd be any easier, and possibly more complicated to configure.  I've usually found it easier to use a proxying setup.  This way you can configure the proxying machine to be as dumb as the local devices need them to be.  But then use it to make any necessary changes to make the outside connections.  This being both outbound SMTP, along with in-bound secured POP or IMAP.
 
He'd mentioned POP with SSL.   I haven't checked lately but a tunnel alone might be problematic with regard to passwords and plain text.  I could be misinformed.
 
That and there's the reliability factor.  A tunnel doesn't help you if the remote end is unreachable for whatever reason.  Some dumb devices do not take well to unexpected errors.  A proxy does the store and forward for you.  Along with having a bit more logging/debugging options.
 
Either way's fine.
 
You must log in or register to reply here.
Back
Top