Hello Martin!

I am trying to add FSXnet to OXP, but the packets are encountering an
error on Import.

The call goes well, I receive a packet:

2020-03-20 22:47:08 netcall: Output mcInfo: b34f27b2.fr1 received
2020-03-20 22:47:08 ncmodem: Log: * Rcvd b34f27b2.fr1, 4269b
2020-03-20 22:47:09 xpncfido: Decompressiong packets: H:\DOWNLOADS\OPENXP\SPOOL\b34f27b2.fr1
2020-03-20 22:47:09 xpncfido: H:\DOWNLOADS\OPENXP\SPOOL\b34f27b2.fr1 is compressed packet

..but I haven't set up decompression for it. I hope to get uncompressed packets, later.

Meanwhile, I unpack the file above, and start the Import/ Read Other
Format steps. I navigate to the PKT file, select it, but OXP reports:

2020-03-20 23:02:53 zftools: converting fido to ZC
2020-03-20 23:02:53 zftools: conversion finished
2020-03-20 23:02:53 _fehler: Error while converting messages

What could be the problem?

Aren't all PKT files alike? :(



../|ug

--- OpenXP 5.0.43
* Origin: û › Ÿ (2:221/1.58)

Re: oxp +anothernet
By: August Abolins to Martin Foster on Fri Mar 20 2020 23:05:00

The call goes well, I receive a packet:

2020-03-20 22:47:08 netcall: Output mcInfo: b34f27b2.fr1 received 2020-03-20 22:47:08 ncmodem: Log: * Rcvd b34f27b2.fr1, 4269b
2020-03-20 22:47:09 xpncfido: Decompressiong packets:

H:\DOWNLOADS\OPENXP\SPOOL\b34f27b2.fr1

2020-03-20 22:47:09 xpncfido: H:\DOWNLOADS\OPENXP\SPOOL\b34f27b2.fr1 is

compressed packet

this wording is wrong... the above file is a bundle... not a packet... bundles contain one or more packets... packets contain zero or more messages...


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

On 21/03/2020 11:15 a.m., mark lewis : August Abolins wrote:

2020-03-20 22:47:08 netcall: Output mcInfo: b34f27b2.fr1 received
2020-03-20 22:47:08 ncmodem: Log: * Rcvd b34f27b2.fr1, 4269b
2020-03-20 22:47:09 xpncfido: Decompressiong packets:

H:\DOWNLOADS\OPENXP\SPOOL\b34f27b2.fr1

2020-03-20 22:47:09 xpncfido: H:\DOWNLOADS\OPENXP\SPOOL\b34f27b2.fr1
is compressed packet

^^^^^^
Hmmm. --------------^

this wording is wrong... the above file is a bundle... not a
packet... bundles contain one or more packets... packets contain
zero or more messages...

Yeah.. I see the incorrect term used in the last line in the log, and then consequently repeated by me!

Wrt OXP that is a minor (ie. low priority) change.

But I appreciate your clarification.



--
Quoted with Reformator/Quoter. Info = https://tinyurl.com/sxnhuxc

--- TB68.4.1/Win7
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

Hello August!

*** 20.03.20 at 23:05, August Abolins wrote to Martin Foster:

I am trying to add FSXnet to OXP, but the packets are encountering an error on Import.

We fix one problem and another one comes rolling through the door <sigh>.

The call goes well, I receive a packet:

2020-03-20 22:47:08 netcall: Output mcInfo: b34f27b2.fr1 received 2020-03-20 22:47:08 ncmodem: Log: * Rcvd b34f27b2.fr1, 4269b
2020-03-20 22:47:09 xpncfido: Decompressiong packets: H:\DOWNLOADS\OPENXP\SPOOL\b34f27b2.fr1 2020-03-20 22:47:09 xpncfido: H:\DOWNLOADS\OPENXP\SPOOL\b34f27b2.fr1 is compressed packet

..but I haven't set up decompression for it.

Well maybe you should until .....

I hope to get uncompressed packets, later.

..... your uplink confirms when this is going to happen.

Meanwhile, I unpack the file above, and start the Import/ Read Other Format steps. I navigate to the PKT file, select it, but OXP reports:

2020-03-20 23:02:53 zftools: converting fido to ZC
2020-03-20 23:02:53 zftools: conversion finished
2020-03-20 23:02:53 _fehler: Error while converting messages

What could be the problem?

Corrupt mail packet?

