I created new credentials for my Amazon SES server and it stopped sending emails. I added the user and password in the Coldfusion admin and everything seems ok on that end because the verification comes back as successful. Anyone knows what might have gone wrong?
This is the errors I'm getting my logs
"Error","scheduler-1","04/07/16","07:28:24",,"javax.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid "
Related
I updated the access key for an IAM SMTP user which was earlier used to send emails. After updating the new active key in the drupal application, email functionality stopped working. I am getting the following error from the application.
SMTP Error: Could not authenticate.
Troubleshooting the issue has led me to this
https://aws.amazon.com/premiumsupport/knowledge-center/ses-rotate-smtp-access-keys/
which mentions that if there is an access key update, it must be changed to SES SMTP format.
With the code mentioned, I generated key in a different format and added to the application but still no luck.
Have anyone come across this issue before?
I've deployed a django website with Heroku. When a user creates an account in the app, a validation email is supposed to be sent. Do do that, I'm using smtp from gmail, and in my account settings, I've activated "less secure app access".
This works perfectly fine on my local machine, but when using the deployed app, I can't get the email to be sent.
The first time, I got a security warning from google saying someone connected to my account. I said it was me and tried again. I didn't get any other security warning but it seems the app is still unable to send emails.
Please, let me know if you have any idea what the issue might be.
Thanks.
I am trying to send email from my Django application. For this, I have used Twilio SendGrid service. Though my application can send the email, it ends up in spam folder. So, I have followed this tutorial to authenticate my domain which I bought from AWS route 53. In sendgrid, the domain authentication status shows 'verified' but the emails are still sent to spam folder. I have not created any MX or TXT record in DNS setting as the tutorial says it was created automatically during domain authentication in sendgrid.
One thing I have noticed that the email still shows, 'via.sendgrid.net' message (attached an image below) with the email. Whereas it should be my authenticated domain name. I have created sendgrid account with an outlook email and using that address to send email from Django app. Is this the reason my emails are going to spam? Or can anyone please help me to find a solution for this problem? Thanks in advance.
FYI: I have done 'Single Sender Verification' in sendgrid during developing this app. But now I have deployed it in aws. I guess this feature is still working instead of 'Domain Authentication'.
i installed a discourse on AWS bitnami edu3d.co. I did the following things but still can't send the login verification email.
config the discourse by this instruction https://docs.bitnami.com/bch/apps/discourse/configuration/configure-smtp/
in AWS, request email sending limits
in AWS, verify my email identity,
in AWS, send test email (it is correct)
create my credential
checked spam boxes (no email)
Thank you!
The problem is solved. I guess problem is that I set the username and password wrongly.
smtp_address = ''
smtp_port = 587
smtp_domain = 'edu3d.co'
smtp_user_name = ''
smtp_password = ''
smtp_enable_start_tls = true
smtp_authentication = login
If you have problem in setting smtp for the discourse installed on AWS EC2 bitnami. You can do the following checks.
1) check whether your VM instance can connect the smtp server (test if smtp_address and smtp_port are correct)
I found 25 is not responding and 465 sometimes broke too, 587 works well.
2) check whether your username and password set correctly.
AWS provides this instruction https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-smtp-client-command-line.html
How I find the problem
I really can't figure out why the smtp setting is 'correct' but i just can't receive the email. So I changed to gmail, the setting is a bit easier than AWS SES. After change, I received the email immediately but it says the login method is not secure so Google blocked it. This proves the smtp setting is working. And according to previous test, my VM instance can connect to the smtp server. So there should have something wrong in the smtp setting.
I go to AWS SES, intending to check the my credential. But I can only create a new one. So I did, then I found I misunderstood the username and password. After change, the email is working. Great!
The following instruction is very helpful!
https://docs.bitnami.com/bch/apps/discourse/configuration/configure-smtp/
I have an Web application that require users to verify their email account after registration. It works when we run it locally and current server.
However when we migrate it to the a staging server, the verification brings the below error.
POST http://www.XXXXXXXXX.org/api/account/verify 403 (Forbidden)
Can i ask if anyone have any idea on this?
Thank you!
Jo