Fully agree with Laurens. We have on multiple occasions developed drivers that ingest e-mails and process those. I recall use cases with e-mails that contained transmission schedules in the broadcast space, and a use case of a network provider that received e-mails from the power grid operator with information about planned maintenance on the power grid (so that they could automatically link HFC network outages with planned maintenance activities on the power grid - to prevent unnecessary escalations or even dispatch of field crews). But in each case it is not so much about being able to receive the mail, but more about the structure of the data contained in it (or lack thereof). In some cases the data was delivered via e-mail, but it was nicely structured in a fixed and well-defined text format, or even an XML file that was attached to the mail.