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 certain number of emails each day, so emails would take
several days to arrive if the limit was reached, and they would charge
outrageous fees if you sent too many emails out. I can't afford any
situation like that. As long as AWS doesn't proxy port 25, I'm not
worried. But not surprising that goDaddy didn't widely publicize their
little proxy scam. So just a bit paranoid.... Just wondering if anybody
had first hand experience with James in AWS.
On 8/12/2019 11:39 PM, Tellier Benoit wrote:
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 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. Assuming I copy my current JAMES build to EC2, set up the
RDS, install SpamAssassin, and open the appropriate ports, are there any
gotchas lurking that I need to be aware of? (Still just getting my feet
wet with AWS....).
Somewhat off topic... what size EC2 is recommended? Do I simply start
small and creep up until the EC2 no longer pegs the meter? Anybody have
an experience with what size EC2 to select?
Thanks.
Jerry
On 6/11/2018 8:16 AM, Jeremy T. Bouse wrote:
Benoit,
Yes it can send to a SMTP endpoint but the FROM address has to be an
approved email address/domain for SES to be able to send it which means
having to modify the envelope headers. Further to that I'm looking at
the possibility of running James in containers on AWS ECS which would be
on a private subnet so it wouldn't be reachable directly without going
through a load-balancer.
On 6/11/2018 12:44 AM, Benoit Tellier wrote:
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 need to implement a new component in James
listening on AWS SNS, upon messages retrieving the mails, and then
enqueue them in James internal MailQueue.
Cheers,
Benoit Tellier
Le 11/06/2018 à 01:53, Jeremy T. Bouse a écrit :
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 really be how to trigger James to be able to process the
alert and ingest the message from S3. I've been thinking about it as a
possible email solution for myself and it seems like it should be
possible but I've not yet been able to determine if there's already an
easy method to do so or if it'll take some development to make it work.
Wanted to see if anyone else had thought about it.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
