• OpenXP 5.0.48 released

    From Martin Foster@2:310/31.3 to All on Sun Dec 27 11:07:00 2020
    Greetings All!

    OpenXP 5.0.48 has been released and is available for download from the following URLs .....

    https://sourceforge.net/projects/openxp5/

    https://openxp.uk/

    OpenXP is a fully integrated FidoNet Point system, email client and
    newsgroup client for the Windows/Linux console.

    OpenXP5.0.48-win.zip - Win32 version.

    openxp-5.0.48-1.x86_64-lnx.zip - Linux 64-Bit ZIP package.

    openxp-5.0.48-1.x86_64.rpm - Linux 64-Bit RPM package.

    Pascal source code packages are also available for download.

    See this document for a complete list of changes ..... https://openxp.uk/doc/changes.txt

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: OpenXP-Team (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Sun Dec 27 10:59:00 2020
    Hello Martin!

    ** On Sunday 27.12.20 - 11:07, Martin Foster wrote to All:

    OpenXP 5.0.48 has been released and is available for download from the following URLs .....

    Woohoo! I'm on it.


    See this document for a complete list of changes ..... https://openxp.uk/doc/changes.txt

    Which reminds me, how exactly do we get the "backward search" to
    work (as mentioned in an earlier fix:

    OpenXP 5.0.42 - 2019-12-28

    Changes (w.r.t. OpenXP 5.0.40):

    - All versions:
    - Message viewer: backward search with <Shift-Tab>
    (in normal search mode only, not in URL-search)
    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to August Abolins on Mon Dec 28 11:31:00 2020
    Hello August!

    *** Sunday 27.12.20 at 10:59, August Abolins wrote to Martin Foster:

    OpenXP 5.0.48 has been released and is available for download from the
    following URLs .....

    Woohoo! I'm on it.

    You like? :-))

    See this document for a complete list of changes .....
    https://openxp.uk/doc/changes.txt

    Which reminds me, how exactly do we get the "backward search" to
    work (as mentioned in an earlier fix:

    OpenXP 5.0.42 - 2019-12-28

    Changes (w.r.t. OpenXP 5.0.40):

    - All versions:
    - Message viewer: backward search with <Shift-Tab>
    (in normal search mode only, not in URL-search)

    After doing a normal search by pressing "s" and then repeating the
    search any number of times for the next occurence of whatever it is
    you're searching for, press <Shift+Tab> and the previous occurence of
    the match will be highlighted until there are no more matches.

    Try searching 4 times for the word "the" in this message and then
    press <Shift+Tab> 4 times to see what I mean :)

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Mon Dec 28 20:47:00 2020
    Am 27.12.20 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    OpenXP 5.0.48 has been released and is available for download from the following URLs .....

    Thank you very much for the new version, OpenXP-team!
    I've just installed it :)

    This is a nice christmas gift :)

    Regards,
    Anna

    --- OpenXP 5.0.48
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Mon Dec 28 16:31:00 2020
    Hello Anna!

    ** On Monday 28.12.20 - 20:47, Anna Christina Nass wrote to Martin Foster:

    Thank you very much for the new version, OpenXP-team!
    I've just installed it :)

    This is a nice christmas gift :)
    -+- OpenXP 5.0.48
    + Origin: Imzadi Box Point (2:240/5824.1)


    Hello Anna. Yes.. OpenXP just keeps on giving.

    BTW.. I notice that you are linked up with Dovenet (via nntp)
    too. Have you noticed that when you post a R)eply in the middle
    of a conversion that the message then gets re-addressed to "All"
    instead? Yet, when you R)eply to a message that *is* addressed to
    your name then the outgoing message is address to the Sender
    properly?

    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)
  • From Oli@2:280/464.47 to Martin Foster on Tue Dec 29 08:53:07 2020
    Martin wrote (2020-12-27):

    See this document for a complete list of changes ..... https://openxp.uk/doc/changes.txt

    Changes and bugfixes (w.r.t. OpenXP 5.0.46):

    - Fido network
    - Added handling of kludge REPLYTO

    There is no "REPLYTO" kludge in Fidonet, it's "REPLY"

    ---
    * Origin: (2:280/464.47)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Tue Dec 29 12:59:00 2020
    Hello Anna!

    *** Monday 28.12.20 at 20:47, Anna Christina Nass wrote to Martin Foster:

    OpenXP 5.0.48 has been released and is available for download from the
    following URLs .....

    Thank you very much for the new version, OpenXP-team!

    You are very welcome.

    I've just installed it :)

    Cool :)

    This is a nice christmas gift :)

    Glad you like it :)

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: OpenXP-Team (2:310/31.3)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Tue Dec 29 19:37:00 2020
    Am 28.12.20 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    BTW.. I notice that you are linked up with Dovenet (via nntp)
    too. Have you noticed that when you post a R)eply in the middle
    of a conversion that the message then gets re-addressed to "All"
    instead? Yet, when you R)eply to a message that *is* addressed to
    your name then the outgoing message is address to the Sender
    properly?

    No, I did not notice this because I mostly use the Synchronet web
    interface for DOVE-Net and not nntp.
    I use OpenXP only for Fido networks (Fido, fsxNet, tqwNet, SciNet).

    Regards,
    Anna

    --- OpenXP 5.0.48
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Martin Foster on Wed Dec 30 23:58:00 2020
    Hello Martin!

    ** On Monday 28.12.20 - 11:31, Martin Foster wrote to August Abolins:

    OpenXP 5.0.48 has been released...

    Woohoo! I'm on it.

    You like? :-))

    What's NOT to like? I am still totally impressed how your simple recommendation (is it 2 years ago now?) steered me off my then chiselled-in-stone decision to stick with a Windows-based Apoint
    or Winpoint. OpenXP's text based system is truly ideal for
    messaging.


    After doing a normal search by pressing "s" and then
    repeating the search any number of times for the next
    occurence of whatever it is you're searching for, press
    <Shift+Tab> and the previous occurence of the match will be
    highlighted until there are no more matches.

    Ah.. excellent. For the most part, messages are pretty short so
    a search for anything hasn't been necessary. But I can see it
    handy when reading a long multiple-screen newsletter. Searching
    backwards in the same message for the same string is a fine
    convenience.

    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to Oli on Fri Jan 1 12:03:00 2021
    Hello Oli!

    *** Tuesday 29.12.20 at 08:53, Oli wrote to Martin Foster:

    See this document for a complete list of changes .....
    https://openxp.uk/doc/changes.txt

    Changes and bugfixes (w.r.t. OpenXP 5.0.46):

    - Fido network
    - Added handling of kludge REPLYTO

    There is no "REPLYTO" kludge in Fidonet,

    Oh?

    = FUTURE4FIDO (2:310/31.3) ====================================================
    Msg : 51 of 101 Snt
    From : Benny Pedersen 2:460/58 02 Dec 20 12:05:12
    To : All
    Subj : ... =============================================================================== @MSGID: 2:460/58 0000054d
    @PID: tg_BBS_v0.6.2
    @CHRS: CP866 2
    @TGUID: 270364579
    @REPLYTO 2:460/58 270364579
    Hello :)

    --- tg BBS v0.6.2
    * Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/58)
    @PATH: 460/58 280/464 310/31 ===============================================================================

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: OpenXP-Team (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Fri Jan 1 13:16:00 2021
    Hello August!

    *** Wednesday 30.12.20 at 23:58, August Abolins wrote to Martin Foster:

    OpenXP 5.0.48 has been released...

    Woohoo! I'm on it.

    You like? :-))

    What's NOT to like? I am still totally impressed how your simple recommendation (is it 2 years ago now?) steered me off my then chiselled-in-stone decision to stick with a Windows-based Apoint
    or Winpoint. OpenXP's text based system is truly ideal for
    messaging.

    I don't remember exactly what I said but I *do* remember referring to
    it as an adventure. Long may the adventure continue :-)

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Oli@2:280/464.47 to Martin Foster on Sat Jan 2 15:00:09 2021
    Martin wrote (2021-01-01):

    There is no "REPLYTO" kludge in Fidonet,

    Oh?

    = FUTURE4FIDO (2:310/31.3) ==================================================== Msg : 51 of 101
    Snt From : Benny Pedersen
    2:460/58 02 Dec 20 12:05:12 To : All
    Subj : ... ===============================================================================
    @MSGID: 2:460/58 0000054d
    @PID: tg_BBS_v0.6.2
    @CHRS: CP866 2
    @TGUID: 270364579
    @REPLYTO 2:460/58 270364579
    Hello :)

    --- tg BBS v0.6.2
    * Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/58) ===============================================================================

    Sorry, I was confused and thought it had something to do with the MSGID and reply linking. I saw REPLYID kludges generated by some software and replyTo is used internally by some message base formats.

    I still don't understand what the REPLYTO kludge is good for in this case. It is also unspecified as a single kludge and not covered by any standard or proposal. There is FSC-0035 (http://ftsc.org/docs/fsc-0035.001) which defines REPLYADDR *and* REPLYTO in combination (both have to be included in the message).

    Using the REPLYTO address and ignoring the REPLYADDR could cause issues and is not a correct implementation of FSC-0035. If this is not intended to be an implementation of FSC-0035, maybe the Telegram Gateway and OpenXP should use another kludge.

    ---
    * Origin: (2:280/464.47)
  • From Martin Foster@2:310/31.3 to Oli on Sun Jan 3 11:16:00 2021
    Hello Oli!

    *** Saturday 02.01.21 at 15:00, Oli wrote to Martin Foster:

    There is no "REPLYTO" kludge in Fidonet,

    Oh?

    = FUTURE4FIDO (2:310/31.3)
    ==================================================== Msg : 51 of 101
    Snt From : Benny Pedersen
    2:460/58 02 Dec 20 12:05:12 To : All
    Subj : ...
    ========================================================================
    ======= @MSGID: 2:460/58 0000054d
    @PID: tg_BBS_v0.6.2
    @CHRS: CP866 2
    @TGUID: 270364579
    @REPLYTO 2:460/58 270364579
    Hello :)

    --- tg BBS v0.6.2
    * Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/58)
    ========================================================================
    =======

    Sorry, I was confused and thought it had something to do with the
    MSGID and reply linking.

    That's OK, no problem, we all get confused from time to time :)

    I saw REPLYID kludges generated by some software and replyTo is used internally by some message base formats.

    I still don't understand what the REPLYTO kludge is good for in this case.

    It's used for netmail replies to echomail messages originating on the Telegram side of the gateway.

    It is also unspecified as a single kludge and not covered by any
    standard or proposal. There is FSC-0035 (http://ftsc.org/docs/fsc- 0035.001) which defines REPLYADDR *and* REPLYTO in combination (both
    have to be included in the message).

    That's absolutely correct.

    Using the REPLYTO address and ignoring the REPLYADDR could cause
    issues and is not a correct implementation of FSC-0035.
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    That's also absolutely correct.

    If this is not intended to be an implementation of FSC-0035, maybe the Telegram Gateway

    I cannot possibly pass comment on the Telegram Gateway software
    developers' intentions in this respect because I'm not conversant with the way in which his software works.

    and OpenXP should use another kludge.

    However, OpenXP doesn't insert the kludge, it recognises an implementation
    of the kludge and takes action on it when necessary.

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Sun Jan 3 09:19:00 2021
    Hello Martin!

    ** On Sunday 03.01.21 - 11:16, Martin Foster wrote to Oli:

    I still don't understand what the REPLYTO kludge is good for
    in this case.

    It's used for netmail replies to echomail messages
    originating on the Telegram side of the gateway.

    Perhaps we can reserve the term gateway to systems that are truly
    insecure like usenet. The Telegram solution that Stas has built
    is limited to itself; the general public cannot access those
    messages unless specifically participating as "known" users.
    Unlike usenet, it is not possible to be a lurker as you can be in
    fidonet or usenet.

    Carol's analogy of the Telegram "system" as an OLR solution is
    better. No one thinks of OLR's as gateways. ;)




    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)
  • From August Abolins@2:221/1.58 to Martin Foster on Sun Jan 3 11:24:00 2021
    Hello Martin!

    ** On Sunday 03.01.21 - 11:16, Martin Foster wrote to Oli:

    It is also unspecified as a single kludge and not covered by
    any standard or proposal. There is FSC-0035 (http://
    ftsc.org/docs/fsc-0035.001) which defines REPLYADDR *and*
    REPLYTO in combination (both have to be included in the
    message).

    That's absolutely correct.

    Ah.. but it seems that application of any particular kludge
    (especially if it is just in the documented proposal stage) is
    optional. Therefore, there is nothing technically wrong with
    REPLYTO appearing by itself if it doesn't break anyone's system.

    Infact, MSGID has appeared by itself by many systems (and may
    still do). However.. that one is now documented as an FTS and to
    be used in conjunction with the REPLYID.

    But.. there will always be people insisting to use old software
    that can't be updated to use anything beyond what's in FTS-0001



    Using the REPLYTO address and ignoring the REPLYADDR could cause
    issues and is not a correct implementation of FSC-0035.
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    That's also absolutely correct.

    What issues? Techically, REPLYTO is working just fine (by
    OpenXP). Why is even REPLYADRR required when all equivalent info
    is already present in *other* parts of the header?

    Too bad the FTC-0035 doesn't provide working examples.
    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to August Abolins on Tue Jan 5 11:18:00 2021
    Hello August!

    *** Sunday 03.01.21 at 09:19, August Abolins wrote to Martin Foster:

    I still don't understand what the REPLYTO kludge is good for
    in this case.

    It's used for netmail replies to echomail messages
    originating on the Telegram side of the gateway.

    Perhaps we can reserve the term gateway to systems that are truly
    insecure like usenet. The Telegram solution that Stas has built
    is limited to itself; the general public cannot access those
    messages unless specifically participating as "known" users.
    Unlike usenet, it is not possible to be a lurker as you can be in
    fidonet or usenet.

    Carol's analogy of the Telegram "system" as an OLR solution is
    better. No one thinks of OLR's as gateways. ;)

    OK, perhaps it would have been better and more accurate if I'd said "originating on Telegram Messenger" instead of saying "originating on the Telegram side of the gateway".

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Tue Jan 5 11:24:00 2021
    Hello August!

    *** Sunday 03.01.21 at 11:24, August Abolins wrote to Martin Foster:

    [snip]
    Using the REPLYTO address and ignoring the REPLYADDR could cause
    issues and is not a correct implementation of FSC-0035.
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    That's also absolutely correct.

    What issues?

    I was actually replying to the text which I'd "underlined" :)

    Techically, REPLYTO is working just fine (by OpenXP).

    Yes it is and thanks for confirming that :)

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Tue Jan 5 08:20:00 2021
    Hello Martin!

    ** On Tuesday 05.01.21 - 11:18, Martin Foster wrote to August Abolins:

    Carol's analogy of the Telegram "system" as an OLR solution is
    better. No one thinks of OLR's as gateways. ;)

    OK, perhaps it would have been better and more accurate if I'd said "originating on Telegram Messenger" instead of saying "originating on the Telegram side of the gateway".

    Perhaps. ;) I think "posted from tg BBS" would be better,
    because Stas' tosser converts Telegram's format to something FTN
    can understand. Technically, the messages dead-end at Stas' BBS
    system. He merely uses the Telegram resources like a VPS, and all
    we have to do is use the Telegram app to read the material.


    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Thu Jan 7 08:15:00 2021
    Hello Anna!

    ** On Tuesday 29.12.20 - 19:37, Anna Christina Nass wrote to August Abolins:

    I use OpenXP only for Fido networks (Fido, fsxNet, tqwNet, SciNet).

    From where are you getting Scinet? I wouldn't mind adding a few
    echo from that.

    Meanwhile, I replied to you FSXnet about a potential source for
    getting DoveNet.

    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Thu Jan 7 16:33:00 2021
    Am 07.01.21 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    I use OpenXP only for Fido networks (Fido, fsxNet, tqwNet, SciNet).

    From where are you getting Scinet? I wouldn't mind adding a few
    echo from that.

    I've used the application form in a SciNet infopack.
    My Hub is the disksh0p bbs (diskshop.ca).
    You can get the infopack here: https://scinet-ftn.org

    Meanwhile, I replied to you FSXnet about a potential source for
    getting DoveNet.

    Thank you!

    Regards,
    Anna

    --- OpenXP 5.0.48
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@1:153/757.2 to Anna Christina Nass on Thu Jan 7 11:17:05 2021
    I've used the application form in a SciNet infopack.
    My Hub is the disksh0p bbs (diskshop.ca).
    You can get the infopack here: https://scinet-ftn.org

    I did not realize that there was a whole website dedicated to that othernet. It's a beautiful work, and the info is well organized.

    I did not realize that you were pointing off of your own bbs initially.

    Maybe non-bbs/independent users are not part of the scinet plan. I will see.

    thx for the info.
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
  • From Jay Harris@1:229/664 to August Abolins on Thu Jan 7 14:30:31 2021
    On 07 Jan 2021, August Abolins said the following...

    From where are you getting Scinet? I wouldn't mind adding a few
    echo from that.

    I've never been a hub or a boss node before, but I've got SciNet and am willing to give it a shot if you are.

    I use Mystic & Bink if that makes any difference.

    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From August Abolins@2:221/1.58 to Jay Harris on Thu Jan 7 17:35:00 2021
    Hello Jay!

    ** On Thursday 07.01.21 - 14:30, Jay Harris wrote to August Abolins:

    I've never been a hub or a boss node before, but I've got SciNet and am willing to give it a shot if you are.

    As long as I am not ruffling anyone's feathers wrt what is
    allowed in the network, I'm game.


    I use Mystic & Bink if that makes any difference.

    Shouldn't be a problem.

    I could send you my pw preference via crash netmail as a
    preliminary test/confirmation.

    Sofar, I am connecting to boss systems that use binkd/1.1a-111
    and binkp/1.1 that all use Synchonet.

    One of them was briefly operating Enigma or Mystic, but switched
    to Sychronet.


    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From Jay Harris@1:229/664 to August Abolins on Thu Jan 7 18:28:08 2021
    On 07 Jan 2021, August Abolins said the following...

    I've never been a hub or a boss node before, but I've got SciNet and willing to give it a shot if you are.

    As long as I am not ruffling anyone's feathers wrt what is
    allowed in the network, I'm game.

    I'll double-check with Frank just to make sure. I just sent him a Netmail.

    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Jay Harris@1:229/664 to August Abolins on Thu Jan 7 22:10:11 2021
    On 07 Jan 2021, Jay Harris said the following...

    I've never been a hub or a boss node before, but I've got SciNet willing to give it a shot if you are.

    As long as I am not ruffling anyone's feathers wrt what is
    allowed in the network, I'm game.

    I'll double-check with Frank just to make sure. I just sent him a Netmail.

    Frank says we can "Go Nuts" ;)

    Haven't got a Netmail from you yet though.


    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From August Abolins@2:221/1.58 to Jay Harris on Thu Jan 7 23:52:00 2021
    Hello Jay!

    ** On Thursday 07.01.21 - 22:10, Jay Harris wrote to August Abolins:

    Frank says we can "Go Nuts" ;)
    Haven't got a Netmail from you yet though.

    I delivered it direct (crash) to your system, hours ago:

    Subject: Netcall to 1:229/664
    Software: OpenXP/5.0.48 (Win32)
    Date: Th 07.01.21, 17:42
    Size: 471 Bytes
    --------------------------------------------------------
    1 15 F1-Help
    = 17:42:35 CONNECT
    17:42:36 OPT CRAM-MD5-34b06aba336d07ae6c6b5df6afe2b1c3
    17:42:36 SYS Northern Realms
    17:42:36 ZYZ Warpslide
    17:42:36 TIME Thu, 07 Jan 2021 17:42:34 -0500
    17:42:36 VER Mystic/1.12A47 binkp/1.0
    17:42:36 BUILD 2021/01/05 00:11:26 Raspberry Pi/32
    17:42:37 non-secure
    17:42:37 QSIZE 0 files 0 bytes
    * 17:42:38 Sent 07174235.PKT, 864b
    = 17:42:38 hangup
    - 17:42:38 exiting


    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Fri Jan 8 11:50:00 2021
    Am 07.01.21 schrieb August Abolins@1:153/757.2 in POINTS:

    Hallo August,

    You can get the infopack here: https://scinet-ftn.org
    [...]

    Maybe non-bbs/independent users are not part of the scinet plan. I will see.

    Why do you think this?
    I guess you can ask if you can connect to diskshop or other BBSes as a point...

    Regards,
    Anna

    --- OpenXP 5.0.48
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Jay Harris@1:229/664 to August Abolins on Fri Jan 8 08:19:13 2021
    On 07 Jan 2021, August Abolins said the following...

    Haven't got a Netmail from you yet though.

    I delivered it direct (crash) to your system, hours ago:

    Hmm, Mystic isn't seeing it as Netmail...

    + Jan 08 08:06:35 Process: Importing EchoMail
    + Jan 08 08:06:35 Waiting for BUSY nodes
    + Jan 08 08:06:35 Importing 07174235.PKT (2:221/1.58 to 1:229/664)
    ! Jan 08 08:06:35 No echomail node configured for 2:221/1.58
    ! Jan 08 08:06:35 Moving /home/pi/mystic/echomail/in/07174235.PKT to /home/pi

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Fri Jan 8 08:41:00 2021
    Hello Anna!

    ** On Friday 08.01.21 - 11:50, Anna Christina Nass wrote to August Abolins:

    Maybe non-bbs/independent users are not part of the scinet plan. I will
    see.

    Why do you think this?
    I guess you can ask if you can connect to diskshop or other BBSes as a point...

    I had a situation in Micronet where I asked if I could come on
    board as a point, but no one was operating one. The guidelines
    seemed to be geared to assume sysop members only.

    I thought that maybe SciNet was sysop-only too.

    Anyway.. I am poised to get a point assignment. It's all good.

    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From August Abolins@2:221/1.58 to Jay Harris on Fri Jan 8 09:03:00 2021
    Hello Jay!

    ** On Friday 08.01.21 - 08:19, Jay Harris wrote to August Abolins:

    On 07 Jan 2021, August Abolins said the following...

    Haven't got a Netmail from you yet though.

    I delivered it direct (crash) to your system, hours ago:

    Hmm, Mystic isn't seeing it as Netmail...

    + Jan 08 08:06:35 Process: Importing EchoMail
    + Jan 08 08:06:35 Waiting for BUSY nodes
    + Jan 08 08:06:35 Importing 07174235.PKT (2:221/1.58 to 1:229/664)
    ! Jan 08 08:06:35 No echomail node configured for 2:221/1.58
    ! Jan 08 08:06:35 Moving /home/pi/mystic/echomail/in/07174235.PKT to /home/pi

    Interesting. Is it because my system is Zone 2, and yours is
    Zone 1?

    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From August Abolins@2:221/1.58 to Jay Harris on Fri Jan 8 09:33:00 2021
    Hello Jay!

    ** On Friday 08.01.21 - 08:19, Jay Harris wrote to August Abolins:

    Hmm, Mystic isn't seeing it as Netmail...

    + Jan 08 08:06:35 Process: Importing EchoMail
    + Jan 08 08:06:35 Waiting for BUSY nodes
    + Jan 08 08:06:35 Importing 07174235.PKT (2:221/1.58 to 1:229/664)
    ! Jan 08 08:06:35 No echomail node configured for 2:221/1.58
    ! Jan 08 08:06:35 Moving /home/pi/mystic/echomail/in/07174235.PKT to /home/pi


    MEANWHILE, I send a netmail routed.

    And, I just delivered another crash netmail but this time I used
    a zone that we have in common, "21:"

    My logs don't record your Z:N/F number. :( But the packet
    number might help you look for it if you have to:

    = 09:13:12 CONNECT
    09:13:14 OPT CRAM-MD5-074d93030edc269a488e40666b8fa33d
    09:13:15 SYS Northern Realms
    09:13:15 ZYZ Warpslide
    09:13:15 TIME Fri, 08 Jan 2021 09:13:12 -0500
    09:13:15 VER Mystic/1.12A47 binkp/1.0
    09:13:15 BUILD 2021/01/05 00:11:26 Raspberry Pi/32
    09:13:16 non-secure
    09:13:16 QSIZE 0 files 0 bytes
    * 09:13:17 Sent 08091311.PKT, 407b
    = 09:13:17 hangup
    - 09:13:17 exiting



    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From Charles Pierson@1:106/127 to August Abolins on Fri Jan 8 08:29:27 2021
    On 08 Jan 2021, August Abolins said the following...
    Maybe non-bbs/independent users are not part of the scinet plan. I
    see.

    Why do you think this?
    I guess you can ask if you can connect to diskshop or other BBSes
    as a ACN> point...

    I had a situation in Micronet where I asked if I could come on
    board as a point, but no one was operating one. The guidelines
    seemed to be geared to assume sysop members only.

    I thought that maybe SciNet was sysop-only too.

    Anyway.. I am poised to get a point assignment. It's all good.

    Each network has it's own thing. I had a lot of trouble finding a system in
    Z1 to accept points for a while.

    All you can do is keep looking around.

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: theoasisbbs.ddns.net:1357 (1:106/127)
  • From Charles Pierson@1:106/127 to August Abolins on Fri Jan 8 08:32:29 2021
    On 08 Jan 2021, August Abolins said the following...
    On 07 Jan 2021, August Abolins said the following...

    Haven't got a Netmail from you yet though.

    I delivered it direct (crash) to your system, hours ago:

    Hmm, Mystic isn't seeing it as Netmail...

    + Jan 08 08:06:35 Process: Importing EchoMail
    + Jan 08 08:06:35 Waiting for BUSY nodes
    + Jan 08 08:06:35 Importing 07174235.PKT (2:221/1.58 to 1:229/664) ! Jan 08 08:06:35 No echomail node configured for 2:221/1.58
    ! Jan 08 08:06:35 Moving /home/pi/mystic/echomail/in/07174235.PKT /home/pi

    Interesting. Is it because my system is Zone 2, and yours is
    Zone 1?

    I would't think so. Maybe it doesnpt accept unknown sources?

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: theoasisbbs.ddns.net:1357 (1:106/127)
  • From Jay Harris@1:229/664 to August Abolins on Fri Jan 8 11:11:22 2021
    On 08 Jan 2021, August Abolins said the following...

    MEANWHILE, I send a netmail routed.

    And, I just delivered another crash netmail but this time I used
    a zone that we have in common, "21:"

    My logs don't record your Z:N/F number. :( But the packet
    number might help you look for it if you have to:

    Weird, Mystic is still trying to toss it as echomail:

    + Jan 08 11:08:09 Importing 08091311.PKT (2:221/1.58 to 21:3/110)
    ! Jan 08 11:08:09 No echomail node configured for 2:221/1.58
    ! Jan 08 11:08:09 Moving /home/pi/mystic/echomail/in/unsecure/08091311.PKT to /home/pi/mystic/echomail/bad/08091311.PKT

    I had a look at the packet and I do see an INTL kludge in there, which I believe only netmail has. (Correct me if I'm wrong) - So I'm not sure what the issue is here.

    At any rate, if I get you setup as a point, my system will then at least know who you are... lol


    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Jay Harris@1:229/664 to Charles Pierson on Fri Jan 8 11:17:37 2021
    On 08 Jan 2021, Charles Pierson said the following...

    I would't think so. Maybe it doesnpt accept unknown sources?

    I do have "Allow UnSecure = Yes" in my bink server config as well as "unsecure_dir = true" in my mailin.ini file. So it *should* be working, I've received direct netmail before from fsx as well as some direct netmails from fido when sending to ping@.

    Not sure where the issue lays here... *scratches head*


    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Tommi Koivula@2:221/1.1 to Jay Harris on Fri Jan 8 18:51:24 2021
    * Originally in wat.netmail
    * Crossposted in points

    * Replying to a msg in points (points)

    Hi Jay.

    08 Jan 21 11:11:22, you wrote to August Abolins:

    On 08 Jan 2021, August Abolins said the following...

    MEANWHILE, I send a netmail routed.

    And, I just delivered another crash netmail but this time I used
    a zone that we have in common, "21:"

    My logs don't record your Z:N/F number. :( But the packet
    number might help you look for it if you have to:

    Weird, Mystic is still trying to toss it as echomail:

    + Jan 08 11:08:09 Importing 08091311.PKT (2:221/1.58 to 21:3/110)
    ! Jan 08 11:08:09 No echomail node configured for 2:221/1.58
    ! Jan 08 11:08:09 Moving /home/pi/mystic/echomail/in/unsecure/08091311.PKT to
    /home/pi/mystic/echomail/bad/08091311.PKT

    I had a look at the packet and I do see an INTL kludge in there, which I believe only netmail has.
    (Correct me if I'm wrong) - So I'm not sure what the issue is here.

    At any rate, if I get you setup as a point, my system will then at least know
    who you are... lol

    This is a crashmail test reply from a point of GoldED/HPT/Binkd.

    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)

    'Tommi


    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)
  • From Jay Harris@1:229/664 to All on Fri Jan 8 11:44:55 2021
    On 08 Jan 2021, Jay Harris said the following...

    Not sure where the issue lays here... *scratches head*

    The plot thickens. I have exactly three files in my /bad directory:

    pi@bbs:~/mystic/echomail/bad $ ll
    total 12K
    -rw-r--r-- 1 pi pi 968 Dec 6 14:36 06193633.PKT
    -rw-r--r-- 1 pi pi 864 Jan 7 12:42 07174235.PKT
    -rw-r--r-- 1 pi pi 407 Jan 8 04:13 08091311.PKT

    All three seem to be direct netmails from Ogg.

    Here is the header of the last packet. I've replaced the escape characters with spaces for the purpose of this message and the "white box" character with *s.

    n * * tkaugabo : jn *08 Jan 21 09:13:00Jay HarrisOggtesting same ZONE F
    MPT 21
    INTL 21:3/110 21:4/106
    MSGID: 21:4/106.21@fsxnet ec3c87c1
    PID: OpenXP/5.0.48 (Win32)
    CHRS: ASCII 1
    TZUTC: -0500

    I'm wondering if the (F)MPT kludge split up on multiple lines is the culprit?

    Does anyone know of a .PKT reader available for arm/linux?


    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Wilfred van Velzen@2:280/464 to Jay Harris on Fri Jan 8 18:26:54 2021
    Hi Jay,

    On 2021-01-08 11:44:55, you wrote to All:

    Does anyone know of a .PKT reader available for arm/linux?

    Do you have a C compiler available for it? If so, I can get you the C source code of one, that works on my (intel) linux machine...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Jay Harris@1:229/664 to Wilfred van Velzen on Fri Jan 8 13:45:32 2021
    On 08 Jan 2021, Wilfred van Velzen said the following...

    Do you have a C compiler available for it? If so, I can get you the C sourcecode of one, that works on my (intel) linux machine...

    I had to build cryptlib for Mystic by installing build-essentials. I *think* that should work?

    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Jay Harris@1:229/664 to Tommi Koivula on Fri Jan 8 13:46:31 2021
    On 08 Jan 2021, Tommi Koivula said the following...

    This is a crashmail test reply from a point of GoldED/HPT/Binkd.

    'Tommi

    Thanks, I got both this and the direct netmail.

    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Tommi Koivula@2:221/1.1 to Jay Harris on Fri Jan 8 20:59:18 2021
    Hi Jay.

    08 Jan 21 13:46:30, you wrote to me:

    On 08 Jan 2021, Tommi Koivula said the following...

    This is a crashmail test reply from a point of GoldED/HPT/Binkd.

    'Tommi

    Thanks, I got both this and the direct netmail.

    Good! So it seems that there is something wrong with OpenXP... Well, it is a _point_ software. Points should send all mail via their boss.

    'Tommi

    ... \\ZPO has been up for: 22 day(s), 11 hour(s), 20 minute(s), 30 second(s) ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)
  • From Wilfred van Velzen@2:280/464 to Jay Harris on Fri Jan 8 21:34:45 2021
    Hi Jay,

    On 2021-01-08 13:45:32, you wrote to me:

    Do you have a C compiler available for it? If so, I can get you the C
    sourcecode of one, that works on my (intel) linux machine...

    I had to build cryptlib for Mystic by installing build-essentials. I *think* that should work?

    Ok, download: http://www.vlzn.nl/tmp/pktview-1.1-src.zip
    Unzip it somewhere, and do something like:

    # gcc pktview.c -o pktview

    Which should give you the 'pktview' command.
    Usage is self explanatory when you run it without arguments.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From August Abolins@2:221/1.58 to Tommi Koivula on Fri Jan 8 16:21:00 2021
    Hello Tommi!

    ** On Friday 08.01.21 - 20:59, Tommi Koivula wrote to Jay Harris:

    Thanks, I got both this and the direct netmail.

    Good! So it seems that there is something wrong with OpenXP... Well, it
    is a _point_ software. Points should send all mail via their boss.

    It's point software with perks, like not discriminating with
    other systems by mishandling established session pwds, it seems.

    :(

    Will have to report that situation.

    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From Jay Harris@1:229/664 to Wilfred van Velzen on Fri Jan 8 16:50:14 2021
    On 08 Jan 2021, Wilfred van Velzen said the following...

    Ok, download: http://www.vlzn.nl/tmp/pktview-1.1-src.zip
    Unzip it somewhere, and do something like:

    # gcc pktview.c -o pktview

    Which should give you the 'pktview' command.
    Usage is self explanatory when you run it without arguments.

    Awesome, thanks! That seems to be working:

    pktview V1.1, Copyright WvV 1998, 2016

    Dest. Node addr: 1:229/664.0
    Orig. Node addr: 2:221/1.58
    QDest Zone : 1
    QOrig Zone : 2
    Aux Net : 0
    Date : 2021/01/07
    Time : 00:00:00
    Baud : 0
    Pkt Type : 2
    ProdCode : 233
    Revision Major : 3
    Revision Minor : 20
    Password : (hidden)
    Capability Word: 0001
    Capability Val.: 0001
    Product data : 00000000

    Date Time To From Subject Area ----------------------------------------------------------------------------- 07 Jan 21 17:41:00 Jay Harris August Abolins SciNet Point

    1 messages in this .pkt file.


    And with -v:

    001 Orig. : 221/1
    Dest. : 229/664
    Attribute: 0081
    Cost : 0
    Date : 07 Jan 21 17:41:00
    To : Jay Harris
    From : August Abolins
    Subject : SciNet Point


    So the packet itself *seems* to be ok, there's no area on the message, but Mystic isn't seeing the message as netmail. Could it be because of the PKT password?

    Just not sure what makes a netmail message.. netmail:

    + Jan 08 16:34:22 Process: Importing EchoMail
    + Jan 08 16:34:22 Waiting for BUSY nodes
    ! Jan 08 16:34:22 Import from /home/pi/mystic/echomail/in/
    ! Jan 08 16:34:22 Import from /home/pi/mystic/echomail/in/unsecure/
    + Jan 08 16:34:22 Importing 06193633.PKT (2:221/1.58 to 1:229/664)
    ! Jan 08 16:34:22 No echomail node configured for 2:221/1.58
    ! Jan 08 16:34:22 Moving /home/pi/mystic/echomail/in/unsecure/06193633.PKT to /home/pi/mystic/echomail/bad/06193633.PKT
    + Jan 08 16:34:22 Importing 07174235.PKT (2:221/1.58 to 1:229/664)
    ! Jan 08 16:34:22 No echomail node configured for 2:221/1.58
    ! Jan 08 16:34:22 Moving /home/pi/mystic/echomail/in/unsecure/07174235.PKT to /home/pi/mystic/echomail/bad/07174235.PKT
    + Jan 08 16:34:22 Importing 08091311.PKT (2:221/1.58 to 21:3/110)
    ! Jan 08 16:34:22 No echomail node configured for 2:221/1.58
    ! Jan 08 16:34:22 Moving /home/pi/mystic/echomail/in/unsecure/08091311.PKT to /home/pi/mystic/echomail/bad/08091311.PKT
    + Jan 08 16:34:22 Results: 0 echo, 0 net, 0 dupes, 0 tossed in 0.08s


    Whereas Tommi's netmail form before:

    + Jan 08 11:55:12 Process: Importing EchoMail
    + Jan 08 11:55:12 Waiting for BUSY nodes
    + Jan 08 11:55:12 Importing 901beb06.pkt (2:221/1.1 to 1:229/664)
    + Jan 08 11:55:12 Netmail from Tommi Koivula (2:221/1.1) to Jay Harris (1:229/664)
    + Jan 08 11:55:12 Results: 0 echo, 1 net, 0 dupes, 0 tossed in 0.08s


    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Wilfred van Velzen@2:280/464 to Jay Harris on Fri Jan 8 23:48:22 2021
    Hi Jay,

    On 2021-01-08 16:50:14, you wrote to me:

    Usage is self explanatory when you run it without arguments.

    Awesome, thanks! That seems to be working:

    pktview V1.1, Copyright WvV 1998, 2016

    Dest. Node addr: 1:229/664.0
    Orig. Node addr: 2:221/1.58
    QDest Zone : 1
    QOrig Zone : 2
    Aux Net : 0
    Date : 2021/01/07
    Time : 00:00:00
    Baud : 0
    Pkt Type : 2
    ProdCode : 233
    Revision Major : 3
    Revision Minor : 20
    Password : (hidden)
    Capability Word: 0001
    Capability Val.: 0001
    Product data : 00000000

    Date Time To From Subject Area ---------------------------------------------------------------------------
    -- 07 Jan 21 17:41:00 Jay Harris August Abolins SciNet Point

    1 messages in this .pkt file.


    And with -v:

    001 Orig. : 221/1
    Dest. : 229/664
    Attribute: 0081
    Cost : 0
    Date : 07 Jan 21 17:41:00
    To : Jay Harris
    From : August Abolins
    Subject : SciNet Point


    So the packet itself *seems* to be ok, there's no area on the message,

    It's a quite simple program. It only shows the contents of the pkt and message headers inside the .pkt file. It skips the text part, including the kludges it contains.

    but Mystic isn't seeing the message as netmail. Could it be because
    of the PKT password?

    No.

    Just not sure what makes a netmail message.. netmail:

    The only distinction is the AREA:XXX line an echomail contains as first line of the text of a message. And a .pkt file can contain both at the same time, and in no particular order...


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/1.1 to August Abolins on Sat Jan 9 08:49:00 2021
    Hi August.

    08 Jan 21 16:21:00, you wrote to me:

    ** On Friday 08.01.21 - 20:59, Tommi Koivula wrote to Jay Harris:

    Thanks, I got both this and the direct netmail.

    Good! So it seems that there is something wrong with OpenXP... Well, it
    is a _point_ software. Points should send all mail via their boss.

    It's point software with perks, like not discriminating with
    other systems by mishandling established session pwds, it seems.

    Even if there is an incorrect pkt password in the .pkt, why does Mystic think the message is echomail?

    August, please send me a crash netmail to 2:221/6. I'll catch the .pkt before processing.

    'Tommi

    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)
  • From August Abolins@1:153/757.2 to Tommi Koivula on Sat Jan 9 08:03:02 2021
    Even if there is an incorrect pkt password in the .pkt, why does Mystic think the message is echomail?

    That would be a Mystic problem? :/
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
  • From Tommi Koivula@2:221/1 to August Abolins on Sat Jan 9 18:33:38 2021
    09 Jan 21 08:03, August Abolins wrote to Tommi Koivula:


    Even if there is an incorrect pkt password in the .pkt, why does Mystic
    think the message is echomail?

    That would be a Mystic problem? :/

    That's what think, yes.

    'Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/1)
  • From August Abolins@2:221/1.58 to Jay Harris on Sat Jan 9 22:55:00 2021
    Hello Jay!

    ** On Friday 08.01.21 - 16:50, Jay Harris wrote to Wilfred van Velzen:

    pktview V1.1, Copyright WvV 1998, 2016

    Dest. Node addr: 1:229/664.0
    Orig. Node addr: 2:221/1.58
    QDest Zone : 1
    QOrig Zone : 2
    Aux Net : 0
    Date : 2021/01/07
    Time : 00:00:00
    Baud : 0
    Pkt Type : 2
    ProdCode : 233
    Revision Major : 3
    Revision Minor : 20
    Password : (hidden)
    ^^^^^^^^

    Nice catch, but you inadvertantly revealed it in a previous
    message.

    ;)


    So the packet itself *seems* to be ok, there's no area on the message,
    but Mystic isn't seeing the message as netmail. Could it be because of the PKT password?

    Are you able to receive netmail as netmail from other sources?


    Whereas Tommi's netmail form before:

    + Jan 08 11:55:12 Process: Importing EchoMail
    + Jan 08 11:55:12 Waiting for BUSY nodes
    + Jan 08 11:55:12 Importing 901beb06.pkt (2:221/1.1 to 1:229/664)
    + Jan 08 11:55:12 Netmail from Tommi Koivula (2:221/1.1) to Jay Harris (1:229/664) + Jan 08 11:55:12 Results: 0 echo, 1 net, 0 dupes, 0 tossed in 0.08s

    OK.. so you're saying Tommi's netmails are being recognized as
    netmails, but mine were not? (I say "were" because now that we
    have a Boss-Point relationship, the problem has gone away?)

    Perhaps someone else who runs OpenXP could drop some crash
    netmails to you for further comparison?
    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From Tommi Koivula@2:221/1.2 to August Abolins on Sun Jan 10 11:58:00 2021
    Whereas Tommi's netmail form before:

    + Jan 08 11:55:12 Process: Importing EchoMail
    + Jan 08 11:55:12 Waiting for BUSY nodes
    + Jan 08 11:55:12 Importing 901beb06.pkt (2:221/1.1 to 1:229/664)
    + Jan 08 11:55:12 Netmail from Tommi Koivula (2:221/1.1) to Jay Harris JH>> (1:229/664) + Jan 08 11:55:12 Results: 0 echo, 1 net, 0 dupes, 0 tossed JH>> in 0.08s

    OK.. so you're saying Tommi's netmails are being recognized as
    netmails, but mine were not? (I say "were" because now that we
    have a Boss-Point relationship, the problem has gone away?)

    Perhaps someone else who runs OpenXP could drop some crash
    netmails to you for further comparison?

    Perhaps.. I just need to learn how. ;)

    'Tommi

    --- OpenXP 5.0.48
    * Origin: -----> (2:221/1.2)
  • From Charles Pierson@1:106/127 to August Abolins on Sun Jan 10 05:53:50 2021
    On 09 Jan 2021, August Abolins said the following...
    Password : (hidden)
    ^^^^^^^^

    Nice catch, but you inadvertantly revealed it in a previous
    message.

    You can always change it via Areafix zi believe.

    So the packet itself *seems* to be ok, there's no area on the message but Mystic isn't seeing the message as netmail. Could it be because the PKT password?

    Are you able to receive netmail as netmail from other sources?


    Whereas Tommi's netmail form before:

    + Jan 08 11:55:12 Process: Importing EchoMail
    + Jan 08 11:55:12 Waiting for BUSY nodes
    + Jan 08 11:55:12 Importing 901beb06.pkt (2:221/1.1 to 1:229/664) + Jan 08 11:55:12 Netmail from Tommi Koivula (2:221/1.1) to Jay Ha (1:229/664) + Jan 08 11:55:12 Results: 0 echo, 1 net, 0 dupes, 0 tos in 0.08s

    OK.. so you're saying Tommi's netmails are being recognized as
    netmails, but mine were not? (I say "were" because now that we
    have a Boss-Point relationship, the problem has gone away?)

    Perhaps someone else who runs OpenXP could drop some crash
    netmails to you for further comparison?

    Is OpenXP available for Linux? I want to experiment with point software with this setup anyway.

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: theoasisbbs.ddns.net:1357 (1:106/127)
  • From August Abolins@2:221/1.58 to Tommi Koivula on Sun Jan 10 07:40:00 2021
    Hello Tommi!

    ** On Sunday 10.01.21 - 11:58, Tommi Koivula wrote to August Abolins:

    Perhaps someone else who runs OpenXP could drop some crash
    netmails to you for further comparison?

    Perhaps.. I just need to learn how. ;)

    There is a Linux version you could play with.

    Hop over to http://openxp.kolico.ca and look under "Get OpenXP"

    And, I would highly recommend simply using the step-by-step walk-
    through in the Quick-start guide. There are some distintions to
    be aware up between the Win and Linux versions during install.

    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From Tommi Koivula@2:221/1.2 to August Abolins on Sun Jan 10 15:16:00 2021
    Perhaps someone else who runs OpenXP could drop some crash
    netmails to you for further comparison?

    Perhaps.. I just need to learn how. ;)

    There is a Linux version you could play with.

    Hop over to http://openxp.kolico.ca and look under "Get OpenXP"

    And, I would highly recommend simply using the step-by-step walk-
    through in the Quick-start guide. There are some distintions to
    be aware up between the Win and Linux versions during install.

    Well, I have this win32 version running. I still don't know how to send
    crash netmail.

    Never mind. :)

    'Tommi

    --- OpenXP 5.0.48
    * Origin: -----> (2:221/1.2)
  • From Martin Foster@2:221/360 to Charles Pierson on Sun Jan 10 15:19:47 2021
    Hi Charles!

    On 10/01/2021 11:53, Charles Pierson : August Abolins wrote:

    [snip]
    Is OpenXP available for Linux? I want to experiment with point software with this setup anyway.

    https://openxp.uk/linux/

    Regards,
    Martin

    --- Thunderbird 78.6.0
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Charles Pierson@1:106/127 to Martin Foster on Sun Jan 10 07:30:25 2021
    On 10 Jan 2021, Martin Foster said the following...
    Is OpenXP available for Linux? I want to experiment with point software this setup anyway.

    https://openxp.uk/linux/


    I'm not sure if those will work for me, This set-up is basically a Raspberry Pi, at least tge arrmf hardware. But I'll try anything once

    .

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: theoasisbbs.ddns.net:1357 (1:106/127)
  • From August Abolins@2:221/1.58 to Tommi Koivula on Sun Jan 10 08:35:00 2021
    Hello Tommi!

    ** On Sunday 10.01.21 - 15:16, Tommi Koivula wrote to August Abolins:

    Well, I have this win32 version running. I still don't know how to send crash netmail.

    Never mind. :)

    -+- OpenXP 5.0.48
    + Origin: -----> (2:221/1.2)


    Yeah.. nevermind. It appears that I have conditioned myself to skip reading Origin lines.

    To send crash.. when first go to Save a message you will see this:


    Public message (quote) Ŀ

    To: /FIDO/POINTS

    Recipient Tommi Koivula

    Subject SciNet Point

    Server 2:221/1 Code: ROT13 possible

    Size 497 Bytes Copies: none

    Send... Change...
    Yes No Internal Special Subj. Server Code Text

    But before you select the default >YES<, press S[p]ecial. There, you will have to option to toggle Crash.



    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From Tommi Koivula@2:221/1.1 to August Abolins on Sun Jan 10 15:57:00 2021
    Hi August.

    10 Jan 21 08:35:00, you wrote to me:

    Yeah.. nevermind. It appears that I have conditioned myself to skip reading
    Origin lines.

    :)

    But before you select the default >YES<, press S[p]ecial. There, you will have to option to toggle Crash.

    Hidden! :D

    But this is what it says:

    === Cut ===
    ┌─ Private message (quote) ──────────────────────────────────────────────────┐
    │ │
    │ To: August Abolins@2:221/1.58 │
    │ │
    │ Subject ┌─ Error ─────────────────────────────────────────────┐ │
    │ │ │ │
    │ Server │ Plese send message to Server as a normal netmail. │ │
    │ │ │ │
    │ Size └─────────────────────────────────────────────────────┘ │
    │ │
    │ Special... │
    │ Park Date RecConf withoutSig delete Crash PGP Back │
    └────────────────────────────────────────────────────────────────────────────┘
    === Cut ===

    'Tommi

    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)
  • From August Abolins@2:221/1.58 to Tommi Koivula on Sun Jan 10 10:00:00 2021
    Hello Tommi!

    ** On Sunday 10.01.21 - 15:57, Tommi Koivula wrote to August Abolins:

    But before you select the default >YES<, press S[p]ecial. There, you
    will have to option to toggle Crash.

    Hidden! :D

    But this is what it says:

    === Cut ===
    Abolins@2:221/1.58
    Plese send
    message to Server as a normal netmail.
    Park Date RecConf withoutSig delete Crash PGP Back
    === Cut ===

    -+-
    + Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)


    AH! That's because we have a secure/direct (server/client)
    setup.

    But you should be able to send Crash from 2:221/1.1 via 2:221/6.

    That's what I did when you asked me to test a message from my
    point to your 2:221/6 system.

    --
    ../|ug

    --- OpenXP 5.0.48
    * Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
  • From Tommi Koivula@2:221/1.2 to August Abolins on Sun Jan 10 18:05:00 2021
    AH! That's because we have a secure/direct (server/client)
    setup.

    But you should be able to send Crash from 2:221/1.1 via 2:221/6.

    That's what I did when you asked me to test a message from my
    point to your 2:221/6 system.

    Ok. Not easy but I did it. ;)

    'Tommi


    --- OpenXP 5.0.48
    * Origin: -----> (2:221/1.2)
  • From Tommi Koivula@2:221/1.2 to Jay Harris on Sun Jan 10 18:11:00 2021
    OK.. so you're saying Tommi's netmails are being recognized as
    netmails, but mine were not? (I say "were" because now that we
    have a Boss-Point relationship, the problem has gone away?)

    Correct, if you netmail me using your SciNet point address it'll come through, but if you send from another point it'll get tossed as bad.

    Tommi's netmail came through no problem, it looks like he's using GoldED as an editor along with Husky/Bink to toss & send.

    I just sent you netmail crash from OpenXP.

    18:07:37 ncmodem: Log: = CONNECT
    18:07:40 ncmodem: Log: OPT CRAM-MD5-9be4cb5a79d020a6103b4d69d640595e
    18:07:40 ncmodem: Log: SYS Northern Realms
    18:07:40 ncmodem: Log: ZYZ Warpslide
    18:07:40 ncmodem: Log: TIME Sun, 10 Jan 2021 11:07:40 -0500
    18:07:40 ncmodem: Log: VER Mystic/1.12A47 binkp/1.0
    18:07:40 ncmodem: Log: BUILD 2021/01/05 00:11:26 Raspberry Pi/32
    18:07:41 ncmodem: Log: non-secure
    18:07:41 ncmodem: Log: QSIZE 0 files 0 bytes
    18:07:41 ncmodem: Log: * Sent 10180736.PKT, 416b
    18:07:41 ncmodem: Log: = hangup
    18:07:41 ncmodem: Log: - exiting

    'Tommi

    --- OpenXP 5.0.48
    * Origin: -----> (2:221/1.2)
  • From Jay Harris@1:229/664 to August Abolins on Sun Jan 10 07:29:18 2021
    On 09 Jan 2021, August Abolins said the following...

    Nice catch, but you inadvertantly revealed it in a previous
    message.

    Yeah, that's my bad. *facepalm*

    OK.. so you're saying Tommi's netmails are being recognized as
    netmails, but mine were not? (I say "were" because now that we
    have a Boss-Point relationship, the problem has gone away?)

    Correct, if you netmail me using your SciNet point address it'll come through, but if you send from another point it'll get tossed as bad.

    Tommi's netmail came through no problem, it looks like he's using GoldED as an editor along with Husky/Bink to toss & send.


    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Jay Harris@1:229/664 to Tommi Koivula on Sun Jan 10 12:24:11 2021
    On 10 Jan 2021, Tommi Koivula said the following...

    I just sent you netmail crash from OpenXP.

    That one came through & I see it in my netmail base. Also replied as a test.

    + Jan 10 11:07:41 Process: Importing EchoMail
    + Jan 10 11:07:41 Waiting for BUSY nodes
    + Jan 10 11:07:41 Importing 10180736.PKT (2:221/1.2 to 1:229/664)
    + Jan 10 11:07:41 Netmail from Tommi Koivula (2:221/1.2) to Jay Harris (1:229/664)
    + Jan 10 11:07:41 Results: 0 echo, 1 net, 0 dupes, 0 tossed in 0.09s


    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From August Abolins@1:153/757.2 to Jay Harris on Mon Jan 11 10:38:47 2021
    On 10 Jan 2021, Tommi Koivula said the following...

    I just sent you netmail crash from OpenXP.

    That one came through & I see it in my netmail base. Also replied as a test.

    + Jan 10 11:07:41 Process: Importing EchoMail
    + Jan 10 11:07:41 Waiting for BUSY nodes
    + Jan 10 11:07:41 Importing 10180736.PKT (2:221/1.2 to 1:229/664)
    + Jan 10 11:07:41 Netmail from Tommi Koivula (2:221/1.2) to Jay Harris (1:229/664)
    + Jan 10 11:07:41 Results: 0 echo, 1 net, 0 dupes, 0 tossed in 0.09s


    Interesting. So, why was it failing when I did the same thing before that?
    Did you tweak something in the meantime?

    Maybe we can get Martin Foster to send a test a crash netmail too.

    Or.. I could assign myself a temp address like 1:999/9999 (or one of the temporary ones in the nodelist) and send you a packet to investigate?
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
  • From Jay Harris@1:229/664 to August Abolins on Mon Jan 11 14:05:16 2021
    On 11 Jan 2021, August Abolins said the following...

    Interesting. So, why was it failing when I did the same thing before that? Did you tweak something in the meantime?

    I'm not sure why Tommi's worked and yours doesn't. I've not changed anything on my end.

    Maybe we can get Martin Foster to send a test a crash netmail too.

    Yup, if Martin wants to send one my way, I'll certainly check to see if I get it.

    Or.. I could assign myself a temp address like 1:999/9999 (or one of the temporary ones in the nodelist) and send you a packet to investigate?

    That works as well. That may help determine whether it's OpenXP in general or maybe just your OpenXP? I'm really at a loss as to whats happening.


    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Martin Foster@2:310/31.3 to August Abolins on Tue Jan 12 09:58:00 2021
    Hello August!

    *** Monday 11.01.21 at 10:38, August Abolins wrote to Jay Harris:

    [snip]
    Maybe we can get Martin Foster to send a test a crash netmail too.

    Test crash netmail sent at 09:54(UTC) :)

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Jay Harris@1:229/664 to Martin Foster on Tue Jan 12 09:36:57 2021
    On 12 Jan 2021, Martin Foster said the following...

    Test crash netmail sent at 09:54(UTC) :)

    No dice:

    + Jan 12 04:54:50 Process: Importing EchoMail
    + Jan 12 04:54:50 Waiting for BUSY nodes
    + Jan 12 04:54:50 Importing 12095445.PKT (2:310/31.3 to 1:229/664)
    ! Jan 12 04:54:50 No echomail node configured for 2:310/31.3
    ! Jan 12 04:54:51 Moving /home/pi/mystic/echomail/in/unsecure/12095445.PKT to /home/pi/mystic/echomail/bad/12095445.PKT
    + Jan 12 04:54:51 Results: 0 echo, 0 net, 0 dupes, 0 tossed in 0.64s


    pktview V1.1, Copyright WvV 1998, 2016

    Dest. Node addr: 1:229/664.0
    Orig. Node addr: 2:310/31.3
    QDest Zone : 1
    QOrig Zone : 2
    Aux Net : 0
    Date : 2021/01/12
    Time : 00:00:00
    Baud : 0
    Pkt Type : 2
    ProdCode : 233
    Revision Major : 3
    Revision Minor : 20
    Password : (hidden) <-- There is one set & visible
    Capability Word: 0001
    Capability Val.: 0001
    Product data : 00000000

    Date Time To From Subject Area ----------------------------------------------------------------------------- 12 Jan 21 09:54:00 Jay Harris Martin Foster Test shot

    1 messages in this .pkt file.


    Jay

    --- Mystic BBS v1.12 A47 2021/01/05 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Martin Foster@2:310/31.3 to Jay Harris on Tue Jan 12 15:30:00 2021
    Hello Jay!

    *** Tuesday 12.01.21 at 09:36, Jay Harris wrote to Martin Foster:

    Test crash netmail sent at 09:54(UTC) :)

    No dice:

    :(

    I've sent another test shot with one of my other setups at 15:22(UTC) and
    the packet should *not* contain a password.

    [snip]
    Password : (hidden) <-- There is one set & visible

    Yeah well, OpenXP shouldn't be doing this but this matter is being investigated.

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:250/1.333 to All on Fri Jan 15 11:10:32 2021
    Greetings All!

    Sunday December 27 2020 11:07, Martin Foster wrote to All:

    OpenXP 5.0.48 has been released

    Something that may have gone unnoticed is that *outgoing* mail packets(*.pkt) are now backed up in the \SPOOL directory. Echomail and *routed* netmail packets are backed up in the appropriate sub-directory and will be automatically deleted in due course, whereas *crash* netmail packets will be backed up in the *root* of the \SPOOL directory and will *not* be automatically deleted.

    Regards,
    Martin

    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Bitz-Box - Bradford - UK (2:250/1.333)
  • From Martin Foster@2:310/31.3 to August Abolins on Tue Jan 19 11:27:00 2021
    Hello August!

    *** Friday 08.01.21 at 16:21, August Abolins wrote to Tommi Koivula:

    Thanks, I got both this and the direct netmail.

    Good! So it seems that there is something wrong with OpenXP... Well, it
    is a _point_ software. Points should send all mail via their boss.

    It's point software with perks, like not discriminating with
    other systems by mishandling established session pwds, it seems.

    :(

    Will have to report that situation.

    Fixed in the next release.

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: OpenXP-Team (2:310/31.3)
  • From Martin Foster@2:310/31.3 to All on Wed Jan 20 11:43:00 2021
    Greetings All!

    *** Friday 15.01.21 at 11:10, Martin Foster wrote to All:

    OpenXP 5.0.48 has been released

    Something that may have gone unnoticed is that *outgoing* mail packets(*.pkt) are now backed up in the \SPOOL directory. Echomail and *routed* netmail packets are backed up in the appropriate sub-directory and will be automatically deleted in due course, whereas *crash* netmail packets will be backed up in the *root* of the \SPOOL directory and will *not* be automatically deleted.

    Update .....

    All .REQ files will also be backed up in the root of the \SPOOL directory
    but will *not* be automatically deleted.

    Regards,
    Martin

    --- OpenXP 5.0.48
    * Origin: OpenXP-Team (2:310/31.3)