home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
gigop806.zip
/
MAPPING.FAQ
< prev
next >
Wrap
Text File
|
1994-04-26
|
5KB
|
114 lines
Q: What is the difference between the various mapping commands?
Q: What are the differences between +, -, =, <, >, @, and ! ?
A: This is a relatively _simple_ part of your configuration.
In your mapping, you can specify (using =, <, and >) direct
transations from newsgroups to echomail and vice versa.
= newsgroup.name ECHOMAILNAME
= newsgroup.name2 ECHOMAILNAME2 moderator@somesite.org
The above two examples are how to perform a direct translation,
when the name of the newsgroup and the name of the echomail areas
are different, or are not to be subject to change by other commands.
The second example shows how to treat a moderated newsgroup; you
simply include the moderator's address.
< tousenet.name TOUSENETECHO
> tofidonet.name TOFIDONETECHO
The above two examples show how to make one-way gateways;
some people do this to stop postings from fidonet, so as not to
clutter the internet side but still allow for discussion in the
fidonet realm.
The remaining symbols are where GIGO's magic really come in.
"+" and "-" are mapping verbs that allow GIGO to use wildcards
when translating newsgroups and echos. When GIGO finds a matching
line with a "+" or "-", GIGO will keep on searching the rest of the
mapping configuration for other "+" or "-" commands. "+" will turn
that newsgroup on, whereas "-" will turn it off.
+ alt.*
+ comp.*
+ talk.*
- *.politics
- *.politics.*
+ *msdos*
The above example keeps all of the alt, comp, and talk newsgroups,
_except_ anything to do with politics. In addition, any newsgroup
with the phrase "msdos" in it (no matter what heirarchy) will be
included, even things like comp.os.msdos.programmer, fubar.msdos,
and quazi.msdos.announce.
Q: What is the "!" mapping option?
A: This signifies that a special command to save the messages from
that newsgroup to either individual files, or to a single log file,
is desired. Examples of current commands:
! newsgroup.name LOGTEXT logfile.log
! newsgroup.name LOGTEXT logfile.log ECHOAREANAME
Both of the above examples are one-way gates, from newsgroup.name.
The second case is how to allow it to still post as echomail. In both
cases, the message that came in for the newsgroup is appended, headers
and all, to logfile.log ..
! newsgroup.name SAVETEXT dirname\
! newsgroup.name SAVETEXT dirname\ ECHOAREANAME
Both of the examples above save the message as a single *.IN file,
in the area specified. Potentially, you can capture the messages
in the MSDOS binaries newsgroups, and run a secondary program
to decode the *.IN files into binary files for your file section.
! .. SAVETEXT and ! .. LOGTEXT work exactly like USER .. SAVETEXT
and USER .. LOGTEXT do.
Q: How can I translate a mailing list into echomail format?
Q: What is the "@" mapping option?
A: [This does NOT apply if you are trying to HOST the mailing list -
this section _only_ applies if you are simply translating the list].
The first step is to subscribe to the mailing list, using a unique
address. For example, if you are going to subscribe to the GIGO
mailing list, you would want to subscribe from an account
such as "list-gigo" (change your name to list-gigo before sending
in the subscription request).
Once you start getting messages to that unique account name, you can edit
your mapping.cfg file. In your mapping config, you will need to use the
"@" option. You will need to know what account you subscribed
with, the name of the echo you want to create, and the address where
new messages should be sent to.
@ list-gigo@mysite.org GIGO_SUPPORT gigo-l@wmeonlin.sacbbx.com
The above statement tells GIGO, that any time a message comes in for
the user "list-gigo", to instead treat it as echomail, and to place
that echomail in an echo called GIGO_SUPPORT. Any messages that you
or your users post in that echo, should be sent to the second
address (in this case, gigo-l@wmeonlin.sacbbx.com) to be reposted
into the mailing list.
Q: How come the mailing list keeps rejecting messages from my users?
Some mailing lists are ran in a "secure" mode. What this means,
is that only the users actually registered in the mailing list are
allowed to post to the mailing list.
When you tell GIGO to translate a mailing list, you are subscribing
with a name (such as list-gigo). When you or a user posts, however,
that name is not what is sent to the mailing list - the user's real
address is sent. When the mailing list is being ran in a secure
fashion, it automaticly rejects the message, due to that user not
being a participant in the mailing list.
The only way around this, is to contact the administrator of that site.
However, most running a secure mailing list are not willing to compromise
the security of that mailing list - your only option in this case is to
either make the mailing list read-only, or to let individual people to
subscribe, and let them receive the mailing list as [net/e]mail.