<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">msgKey is used as a key in the
nsIMsgDatabase to get the msg hdr for a particular key, so yes,
it's still used in all sorts of places in the code, but should not
be used as the offset into the berkeley mailbox. If it were,
maildir support would not work at all, instead of only kinda
working.<br>
<br>
- David<br>
<br>
On 01/17/2013 10:59 AM, Kent James wrote:<br>
</div>
<blockquote cite="mid:50F84A1E.2070809@caspia.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 1/17/2013 7:29 AM, David Bienvenu
wrote:<br>
</div>
<blockquote cite="mid:50F818E2.5070501@davidbienvenu.org"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 1/16/2013 2:16 PM, Kent James
wrote:<br>
</div>
<blockquote cite="mid:50F726D4.4070204@caspia.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
I was looking today at trying to fix the relatively simple bug
793865 "<span id="summary_alias_container"><span
id="short_desc_nonedit_display">nsIMsgParseMailMsgState.envelopePos
must be 64bits to support large mbox folders"</span></span>,
figuring that was one needed step on a relatively small path
to support >4GB mbox files in local folders. But as I
looked into it, we have never resolved the issue of a 32 bit
nsMsgKey, which also equals the message offset in local
folders. It is a far from trivial issue to make progress on
that.<br>
</blockquote>
There's a msg hdr property called something like
"message-offset" that's used instead of the msgKey as the offset
into the local folder, by the berkeley mailbox store. The msgKey
is used for backwards compatibility if there is no
message-offset. Are you saying the message-offset is never used,
or sometimes not used?<br>
<br>
- David<br>
</blockquote>
What I am saying is that the 32 bit nsMsgKey which equals the
offset in the case of local mbox folders, is still used in way too
many places as a way to access the particular message in a folder.<br>
<br>
If I do an mxr search for nsMsgKey in mail folders, I get "Too
many hits, displaying the first 1000" I don't understand how the
application is supposed to work with message-offset as an
alternative to nsMsgKey in all of those places.<br>
<br>
I would love for you to tell me that I am incorrect. But just to
pick a few examples out of over 1000:<br>
<br>
nsIMsgDBView has "selectMsgByKey(in nsMsgKey key)" which is used
in mailContextMenus.js<br>
<br>
nsMsgFilterService has the array m_searchHits which stores search
hits by their nsMsgKey value<br>
<br>
I don't understand how those are supposed to work with a big mbox
where the offset has exceeded 4GB and the message-offset needs to
be used instead.<br>
<br>
:rkent<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
tb-planning mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
<br>
</body>
</html>