19-Mar-1996 15:34:44 -0800,2972;000000000001 Return-Path: Received: via tmail-4.0(2) for deroest; Tue, 19 Mar 1996 15:34:44 -0800 (PST) Return-Path: Received: from mailer3.u.washington.edu by franklin01.u.washington.edu (5.65+UW96.02/UW-NDC Revision: 2.33 ) id AA16340; Tue, 19 Mar 96 15:34:43 -0800 Received: from mx2.cac.washington.edu by mailer3.u.washington.edu (5.65+UW96.02/UW-NDC Revision: 2.33 ) id AA54176; Tue, 19 Mar 96 15:34:41 -0800 Received: from homer22.u.washington.edu by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA18556; Tue, 19 Mar 96 15:34:39 -0800 Received: by homer22.u.washington.edu (5.65+UW96.02/UW-NDC Revision: 2.33 ) id AA34180; Tue, 19 Mar 96 15:34:37 -0800 X-Sender: remmers@homer22.u.washington.edu Date: Tue, 19 Mar 1996 15:34:37 -0800 (PST) From: Tom Remmers To: Oren Sreebny Cc: Jim DeRoest , bshirey@cac.washington.edu, davidw@cac.washington.edu, Ed Lightfoot , "W. Washburn" , garrick@u.washington.edu, Sandy Moy , Ron Johnson Subject: Re: ASUW All Student Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 19 Mar 1996, Oren Sreebny wrote: > > - I believe we now have some new requirements as a result of our > discussions: > - The Registrar's Office has indicated a need for a list to contact > *all* students - we believe that this is a separate list from the > ASUW list. An all student list could reach the students who have Uniform Access accounts, as of March 18, 30,371 students of a total 37,652, or 81%. > - We must keep the names of the subscribers on the list private, > even from the ASUW people who will be administering the list. Tom, > is this possible? Yes, if a trusted person is the list owner, the list can be configured to implement the procedures Garrick develops for posting and to meet subscriber privacy requirements. > - Questions > - (for Tom) - How do we get the original subscription mechanism to know > to not subscribe students who've opted out of ASUW membership? The student subscriber list is currently built from student directory data and student Uniform Access verification data on Austen. The ASUW membership status is not on Austen and would have to come from another source (Bill Shirey?). > - (for Tom) - Will people unsubscribe with a normal "unsubscribe" > request to listproc? Yes. -- Tom Remmers remmers@u.washington.edu University Computing Services (206) 543-4756 University of Washington 8-Apr-1996 14:00:52 -0700,3187;000000000001 Return-Path: Received: via tmail-4.0(2) for deroest; Mon, 8 Apr 1996 14:00:51 -0700 (PDT) Return-Path: Received: from mx4.u.washington.edu by franklin01.u.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA13348; Mon, 8 Apr 96 14:00:47 -0700 Received: from red6.cac.washington.edu by mx4.u.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA25505; Mon, 8 Apr 96 14:00:39 -0700 Received: from localhost by red6.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA15498; Mon, 8 Apr 96 14:00:37 -0700 Date: Mon, 8 Apr 1996 14:00:36 -0700 (PDT) From: David Wall X-Sender: davidw@red6.cac.washington.edu Reply-To: David Wall To: Tom Remmers Cc: Yonah Karp , Sandra Moy , James W DeRoest , Oren Sreebny , Ken Lowe Subject: Re: listdist --> listproc In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 8 Apr 1996, Tom Remmers wrote: :) > Dave thinks that it doesn't make much sense to automate the :) > process -- too many variables. :) :) If the listdist owners fill out the standard listproc registration form, :) we can combine that with the information in the listdist.cf file to create :) a listproc list. We would have to send the owner documentation, but I :) don't see any variables. C&CI or I would have to run the conversion :) process, so it wouldn't be totally automated like 'moveme', We are close to the same thing here. I was saying that it didn't seem to me to be worth it to try to write a script to read the listdist.cf file and automatically convert that to a ListProc configuration. There may be few things that will be a challenge to convert anyway. The 'variables' I was thinking of are things like listdists "P" addresses, cases where the owner is a supplemental or other multiple named account, the "A" addresses and some of the header settings that might not translate directly. but the owners :) wouldn't have to copy their subscribers and configure their own list :) by looking through the documentation. Agreed. We should help with these things. I think that in terms of support I'd like to do everything I could to 'encourage' owners to get familiar with the documentation. And I don't think it would be a bad idea to recommend to owners that they have all their subscribers go through a subscription process. (at least for the lists where owners will want subscribers to take care of themselves.) That would start them on the road to self-sufficiency. I think that the more we do for people, the less outcry we'll have about having to convert. But the more we do for them now, the more we'll have to do for them in ongoing support, so I'd like to see some balance if possible. -- Dave 10-May-1996 16:21:53 -0700,1822;000000000001 Return-Path: Received: via tmail-4.0(2) for deroest; Fri, 10 May 1996 16:21:52 -0700 (PDT) Return-Path: Received: from homer06.u.washington.edu by franklin01.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA16698; Fri, 10 May 96 16:21:52 -0700 Received: from localhost by homer06.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA41895; Fri, 10 May 96 16:21:48 -0700 Date: Fri, 10 May 1996 16:21:48 -0700 (PDT) From: Tom Remmers Reply-To: Tom Remmers To: Student Mailing List , David Wall , "James W. DeRoest" , Elizabeth Campbell , Garrick Hileman , joanrw@u.washington.edu, Oren Sreebny , Sandra Moy , "W. Washburn" Subject: Test asuw-l list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII An asuw-l test list has been configured and is almost ready for testing. I need the name of the asuw account that will be sending in the mail for moderation and the name of the Student Records owner account. There also need to be some volunteers to be test student subscribers, especially those who will be involved with moderating the list. Once I have these addresses, it will be possible to do a few dry runs to iron out the details. Thanks, -- Tom Remmers remmers@u.washington.edu University Computing Services (206) 543-4756 University of Washington 15-May-1996 10:27:22 -0700,4869;000000000001 Return-Path: Received: via tmail-4.0(2) for deroest; Wed, 15 May 1996 10:27:21 -0700 (PDT) Return-Path: Received: from homer03.u.washington.edu by franklin01.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA22868; Wed, 15 May 96 10:27:21 -0700 Received: from localhost by homer03.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA140328; Wed, 15 May 96 10:27:15 -0700 Date: Wed, 15 May 1996 10:27:15 -0700 (PDT) From: Tom Remmers Reply-To: Tom Remmers To: "W. Washburn" , vjohnson@u.washington.edu, Garrick Hileman , Brian Bridges Cc: Oren Sreebny , "James W. DeRoest" , David Wall Subject: Re: Test asuw-l list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The asuw-l list is ready for testing. The procedure for sending a message is, - A message to the list is sent from the asuw@u.washington.edu account to asuw-l@u.washington.edu - Listproc will receive the message and notify vjohnson@u.washington.edu. The notification will look similar to, Date: Wed, 8 May 1996 16:02:20 PDT From: University of Washington ListProcessor To: vjohnson@u.washington.edu Subject: List ASUW-L msg #18: approval request Parts/attachments: 1 Shown 9 lines Text 2 Shown 768 bytes Message, "Some Subject" 2.1 Shown 7 lines Text ---------------------------------------- Approval request from listproc@u.washington.edu for posting the following message to moderated list ASUW-L. If approved, send the following request to listproc@u.washington.edu: APPROVE ASUW-L 18 If the message is to be discarded, reply with the following request: DISCARD ASUW-L 18 [ Part 2: "Included Message" ] Date: Wed, 8 May 1996 16:02:01 -0700 (PDT) From: Tom Remmers To: ASUW Mailing List Subject: Some Subject Body of message. ... - Van Johnson will follow the directions above, in this case, he will send, or reply, to listproc@u.washington.edu with just the text, approve ASUW-L asuw-l 18 Here "asuw-l" is the asuw-l listproc password. We have not had security problems with list passwords, but if you want to change it, let me know via phone. - The message will then be sent to the list, which has these subscribers, remmers@u.washington.edu bbridges@u.washington.edu garrick@u.washington.edu timwash@u.washington.edu davidw@u.washington.edu - When these subscribers receive a message, the reply should go directly to asuw-l if the respond "No" to Pine's question, "Reply to all recipients?". If these accounts respond "Yes", mail will be sent to the list also, however the Listproc server should transparently ignore the message. This part should be tested to make sure vjohnson@u does not receive replies to the list, which could become quite numerous. Note: As the list owner, vjohnson@u.washington.edu can post directly to the list, bypassing moderation. This feature may be useful if a message is sent back and forth for editing. If there are any problems are questions, please contact me right away. -- Tom Remmers remmers@u.washington.edu University Computing Services (206) 543-4756 University of Washington On Mon, 13 May 1996, W. Washburn wrote: > Tom: Van Johnson, Associate Registrar will be the owner of the list. His > address is vjohnson@u. > > Tim Washburn, Executive Director > Admissions and Records > University of Washington PC 30 > Seattle WA 98195 > 206 543-3511 FAX 685-3655 > timwash@u.washington.edu > > On Fri, 10 May 1996, Tom Remmers wrote: > > > An asuw-l test list has been configured and is almost ready for testing. > > I need the name of the asuw account that will be sending in the mail for > > moderation and the name of the Student Records owner account. There also > > need to be some volunteers to be test student subscribers, especially > > those who will be involved with moderating the list. > > > > Once I have these addresses, it will be possible to do a few dry runs to > > iron out the details. > > > > Thanks, > > > > -- Tom Remmers remmers@u.washington.edu > > University Computing Services (206) 543-4756 > > University of Washington > > > > > > > > 16-May-1996 14:54:59 -0700,1106;000000000011 Return-Path: Received: via tmail-4.0(2) for deroest; Thu, 16 May 1996 14:54:59 -0700 (PDT) Return-Path: Received: from homer22.u.washington.edu by franklin01.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA09984; Thu, 16 May 96 14:54:59 -0700 Received: from localhost by homer22.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA45240; Thu, 16 May 96 14:54:58 -0700 Date: Thu, 16 May 1996 14:54:58 -0700 (PDT) From: Tom Remmers To: "James W. DeRoest" Subject: Listproc multi-threading bug Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Jim, With KenM's help, I've tracked down the Listproc bug that limited the total number of threads in the Listproc server. There was an amusing, but deadly, error with a select() call. I upped the threads from 3 to 10, and it's very fast. I'm anxious to see how ASUW-L does with 10 of its own threads! Tom 17-May-1996 09:58:12 -0700,2299;000000000001 Return-Path: Received: via tmail-4.0(2) for deroest; Fri, 17 May 1996 09:58:12 -0700 (PDT) Return-Path: Received: from mailer14.u.washington.edu by franklin01.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA16842; Fri, 17 May 96 09:58:11 -0700 Received: from mx2.cac.washington.edu by mailer14.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA72591; Fri, 17 May 96 09:58:10 -0700 Received: from homer08.u.washington.edu by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA01745; Fri, 17 May 96 09:58:09 -0700 Received: from localhost by homer08.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA138440; Fri, 17 May 96 09:58:09 -0700 Date: Fri, 17 May 1996 09:58:08 -0700 (PDT) From: Tom Remmers To: James W DeRoest Subject: Re: Listproc multi-threading bug In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Susan Archdeacon just set up a procedure to send the needed information to Austen, and I have written a program to create a subscribers file. I've hacked Listproc to record asuw-l subscribe and unsubscribe requests, but I haven't written any automatic processing of these records. I informed the principles to start testing the list, but I don't think they have yet. Since Pine will always try to reply to the To: field, I hacked Listproc to either not include it in outgoing messages or to either set it to asuw@u, depending on what the principles decide. Unfortunately I can't put something like this in the .ignored file ~asuw@u.washington.edu&&~vjohnson@u.washington.edu because this will also cause Listproc to ignore unsubscribe requests, thus the necessity to hack the To: field. CREN should give us a couple free years of Listproc for finding this bug! Tom PS. I've got quite a scratchy throat today, and I'm run down. Since it's been with me three days now, I'm going to take at least 4 hours sick leave today as prevention. > > Great! How's the list testing coming? > > Jim > 15-May-1996 15:44:21 -0700,2027;000000000001 Return-Path: Received: via tmail-4.0(2) for deroest; Wed, 15 May 1996 15:44:21 -0700 (PDT) Return-Path: Received: from homer03.u.washington.edu by franklin01.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA20964; Wed, 15 May 96 15:44:21 -0700 Received: from localhost by homer03.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA58624; Wed, 15 May 96 15:44:16 -0700 Date: Wed, 15 May 1996 15:44:16 -0700 (PDT) From: Tom Remmers To: "W. Washburn" , vjohnson@u.washington.edu, Garrick Hileman , Brian Bridges Cc: Oren Sreebny , "James W. DeRoest" , David Wall Subject: slight change Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII My original scheme to prevent replies to the list owner, vjohnson@u, had a small flaw in that user's unsubscribe requests would be ignored. Since Pine will attempt to reply to the "To:" header field, which is the list name asuw-l@u, I hacked the code to not include the "To:" header in outgoing messages, thus subscribers would see something like, Date: Wed, 15 May 1996 14:43:09 -0700 (PDT) From: ASUW account Subject: subject Text ... Although it is not necessary to have a "To:" address, it may be less confusing if we make one up for outgoing messages, eg., Date: Wed, 15 May 1996 14:43:09 -0700 (PDT) From: ASUW account To: ASUW Mailing List Subject: subject Text ... See how it looks when you test it out. Thanks, -- Tom Remmers remmers@u.washington.edu University Computing Services (206) 543-4756 University of Washington