I keep getting these bounce backs, works on any other domain gmail, yahoo but not outlook/hotmail. is it me or them? I am using Smartermail with all possible settings setup ie DKIM SPF ii basically get a perfect score on https://www.mail-tester.com/web-zorml
Could not deliver message to the following recipient(s):
Failed Recipient: xxxxxxxxxxxxxxxxxxxxxx
Reason: Remote host said: 501 5.5.4 Invalid domain name [DB5EUR03FT018.eop-
EUR03.prod.protection.outlook.com]
prod.protection.outlook.com is Outlook/Microsoft's anti-snooping service. In case you didn't know, by viewing an email header, you can see the sender's IP. In order to circumvent this, Microsoft/Outlook sends your emails to prod.protection.outlook.com and then to the recipient, so if someone views the header, they get prod.protection.outlook.com's IP instead of yours. My guess is that your email provider doesn't recognise prod.protection.outlook.com as a valid domain name and thus can't send the email.
Related
I am performing some tests on my Nopcommerce site that should allow the user to type a message in to the contact box of the site and that message should be sent by email to a user.
When setting up and testing said user on the site, I am able to perform an email test against an internal email address and this works fine, I receive the email. However, if I try and send the email to an external email address, such as hotmail etc, I receive no error logs at all.
Has anyone ever come across this issue when trying to set up an email on a Nopcommerce site?
I am using port 25 however I have tried to use port 587 with no luck
The answer was that the username and password no longer existed for the server I was sending mail from. Moreover, another issue I had was that the mail still wasn't sending and was sitting in the Message queue. To overcome this I had to make sure that the bindings for the site on IIS were identical to the host values on the site. Doing this allowed me to send mail.
We are trying to figure out how to reduce the amount of bounces for our email platform and, one of the solutions we've found on the internet is to, via telnet, verify if the email exists.
So, for this example, we connect to the MX:
telnet alt4.aspmx.l.google.com 25
We start the communication:
helo hi
And, for every email we try (valid and invalid ones), we always receive the same response:
mail from: <fsafsaffsf#FasgagaoaSFasfas.co>
250 2.1.0 OK d8si998940wrc.143 - gsmtp
Are they doing this to prevent maybe a possible listing of valid emails?
What is the best way to verify if an email is valid before sending an email to it? We need this because our clients often uploads a spreadsheet with customer emails and always one or two of them are mistyped.
Thanks.
For a given recipient email address, you can:
extract its domain name (everything after #)
query DNS for the MX record(s) of that domain
for each specified server, connect and issue a VRFY command (see RFC 5321 Section 3.5), asking the server to verify the email address.
stop when you get a success reply.
However, SMTP servers are not required to implement VRFY. The simpler solution would be to just send the email normally, and then handle any errors from the RCPT TO command, and also handle the possibility that you simply can't always detect delivery errors in real time. If the email has to be relayed across servers, it might not fail on the server you use for sending, it may not fail until it is relayed to another server after you have already ended your SMTP session. In which case, the only way to detect delivery errors is to monitor your inbound mailbox for delivery failure emails being sent back to you.
I am creating a webservice with Mailgun to send out emails. It will BCC my own domain's email for every email sent out. Assuming my domain is "example.com". For every email sent out to a customer, say, customer1#gmail.com, I will BCC its content to sales#example.com.
Currently, the domain example.com and its email is hosted on a server with CPanel.
In Mailgun, I have added and verified the domain example.com. Using this domain, I've sent a mail to customer1#gmail.com and sales#example.com. The email is sent without issues to Gmail, however when sending to sales#example.com, I keep getting the error Server response: 550 550 Verification failed for <bounce+e0f051.e0179a-sales=example.com#example.com> No Such User Here.
What's baffling here is that if i send the email via Mailgun with another verified domain such as anotherexample.com, and then using this, I send my mail to sales#example.com. The email arrives perfectly fine without errors.
So far, the things I've tried:
Added Mailgun suggested SPF and DKIM
Modified SPF to include my CPanel server's IP (together with Mailgun SPF)
Deleted both the SPF and DKIM (one at a time and both at once)
Verified that the email sales#example.com exists. Using the CPanel webmail's interface, I can send and receive emails just fine.
Tried updating the CPanel MX entries Email routing from Local -> Automatic -> Remote. ("Local" works the best. If its set to "Remote", email sending and receiving doesnt work at all, even if mails are sent through Gmail/Hotmail).
My current MX settings are:
Priority 0: mail.example.com
My current Zone file records on CPanel:
example.com A <some ip>
mail.example.com A <same ip as above>
The code I am using to send mails via Mailgun (Ruby):
mg_client = Mailgun::Client.new 'xxxxxxxxxxx'
message_params = {:from => from_email,
:to => customer.email,
:bcc => bcc_email,
:subject => MessageTemplate.email_subject,
:text => message}
result = mg_client.send_message('example.com', message_params).to_h!
I currently do not have the SPF and DKIM records in the zone files. I've added and removed them and they had no effect on the error (still delivers fine to Gmail too).
I've spend the whole on this, scouring forums and whatnot but can't seem to find a solution.
If at all relevant, I have a 301 redirect of example.com to www.example.com(Which has a CNAME pointing to another server). But I've researched and found out that 301 redirect does not affect emails.
I don't think this is a send-side problem. You're sending to sales#example.com, but you're getting errors relating to bounce+e0f051.e0179a-sales=example.com#example.com, which is a typical VERP address. Now, VERP addresses are fine, so long as you're expecting them. Given that you are not apparently providing that explicit address to MailGun, I assume that they are generating that address automatically. I would check their documentation for how they generate return-path (envelope sender) addresses, and either override the sender address (with just sales#example.com), or configure handling of those VERP addresses on your own inbound mail server.
Here is a mailgun explanation
This error occurs due to what is termed Sender Address Verification (SAV). During SAV, an email server performs an MX lookup upon the domain (example.com) listed within the message envelope's Mail-From field. SAV typically rejects the message if,
the sender's (in this case, Mailgun's) MX records are not configured for that domain AND
the domain of the message envelope's Mail-From field does not match the domain of the message header's From field.
https://help.mailgun.com/hc/en-us/articles/360011804533-Sender-Verification-Error
The problem started suddenly. I have a problem that I can not solve when a random address send email to my domain martizi.com:
Technical details of permanent failure: Google tried to deliver your
message, but it was rejected by the server for the recipient domain
martizi.com by feedback-smtp.us-west-2.amazonses.com.
The error that the other server returned was: 550 Mailbox does not
exist!"
I use SES only to send email, just that. I want to be clear about the problem I'm having:
Use SES only to send email.
I have a corporate email that is provided by another company (here I can not receive the emails)
In my domain I have another MX address that is from the company email. Sometimes when someone tries to send email to some box # martizi.com, it returns with the error shown above.
I've seen a solution to this problem: Adding email from domains
SES panel> Domains> Mail From Domains> ...
After this he gives me an mx record to put in my domain, I put it, however it stays PENDING VERIFY and after 72 hours, it fails. I've done this twice and it does not check. Is this the solution?
TKS!
Either you are receiving email for martizi.com using SES, or you aren't.
You say that you aren't. This means you should not have this entry in DNS.
martizi.com. 3600 IN MX 10 feedback-smtp.us-west-2.amazonses.com.
With that entry, you're telling the world that feedback-smtp.us-west-2.amazonses.com. is one possible server (of several) that will accept incoming email addressed to martizi.com. That isn't the case, so the existence of this is a misconfiguration. Remove this entry.
I use Amazon SES to delivery mail to mobile devide Japanese such as ****#docomo.ne.jp, ******#softbank.ne.jp. But I always get an error.
Example:
An error occurred while trying to deliver the mail to the following recipients:
******#docomo.ne.jp
Final-Recipient: rfc822; ******#docomo.ne.jp
Action: failed
Diagnostic-Code: smtp; 550 Unknown user ******#docomo.ne.jp
Status: 5.3.0
in my opinion, your mail domain is not supported in sending email through third party apps such as SES (or maybe some settings in your mail is blocking it).
i have tried to send mail from Yahoo and its not working. then i tried to send it via Gmail and send it to that Gmail account itself. it works like charm.
so my solution is: you better try another mail domain in this problem.
It turns out that a large percent of the bounced mail that SES
forwards back isn't actually 100% readable by Gmail.
If this is your case, you can find the actual cause inside the *eml download file.
See more at https://forums.aws.amazon.com/thread.jspa?threadID=324457
In my case was related to the suppression list for my AWS account
In my case, I verified the email & getting the issue as in the question.
I can able deliver the mail After I verified the domain.
I think No verification required for non-business domains like (Gmail, Outlook, etc..) & custom domain requires verification.
Had issues with sending with #yahoo.com domain myself and this post helped me confirm my suspicions. Used a #gmail.com domain (with no custom profile settings) and it worked first try.