-=> Charles Stephenson wrote to mark lewis <=-
ML> CS> Got it working here, now to figure out why Areafix wont work
ML> CS> right in Synchronet... Ugh....
ML> what problems are you having with sbbsecho's areafix? it does use a
ML> slightly different syntax than traditional areafix...
CS> It just 'stopped' working. It's been working flawlessly for over
CS> a year now, now I can't seem to send my Hub a areafix. At this
CS> point, I don't know if it's error on my part or my hub. I've been
CS> trying to contact him via netmail and email. I can send/recieve
CS> netmail fine. I'm now looking for another hub to feed my other
CS> BBS..
This doesn't really make any sense...
If you can "send/receive netmail fine", then the problem is
obviously at the hub's end. Sending your hub an areafix is
nothing more than sending a netmail. If the hub doesn't respond
properly to that netmail, it's a problem at the hub. If the hub
is running Synchronet, then yes, it could be a problem with the
hub's SBBSecho.
All of this is assuming you're sending a properly formatted
netmail to the hub's "areafix". Should be to "Areafix@1:xxx/xxx"
with your areafix password in the Subject line, and then the
desired areafix commands (like +FIDONEWS) in the body of the
netmail.
I'd recommend checking all of the above requirements for a
properly formatted Areafix netmail, and if it is indeed correct,
then send a regular netmail to the Hub Sysop asking why things are
not working. Good luck!
... Internal Error: The system has been taken over by sheep at line 19960
=== MultiMail/Linux v0.52
--- SBBSecho 3.10-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
|