I'm using an EC2 with tomcat and jdbc with RDS with no problems. So that
shouldn't be a problem. My main concern was whether or not AWS blocks
port 25. At one time, goDaddy dedicated servers were forced to go
through a goDaddy proxy for port 25. The troll under the bridge would
only send a
If there is a JDBC driver for RDS then that is the way to go.
Am I missing something?
Cheers,
Benoit
On 05/08/2019 23:24, Jerry Malcolm wrote:
> I'm looking at moving off of my dedicated server to AWS, which means
> moving JAMES. Interesting concepts in this thread below from a year or
> so
I'm looking at moving off of my dedicated server to AWS, which means
moving JAMES. Interesting concepts in this thread below from a year or
so ago about using SES. But all I want to do is get JAMES up and
running in an AWS EC2 with an RDS with as little rip up and effort as
possible.
Hi Jeremy,
Can't AWS SES send these messages to a SMTP endpoint? This way it will
work without any further development.
That being said, I consider the feature you propose extremely
interesting, as it will provide alternatives to SMTP for applications
sending emails.
In my opinion, you would
Has anyone thought about how to possibly make use of AWS SES email
receiving to accept inbound email and get it passed along into James?
With AWS SES email receiving you can have it save the actual message to
an S3 bucket and then fire off an SNS topic or Lambda function so the
question would
