My Add-in can use the EWS and REST endpoints, and both send email fine, and I expect the Graph endpoint will as well (since it's replacing REST which will be retired in Oct 2022)... except I'm not sure under what conditions those endpoints might fail, or which one(s) to use and when (e.g. android(web+app)/apple(web+app)/live.com/office.com(free+paid+corporate)/outlook.exe(pc+mac)/tablets/... and whether or not the customers server in use matters (exchange/SMTP/free/paid/...) ... so yeah... having some way to send that "sorts all that out for us" would be a great idea.
IDEALLY - a way that give us full control over all email headers (including the To: and Cc: which are *independant* of the recipient (e.g. Bcc)) would be perfect. There are many use cases where a multi-party email needs to go to more than 1 person with each person getting a slightly different version (e.g. for forensic purposes, so if one of those parties "leaks" content in violation of policies, the culprit can be identified).
No CommentsBe the first to comment