<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Maybe some case-sensitive examples are available as I only could 
    find an example with completely<br>
    changed bids. This was due to a bug in linBPQ version 6.0.9.31<br>
    <br>
    Bob VE3TOK<br>
    <meta http-equiv="content-type" content="text/html;
      charset=windows-1252">
    <div class="msg-title-bar" id="yui_3_15_0_1_1423448187222_2467"
      style="margin: 0px; padding: 10px 10px 7px; border-left-width:
      1px; border-left-style: solid; border-left-color: rgb(226, 226,
      230); border-right-width: 1px; border-right-style: solid;
      border-right-color: rgb(226, 226, 230); height: inherit; color:
      rgb(63, 63, 63); font-family: 'Helvetica Neue', Helvetica, Arial,
      san-serif, Roboto; font-size: 13px; font-style: normal;
      font-variant: normal; font-weight: normal; letter-spacing: normal;
      line-height: 16.25px; orphans: auto; text-align: start;
      text-indent: 0px; text-transform: none; white-space: normal;
      widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      background-color: rgb(250, 250, 252);">
      <div class="msg-title" id="yui_3_15_0_1_1423448187222_2469"
        style="margin: 0px; padding: 0px; line-height: 28px; max-width:
        90%; display: inline-block;">
        <h2 id="yg-msg-subject" class="fs-14 fw-600 sprint" alt="URGENT
          - Duplicate Bulls in linbpq version 6.0.9.31 and BPQMal
          1.4.62.2-6" data-subject="URGENT - Duplicate Bulls in linbpq
          version 6.0.9.31 and BPQMal 1.4.62.2-6" style="margin: 0px;
          padding: 0px; font-size: 14px; font-weight: 600; overflow:
          hidden; white-space: nowrap; text-overflow: ellipsis;
          text-align: left; cursor: pointer;"><span
            id="yui_3_15_0_1_1423448187222_2470" style="padding-right:
            10px; font-weight: normal;">16169</span>URGENT - Duplicate
          Bulls in linbpq version 6.0.9.31 and BPQMal 1.4.62.2-6</h2>
      </div>
      <div class="msg-readview-id" style="margin: 0px; padding: 0px;
        line-height: 28px; max-width: 10%; float: right;"><span
          class="msg-expand" aria-label="Expand Messages" role="button"
          tabindex="0" data-action="msg-expand"><i class="yg-sprite tip
            expand-right" data-tooltip="Expand Messages" pos="bottom"
            role="presentation" style="vertical-align: text-bottom;
            width: 26px; height: 20px; float: right; font-size: 0px
            !important; margin: 6px 0px auto 4px; cursor: pointer;
            background-image:
            url(https://s1.yimg.com/dh/ap/groups/sprite43.png);
            background-color: transparent; background-position: -74px
            -593px; background-repeat: no-repeat;">Expand Messages</i></span></div>
    </div>
    <ul class="msg-list-container"
data-sender-status="EvBzNJ5pmSO_BQMzxxvKJclcBY3ek5-w6ixb1Jbp8mGIcAmBlRDSJgSfbBvOmwl8Cj1SZ7ZAZE2Xj2YifBRTVMYH9JYcG3sZwtu7PmkVPg"
      data-default-email="BPQ32@{{emailDomain}}"
      data-attachment-status="1" data-reply-to="LIST"
      data-poll-enabled="1" id="yui_3_15_0_1_1423448187222_2402"
      style="margin: 0px; padding: 0px; list-style: none; color: rgb(63,
      63, 63); font-family: 'Helvetica Neue', Helvetica, Arial,
      san-serif, Roboto; font-size: 13px; font-style: normal;
      font-variant: normal; font-weight: normal; letter-spacing: normal;
      line-height: 16.25px; orphans: auto; text-align: start;
      text-indent: 0px; text-transform: none; white-space: normal;
      widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      background-color: rgb(250, 250, 252);">
      <li class="card clrfix yg-msg-read-container" data-msgid="16169"
        data-uid="409424114" data-email="bpq32@{{emailDomain}}"
