home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Pier Shareware 6
/
The_Pier_Shareware_Number_6_(The_Pier_Exchange)_(1995).iso
/
005
/
wildpack.zip
/
TOALL.DOC
< prev
next >
Wrap
Text File
|
1994-12-05
|
5KB
|
106 lines
To All: Utility to send messages to ALL
Table Of Contents:
1) Functionality / Description
2) Setup
3) Unregistered Restrictions
1) Functionality:
Have you ever wanted to send a message to all so that it goes into
EVERYONES mailbox only to find that you message is just hanging in limbo
pretty much addressed to noone and only those activly searching will find
your message?
Well, this will happen no more. With this application, if you send a
message to ALL, EVERYONE will get that message in their mailbox. Otherwise,
it fuctions like normal. So you can also use this same application to send a
message to just one person. So in effect, it is just an enhanced version of
the existing 'ENTER A MESSAGE' option. The only thing that this does not do
is ask which conference the message is getting routed to (it only sends it in
the current conference. The ability to route the message to another
conference will come in the next minor revision).
Also with TOALLSET, as newusers log on, they will be added to the
necessary files so that when a user does send a message to ALL that user will
be sending to all the users that are part of the BBS up-to-the-minute.
2) Setup:
This one is probably the most difficult to set up out of all the
applications included in WILDPACK. It would help if you had some knowledge of
the GROUP###.LST files and how Wildcat uses them.
Basically, a sysop can create a GROUP###.LST file with a bunch of users
names (lets say, all the users in the database). Well, not only does the
sysop have to create the file, but must also keep it up to date AND the sysop
must tell all the users the name of the file and that it is available. Once
ALL of that is done, when a user 'ENTER's a message, that user could (instead
of sending it to a user name) send it to GROUP???.LST (whatever the sysop set
up) and that message will be distributed to all the users that are listed in
the GROUP###.LST file. Well, that is a hell of alot of work for both the
Sysop and the users and it is no wonder why there are not very many Sysops
who actually offer that functionality.
These two applications negate all that work. The TOALLSET adds the names
to the (sysop defined) GROUP###.LST files (if they are not currently added
to the file) and keeps them up to date. The TOALL actually uses those
GROUP###.LST files to distribute the message if a users sends the message to
ALL.
You must create a file called TOALL.INI in the current directory (The
Wildcat Home Directory). All of the WILDPACK applications MUST be run from
your Wildcat Home Directory. A sample will be included, but unless you are a
registered sysop, the TOALL.INI will not be used. However, even if you are
an unregistered sysop, the INI file MUST EXIST.
Here is an example of the TOALL.INI:
5
NEWUSER = GROUP1.LST
FULLUSER = GROUP1.LST
SUBSCRIBER = GROUP2.LST
SYSOP = GROUP9.LST
Here is what it all means:
Comment number to use to keep track of who has been added
Security Level = GROUP###.LST
*Notice: The INI file must be formatted this way. The comment number first
followed by all defined security levels/GROUP###.LST files. There
can be spaces on either side of the '=' sign.
So basically what happens (using the above example) is that when a user
logs on, TOALLSET will check your defined comment field for the string
'ADDED'. If it does not find that string, then the application adds that
users name to the GROUP###.LST file that they are associated by security
level with. This way, the GROUP###.LST files will be kept up-to-date as users
log on.
When a user with a sysop defined security level sends a message to ALL,
the TOALL application uses the GROUP###.LST file associated with that
security level and distributes the message to ONLY those users listed in that
GROUP###.LST file. So this being the case, when a SUBSCRIBER (again, using
the above example) send a message to ALL, the user will be sending that
message ONLY to other SUBSCRIBERs. In a future revision of this application,
there are plans to add the functionality so that you can associate more than
one GROUP###.LST file per security level.
The TOALLSET application must be added to your LOGON.WCX in order for it
to insure that the GROUP###.LST files are kept up-to-date as users log on.
The TOALL application can be setup to replace the 'ENTER A MESSAGE' menu
option.
3) Unregistered Restrictions:
The only restriction is that you can only use GROUP1.LST. All defined
security levels will be part of that GROUP file, so in effect all users will
be part of that file. You will not be able to break it up by security levels.
You can (and MUST) still define all security levels that you will allow to
use this functionality.