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.
Protect your testonly-owner address one step further by disallowing the
address to be referenced via an SMTP connection to your server. If you
are using a recent sendmail, add this to your /etc/mail/virtusertable;
testonly-owner-outgoing@testdomain.com error:nouser User unknown
Dan Liston
Allan P. Magmanlac wrote:
> hello,
> I have a closed list but somehow the spammers are using the owner of
> the list address which gets to the list owner. Sample setup of a list.
> So in this setup, the spammer insstead of using testonly@testdomain.com
> he's using testonly-owner@testdomain.com. How can I configure majordomo,
> so that he cannot send message to the owner directly.
>
>
>
> testonly: "|/usr/local/majordomo/wrapper resend -a
> /usr/local/mail/lists/testonly.pa
> sswd -l testonly -h my.testdomain.com -r testonly -f testonly-owner
> testonly-outgoing"
> owner-testonly: testonly-owner
> testonly-request: "|/usr/local/majordomo/wrapper request-answer testonly"
> testonly-outgoing: :include:/usr/local/mail/lists/testonly
> owner-testonly-request: testonly-owner
> testonly-owner: testowner@testdomain.com
> testonly-approval: testowner@testdomain.com
>
> Thanks.
>
>
References:
|
|
