Hello,
We currently only use AWS S3 (and API-compatible services) only as blob
store (and alternative to Cassandra and Swift) to store messages.
Regarding AWS SES:
* It is not design to our use case (in my understanding it's
principally for sending campaigns, while we are developing a general
purpose email service)
* It would imply to redevelop a lot of things (integration with AWS
Queues, reprocessing messages, we are currently doing things from
protocol interactions)
Anyway, if we had to be more tightly coupled with AWS, it would be a
great opportunity to be more serverless, it would help us to have a
better scaling management.
Regards.
Le 23/03/2019 à 18:46, Jeremy T. Bouse a écrit :
I have not had a chance to take a deep look at the individual patches
this included, but just reading the names is this something that could
potentially be used with AWS SES Mail receiving and storage to S3 or is
this simply using S3 to behind JAMES to store the received mail?
On 3/22/2019 12:18 PM, rouaz...@apache.org wrote:
This is an automated email from the ASF dual-hosted git repository.
rouazana pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git.
from 9720338 Post for MIME4J 0.8.3 release
new 4d82b40 JAMES-2671 Share AWS S3 configuration
new b028cd4 JAMES-2671 Add content length in save BlobStore API
new 775d84f JAMES-2671 Calculate the length of encrypted content
new fa24a09 JAMES-2671 Introduce AWS S3 blob store implementation
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
