<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Maiko and all,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I’ve been running 2.0k.rc for a few days and saving telnet traces of a link with FBB and a link with BPQ. I scanned the traces with grep to find the types of problems I reported against “bleeding” and none were found. In fact I found no errors of any type. Also JNOS_LOG_INCOMING_LOCAL_PORTS seems to be working just fine. Also, expire future is no longer deleting recent BBS-forwarded messages.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>For the record, I included below my previous summary of issues I reported against “bleeding”, updated with 2.0k.rc status. Basically, all of the “bleeding” issues are closed.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>BRAVO! And thank you.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>When do you expect to release 2.0k?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Michael<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>N6MEF<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>P.S. Reminder: Just prior to “bleeding”, one of my BPQ forwarding partners complained that JNOS is still changing the case of message IDs, causing his users to get duplicate messages. But that wasn’t part of 2.0k.rc work – just a reminder.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Summary of issues reported against “bleeding”:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>Issue noted by Maiko: Default behavior of handling IAC breaks forwarding with legacy JNOS, BPQ and possibly other BBSs. <o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>2.0k.rc Status: Confirmed fixed. User has the option to default to IAC or no-IAC and methods to override either on inbound and outbound connections.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>Issue: JNOS displays inconsistent SID. <span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>2.0k.rc Status: Confirmed fixed. JNOS now displays B1F for incoming and outgoing connections (assuming configured for mbox fbb 2 and remote site also handles B1F)<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Issue: On incoming sessions (remote BBS connects to JNOS), JNOS telnet sessions hang if the remote end sends only a CR at the end of a command because JNOS waits for the LF. <o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>2.0k.rc Status: Still an issue, but with an improvement. JNOS now waits for mbox tdisc seconds, and then, instead of disconnecting, tries to continue. The real solution needs to come from FBB.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>Issue: “!” in forward.bbs only works on outbound connections. It would be preferable to turn off compression in both directions for a remote BBS that doesn’t handle it well.<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>2.0k.rc Status: As far as I know, there’s no way to selectively turn off compression for outbound sessions. Since compressed forwarding seems to be working well now with all links, I don’t currently have this need any longer.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>Issue: some error messages in nos.log do not include the connection info (<ipaddr>:<port>) or the MBOX (<callsign>) info. <o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>2.0k.rc Status: Maiko has said this is not worth fixing. The IP address and port *<b>are</b>* included. So it is possible to see which connection the message belongs to.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>Issue: JNOS sometimes quits a forwarding session prematurely. Nos.log does not display a reason.<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>2.0k.rc </span><span style='color:#1F497D'>Status: Maiko mentioned seeing this occasionally/rarely with 2.0k.rc. I haven’t seen it yet with 2.0k.rc. <o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Issue: Prior to the IAC fix, telnet with FBB binary compression (mbox fbb 2) worked for inbound BPQ to JNOS forwarding, but not work for outbound JNOS to BPQ forwarding.<b><i> </i></b> <o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>2.0k.rc Status: Confirmed fixed. Bi-directional forwarding with BPQ seems to work really well.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>