[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-dev
Subject:    [jira] [Commented] (JAMES-729) Store the emails in  Amazon S3
From:       "Jeremy T. Bouse (JIRA)" <server-dev () james ! apache ! org>
Date:       2012-08-31 13:58:07
Message-ID: 972158599.22128.1346421488051.JavaMail.jiratomcat () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/JAMES-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445939#comment-13445939 \
] 

Jeremy T. Bouse commented on JAMES-729:
---------------------------------------

Yeah I was think that using a DB table for holding the metadata while S3 to hold the \
actual message would be the best solution. Sort of similar to dbfile just using S3 \
instead of local filesystem. I haven't looked into it yet much yet as I'm currently \
working on LDAP. After LDAP I'll decide whether to look into this or my Enkive \
archive mailet.  
> Store the emails in  Amazon S3
> ------------------------------
> 
> Key: JAMES-729
> URL: https://issues.apache.org/jira/browse/JAMES-729
> Project: JAMES Server
> Issue Type: Improvement
> Components: MailStore & MailRepository
> Reporter: im-james
> 
> I would be great if James could store the emails in Amazon S3. 
> There would be some advantages to this setup.
> 1) once the email is on S3, the email is safe and will not be lost.
> 2) the email is available from anywhere. 
> In the case you have a lot of mail traffic, you can have many James instances and \
> all of them will have access to the same store, so any of them will be able to \
> fetch the email. S3 has 2 apis: SOAP and REST.  (I prefer REST because it is \
> simpler to use).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]