Since using SMTP mail sending with Basic auth will be phased-out, we are working to transition with an alternative. We are trying both Graph API and SMTP with oauth, and we are facing some issues with a critical use case of our app, that is sending meeting request using an attached IcalFile.
We discover that with the 2 solutions, we can no more receive an ica file properly displayed as a meeting request in outlook (even it works fine in other email client like gmail)
Since the problemn seem lionked to the way email is processed and sent, can we have any help and solutions on this issue ? Please fin below some details about the tryout we did, and the behavior we observed.
We can adapt some option on how we use emails, how be build ICS, but we need to keep sending ICS files, since we need to be able to send email using other providers, using regular SMTP servers.
Regards.
CASE 1 Configuration : SMTP with oauth / - ".ics" file send as "attachment" Results
- Outlook : attachment visible, but not interpreted as meeting request ICS part visible in raw format when downloading message
- Gmail : all is fine
(see attached file "SMTP & STARTTLS - attachment.pdf")
CASE 2
Configuration : SMTP with oauth / - ".ics" file send as "inline"
Results
- Outlook : no attachment nor meeting request visible
ICS part not visible when doanwsloding message, it seems have been supressed
- Gmail : no attachment nor meeting request visible
ICS part not visible when doanwsloding message, it seems have been supressed
(see attached file "SMTP & STARTTLS - inline.pdf")
CASE 3
Configuration : sending mail with GraphAPI / - ".ics" file send as "attachment"
Results
- Outlook : attachment visible, but not interpreted as meeting request
- Gmail : all is fine
(see attached file "GRAPH API - attachment")
CASE 4
Configuration : sending mail with GraphAPI / - ".ics" file send as "attachment"
Results
- Outlook : no attachment nor meeting request visible ICS file part visible when downloading raw message
- Gmail : all is fine
(see attached file "GRAPH API - inline")
Since using SMTP mail sending with Basic auth will be phased-out, we are working to transition with an alternative.
We are trying both Graph API and SMTP with oauth, and we are facing some issues with a critical use case of our app, that is sending meeting request using an attached IcalFile.
We discover that with the 2 solutions, we can no more receive an ica file properly displayed as a meeting request in outlook (even it works fine in other email client like gmail)
Since the problemn seem lionked to the way email is processed and sent, can we have any help and solutions on this issue ?
Please fin below some details about the tryout we did, and the behavior we observed.
We can adapt some option on how we use emails, how be build ICS, but we need to keep sending ICS files, since we need to be able to send email using other providers, using regular SMTP servers.
Regards.
CASE 1
Configuration : SMTP with oauth / - ".ics" file send as "attachment"
Results
- Outlook : attachment visible, but not interpreted as meeting request
ICS part visible in raw format when downloading message
- Gmail : all is fine
(see attached file "SMTP & STARTTLS - attachment.pdf")
CASE 2
Configuration : SMTP with oauth / - ".ics" file send as "inline"
Results
- Outlook : no attachment nor meeting request visible
ICS part not visible when doanwsloding message, it seems have been supressed
- Gmail : no attachment nor meeting request visible
ICS part not visible when doanwsloding message, it seems have been supressed
(see attached file "SMTP & STARTTLS - inline.pdf")
CASE 3
Configuration : sending mail with GraphAPI / - ".ics" file send as "attachment"
Results
- Outlook : attachment visible, but not interpreted as meeting request
- Gmail : all is fine
(see attached file "GRAPH API - attachment")
CASE 4
Configuration : sending mail with GraphAPI / - ".ics" file send as "attachment"
Results
- Outlook : no attachment nor meeting request visible
ICS file part visible when downloading raw message
- Gmail : all is fine
(see attached file "GRAPH API - inline")
Attachments :
https://share.adequasys.com/link/l2Y3EnJg7FAUsCOTZBQC0L