• FMail 2.3.0.0 public beta release

    From Wilfred van Velzen@2:280/464 to All on Sat Mar 16 18:30:12 2024

    Hi All,

    2024-03-15 - 2.3.0.0-Beta

    This public beta release is mainly about the release of fconfig for linux.
    So FMail is now fully linux compatible.
    There are a few minor changes in the Windows version too.
    See the ChangeLog file for the full details.

    Downloads:

    http://www.vlzn.nl/fmail/files/FMail-lnx32-2.3.0.0-Beta20240315.zip http://www.vlzn.nl/fmail/files/FMail-lnx64-2.3.0.0-Beta20240315.zip

    http://www.vlzn.nl/fmail/files/FMailW32-2.3.0.0-Beta20240314.zip http://www.vlzn.nl/fmail/files/FMailW64-2.3.0.0-Beta20240314.zip


    For the linux version, instead of using above statically linked executables,
    I recommend, if you have the setup/tools for it,
    to download the sources with git, and compile it yourself.

    These are the steps/commands:

    # git clone git://git.code.sf.net/p/fmail/code FMail
    # cd FMail
    # git checkout --track origin/fconfig_linux
    # mkdir cmake-build
    # cd cmake-build
    # cmake ..
    # make


    I tested the linux version of fconfig on a few systems:

    Ubuntu 20.04.6 LTS (konsole remote ssh)
    Ubuntu 22.04.3 LTS (konsole remote ssh)
    openSUSE Leap 42.1 (konsole local, putty remote ssh)
    SUSE Linux Enterprise Server 15 SP5 (konsole remote ssh, putty remote ssh)

    Only on the latter I had some issues with messed up screens, until I changed some
    terminal settings. After which it behaved just as well as in the others.


    I would appreciate any feedback, especially on the behaviour of fconfig for linux, you can give!


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.0-B20240315
    * Origin: FMail development HQ (2:280/464)
  • From Stephen Walsh@3:633/280 to Wilfred van Velzen on Sun Mar 17 12:08:46 2024

    Hello Wilfred!

    16 Mar 24 18:30, you wrote to all:

    For the linux version, instead of using above statically linked executables, I recommend, if you have the setup/tools for it, to
    download the sources with git, and compile it yourself.


    See netmail...



    Stephen


    --- GoldED+/LNX 1.1.5-b20240302
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)
  • From Tommi Koivula@2:221/6.26 to Wilfred van Velzen on Sun Mar 17 08:55:36 2024
    Hi Wilfred.

    16 Mar 24 18:30, you wrote to All:

    For the linux version, instead of using above statically linked executables,
    I recommend, if you have the setup/tools for it,
    to download the sources with git, and compile it yourself.

    Compiled in Raspberry PI3 running Debian 32bit. No problems.

    Started fconfig from scratch and imported areas.bbs created from husky setup. So this fmail setup runs in parallel with husky/hpt now. Seems ok :)

    Next we need fconfig to import husky config. :D

    'Tommi

    --- FMail-lnx 2.3.0.0-B20240317
    * Origin: Linux 6.1.21-v7+ armv7l (2:221/6.26)
  • From Wilfred van Velzen@2:280/464 to Stephen Walsh on Sun Mar 17 12:41:34 2024
    Hi Stephen,

    On 2024-03-17 12:08:46, you wrote to me:

    For the linux version, instead of using above statically linked
    executables, I recommend, if you have the setup/tools for it, to
    download the sources with git, and compile it yourself.

    See netmail...

    Answered. ;)

    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.0-B20240315
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sun Mar 17 12:46:28 2024
    Hi Tommi,

    On 2024-03-17 08:55:37, you wrote to me:

    For the linux version, instead of using above statically linked
    executables, I recommend, if you have the setup/tools for it, to
    download the sources with git, and compile it yourself.

    Compiled in Raspberry PI3 running Debian 32bit. No problems.

    Wow! Wouldn't have guessed that was possible out of the box! ;-)

    Started fconfig from scratch and imported areas.bbs created from husky setup. So this fmail setup runs in parallel with husky/hpt now. Seems ok :)

    Great!

    Next we need fconfig to import husky config. :D

    I'll leave that to someone else. ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.0-B20240315
    * Origin: FMail development HQ (2:280/464)
  • From Stephen Walsh@3:633/280 to Wilfred van Velzen on Mon Mar 18 12:13:26 2024

    Hello Wilfred!

    17 Mar 24 12:41, you wrote to me:

    For the linux version, instead of using above statically linked
    executables, I recommend, if you have the setup/tools for it, to
    download the sources with git, and compile it yourself.

    See netmail...

    Answered. ;)


    For the onlookers:

    Just for the thrill of it, I compiled it on Linux M68K! (What would we find under the hood?
    Little endian/big endian issues?)

    Fconfig config actually runs, but did a Segmentation fault when the ssh session was 80x24
    screen size. It was fine at 91x28.

    Was able to move around and look at things, but didn't do any more. Fmail about works..

    Though as I don't have a fmail.cfg file yet, nothing else works.

    (Some compile issues removed for this post)

    Latter:

    I've now created a fmail config, and will through some packets at it tonight...


    The issue now is a editor, as they have issues on M68K..

    I'll see if I can compile MagickaBBS again, as it supports jam msg bases...


    Stephen


    --- GoldED+/LNX 1.1.5-b20240302
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)
  • From Wilfred van Velzen@2:280/464.112 to Stephen Walsh on Mon Mar 18 08:20:42 2024
    Hi Stephen,

    On 18 Mar 24 12:13, Stephen Walsh wrote to Wilfred van Velzen:
    about: "FMail 2.3.0.0 public beta release":

    Fconfig config actually runs, but did a Segmentation fault when the
    ssh session was 80x24 screen size. It was fine at 91x28.

    This was due to a wrong check for the screen size, which I set for debugging, but forgot to change back.

    As FConfig is originally a DOS program it expects a terminal of at least 80x25. Yesterday I created a version that will run in a 80x24 terminal for linux (there was a more or less unused line at the bottom of the screen ;-)). I have to do some more testing before I commit the code to git though...

    Wilfred.

    --- FMail-W64 2.3.0.0-B20240314
    * Origin: point@work (2:280/464.112)
  • From Stephen Walsh@3:633/280 to Wilfred van Velzen on Tue Mar 19 11:35:46 2024

    Hello Wilfred!

    Source was 21:1/195 to 21:1/195.1

    pkt.zip & fmailm68k.zip in your inbound.... If you want to do something with M68K support...
    (This is after all just something todo on my part!)


    FMail-lnx-m68k-2.3.0.0-Beta20240317 - The Fast Echomail Processor
    Copyright (C) 1991-2024 by FMail Developers - All rights reserved

    Scanning netmail directory...

    Tossing messages...

    Packet is addressed to another node (256/49920); packet file: /home/vk3heg/fmail/inbound/f8d28501.pkt is
    renamed with extension: '.wrong_destination'

    Packet is addressed to another node (256/49920); packet file: /home/vk3heg/fmail/inbound/f8d7dd01.pkt is
    renamed with extension: '.wrong_destination'

    Packet is addressed to another node (256/49920); packet file: /home/vk3heg/fmail/inbound/f87f8a01.pkt is
    renamed with extension: '.wrong_destination'

    Updating actual message base files...

    Netmail: 0, Personal: 0, Hudson: 0, JAMbase: 0
    Msgbase net: 0, echo: 0, dup: 0, bad: 0

    Toss Active: 0.070 sec.




    Stephen


    --- GoldED+/LNX 1.1.5-b20240302
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)
  • From Wilfred van Velzen@2:280/464.112 to Stephen Walsh on Tue Mar 19 08:09:16 2024
    Hi Stephen,

    On 19 Mar 24 11:35, Stephen Walsh wrote to Wilfred van Velzen:
    about: "FMail 2.3.0.0 public beta release":

    Source was 21:1/195 to 21:1/195.1

    pkt.zip & fmailm68k.zip in your inbound.... If you want to do something with M68K support... (This is after all just something todo on my part!)

    Not really. ;-) I think there are more important things on the todo list.

    FMail-lnx-m68k-2.3.0.0-Beta20240317 - The Fast Echomail Processor Copyright (C) 1991-2024 by FMail Developers - All rights reserved

    Scanning netmail directory...

    Tossing messages...

    Packet is addressed to another node (256/49920); packet file: /home/vk3heg/fmail/inbound/f8d28501.pkt is renamed with extension: '.wrong_destination'

    256/49920 = 1/195, if you swap bytes. So a typical endianess problem...


    Wilfred.

    --- FMail-W64 2.3.0.1-B20240318
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464 to Stephen Walsh on Tue Mar 19 22:33:22 2024
    Hi Stephen,

    On 2024-03-18 08:20:42, I wrote to you:

    Fconfig config actually runs, but did a Segmentation fault when the
    ssh session was 80x24 screen size. It was fine at 91x28.

    This was due to a wrong check for the screen size, which I set for debugging, but forgot to change back.

    As FConfig is originally a DOS program it expects a terminal of at least 80x25. Yesterday I created a version that will run in a 80x24 terminal for
    linux (there was a more or less unused line at the bottom of the screen ;-)). I have to do some more testing before I commit the code to git though...

    fconfig for linux is now 80x24. You can get the source from the git repository.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From Stephen Walsh@3:633/280 to Wilfred van Velzen on Thu Mar 21 12:21:52 2024

    Hello Wilfred!

    19 Mar 24 08:09, you wrote to me:

    pkt.zip & fmailm68k.zip in your inbound.... If you want to do
    something with M68K support... (This is after all just something
    todo on my part!)

    Not really. ;-) I think there are more important things on the todo
    list.

    That's understandable, I doubt you'd have a huge M68K user base... Mostly a count of 1... #-)

    FMail-lnx-m68k-2.3.0.0-Beta20240317 - The Fast Echomail Processor
    [...]
    Packet is addressed to another node (256/49920); packet file:
    /home/vk3heg/fmail/inbound/f8d28501.pkt is renamed with
    extension: '.wrong_destination'

    256/49920 = 1/195, if you swap bytes. So a typical endianess
    problem...

    I just looked through what andrew did to add M68K support in Talisman BBS and it's not just a few lines of code...

    https://gitlab.com/apamment/talisman/-/commits/master?search=endian

    I still have it running, but only as a point in FSXNet...


    Stephen


    --- GoldED+/LNX 1.1.5-b20240302
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)
  • From Wilfred van Velzen@2:280/464.112 to Stephen Walsh on Thu Mar 21 08:10:32 2024
    Hi Stephen,

    On 21 Mar 24 12:21, Stephen Walsh wrote to Wilfred van Velzen:
    about: "FMail 2.3.0.0 public beta release":

    pkt.zip & fmailm68k.zip in your inbound.... If you want to do
    something with M68K support... (This is after all just something
    todo on my part!)

    Not really. ;-) I think there are more important things on the todo
    list.

    That's understandable, I doubt you'd have a huge M68K user base... Mostly a count of 1... #-)

    You are not using it! So 0. ;-)

    FMail-lnx-m68k-2.3.0.0-Beta20240317 - The Fast Echomail Processor
    [...]
    Packet is addressed to another node (256/49920); packet file:
    /home/vk3heg/fmail/inbound/f8d28501.pkt is renamed with
    extension: '.wrong_destination'

    256/49920 = 1/195, if you swap bytes. So a typical endianess
    problem...

    I just looked through what andrew did to add M68K support in Talisman BBS and it's not just a few lines of code...

    Making the pkt code endianness agnostic isn't a big task. My pktviewer code does it. I wrote it decades ago, so it would compile on both the Amiga and PC. ;-)

    But doing so for the three supported messagebases (msg, hudson, jam), is a huge pain in the ass, because the code for these is all over the place.


    Wilfred.

    --- FMail-W64 2.3.0.1-B20240319
    * Origin: point@work (2:280/464.112)
  • From Stephen Walsh@3:633/280 to Wilfred van Velzen on Sat Mar 23 10:36:58 2024

    Hello Wilfred!

    21 Mar 24 08:10, you wrote to me:

    Not really. ;-) I think there are more important things on the
    todo list.

    That's understandable, I doubt you'd have a huge M68K user
    base... Mostly a count of 1... #-)

    You are not using it! So 0. ;-)

    Yes. The use case is way out west on a deserted road looking at the ground. &-) Plus see latter in this message.

    I just looked through what andrew did to add M68K support in
    Talisman BBS and it's not just a few lines of code...

    Making the pkt code endianness agnostic isn't a big task. My pktviewer code does it. I wrote it decades ago, so it would compile on both the Amiga and PC. ;-)

    Do you want me to test it? Link to the code?

    But doing so for the three supported messagebases (msg, hudson, jam),
    is a huge pain in the ass, because the code for these is all over the place.

    It's a chicken & egg issue..

    Magicka supports JAM but is no longer supported.
    Talisman only supports squish, but is still supported!

    Both compile and work on M68K Linux!



    Stephen


    --- GoldED+/LNX 1.1.5-b20240302
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)
  • From Wilfred van Velzen@2:280/464 to Stephen Walsh on Sat Mar 23 01:37:42 2024
    Hi Stephen,

    On 2024-03-23 10:36:58, you wrote to me:

    I just looked through what andrew did to add M68K support in
    Talisman BBS and it's not just a few lines of code...

    Making the pkt code endianness agnostic isn't a big task. My pktviewer
    code does it. I wrote it decades ago, so it would compile on both the
    Amiga and PC. ;-)

    Do you want me to test it? Link to the code?

    http://www.vlzn.nl/fmail/files/pktview-1.1-src.zip

    But doing so for the three supported messagebases (msg, hudson, jam),
    is a huge pain in the ass, because the code for these is all over the
    place.

    It's a chicken & egg issue..

    Indeed.

    Magicka supports JAM but is no longer supported.
    Talisman only supports squish, but is still supported!

    Both compile and work on M68K Linux!

    Maybe I'll try to make the pkt code endianess agnostic first. If that works for you I could look at the message base code.

    Does your compiler/environment have endian.h ?


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From Stephen Walsh@3:633/280 to Wilfred van Velzen on Sat Mar 23 17:23:44 2024

    Hello Wilfred!

    23 Mar 24 01:37, you wrote to me:

    Do you want me to test it? Link to the code?

    http://www.vlzn.nl/fmail/files/pktview-1.1-src.zip

    Compiles and works:

    vk3heg@a3000:~/source/pktview$ ./pktview -v fc5c2f01.pkt
    pktview V1.1, Copyright WvV 1998, 2016

    Dest. Node addr: 21:1/195.1
    Orig. Node addr: 21:1/195.0
    QDest Zone : 21
    QOrig Zone : 21
    Aux Net : 0
    Date : 2024/03/22
    Time : 03:09:46
    Baud : 0
    Pkt Type : 2
    ProdCode : 4351
    Revision Major : 1
    Revision Minor : 9
    Password :
    Capability Word: 0001
    Capability Val.: 0001
    Product data : 00000000

    001 Orig. : 1/195
    Dest. : 1/195
    Attribute: 0100
    Cost : 0
    Date : 21 Mar 24 17:09:11
    To : pSYKo
    From : Zip
    Subject : Re: Msg Test
    Area : FSX_TST


    1 messages in this .pkt file.

    But doing so for the three supported messagebases (msg, hudson,
    jam), is a huge pain in the ass, because the code for these is
    all over the place.

    It's a chicken & egg issue..

    Indeed.

    Magicka supports JAM but is no longer supported.
    Talisman only supports squish, but is still supported!

    Both compile and work on M68K Linux!

    Maybe I'll try to make the pkt code endianess agnostic first. If that works for you I could look at the message base code.

    It's upto you if you want to spend the time doing it... This was just a test to see if fmail etc, would
    even compile and run...

    Talsiman's tosser works fine. The only thing I wish it did was toss the messages into the msg base in
    date order. The point system doesn't have a set poll schedule.

    Does your compiler/environment have endian.h ?

    Yes, it is after all Debian Linux M68K:

    vk3heg@a3000:~/source/pktview$ whereis endian.h
    endian.h: /usr/include/endian.h


    Stephen


    --- GoldED+/LNX 1.1.5-b20240302
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)
  • From Wilfred van Velzen@2:280/464 to Stephen Walsh on Sat Mar 23 11:32:22 2024
    Hi Stephen,

    On 2024-03-23 17:23:44, you wrote to me:

    Do you want me to test it? Link to the code?

    http://www.vlzn.nl/fmail/files/pktview-1.1-src.zip

    Compiles and works:

    To be sure: This was on M68K? In that case: Cool! ;-)

    vk3heg@a3000:~/source/pktview$ ./pktview -v fc5c2f01.pkt
    pktview V1.1, Copyright WvV 1998, 2016

    Magicka supports JAM but is no longer supported.
    Talisman only supports squish, but is still supported!

    Both compile and work on M68K Linux!

    Maybe I'll try to make the pkt code endianess agnostic first. If that
    works for you I could look at the message base code.

    It's upto you if you want to spend the time doing it... This was just a test
    to see if fmail etc, would even compile and run...

    And fconfig works and runs too, I think you said so. But if it doesn't there isn't much sense in trying to go for a different endianess support.

    Talsiman's tosser works fine. The only thing I wish it did was toss
    the messages into the msg base in date order. The point system doesn't have a set poll schedule.

    FMail doesn't do that either.

    Does your compiler/environment have endian.h ?

    Yes, it is after all Debian Linux M68K:

    vk3heg@a3000:~/source/pktview$ whereis endian.h
    endian.h: /usr/include/endian.h

    Can you sent it to me, for comparison, with the one on my linux?

    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From Stephen Walsh@3:633/280 to Wilfred van Velzen on Sun Mar 24 13:03:56 2024

    Hello Wilfred!

    23 Mar 24 11:32, you wrote to me:

    Compiles and works:
    To be sure: This was on M68K? In that case: Cool! ;-)

    Yes Linux on my Amiga 3000... Btw: Fconfig does work and creates a config file.

    And just to confirm:

    https://www.youtube.com/watch?v=caZtHdNe0Ag

    That is my Amiga 3000 in this video.. #-) (Eeven with the fact errors & fud %$#^&% )

    Does your compiler/environment have endian.h ?
    Yes, it is after all Debian Linux M68K:

    vk3heg@a3000:~/source/pktview$ whereis endian.h
    endian.h: /usr/include/endian.h

    Can you sent it to me, for comparison, with the one on my linux?

    There's not much in it:

    /* Copyright (C) 1992-2023 Free Software Foundation, Inc.
    This file is part of the GNU C Library.

    The GNU C Library is free software; you can redistribute it and/or
    modify it under the terms of the GNU Lesser General Public
    License as published by the Free Software Foundation; either
    version 2.1 of the License, or (at your option) any later version.

    The GNU C Library is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
    Lesser General Public License for more details.

    You should have received a copy of the GNU Lesser General Public
    License along with the GNU C Library; if not, see
    <https://www.gnu.org/licenses/>. */

    #ifndef _ENDIAN_H
    #define _ENDIAN_H 1

    #include <features.h>

    /* Get the definitions of __*_ENDIAN, __BYTE_ORDER, and __FLOAT_WORD_ORDER. */ #include <bits/endian.h>

    #ifdef __USE_MISC
    # define LITTLE_ENDIAN __LITTLE_ENDIAN
    # define BIG_ENDIAN __BIG_ENDIAN
    # define PDP_ENDIAN __PDP_ENDIAN
    # define BYTE_ORDER __BYTE_ORDER
    #endif

    #if defined __USE_MISC && !defined __ASSEMBLER__
    /* Conversion interfaces. */
    # include <bits/byteswap.h>
    # include <bits/uintn-identity.h>

    # if __BYTE_ORDER == __LITTLE_ENDIAN
    # define htobe16(x) __bswap_16 (x)
    # define htole16(x) __uint16_identity (x)
    # define be16toh(x) __bswap_16 (x)
    # define le16toh(x) __uint16_identity (x)

    # define htobe32(x) __bswap_32 (x)
    # define htole32(x) __uint32_identity (x)
    # define be32toh(x) __bswap_32 (x)
    # define le32toh(x) __uint32_identity (x)

    # define htobe64(x) __bswap_64 (x)
    # define htole64(x) __uint64_identity (x)
    # define be64toh(x) __bswap_64 (x)
    # define le64toh(x) __uint64_identity (x)

    # else
    # define htobe16(x) __uint16_identity (x)
    # define htole16(x) __bswap_16 (x)
    # define be16toh(x) __uint16_identity (x)
    # define le16toh(x) __bswap_16 (x)

    # define htobe32(x) __uint32_identity (x)
    # define htole32(x) __bswap_32 (x)
    # define be32toh(x) __uint32_identity (x)
    # define le32toh(x) __bswap_32 (x)

    # define htobe64(x) __uint64_identity (x)
    # define htole64(x) __bswap_64 (x)
    # define be64toh(x) __uint64_identity (x)
    # define le64toh(x) __bswap_64 (x)
    # endif
    #endif

    #endif /* endian.h */





    Stephen


    --- GoldED+/LNX 1.1.5-b20240302
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)
  • From Wilfred van Velzen@2:280/464 to Stephen Walsh on Sun Mar 24 13:25:52 2024
    Hi Stephen,

    On 2024-03-24 13:03:56, you wrote to me:

    Compiles and works:
    To be sure: This was on M68K? In that case: Cool! ;-)

    Yes Linux on my Amiga 3000... Btw: Fconfig does work and creates a config file.

    Good!

    And just to confirm:

    https://www.youtube.com/watch?v=caZtHdNe0Ag

    That is my Amiga 3000 in this video.. #-) (Eeven with the fact errors & fud
    %$#^&% )

    Nice! ;-)

    vk3heg@a3000:~/source/pktview$ whereis endian.h
    endian.h: /usr/include/endian.h

    Can you sent it to me, for comparison, with the one on my linux?

    There's not much in it:

    It's just to verify you have the same functions available. And it's almost the same as mine, so that is good!


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)