data-reply-to-header="{"messageIdInHeader":"PDc1RDcwMDYyMkY1RTQ1RTJBMDMwRURCMTAyQ0ZCQTZEQFpvbz4=","inReplyToHeader":"PENBSnYrQWRkT0tBX1d3d3g3N3FmPWZUZmllUVI0OFF2Y3JTd3RwM1JLcWNxREJ0ND1qUUBtYWlsLmdtYWlsLmNvbT4=","referencesHeader":"PENBSnYrQWRkT0tBX1d3d3g3N3FmPWZUZmllUVI0OFF2Y3JTd3RwM1JLcWNxREJ0ND1qUUBtYWlsLmdtYWlsLmNvbT4="}"
data-sender-status="EvBzNJ5pmSO_BQMzxxvKJclcBY3ek5-w6ixb1Jbp8mGIcAmBlRDSJgSfbBvOmwl8Cj1SZ7ZAZE2Xj2YifBRTVMYH9JYcG3sZwtu7PmkVPg"
        data-sender-email="john.wiseman@..." data-content-transformed=""
        data-author="John Wiseman" data-system-message=""
        id="yui_3_15_0_1_1423448187222_2440" style="margin: 0px 0px
        20px; padding: 0px; zoom: 1; height: 417px; outline: none;
        list-style-type: none; border: 1px solid rgb(226, 226, 230);
        overflow-x: hidden; background-color: rgb(255, 255, 255);">
        <div class="wrapper" id="yui_3_15_0_1_1423448187222_2439"
          style="margin: 0px; padding: 0px; position: relative; height:
          417px; width: 673px;">
          <div class="msg-header" id="yui_3_15_0_1_1423448187222_2464"
            style="margin: 0px; padding: 0px; display: block; width:
            673px; cursor: pointer;">
            <div id="yui_3_15_0_1_1423448187222_2465" style="margin: 0px
              10px; padding: 10px 0px 5px; height: 20px; line-height:
              20px; position: relative; border-bottom-width: 1px;
              border-bottom-style: solid; border-bottom-color: rgb(226,
              226, 230);">
              <div class="author fleft fw-600"
                id="yui_3_15_0_1_1423448187222_2466" style="margin: 0px;
                padding: 0px; font-weight: 600; float: left !important;
                max-width: 50%; height: 18px; overflow: hidden;
                text-overflow: ellipsis; cursor: default; white-space:
                nowrap;">John Wiseman</div>
              <div class="tm single" style="margin: 0px; padding: 5px
                0px 0px 15px; position: absolute; top: 0px; right: 0px;
                color: rgb(153, 153, 153); background-color: rgb(255,
                255, 255);"><span class="tip" pos="bottom"
                  data-tooltip="Message sent time" style="line-height:
                  29px;">Feb 6 4:58 AM</span></div>
            </div>
          </div>
          <div class="msg-content undoreset"
            id="yui_3_15_0_1_1423448187222_2438" style="margin: 0px;
            padding: 10px; display: block; position: relative;
            word-wrap: break-word; overflow-x: auto;">
            <div id="ygrps-yiv-1619197795" style="margin: 0px; padding:
              0px;">
              <div class="ygrps-yiv-1619197795Section1"
                id="yui_3_15_0_1_1423448187222_2437" style="margin: 0px;
                padding: 0px;">
                <div id="yui_3_15_0_1_1423448187222_2436" style="margin:
                  0px; padding: 0px;">
                  <p class="ygrps-yiv-1619197795MsoNormal"
                    id="yui_3_15_0_1_1423448187222_2457" style="margin:
                    0px 0cm; padding: 0px; display: block; font-size:
                    12pt; font-family: 'Times New Roman';"><font
                      id="yui_3_15_0_1_1423448187222_2459" color="navy"
                      face="Arial" size="2"><span
                        id="yui_3_15_0_1_1423448187222_2458"
                        style="font-size: 10pt; font-family: Arial;
                        color: navy;">A version of LinBPQ which can in
                        some circumstances create a new BID for an
                        incoming message was available on dropbox from
                        around Jan 21<sup style="vertical-align:
                          text-top;">st</sup><span
                          class="Apple-converted-space"> </span>to Feb 3<sup
                          style="vertical-align: text-top;">rd</sup><span
                          class="Apple-converted-space"> </span>The
                        affected version is 6.0.9.31. If you are running
                        this version, please update as soon as possible.</span></font></p>
                  <p class="ygrps-yiv-1619197795MsoNormal"
                    id="yui_3_15_0_1_1423448187222_2456" style="margin:
                    0px 0cm; padding: 0px; display: block; font-size:
                    12pt; font-family: 'Times New Roman';"><font
                      color="navy" face="Arial" size="2"><span
                        style="font-size: 10pt; font-family: Arial;
                        color: navy;"> </span></font></p>
                  <p class="ygrps-yiv-1619197795MsoNormal"
                    id="yui_3_15_0_1_1423448187222_2435" style="margin:
                    0px 0cm; padding: 0px; display: block; font-size:
                    12pt; font-family: 'Times New Roman';"><font
                      id="yui_3_15_0_1_1423448187222_2434" color="navy"
                      face="Arial" size="2"><span
                        id="yui_3_15_0_1_1423448187222_2433"
                        style="font-size: 10pt; font-family: Arial;
                        color: navy;">The same bug could be in versions
                        of BPQMail between 1.4.62.2 and 1.4.62.6.</span></font></p>
                  <p class="ygrps-yiv-1619197795MsoNormal"
                    id="yui_3_15_0_1_1423448187222_2447" style="margin:
                    0px 0cm; padding: 0px; display: block; font-size:
                    12pt; font-family: 'Times New Roman';"><font
                      id="yui_3_15_0_1_1423448187222_2449" color="navy"
                      face="Arial" size="2"><span
                        id="yui_3_15_0_1_1423448187222_2448"
                        style="font-size: 10pt; font-family: Arial;
                        color: navy;"> </span></font></p>
                  <p class="ygrps-yiv-1619197795MsoNormal"
                    id="yui_3_15_0_1_1423448187222_2452" style="margin:
                    0px 0cm; padding: 0px; display: block; font-size:
                    12pt; font-family: 'Times New Roman';"><font
                      id="yui_3_15_0_1_1423448187222_2451" color="navy"
                      face="Arial" size="2"><span
                        id="yui_3_15_0_1_1423448187222_2450"
                        style="font-size: 10pt; font-family: Arial;
                        color: navy;">My apologies for any inconvenience
                        caused.</span></font></p>
                  <p class="ygrps-yiv-1619197795MsoNormal"
                    id="yui_3_15_0_1_1423448187222_2453" style="margin:
                    0px 0cm; padding: 0px; display: block; font-size:
                    12pt; font-family: 'Times New Roman';"><font
                      color="navy" face="Arial" size="2"><span
                        style="font-size: 10pt; font-family: Arial;
                        color: navy;"> </span></font></p>
                  <p class="ygrps-yiv-1619197795MsoNormal"
                    id="yui_3_15_0_1_1423448187222_2494" style="margin:
                    0px 0cm; padding: 0px; display: block; font-size:
                    12pt; font-family: 'Times New Roman';"><font
                      id="yui_3_15_0_1_1423448187222_2496" color="navy"
                      face="Arial" size="2"><span
                        id="yui_3_15_0_1_1423448187222_2495"
                        style="font-size: 10pt; font-family: Arial;
                        color: navy;">Just for the record, this isn’t
                        the same issue reported where the case of BIDS
                        has been changed. In this case a new BID is
                        generated from  the receiving station’s  Message
                        Number and Call.</span></font></p>
                  <p class="ygrps-yiv-1619197795MsoNormal"
                    id="yui_3_15_0_1_1423448187222_2497" style="margin:
                    0px 0cm; padding: 0px; display: block; font-size:
                    12pt; font-family: 'Times New Roman';"><font
                      color="navy" face="Arial" size="2"><span
                        style="font-size: 10pt; font-family: Arial;
                        color: navy;"> </span></font></p>
                  <p class="ygrps-yiv-1619197795MsoNormal"
                    id="yui_3_15_0_1_1423448187222_2498" style="margin:
                    0px 0cm; padding: 0px; display: block; font-size:
                    12pt; font-family: 'Times New Roman';"><font
                      color="navy" face="Arial" size="2"><span
                        style="font-size: 10pt; font-family: Arial;
                        color: navy;">73, John</span></font></p>
                  <p class="ygrps-yiv-1619197795MsoNormal"
                    id="yui_3_15_0_1_1423448187222_2499" style="margin:
                    0px 0cm; padding: 0px; display: block; font-size:
                    12pt; font-family: 'Times New Roman';"><font
                      color="navy" face="Arial" size="2"><span
                        style="font-size: 10pt; font-family: Arial;
                        color: navy;"> </span></font></p>
                </div>
              </div>
            </div>
          </div>
        </div>
      </li>
      <li class="card clrfix yg-msg-read-container" data-msgid="16169"
        data-uid="409424114" data-email="bpq32@{{emailDomain}}"
