No, you still need an entire testonly-owner.config file. Using a
default config file that gets created by majordomo does not cause any
message or header content to change on it's way to a recipient list.
The only settings you would change are the admin password, which every
list owner should change as soon as their list is created, and the
restrict_post setting discussed in our previous exchange of messages.
Remember, the point was to prevent spammers from using the address of
the list owner, while still allowing list members to talk to the owner
as necessary. If the spammer joins your list, the whole game plan
changes. ;)
Dan Liston
David J. Chase wrote:
> In this scheme, could one have nothing _but_ restrict_post in
> testonly-owner.config? My concern is to not have any additional
> changes occur to messages after those intended (and imposed by
> testonly.config).
>
> Dan Liston wrote (Tue, 06 Dec 2005 12:19:18 -0600):
>
> The simple answer is to make your testonly-owner alias another list,
> which has it's own config file allowing only members of the testonly
> list to post messages to.
>
> testonly-owner: "|/usr/local/majordomo/wrapper resend -l testonly-owner
> testonly-owner-outgoing"
> testonly-owner-outgoing: :include:/usr/local/mail/lists/testonly-owner
>
> In your <path-to>/lists/testonly-owner file, have only the owner's email
> address like any other single user list.
>
> In your <path-to>/lists/testonly-owner.config file, use restrict_post;
>
> restrict_post = testonly testonly-post testonly-owner
>
> Now, anyone that already belongs to the testonly list can post to the
> owner, anyone that can post to the testonly list can post to the owner,
> and the owner is even allowed to post to theirself.
>
> ...cut...
>
> Thanks,
> David Chase
References:
|
|
