This may be more of a Binkleyterm question, but long story short, D'Bridge uses a unique method of storing Netmail and compressed mail, called Base36. In order to integrate BinkD with D'Bridge, I have had to write a tremendous amount of code to convert Base36 to ArcMail. This is all done using the "mailbox" directory support in BinkD... but is a real challenge to program.

It would be nice, if in my code, I could just use BinkD/Binkley
control files to translate the filenames of these so the remote system that polls here via BinkD can directly download their waiting mail but the
filenames are then correctly translated by BinkD to ArcMail format (*.PKT and *.Day-of-the-week/sequence number for compressed mail).

Lets say for example, there is Netmail waiting for 1:229/427. The Base36 Queue entry looks like this: C:\QUEUE\N-00106D.0BV. Now if 1:229/427 polls here
via BinkD, I would like BinkD to send that as 00E501AB.PKT.

All I can tell is that there are two ways to do this, as per FSP-1034 (I think thats the name). List it in an appropriate FLO file or make a "?ut" file.

The problem is that I do not see a way to do filename translation in the FLO file. In other words, ^C:\QUEUE\N-00106D.0BV would be sent as-is to the remote system, and obviously that remote system won't toss it as it is not ArcMail, no tosser would understand what to do with a "*.0BV" file.

So looking at the "?ut" method, I do see that the contents will be sent as dynamically-named *.PKT files to the remote system, but that does not take into account compressed ArcMail.... so uncompressed PKT files would in theory work, but I'm back to square one dealing with how to send compressed ArcMail-named files on the fly.

Is there a control file that BinkD reads, so upon a connection, it will look at it, send the contents as a different name when that remote system connects?

Something like 00E501AB.FLO containing "^C:\QUEUE\N-00106D.0BV 00E501AB.PKT"

Would be VERY helpful in my quest to simplify a lot of the D'Bridge code.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Hello Nick!

28 Apr 18 13:29, Nick Andre wrote to All:

Lets say for example, there is Netmail waiting for 1:229/427. The
Base36 Queue entry looks like this: C:\QUEUE\N-00106D.0BV. Now if 1:229/427 polls here via BinkD, I would like BinkD to send that as 00E501AB.PKT.

Nick, It sounds like D'Bridge doesn't fully support BSO (binkley-style Outbound). There is no need for your Base36 queue with a BSO mailer such as BinkD. Your tosser/scanner should create and store all files in the appropriate outbound directory.

All I can tell is that there are two ways to do this, as per FSP-1034
(I think thats the name).

Refer to FTS-5005.001, that is the approved and updated version of the proposal
FSP-1034.

List it in an appropriate FLO file or make a "?ut" file.

Correct. With BSO, ncompressed NetMail is stored in <nnnnffff>.?ut files. Compressed mail bundles are listed in <random_number>.<DayOfWeek>.? files and listed in a <nnnnffff>.?lo file. THIS IS WHAT BINKD EXPECTS TO SEE!

The problem is that I do not see a way to do filename translation in
the FLO file. In other words, ^C:\QUEUE\N-00106D.0BV would be sent as-is to the remote system, and obviously that remote system won't toss it as it

is not ArcMail, no tosser would understand what to do with a "*.0BV" file.

In order to use a ?lo file, your tosser/scanner needs to create a mail bundle with the NetMail packet inside. The packet name should be unique, with an extension of .pkt.

So looking at the "?ut" method, I do see that the contents will be
sent as dynamically-named *.PKT files to the remote system, but that
does not take into account compressed ArcMail....

True. A BSO mailer will rename <ffffnnnn>.?ut to <unique_number>.pkt before sending.

Note that WaZoo file requests also get renamed. See log snippet below.

----- Binkley.Log begins -----
- 23 Mar 11:08:05 [860] sending c:\BinkD\out\008400ae.out as 514dc57e.pkt (14) - 23 Mar 11:08:05 [860] sending c:\BinkD\out\008400ae.req as 514e0d78.req (8)
+ 23 Mar 11:08:05 [860] sent: c:\BinkD\out\008400ae.out (14, 14.00 CPS, 1:132/174@fidonet)
+ 23 Mar 11:08:05 [860] sent: c:\BinkD\out\008400ae.req (8, 8.00 CPS, 1:132/174@fidonet)
----- Binkley.Log ends -----

so uncompressed PKT files would in theory work

They will!

but I'm back to square one dealing with how to send compressed ArcMail-named files on the fly.

Your tosser/scanner needs to create properly named files in the outbound directory for BSO support. No renaming is necessary when using Compressed mail
bundles.

--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)