I am configuring a new Cognito User Pool. I have a verified email address which I am using, but when I try to create the user pool, I get the following error with no hint as to which parameter is invalid:
Cannot configure From email address for default email configuration (Service: AWSCognitoIdentityProviderService; Status Code: 400; Error Code: InvalidParameterException*'*
Any ideas?
I had same issue, Since I had from email address arn, I removed the from email address it worked for me.
There are two solutions here:
using SES
remove email "FROM email address" to use defaults
As mentioned in the comment above, changing to use SES seems to solve this issue. I had exactly same problem and using SES worked.
Related
I have an Amazon SES connection setup which is currently in Sandbox mode.
I have my email address, I use my real one but for this post let's call it myemail#arealdomain.com. It's verified in SES, in the email tab it says "verified" right next to it.
I have a Node app which sends the mail via Nodemailer
this.transporter = nodemailer.createTransport({
SES: new aws.SES({ region: "us-east-1" })
});
this.defaultFromAddress = 'myemail#arealdomain.com';
and then I send it with this.transporter.sendMail, with ALL email addresses being the same myemail#arealdomain.com
When I try to send an email, (both TO and FROM the same address, which is Verified on SES)
On send I get the below error
Error: MessageRejected: Email address is not verified. The following identities failed the check in region US-EAST-1: myemail#arealdomain.com
Any ideas how to fix?
update
Per the conversation below I triple confirmed both my region and email address is correct across both my code and AWS. The to and from address are the same, and is listed in AWS as "verified". I'm still having this issue and totally unsure how to proceed
update2
Sending a "Test Email" from the SES dashboard works just fine, using the same email addresses...
update3
It gets weirder! So we got out of Sandbox mode yesterday and are a normal SES account now. Same exact errors no matter what combo of to/from addresses I'm using. I'm always using a "verified" address as the FROM, and no matter the TO (even if it's also a verified address) I get the exact same error that
Error: MessageRejected: Email address is not verified. The following
identities failed the check in region US-EAST-1:
myemail#arealdomain.com
Okay so it turns out while I was running locally it was using the incorrect AWS credentials (for an other project). Still unsure how to fix but that's the actual problem nothing wrong with SES
We had a similar problem today, and after checking all the credentials and the SES dashboard, the answer turned out to be a case-sensitivity issue in the left-hand side of the address. The verified email was:
noreply#company.com
but I was setting
NoReply#company.com
in the header, and that caused the verification to fail.
Faced the same issue today. Wasted couple of hours on this.
SESv2Client library for node.js uses the default aws-cli config when the credentials config is not passed propery.
const ses = new SESv2Client({
region: 'region-code',
credentials: {
accessKeyId: 'ABC',
secretAccessKey: 'xyz'
}
});
I have a bugzilla 4.4.2 installation. I want to use the gmail smtp service to send email from my application. I have applied these blogs
http://www.dawood.in/bugzilla-alerts-using-gmail/
http://prasadlinuxblog.wordpress.com/2014/02/26/975/
Applied the patches mentioned there. I configured the mta parameters in Bugzilla admin section with my gmail user name and password. Note that, I am not using two step verification in google account. So after all these, the application fails with an Authentication Error. It says the following message
There was an error sending mail from 'myemailaddress#gmail.com' to 'receiver#gmail.com': Could't set FROM: 530 5.5.1 Authentication Required. Learn more at at lib/Email/Send/SMTP/TLS.pm line 49
Cant really figure out whats going wrong here. I found one similar question https://stackoverflow.com/a/8533805/3692283 but I am already following the solution mentioned there.
Check whether the email entered at the SMTP user is still valid. If the password is no longer valid, then it cannot be chosen as the SMTP user name.
The SMTP password is the email's password.
In my organization, some users don't have an e-mail address. At the e-mail field in ActiveDirectory, they have a fake (malformed) e-mail address, something like "user.name#xx".
When these users try to login into Gitlab, they get the following error:
'Could not authorize you from LDAP because "Validation failed: email is invalid, email is invalid".'
Is there any configuration to ignore email adress checking with LDAP?
The issue 6230 has been tracking this:
The mail validation on user model is performed by validation here: app/models/user.rb.
I think you can configure your own regexp here: config/initializers/devise.rb.
However, the official statement is:
Disabling validation is not something that will be done on GitLab side. This can lead to inconsistencies in the database and could cause a plethora of issues.
I suggest you :
either fix your LDAP
or have allow_username_or_email_login setting enabled: https://github.com/gitlabhq/gitlabhq/blob/master/config/gitlab.yml.example#L130
This is issue is a support question so I will point you to the contributing guide and close it.
Not directly with GitLab itself, because that error message is the result of an omniauth callback: see config/locales/devise.en.yml:
omniauth_callbacks:
success: 'Successfully authorized from %{kind} account.'
failure: 'Could not authorize you from %{kind} because "%{reason}".'
Yet, the Rodrigo Carvalho reports in the comments:
I actually discovered this is a Gitlab behaviour.
I changed the "/lib/gitlab/oauth/user.rb" (Gitlab code) to append a ".com" in the end of the invalid email address and it worked.
I recently set up my amazon ses. and I have a verified DKIM and have published the SPF and senderid record from my DNS. When I send a sample mail from management console of SES the mail landed in the SPAM of hotmail.infact it is a verified sender as I am still in sandbox. I could not get much help from aws team either..
any help would be greatly appreciated
thanks
I have seen hotmail put an email in the spam folder when the html is malformed. Make sure your html is valid, and there are no unclosed tags.
This is not Amazon SES issue. You have to check with Microsoft why their Hotmail spam filters classify your domain email as junk. Note that they might also be looking at the content of the message and classify it as junk based not on the sender, but on what the body contains.
Amazon also has intermittent issues with blacklisting. It would be wise to check the SES forums to make sure that all is well with the SES IP you are sending from and that your email itself is not on a blacklist
Check the SES forums here
https://forums.aws.amazon.com/forum.jspa?forumID=90
I have a contact page form that is setup to send an email to a Gmail account. Only problem is it won't send. I believe I have narrowed the error down to my settings inside of the initializers directory.
These are my current settings for trying to setup a standard gmail account to send mail:
Could it be that my domain setting is wrong or should I be typing in myemail#gmail.com for :user_name? This is the first time I have used ActionMailer so I don't really know what I am doing. Can somebody please help me out!? Thanks!
If you are using the development environment, change the development.rb to raise delivery errors, with
config.action_mailer.raise_delivery_errors = true
Also, the problem might be that :user_name should be the entire email address (myemail#gmail.com), that's how Gmail authenticates users.
domain does not necessarily have to be "gmail.com". You can put your own domain here is you wish.
You also need to specify :from. I found that if you deliver your email with .deliver you do not get an exception for the errors. Try .deliver! instead. With .deliver! you get details about what is wrong.