I am moving a client from an AWS installation controlled by a 3rd party. I dont have access to the installation to get all the configuration data.
Most things are working, but one thing I am having issues with is getting SES and Email from 2 applications working. This isnt mass email distribution, it it occasional email from 2 systems that customers use.
The email comes from the following 2 systems.
SQL Server Reporting Services aka SSRS (a few reports sent out daily)
Custom ASP.NET application that uses legacy .NET SMTP API.
I have gotten to the point where I have created a domain in SES, added and verified a few email addresses for testing and have created SMTP credentials. --Have sent a test email to my email account from SES through the test tool, but the emails havent arrived--. EDIT: Test Emails from SES test tool have came through.
I also went into SSRS and configured the email server. This is simply the email server, the userid, and password supplied when I created credentials. I setup a schedule for a report to run and be delivered to one of the test email addresses I verified. It doesnt arrive and when I look at the SSRS logs it seems like SSRS is having issue connecting to the SES email server. Do I have to create any special Security Group to allow the Windows Server to connect to the SES email server?
For the legacy ASP.NET application I believe I need to setup the SMTP Service on Windows Server. I have done that using the same information I used with SSRS according to the following article.
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-windows-server.html
When I try to send a test message it never comes through.
What am I missing?
Edited by: KeithF1138 on Mar 24, 2020 11:45 AM
AWS OFFICIALAktualisiert vor 3 Jahren