quantranhong1999 commented on pull request #481:
URL: https://github.com/apache/james-project/pull/481#issuecomment-858470927


   Hi, 
   I think there are some we need to discuss about.
   About the algorithm input, based on your suggestion, JMAP specs and what was 
proposed preliminary in GSoC proposal. I suppose the guessing algorithm method:
   ```
   ThreadId guessThreadId(Username username, MessageId messageId, Message-ID 
message-id, List<References> references, Subject subject);
   ```
   Where:
   - MessageId to be the naive ThreadId for now
   - Username so we can get all emails of that user => get all header fields 
like Message-ID, In-reply-to, References, Subject => compare to already having 
Message-ID, In-reply-to, References, Subject fields.
   
   Can someone explain me about the create and saving a message process in 
James? I doubt that in the final implementation of guessing thread id 
algorithm, there should not be MessageId messageId in the params because 
MessageId only available when we created a message (so threadId also).  After 
we have threadId, we can pass it into some create message params and save it. 
After that I suppose we can use ThreadIdManager to save a trio of 
accountId(Username), MessageId, ThreadId to the ThreadId table. 
   Beside that, I have some other question (Which could be nice if you can 
answer shortly and directly to me. Otherwise I think I can read RFC5322 about 
this by my self, I'm fine.)
   - What is Message-ID meaning? The difference between Message-ID and 
MessageId? Who decided Message-ID (client/ server...)?
   - What is References header field meaning?
   - Why should we combine  In-Reply-To and References into a object?
   
   I know this is really a long discuss with many questions and I would very 
appreciate for your answers. :')
    


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to