-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authorized Recipients #5
Comments
Can you try with the same sender email address that you tried to create an account with the mailgun. I had this issue and it was resolved when I made that change. |
or you can add a test email address in your mailgun sanbox dashboard - see https://help.mailgun.com/hc/en-us/articles/217531258-Authorized-Recipients |
updated the readme FAQ with this issue |
@theoomoregbee Getting the below error while trying to run the script. Please check and suggest what is wrong and needs to be fixed to make it work:- I have update the .env file and below values i changed as per my mailgun account:- Also, please confirm that for the MAILGUN_USERNAME we need to add our email with which we signedup for mailgun and for MAILGUN_API_KEY we need to add pubkey value from our accounts API Keys section, as i didn't find any value starting only with key-xxxxxx |
Hello, i am having this error when i run 'npm start': Error: Parameter "key" is required My env is setting as: |
I have the same error here. There are 3 types of API_KEY: 1) Mailgun API keys, for example, 8fff941a7a43bcc4c45517a4a0204f11-d010bdaf-47f054a6 ; 2) Last Segments of the Mailgun API Key, for example, d010bdaf-47f054a6 ; 3) Verification public key: begins with pubkey-xxxx. It only works with their deprecated v3 validations endpoint. If users want to use Validations via API, please use the v4 validations endpoint and create a Mailgun API key above. How do I resolve this error? |
"status: 403,
details: 'Domain sandboxe1164ceef2a340a89c348279b0dde46b.mailgun.org is not allowed to send: Sandbox subdomains are for test purposes only. Please add your own domain or add the address to authorized recipients in Account Settings.' "
I added the authorized recipient e-mail address and got it approved, but it still gave the same error.
The text was updated successfully, but these errors were encountered: