• Crashmail issues

    From Flavio Bessa@4:801/189.1 to All on Fri Dec 16 20:11:22 2016
    Hello everybody.

    I am setting up a system with Crashmail/JamNNTPD to run under Linux. All went well, I can toss messages into the system, but when I try to scan for messages to export I get the following error message:

    ^ 16-Dec-16 14:10:09 Scanning all areas for messages to export
    ! 16-Dec-16 14:10:09 Failed to read message #231 in JAM messagebase "/home/flbessa/fido/echo/BR_BBSING"

    Any ideas? I can see the messages over JAMNNTPD.

    Flavio

    ... Chia, vc gosta da Dinha? <daemon>
    --- MacFidoIP 1.0 (OSX)
    * Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)
  • From Rick Christian@1:135/377 to Flavio Bessa on Sat Dec 17 01:14:20 2016

    Hello Flavio!

    16 Dec 16 20:11, you wrote to all:

    I am setting up a system with Crashmail/JamNNTPD to run under Linux. All went well, I can toss messages into the system, but when I
    try to scan for messages to export I get the following error message:

    ^ 16-Dec-16 14:10:09 Scanning all areas for messages to export
    ! 16-Dec-16 14:10:09 Failed to read message #231 in JAM messagebase "/home/flbessa/fido/echo/BR_BBSING"

    Any ideas? I can see the messages over JAMNNTPD.


    You don't mention which distroy and the bitness... BUT...

    That is exactly the issue I had... on Kubuntu 14.04.5 *64b*

    CM II is/was written with only a - > *32b* < - world in mind..

    What you need to do is,

    Download this:

    eljaco.se/FILES/Billing/cm071linux.zip

    Then unzip it

    In there will be a bin/ directory

    @fidodev:~/cmzip$ unzip -l cm071linux\(1\).zip
    Archive: cm071linux(1).zip
    Length Date Time Name
    --------- ---------- ----- ----
    0 2004-07-10 08:51 crashmail-0.71/
    0 2004-07-10 08:56 crashmail-0.71/bin/
    38052 2004-07-10 08:56 crashmail-0.71/bin/crashmaint
    22164 2004-07-10 08:56 crashmail-0.71/bin/crashstats
    18516 2004-07-10 08:56 crashmail-0.71/bin/crashwrite
    18464 2004-07-10 08:56 crashmail-0.71/bin/crashlist
    205044 2004-07-10 08:56 crashmail-0.71/bin/crashmail
    22272 2004-07-10 08:56 crashmail-0.71/bin/crashlistout
    19476 2004-07-10 08:56 crashmail-0.71/bin/crashexport
    15768 2004-07-10 08:56 crashmail-0.71/bin/crashgetnode

    This will have precompiled versions of the CM II 0.71 version.

    These WILL RUN on *64b* systems and export messages, and not corrupt the message base.

    Do NOT use the versions in the *buntu repos... they are useless, and suffer the same bitness problems.

    They will compile on 64b systems, and then totally fail and corrupt things when run.

    DO the above, and still have issues, please let me know..

    I will be glad to help and provide info.

    I am using CMII 0.71 and JamNNTPd on Ubuntu 14.04.5

    Rick


    ... Ding Dong the Witch is DEAD! I Made America Great Again! President Trump! --- GoldED+/LNX 1.1.5-b20160322
    * Origin: Vina's Talos Moon Base Alpha (1:135/377)
  • From Flavio Bessa@4:801/189.1 to Rick Christian on Sat Dec 17 11:50:22 2016
    Hello Rick.

    17 Dec 16 01:14, you wrote to me:


    You don't mention which distroy and the bitness... BUT...

    That is exactly the issue I had... on Kubuntu 14.04.5 *64b*

    CM II is/was written with only a - > *32b* < - world in mind..

    Thanks a lot! It worked:

    flbessa@ubuntu:~/files$ sudo crashmail SETTINGS /etc/crashmail.prefs NOSECURITY TOSS
    CrashMail II 1.5 started successfully!
    Packets will be tossed without security checks
    Tossing files in /var/spool/ftn/inb...

    Unarchiving /var/spool/ftn/inb/00000001.sa1 using ZIP

    Archive: /var/spool/ftn/inb/00000001.sa1
    inflating: 0a5fb121.pkt

    Tossing 0a5fb121.pkt (1K) from 4:801/188.0 (17-???-16 11:13:54) / pw, 4d

    Area BR.BBSING -- 1 messages

    Total -> Read messages: 1 Written messages: 0
    Imported -> Imported messages: 1 Routed netmails: 0
    Bad -> Bad messages: 0 Duplicate messages: 0

    Scanning for orphan files
    Scanning for old packets
    Scanning for new files to pack
    Linking JAM area BR.BBSING
    CrashMail end

    Although there were an issue with the date (here it's DD-MM-AA, I don't know how to fix it), it went out well.

    Scan is also fine.

    Thanks again!

    Flavio

    ... "Me mostra o seu celuloso ai!" - Jones, II Enc UN TNG
    --- MacFidoIP 1.0 (OSX)
    * Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)
  • From Rick Christian@1:135/377 to Flavio Bessa on Sat Dec 17 17:46:03 2016
    17 Dec 16 11:50, you wrote to me:

    Thanks a lot! It worked:

    Thats what the whole point of this echo is!

    NOSECURITY TOSS CrashMail II 1.5 started successfully! Packets will be

    What distro and bitness is this?? I see CM II 1.5, so I am guessing instead that you chose to move to a 32b distro versus the older 0.71 version?

    Tossing 0a5fb121.pkt (1K) from 4:801/188.0 (17-???-16 11:13:54) / pw,

    Although there were an issue with the date (here it's
    DD-MM-AA, I don't know how to fix it), it went out well.

    Smart Aleck humor ON
    Can't fix that, as your date is wrong. :p ;) :) ;) ;)
    Smart Aleck humor OFF

    Scan is also fine.
    Thanks again!

    Glad its working, but if you could provide what you did ...

    Distro? Release and version?

    Change distro bitness?

    Or something else?

    I ask since your using the CM II 1.5 version, and I would like to add to the KB for others in the future...

    Even playing with some things on that CM II 1.5 version which should resolve this, on 64b systems, it still doesn't there is still a sneak 64 v.32b issue in there some where.

    But the 0.71 version resolved it....
    0@fidonet:~/fido/crashmail$ ./crashmail TOSS SCAN SETTINGS ~/fido/crashmail/crashmailTEST.prefs
    CrashMail II 0.71 started successfully!
    Tossing files in /home/c/fido/binkd/inb...


    Total -> Read messages: 0 Written messages: 0
    Imported -> Imported messages: 0 Routed netmails: 0
    Bad -> Bad messages: 0 Duplicate messages: 0

    Scanning for orphan files
    Scanning for old packets
    Scanning for new files to pack
    Scanning all areas for messages to export
    Scanning area NETMAIL
    Scanning area PYTHON
    Scanning area SCANRADIO
    Scanning area TEST
    Exporting message #3 from "c" to "c" in TEST
    Is in HandleMessage()

    1 message exported
    Scanning for orphan files
    Scanning for old packets
    Scanning for new files to pack
    Packing 55c11300.pkt for 1:393/68.0 with ZIP
    adding: 55c11300.pkt (deflated 29%)
    CrashMail end

    Rick


    ... Ding Dong the Witch is DEAD! I Made America Great Again! President Trump! --- GoldED+/LNX 1.1.5-b20160322
    * Origin: Vina's Talos Moon Base Alpha (1:135/377)
  • From Flavio Bessa@4:801/189.1 to Rick Christian on Mon Dec 19 09:26:40 2016
    Hello Rick.

    17 Dec 16 17:46, you wrote to me:

    NOSECURITY TOSS CrashMail II 1.5 started successfully! Packets
    will be

    What distro and bitness is this?? I see CM II 1.5, so I am guessing instead that you chose to move to a 32b distro versus the older 0.71 version?

    I am running Ubuntu 16.04 64-bit release. I downloaded the ZIP package from eljaco.se as you suggested and am using it here. :)

    Tossing 0a5fb121.pkt (1K) from 4:801/188.0 (17-???-16 11:13:54) /
    pw,

    Although there were an issue with the date (here it's
    DD-MM-AA, I don't know how to fix it), it went out well.

    Smart Aleck humor ON
    Can't fix that, as your date is wrong. :p ;) :) ;) ;)
    Smart Aleck humor OFF

    AHAHAHAHAHAHA... Ok :)

    Scan is also fine.
    Thanks again!

    Glad its working, but if you could provide what you did ...

    Distro? Release and version?

    Change distro bitness?

    Or something else?

    I ask since your using the CM II 1.5 version, and I would like to add
    to the KB for others in the future...

    Even playing with some things on that CM II 1.5 version which should resolve this, on 64b systems, it still doesn't there is still a sneak
    64 v.32b issue in there some where.

    I just downloaded the package from the URL you suggested... Is there a specific command that will show the correct version?

    Flavio

    ... "Teu irmo gostoso?" - Xalas, 1 Encontro UnionNet: TNG
    --- MacFidoIP 1.0 (OSX)
    * Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)
  • From Rick Christian@1:135/377 to Flavio Bessa on Mon Dec 19 08:49:53 2016
    Hello Flavio!

    19 Dec 16 09:26, you wrote to me:

    I am running Ubuntu 16.04 64-bit release. I downloaded the ZIP package from eljaco.se as you suggested and am using it here. :)

    I just downloaded the package from the URL you suggested... Is there a specific command that will show the correct version?

    Did you use the previous install of a DEB or repo version????

    ie: did you at some point do sudo apt-get install crashmail?

    When you run this version you should get something like this:

    :~/cmzip/crashmail-0.71/bin$ ./crashmail VERSION
    This is CrashMail II version 0.71

    Operating system: Linux
    Compilation date: Jul 10 2004
    Compilation time: 14:56:38

    Available messagebase formats:
    MSG Standard *.msg messagebase as specified in FTS-1
    JAM JAM Messagebase

    Available nodelist formats:
    CMNL CrashMail nodelist index
    V7+ Version 7+ format
    r@fidodev:~/cmzip/crashmail-0.71/bin$


    I only ask this as you out put shows CM II 1.5 in the message...

    When you run it if you have an apt version installed if you run it like so:

    crashmail the system will find that version first and run it...

    ./crashmail as you see above will make it run the version in the directory where ever you have it.

    If you got 1.5 to run on a 64b thats interesting

    lbessa@ubuntu:~/files$ sudo crashmail SETTINGS /etc/crashmail.prefs NOSECURITY TOSS #
    CrashMail II 1.5 started successfully! #
    Packets will be tossed without security checks #
    Tossing files in /var/spool/ftn/inb...

    CM II 1.5 will TOSS pkts , but will NOT export message from JAM... on 64b systems... MSG format on 64b is fine...

    JAM uses 32b binary data in parts of its header and when its compiled on 64b it becomes 64b wide, which breaks things massively.

    Even doing a compile with -m32 doesn't solve it... as there still is something sneaking in 64b stuff when I only want 32b var, just have not found it yet..

    Do a:

    sudo apt-get purge crashmail

    Then in the directory with the files you downloaded

    to run them prefix it with ./

    ie: ./crashmail

    You could do something else but for now... just run it with ./ and then we can look at making work like an apt installed versions.

    Rick


    ... Ding Dong the Witch is DEAD! I Made America Great Again! President Trump! --- GoldED+/LNX 1.1.5-b20160322
    * Origin: Vina's Talos Moon Base Alpha (1:135/377)
  • From Björn Felten@2:203/2 to Flavio Bessa on Mon Dec 19 15:24:55 2016
    I just downloaded the package from the URL you suggested... Is there a specific command that will show the correct version?

    Well, all I can say that if you get the original Johan package from eljaco.se, this is what it looks like on an XP system (the command obviously is 'version'):

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    S:\JAMNNTP>crashmail version
    This is CrashMail II version 0.71

    Operating system: Win32
    Compilation date: Jul 10 2004
    Compilation time: 15:21:29

    Available messagebase formats:
    MSG Standard *.msg messagebase as specified in FTS-1
    JAM JAM Messagebase

    Available nodelist formats:
    CMNL CrashMail nodelist index
    V7+ Version 7+ format

    S:\JAMNNTP>




    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)