>> Thanks Benoit, very helpful! It does lead to more questions, though. :-)
>
> The contrary would have surprised me ;-)
Thanks again! There is a lot to digest here. All this information has been
really useful.
I will try to put my thoughts together by advancing with the documentation
before I
On 22/05/2020 18:06, David Leangen wrote:
> Thanks Benoit, very helpful! It does lead to more questions, though. :-)
The contrary would have surprised me ;-)
I have been yet again quitte verbose once again, don't hesitate to raise
a warning if the signal/noise ratio gets to low...
Cheers,
>
>>
Thanks Benoit, very helpful! It does lead to more questions, though. :-)
> - **mailet** are separated in an effort to serve as a specification for...
> - **mailbox** as presented below is a storage service for the server….
> - **protocols** is an effort to provide mail protocol utility for...
> I
Hello David,
> I know you are all probably very busy, but to allow my contribution to
be useful, it would be very nice to get comments on my journey so far.
If I don’t document the “right” thing and run out of time, it would be a
wasted opportunity. :-(
100% agree with that.
Don't hesitate if yo
Hello,
> If we can reach agreement on a definition for each of these, then we can
> determine (1) how to document the concepts, and (2) if the code should be
> refactored to better reflect these concepts.
Since I am starting to run out of time, I need to press forward. So for now
since I ha
Hi,
I created the issue: https://issues.apache.org/jira/browse/JAMES-3190
> I was told [1] that James has a hexogonal architecture [2]. However, that is
> not at all apparent neither in the documentation, nor in the code itself.
> If this is truly the fundamental concept of the system design,
