ml>> i do know that FD sends the EMSI text... it has to so the
 ml>> remote end can see it to act on it if it wants to... its
 ml>> up to the BBS to send the IEMSI text and handle that...

 ml>> are we confusing EMSI and IEMSI?

 IJ> marc ...

marK ;)  marC is the one in louisana >

 IJ> I use FD to make calls to other BBSes as a terminal...

actually, that's the terminal app that's built in... joho actually
extracted it and compiled it seperately... its known as fdterm to those who
have it ;)

 IJ> I do it with both versions ... OS2 & DOS and have
 IJ> no problems

right... its not that there are any real problems but that the EMSI and/or
IEMSI trigger strings are visible...

 IJ> If the other BBS system supports EMSI FD will use it...
 IJ> I have a test ELE BBS system and FD logs on with EMSI
 IJ> okay.

just to clarify... EMSI is mailer to mailer... IEMSI is Interactive and
terminal to bbs... there's a very important distinction there... hummm... i
think i understand, now, where this thread started but i don't know if
anything can be done about it... part of the "problem" is likely
from the bbs side and the order in which it detects ANSI and sends the
IEMSI trigger...

)\/(ark