I'm wrote an java application that send Gmail SMTP messages from AWS EC2 Ubuntu, the problem is that google blocks any connection not authorized, Google delivery a page, to access from a browser, that enable access to Gmail from same IP of page access, but in EC2 Ubuntu there is no browser to SSH character environment. There are some way to set server ip to some Gmail permition list?
Just use AWS simple mail service instead.
Related
Setup: Node.js app running on EC2 Linux box. No outbound rules currently defined
Goal: To allow Node.js app to send email using AWS SES (via aws-sdk).
Issue: Cannot send email(running into timeout errors)
How should I go about setting up the EC2 security to only allow sending of emails via AWS SES?
Please refer troubleshoot SMTP timeout issues with Amazon SES document from AWS.
I'm running a wordpress multisite install on a linux AWS ec2 server.
We're having some issues with emails sent via sendmail being blocked by the end user. The issue is generally not a problem with personal email accounts, more so with larger organisations with nasty firewalls.
At the moment, the server doesn't have a public domain name... So I'm not sure how to configure my php.ini file's sendmail_from
Any help would be great!
I'm running a nodejs server hosted on AWS (Ireland) and using emailjs to send emails. The email account I'm using is a gmail account and I can send emails from my local machine without any issues, but the emails fail to send from the production server.
Outbound firewall is set to allow all traffic on all ports.
The error message I get is "authorization.failed".
Gmail blocks IP addresses from AWS by default.
After logging into gmail locally, visit the following URL.
https://accounts.google.com/DisplayUnlockCaptcha
Once you verify that you want your AWS server to be able to access your gmail account then your server will be whitelisted.
I have a site hosted on Windows Azure and currently I am using SendGrid to send emails. However, we have Mimecast as our email provider and it is marking all emails received from SendGrid as spam.
Is there a way to use Mimecast as the SMTP Relay service from my Windows Azure application?
Well,
Azure as such does not apply any restriction on the outgoing traffic (beside some bandwidth throttling based on the Size of the VM you are running on, but this quite generous). So in practice you can use any SMTP relay service.
Whether you can use Mimecast specifically, you shall turn to Mimecast support or products page. But there is nothing in Azure that would stop you from using this or that service (any service).
And Yes, you can use System.Net.Mail.SmtpClient or any other Smtp Client library to talk to external SMTP Service. Whether that external SMTP Service will accept your connection or not, is not subject to any kind of Azure limitation, but sole decision of the service you chose to use.
You should raise a ticket with SendGrid so they can manage this situation. The reason SendGrid is provided is to precisely avoid your mail being marked as spam. You will be unlikely to see any successful mail delivery if you route SMTP traffic directly from an Azure host to a receiving SMTP server.
I have an EC2 instance running the standard LAMP stack (Linux, Apache, MySQL, PHP). I am using PHP to send out a few e-mails a day (4 or 5 at the most). This is working without a hitch.
Every once in a while, I will need to debug or test some of the e-mails that are sent. To do this, I will run a particular e-mail sending script 10-20 times in succession. I noticed that some of those e-mails are never received by the listed e-mail addresses. This is sporadic and happens when the script has not been changed. I am assuming this is because EC2's built-in SMTP server is throttling my e-mails.
How do I view the logs for the SMTP server on EC2?
If your application is using your localhost as SMTP server, your logs should be in /var/log/maillog.
Note: There is a limitation from AWS for emails sent from EC2 instances:
AWS EC2 email sending limit when using third party smtp server
Amazon EC2 mail limit reached while using external smtp server to send emails