data-reply-to-header="{"messageIdInHeader":"PDc1RDcwMDYyMkY1RTQ1RTJBMDMwRURCMTAyQ0ZCQTZEQFpvbz4=","inReplyToHeader":"PENBSnYrQWRkT0tBX1d3d3g3N3FmPWZUZmllUVI0OFF2Y3JTd3RwM1JLcWNxREJ0ND1qUUBtYWlsLmdtYWlsLmNvbT4=","referencesHeader":"PENBSnYrQWRkT0tBX1d3d3g3N3FmPWZUZmllUVI0OFF2Y3JTd3RwM1JLcWNxREJ0ND1qUUBtYWlsLmdtYWlsLmNvbT4="}"
data-sender-status="EvBzNJ5pmSO_BQMzxxvKJclcBY3ek5-w6ixb1Jbp8mGIcAmBlRDSJgSfbBvOmwl8Cj1SZ7ZAZE2Xj2YifBRTVMYH9JYcG3sZwtu7PmkVPg"
        data-sender-email="john.wiseman@..." data-content-transformed=""
        data-author="John Wiseman" data-system-message=""
        id="yui_3_15_0_1_1423448187222_2440" style="margin: 0px 0px
        20px; padding: 0px; zoom: 1; height: 417px; outline: none;
        list-style-type: none; border: 1px solid rgb(226, 226, 230);
        overflow-x: hidden; background-color: rgb(255, 255, 255);"><font
          color="navy" face="Arial" size="2"><span style="font-size:
            10pt; font-family: Arial; color: navy;"><br>
          </span></font></li>
    </ul>
    <p><br>
    </p>
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 15-02-08 12:53 PM, Maiko Langelaar
      wrote:<br>
    </div>
    <blockquote
