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
Related
We've used Mailgun for 8+ years for inbound email routing, and always noticed lots of emails ended up in our spam folder(s).
After speaking to the Google team, it turns out that Mailgun is simply not compatible with Gmail when using inbound routes as it doesn't "relay" emails, but rather re-sends them modifying the headers.
This causes all emails to fail SPF! This means a certain (often large %) of your emails will end up in the spam folder for no good reason.
From Google:
"We've identified that Mailgun is re-sending those emails, while Google is expecting for those emails to be relayed. Re-sending emails causes the SMTP sender to change to [redacted]. What happens then is SPF is checked for [redacted]. Inbound gateway is telling to ignore Mailgun's IP address, so the previous one is being used instead. This would cause all emails to fail SPF.
In this scenario, it's recommended to contact Mailgun and ask them if there's a way to relay those emails, so that SMTP sender would not change."
Mailgun Response:
"Unfortunately, there isn't much that can be done to prevent this as this is how our Routes work"
Any solutions?
Has anyone managed to work around this issue?
Or does anyone have a fully-featured recommended alternative to Mailgun Routes?
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 am trying to setup mails on my VestaCP, i have made MX, Dmarc records, followed every guide about these records on google but there are 2 problems.
Here is my mxtoolbox results
https://mxtoolbox.com/domain/letsupload.co/
=======
1st Problem -/
The first problem is that all my mails sent from contact#letsupload.co are sent into spam folders, though i created all required records.
2nd Problem -/
I can send emails from my webmail but i cant receive them, when i send email from gmail it gets sent, there is no error that my email was not delivered but i dont receive it in my webmail.
Please help me out.
You will find that not many people will help because of the lack of code. Just always make sure that when you ask a question like this wondering why something isn't working, you provide code so people can pin point a problem. Stack Overflow don't put that page there before you ask a question because they think you're stupid, they do it so you can get a more specific and the best response to your question. So just make sure you give this a look.
However, I had a similar issue before where all my mails were being sent to the spam folder and they're a few things that could be the cause:
Mail Client Reverse DNS Checks: You mentioned that you are using a personal domain but one thing to remember is that your domain will have its on DNS server.e.g. if you are with GoDaddy that would be the default DNS setting. So the problem is that when you send an email to lets say a #outlook.com email server the mail client of the recipient will do a reverse DNS check. So it realises that you are sending to an #outlook.com but the email is coming from #letsupload.co. So it realises that you are sending from an IP that isn't related to the domain you sending to and that is what SPAM is! Like I said without seeing your code I can't exactly know how to help but if you aren't aready using a mail server with Authentication enabled that could be a cause. Try using a server with authentication and add this code:
// I am using $mail as my instance of PHPMailer
$mail->Host = 'your-new-server-with-authentication';
$mail->Port = 587; // usually the default port (double check though)
$mail->SMTPAuth = true;
// now define the username and password for your mail server
$mail->Username = 'your-username#mailserver.com';
$mail->Password = 'OpenSesame123';
Reply to: You can also try adding a reply-to email address. Some mail servers tend to put emails in spam that don't have a reply email address to stop bots from spamming a person's email account. So try adding this if you haven't already:
// I am using $mail as my instance of the PHPMailer
$mail->AddReplyTo('youremail#domain.com');
Implementing SPF: If the above to fail then the chances are that you need to implement SPF. You can learn all about this from an expert on the subject gr8gonzo here is the tutorial and article he wrote on the subject. That will not only just help with implementing SPF but also with the best practises for when you're sending emails.
I'm setting mailgun route to xx#me.com to forward an email to a server at http://xxx:7000/reply.
I tested already the email route and it's fine as well as the server is up both in browser and using curl. However sending an email to xx#me.com still nothing happens.
There is already a similar question but nobody answered:
Can't recieve incoming mail with Mailgun
There are a few requirements for handling incoming emails with Mailgun.
Your account must be verified (email/SMS message)
The domain or subdomain must be added to the account.
SPF & DKIM must be verified and have MX records configured with Mailgun's values. Details for DNS record information
Route filters configured with the recipient domain or subdomain matching. (Example: Domain "bar.com" is added to the account. The expression can match_recipient("foo#bar.com"). If a subdomain is added, then it will need to match the subdomain, e.g. match_recipient("foo#mg.bar.com"))
The error from the linked question would be due to one of the above requirements wasn't fulfilled. A rejection of "550 5.7.1 Relaying denied" from Mailgun's incoming mail servers indicates a domain or subdomain has MX records pointed toward Mailgun's but the domain does not exist within an account.
**Disclaimer I work at Mailgun
I know this is 6 months old, but since I spent 4 hours trying to figure this out, I will share my solution:
There is another cause of the 5.7.1 Relaying denied message: My mailgun account wasn't verified. I saw someone suggest this but I figured they just meant that I had to verify the address I was forwarding to. Nope, when I logged in today I saw a banner at the top saying click here to resend your verification email. I did that, it went through a text message verification process, and all immediately started working!
I know this is quite a stale thread, but I also wanted to chime in here in hopes of saving folks a few hours of their life trying to solve the "550 5.7.1 Relaying denied" caper.
For me? It was what has plagued me on several occasions. I was able to verify via Gmail > 'Settings' > 'Accounts and Import' > 'Add another email address' only after I disconnected from my software-based VPN (Private Internet Access).
[Your sigh or wince here]
Now, go get it... make it happen. ;-)
If you're using MailGun with cPanel (for example, after following this tutorial) and you're getting the 550 5.7.1 Relaying denied error, make sure you're using the MailGun SMTP credentials given after adding your domain (as opposed to your MailGun username and password as the documentation suggests). That was the origin of my own problem.
Another reason for this error code may well be that you are trying to send stuff over SMTP whereas you've indicated on the sending properties of mailgun settings for your domain that you want to use the API...
I know there are lots of questions on here already about being able to send emails to hotmail. I have read through them all, as well as lots of online posts over the last few weeks and have still been unable to fix this issue.
The issue that I am having is that I am unable to send emails to customers who have a hotmail email address. I can send emails to yahoo fine, I can also send emails to gmail as well (although these seem to go to the junk folder), however when I sent emails to hotmail email addresses, they just seem to never arrive.
I am using swiftMailer in a PHP Symfony2 Application to send the emails.
The server that my application sits on is a Linux CentOs box and I have open relay turned off
I have sent emails to 'auth-results#verifier.port25.com' to check that SPF, DKIM and Sender-Id is setup correctly. Partial output of that report is below:
==========================================================
Summary of Results
SPF check: pass
DomainKeys check: neutral
DKIM check: pass
Sender-ID check: pass
SpamAssassin check: ham
==========================================================
The DomainKeys check is neutral, i'm not sure if that is required as as DKIM is an extension on the DomainKeys.
I have setup a v=spf1 record and a spf2.0/pra record in the DNS as TXT entries.
My help on this would be greatly appreciated. I think the issue may be to do with Sender-ID, but I dont know too much about this subject area.
Check your mail server logs. Are you seeing something like this for delivery to your Hotmail recipients:
550 SC-001 (COL004-MC4F43) Unfortunately, messages from xxx.xxx.xxx.xx weren't sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors.
If so, then it means that your mail server IP is on Microsoft's blacklist. You probably won't have much luck sending to users at live.com, outlook.com, or msn.com either. Fortunately, there is a solution. See the link below for a decent guide on how to resolve the problem:
https://www.rackaid.com/blog/hotmail-blacklist-removal/.
The key is to submit a request to Microsoft to remove your IP address from their blacklist (at https://support.live.com/eform.aspx?productKey=edfsmsbl3&ct=eformts&wa=wsignin1.0&scrx=1), but don't do that until you are sure that whatever caused you to become blacklisted has been resolved, as Microsoft doesn't like repeat offenders.