Hi Matthieu,
> We somehow already analyzed that topic in the past and this is what we came
> to :
>
> 1. James is a mail server that can integrate your business logic
> 2. James is a mail framework : you can build you application and specific
> needs into James
> 3. James is a set of libraries:
Hi Benoit:
> I gave a shot at defining:
>
> - Core components, that offers services at heart of James
> - Utility components, that offers services core-components
> implementations can rely on.
> - Mailbox sub-components.
Wow, there is a lot here! It will take me some time to digest, but this
Hi David,
I gave a shot at defining:
- Core components, that offers services at heart of James
- Utility components, that offers services core-components
implementations can rely on.
- Mailbox sub-components.
Here is the result. I encourage other project members to review it.
- Did I forgot
Hi David,
Thank you for keeping up with that topic.
We somehow already analyzed that topic in the past and this is what we came
to :
1. James is a mail server that can integrate your business logic
2. James is a mail framework : you can build you application and specific
needs into James
3. Jame
