While most of the time, email is simply used for a short message here and there about sales or correspondence, it's an ubiquitious and can be easily harnessed to do more interesting things for us. I've found that sometimes I want to know more than just the text that's there... Analytics, Data collection, triggering scripts, or even just more indepth processing of a stream of emails, using an external script can help out tremendously. It's fairly straight forward to setup, so let's take a peek at the process!
Here's a really simple one. When you decide to remove an Elasticsearch node, either because it's having trouble or in need of an update, it's best to proactively shift shards off of that node, so there's no hit to the cluster or risk of dataloss when it's removed. See how its done
Many times we use internal domains for test or beta environments, or perhaps just internal or intranet services. SSL Certs can be expensive, especially wildcard certs, so we let it slide... Hitting that Chrome or Firefox "Just let me in, I know it's self signed!" button every time you visit a site. And while that works, even though it's annoying, it doesn't promote secure communications and best practices. If users get used to that, what if it really IS a man in the middle attack? What if you need to query those https endpoints programmatically... and not always have an "Ignore the cert" option? There is a good way around this: Create your own Root CA and sign your internal domain. See how...