home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
SFCMB15.ZIP
/
SFCMB.DOC
< prev
next >
Wrap
Text File
|
1994-10-13
|
9KB
|
189 lines
╓───────────────────────────────────────────────────────────╖
║ SFCMB v1.5 Spitfire Clean Message Base Utility ║
║ Copyright(C) 1994 by Kevin Cummins ║
║ Crimson Cross BBS (618)253-3608 USR Dual 28.8 ║
╙───────────────────────────────────────────────────────────╜
Brief Description:
══════════════════
SFCMB is a utility for SF 3.5+ that attempts to 'clean' up your
message base from offensive, profane, or unwanted text. It scans
the message body, as well as the TO:, FROM:, and SUBJECT fields
in the message header. When a violation is found, SFCMB either
marks that message for Deletion, or masks the offensive text
with the '*' character. The action taken is determined by the
individual sysop.
Installation:
═════════════
Place SFCMB.EXE in your main Spitfire directory, where it can
find SFNODE.DAT. It MUST execute from there!
You can run SFCMB without doing anything else as far as
Installation. SFCMB has an internal list of the most commonly
found words that are offensive to any BBS sysop concerned with
this sort of thing. As an OPTION, you can create your own list
of words that SFCMB will use to scan messages for. If you wish
to use your own list, read the following info. If you wish to
use the internal list, you may skip ahead to the section
entitled 'Execution'.
SFCMB looks for the file, BADWORDS.LST in the default directory
at runtime. BADWORDS.LST is a file that you must create if you
choose not to use the internal list. If not found, it uses the
internal list of words.
NOTE: SFCMB will only use one list, either the internal or the
external. It will NOT use a combination of both!
BADWORDS.LST can contain up to 25 words, each on a separate
line, with a 15 character field limit. Simply enter each word on
its own line (case doesn't matter), and save in standard ASCII
format.
NOTE: Read this carefully! I have found a slight
problem that can be created when setting up your
BADWORDS.LST, and I need to explain. I have provided a
work-around for this, *IF* you set it up correctly. I
have to be explicit here, so please be forgiving. :)
For example, if you were to put the word 'ASS' in your
list, SFCMB will recognize words like ASSUME, MASS,
etc to be offensive, when they are not in fact. The
only way I can think of is to look for a space before
and after the string for words like this. You CAN add
a space of front of the word in the .LST file, but you
CANNOT add a space at the end, as it will be trimmed
when read into the variable. So, what we will do is
substitute another character for a leading or trailing
space for words like the above when you want to
include them in your list. I am going to use the
underscore character (_) to represent the space in the
.LST file.
So, given the above, you could enter _ASS_ in the .LST
file, and it would be recognized as offensive only
when it is preceded AND followed by a space. The only
time it might be missed, is if the word is at the very
beginning or very end of a line. With a probability
factor figured in, I think this will work at least
90%+ of the time.
Again, using the above word as an example, you can
probably think of another word that WOULD be made up
of the first word: ***HOLE. I hope you can see that
you would need to enter this word as a separate entry
to the above, or it will now be overlooked because of
the way you have set up the first one.
While working on this project, I can see that
filtering out the bad words can, in some instances, be
difficult without affecting some messages that are
entirely harmless. If you have any questions, or
suggestions regarding the above, PLEASE let me know.
Execution:
══════════
To execute SFCMB, you MUST include at least one command line
parameter, that being the conference number(s) you wish SFCMB to
process. For example, if you want to run it on only one
conference, you would enter SFCMB 5. This would cause SFCMB to
process message area #5.
Entering SFCMB 5..10 would process message areas 5-10. Simple
enough?
Optionally, you can enter MASK after the conference number, to
force SFCMB into Mask mode instead of the default of 'MARK
MESSAGE FOR DELETION' mode. A second parameter is not necessary
if you wish to use the delete mode.
When a positive scan is found, that message is either masked or
marked for deletion, and a line is written to the file SFCMB.LOG
informing the sysop of the Scan time, message number, and
conference number for future reference.
If no message violations are found, SFCMB simply quits. If it
does find any, it will import a message to the sysop in
conference #1 stating that such messages were found and taken
care of.
SFCMB writes its activities to a file called SFCMB.LOG. It
records the date and time of each execution of SFCMB, and logs
the message number and conference number for any offending
messages found so that you can easily track what SFCMB is doing.
It also logs if the violation was found in the message body or
the message header.
Question?
═════════
If I put someone's name or an alias or whatever in BADWORDS.LST,
will it DELETE any messages entered by that person?
A: Yes, it should. But, keep one thing in mind. SFCMB, in its
present form, will mark any message that contains that name in
the message body as well as the message header. For instance, if
you have JOE BLOW in your BADWORDS.LST, SFCMB will mark any
message that has that name in it, whether in the message body,
or the header. The message might not be from JOE BLOW, but could
just be about him, and still will be marked by SFCMB.
Registration:
═════════════
Listed below are the most important differences in the REGISTERED
version of SFCMB vs. UNREGISTERED.
UNREGISTERED:
1: The message imported to the message base is flagged as
<P>ublic.
2: This message also has an unregistered reminder in the
message body.
3: There is an occasional reminder to register your
shareware version. You will only see this about 10% of
the time.
REGISTERED:
1: The message imported is flagged <P>rivate.
2: The unregistered reminder is replaced by your name and
registration number.
3: No shareware reminders.
Registration is provided through Crimson Cross BBS. All you need to
make your copy of SFCMB registered is the proper registration
number, which will be available for download from Crimson Cross as
soon as possible after receiving your registration form. (usually
less than 24 hours)
Registration for SFCMB is only $5, which I think is plenty
reasonable for utilities of this sort. I, too, am a sysop so I
understand the cost involved for BBS operation. :)
Disclaimer:
═══════════
Use of this program acknowledges this disclaimer of warranty: "This
program is supplied as is. Kevin Cummins disclaims all warranties,
express or implied, including, without limitation, the warranties
of merchantability and of fitness of this program for any purpose.
Kevin Cummins also assumes no liability for damages direct or
consequential, which may result from the use of this program."
Distribution:
═════════════
SFSNS is released as Shareware. You are welcome to distribute it
freely in it's unmodified form. You may evaluate it for a period of
thirty days, and are then requested to register if you continue
its use.
Questions, comments, or program suggestions can be directed to Kevin
Cummins at:
Crimson Cross BBS 618-253-3608 RIME Network
100 Humphrey Road Node: #1390 CCBBS
Harrisburg, IL 62946