What does the following Mailgun error response mean when one tries to send a message?
Status: 400
Body: {"message": "Sandbox subdomains are for test purposes only. Please add your own domain or add the address to authorized recipients in Account Settings."}
Have you set up some authorized recipients for the sandbox domain?
https://documentation.mailgun.com/en/latest/faqs.html#how-do-i-pick-a-domain-name-for-my-mailgun-account
A sandbox subdomain of mailgun.org. Example: sandboxXX.mailgun.org.
This option allows for quick testing, without having to setup DNS
entries. This domain is provisioned automatically with every new
account. But you can send only to authorized recipients.
in 2019 is:
Click to your domain, and you see at the right the Authorized Recepients box
i have faced this problems.
if testing with sandbox, should be add the authorized recipients.
then copy the sandbox name as a domain.
Thanks you.
Log in to your Mailgun account, go to the log section. There you should see a log entry for the failed attempt to delivery that email. Click on it to see all details. it should display the full error message as well as additional information.
However, most likely you forgot to add that specific email address to the list of authorized email addresses.
Side note: after adding yourself to authorized recipients, you also need to verify your email address. I almost disregarded the following email as commercial, but in fact I kept getting the error until I agreed:
Hi there,
Mailgun account "[...]" provided your address to test their integration with Mailgun.
Please click the link below if you agree to receive emails from their account.
I had the same problem I solved this by doing below steps.
Add an email to Authorized Recipients - Steps.
When you add from and to emails Don't add Quotation marks
Related
I cannot sign into AWS account. The AWS management console accepts password but then throws 400 error before getting to MFA. Link to Support takes me to login again, haha. I cleared cache and cookies for all of time. I tried different browsers and devices.
I had the same problem and the same unsuccessful attempts to resolve. It now appears to be fixed at least for me. Hopefully for you all as well.
According to AWS support, they said that I have two AWS accounts. That means my Amazon.com account also counts as an AWS account I guess. Both have the same email address, e.g. myemail#gmail.com. Therefore, the below StackOverflow link fixed my issue.
I just had to modify my Amazon.com email to include +amazon so if it was myemail#gmail.com, then I needed to change it to myemail+amazon#gmail.com. Do this by logging into Amazon.com, then navigate to Your Account > Login & security
Don't worry, you don't actually need to create an email for myemail+amazon#gmail.com
Seems like Amazon.com removes the +amazon and continues to treat it as myemail#gmail.com as far as I've noticed so far. You are still even allowed to log into Amazon.com with myemail#gmail.com without adding the +amazon
After doing this, I was able to log into AWS account as usual. =)
Source: https://stackoverflow.com/a/57104601
I contacted AWS support (like the OP, I had to convince them that "log in to your account to get support when you can't log in to your account" was unreasonable) and they fixed the problem for me but unfortunately provided no details on what caused it. In case anyone missed it in the comment on the question, support when you can't log in is at https://support.aws.amazon.com/#/contacts/aws-account-support .
My OAuth consent screen verification shows me this messsage
Comply with domain verification requirements
Ensure your application's domains have completed the Search Console verification process
But in my Authorized domains there domains like **.chromiumapp.org or *.extensions.allizom.org/
which ownership I cant verify.
Assume that you already verified your domain and still getting this error, try to do this:
Go to your "Google Console" > "OAuth Consent Screen" and under "Publishing status" click "Back to testing"
Now you are back in the test mode, click "publish" again
You may see some new demands to publish it, which were unknown before. You could follow these demands now.
After that, you will see "The Trust and Safety team has received your form." message.
If you can't make changes to the DNS of the domain you want to verify, you can try verifying the ownership of your domain by Verify file or html tag method. Take a look at this link for more information.
Go to your Google webmaster and make sure you can see your domain there,
If not follow the steps on the same page to verify the domain owner.
Suddenly all the emails sent through gmail api are landing with a red banner in recipients inbox as shown below.
So, I created a new OAuth ClientID in Google Cloud platform and used those credentials to provide access to my test gmail account. Then I sent emails using Gmail Api and emails are landing in inbox without any red banner which is good.
But we need to use the same old OAuth ClientID as we have so many users who provided access to it. If we change these ClientID and ClientSecret to use the new one, we need all our users to re-authorize, which we don't want to do. Can someone help why the existing OAuth Client ID is throwing this red banner in recipients mailbox?
As stated in this blog, this warning message speaks about one of the security measures taken by Google. Also from this related SO post, either your message contains a scam web page that steal users informations or the Domain/IP of your server has been used in the past for stealing personal informations. Check if IP is blacklisted on Mxtoolbox Configure Reverse DNS (Match your domain name with your IP), SPF and DKIM, Send legitimate email and everything will be fine.
I've gone through all the prereqs on Google's site.
Got and installed a SSL cert (from Let's Encrypt) on server.
Registered and verified the domain (yes, the https url) on Google Search Console (like https://example.org).
Added to the domain to my API Credential's Domain Verification.
topic='projects/myproject/subscriptions/mytopic'
sub='projecs/myproject/subscription/mysub'
client.projects().topics().create(topic=topic, body={}).execute()
client.projects().subscriptions().create(name=sub, body={'topic': topic, 'pushConfig': {'pushEndpoint': 'https://example.org/push-handler'}})
And I get back:
googleapiclient.errors.HttpError: https://pubsub.googleapis.com/v1/projects/myproject/subscriptions/mysub?alt=json returned "Invalid push endpoint given (endpoint=https://example.org/push-handler). Refer to https://cloud.google.com/pubsub/subscriber#create for more information.">
Also, I'm unable to create subscriptions from Google's Pub/Sub developer console. When I try, I get back a "Subscription cannot be added" notification. I am the full owner of this topic and project, with read and write permissions. I'm able to add pull subscriptions with no problem.
Any ideas on why? It seems like I'm not the only one hitting this.
Figured it out. I included the protocol (https://example.org) in the domain verification, instead of just example.org. It would have been nice of the domain verification tool provided some validation preventing this.
https://console.developers.google.com/apis/credentials/domainverification
I have my catch_all() set to forward("my.username#gmail.com"). I expected that any emails caught by this route would be forwarded to my email address as actual emails, but I never received them. The mailgun logs state that the message was routed, accepted, and delivered successfully.
What am I missing?
The problem ended up being gmail... I was sending my test messages from my gmail account and had the forward setup to return to my gmail. Gmail filters out loopbacks. Sending the test message from a different account yielded the expected results
You are correct, setting the catch_all and forward filters and actions does just that!
Did you set up the MX records for your domain properly? If not, that might be the issue (check Domains in the control panel)
Check the logs at https://mailgun.com/cp/log to debug the issue!
Best