REPLY: 1:18/200@fidonet.org 61e6e72c
MSGID: 2:250/1@fidonet 61e82ec8
CHRS: UTF-8 2
TZUTC: 0000
TID: MBSE-FIDO 1.0.7.24 (GNU/Linux-x86_64)
Hello Sean!

Tuesday January 18 2022 16:12, you wrote to me:

 > Hello Vincent,

 > Tuesday January 18 2022 20:00, you wrote to me:

 VC>> The hatch program as near as I can tell does NOT read the
 VC>> FILE_ID.DIZ but accepts a line for the description.

 > Let me look into this.  I should be able to write a bash script to do
 > this.

I have re-discovered a way around it if the files will be hatched more than
once by using the FILES hatch facility how ever that also uses a one liner so
the file needs to be an archive with FILE_ID.DIZ within.

This has forced me to issues the files FILEGATE.HDR and FILEGATE.ZXX within
there own archives with a .DIZ file.

OK, but I cannot handle one off's.

This could be a problem when filegate contributors send me files adhoc via a
email or just uploaded into the inbound directory for me to process.

Clearly it is best (for me at least) for them to connect to a Hub such as here
and upload it along with the .tic file but that assumes they have the
appropriate software on their system and are running at least a mailer or can
use anonymous ftp to get to my server.

It can get tricky :)

Clearly using automation is best for them and myself - being a bit of a lazy
git :)


Vincent
--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
 * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
SEEN-BY: 1/123 14/0 15/0 18/200 25/0 21 30/0 90/1 103/705 105/81 106/201
SEEN-BY: 120/340 123/131 129/305 330 153/7715 154/10 218/700 221/1
SEEN-BY: 221/6 226/30 227/114 229/110 317 400 424 426 428 452 550
SEEN-BY: 229/664 700 240/1120 5832 249/206 250/0 1 2 3 4 5 6 7 8 10
SEEN-BY: 250/21 263/0 266/512 280/464 282/464 1038 292/854 301/0 1
SEEN-BY: 301/101 113 317/3 320/219 322/757 342/200 396/45 633/280
SEEN-BY: 712/848 920/1 3634/12 5020/1042 5058/104
PATH: 250/1 301/1 229/426