• testing bw from dangerbay

    From August Abolins@1:153/135 to All on Wed May 8 19:26:00 2019
    Hi All,

    Just a test upload with SemPoint + BW -> dangerbay bbs (pcboard) and bluewave door.

    Upon download of the first packet, I noticed that the "time" field was "00:00" for all the messages. Probably not a good sign. :(

    Also, there were no kludges in the header. :(

    Starting to look like BW is not well supported anymore. But here's hoping that the CRs will work on this "official" bluewave system.


    ../|ug



    * SeM. 2.26 * Behaviorism is the art of pulling habits out

    --- PCBoard (R) v15.3/100
    * Origin: Danger Bay BBS * Vancouver, Canada (1:153/135)
  • From Paul Quinn@3:640/1384 to August Abolins on Thu May 9 16:07:34 2019
    Hi! August,

    On 08 May 19 19:26, you wrote to All:

    @MSGID: 1:153/135 0016d24b
    @PID: PCBWave v1.10+

    Hi All,

    Just a test upload with SemPoint + BW -> dangerbay bbs (pcboard) and bluewave door.

    Upon download of the first packet, I noticed that the "time" field was "00:00" for all the messages. Probably not a good sign. :(

    Also, there were no kludges in the header. :(

    Starting to look like BW is not well supported anymore. But here's
    hoping that the CRs will work on this "official" bluewave system.


    ../|ug



    * SeM. 2.26 * Behaviorism is the art of pulling habits out

    --- PCBoard (R) v15.3/100
    * Origin: Danger Bay BBS * Vancouver, Canada (1:153/135)
    SEEN-BY: 153/105 135 250 757 6809 7715 154/10 203/0 221/0 1 6 360
    240/1120
    SEEN-BY: 267/67 280/464 5003 5555 290/10 320/119 219 640/1321 1384
    712/848
    SEEN-BY: 3634/12
    @PATH: 153/135 757 221/6 1 640/1384

    Sweet. Just as the maker (SemPoint author) intended. ;) The BW door is a little lacking.

    Cheers,
    Paul.

    ... Gort, Klaatu Barada Nikto.
    --- GoldED+/LNX 1.1.5-b20130515
    * Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)
  • From Wilfred van Velzen@2:280/464 to August Abolins on Thu May 9 08:55:33 2019
    Hi August,

    On 2019-05-08 19:26:00, you wrote to All:

    @MSGID: 1:153/135 0016d24b
    @PID: PCBWave v1.10+

    Hi All,

    Just a test upload with SemPoint + BW -> dangerbay bbs (pcboard) and bluewave door.

    Upon download of the first packet, I noticed that the "time" field was "00:00" for all the messages. Probably not a good sign. :(

    Also, there were no kludges in the header. :(

    At least the MSGID kludge is in your message on arrival here...

    Starting to look like BW is not well supported anymore. But here's
    hoping that the CRs will work on this "official" bluewave system.

    The formatting looks alright.

    ../|ug



    * SeM. 2.26 * Behaviorism is the art of pulling habits out

    --- PCBoard (R) v15.3/100
    * Origin: Danger Bay BBS * Vancouver, Canada (1:153/135)
    SEEN-BY: 103/705 153/105 135 250 757 6809 7715 154/10 203/0 221/0 1 6 SEEN-BY: 221/360 229/426 240/1120 5832 267/67 280/464 5003 5555 290/10 SEEN-BY: 310/31 396/45 423/120 712/848 770/1 2452/250
    @PATH: 153/135 757 221/6 1 280/464

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Alan Ianson@1:153/757 to August Abolins on Thu May 9 00:06:32 2019
    Hi All,

    Just a test upload with SemPoint + BW -> dangerbay bbs (pcboard) and
    bluewave
    door.

    Upon download of the first packet, I noticed that the "time" field was "00:00"
    for all the messages. Probably not a good sign. :(

    As it happens, PCBoard is under development again by Ozz Nixon. I'm not sure if the blue wave support in PCBoard is internal or an external door. If it's internal the deveoloper might like to hear your comments and experiences.

    Starting to look like BW is not well supported anymore. But here's hoping tha
    the CRs will work on this "official" bluewave system.

    There has been no BW development since George Hatchew stopped developing it. The latest BW readers and doors are Y2K broken but there are patches available for them, thankfully.

    I do like the BW format that George left us with though and it is still useable today. MultiMail is a modern (0.52 was just released last month) reader that supports BW.

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From August Abolins@2:221/360 to Wilfred Van Velzen on Thu May 9 23:57:00 2019
    Hi Wilfred,
    On <Thu, 09 May 19>, you wrote me:

    @MSGID: 1:153/135 0016d24b
    @PID: PCBWave v1.10+

    Just a test upload with SemPoint + BW -> dangerbay bbs
    (pcboard) and bluewave door.


    At least the MSGID kludge is in your message on arrival here...


    The MSGID originating from SemPoint is being replaced with a new one by the PCBWave door.

    Infact, it looks like every host system is replacing the original MSGID and
    PID that SemPoint puts in. I thought that if those were present upon upload, they would remain untouched.

    Not a major issue. But the lack of ANY kludges in the downloaded packets from DangerBay's PCBWave door, is a bit disconcerting.

    ../|ug





    * SeM. 2.26 * Geneology: chasing your own tale.

    --- Concord/2/BW 001B30d (Reg.)
    * Origin: - rbb - telnet://rbb.homeip.net - (2:221/360)
  • From Wilfred van Velzen@2:280/464 to August Abolins on Fri May 10 09:05:21 2019
    Hi August,

    On 2019-05-09 23:57:00, you wrote to me:

    Just a test upload with SemPoint + BW -> dangerbay bbs
    (pcboard) and bluewave door.

    At least the MSGID kludge is in your message on arrival here...

    The MSGID originating from SemPoint is being replaced with a new one
    by the PCBWave door.

    Infact, it looks like every host system is replacing the original MSGID
    and
    PID that SemPoint puts in. I thought that if those were present upon upload, they would remain untouched.

    If it's from a bluewave package I can see the logic in that. Because bluewave packages basically are equal in status to messages written online by a bbs user. And those messages get the MSGID from the bbs.

    Not a major issue. But the lack of ANY kludges in the downloaded
    packets from DangerBay's PCBWave door, is a bit disconcerting.

    I don't see a reason why they should be removed unless the bluewave standard requires so?

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Alan Ianson@1:153/757 to Wilfred van Velzen on Fri May 10 12:39:54 2019
    Not a major issue. But the lack of ANY kludges in the downloaded
    packets from DangerBay's PCBWave door, is a bit disconcerting.

    I don't see a reason why they should be removed unless the bluewave standard requires so?

    I haven't used offline mail much in recent years but before I had my own node early in the 90's I used offline mail. The kludges were never included in mail packets I downloaded. It's just as well, the average offline user doesn't know or care what all that is about.

    BBBS has an option to turn them on for those that want them but more often than
    not offline mail packets don't include the kludges.

    Synchronet also has options for kludges in the QWK packets it creates although they are a bit different that what we see here.

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From August Abolins@2:221/1.58 to Alan Ianson on Fri May 10 19:30:00 2019
    Hello Alan!

    ** 10.05.19 - 12:39, Alan Ianson wrote to Wilfred van Velzen:

    Not a major issue. But the lack of ANY kludges in the downloaded
    packets from DangerBay's PCBWave door, is a bit disconcerting.

    I don't see a reason why they should be removed unless the bluewave
    standard requires so?

    I haven't used offline mail much in recent years but before I had my own
    node early in the 90's I used offline mail. The kludges were never
    included in mail packets I downloaded. It's just as well, the average
    offline user doesn't know or care what all that is about.

    The MSGID and REPLY kludges are what make the thread systems in the
    readers work (and thereby make it easy to follow a conversation properly. Those ought to be the minimum to have. Very useful! :)


    BBBS has an option to turn them on for those that want them but more
    often than not offline mail packets don't include the kludges.

    Yes.. I've noticed that. By default, no kludges. :(

    I guess back in the very early days of QWK for example, we worked with one packet at a time. But with database/messagebase offline readers like SemPoint.. (and this is from the SemPoint Help):

    "When you import a new mailpacket the messages will be written at
    the end of the message base for each area."

    You will have several advantages with this way of working:

    you don't need any more to open-close-open-close-open-close the
    mail packets if they are too much to be read in the time you have;

    it is easier to follow a thread or reading the message that
    generated the answer;

    if you use both a point and QWK or BlueWave or X)press you can
    answer to a user in another area (example NetMail) without
    problems;

    you can find immediately an old message without looking for the
    mail packet it was included in.


    ../|ug

    --- OpenXP 5.0.38
    * Origin: /|ug's Point, Ont. CANADA (2:221/1.58)
  • From Tommi Koivula@2:221/360 to Wilfred Van Velzen on Sat May 11 07:07:41 2019
    Wilfred van Velzen wrote to August Abolins <=-

    TID: FMail-lnx64 2.1.0.18-B20170815
    PID: GED+LNX 1.1.5-b20161221
    REPLY: 2:221/360 EF6B28DC
    MSGID: 2:280/464 779086FC
    Hi August,

    On 2019-05-09 23:57:00, you wrote to me:

    Just a test upload with SemPoint + BW -> dangerbay bbs
    (pcboard) and bluewave door.

    At least the MSGID kludge is in your message on arrival here...

    The MSGID originating from SemPoint is being replaced with a new one
    by the PCBWave door.

    Infact, it looks like every host system is replacing the original MSGID
    and
    PID that SemPoint puts in. I thought that if those were present upon upload, they would remain untouched.

    If it's from a bluewave package I can see the logic in that. Because bluewave packages basically are equal in status to messages written online by a bbs user. And those messages get the MSGID from the bbs.

    Not a major issue. But the lack of ANY kludges in the downloaded
    packets from DangerBay's PCBWave door, is a bit disconcerting.

    I don't see a reason why they should be removed unless the bluewave standard requires so?

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)

    Just a test reply by Multimail/BW/Concord.

    This combination seems to be able to show the kludges...

    'Tommi

    ... MultiMail, the new multi-platform, multi-format offline reader!

    --- Concord/2/BW 001B30d (Reg.)
    * Origin: - rbb - telnet://rbb.homeip.net - (2:221/360)
  • From Tommi Koivula@2:221/360 to Wilfred Van Velzen on Sat May 11 10:38:00 2019
    * Originally from Tommi Koivula to Wilfred Van Velzen :

    Wilfred van Velzen wrote to August Abolins <=-

    TID: FMail-lnx64 2.1.0.18-B20170815
    PID: GED+LNX 1.1.5-b20161221
    REPLY: 2:221/360 EF6B28DC
    MSGID: 2:280/464 779086FC
    Hi August,

    Just a test reply by Multimail/BW/Concord.

    This combination seems to be able to show the kludges...

    But no REPLY kludge, when replying with Multimail...

    'Tommi

    --- Concord/2 001B30d (Reg.)
    * Origin: - rbb - telnet://rbb.homeip.net - (2:221/360)
  • From Alan Ianson@1:153/757 to August Abolins on Sat May 11 00:38:28 2019
    The MSGID and REPLY kludges are what make the thread systems in the
    readers work (and thereby make it easy to follow a conversation properly. Those ought to be the minimum to have. Very useful! :)

    They are. Nodes and points can use the MSGID and REPLY kludges but not offline mail users. The BBS will always add the MSGID and REPLY kludges when you are online but if you upload a .new packet with replies they will get a MSGID only. When you reply via offline reader the BBS has no idea what message you are replying to so no REPLY kludge is included.

    That is one case where using a node or point is a good thing. Offline readers use message subject lines for threading, if they do threading.

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat May 11 11:14:04 2019
    Hi Tommi,

    On 2019-05-11 07:07:41, you wrote to me:

    TID: FMail-lnx64 2.1.0.18-B20170815
    PID: GED+LNX 1.1.5-b20161221
    REPLY: 2:221/360 EF6B28DC
    MSGID: 2:280/464 779086FC

    If it's from a bluewave package I can see the logic in that. Because
    bluewave packages basically are equal in status to messages written
    online by a bbs user. And those messages get the MSGID from the bbs.

    Not a major issue. But the lack of ANY kludges in the downloaded
    packets from DangerBay's PCBWave door, is a bit disconcerting.

    I don't see a reason why they should be removed unless the bluewave
    standard requires so?

    Just a test reply by Multimail/BW/Concord.

    This combination seems to be able to show the kludges...

    So it's not dictated by BW...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)