cite="mid:alpine.LNX.2.02.1502081136130.12131@shodan.physics.umanitoba.ca"
      type="cite">
      <br>
      Recently I received an email from a JNOS user, and he brings up a
      very
      <br>
      interesting point. Some of you may have already read up about this
      on
      <br>
      the BPQ32 Yahoo group.
      <br>
      <br>
      Why am I bringing this up ? Apparently the issue cause multiple
      copies
      <br>
      of the same message to appear at people's systems. I suppose one
      could
      <br>
      look at the expression, 'better 2 then none', but anyways ...
      <br>
      <br>
      <blockquote type="cite">I'm no expert on BBSs, but it seems to me
        the root problem is that BPQ
        <br>
        is making case-sensitive comparisons of MIDs/BIDs and when the
        other
        <br>
        major BBSs (JNOS, TNOS and apparently FBB) evidently don't care
        about
        <br>
        case.
        <br>
      </blockquote>
      <br>
      Putting in my 2 cents worth, JNOS (and TNOS too) may very well be
      sending
      <br>
      out lower case bids for non FBB forwarding session. Other then
      that, JNOS
      <br>
      and TNOS both use uppercase for FBB proposals (automatically
      uppercase
      <br>
      any bid values). As for comparison, JNOS and TNOS use strcasecmp,
      so the
      <br>
      case is actually ignored when 'we' do it. We don't care about
      case.
      <br>
      <br>
      <blockquote type="cite">After all, if you make the change to
        always force upper case, then BPQ
        <br>
        still has a problem if an originating BBS uses lower case.  So
        either
        <br>
        everyone needs to be either case-sensitive or case-insensitive.
        Right?
        <br>
      </blockquote>
      <br>
      I don't want this to be a BPQ vs 'the rest of them' issue.
      <br>
      <br>
      From my perspective, I can try and ensure that NOS is 'consistent'
      with
      <br>
      keeping it uppercase (for starters). But the logistics of asking
      ALL of
      <br>
      the NOS users out there to patch just this one issue is raised. We
      could
      <br>
      probably eliminate the majority of these issues by telling people
      to just
      <br>
      stop using mbox fbb 0 (non fbb forward modes), not sure how well
      that will
      <br>
      be received by sysops. Perhaps that will force them to understand
      why
      <br>
      they are not able to get mbox fbb 1 or higher to work properly ?
      <br>
      <br>
      Even if the consensus is to agree to case sensitivity, we still
      need to
      <br>
      get the systems out there updated. What a mess this might be.
      <br>
      <br>
      So, let's talk about it ... the BPQ guys are, so perhaps we should
      too :)
      <br>
      <br>
      Maybe after this discussion, then we could get the 3 or 4
      maintainers
      <br>
      or authors to have an internal email talk about the results ? Or
      am I
      <br>
      being naive (even after all these years of doing this) ???
      <br>
      <br>
      Maiko
      <br>
      _______________________________________________
      <br>
      nos-bbs mailing list
      <br>
      <a class="moz-txt-link-abbreviated" href="mailto:nos-bbs@tapr.org">nos-bbs@tapr.org</a>
      <br>
      <a class="moz-txt-link-freetext" href="http://www.tapr.org/mailman/listinfo/nos-bbs">http://www.tapr.org/mailman/listinfo/nos-bbs</a>
      <br>
    </blockquote>
    <br>
  </body>
</html>