That was fast!
Unfortunately it didn't receive my code - 92b930c6-b2ff-419a-ba1d-a8efcd05f100 , I tried mailing without signature and tried all three email ids.
This approach has its advantages and disadvantages,
- Not dependent upon the email service provider's status updates, So we can get the status even if the provider doesn't update the outage.
- Private.
But,
- Can't say if the email got stuck in the spam or whether there was an outage.
- Chances of sender's email loosing reputation is high if it gets sent to spam repeatedly due to unusual email content.
- Waiting period wouldn't be practical for mailing lists.
(A) I think the first two can be addressed by using your email id(X) as a bridge and then verifying the email service status by mailing to your own pool of email ids(Y) from each service which has A listed as contact, so that it wouldn't end up in spam and that it's not dependent upon single email id now.
Waiting period can be addressed by not having to receive email from the sender in first place, you can conduct(A) at regular intervals and have the status ready on demand through API.