Amazon gives 'Delivery Status Notification (Failure)'.
Important information:
the gsuite recipient didn't exist when the first 5-ish emails where sent.
The gsuite destination domain is mine, we're using ses to do automated mailings to our own students. Some users didn't get created automatically but were targeted by SES regardless.
However, even once the recipient is created, the problem remains. Same error.
Sending to recipient+blabla#gsuite works. So I'm assuming SES decides not to send to recipients that failed too many times?
If this is the case, is there a way to tell SES to retry anyway?
And no, I didn't ask amazon, apparently you need to pay for a support subscription before they're willing to help...
Thanks in advance,
Wim
Update:
There is also an account level suppression list ( [https://docs.aws.amazon.com/ses/latest/DeveloperGuide/sending-email-suppression-list.html] ). I checked the 'global' suppression list before, which didn't help.
Why all of this information is this hard to find is beyond me. Or maybe it's just me '-)
Extra note for people fighting with aws cli: before you can list the suppressed addresses or remove them you first have to 'turn on' the management of the list:
aws sesv2 put-account-suppression-attributes --suppressed-reasons BOUNCE COMPLAINT
Hope this helps someone else...
Related
We have a client account of Amazon seller central. We need to pull campaign performance data from this account. With Amazon Advertising API we can pull this report.
Here are the documentation links:
https://images-na.ssl-images-amazon.com/images/G/01/AdProductsWebsite/downloads/Amazon_Advertising_API_Getting_Started_Guide.TTH.pdf
https://images-na.ssl-images-amazon.com/images/G/01/AdProductsWebsite/downloads/Amazon_Advertising_API_Reference.TTH.pdf
I followed the procedure in Getting Started Guide
1) Created a developer account(Login with Amazon)
2) completed the sign up form as specified in second step.
I am not sure what to do next as I did not receive any reply from amazon regarding this. Does anyone faced similar issue before?
Thanks.
It takes two or three days from Amazon to reply in most case and as they are getting high volume of application it might be possible that they have rejected it so try more then once. And try to give some information to use in the comment section.
In addition, a business registration in either NA or EU is required before they can grant permission to the Advertising API.
After all this verification they can allow access.
Hope this help to you.
Thanks,
James
If you have already received the onboarding e-mail, and you are sure that you are sending the correct API communications yet you are getting bad scope errors, then you are not yet White Listed so your requests are all rejected.
For me and many others I found while googling for hours to find the answer, this problem was due to not yet signing a license agreement which is in a very easy to overlook link hidden in a paragraph of the e-mail which starts: "Before you can register your application, you need to agree to the Amazon Advertising API License Agreement" Hit that link and accept the agreement to become white listed.
As a last resort if the above doesn't work, Amazon support had given me a direct e-mail to LWA and you can contact their support: lwa-support at amazon com.
I am currently working on a Chrome Extension that uses the Gmail API to sync emails.
As I am testing, refreshing, changing code etc, I often get a message that Google has detected Unusual Activity from my IP address, causing the entire office to have to enter CAPTCHAS to do any Google searches.
Today I actually had my test email account locked for one hour because I was requesting email too often.
Does anyone know of a way to ask Google to whitelist a specific IP for development?
EDIT* if you are going to downvote my question can you at least explain why? I would like to be a good netizen but if you dont tell me what I am doing wrong you are part of the problem, not part of the solution.
As Google documents in their help article: "...we notify you about unusual account activity, such as sign-ins or password changes from unfamiliar locations and devices. You can review this activity and confirm whether or not you actually took the action."
https://support.google.com/accounts/answer/1144110?hl=en
You might also check this article about "How to Turn Off a Gmail IP Address Tracker" at http://smallbusiness.chron.com/turn-off-gmail-ip-address-tracker-51241.html.
I'm getting returned email in my indox that I nerver sent before,How Can I use Cpanel to stop it, my inbox alway filled up.
I read this article
http://www.werockyourweb.com/stop-spoof-email
But it seen doesn't work for me. Thank!
It seem some email system block my email address, it look like
This message was created automatically by mail delivery software.
A message that you sent has not yet been delivered to one or more of its
recipients after more than 24 hours on the queue
Please let us know a sample header of the similar mail from queue
Make sure that the domain engaged in the process is having a valid SPF(TXT) record.
SPF
Spoofing can be done in many ways like if you have any form which may have bug in it and causing spamming from it .. or many any of your signup process form has bug which allows spamming over it
if its clear spoofing then yes SPF and DKIM will help to reduce it.
That's correct! Adding DKIM and SPF should help to reduce the spoof emails. If you will paste the headers here, we can identify the real cause of it. You will find it from the returned email as well from the server logs.
While the SES dashboard shows aggregated statistics about the bounce rate of emails sent through the service, I do not see a way of retrieving the individual addresses that bounced. Is this possible? Our situation is that the 'from' address we had set in certain emails was incorrect and resolved to a non existant mailbox on our (verfied sender) domain, so anything SES would have forwarded to the from address is likely gone.
Use the Amazon SNS (simple notification service), and then you can add your email address - or Amazon SQS service for holding a log of all bounces/complaints.
The answer is no, they are gone. Lesson: make sure you from address is valid (good practice obviously) and goes to a mailbox that resolves (and/or set up and process a SQS queue for them to go to)
I had the same problem. The SES report didn't show enough details for the accruing bounce error. I modified the sesreport.zip, where the deliveries, from-emails/source-emails, and the subject column are added and are included in the report.
You can find my modification here:
https://github.com/Morning-Train/AWS-SES-Report
I hope my answer helps you with your problem.
Problem Background:
I have a 35K+ user members and growing fast. I am planning to migrate to Amazon SES service. Amazon SES has a criteria to reduce the quota or even terminate service based on bounce-back emails.
I send promotional emails to my members. But the fear is that there are email address which are no longer exists so a fair possibility that Amazon SES notice me and take action to reduce or terminate my service. I need to make sure I have valid email address which do not disturb SES.
Possible Solution:
To cope this problem I am planning to do the following procedure for each email address;
Step1. Collect the MX record for the email domain.
Step2. telnet to that MX domain
Step3. Verify email address with the following pattern
EHLO my_domain_name
MAIL FROM:<my_valid_email#my_domain_name>
RCPT TO:<email_to_verify#my_user_email_domain>
I will verify the response after each command trigger such as email is valid if I receive 250 status after RCPT command
Now what are the possible precautions I should care about to be not marked as SPAM or rejected by the remote server???
I guess you have seen this question here: How to check if an email address exists without sending an email? ? That talks a bit about the disadvantages.
I am no expert but I suspect that it is going to be pretty hard to guarantee that someone won't blacklist you at some point or that you get 100% accurate results from this, or any other method for that matter.
For your scenario though, maybe that does not matter too much - just try to do the check infrequently so that you reduce the number of guaranteed bounce backs and if you send only a few that get bounced back it won't matter too much. On top of that you can have your own system that handles a bounce back and makes sure you do not re-send to that email again.
Doing all of that may be just "good enough" to work.
You may get very different answers from what you expect. Many (most?) e-mail systems set up to prevent spam won't give away user information just like that. My own server, for example, will say 250 OK for every address on my domains, even if those addresses are in fact non-existing.
What you should do is have a system which reads those bounce e-mails and remove unused addresses after a number of bounces. A good way of doing that is having different sender addresses for each message (or at least for each recipient), making it easy to connect bounce messages with their intended recipients. This technique is sometimes called Variable envelope return path.