There are some subtleties that we should consider. When copying messages within a a gmail account, we most likely don't need to copy the offline store copy of the messages. Change autosync to know the same thing so that it doesn't try to download a message we already have.ģ. And enhance the logic that actually loads the offline message to know where to look for the message.Ģ. When trying to fetch a message, enhance the "do we have a copy of this message offline" logic to know that gmail messages can be in multiple folders, and one of those folders might already have this message offline. The next step after that is to use this information to only download one copy of a message for offline use. This should be fairly similar to what you've already done, except that parsing the response is a bit harder, since it's a paren group and not an atom. For the next step, I think we want to fetch x-gm-labels as well, and store the set of those as a property for each message. If this is used, Tb's work needed in mail threading is "threading in a conversation" only.Įxcellent. (iii) Access to the Gmail thread ID: X-GM-THRIDīy X-GM-THRID, same thread as Gmail's conversation can be obtained. And if (i) is used at any Gmail Label(Gmail IMAP) folder, association to Gloda entory is possible. If (i) and (ii) is used at /All Mail, "Gloda Indexing at /All only" is possible. X-GM-LABELS, all Gmail Label added to a mail can be known, although it looks that distinction from IMAP flag(user added keyword) is slightly difficult. (i) Access to the Gmail unique message ID: X-GM-MSGIDīy X-GM-MSGID, relation between copy of mail in a Gmail IMAP folder(Gmail Label) and original mail in /All Mail can be known. Please consider using Gmail IMAP Extension of X-GM-MSGID, X-GM-THRID, X-GM-LABELS in addition to XLIST. > Access to the Gmail thread ID: X-GM-THRID > Access to the Gmail unique message ID: X-GM-MSGID Extension of the SEARCH command: X-GM-RAW
0 Comments
Leave a Reply. |