MSGID: 2:240/2188.31@fidonet d721a329
REPLY: 2:221/1.58@fidonet d7180ac1
PID: OpenXP/5.0.36 (Linux) (x86_64)
CHRS: ASCII 1
Hello August!
On 04.04.19 at 21:38, August Abolins wrote to Martin Foster:
AA>>> I seem to remember my boss stating that he does not compress
AA>>> anything.
MF>> OK, fair enough but just to make sure, have a look in the "Netcall"
MF>> area where you'll find all your session logs.
AA> OK. What do I look for in there? Here's a recent sample:
[snip]
AA> * 19:50:12 Rcvd a68c2206.pkt, 617b
^^^
This
[snip]
AA> * 19:50:15 Rcvd a67f7705.pkt, 1634b
^^^
And this
However, this does not mean to say that these contain echomail
messages. It would be better to look back through your session logs
for occurences of *.SU?, *.MO?, *.TU? etc. etc. These are compressed
mail bundle extensions.
AA>>> So.. the given "copy..." option for the download field is the
AA>>> right choice?
MF>> I'm still a bit baffled about this one but suffice to say that if it's
MF>> working then it must be the right choice ;-)
AA> I have this:
AA> Upload packer:
AA> Download packer: copy $DOWNFILE $PUFFER
AA> All the other dropdown options for the "Download packer" referenced
AA> archivers, so I avoided those. "copy.." was the only other choice so as
AA> to avoid the screetching banshee.
AA> What is the baffling part?
A combination of the online help topic being incorrect and one of the
errors which keeps popping up below .....
AA> Meanwhile.. I noticed in LOG/ERRORS.LOG:
AA> 10.03.19 19:49:58 2:221/1: incomplete point data - please check server
AA> config
AA> 10.03.19 19:51:01 No matching servers.
You can safely ignore those two, as they haven't popped up again.
AA> 10.03.19 20:02:36 2:221/1: incomplete packer settings - please check
AA> server config
This is the one that's bugging me.
AA> 31.03.19 14:02:55 Empty timing list.
You can ignore this one, as it hasn't popped up again.
AA> 31.03.19 22:28:30 2:221/1: incomplete packer settings - please check
AA> server config
AA> 31.03.19 22:37:28 2:221/1: incomplete packer settings - please check
AA> server config
AA> 02.04.19 12:26:28 2:221/1: incomplete packer settings - please check
AA> server config
AA> 02.04.19 12:27:58 2:221/1: incomplete packer settings - please check
AA> server config
Cropping up repeatedly so there's obviously an unsolved problem.
AA> 02.04.19 21:33:48 Can't talk to the device!
Never seen that one before.
AA> 04.04.19 19:50:17 Datei(en) wurde(n) nicht korrekt entpackt!
Literal translation is "File incorrectly unpacked". On occasion, I've
seen this error message in my own setup and the first time I saw it,
it threw me completely and it took me ages to figured it out.
AA> I saw this last one following a NODELIST delivery today.
I can think of two possible reasons for this:
[1]Even though you're not using an unpacker for your incoming mail
packets, you still need one for the Zip'd nodelists/pointlists and
their respective Zip'd diffs. Additionally, you need one/some for the
built-in Archive Viewer to function.
Check this out .....
Config/External/Unpacker
Do you see a "tick" mark at the right-hand end of the ZIP entry. If
you don't, that's one possible reason why you're getting the "File
incorrectly unpacked" error. The unpacker(s) that you wish to use
should either be on your path or in OpenXP's root directory.
[2]
I noticed in the logfile that you posted, that the filename of the
nodelist was NODELIST.ZIP but OpenXP expects nodelist filenames to be
in the form NODELIST.Z??, where "??" is the last two characters of the
Julian day number. In this particular case, OpenXP would have been
expecting NODELIST.Z95.
Regards,
Martin
--- OpenXP 5.0.36
* Origin: Bitz-Box - Bradford - UK (2:240/2188.31)
SEEN-BY: 15/2 123/1970 226/17 229/107 354 426 1014 240/2100 2188 5138
SEEN-BY: 240/5832 5853 246/2027 249/206 317 400 280/464 292/854 317/3
SEEN-BY: 320/219 322/757 342/200 393/68 2432/200 390 2454/119
PATH: 240/2188 5832 229/426
|
