What would be the human reaction to a 15 second latency (nothing to
regular e-mail service) on a light switch - hit it again and again until
the first message arrives.
Fun to imagine lights suddenly turning on and off in rapid succession as
delayed e-mail starts to get delivered a few seconds after the initial
request.
The fridge could e-mail the grocery list when the milk runs low but
e-mail not a good fit for most IoT applications.
Ron
On 17/03/2017 3:18 AM, Sean Greenslade wrote:
On Thu, Mar 16, 2017 at 05:48:49PM -0700, [email protected] wrote:
I had no idea you could receive email on any port. I wonder how many
ISPs allow this.
Sure, you can run any service on any port. The default ports (e.g. 25
for SMTP) are simply there to make interoperability easy.
Most ISPs do nothing to block specific services on specific ports. The
only thing I've ever seen is some residential ISPs block all outgoing
connections on port 25 to hamstring spambots on infected home PCs. This
is typically a blanket port ban, so it doesn't matter if it's a SMTP
server on that port or not; nothing goes out port 25. This generally
doesn't effect home users, since they almost always use a submission
port or a webmail client to get to their mail relay.
In any event, would this be THE scheme to use for an IOT application?
That is send an email to turn on/off a sprinker, light, etc. The idea
being postfix et all does all the security, AKA the hard part.
While it would certainly be _A_ way of doing IoT, I certainly wouldn't
call it _THE_ way. Email is not particularly well-suited for command and
control type applications. Lots of protocol and message overhead, high
latency, unidirectional channels...overall not a great fit.
--Sean
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102