open/click events, unsubscribes, etc.).Īlso note that at the time of writing, that answer had 26 downvotes (and zero upvotes) on the SendGrid website, probably indicating that many other users have experienced this problem. Step 1: Make sure MX records are set up correctly Mail Exchange (MX) records direct your domain's email to the servers that host your domain's user accounts. Any additional Twilio SendGrid events for your email message would be triggered by recipient engagement (i.e. In this situation, we would have posted the Delivered event, but not have any insight into the additional filtering. Often times, a recipient domain will initially accept a message for delivery, and then apply additional filtering afterwards. The receiving server could send it to the inbox, queue it for later delivery, put it into the spam folder, etc. Once an email is accepted by the destination server, we are unable to see what happens to the message. Twilio SendGrid posts the Delivered event after the destination server accepts the message with a 250 OK response. ![]() At this point, the receiving server could send your mail to the inbox, queue it for later delivery, put it into the spam folder, or even drop the email. ![]() This is not an answer, as it doesn't help work out why the emails that are "Delivered" have not been received, but this is SendGrid's note on why Email messages with the “Delivered” status are not received: Why is mail marked 'Delivered' when it isn't in the inbox Twilio SendGrid posts the Delivered event after the recipient server accepts the message with a 250 OK response.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |