Virtual Private Server (VPS) Hosting provided by Central Point Networking cpnllc.com
For some reason, the "Nodelist" and "Recent Callers" features are not working.
| Sysop: | Ray Quinn |
|---|---|
| Location: | Visalia, CA |
| Users: | 60 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 64:38:49 |
| Calls: | 12 |
| Files: | 12,938 |
| Messages: | 99,119 |
Check out the US 99 menu above for links to information about US Highway 99, after which the US 99 BBS is named.
Be sure to click on the Amateur Radio menu item above for packet BBSes, packet software, packet organizations, as well as packet how-to's. Also included is links to local and some not-so-local Amateur Radio Clubs.
I've so far focused on Argus. It's still the original, very elegant source. But what additions (but a lot of added bugs) do y'all think that Radius has?
I tend to stay with Argus. It's so much easier to maintain, and I don't see any real advantages with Radius, really.
Radius has some slightly better nodelist parsing ability.
biggest advantage is the treatment of semaphores: having both a
dedicated directory, and the ability to add custom-designed semaphores.
Argus by another name, by your hand, could a Good Thing. 8-)
P.S. When the time of general introduction of IPv6 comes, I will be switching to Linux.
biggest advantage is the treatment of semaphores: having both asemaphores.
dedicated directory, and the ability to add custom-designed
Indeed. But on the other hand, us batch file phantoms can probably
do with just one semaphore file exit, can't we? With an 'EXEC_NOW.OK'
flag file that causes Argus to execute 'EXEC_NOW.BAT' (as I've made it now) wouldn't that actually be enough?
P.S. When the time of general introduction of IPv6 comes, I will be
switching to Linux.
Negatory! You'll hang on to the good old Argus family, by then IPv6 aware, you hear!
Paul? Mark? You were the ones who made me make the switch from
Argus to Radius, what do *you* think?
Indeed. But on the other hand, us batch file phantoms can
probably do with just one semaphore file exit, can't we? With an 'EXEC_NOW.OK' flag file that causes Argus to execute 'EXEC_NOW.BAT'
(as I've made it now) wouldn't that actually be enough?
Argus by another name, by your hand, could a Good Thing. 8-)
Thanks. I'll at least make sure it'll be 100% backwards
compatible -- Mark convinced me of that.
P.S. When the time of general introduction of IPv6 comes, I will be switching to Linux.
Negatory! You'll hang on to the good old Argus family, by then
IPv6 aware, you hear!
I tend to stay with Argus. It's so much easier to maintain, and I don't see any real advantages with Radius, really.
Paul? Mark? You were the ones who made me make the switch from Argus to Radius, what do *you* think?
I switched from Argus to Radius mostly for aesthetic reasons and because I assumed since Radius appeared to be derived from Argus it'd be less buggy.
If Argus is a viable base to develop from and is being actively developed/patched, I'd be happy to switch back.
but the mailer is not exiting, is it??
The only reason I switched was because Radius could handle flag
files. Now fixed in Argus -- well it can only search for one file, EXEC_NOW.OK, and then executes EXEC_NOW.BAT, but one file was all I
needed anyway.
Paul? Mark? You were the ones who made me make the switch from
Argus to Radius, what do *you* think?
it doesn't matter to me, really... i like taurus and the additional capabilities it has...
cannot send from Taurus at the moment
On Sat, 29 Nov 2014, Bj├╢rn Felten wrote to Paul Quinn:
Indeed. But on the other hand, us batch file phantoms can
probably do with just one semaphore file exit, can't we? With an
'EXEC_NOW.OK' flag file that causes Argus to execute 'EXEC_NOW.BAT'
(as I've made it now) wouldn't that actually be enough?
but the mailer is not exiting, is it?? the capability is easily handled
by the even scheduler as paul showed previously... or am i missing something besides a decent beverage again??
That's the thing: it's not something based on an event but simply the appearance of the flag from an external source (JamNNTPd in this case,
for whenever there's mail to scan out). Argus cannot do this itself with the supplied flag-file (aka semaphore) responses. So, Bj├╢rn is adding on this function in his revised version of Argus.
Note to self. Paul got confused, and thought that EXEC_NOW.[OK/BAT]
could serve as a standard naming convention that could be used by
several functions, for different reasons. He did think that the BAT
could be pre-loaded with some task's script and then called using the flag. Paul had forgotten that Argus works in a multi-tasking
environment, and that there could come an instant where several tools/events might want to use the EXEC_NOW.[OK/BAT] simultaneously.
Silly boy, he is.[sfx; smack! to the forehead]
cannot send from Taurus at the moment
What does Ctrl-P show you?
it won't sent netmail
it won't sent netmail
How do you convert your netmail (*.MSG?) to a proper *.PKT file,
how do you put it in the proper "OUT" directory?
Paul? Mark? You were the ones who made me make the switch from
Argus to Radius, what do *you* think?
it doesn't matter to me, really... i like taurus and the additional capabilities it has...
My name is Ian Segers from bbs called 1st Choice Core in Ashburton
New Zealand and I am using Taurus, and I have got it to receive pkt
which is good but I ust cannot send from Taurus at the moment I am
useing Taurus for inbound and irex for ontbound.
Can you or same one else help me with that via this echo or ICQ.
how do you put it in the proper "OUT" directory?
When I process this message via sbbsecho.exe, it goes to the taurus outbound but as 1:340/400@outbound I have to manual change it to 1:340/400@fidonet then works
netmail in taurus outbound via *.msg the *.msg there but @ 3:770/330@fidonet which is my address
if the netmail is in pkt form in dir of out in taurus outboound its
@ 3:770/330@fidonet with no pkt attached
On Sun, 30 Nov 2014, Ian Segers wrote to mark lewis:
Paul? Mark? You were the ones who made me make the switch from
Argus to Radius, what do *you* think?
it doesn't matter to me, really... i like taurus and the additional capabilities it has...
My name is Ian Segers from bbs called 1st Choice Core in Ashburton
New Zealand and I am using Taurus, and I have got it to receive pkt
which is good but I ust cannot send from Taurus at the moment I am
useing Taurus for inbound and irex for ontbound.
do you mean you cannot get it to send to another system via http or one
of those other capabilities??
Can you or same one else help me with that via this echo or ICQ.
handling it in the echo would probably be the best... that way many
eyes can be brought into play ;)
this seems to indicate that you are trying to operate your mailer in 5D format when your tosser (sbbsecho) is only 4D... you must operate your mailer in 4D also... that means that you'll have only one outbound directory defined and others will be derived from it... all domains
will appear the same... it is the zone addresses that will make the difference...
what is your outbound directory definition in ?
what is your outbound direcrory definition in argus/radius/taurus?
netmail in taurus outbound via *.msg the *.msg there but @ 3:770/330@fidonet which is my address
if the netmail is in pkt form in dir of out in taurus outboound its
@ 3:770/330@fidonet with no pkt attached
this is hard to understand... PKT names are 8.3 format... are you
trying to use taurus' dynamic netmail packing capability? taurus and sbbsecho should not know of the other's MSG directory... sbbsecho
handles its MSG directory all on its own and in its own special way...
it is much different than what other mailers would expect...
I unticked the 5d outbound in Taurus path config, didn't make
much differnce unless there is same were else I was meant to do
it.
what is your outbound directory definition in ?
in sbbsecho.cfg is d:\bbs\fd\outbound\
what is your outbound direcrory definition in argus/radius/taurus?
in rgus/radius/taurus its D:\bbs\fd\outbound
netmail in taurus outbound via *.msg the *.msg there but @ 3:770/330@fidonet which is my address if the netmail is in pkt
form in dir of out in taurus outboound its @ 3:770/330@fidonet
with no pkt attached
this is hard to understand... PKT names are 8.3 format... are you
trying to use taurus' dynamic netmail packing capability? taurus and sbbsecho should not know of the other's MSG directory... sbbsecho
handles its MSG directory all on its own and in its own special way...
it is much different than what other mailers would expect...
Should I have the dynamic netmail packing capability unticked
in taurus netmail preference.
Should I have the dynamic netmail packing capability unticked
in taurus netmail preference.
yes, you need to operate taurus in pure BSO/FLO mode... [...]
my apologies, ian... i've only helped setup and operate sbbs in a BSO/FLO environment... it just sudenly hit me that you may be attempting to operate sbbs in a FD style environment... i don't know how that would work with sbbs and sbbs' netmail directory... let's see if we can get you working properly and sending netmail in BSO/FLO mode and then the other form may be looked into if desired...
my apologies, ian... i've only helped setup and operate sbbs in a
BSO/FLO environment... it just sudenly hit me that you may be
attempting to operate sbbs in a FD style environment... i don't
know how that would work with sbbs and sbbs' netmail directory...
let's see if we can get you working properly and sending netmail
in BSO/FLO mode and then the other form may be looked into if
desired...
You may not be aware, but Synchronet does not have a netmail
folder.
At least not one that you can access remotely.
If using FD style then you set up a folder that it writes netmail
to, to send out. and netmail is imported into that same folder
from the mail packets, if it cannot be imported by sbbsecho.
I think much the same will hold true in BSO style.
If using FD style then you set up a folder that it writes netmail
to, to send out. and netmail is imported into that same folder
from the mail packets, if it cannot be imported by sbbsecho.
that's something that will require some additional research... everything i've found so far has been running sbbsecho with binkd in BSO format...
I think much the same will hold true in BSO style.
in BSO format, you're not even presented with a netmail directory field to fill out...
On Mon, 01 Dec 2014, Ian Segers wrote to mark lewis:
I unticked the 5d outbound in Taurus path config, didn't make
much differnce unless there is same were else I was meant to do
it.
no, that's the one place...
what is your outbound directory definition in ?
in sbbsecho.cfg is d:\bbs\fd\outbound\
what is your outbound direcrory definition in argus/radius/taurus?
in rgus/radius/taurus its D:\bbs\fd\outbound
those two look ok... Zone 3 is your default outbound so your outbound directories would match like this...
D:\bbs\fd\outbound Z3
D:\bbs\fd\outbound.001 Z1
D:\bbs\fd\outbound.002 Z2
D:\bbs\fd\outbound.004 Z4
D:\bbs\fd\outbound.028 Z40
the plain "outbound" or "out" or whatever you want to name it is always your default zone... your default zone is taken from your first FTN address... the other directories are given an extension, in hex, of the other zones...
netmail in taurus outbound via *.msg the *.msg there but @ 3:770/330@fidonet which is my address if the netmail is in pkt
form in dir of out in taurus outboound its @ 3:770/330@fidonet
with no pkt attached
this is hard to understand... PKT names are 8.3 format... are you
trying to use taurus' dynamic netmail packing capability? taurus and sbbsecho should not know of the other's MSG directory... sbbsecho
handles its MSG directory all on its own and in its own special way...
it is much different than what other mailers would expect...
Should I have the dynamic netmail packing capability unticked
in taurus netmail preference.
yes, you need to operate taurus in pure BSO/FLO mode... in sbbs'
echocfg program, what mailer type do you have selected? this should be binkley/FLO...
taurus should not be looking in any special directory
for netmail... sbbsecho has to do your netmail packing and routing...
with that said, what does your sbbsecho.cfg contain for its DIRECT and ROUTE_TO lines?
)\/(ark
* Origin: (1:3634/12)
Following up a post on Mon, 01 Dec 2014, from mark lewis to Ian Segers:
Should I have the dynamic netmail packing capability unticked
in taurus netmail preference.
yes, you need to operate taurus in pure BSO/FLO mode... [...]
my apologies, ian... i've only helped setup and operate sbbs in a
BSO/FLO environment... it just sudenly hit me that you may be
attempting to operate sbbs in a FD style environment...
i don't know
how that would work with sbbs and sbbs' netmail directory... let's see
if we can get you working properly and sending netmail in BSO/FLO mode
and then the other form may be looked into if desired...
these directories, do I have to create them myself or does taurus
creates them itself.
taurus should not be looking in any special directory for
netmail... sbbsecho has to do your netmail packing and routing...
with that said, what does your sbbsecho.cfg contain for its DIRECT
and ROUTE_TO lines?
Direct is yes
ROUTE_TO is set to my provider 1:340/400
Netmail format is *.msg and front door I use to post a netmail
message
these directories, do I have to create them myself or does taurus
creates them itself.
your mail tosser should create them as needed and then only for the
zones that mail is destined to... in some cases, a mailer may remove
them when there is no more mail in them to be sent but i don't recall if the argus family does this or not... i have seen it in my taurus but
only fleetingly and only once...
On Tue, 02 Dec 2014, Ian Segers wrote to mark lewis:
these directories, do I have to create them myself or does taurus
creates them itself.
your mail tosser should create them as needed and then only for the
zones that mail is destined to... in some cases, a mailer may remove
them when there is no more mail in them to be sent but i don't recall
if the argus family does this or not... i have seen it in my taurus but only fleetingly and only once...
[trim]
taurus should not be looking in any special directory for
netmail... sbbsecho has to do your netmail packing and routing...
with that said, what does your sbbsecho.cfg contain for its DIRECT
and ROUTE_TO lines?
Direct is yes
hunh? are you talking about in some of your node entries in echocfg?
I was looking for the line from your sbbsecho.cfg file...
ROUTE_TO is set to my provider 1:340/400
can you post those lines, too, please? i'm looking to see what happens with netmail to nodes that you do not have specific routing for...
Netmail format is *.msg and front door I use to post a netmail
message
ahhh... yes, that complicates things a little more... right now i'm thinking that sbbsecho will hopefully see those and pack them into
BSO/FLO style and set them where they need to be for delivery... i
think we're getting down to your route_to lines missing default (aka
catch all) routing... that's why i wanted to see the above two
mentioned sets of lines from your sbbsecho.cfg file ;)
ahhh... yes, that complicates things a little more... right now i'm thinking that sbbsecho will hopefully see those and pack them into
BSO/FLO style and set them where they need to be for delivery... i
think we're getting down to your route_to lines missing default (aka
catch all) routing... that's why i wanted to see the above two
mentioned sets of lines from your sbbsecho.cfg file ;)
Not sure if this will help you at all
sbbsecho.cfg file :-
-----------------------------------------------
PKTPWD 1:14/400 XXXXXXXX
PKTPWD 1:340/400 XXXXXXXX
DIRECT 1:14/400 1:229/426 3:770/1 1:340/400
ROUTE_TO 3:770/1 3:770/1
ROUTE_TO 1:340/400 1:340/400
Yes, the other zones' directories are created & destroyed. Such an annoying behaviour that I permanently created the two directories for zones 1 & 2, with a .jpg called 'KilroyWasHere' in each. It might be a virtual HD but all the disk thrashing still irked me.
PKTPWD 1:14/400 SUSPECT0
Joe Delahaye wrote to Ian Segers <=-
Re: Re: RFC seriously
By: Ian Segers to mark lewis on Wed Dec 03 2014 18:06:00
PKTPWD 1:14/400 SUSPECT0
I hope these are fake paswords??
sbbsecho.cfg file :-
/there/ ya go :)
-----------------------------------------------
PKTPWD 1:14/400 XXXXXXXX
PKTPWD 1:340/400 XXXXXXXX
make sure you change your PKT passwords with those two systems unless
the ones i X'd out were already faked by you for this posting... and
your AREAFIX passwords!
DIRECT 1:14/400 1:229/426 3:770/1 1:340/400
there's one of the lines i was after...
ROUTE_TO 3:770/1 3:770/1
ROUTE_TO 1:340/400 1:340/400
and there's the other ones...
ok, so you do not have any fallback "catch all" routes in place... you need something to tell sbbsecho where to send netmails that do not have any other directions... so we'll do that here... edit your sbbsecho.cfg and change the two lines above like this...
ROUTE_TO 3:770/1 3:ALL
ROUTE_TO 1:340/400 1:ALL 2:ALL 4:ALL
you don't need to route mail thru a system to itself... the above two changes will
* route all non-direct Z3 netmail to paul hayton's system
* route all non-direct Z1, Z2 and Z4 netmail to robert starr's system
that should all netmails to any system to be sent routed... the four systems listed in your DIRECT line above are the only ones that will go DIRECT -=unless=- you have SCFG->Networks->FidoNet EchoMail and NetMail
- NetMail Defaults to Crash Yes AND/OR
- NetMail Defaults to Direct Yes AND/OR
- NetMail Defaults to Hold Yes
those control netmail from within synchronet... we keep them all set to
No so the routing laid out in sbbsecho.cfg takes over and controls
where things go...
the only other thing i can think of is your FIDOIN and FIDOOUT events
in SCFG->External Programs->Timed Events...
FIDOIN %!sbbsecho%. -belrsy!
FIDOOUT %!sbbsecho%. -linf
i /know/ that the FIDOIN command line is slightly different than the default that comes with synchronet... one change was the order of the options... the other change is more important in some respects in that
it allows users on your bbs to write netmail to another user on your bbs... they shouldn't use netmail for this but they can... what happens
is that the netmail is exported into the sbbs netmail directory and it would sit there and not go any further... the additional option in the above FIDOIN tells sbbsecho to import those local netmails back into
the bbs since they are destined to a user on the bbs... in other words, local and foreign netmail written to users on your bbs will be imported
to them...
in any case, i think the above should take care of netmail from the bbs going routed... you can try using FM to send netmail if your FD netmail area is still pointing at the sbbs netmail directory... the key is that when you write netmail in FM, you'll also need to touch the sbbs\data\fidoout.now semaphore file or wait for someone to write a FTN network message on the bbs for that event to be triggered and the mail scanned out... you might need to touch the sbbs\data\fidoin.now
semaphore in some cases to toss mail into the bbs... your mailer should
be creating the fidoin.now one already so that mail is tossed when it arrives... unless you have a cron job doing that for you on a certain schedule ;)
alright... i've been up over 24 hours again and i'm rambling...
sorry... i'm off'a'here ;)
I hope these are fake paswords??
No it not fake, posted it by mistake, how ever all password that I posted have been changed
and I won't be doing that again.