Subj : FReqs
To   : Paul Quinn
From : Fred Riccio
Date : Mon May 22 2017 08:04 am

22 May 17 17:12, Paul Quinn wrote to Fred Riccio:

 FR>>> Can Mystic execute a DOS command when it receives a *.req file?

 BR>> Yes

 PQ> That's not really even an option.  It's no good if Mystic drops 
 PQ> carrier on a current session.  Working in absentia from the calling 
 PQ> node isn't what FREQ-ing is all about, as you know.

I'm not following you here.  Are you saying than Mystic *can* do it, but only 
after the BinkP session ends?  I guess what I should have asked is if Mystic 
can do it asynchronously, or in another thread.



 PQ> Ben & company need to press for SRIF support in Mystic when a FREQ 
 PQ> transaction is attempted.  It's relatively simple for software 
 PQ> maintainers to implement... in my simplistic view of the universe.  
 PQ> ;-)

Or native support of FREQs.  Back in the olden days the more popular mailers 
had FREQ built in.  No SRIF or add-on processors needed.  It was the newer 
developers who dropped support for it.



 FR>>> Does Mystic truely support BinkP 1.1 or does it just fake it?

 BR>> 1.1a-89 it says :)

 PQ> A session with Ben's system reports...

 PQ> : 21-May-2017 15:35:38     Mailer : Mystic/1.12A33 binkp/1.0

So Ben needs to upgrade from A33 to A89 in order to get File requests to work?

Unless...  The BinkP/1.0 optional extension "multiple batch mode" (FSP-1021.001 
/ FRL-1018.001) was implemented by Mystic.  I highly doubt this because I 
havent seen his Mystic send "OPT MB" in any session we have had, but it *does* 
appear with his (and others' systems) IREX 2.29 mailer.

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

.