If you still have the mail packet and you can find a packet
sniffer(InspectA was a good one), that may throw some light on the issue.

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello mark!

*** 21.03.20 at 11:15, mark lewis wrote to August Abolins:

[snip]

this wording is wrong... the above file is a bundle... not a packet... bundles contain one or more packets... packets contain zero or more messages...

Yep, absolutely spot on and I'll try and fix the technically incorrect wording for the next release.

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello August!

*** 21.03.20 at 20:12, August Abolins wrote to mark lewis:

[snip]

Yeah.. I see the incorrect term used in the last line in the log, and
then consequently repeated by me!

Wrt OXP that is a minor (ie. low priority) change.

Yep, along with all the other low priority stuff, some of which has been hanging about in there for the last 20 years :(

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** 24.03.20 - 13:07, Martin Foster wrote to August Abolins:

What could be the problem?

Corrupt mail packet?

If you still have the mail packet and you can find a packet
sniffer(InspectA was a good one), that may throw some light on the issue.

Thanks for the InspectA tip. The program confirms that the .pkt files are type 2+ and that all is good.

What next? I can send you a few of them.



../|ug

--- OpenXP 5.0.43
* Origin: û › Ÿ (2:221/1.58)

Re: oxp +anothernet
By: August Abolins to Martin Foster on Tue Mar 24 2020 18:27:00

If you still have the mail packet and you can find a packet sniffer(InspectA was a good one), that may throw some light
on the issue.

Thanks for the InspectA tip.

there are other pkt dumping/analyzing tools available, too... inspecta is really a full blown file manager with pkt handling capabilities...

The program confirms that the .pkt files are type 2+ and
that all is good.

that's just the header... is the pkt complete, though... scroll to the last message in the pkt and see if it terminated properly... it may not and would be
a truncated pkt which might toss all the messages up to the broken one... it depends on the tosser code, though...


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello August!

*** 24.03.20 at 18:27, August Abolins wrote to Martin Foster:

What could be the problem?

Corrupt mail packet?

If you still have the mail packet and you can find a packet
sniffer(InspectA was a good one), that may throw some light on the
issue.

Thanks for the InspectA tip. The program confirms that the .pkt files
are type 2+ and that all is good.

What next? I can send you a few of them.

They wouldn't be any good to me because I don't have an FSXNet server configured, as I'm not on FSXNet.

What do you have in the "Area prefix" field in the "Robots" section of
your FSXNet server config?

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** 29.03.20 - 08:43, Martin Foster wrote to August Abolins:

What next? I can send you a few of them.

They wouldn't be any good to me because I don't have an FSXNet server
configured, as I'm not on FSXNet.

BUT.. I thought OXP is open to importing *ANY* pkts?

What do you have in the "Area prefix" field in the "Robots" section of
your FSXNet server config?

You didn't tell me HOW to get to that section! :) But my handy openxp.kolico.ca project reminded me that it was:

/Edit/Servers/Edit/Robots

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ 21:4/106 Fido Ogg ³
³F 2:221/1 Fido August Abolins It's too cold outside! ³
³ ³
³ ³
³ ³
³ ³
³ ÚÄ Robots Options ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³
³ ³ ³ ³
³ ³ Areafix Name Areafix  ³ ³
³ ³ Password ######## ³ ³
³ ³ ³ ³
³ ³ [x] "+" for area requests ³ ³
³ ³ [ ] Commands in subject ³ ³
³ ³ [ ] d'Bridge Areafix ³ ³
³ ³ ³ ³
³ ³ AllFix Name Allfix  ³ ³
³ ³ Password ######## ³ ³
³ ³ ³ ³
³ ³ Misc. Area prefix /FSXnet/  ³ ³
³ ³ ³ ³
³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ [F2] ÄÙ ³
³ ³
³ ³
³ ³
³ ³
³ ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³ New Delete Select  Edit  Net type OK ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

../|ug

--- OpenXP 5.0.43
* Origin: û › Ÿ (2:221/1.58)

Hello August!

*** 29.03.20 at 21:49, August Abolins wrote to Martin Foster:

What next? I can send you a few of them.

They wouldn't be any good to me because I don't have an FSXNet server
configured, as I'm not on FSXNet.

BUT.. I thought OXP is open to importing *ANY* pkts?

Yes, indeed it is and I'll expand on that later(if I need to). In the meantime, have you tried importing any of these FSXNet mail packets into
your WinPoint setup?

What do you have in the "Area prefix" field in the "Robots" section of
your FSXNet server config?

You didn't tell me HOW to get to that section! :)

Ah well, that was your leetle test for the day :-))

