Hello Jeremy, Thanks a lot for the interest on ongoing development!
We introduced a Blob storage API that backends can use to store large blobs (storing them in Data-bases is both expensive and not efficient). This blobs API leverages has various implementation: memory (testing purposes), OpenStack Swift, Cassandra, and now S3 (the API, it can be used with Scality for example). Note that the James components needs to explicitly handle the blob store - which mailbox/cassandra server/mail-reporitory/cassandra and server/queue/rabbitmq does so far. This work has nothing to do with SES Mail. Do you have any additional questions regarding this topic? Cheers On 24/03/2019 00:46, Jeremy T. Bouse wrote: > 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, [email protected] 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: [email protected] For additional commands, e-mail: [email protected]
