TIP: Click on subject to list as thread! ANSI
echo: ftsc_public
to: PAUL QUINN
from: NICHOLAS BOEL
date: 2014-10-20 16:34:00
subject: Re: FTSC-5001 question

Hello Paul,

On 20 Oct 14 08:55, Paul Quinn wrote to Nicholas Boel:

 PQ> Hi! Nick,

 PQ> On 10/20/2014 07:20 AM, you wrote:

 AL>>> The best thing to do is have Argus answer telnet on an alternate
 AL>>> port such as 60177.  Then just list it in the nodelist as
 AL>>> ITN:60177.  That way BBS callers on port 23 get right to the BBS
 AL>>> and mail can still come in via telnet at the same time.  I run
 AL>>> MBSE this way and it works fine.

 NB>> That's exactly what I was asking and the direction I was going
 NB>> with what I had posted. Thank you for the confirmation on that!

 PQ> Bad logic IMHO.  MBSE is handicapped.  It is a BBS, with mailer
 PQ> functions.  My shortcoming now: I _think_ that ports specified in
 PQ> MBSE's config cannot be re-used between BBS & mailer functions.

I think it's more in the sense of BBS softwares that run a telnet server on
port 23. It's apparant (since you've said so) that you can run Argus as your
frontend, and not run a BBS telnet server.. but some people prefer to run the
BBS's telnet server and use Argus aside from that. In that case, you would have
to run the mailer's telnet server on another port - which is the direction I
was originally going with it as well as Andrew.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/701)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.