Date: Thu, 1 Oct 1998 17:58:28 +0200 From: Detlef Beyer <d.beyer at crash dot de> Subject: Process Extender problem P.S. I forgot to mention: two other process extenders "Before Processing" and "After Processing" are beeing called by all lists - only "Subscribe" and "Unsubscribe" are beeing ignored by one list (the list itself is running fine). Det
Date: 01 Oct 98 11:49:53 -0500 From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us> Subject: Enclosures & Autoshare I knew the answer to this but have forgotten it. Must be oldtimer's = disease..... How can I allow members of a list to send enclosures to the list? I'm = running ver 2.4 Yeah I know that is not a very good idea, but we do have a circumstance in = which it is appropriate. And, I thought I had things all set up, but = either I didn't or an upgrade to Autoshare has changed the rules. I tried = sending a Binhex enclosure and it cam over still binhexed and attached as = part of the message.
Date: Thu, 01 Oct 1998 12:37:47 -0700 From: Camelot Administrator <camelot.admin at lmco dot com> Subject: Re: AutoShare 3.0b9 (US Web Mirror) At 11:45 PM -0700 on 9/30/98, Mikael Hansen wrote: > The 3.0b9 archive has been uploaded to > > <ftp://ftp.dnai.com/users/m/meh/AutoShare/Beta/> > > New in b9 > -compiled using CW4 > -IC 2.0 error at start-up fixed > -updated sample language files > -refined dir response with remote system command > -case-sensitivity in contributions for To and Reply-To > -roll-over based on messages, file sizes or time > > I haven't had time to test or document the last one (plus no time the next > few days), but the values (in the Messages field in the Admin's List > window) are now divided into 4 parts: 0: no roll-over as usual, 1-1000: > number of messages as usual, > 1000: file size of archive pair in bytes, < > 0: number of hours between roll-overs (Honza, please send me feedback). > Also available at http://pascal-central.com/autoshare/beta/AutoShare3.0b9.sit +----------------------------------------------------------------+ | Camelot Postmaster, mailto:camelot.admin at lmco dot com | | Lockheed Martin, Enterprise Information Systems, Sunnyvale, CA | +----------------------------------------------------------------+
Date: Thu, 01 Oct 1998 21:50:18 -0700 From: Mathew Hill <happytwo at milepost1 dot com> Subject: Re: AutoShare-Talk digest 30 Sep 1998 > This is going to seem like a silly newbie question. But I can not seem to make > it work. How do you set up a moderated list?? Thanks Matthew
Date: Thu, 1 Oct 1998 23:59:26 +0200 From: Jan Koudelka <koudelka at appleklub dot cz> Subject: Re: AutoShare 3.0b9 >I haven't had time to test or document the last one (plus no time the next >few days), but the values (in the Messages field in the Admin's List >window) are now divided into 4 parts: 0: no roll-over as usual, 1-1000: >number of messages as usual, > 1000: file size of archive pair in bytes, < >0: number of hours between roll-overs (Honza, please send me feedback). Sorry, no time until next week. However, here is my opinion about your implementation. It's hard to imagine a mailing list, whose archive needs roll-over every X hours. It would be usually days. But, most probably, monthly based roll-over will be used. And here is the problem: months differ in length (28, 30, 31). I think that nobody will need a precise setup in hours or days, so the following setup can be better: 0 no roll-over 1-1000 number of messages > 1000 file size -1 to -24 hours -24 one day -30 one week -40 one month -50 three months -60 six months -70 one year All times counting January 1, 0:00 as zero. HOnza
Date: Fri, 2 Oct 1998 10:37:34 -0500 From: Andrew Wimmer <wimmer at sofie dot org> Subject: Re: Multiple Domains and SIMS Mikael wrote: >>From the documentation: "It is however possible to arrange for >multi-preference sets within a single-domain environment as long as you >avoid conflicting user names for the special accounts", which doesn't apply >to your environment as you have multiple domains set up in SIMS. Yes, I was making it more complicated than I needed to. I realized that all I needed to do was make a router entry for each domain, e.g. <autoshare at domain1 dot org> = domain1lists where domain1lists is set to save to folder read by AutoShare. Thanks for your help. Andrew Wimmer
Date: Fri, 2 Oct 1998 12:45:33 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: AutoShare-Talk digest 30 Sep 1998 >This is going to seem like a silly newbie question. But I can not seem >to make it work. How do you set up a moderated list?? If it already works as a regular subscription list, then simply click on the Moderated radio button in the Admin's List window.
Date: Fri, 2 Oct 1998 12:51:02 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: Enclosures & Autoshare At 11:49 -0500 10/1/98, Chuck Boody wrote: >How can I allow members of a list to send enclosures to the list? I'm >running ver 2.4 You don't have to do anything. >I tried sending a Binhex enclosure and it cam over still binhexed and >attached as part of the message. It would depend on the specifics why this would happen. It shouldn't.
Date: 02 Oct 98 15:36:49 -0500 From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us> Subject: Re: Enclosures & Autoshare Ah, but it does happen Mikael. = Tell me what setup Autoshare wants to see in re the enclosure and message. = = We use QuickMail Pro or Eudora Light, and either can be set to BinHex the = enclosure and then to a series of choice of message type (Text, MIME-Plain = Text, MIME-Stylized Text on QM Pro where I believe Stylized implies HTML = encoding). If I set to BinHex and Text I get the message attached as = described below. If I set to BinHex and either MIME choice I get the = message but the attachment is entirely missing. AutoShare is set to "QP = always" if that has anything to do with it. The message is flowing through two EIMS 2.2 servers and no other places. = I suppose EIMS could be causing the problem, but somehow that seems = unlikely. Any help you (or others out here) can give would be appreciated. Thanks, Chuck ============= Mikael Hansen wrote: >At 11:49 -0500 10/1/98, Chuck Boody wrote: > >>How can I allow members of a list to send enclosures to the list? I'm >>running ver 2.4 > >You don't have to do anything. > >>I tried sending a Binhex enclosure and it cam over still binhexed and >>attached as part of the message. > >It would depend on the specifics why this would happen. It shouldn't. > >** The AutoShare-Talk archives are at: >** <http://frutiger.staffs.ac.uk/autoshare/archives/> > >RFC822 header >----------------------------------- > >Return-Path: <bounce at frutiger.staffs.ac dot uk> >Received: from frutiger.staffs.ac.uk (194.66.172.10) by hopkins.k12.mn.us = with > ESMTP (Eudora Internet Mail Server 2.2); Fri, 2 Oct 1998 15:23:14 -0500 >Received: from mercury.dnai.com (207.181.194.99) by frutiger.staffs.ac.uk = with > ESMTP (Eudora Internet Mail Server 2.2); Fri, 2 Oct 1998 21:14:07 +0100 >Received: from [207.181.206.36] (dnai-207-181-206-47.dialup.dnai.com = >[207.181.206.47]) > by mercury.dnai.com (8.8.7/8.8.7) with ESMTP id MAA03743 > for <autoshare-talk at frutiger.staffs.ac dot uk>; Fri, 2 Oct 1998 12:51:52 -= 0700 = >(PDT) >Mime-Version: 1.0 >Content-Type: text/plain; charset="us-ascii" > ; format="flowed" >X-Sender: meh at pop.dnai dot com >In-Reply-To: <878650266689112047548 at frutiger.staffs.ac dot uk> >Date: Fri, 2 Oct 1998 12:51:02 -0700 >Reply-To: autoshare-talk at frutiger.staffs.ac dot uk (Subscribers of AutoShare-= Talk) >Errors-To: bounce at frutiger.staffs.ac dot uk (AutoShare bounce account) >Precedence: bulk >List-Subscribe: = ><mailto:autoshare at frutiger.staffs.ac dot uk?body=subscribe%20autoshare-talk>= >List-Unsubscribe: = ><mailto:autoshare at frutiger.staffs.ac dot uk?body=unsubscribe%20autoshare-= talk> >X-List-Digest: = ><mailto:autoshare at frutiger.staffs.ac dot uk?body=set%20autoshare-talk%= 20digest> >List-Archive: = ><mailto:autoshare at frutiger.staffs.ac dot uk?body=index%20autoshare-talk> >List-Post: <mailto:autoshare-talk at frutiger.staffs.ac dot uk> >List-Owner: listmaster at frutiger.staffs.ac dot uk (James Berriman) >List-Help: <http://www.dnai.com/~meh/autoshare/> >List-Software: AutoShare 3.0b9 by Mikael Hansen >X-To-Unsubscribe: autoshare at frutiger.staffs.ac dot uk, body: unsub autoshare-= talk >To: autoshare-talk at frutiger.staffs.ac dot uk (Subscribers of AutoShare-Talk) >From: Mikael Hansen <meh at dnai dot com> >Subject: Re: Enclosures & Autoshare >Message-Id: <340059426398230138068 at frutiger.staffs.ac dot uk> >
Date: Fri, 2 Oct 1998 15:05:02 -0500 From: Andrew Wimmer <wimmer at sofie dot org> Subject: Creating lists in SIMS As I continue my EIMS to SIMS conversion, I'm discovering some nice surprises. Unlike EIMS which stores account info in the prefs file, all the information about an individual SIMS account is stored in the resource fork of that account's text file in the Accounts folder. Accounts can, therefore, be duplicated and deleted in the Finder. For quick AutoShare list setup, I created a generic list.m account and a list.d account. To create new mailing list acounts I simply make Finder copies of these two files and rename them newlist.m and newlist.d. Then copy in the aliases of the AutoShare lists. The whole process can be scripted. No need to use Communigate or Web interface. Maybe this is old news, but I was certainly happy to discover it. Yours, Andrew
Date: Sat, 03 Oct 1998 13:24:10 -0700 From: Mathew Hill <happytwo at milepost1 dot com> Subject: Re: AutoShare-Talk digest 3 Oct 1998 The message I get back is that your message has not been posted or forwarded. I can not figure out which setting I have set wrong. > > > >This is going to seem like a silly newbie question. But I can not seem > >to make it work. How do you set up a moderated list?? > > If it already works as a regular subscription list, then simply click on > the Moderated radio button in the Admin's List window. > >
Date: Sun, 4 Oct 1998 17:21:44 +0200 From: Detlef Beyer <d.beyer at crash dot de> Subject: Re: Process Extender problem P.S. >I forgot to mention: > >two other process extenders "Before Processing" and "After Processing" are beeing called by all lists - only "Subscribe" and "Unsubscribe" are beeing ignored by one list (the list itself is running fine). > Hello, I found the solution myself ;) The reason for my problem: I removed the /=sub tag from the reply document because I donb't want the list options to be shown here - I had no idea that those tags start the external events... Best, Det **** please note my new mail adress: **** **** d.beyer at crash dot de ****
Date: Sun, 4 Oct 1998 22:02:42 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: Subject token in monthly help file? At 08:02 -0500 10/1/98, Jon & Janelle Gardner wrote: >At the top of a monthly help file (AS 2.4), I have the /=subject token; >however, when the help file is sent out, the token doesn't get parsed >and shows up "as-is" on the first line of the email. Is this proper >behaviour? The monthly help file doesn't fit into the scheme of token support. I can do it, so the subject may be changed using a language file entry. (Detlef and others, it'll be 1091,2)
Date: Sun, 4 Oct 1998 22:04:53 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: AutoShare 3.0b9 At 23:59 +0200 10/1/98, Jan Koudelka wrote: >I think that nobody will need a precise setup in hours or days, so the >following setup can be better: I dunno. When fixing what was broken, I changed it to hours. I need some time to give this some thought. Noted for 3.1.
Date: Sun, 4 Oct 1998 22:06:56 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: AutoShare 3.0b9 I wrote: >When fixing what was broken, I changed it to hours. I meant to say from hours to days.
Date: Sun, 4 Oct 1998 22:08:02 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: Enclosures & Autoshare At 15:36 -0500 10/2/98, Chuck Boody wrote: >We use QuickMail Pro or Eudora Light, and either can be set to BinHex >the enclosure and then to a series of choice of message type (Text, >MIME-Plain Text, MIME-Stylized Text on QM Pro where I believe Stylized >implies HTML encoding). If I set to BinHex and Text I get the message >attached as described below. If you could send me a file from the Filed Mail folder (StuffIt'ed please), I'll look into it. Thanks.
Date: Sun, 4 Oct 1998 22:10:35 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: AutoShare-Talk digest 3 Oct 1998 At 13:24 -0700 10/3/98, Mathew Hill wrote: >The message I get back is that your message has not been posted or >forwarded. The following line should detail the situation. Several possibilities.
Date: Mon, 5 Oct 1998 01:13:21 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: AutoShare 3.0fc1 The 3.0fc1 archive has been uploaded to <ftp://ftp.dnai.com/users/m/meh/AutoShare/Beta/> Various minor stuff only has been attended to in fc1, which has been named so as it's time for me to clear my head. 3.0 will be released in a couple of days (unless something important is terribly wrong), so if you have some last minute stuff to be included, now is the time. Thanks.
Date: 05 Oct 98 08:26:05 -0500 From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us> Subject: RE: AutoShare 3.0fc1 Autoshare beta 3.0fc1 is now available by mail. Send a message to = mailit at stumail.hopkins.k12.mn dot us with the word autosharebeta in the subject. The latest beta will be returned to you by e-mail. Contact me directly if you have any trouble with this service. Chuck Boody analyst/programmer ISD 270 chuck_boody at hopkins.k12.mn dot us =============
Date: Mon, 05 Oct 1998 07:03:40 -0700 From: Camelot Administrator <camelot.admin at lmco dot com> Subject: Re: AutoShare 3.0fc1 At 1:13 AM -0700 on 10/5/98, Mikael Hansen wrote: > The 3.0fc1 archive has been uploaded to > > <ftp://ftp.dnai.com/users/m/meh/AutoShare/Beta/> > > Various minor stuff only has been attended to in fc1, which has been named > so as it's time for me to clear my head. 3.0 will be released in a couple > of days (unless something important is terribly wrong), so if you have some > last minute stuff to be included, now is the time. Thanks. > ...and available from http://pascal-central.com/autoshare/beta/. Cheers, Bill +----------------------------------------------------------------+ | Camelot Postmaster, mailto:camelot.admin at lmco dot com | | Lockheed Martin, Enterprise Information Systems, Sunnyvale, CA | +----------------------------------------------------------------+
Date: Tue, 06 Oct 1998 01:02:44 +0100 Subject: Re: AutoShare 3.0fc1 From: "James Berriman" <J.R.Berriman at staffs.ac dot uk> fc1 seems to be doing strange things on my LCII. It keeps sucking up cpu cycles for no apparent reason (menubar clock freezes for several seconds at a time). This is not due to normal file processing - there are no messages waiting to be processed. I've gone back to 3.0b9 for the moment. Anyone else having problems on 68k machines? ( :-]) James
Date: Tue, 6 Oct 1998 06:59:17 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: AutoShare 3.0fc1 At 01:02 +0100 10/6/98, James Berriman wrote: >fc1 seems to be doing strange things on my LCII. It keeps sucking up cpu >cycles for no apparent reason (menubar clock freezes for several seconds >at a time). This is not due to normal file processing I have sent James a version that is fine in this respect.
Date: Tue, 6 Oct 1998 17:16:46 +0100 From: James Berriman <J.R.Berriman at staffs.ac dot uk> Subject: Re: AutoShare 3.0fc1 At 14:59 6/10/98, Mikael Hansen wrote: >I have sent James a version that is fine in this respect. Now up and running OK :-) ( :-]) James
From: Laine Lee <LLee at utsa dot edu> Subject: Current digest not returned with subscription Date: Tue, 6 Oct 1998 12:43:46 -0500 Hello, I recently noticed that a current digest is no longer being sent to new subscribers when a subscription request is received. All other subscription actions seem normal. I discovered that when I request a subscription using the File Mail command from AutoshareAdmin.acgi, the current digest is sent to the new subscriber. I'm using a version 3 beta of autoshare, but the same was true of version 2.4. Please offer suggestions. Thanks.
Date: Tue, 6 Oct 1998 12:30:55 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: Current digest not returned with subscription At 12:43 -0500 10/6/98, Laine Lee wrote: > I recently noticed that a current digest is no longer >being sent to new subscribers when a subscription request is received. I just tried it, and it worked fine. A partial digest will however not be sent at subscription time if the digest file doesn't contain at least one list contribution or if the letter e is specified in the Admin's List Stuff field to suppress partial digests.
Date: Tue, 6 Oct 1998 21:43:08 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Version 3.0 released It's up there, folks. <ftp://ftp.dnai.com/users/m/meh/AutoShare/> <http://www.dnai.com/~meh/autoshare/>
From: "Suarez, William" <WSuarez at wal.osicom dot com> Subject: RE: Version 3.0 released Date: Wed, 7 Oct 1998 08:12:17 -0400 ............and the crowd goes wild, cheering, etc. This work, as always, Mikael. Thanks again for all your hard work on Autoshare! Regards, Bill Suarez -----Original Message----- From: Mikael Hansen [mailto:meh at dnai dot com] Sent: Wednesday, October 07, 1998 12:43 AM To: autoshare-talk at frutiger.staffs.ac dot uk Subject: Version 3.0 released It's up there, folks. <ftp://ftp.dnai.com/users/m/meh/AutoShare/> <http://www.dnai.com/~meh/autoshare/> ** The AutoShare-Talk archives are at: ** <http://frutiger.staffs.ac.uk/autoshare/archives/>
Date: 07 Oct 98 10:47:59 -0500 From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us> Subject: RE: AutoShare 3.0 Release version available by mail. Autoshare 3.0 is available by mail. Send a message to = mailit at stumail.hopkins.k12.mn dot us with the word autoshare3 in the subject. Version 3 will be returned to you by e-mail. To get the Complete Administrator package for Autoshare 3.0 send a message = to the above address with AutoshareAdmin3 in the subject. As usual the current beta is available by placing = AutoSharebeta in the subject of a message to the above address. However, currently the = release version (3.0) is newer than the latest beta (3.0fc1). Contact me directly if you have any trouble with this service. Chuck Boody analyst/programmer ISD 270 chuck_boody at hopkins.k12.mn dot us =============
Date: Wed, 07 Oct 1998 22:55:31 +0100 Subject: Re: Version 3.0 released From: "James Berriman" <J.R.Berriman at staffs.ac dot uk> Now available at: <mailto:AutoShare-software at dcl.co.uk?subject=AutoShare-3.0 dot sit> and <http://www.dcl.co.uk/MacOS/email/autoshare/AutoShare-3.0.sit.bin> ( :-]) James
Date: Thu, 8 Oct 1998 12:27:50 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: AutoShare 3.0.1b1 The 3.0.1b1 archive (server applications only) has been uploaded to <ftp://ftp.dnai.com/users/m/meh/AutoShare/Beta/> I upgraded from CWPro3 to CWPro4 a week ago, and a CWPro bug surfaced this morning, as I was doing some testing. While it appears to affect only the built-in database subscriber format which has now been fixed, I'll wait a few days to make sure before releasing 3.0.1. If you had trouble downloading, try the mirror sites: <http://www.dcl.co.uk/MacOS/email/autoshare/> <mailto:AutoShare-software at dcl.co dot uk> <ftp://ftp.cbc.bryan.tx.us/as/> <http://pascal-central.com/autoshare/beta/> <mailto:mailit at stumail.hopkins.k12.mn dot us> The web pages will be updated soonish.
Date: Thu, 08 Oct 1998 12:41:43 -0700 From: Camelot Administrator <camelot.admin at lmco dot com> Subject: Re: Version 3.0 released Now available at the Pascal Central mirror... Autoshare 3.0 Binary (1.4M) - http://pascal-central.com/autoshare/autoshare3.0.bin Autoshare 3.0 Binhex (1.9M) - http://pascal-central.com/autoshare/autoshare3.0.bin.hqx Autoshare Complete Admin Binary (494k) - http://pascal-central.com/autoshare/complete.admin3.0.bin Cheers, Bill +----------------------------------------------------------------+ | Camelot Postmaster, mailto:camelot.admin at lmco dot com | | Lockheed Martin, Enterprise Information Systems, Sunnyvale, CA | +----------------------------------------------------------------+
Date: Thu, 8 Oct 1998 13:42:31 -0700 From: Michael Swan <swan at neon dot com> Subject: AutoShare 3.0 compatibility? Hello, We've been using, believe it or not, AutoShare 1.0 for quite some time. We would very much like to update to the new v3.0 but have a quick question. Aside from the warnings given in the "upgrade" html document, will the new version use the 1.0 mailing list database (i.e. the list of subscribers for each mailing list) without modification? Thanks for your time, Michael Swan Neon Software, Inc.
Date: Thu, 8 Oct 1998 01:56:49 +0200 From: Jan Koudelka <koudelka at appleklub dot cz> Subject: Re: Version 3.0 released >It's up there, folks. > > <ftp://ftp.dnai.com/users/m/meh/AutoShare/> > <http://www.dnai.com/~meh/autoshare/> How many people want me to make an upgrade of Remote Admin CGI? I know about only two users - me and Laine Lee, and that's too few to spend my time on that. HOnza
Date: Thu, 8 Oct 1998 23:15:28 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: AutoShare 3.0 compatibility? At 13:42 -0700 10/8/98, Michael Swan wrote: >will the new version use the 1.0 mailing list database (i.e. the list of subscribers for each mailing list) without modification? Yes, the standard subscriber format should be okay. Make a backup and walk carefully at first, and it's likely to be fine.
Date: Fri, 9 Oct 1998 15:39:12 -0600 From: Ken Tuley <tuley at aps dot edu> Subject: Re: Version 3.0 released At 1:56 AM +0200 10/8/98, Jan Koudelka altered cyberspace by writing: >>It's up there, folks. >> >> <ftp://ftp.dnai.com/users/m/meh/AutoShare/> >> <http://www.dnai.com/~meh/autoshare/> > >How many people want me to make an upgrade of Remote Admin CGI? > >I know about only two users - me and Laine Lee, and that's too few to spend >my time on that. I'd use it. Kenneth L. Tuley Manager, Software and Training Albuquerque Public Schools Technology Department 220 Monroe SE Albuquerque, NM 87108 (505) 256-4269 tuley at aps dot edu http://www.aps.edu
Date: Fri, 9 Oct 1998 18:47:36 -0400 From: Cris Mooney <cmooney at jumpdev dot com> Subject: Re: Version 3.0 released Hi Mikael: Back on 7/2/98 I made a couple suggestions for some features that when creatively used would add great power to the Auto-Response system (and offer power to "list" users as well). Retrospectively, I can see that they might have been difficult to implement and perhaps that has delayed any consideration you might have given them. On the other hand, if their are equivalents that I am not aware I would appreciate pointers to the documentation I might have missed. Auto-Response ------------- My main objective is that I do not always want to respond to all messages coming into a mailbox. I have a newer simpler "one command" solution, that would accomplish my goals as well as add extra (subtle) power to auto-response. The new requested "Auto-Response token": /=response-to <addr> = Send response to <addr> restoring original envelope sender and RFC From, rather than back to sender. If <addr> is "void", kill response. This would: 1) Allow no response to be sent for some subjects. In such cases, the message may already have been forked to another mailbox, or "/=forward" may have been used. 2) Allow modification of subject and message content, so we could fix up common errors made by users. This leverages all the work done on "responses" to be able to be used on incoming messages as a simple filter. It should also be killer simple to add, if I have any clue as to how this thing works. General ------- I would still like to see some sort of pattern matching of "string" to "filename" matching (in specific for Auto-Response documents). A simple solution might be a *filter* file in the "files" folder. Each line provides a pattern, and if the string (subject) matches then a file name is used. If the *filter* file doesn't exist, everything works the same. Example of both --------------- ------*filter*------ *add me*/subscribe_response *join*/subscribe_response *remove*/unsubscribe_response *jerks*/hates_lists -------------------- ------subscribe_response------ /=response-to my-list /=subject subscribe my-list subscribe my-list /=original ------subscribe_response------ ---------hates_lists---------- /=response-to void /=forward support Since response-to is void, the following is a comment. This user is confused and doesn't know how to use lists. Deal with them by hand at support rather than enrage them any more with automatic reponses. ------------------------------ Both these are fully backwards compatible, hurting no one, and at least the "/=response-to" should be very easy to implement. I hope you will consider them. Thanks for listening, Cris Mooney
Subject: Re: AutoShare-Talk digest 9 Oct 1998 Date: Fri, 9 Oct 98 18:42:59 -0500 From: Jon & Janelle Gardner <jgardner at kairosnet dot com> >How many people want me to make an upgrade of Remote Admin CGI? > >I know about only two users - me and Laine Lee, and that's too few to spend >my time on that. Y'know, I haven't tried your Remote Admin CGI (been using Timbuktu), but if you ever get around to updating it, I'd like to know about it. No pressure. Jon <>< Jon & Janelle Gardner <mailto:jgardner at kairosnet dot com> <AOLIM:DaGardners> Kairos Network Services <http://www.kairosnet.com/kairos/> PGP public key available at <http://www.kairosnet.com/kairos/pgpkey.html> ...as for me and my household, we will serve the Lord. (Joshua 24:15 NIV)
Date: Sun, 11 Oct 1998 00:53:08 -0400 From: Jerry Thompson <mlists at ppdirect dot com> Subject: AS 3.0.... and all is well. Greetings, Have the 3.0 version up and running... no problems. I'm sure it was mentioned, but I must have missed it. How do I move the users from the text file to the built-in database? Best Regards, Jerry Thompson MIS Director/Webmaster PP List Management, Inc. http://www.ppdirect.com/
Date: Mon, 12 Oct 1998 07:25:58 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: Version 3.0 released At 18:47 -0400 10/9/98, Cris Mooney wrote: >Back on 7/2/98 I made a couple suggestions for some features that when >creatively used would add great power to the Auto-Response system (and >offer power to "list" users as well). They were good suggestions and have not been forgotten. They just happened at a time when my time was taken up by the database subscriber formats. >Auto-Response >/=response-to <addr> = Send response to <addr> restoring original envelope > sender and RFC From, rather than back to sender. If > <addr> is "void", kill response. It's my guess that this would be fairly easy to do, if the change is no more than updating the SMTP envelope recipient address. You can btw probably do it already at this time by using the SetRes command in a process extender. >General >------- > >I would still like to see some sort of pattern matching of "string" >to "filename" matching (in specific for Auto-Response documents). Such a substring pattern would call for a search of potentially all files in the given folder. That should generally not be a problem. >A simple solution might be a *filter* file in the "files" folder. Each line >provides a pattern, and if the string (subject) matches then a file name is >used. If the *filter* file doesn't exist, everything works the same. > >Example of both >--------------- > >------*filter*------ >*add me*/subscribe_response I don't quite understand this. Specific actions are likely to require the tokens to be in the respective documents.
Date: Mon, 12 Oct 1998 07:26:14 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: AS 3.0.... and all is well. At 00:53 -0400 10/11/98, Jerry Thompson wrote: >Have the 3.0 version up and running... no problems. Thanks. >I'm sure it was mentioned, but I must have missed it. How do I move >the users from the text file to the built-in database? From the documentation: Running the server Running a list server List server and list basics Subscriber list files and formats Built-in database format "List files in the old standard format can be converted to the new built-in database format by dragging the list file in the List Server folder onto the AutoShare application icon (set to dbBuiltin first)." Be sure to use the posted 3.0.1b1 though, as testing of 3.0 revealed a compiler related bug affecting the built-in database format. As always, try with a test list first before getting serious.
Date: Tue, 13 Oct 1998 11:15:53 -0400 From: Cris Mooney <cmooney at jumpdev dot com> Subject: Re: "/=response_to" and "AS_Patterns" Hi Mikael: >>Auto-Response > >>/=response-to <addr> = Send response to <addr> restoring original envelope >> sender and RFC From, rather than back to sender. If >> <addr> is "void", kill response. > >It's my guess that this would be fairly easy to do, if the change is no >more than updating the SMTP envelope recipient address. I think that this is correct, and that is why I thought this new suggested implementation might be much simpler to implement and just as powerful as the original suggestions I made. >You can btw >probably do it already at this time by using the SetRes command in a >process extender. Thanks for this pointer. I have not had the time to investigate process extenders yet, but I will try to pull together the time to figure it out. Certainly, the step from configuring AutoShare to setting up to compile executables to link in to AutoShare is not a trivial leap (always a nasty startup penalty to get something like "hello extenders" to work). Whipping off a process extender is no doubt trivial for you since you are set up, but I suspect it would be a black hole for me (...oh, you mean I needed that release of that header file...I see, cc v7.8.1f3b has the fix for that bug...bla, bla, bla...). >>General >>------- >> >>I would still like to see some sort of pattern matching of "string" >>to "filename" matching (in specific for Auto-Response documents). > >Such a substring pattern would call for a search of potentially all files >in the given folder. That should generally not be a problem. > >>A simple solution might be a *filter* file in the "files" folder. Each line >>provides a pattern, and if the string (subject) matches then a file name is >>used. If the *filter* file doesn't exist, everything works the same. >> >>Example of both >>--------------- >> >>------*filter*------ >>*add me*/subscribe_response > >I don't quite understand this. Specific actions are likely to require the >tokens to be in the respective documents. I think that perhaps I was not very clear in describing my proposed solution. The problem addressed is that humans are not very specific, and thus often fail to get requests for "specific actions" properly phrased (like in the subject). If you tell someone to put remove in a subject to perform the specific action "unsubscribe", you will undoubtedly get "remove", "re: remove", and "re: Instructions, remove", all of which require the same "specific actions" to be performed. No doubt, in your internal list implementation you already have some form of limited predefined tolerance to address this problem (you have a built in limited pattern matching). What I suggest is a generic configurable pattern matching ability by adding a small enhancement to AutoShare. Creative pattern recognition can assist greatly. A pattern "*remove*" would reasonably cover all cases described above. Though one may not choose to use this feature, because in some cases it might be too ambiguous and dangerous, in many cases it is very acceptable. Moreover, there are often multiple disjoint instances that require the same actions and pattern matching provides the power to consolidate implementations. For example, since "remove" and "unsubscribe" are equivalent, they should perform the same "specific actions". The use of Mac file system "aliases" in many cases will suffice (and is what I do now; "re: remove"->"remove" and "re:remove"->"remove"). However, this is weaker than the equivalent "filters" in Eudora which allow the "contains" matching. As a result, I can distinguish all messages matching "*remove*" and "*unsubscribe*" in Eudora, but I can't do the same in AutoShare (I must try and predict every possible permutation dysfunctional humans can come up with). I am not suggesting that AutoShare is Eudora, nor that it should strive to be, I am simply drawing the parallel to further define the subject matter. With the problems and solutions redefined, perhaps my suggested implementations will make more sense when restated: By "*filter*" I meant a file of some random predefined name. Instead of "*filter*", let's remove the ambiguous "*"s and call this file "AS_Patterns" instead. I suggest the name "AS_Patterns" since it would contain pattern mappings, but any name will do in the same way you have predefined a special meaning for the name "Default". If "AS_Patterns" exists in a folder when AutoShare is attempting to access a file (call it <filename>) then, autoshare opens the "AS_Patterns" and processes each line to see if <filename> should be changed before opening the file. In the case above, if <filename> is "Add me to your list" (obtained from a message subject) then Autoshare would: 1) move to the appropriate documents directory based on the recipient mailbox 2) discover "AS_Patterns" and process each line (if no "AS_Pattern" skip to 3). a) if a pattern matches the <filename>, then use the new name. In my hypothetical case, the <filename> "Add me to your list" would match the pattern "*add me*" and thus <filename> would be changed to "subscribe_response". 3) open up <filename> ("subscribe_response") and proceed as normal. This long winded description is all just to describe adding step #2. Of course, this pattern matching might be extended to all file and directory access. For example, the folder "documents" could contain an "AS_Patterns" file and thus the "recipient" could be pattern matched before picking the appropriate "recipient" directory to use. Logically, this is all very similar to the "Default" technique used by Auto Share which allows you to use "Default" to apply to substitute for other names (subjects and recipients). Just a powerful variant. Though I can site numerous side benefits, like the fact that this would remove the "31 character <subject> matching limitation because of file name length", it is my experience that pattern matching like this is often leveraged in many ways no one will foresee. This sort of feature is so powerful that creative usage often surprises the author. It is possible, that you might have some pattern matching code and could just hook it into a strategic place with a file open and a small loop such that this power is provided across the board. In all this I recognize that your time is already generous and I appreciate it. These are only suggestions for you to consider if you like them. If you thought that you would add such a feature, I might be persuaded to pull together source for a routine "void filterSpec(FSSpec *filterMe)" that would take the normal spec and apply rule #2 above and you could insert it at strategic points in AutoShare. Thanks again for listening, Cris
Date: Tue, 13 Oct 1998 13:04:16 -0700 From: Camelot Administrator <camelot.admin at lmco dot com> Subject: Bug in 3.0? I had a mailing list which used an in-house alias address, mac.guild at lmco dot com. In Autoshare Admin, the list was set to configurable reply-to, and this alias was designated as the reply-to address (in the "Address" field). This worked perfectly! We were then informed that we would soon be losing the alias, so after years of using mac.guild, I had to change the configuration. I went into Autoshare Admin today and changed the address to mac at camelot.lmms.lmco dot com. I tested by making a post, and mac.guild at lmco dot com was still showing up as the reply-to and the to. So then I changed the list to no longer be configurable. It was set to reply-to list, and I deleted the address in the Address field. Another test post... same results. Mac.guild at lmco dot com was still showing up! Where was it getting it? I looked high and low for some hidden corner that I needed to clean up, but could not find it. As a last resort, I shutdown Autoshare, and restarted it. I made another post. This time I did observe in the autoshare status window that under "last time processed", the "to" line now indicates the mac at camelot.lmms.lmco dot com address (previous posts it was showing mac.guild at lmco.com). However, it is still showing mac dot guild at lmco dot com in the reply-to and the to of the posts! Aye carumba! What am I missing??? Bill In case it helps, here's what the Analysis file says: mac (1002): bill at camelot.lmms.lmco.com, admin at camelot dot lmms dot lmco dot com subscription, reply-to list, show names address: <default> NOCONCEAL, NODIGEST, MAIL, ACK, POST rollover is 10, max lines is 300 response must contain at least 1 percent of unquoted text List-Help: <default> no alternate name, show list web path: Camelot:Auto:Web: mail-back string: <default> subject prefix: <default> remote password: **** suppressing RFC headers: 123456789 list stuff: <default> address protection disabled tip of the day disabled approval both envelope and RFC enabled hard bounces do not unsubscribe disabled language: <default> database format <default> +----------------------------------------------------------------+ | Camelot Postmaster, mailto:camelot.admin at lmco dot com | | Lockheed Martin, Enterprise Information Systems, Sunnyvale, CA | +----------------------------------------------------------------+
Date: 13 Oct 98 14:34:37 -0500 From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us> Subject: Re: key in subject Autoshare3.0.1.b1 is available by mail from mailit at stumail.hopkins.k12.mn dot us Put Autosharebeta in the subject line of the message. Release version 3.0 is also available. Put Autoshare3 in the subject line. Problems with this system? Please contact chuck_boody at hopkins.k12.mn dot us =============
Date: Tue, 13 Oct 1998 20:19:15 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Version 3.0.1 released This partial archive has been uploaded to <ftp://ftp.dnai.com/users/m/meh/AutoShare/> <http://www.dnai.com/~meh/autoshare/> The minor 3.0.1 version gets around a compiler related bug affecting the built-in database subscriber format. Version 3.0 announcement in TidBITS: <http://www.tidbits.com/tb-issues/TidBITS-450.html>
Date: Tue, 13 Oct 1998 20:02:41 -0700 From: Mikael Hansen <meh at dnai dot com> Subject: Re: Bug in 3.0? At 13:04 -0700 10/13/98, Camelot Administrator wrote: >I went into Autoshare Admin today and changed the address to >mac at camelot.lmms.lmco dot com. >What am I missing??? >mac (1002): > bill at camelot.lmms.lmco.com, admin at camelot dot lmms dot lmco dot com > subscription, reply-to list, show names > address: <default> Set reply-to to configurable and address to mac at camelot.lmms.lmco dot com. If it doesn't work for you, send me the analysis file.
Date: Wed, 14 Oct 1998 15:02:49 +0100 From: James Berriman <james at dcl.co dot uk> Subject: Version 3.0.1 available at dcl.co.uk Roll up and get yours here, folks :-) <mailto:AutoShare-software at dcl.co.uk?subject=AutoShare-3.0.1 dot sit> <http://www.dcl.co.uk/MacOS/email/autoshare> ( :-]) James
Date: Wed, 14 Oct 1998 09:53:05 -0700 From: Camelot Administrator <camelot.admin at lmco dot com> Subject: Re: Version 3.0.1 released At 8:19 PM -0700 on 10/13/98, Mikael Hansen wrote: > This partial archive has been uploaded to > > <ftp://ftp.dnai.com/users/m/meh/AutoShare/> > <http://www.dnai.com/~meh/autoshare/> > > The minor 3.0.1 version gets around a compiler related bug affecting the > built-in database subscriber format. > Also available from http://pascal-central/autoshare/autoshare3.0.1.bin Cheers, Bill +----------------------------------------------------------------+ | Camelot Postmaster, mailto:camelot.admin at lmco dot com | | Lockheed Martin, Enterprise Information Systems, Sunnyvale, CA | +----------------------------------------------------------------+
From: Laine Lee <LLee at utsa dot edu> Subject: RE: Current digest not returned with subscription Date: Wed, 14 Oct 1998 17:19:58 -0500 >From: Mikael Hansen >Subject: Re: Current digest not returned with subscription > >At 12:43 -0500 10/6/98, Laine Lee wrote: > >> I recently noticed that a current digest is no longer >>being sent to new subscribers when a subscription request is received. > >I just tried it, and it worked fine. A partial digest will however not be >sent at subscription time if the digest file doesn't contain at least one >list contribution or if the letter e is specified in the Admin's List Stuff >field to suppress partial digests. I can still find no reason for this situation. The puzzling part is that the partial digest is generated successfully if the subscribe request is sent via the file mail command in the AutoshareAdmin.acgi. I'm wondering if the Autoshare preferences need to be renewed.
Date: Thu, 15 Oct 1998 09:55:09 -0700 From: Michael Ross <mross at antigone dot com> Subject: Eudora & CRON This might be a bit off-topic, but I'm trying to use the cron feature of AutoShare to send out a monthly text file (which is created by other means). So far my thoughts are to write an Applescript to instruct Eudora Light to do this. (If anyone has a script that takes a text file, creates the To: and Subject: fields, and queues it up, that would be great!) Anyone have any other ideas (this would be a nice feature to have "out of the box")? Cheers, Michael --- Michael Ross Antigone Press, Occidental CA USA mailto:mross at antigone dot com
Date: Fri, 16 Oct 1998 02:52:41 +0100 Subject: FW: Autoshare/SIMS/Multi-domains and lists From: listmaster at frutiger.staffs.ac dot uk (James Berriman) ---------- From: Greg Kopp <gkopp at haselow dot com> To: autoshare-talk at frutiger.staffs.ac dot uk (Subscribers of AutoShare-Talk) Subject: Autoshare/SIMS/Multi-domains and lists Date: Thu, Oct 15, 1998, 21:22 ************************************************************ Message body too big (229 > 150), forwarded to the moderator ************************************************************ I am having trouble getting Autoshare 3.0 to act as a list server with SIMS= 1.7b4. I have attached an Analysis file if it would help. I already have an autoresponder working in "request" and it is working fine. It's when trying to get "listserv" working that I run into trouble. I= have four accounts enabled. Two, "autoshare", and "link-comm" are save as folder only. "link-comm.d" and "link-comm.m" are distribution lists only. I= have the Finder Alias's made for each of these as per the SIMS-Autoshare instructions. I also have an alias built into the SIMS router so that a message sent to "listserv" will get re-routed to "autoshare." I am also running e-mail for several domains on this same machine, as can be noted in the analysis. When I try to subscribe with a message body of "subscribe link-comm Greg Kopp" sent to "listserv@cars dot org", I get the file Documents->listserv->Default. And no subscription is made. What am I doing wrong? Greg ------ Thu, 15 Oct 1998 15:01:55 AutoShare version is 3.0.1 AutoShare path: Server Startup:Server Applications:AutoShare: System Preferences path: Server Startup:System Folder:Preferences: AutoShare Preferences path: Server Startup:System Folder:Preferences:AutoShare: AutoShare memory: Memory available: 111K Memory at lowest: 110K Macintosh information: System version is 8.1 Processor type is PowerPC Finder processes: AppleShare IP Registry: 968K Finder Speed Copy 8 Server: 275K AppleShare IP Web & File Server: 200K Daemon: 290K MacDNS: 1,500K StylusRIP Server: 13,968K AppleShare IP Web & File: 2,621K SIMS: 900K Claris Emailer: 4,478K SimpleText: 512K AutoShare: 1,053K Macintosh memory: Low memory size: 10K Logical RAM size: 65,536K Disk usage: Disk Server Startup has 1,693,404,672 bytes available Time since run: 0 days 0 hours 10 minutes 5 seconds Next log in 24:00:00 Next digest in 24:00:00 Hosts: haselow.com cars.org safetyteam.org radix-wire.com high-temperature-wire.com ifi-fasteners.org industrial-fasteners.org Address of the list server account: autoshare at haselow dot com (Haselow List Server) The status window is hidden when in the background List-specific resources are not purged when starting up Processing delay is 0 seconds Relinguished processing time is 5 ticks Default creator is ttxt Default file type is TEXT Preferences creator is RSED Preferences file type is rsrc Expired mail-back files are checked every 10 minutes Expiration period of mail-back files is 600 minutes Lists are sorted by Unsorted Process time is displayed in Log Status of MIME is Text Plain Test bounce messages are sent every 1440 minutes Bounce received threshold is 5 Bounce sent threshold is 3 Time of bounce entry from created until deleted is 10080 minutes List-specific web archives are set to Complete List host is Subscriber addresses are based on envelope sender Subscriber aliases are not used Number of characters per formatted line is 80 Applications are kept up every 10 minutes Adjusting the processing mode every 60 minutes Adjusting the locking mode every 60 minutes Position of status window is Misc stuff is List server command sent to list= is suppressed for Always List server label is Unknown addresses is Bounce grace period is 7200 minutes Address of the administrator: listadmin at haselow dot com Address of the bounce account: Postmaster at haselow dot com (Haselow Postmaster) Log: Brief Format: Text Bounce: On Commands: Body Filed Mail folder: Server Startup:Server Applications:AutoShare:AutoShare Files:Filed Mail: Incoming Mail folder: Server Startup:System Folder:SIMS Folder:Submitted: Document folder: Server Startup:Server Applications:AutoShare:AutoShare Files:Documents: listserv: Default Footer.link-comm Get Header.link-comm Help: Default link-comm Index List Mailback Month.link-comm Query Release Review Search Set Sub Sub.link-comm Unsub Which request: Default GrinnellMacintosh GrinnellMacintosh.hqx GrinnellWindows RadixMacintosh RadixMacintosh.hqx RadixWindows RadixWindows.hqx List Server folder: Server Startup:Server Applications:AutoShare:AutoShare Files:List Server: link-comm link-comm.d link-comm.m Archive folder: Server Startup:Server Applications:AutoShare:AutoShare Files:Archive: link-comm: Current.text Current.txt Digest.text Digest.txt Filter folder: Server Startup:Server Applications:AutoShare:AutoShare Files:Filter: Mail Back folder: Server Startup:Server Applications:AutoShare:AutoShare Files:Mail Back: Hold Mail folder: Server Startup:Server Applications:AutoShare:AutoShare Files:Hold: Bounce folder: Server Startup:Server Applications:AutoShare:AutoShare Files:Bounce: General list configuration (1000): listadmin at haselow dot com , reply-to , NOCONCEAL, NODIGEST, MAIL, NOACK, POST rollover is 0, max lines is 0 response must contain at least 0 percent of unquoted text show list address protection disabled tip of the day disabled approval both envelope and RFC disabled hard bounces do not unsubscribe disabled database format standard List-specific configuration: link-comm (0): <default> <default>, reply-to <default>, <default> address: <default> <default>, <default>, <default>, <default>, <default> rollover is <default>, max lines is <default> response must contain at least <default> percent of unquoted text List-Help: <default> no alternate name, <default> web path: <default> mail-back string: <default> subject prefix: <default> remote password: <default> suppressing RFC headers: <default> list stuff: <default> address protection <default> tip of the day <default> approval both envelope and RFC <default> hard bounces do not unsubscribe <default> language: <default> database format <default> Internet Config: Internet Config Extension not installed -------- Greg Kopp (gkopp at haselow dot com) Multimedia Specialist / Network Administrator Haselow Marketing Communications (http://www.haselow.com)