Return-Path: Delivered-To: apmail-james-server-user-archive@www.apache.org Received: (qmail 84038 invoked from network); 3 Jun 2004 20:48:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 3 Jun 2004 20:48:01 -0000 Received: (qmail 68142 invoked by uid 500); 3 Jun 2004 20:48:17 -0000 Delivered-To: apmail-james-server-user-archive@james.apache.org Received: (qmail 68053 invoked by uid 500); 3 Jun 2004 20:48:16 -0000 Mailing-List: contact server-user-help@james.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "James Users List" Reply-To: "James Users List" Delivered-To: mailing list server-user@james.apache.org Received: (qmail 68035 invoked by uid 99); 3 Jun 2004 20:48:16 -0000 Received: from [69.44.58.116] (HELO jwmhosting) (69.44.58.116) by apache.org (qpsmtpd/0.27.1) with SMTP; Thu, 03 Jun 2004 13:48:16 -0700 Received: from pixpat.austin.ibm.com ([192.35.232.241]) by jwmhosting (JAMES SMTP Server 2.2.0a17) with SMTP ID 760 for ; Thu, 3 Jun 2004 15:47:41 -0500 (CDT) From: "J Malcolm" To: "James Users List" Subject: Restricting List Server Sending Date: Thu, 3 Jun 2004 15:47:50 -0500 Message-ID: <001701c449ac$09490740$9f372909@jmalcolmt40> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-MessageIsInfected: false X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I am setting up the Avalon-based list server. I see one of the options is to restrict that only members of the list can send to the list. That's fine. But I need even more restriction. I want only one or two email addresses to be able to send to the list. (Basically it's a one-way notification list). I believe I can set it up in the matcher/mailet chain where notes from non-authorized addresses will get canned. But is that the best way (i.e. using an IsSender matcher). Or is there a way inside the list processor to restrict senders more than just the list-member option? Surely, I'm not the first person that's had this requirement. I just don't want to re-invent the wheel. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org For additional commands, e-mail: server-user-help@james.apache.org