Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Support Echo For JAMNNTPD NNTP S...  <--  <--- Return to Home Page
   Networked Database  Support Echo For JAMNNTPD NNTP S...   [33 / 238] RSS
 From   To   Subject   Date/Time 
Message   Rick Christian    Paul Quinn   crashmail Echo JAM Base - Errors and Exporting   October 31, 2016
 10:04 AM *  

* Replying to a msg in PERSONAL_MESSAGES (Personal Messages)

 PQ> You'll note straight up that there's no warning of bad things about
 PQ> the headers.

What is the setup on this? Distro and arch and version(s)?

DEV VM for fido

Has no message bases, or anything on it.

took crashmail 1.5 DEB and installed

took crashmail.prefs from operating node and scp'd

took some PKT's from my arhcive (I keep'em) and scp'd

ran a test.. Same errors!

Golded has NEVER TOUCHED the JAM files on here, as its not on there to run..

Kubuntu 14.04.5 *64bit*

I am replying to this on my operating node, which I *changed* to MSG format as
that is the ONLY format that will export and generate PKTS.

Log/transcript follows:

rec9140@fidodev:~$ sudo dpkg -i crashmail_1.5-1_amd64.deb
[sudo] password for rec9140:
Selecting previously unselected package crashmail.
(Reading database ... 77870 files and directories currently installed.)
Preparing to unpack crashmail_1.5-1_amd64.deb ...
Unpacking crashmail (1.5-1) ...
Setting up crashmail (1.5-1) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
rec9140@fidodev:~$ crashmail
Failed to read configuration file crashmail.prefs
rec9140@fidodev:~$ cd fido/
rec9140@fidodev:~/fido$ ls -la
total 12


rec9140@fidodev:~/fido/crashmail$ crashmail TOSS SCAN SETTINGS
~/fido/crashmail/crashmail.prefs
Creating new dupe file /home/rec9140/fido/logs/crashmail.dupes
CrashMail II 1.5 started successfully!
Tossing files in /home/rec9140/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 TESTECHO
Creating JAM messagebase "/home/rec9140/fido/jam/TESTECHO"
Scanning area TEST
Scanning area BINKD
Creating JAM messagebase "/home/rec9140/fido/jam/BINKD"
Scanning area NET135
Creating JAM messagebase "/home/rec9140/fido/jam/NET135"
Scanning area NET135FILE
Creating JAM messagebase "/home/rec9140/fido/jam/NET135FILE"
Scanning area NET135HUB
Creating JAM messagebase "/home/rec9140/fido/jam/NET135HUB"
Scanning area FIDONEWS
Creating JAM messagebase "/home/rec9140/fido/jam/FIDONEWS"
Scanning area RBERRYPI
Creating JAM messagebase "/home/rec9140/fido/jam/RBERRYPI"
Scanning area JAMNNTPD
Creating JAM messagebase "/home/rec9140/fido/jam/JAMNNTPD"

No messages exported
Scanning for orphan files
Scanning for old packets
Scanning for new files to pack
CrashMail end
rec9140@fidodev:~/fido/crashmail$ crashmail TOSS SCAN SETTINGS
~/fido/crashmail/crashmail.prefs
CrashMail II 1.5 started successfully!
Tossing files in /home/rec9140/fido/binkd/inb...
Tossing c5b3ac3d.pkt (16K) from 1:135/300.0 (20-Oct-16 15:41:03) / 4d
Is in HandleMessage()

Area NETMAIL -- 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
Scanning all areas for messages to export
Scanning area NETMAIL
Scanning area TESTECHO
Scanning area TEST
Scanning area BINKD
Scanning area NET135
Scanning area NET135FILE
Scanning area NET135HUB
Scanning area FIDONEWS
Scanning area RBERRYPI
Scanning area JAMNNTPD

No messages exported
Scanning for orphan files
Scanning for old packets
Scanning for new files to pack
CrashMail end
rec9140@fidodev:~/fido/crashmail$ crashmail TOSS SCAN SETTINGS
~/fido/crashmail/crashmail.prefs
CrashMail II 1.5 started successfully!
Tossing files in /home/rec9140/fido/binkd/inb...
Tossing 16827d04.pkt (33K) from 1:135/300.0 (30-Oct-16 19:28:37) / 4d
Is in HandleMessage()
Is in HandleMessage()
Is in HandleMessage()
Is in HandleMessage()
Is in HandleMessage()
Is in HandleMessage()

Area FIDONEWS -- 6 messages

   Total ->     Read messages:      6     Written messages:      0
Imported -> Imported messages:      6      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 FIDONEWS
Scanning all areas for messages to export
Scanning area NETMAIL
Scanning area TESTECHO
Scanning area TEST
Scanning area BINKD
Scanning area NET135
Scanning area NET135FILE
Scanning area NET135HUB
Scanning area FIDONEWS
Failed to read message #2 in JAM messagebase "/home/rec9140/fido/jam/FIDONEWS"
Failed to read message #4 in JAM messagebase "/home/rec9140/fido/jam/FIDONEWS"
Scanning area RBERRYPI
Scanning area JAMNNTPD

No messages exported
Scanning for orphan files
Scanning for old packets
Scanning for new files to pack
CrashMail end
rec9140@fidodev:~/fido/crashmail$




 PQ>  There's your problem.  You most likely have bad binaries.  I've
 PQ> seen similar behaviour on my 'shadow' system, even with recent
 PQ> incarnations of later version binaries.

I don't think so.. as it runs, and see above, *Same errors*.

 PQ> I'll send you a copy of the original archive.  It'll just arrive
 PQ> unanounced in your _insecure_ inbound.  The original binaries worked
 PQ> well in Puppy Linux 5.25 and Xubuntu 11.10, and still run nicely in
 PQ> the current Puppy 4.21 (yes, a retrograde step for very good reasons).

Nothing here...


 PQ> * destroy your existing JAM messagebase (completely? see note, below);

 I did this on the operating node, this one, I am replying from.. *same erorrs*
 on old or new packets

 Did it a couple times to nuke the JAM files...

 Finally created a TEST Echo in MSG format.... WORKS!


 PQ> Your netmail area _may_ be okay?  Is it a *.Msg area?  Otherwise,
 PQ> trash it too.

Nope, Netmail is/always is MSG format....

 PQ> No other changes needed... fingers crossed.  ;)  Just let CM re-create
 PQ> your messagebase...


No joy! See above.



Rick


--- GoldED+/LNX 1.1.5-b20160322
 * Origin:  (1:135/377)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Support Echo For JAMNNTPD NNTP S...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0883 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_s4qgfjvhteqg4vucrlc24n9494, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_s4qgfjvhteqg4vucrlc24n9494, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_s4qgfjvhteqg4vucrlc24n9494, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0