<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>On Fri, Jan 22, 2016, at 02:50 AM, Jim wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><div><div><div>On Thu, Jan 21, 2016 at 2:18 PM, Joshua Cranmer 🐧 <span dir="ltr"><<a href="mailto:pidgeot18@gmail.com">pidgeot18@gmail.com</a>></span> wrote:<br></div>
<blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;">At present, Thunderbird already uses two JS protocol libraries: JSMime and ical.js. I've also prepared a SASL library and I've poked away at an NNTP library that I want to try testing (to replace nsNNTPProtocol eventually) sometime this year; I've also poked a little bit at the <a href="http://whiteout.io">whiteout.io</a> (now emailjs) libraries.<br></blockquote><div> </div>
<div>I'd be especially interested in the NNTP library so we could finally enable Gloda on NNTP. I seem to recall the issue being somewhere in nsNNTPProtocol (or maybe a related class), and no one actually knowing quite how to fix it. <br></div>
</div>
</div>
</div>
</blockquote><div> </div>
<div>I think the main stumbling block was propagating the URI flag to libmime that made gloda's custom MIME emitter stuff work. My initial attempt broke NNTP downloads and I ran out of time to investigate. It's possible to address this in the C++ code by tracing down the various URI flag paths and then adding the appropriate unit tests when fixing. Besides telling gloda to stop ignoriong NNTP, gloda may also need to be taught about when it's appropriate to index an NNTP message if the same flags aren't used on the messages and folders as they are for IMAP for indicating that the message will be fully synchronized but isn't yet.<br></div>
<div> </div>
<div>Of course, if the pure JS implementation is coming imminently, then that's probably the better time to do gloda hookup.<br></div>
<div> </div>
<div>Andrew<br></div>
</body>
</html>