At 11:59 AM 9/14/98 -0700, you wrote:
>i use majordomo to run a private list. however, a nonmember continues to
>post to the list. they are not a subscriber, so they don't receive
>postings. [...]
Sounds like the configuration is such that subcriptions must be approved,
but posting is not restricted to the list?
See configuration file:
# restrict_post [restrict_post] (undef) <resend>
# If defined, only addresses listed in these files (colon or space
# separated) can post to the mailing list. By default, these files
# are relative to the lists directory. These files are also checked
# when get_access, index_access, info_access, intro_access,
# which_access, or who_access is set to '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 = mylist
^^^^^^
Put your list's name here, which will be the file listing the subscribers here.
Or,see:
# taboo_body [regexp_array] (undef) <resend>
# If any line of the body matches one of these regexps, then the
# message will be bounced for review.
taboo_body << END
END
and put a regular expression matching the spammers e-mail address in between
the ENDs, like /spammer@someplace.com/
Harrington
--------------------------------------------------------------------------
Harry Laufman Manager, Computer Operations
OSU College of Food, Agricultural and Environmental Sciences
E-Mail: laufman.1@osu.edu
101 Vivian Hall Voice: 614-292-6554
Columbus, Ohio 43210 FAX : 614-688-4009
--------------------------------------------------------------------------
References:
|
|
