On Sun, 28 Apr 1996, Jack Schnapper wrote:
> Date: Sun, 28 Apr 1996 00:31:11 -0400
> From: Jack Schnapper <jjflash@pobox.com>
> To: majordomo-users@GreatCircle.COM
> Subject: Commercial Posts - What To Do?
>
> I run 2 small lists (both under majordomo). Recently my lists have been
> getting advertisements (usually fairly large messages - @13k) from
> non-members soliciting magazine subscriptions. These always (I am pretty
> sure) come from AOL addresses that are deleted after the messages are sent.
>
> My host site is POBOX and I don't have access to the server. Therefore, I
> don't believe that I can make the lists closed to postings by non-members.
>
> Does anyone have any ideas for me? My listmembers are getting irritated.
can't you use ... (cut from a MD 1.93 listname.config file)
# restrict_post [restrict_post] (undef) <resend>
# If defined only address listed in one of the files (colon or space
# separated) can post to the mailing list. This is less useful than it
# seems it should be since there is no way to create these files if
# you do not have access to the machine running resend. This mechanism
# will be replaced in a future version of majordomo/resend.
restrict_post = /hda6/lists/sanctuary:/hda6/lists/sanctuary-digest
and just point it at MD maintained lists of addresses that CAN do postings
either the listname or some other MD maintained list of addresses.
we allow members of both the digest and non-digest lists to post to the
non digest list, for example.
that way you can maintain the posting list remotely, and still block
via "non-member posting bounce" the spam.
you can update the list.config file with:
<cut from the list-owner-info sample file>
config <list> <password>
retrieve a self-documenting configuration file for
the list <list>. The <password> can be the password
contained in the file <listname>.passwd or the
admin_password in the configuration file.
newconfig <list> <password>
Validates and installs a new configuration file. It reads
everything after the "newconfig" command to end-of-message or
the word "EOF" on a line by itself as the new info for the
list. The config file is expected to be a complete config
file as returned by "config". Incremental changing of the
config file is not yet supported. As soon as the config file
is validated and installed its settings are available for
use. This is useful to remember if you have multiple commands
in your mail message since they will be subject to the
settings of the new config file. If there is an error in the
config file (incorrect value...), the config file will not be
accepted and the error message identifying the problem line(s)
will be returned to the sender. Note that only the error
messages are returned to the sender not the entire config
file, so it would be a good idea to keep a copy of your
outgoing email message.
writeconfig <list> <password>
Write a new config file in standard form. Writeconfig forces a
rewrite of the config file with all comments and default
values in place. It is useful to use after an upgrade of
majordomo since it will add the new keywords for people to
change. It also updates the documentation in the file if that
has changed.
Fuzzy
Sys Admin, ASARian.org
References:
|
|
