Subj : Problems with TELGATE
To : Night Owl
From : Digital Man
Date : Fri Sep 10 2004 11:53 pm
Re: Problems with TELGATE
By: Night Owl to Night Owl on Sat Sep 11 2004 01:22 am
> RE: Problems with TELGATE
> BY: Night Owl to Digital Man on Fri Sep 10 2004 23:36:29
>
> Digital -- After you gave me a clue at what to look at I started playing aro
> with the telgate.src file -- made two new files: telgate1.src and telgate2.s
> Basicly in Telgate1.src I removed the line:
>
> printf "\r\n\1h\1hPress \1yCtrl-]..... blah blah
> pause
>
> compiled telgate1.src and it worked fine -- connected right to vert.synchro.
>
> In telgate2.src I left everything the same, but took out the pause line -- a
> worked fine. and connected right to vert.synchro.net
>
> I don't know what that "pause" command does --
It displays a "Hit a key" prompt.
> I did change the default paus
> while ago -- do you think that might have something to do with it?
Absolutely. If your 3rd party pause module over-writes the "str" variable, that
would break telgate and probably a lot of other modules.
> I'm not sure, is it going to hurt anything if I remove the pause out of the
> telgate.src file and recompile it??
No, but it doesn't truely fix the problem (your pause module).
> Thanks again for all your help!!! This one is fixed, one problem at a time -
> I'm getting a large amount of errors when I'm sending netmail, sometimes it
> works, sometimes it doesn't
> The errors I'm getting are:
>
> 0000 !SEND ERROR -103 (corrupt message header ID:SMB ) reading message heade
> #0
> 1196 !SOCKET INACTIVE
Are you talking about netmail (QWK or FidoNet) or Internet e-mail? In any case,
if you have a corrupted mail database (run chksmb on it to find out), you can
use fixsmb to fix it.
> I had it working at one point, and it stopped working again -- that one did
> have something to do with the DNS in the mail server configuration -- I'm
> starting to think that my ISP (Time Warner Road Runner) is blocking the SMTP
> port -- It's only a guess....
> Does anyone know if I need to have the SMTP port open on my router -- or sho
> I close that, and see what happends?
TCP ports have nothing to do with the above errors.
digital man
Snapple "Real Fact" #126:
A pigeon's feathers are heavier than its bones.
---
� Synchronet � Vertrauen � Home of Synchronet � telnet://vert.synchro.net