But my handy openxp.kolico.ca project reminded me that it was:

/Edit/Servers/Edit/Robots

Good :)

[snip]

³ ³ Misc. Area prefix /FSXnet/  ³

OK, test passed, 10/10 :-))

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

After adding a new "othernet", how can I get oxp to recognize the alias
that I use?

For example, I use "Ogg" for messages in FSXnet. But oxp's message
listing does not highlight the messages that are From or To "Ogg"

The highlight would be nice so that I could spot the messages to me
easier.


../|ug

--- OpenXP 5.0.43
* Origin: û › Ÿ (2:221/1.58)

Hello August!

*** 01.04.20 at 23:40, August Abolins wrote to Martin Foster:

After adding a new "othernet", how can I get oxp to recognize the alias that I use?

For example, I use "Ogg" for messages in FSXnet. But oxp's message listing does not highlight the messages that are From or To "Ogg"

The highlight would be nice so that I could spot the messages to me easier.

As I've never used an alias with an FTN-compatible network, I'm sorry
but I don't know. Perhaps you might like to ask in the support
newsgroup, I'm sure there's somebody in there who may be able to help
you ;)

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello August!

*** 31.03.20 at 9:29:00, Martin Foster wrote to August Abolins:

[snip]

BUT.. I thought OXP is open to importing *ANY* pkts?

Yes, indeed it is and I'll expand on that later(if I need to). In the meantime, have you tried importing any of these FSXNet mail packets into your WinPoint setup?

Have you tried my suggestion yet?

Regards,
Martin

--- WinPoint Beta 5 (359.1)
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** 13.04.20 - 14:34, Martin Foster wrote to August Abolins:

BUT.. I thought OXP is open to importing *ANY* pkts?

Yes, indeed it is and I'll expand on that later(if I need to). In the
meantime, have you tried importing any of these FSXNet mail packets into
your WinPoint setup?

Have you tried my suggestion yet?

Sorry.. I got sidetracked or something.

Here is the result.

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

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


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

Thus "Tossed 9" - ""BAD received 7" = 2


BUT.. they tossed SUCCESSFULLY in APoint.

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


../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello August!

*** Monday 13.04.20 at 10:31, August Abolins wrote to Martin Foster:

BUT.. I thought OXP is open to importing *ANY* pkts?

Yes, indeed it is and I'll expand on that later(if I need to). In the
meantime, have you tried importing any of these FSXNet mail packets
into your WinPoint setup?

Have you tried my suggestion yet?

Sorry.. I got sidetracked or something.

Here is the result.

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

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

This suggests that the problem is not specific to OpenXP.

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

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

Does this problem still persist?

Thus "Tossed 9" - ""BAD received 7" = 2

BUT.. they tossed SUCCESSFULLY in APoint.

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

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

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

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

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

Here is the result.

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

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

This suggests that the problem is not specific to OpenXP.

Huh?

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

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

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

Does this problem still persist?

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

BUT.. they tossed SUCCESSFULLY in APoint.

..... 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.

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

Well, you could send them if you like but whether I could do anything with
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)

Hello August!

*** Tuesday 21.04.20 at 21:30, August Abolins wrote to Martin Foster:

Here is the result.

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

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

This suggests that the problem is not specific to OpenXP.

Huh?

If the problem was specific to OpenXP, I wouldn't have expected WinPoint
to have had problems.

[snip]

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

Yes :)

There doesn't seem to be an option in the config to accomodate that.

Eh??

It looks like all the servers have to feed the same file formats
(either a bundle or separate .pkt files).

As each server has its own separate config, the packer/unpacker can be defined on a per server basis.

Does this problem still persist?

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

So why are we still discussing this :-))

[snip]

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?

OK, send them(Zip'd) and I'll play about with them here.

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** On 23.04.20 - 11:13, Martin Foster wrote to August Abolins:

If the problem was specific to OpenXP, I wouldn't have expected WinPoint
to have had problems.

Oh yeah. Got it. :/

[snip]

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

Yes :)

I did not realize this! I will be trying that shortly with a 3rd server.

It looks like all the servers have to feed the same file formats
(either a bundle or separate .pkt files).

