Configuration options for .ics files when using a mailgun template (support for Outlook)
Outlook cannot automatically read the default way Mailgun attaches .ics attachments to emails. (Gmail can, but sadly, outlook can't).
We would like to (a) send an email with a mailgun template with (b) a .ics file attached that (c) gets added correctly to a recipient's calendar.
Using the normal
messages endpoint of the API with a template, we can get (a) and (b), but not (c). If we construct our own MIME message, we can get (b) and (c), but not (a).
Mailgun attaches .ics invites in the following way:
Example from mailgun (using a template): --1635db27c5b9dd89a16962b725b259cd7c88d10b65664ba25a3bda4e481a Content-Type: text/calendar; name="invite.ics" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="invite.ics" b64-encoded-string...
Outlook expects them to be encoded like the following:
Example of what works with outlook: --_000_PN3P287MB0720741F92424A8DE26DB3AEB638APN3P287MB0720INDP_ Content-Type: text/calendar; charset="utf-8"; method=REQUEST Content-Transfer-Encoding: base64 b64-encoded-string...
Feature idea: add the ability to, with .ics files, add them in both ways so that all email clients can read the calendar data (calendly sometimes does this with invites).