Hello Nick!

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

 NA> Lets say for example, there is Netmail waiting for 1:229/427. The 
 NA> Base36 Queue entry looks like this: C:\QUEUE\N-00106D.0BV. Now if
 NA> 1:229/427 polls here via BinkD, I would like BinkD to send that as 
 NA> 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.




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

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


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

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


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



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

True.  A BSO mailer will rename .?ut to .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 -----


 NA> so uncompressed PKT files would in theory work

They will!


 NA> but I'm back to square one dealing with how to send compressed 
 NA> 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