As each server has its own separate config, the packer/unpacker can be
defined on a per server basis.

Again.. I missed noticing that option. Duh. The 3rd server will be my test.

OK, send them(Zip'd) and I'll play about with them here.

DONE.

Thank you.


../|ug

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

Hello August!

*** Thursday 23.04.20 at 18:15, August Abolins wrote to Martin Foster:

[snip]

OK, send them(Zip'd) and I'll play about with them here.

DONE.

Received this morning, thanks.

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello August!

*** Friday 20.03.20 at 23:05, August Abolins wrote to Martin Foster:

I am trying to add FSXnet to OXP, but the packets are encountering an error on Import.

The call goes well, I receive a packet:

2020-03-20 22:47:08 netcall: Output mcInfo: b34f27b2.fr1 received 2020-03-20 22:47:08 ncmodem: Log: * Rcvd b34f27b2.fr1, 4269b
2020-03-20 22:47:09 xpncfido: Decompressiong packets: H:\DOWNLOADS\OPENXP\SPOOL\b34f27b2.fr1 2020-03-20 22:47:09 xpncfido: H:\DOWNLOADS\OPENXP\SPOOL\b34f27b2.fr1 is compressed packet

..but I haven't set up decompression for it. I hope to get
uncompressed packets, later.

Meanwhile, I unpack the file above, and start the Import/ Read Other Format steps. I navigate to the PKT file, select it, but OXP reports:

2020-03-20 23:02:53 zftools: converting fido to ZC
2020-03-20 23:02:53 zftools: conversion finished
2020-03-20 23:02:53 _fehler: Error while converting messages

What could be the problem?

Here's how my tests went with the "suspect" FSXNet compressed mail bundles you kindly sent me .....

[1] Configured a "dummy" FSXNet server.

[2] Manually unpacked the compressed mail bundle into a temporary
directory, which resulted in four mail packets(.pkt) sitting in the
temporary directory.

[3] Selected OpenXP -> Import -> Read other format.

[4] Navigated my way to the temporary directory.

[5] Hit <Enter> over the first .pkt file.

[6] In the dialogue that popped up, I selected the "dummy" FSXNet server
by pressing <F2> and then pressing <Enter>.

[7] Pressed <Enter> on the following two options, which took me back to
OpenXP's area list screen.

[8] Repeated steps [3] to [7] for the other three mail packets.

I now have an FSXNet netmail area containing two messages and an FSXNet echomail area containing seven messages.

No errors encountered anywhere along the way.

Sorry but I cannot reproduce your problem.

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** On 01.05.20 - 19:50, Martin Foster wrote to August Abolins:

2020-03-20 23:02:53 zftools: converting fido to ZC
2020-03-20 23:02:53 zftools: conversion finished
2020-03-20 23:02:53 _fehler: Error while converting messages

What could be the problem?

Here's how my tests went with the "suspect" FSXNet compressed mail bundles
you kindly sent me .....

[6] In the dialogue that popped up, I selected the "dummy" FSXNet
server by pressing <F2> and then pressing <Enter>.

Thank you for doing all that.

MEANWHILE, I discovered [6] was my error. I failed to select the server associated with the packets. When I went through the same steps +
selecting the fsxnet server from the F2 drop-down, the import went well.

No errors encountered anywhere along the way.
Sorry but I cannot reproduce your problem.

Yep. All good.


../|ug

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

Hello August!

*** Monday 13.04.20 at 10:31, August Abolins wrote to Martin Foster:

BUT.. I thought OXP is open to importing *ANY* pkts?

Yes, indeed it is and I'll expand on that later(if I need to). In the
meantime, have you tried importing any of these FSXNet mail packets
into your WinPoint setup?

Have you tried my suggestion yet?

Sorry.. I got sidetracked or something.

Here is the result.

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

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

Further to my previous reply regarding my tests with OpenXP, I've just
tried this with my own WinPoint setup and I got exactly the same result as you .....

---------- 8< ----------
01.05.20 20:04:30 Starting Import
01.05.20 20:04:30 1 messages from b34f0322.pkt
01.05.20 20:04:30 Packet b34f0322.pkt has been moved to backup directory 01.05.20 20:04:30 1 messages from b34f27b1.pkt
01.05.20 20:04:30 Packet b34f27b1.pkt has been moved to backup directory 01.05.20 20:04:30 3 messages from b34f396f.pkt
01.05.20 20:04:30 Packet b34f396f.pkt has been moved to backup directory 01.05.20 20:04:30 4 messages from b34f4a41.pkt
01.05.20 20:04:30 Packet b34f4a41.pkt has been moved to backup directory 01.05.20 20:04:30 Area NETMAIL received 2 messages
01.05.20 20:04:30 Area BAD received 7 messages
01.05.20 20:04:30 Tossed 9 messages from 4 packets
---------- 8< ----------

Having thought about this, I'm not actually surprised by the outcome
because I didn't configure a "dummy" FSXNet uplink prior to doing the
test. Any thoughts?

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** On 01.05.20 - 20:17, Martin Foster wrote to August Abolins:

Hello August!

*** Monday 13.04.20 at 10:31, August Abolins wrote to Martin Foster:

^^^^^^

I like that addition!

Further to my previous reply regarding my tests with OpenXP, I've just
tried this with my own WinPoint setup and I got exactly the same result as
you .....

---------- 8< ----------
01.05.20 20:04:30 Starting Import
01.05.20 20:04:30 1 messages from b34f0322.pkt
01.05.20 20:04:30 Packet b34f0322.pkt has been moved to backup directory
01.05.20 20:04:30 1 messages from b34f27b1.pkt
01.05.20 20:04:30 Packet b34f27b1.pkt has been moved to backup directory
01.05.20 20:04:30 3 messages from b34f396f.pkt
01.05.20 20:04:30 Packet b34f396f.pkt has been moved to backup directory
01.05.20 20:04:30 4 messages from b34f4a41.pkt
01.05.20 20:04:30 Packet b34f4a41.pkt has been moved to backup directory
01.05.20 20:04:30 Area NETMAIL received 2 messages
01.05.20 20:04:30 Area BAD received 7 messages
01.05.20 20:04:30 Tossed 9 messages from 4 packets
---------- 8< ----------

Having thought about this, I'm not actually surprised by the outcome
because I didn't configure a "dummy" FSXNet uplink prior to doing the
test. Any thoughts?

I bet that is exactly why it failed for us in WinPoint. I assumed that WinPoint would automatically create the network particulars just like it
does the echo areas when something arrives.

Creating an uplink entry *first* before tossing makes sense. I guess we wouldn't want WinPoint to blindly accept every pkt or bundle that it receives. It's a good thing that the "unknown" .pkts are moved out of the way.

BUT.. Apoint doesn't seem to care! ;) The only thing I see failing in Apoint would be the building of outbound bundles to the proper Boss node.
In which case, that should probably be configured before Exporting any new messages created locally.

../|ug

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

Hello Martin,

On Saturday 01.05.20, you wrote to August Abolins:
^^^^^^^^^

WTF. Why isn't that working in WinPoint?


../|ug

--- WinPoint Beta 5 (359.1)
* Origin: Please write your complaint in this box [ ] - Legibly (2:221/1.59)

Hello August!

*** Monday 04.05.20 at 09:35, August Abolins wrote to Martin Foster:

=======variables test========
% sendday = Monday: Original day of week

Yes, correct.

% tossday = Monday: Arrivel [sic] day of week

Yes, correct.

% storeday = Monday: Day of week

Can't find that one ?

=====================

[snip]

And another thing I learned about the templates. After editing a template, the user either has to exit WinPoint, or switch to another subgroup of headers before the editing sticks or takes.

Yep.

I can't tell you how many times I made a change in my "Replies (header)" template and the changes did not appear!

Yep, been there, got the T-Shirt :)

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello August!

*** Tuesday 05.05.20 at 20:58, Martin Foster wrote to August Abolins:

[snip]

% storeday = Monday: Day of week

Can't find that one ?

Later .....

Just found it, silly me!

Regards,
Martin

--- OpenXP 5.0.43
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** On Tuesday 05.05.20 - 21:06, Martin Foster wrote to August Abolins:

[snip]

% storeday = Monday: Day of week

Can't find that one ?

Later .....

Just found it, silly me!

That variable is at the very bottom of the list, and offscreen if you last viewed the list in a different scroll position. BUT, note that the list items will be in the same position the last time you used it.

Like I said, when I was looking for "Day of Week" the first time, my list- view was already all the way down to the bottom of the list. I had no
reason to *think* that there would be other "Day of Week" variables. So, %storeday was the one I saw, and it was the one I used.



../|ug

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