Re: [PLUG] Question for the sysops -- IoT devices and email

Lots of factors to weigh here, and not a ton of detail. In the abstract (and I'm sure loads of other PLUG folks have more experience running email servers than i do), contracting with an existing provider of bulk email (e.g. mailchimp) so that they can provide features like rate limiting,

Re: [PLUG] Question for the sysops -- IoT devices and email

Outbound email is amongst the most likely thing to be blocked, so getting your "fix-me-feed-me" message outside the local network by some other means seems necessary. How far away does the message need to get? Conceptually, you need the sender and receiver of your message to rendezvous some how.

Re: [PLUG] Question for the sysops -- IoT devices and email

On 03/04/2018 02:52 PM, t...@wescottdesign.com wrote: Not a device that lets YOU send email -- a device that sends you email when it needs attention (i.e., it fails a built-in-test, or it's out of feedstock, or whatever). Are you a sysop?  Do you have to take care of IoT devices (nuclear

Re: [PLUG] Question for the sysops -- IoT devices and email

A. Thanks for clarifying! Maybe I still don't understand what you're asking but SNMP, email push and text notifications have been around for decades. Now most ip devices have either a web gui or telemetry app. But anyway, I personally don't do IoT mostly due to security but also b'cuz

Re: [PLUG] Question for the sysops -- IoT devices and email

On 2018-03-04 12:44, Russell Senior wrote: On Sun, Mar 4, 2018 at 12:41 PM, Russell Senior wrote: What is the purpose of the message? Maybe you can send a message instead to a central server (e.g. via a UDP packet to a particular port), do some validation on that

Re: [PLUG] Question for the sysops -- IoT devices and email

On 2018-03-04 13:11, Mke C> wrote: On 03/04/2018 11:52 AM, plug-requ...@pdxlinux.org wrote: If I sold you an IoT device that sent email, how would you want it to do so? I'm looking for the ideal compromise between minimum work programming the thing, reliably getting emails to people who need

Re: [PLUG] Question for the sysops -- IoT devices and email

On 03/04/2018 01:39 PM, plug-requ...@pdxlinux.org wrote: do some validation on that message (perhaps with public key cryptography) and have the central server send the email for you? Knowing just enough about BlockChain to be dangerous, Russel's comment makes me think that if BlockChain was

Re: [PLUG] Question for the sysops -- IoT devices and email

On 03/04/2018 11:52 AM, plug-requ...@pdxlinux.org wrote: If I sold you an IoT device that sent email, how would you want it to do so? I forgot to mention, The FreedomBox. https://freedomboxfoundation.org/learn/ What is FreedomBox? * Email and telecommunications that protects privacy and

Re: [PLUG] Question for the sysops -- IoT devices and email

On Sun, Mar 4, 2018 at 12:41 PM, Russell Senior wrote: > What is the purpose of the message? Maybe you can send a message > instead to a central server (e.g. via a UDP packet to a particular > port), do some validation on that message (perhaps with public key >

Re: [PLUG] Question for the sysops -- IoT devices and email

What is the purpose of the message? Maybe you can send a message instead to a central server (e.g. via a UDP packet to a particular port), do some validation on that message (perhaps with public key cryptography) and have the central server send the email for you? On Sun, Mar 4, 2018 at 12:35

Re: [PLUG] Question for the sysops -- IoT devices and email

Thanks John. You've kind of summed up what I know -- at least I know I have it right. Need to think of how to make it work as you said, without burdening any non-technical people with too much work. On 2018-03-04 11:51, John Meissen wrote: Sending email is easy. The device simply connects

Re: [PLUG] Question for the sysops -- IoT devices and email

Sending email is easy. The device simply connects to the MX host for the destination (specified in the destination domain's DNS records) and hands off the email. The problems arise when ISPs block outgoing connections to port 25 (to mitigate spam from compromised systems inside their network)