http://james.apache.org/server/3/feature-persistence.html
The middle-term goal is to merge the store with the mailbox persistence.
Once done, all mailbox implementation will get the benefits. To do this,
you don't have to code on the hbase mailbox level, but on the server level.
On 24/10/13 20:14, Patrick Sauts wrote:
Thank you Matthieu.
Looking into the hbase implementation: it does domains list, users,
mailboxes, RecipientRewrite, but not mail repository. In fact I'm using
their code to add mail repository feature.
I can see you're french "Le mercredi 23 octobre 2013 à 13:26 -0700,
Patrick Sauts a écrit :" ;) So am I
According to the code: mail repository store what can't be sent. It is
referred to in the mailet. Depending on mailetcontainer.conf configuration
it can store relayed-denied, spams, errors, maybe hard bounces etcŠ
So it's not really a mail box.
On 10/24/13 12:24 AM, "Matthieu Baechler" <[email protected]>
wrote:
Hi Patrick,
I'm quite new to James too, but I think I can answer some of your
questions. See below.
Le mercredi 23 octobre 2013 à 13:26 -0700, Patrick Sauts a écrit :
Hi,
I'm new with James and I have a fez questions.
What is the exact purpose of the mail repository ?
It's a store for messages and mailboxes. It seems to be very close to
IMAP semantic.
I'm currently writing an implementation of the mail repository for
hbase, is
it of any use ?
There's already one in
http://svn.apache.org/repos/asf/james/mailbox/trunk/hbase
Where do hard bounces are stored ?
Thank you for your answers.
Patrick Sauts
--
Matthieu Baechler <[email protected]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
