JM>  MT> Since we would not get te sources this is out of questions, but are
JM>  MT> there a considerable ammount of fido-system who does not have EMSI
JM>
JM>  PW> Could have sworn there were mailers which only did YooHoo, rather than
JM>  PW> EMSI.  I can't remember their name, but I'm sure others can. :)
JM>
JM> flame comes to mind

Binkley versions before 2.60 only supports YooHoo as it's highest
protocol. Opus BBS still only supports YooHoo. Fido BBS v12 only
supports YooHoo. (Previous versions only supported FTS-1.) TBBS's
TIMS only supports YooHoo.

XBBS does YooHoo as it's highest protocol, but not ZedZap, ZedZip,
Janus, etc; only DietIFNA. (SEAlink in a YooHoo session) If you
don't have support for this, what will occur I suppose is a
fallback to FTS-1 type sessions.

Also, I do recall systems running under SEAMail who wouldn't even
do Yoohoo sessions, they would use they would use SEALink in a
session that IIRC is like FTS-1; as detailed in FTS-7, and Bark
f'reqs as per FTS-8.

Incidentally, support for FTS-1 sessions, the basic protocol, is
*required* for FidoNet nodes, according to network policy. If your
mailer doesn't support FTS-1, it's unsuitable for usage on a node
in FidoNet.

                       JBL

... nfx v3.1 DOS isn't dead, it just smells funny.                           
--- Platinum Xpress/Win/Wildcat5! v3.0pr2