You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since I am the developer, I want to have freedom to set the headers. One of the reasons is to make sure the content is correctly interpreted when the attachment is sent. For example, when I see the attachment I can see that it is correctly sent as attachment but the content inside the file is not correct probably a buffer/unrecognizable characters, this confuses gmail and mark it as a potential risk, what I would expect from a library and the platform is:
Able to see the exact headers used
Override the headers
Notes
Hey devs, I just found out that using Buffer with uft-8 encoder did the trick:
Turns out that sending a string is not enough, somehow the content is not interpreted correctly.
I also had some inconsistencies with my ics file so I decided to create a valid one from another platform, one that can be added to calendar and also to discard other factors in this issue , after getting a valid ics I tried to send it different ways, so Buffer was how I was able to send it without issues.
I will let this issue open so you guys can close it, if you close it I will assume you read this issue.
Perfection is achieved not when there is nothing more to add, but rather when there is nothing more to take away.Antoine de Saint-Exupéry
The text was updated successfully, but these errors were encountered:
Context
What should be expected?
Since I am the developer, I want to have freedom to set the headers. One of the reasons is to make sure the content is correctly interpreted when the attachment is sent. For example, when I see the attachment I can see that it is correctly sent as attachment but the content inside the file is not correct probably a buffer/unrecognizable characters, this confuses gmail and mark it as a potential risk, what I would expect from a library and the platform is:
Notes
Hey devs, I just found out that using Buffer with uft-8 encoder did the trick:
I was trying to follow a mix between two examples, where the ics file was sent as a string (attachment).
https://github.com/resend/resend-examples/blob/main/with-ical/src/pages/api/send.ts
Turns out that sending a string is not enough, somehow the content is not interpreted correctly.
I also had some inconsistencies with my ics file so I decided to create a valid one from another platform, one that can be added to calendar and also to discard other factors in this issue , after getting a valid ics I tried to send it different ways, so Buffer was how I was able to send it without issues.
I will let this issue open so you guys can close it, if you close it I will assume you read this issue.
The text was updated successfully, but these errors were encountered: