Given that Zawinski's Law of Software Envelopment[0] still seems to hold true, this all looks super powerful. What type of uses does the CLI have? Is it for tr

Given that Zawinski's Law of Software Envelopment[0] still seems to hold true, this all looks super powerful. What type of uses does the CLI have? Is it for triggering actions? One thing I think would be cool is if I could write a program that would run on one of my servers that would execute some automation when mailscript triggers an action. I assume there is some generic webhook support in mailscript that I could use to implement this, but the automation I'm thinking of is not the kind of thing I'd want to expose as a web-hook (like alarm remediations) so I guess I'd be looking for something more secure. Typing that out gave me another idea for a potential category of actions: AWS (and other cloud providers). I could implement this on my own with the previous feature, but if it makes sense it could be cool to have them baked in if the user provided creds for a AWS API user with some IAM roles and let me template API calls to be run as actions. A less glamorous but very interesting use case to investigate might be Linux kernel maintainers, whose workflows are heavily based around email (e.g. the use of git send-email [1] and all of the conventions in the Submitting patches guide[2]). This looks like fun and I can totally imagine some use cases for this with personal projects. Excited to see where this goes! [0] "Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can." -- Jamie Zakinski [1] https://www.kernel.org/doc/html/v4.17/process/email-clients.html#email-clients https://www.kernel.org/doc/html/v4.17/process/email-clients.... [2] https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html https://www.kernel.org/doc/html/v4.17/process/submitting-pat...