Subj : oxp +anothernet
To   : Martin Foster
From : August Abolins
Date : Tue Apr 21 2020 21:30:00

Hello Martin!

** On 19.04.20 - 13:16, Martin Foster wrote to August Abolins:

 AA>> Here is the result.

 AA>> 13.04.20 10:23:19 AM  Starting Import
 AA>> 13.04.20 10:23:19 AM  1 messages from b34f0322.pkt
 AA>> 13.04.20 10:23:19 AM  Packet b34f0322.pkt has been moved to backup
 AA>> directory 13.04.20 10:23:19 AM  1 messages from b34f27b1.pkt
 AA>> 13.04.20 10:23:19 AM  Packet b34f27b1.pkt has been moved to backup
 AA>> directory 13.04.20 10:23:19 AM  3 messages from b34f396f.pkt
 AA>> 13.04.20 10:23:19 AM  Packet b34f396f.pkt has been moved to backup
 AA>> directory 13.04.20 10:23:19 AM  4 messages from b34f4a41.pkt
 AA>> 13.04.20 10:23:19 AM  Packet b34f4a41.pkt has been moved to backup
 AA>> directory 13.04.20 10:23:19 AM  Area NETMAIL received 2 messages
 AA>> 13.04.20 10:23:19 AM  Area BAD received 7 messages
 AA>> 13.04.20 10:23:19 AM  Tossed 9 messages from 4 packets

 AA>>  + Origin: WinPoint Integrated Tosser (0:0/0)

 MF>This suggests that the problem is not specific to OpenXP.

Huh?

There is no clue as to WHY the 7 packets were BAD.


 AA>> MEANWHILE, 2 of the above contained netmail messages that WERE
 AA>> successfully posted in the netmail area.

 MF>Assuming that the netmails were originally contained in an uncompressed
 MF>packet(s) and the echomail messages were originally contained in a
 MF>compressed mail bundle, that may account for why the netmails were tossed
 MF>successfully. Please correct me if I'm wrong but I recall you saying in a
 MF>previous post that you were receiving compressed echomail bundles but that
 MF>you didn't have an unpacker defined in your FSXNet server config. If that
 MF>was the case, perhaps the mail packets got damaged when OpenXP attempted
 MF>to unpack the echomail bundle?

The "originals" were received compressed/bundled:

        b34f27b1.fr1
        b34f0301.fr1

Then, I used 7zip manually to unpack them into respective subdirs:

        /b34f27b1
        /b34f0301

  ...that contained the .pkt files.

At that time, I ust tried the Import packets feature of OXP one pkt at a  
time.  ALL of them failed to import.

QUESTION: can OXP operate with a mix of an uncompressed feed from one  
server and a compressed/bundle feed from another?

There doesn't seem to be an option in the config to accomodate that.  It  
looks like all the servers have to feed the same file formats (either a  
bundle or separate .pkt files).


 MF>Does this problem still persist?

I gave up on working with the original compressed "bundle" with OXP.



 AA>> BUT.. they tossed SUCCESSFULLY in APoint.

 MF>..... and along comes APoint and spoils the party LOL!

Yes..  Apoint had no problem with the individual .pkt files that I  
extracted from the bundles at all.


 AA>> Hmmmm.   So what would have been the problem?   I could still send you
 AA>> those .pkt files.

 MF>Well, you could send them if you like but whether I could do anything with
 MF>them is doubtful.

I meant that maybe I could send you the bundles:

        b34f27b1.fr1
        b34f0301.fr1

   H:\DOWNLOADS\OpenXP\BAD>unzip -tl *.fr1
   Archive:  b34f0301.fr1
       testing: b34f0322.pkt             OK
   No errors detected in compressed data of b34f0301.fr1.

   Archive:  b34f27b1.fr1
       testing: b34f27b1.pkt             OK
       testing: b34f396f.pkt             OK
       testing: b34f4a41.pkt             OK
   No errors detected in compressed data of b34f27b1.fr1.

   2 archives were successfully processed.


OXP clearly failed to unpack the bundle/archives because I did not have an  
unpacker defined.  But I still wonder WHY did the .pkt files fail to  
import?


  ../|ug

--- OpenXP 5.0.43
 * Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)

.