Subj : FReqs To : Fred Riccio From : Paul Quinn Date : Tue May 23 2017 08:18 am Hi! Fred, On 05/22/2017 10:04 PM, you wrote: 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. FR> I'm not following you here. Are you saying than Mystic *can* do it, but FR> only after the BinkP session ends? I guess what I should have asked is FR> if Mystic can do it asynchronously, or in another thread. Oh, dear. No. Maybe. 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>> ;-) FR> Or native support of FREQs. Back in the olden days the more popular FR> mailers had FREQ built in. No SRIF or add-on processors needed. It was FR> the newer developers who dropped support for it. On my main node I've run FrontDoor, BinkleyTerm and Argus/Radius. I know this. 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 FR> So Ben needs to upgrade from A33 to A89 in order to get File requests to FR> work? Look closely. Apples & oranges. FR> Unless... The BinkP/1.0 optional extension "multiple batch mode" FR> (FSP-1021.001 / FRL-1018.001) was implemented by Mystic. I highly doubt FR> this because I havent seen his Mystic send "OPT MB" in any session we FR> have had, but it *does* appear with his (and others' systems) IREX 2.29 FR> mailer. Mmm... fascinating. Mystic doesn't even report local system time. Cheers, Paul. --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 * Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384) .