Does anyone came across with this error message when sending mail in Laravel, is there a way to solve this?
Swift_TransportException in AbstractSmtpTransport.php line 383:
Expected response code 250 but got code "554", with message "554 Message rejected: Email address is not verified.
"
I did verified the email addresses and its been "verified" but still came across this error..
Laravel is working fine. You are getting an error message from the AWS mail server.
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html
You are trying to send email from an email address or domain that you have not verified with Amazon SES. If your account is still in the sandbox, you also need to verify the recipient address. For more information, see Verifying Email Addresses in Amazon SES.
Note that Amazon SES has endpoints in multiple AWS regions, and email address verification status is separate for each AWS region. You must complete the verification process for each sender in the AWS region(s) you want to use. For information about using Amazon SES in multiple AWS regions, see Regions and Amazon SES.
Make special note of that second paragraph. You may need to verify the email for the specific region you are trying to contact, or you need to change your contact address to the correct region.
For breif information refer below link
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html
Related
I am using Office 365 setting for sending my project's promotional email marketing. My mail sender email address is registered with office365 and I used SMPT settings with office365. When I send email with fewer recipient's email addresses there are no error. But when I try to send email to all my customer more than 3000 recipients, I got this error.
Error screen
I think you are hitting the rate limit of Exchange Limit which is 30 message per minute. For more information please see this: Exchange Sending limits
By the way office 365, Gmail or other services like this are not suitable for bulk operations. Try using other services like AWS SES, Mailgun and etc.
Using a Laravel job to send email to subscribers, but suddenly all gmail.com mail is bounced back with
Reporting-MTA: dsn; e226-11.smtp-out.us-east-2.amazonses.com
Diagnostic-Code: smtp; 550-5.1.1 The email account that you tried to reach does not exist.
This is only happening with gmail.com mail. I have confirmed this with my own gmail.com account that goes thru okay from my own domain. It's only when sending thru SES smtp.
Have you checked this:
Gmail - Service Details
This should be fixed now.
"The problem with Gmail has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. Please rest assured that system reliability is a top priority at Google, and we are making continuous improvements to make our systems better. If you are still experiencing an issue, please contact us via the Google Help Center.
Affected users received a bounce notification with the error "The email account that you tried to reach does not exist" after sending an email to addresses ending in #gmail.com."
I'm working on a product for Japanese clients and am getting an error when trying to send to email addresses like ああ#ああ.blah.jp AWS SES (simple email service) rejects the email address:
Aws::SES::Errors::InvalidParameterValue (Local address contains control or whitespace)
The SES docs say that you need to use RFC 2047 encoding which I am. ActionMailer encodes these addresses automatically so what gets sent to SES looks like:
=?UTF-8?Q?=E3=83=A6=E3=83=BC=E3=82=B6=E3=83=BC=E6=83=85=E5=A0=B1=E3=83=A6=E3=83=BC=E3=82=B6=E3=83=BC=E6=83=85=E5=A0=B1=E3=83=A6=E3=83=BC=E3=82=B6=E3=83=BC=E6=83=85=E5=A0=B1=E3=83=A6=E3=83=BCsfd=E3=82=B6=E3=83=BC=E6=83=85=E5=A0=B1#sdfds.com?=
I don't understand why I'm getting the error.
Looks like it's not supported by SES yet. Documentation is confusing on this topic.
Duplicate of this question.
I realised that user email contained whitespace the the end. So I removed the whitespace and it starts working
We've been using Mandrill for years to deploy our app's signup confirmation and password reset emails. This has worked perfectly as we've had SPF and DKIM records added to the DNS configuration according to Mandrill's documentation for verifying sending domains.
However, after merging the Mandrill account with a new Mailchimp account--which is mandated by April 27th--it's requiring me to send a verification email to an address at that domain. The problem is that we don't have a mail server set up to receive emails. The domain is only used to send the "noreply#domain.com" emails.
Any ideas on how I might resolve this? Mailchimp is not giving an option to undo the merge, so effectively I have an app that users are not able to sign up for at the moment, which is problematic to say the least.
You'll want to configure at least one mailbox on that domain somehow to receive mail. That's the only way to confirm ownership of the domain.
I have made a simple contact form and use swiftmailer(with symfony2) to send and email.
Everything is fine when I'm using gmail account but on production it has to be a noreply address in website domain.
So I changed parameters to correspond this email account.
It looks like it is working a send method return true but no message is received, i checked a spam folder but it didn't get there either. Settings are 100% correct as they work in thunderbird.
Have no idea where to look for a problem. Any suggestions what should I check?
I have tried to send email with PHPMailer using same account and it worked so it seems problem is just with swiftmailer.
I'm sending emails in few more places in my project and would like to avoid changing it now but fix it instead.
After checking logs the problem was found.
Emails were rejected because I was setting From filed to email provided by user. Server was rejecting them because this address don't belong to account I was sending from.
By default the logging for swiftmailer is disabled in production. You can enable logging for swiftmailer in config.yml by adding a "logging: true" to the swiftmailer section as outlined here: http://symfony.com/doc/master/reference/configuration/swiftmailer.html#logging
Hopefully this will give you some more specific error messages to search on.