Is it possible to permanently reject a given SendGrid Inbound Parse message so that delivery is not re-attempted? Should I return "HTTP 406-Not Acceptable" to accomplish this?
Apparently, this is not possible with SendGrid Inbound Parse (although it is with MailGun).
Related
I am working on an IMAP implementation using AWS API gateways in which I have to retrieve e-mails from a S3-bucket and get them into an e-mail client somehow, but I've not been able to find which requests those clients send when you try to retrieve e-mails from another source. My guess is GET-requests, but I'm honestly not even sure if it's REST-requests that are being sent. Does anyone have an idea?
Thanks in advance!
I am trying to send an email from my Firebase Cloud Functions using the SendGrid's mail client for Node.js
I am following their example described as follows:
const sgMail = require('#sendgrid/mail');
sgMail.setApiKey(functions.config().sendgrid.key);
const msg = {
to: 'my_own_mail#gmail.com',
from: 'my_other_own_mail#gmail.com',
subject: 'Sending with Twilio SendGrid is Fun',
text: 'and easy to do anywhere, even with Node.js',
html: '<strong>and easy to do anywhere, even with Node.js</strong>',
};
sgMail.send(msg);
Once the function is fired, everything gets executed successfully. In my function logs I get Status 202 and the actual mail gets delivered but not in the main mailbox but rather in the Spam folder. When I open the message, it simply says:
I don't really understand what is the problem.
NOTE: If I send the message to an Yahoo email it doesn't go in the Spam folder. Same applies if I send it to my business email.
Your problem is not related to cloud functions or the code, there are a few anti-spam rules you need to follow, this gave me a good starting point
Sendgrid does not send your messages to the SPAM folder it all depends on the recipients mail delivery flow spam filters.
Most messages are marked as spam for one of the following reasons
1. Message is not authenticated properly
Validated that your message is authenticated properly with SPF or DKIM
2.Your message originates from an IP that is in a Blacklist (this might be on Sendgrid's)
Try by sending a message to your self and open the message headers , then look for entries like the one below
Received: from xxxxxxxxx.com (xxxxxxx.com [xxx.xx.xxx.xx])
by xxxx.com with SMTPS id ##############
The IP between [] is the sending server IP try to use public blacklist such as spamhaus to see if it is blacklisted and report to Sendrig if you find a match
3.The content of your message has known phishing techniques (accidentally or not)
Check the "Format your mail" section for Gmail senders guidelines as general recommendation
I tried to send an email through sendgrid. I have a custom domain myself#contoso.com. If i try to send an email to user1#gmail.com with the from address as myself#contoso.com,then,the email is delivered to gmail with "via". When i try sending email to myself#contoso.com with the from address being myself#contoso.com the activity says the email is delivered however, in outlook client i have not received the email. What is it that I can try or do?
I have tried whitelisting contoso.com but it did not work
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:
Twilio SendGrid posts the Delivered event after the destination server accepts the message with a 250 OK response. Once an email is accepted by the destination server, we are unable to see what happens to the message. The receiving server could send it to the inbox, queue it for later delivery, put it into the spam folder, etc.
Often times, a recipient domain will initially accept a message for delivery, and then apply additional filtering afterwards. In this situation, we would have posted the Delivered event, but not have any insight into the additional filtering. Any additional Twilio SendGrid events for your email message would be triggered by recipient engagement (i.e. open/click events, unsubscribes, etc.).
Also 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.
I had several issue solving this problem. The most important part is to set "Sender Authentication" from sendgrid to your domain dns. There is a instruction here. I'm using godaddy, so the link to set dns is https://dcc.godaddy.com/manage//dns .
Short question:
Is there a way to reliably deliver emails using mailgun routes without getting this error message:
Failed: redacted#yahoo.com → redacted#gmail.com 'Re: Sample Subject Line' Server response: 550 550 5.7.1 Unauthenticated email from yahoo.com is not accepted due to domain's 5.7.1 DMARC policy. Please contact administrator of yahoo.com domain if 5.7.1 this was a legitimate mail. Please visit 5.7.1 http://support.google.com/mail/answer/2451690 to learn about DMARC 5.7.1 initiative. pw18si13572314vdb.85 - gsmtp
I like using mailgun routes because it meets my needs perfectly... but it seems that I can't reliably deliver mail to multiple recipients this way.
Long Story
I'm trying to find a service that will allow me to
create an email alias, mylist#mydomain.com
Send emails to mylist#mydomain.com and have that single email delivered to 10-20 people with me as the sender and mylist#mydomain.com in the to field (so "reply" goes to the sender and "reply-all" goes to everyone)
Mailgun routes fit this perfectly
I read their API docs and implemented a solution to read from our group database and make web calls to update my routes. Everything is great.
Everything worked great until I started getting the DMARC messages. Is there a way to avoid this? We're a small group (but dynamic) group and we'd like to make sending emails easy.
Thanks~!
Mailgun is now providing mailing list support, so you only need to create a new mailing list mylist#mydomain.com, add members to it, and then each members can discuss by sending an email to mylist#mydomain.com.
See https://documentation.mailgun.com/user_manual.html#mailing-lists
Does anyone know how to reject an email received through mailgun (mailgun.com)?
As a comparison, a similar service, cloudmailin allow you to return a status code of 404 or 403 to reject an email, and the sender of that email will receive a delivery failure notice.
I am trying the same with mailgun, however, mailgun will attemp to redeliver with longer and longer interval once it receive the 404 or 403 status code.
What I have tried:
Mailgun documentation doesn't say anything about this.
Mailgun support is not responding to my emails.
If I got an answer from mailgun I will post it here as an update.
Your app could return 406 code to mailgun to stop retrying. We added that feature recently and haven't yet updated our documentation regarding that.