Date: Thu, 18 Feb 1999 17:51:21 +0100
From: Jochen Haeberle <listen at MIDRAS dot de>
Subject: How do I stop partial Digests?
Hi,
How do I stop AutoShare from sending newly subscribed people a partial digest?
Or is there a way to delete some (test) messages from the lot that
will be put into the digest? Are these the archives?
Thanks for shedding some insight on me!
Jochen
Date: Thu, 18 Feb 1999 12:30:21 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: How do I stop partial Digests?
At 17:51 +0100 2/18/99, Jochen Haeberle wrote:
> How do I stop AutoShare from sending newly subscribed people a
> partial digest?
In order to suppress partial digests with new subscriptions, include
the letter e in the List Stuff field in the Admin's Yet More List
window.
(mentioned in minor improvements and bug fixes for version 2.1)
Date: Thu, 18 Feb 1999 12:38:11 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: AutoShare List Mails to Netscape users
At 15:06 +0100 2/18/99, Jochen Haeberle wrote:
> When AutoShare (3.0.3 at the moment) is sending mail (AutoReply or
> list-postings) to users using Netscape, they can only read the
> subject line of the message, the body seems to be empty.
>
> Only if people look at _the source_ of the message, they will find
> the actual message.
Do you have a sample illustrating this?
Date: Thu, 18 Feb 1999 12:44:14 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: preprocesor
At 11:52 -0800 2/13/99, Matthew Hill wrote:
> What i am looking for is a preprocessor that will grab the email to the
> list server check to be sure there is an email address, name, and user
> number. Then to check to be sure they can subscribe to a given list.
> If they can then subscribe them and add all the info to a data base.
I may have time this weekend to do a draft, unless someone else does
it first. Shouldn't be a difficult script and shouldn't be very
different from some of the sample scripts. For the sake of the
educational aspect, let's start up a discussion on the autoshare-dev
list doing this project.
Date: Thu, 18 Feb 1999 12:54:26 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Turning off Archives
At 15:04 -0600 2/12/99, Chuck Boody wrote:
> In the Documentation for AutoShare I read:
>
> You may choose both text and HTML formatted archives (rather than
> just one or the other). Having chosen this option (in the AutoShare
> application or using
> AppleScript; the Admin, see the List window), both text and HTML
> formatted archive files are created if necessary and updated when a
> list contribution is
> processed.
That's a typo. Should be the Misc window (Cmd-M).
> How do I get rid of archiving completely?
If I remember correctly, archives are only created if you specify a
valid archives folder path. But then digests aren't created either. I
should probably add a None option under Format in Cmd-M.
Date: 18 Feb 99 16:36:57 -0600
From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us>
Subject: Re: Turning off Archives
Reply to: Re: Turning off Archives
Yeah, do add the no archive option....
Chuck Boody
Analyst/Programmer
ISD 270
=======
Mikael Hansen wrote:
>At 15:04 -0600 2/12/99, Chuck Boody wrote:
>
>> In the Documentation for AutoShare I read:
>>
>> You may choose both text and HTML formatted archives (rather than =
>> just one or the other). Having chosen this option (in the AutoShare =
>> application or using
>> AppleScript; the Admin, see the List window), both text and HTML =
>> formatted archive files are created if necessary and updated when a =
>> list contribution is
>> processed.
>
>That's a typo. Should be the Misc window (Cmd-M).
>
>> How do I get rid of archiving completely?
>
>If I remember correctly, archives are only created if you specify a =
>valid archives folder path. But then digests aren't created either. I =
>should probably add a None option under Format in Cmd-M.
>
>
>** 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); Thu, 18 Feb 1999 15:04:05 -=
0600
> Received: from mercury.dnai.com (207.181.194.99) by frutiger.staffs.ac.=
uk with
> ESMTP (Eudora Internet Mail Server 2.2.1b4); Thu, 18 Feb 1999 20:58:27 +=
0000
> Received: from [207.181.206.18] (dnai-207-181-206-54.dialup.dnai.com =
>[207.181.206.54])
> by mercury.dnai.com (8.8.7/8.8.7) with ESMTP id MAA15555
> for <AutoShare-Talk at frutiger.staffs.ac dot uk>; Thu, 18 Feb 1999 12:54:53 =
>-0800 (PST)
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
> X-Sender: meh at pop.dnai dot com
> In-Reply-To: <148354690427139109342 at frutiger.staffs.ac dot uk>
> Date: Thu, 18 Feb 1999 12:54:26 -0800
> 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-ID: AutoShare-Talk.frutiger.staffs.ac.uk
> List-Software: AutoShare 3.0.5d1 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: Turning off Archives
> Message-Id: <283361745774058499471 at frutiger.staffs.ac dot uk>
>
Date: Fri, 19 Feb 1999 11:26:13 +0100
From: Jochen Haeberle <listen at MIDRAS dot de>
Subject: Re: How do I stop partial Digests?
Hi,
thanks for the tip!
At 12:30 Uhr -0800 18.02.1999, Mikael Hansen wrote:
> At 17:51 +0100 2/18/99, Jochen Haeberle wrote:
>
>> How do I stop AutoShare from sending newly subscribed people a
>> partial digest?
>
> In order to suppress partial digests with new subscriptions,
> include the letter e in the List Stuff field in the Admin's Yet
> More List window.
The ballon-help does not reflect this
> (mentioned in minor improvements and bug fixes for version 2.1)
sorry, yes, but I did not take the time to read the whole
documentation again for this. And finding a special info there is a
bit difficult.
Regards and thanks again
Jochen
Date: Fri, 19 Feb 1999 14:27:54 +0100
From: Jochen Haeberle <listen at MIDRAS dot de>
Subject: Re: AutoShare List Mails to Netscape users
Hi Mikael,
At 12:38 Uhr -0800 18.02.1999, Mikael Hansen wrote:
> At 15:06 +0100 2/18/99, Jochen Haeberle wrote:
>
>> When AutoShare (3.0.3 at the moment) is sending mail (AutoReply or
>> list-postings) to users using Netscape, they can only read the
>> subject line of the message, the body seems to be empty.
>>
>> Only if people look at _the source_ of the message, they will find
>> the actual message.
>
> Do you have a sample illustrating this?
What would you suggest? I will redirect a message created by my list
to your private account renaming it
"Attn: mysterious Netscape-Message", alright?
Or you could send an empty mail to mailto:vacation at midras dot de
This triggers an autoreply directly created by AutoShare and it
defenitely is not readable by Netscape users.
Regards
Jochen
Date: Fri, 19 Feb 1999 12:54:37 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: AutoShare List Mails to Netscape users
At 14:27 +0100 2/19/99, Jochen Haeberle wrote:
> This triggers an autoreply directly created by AutoShare and it
> defenitely is not readable by Netscape users.
Thanks to Jochen for off the list sending me a raw message file
processed by AutoShare. The only thing that I can find which may or
may not be wrong is the space before the semicolon, originated by the
sending mailer:
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Looks fine otherwise.
Date: Fri, 19 Feb 1999 12:56:19 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: How do I stop partial Digests?
At 11:26 +0100 2/19/99, Jochen Haeberle wrote:
> thanks for the tip!
>
> At 12:30 Uhr -0800 18.02.1999, Mikael Hansen wrote:
>> At 17:51 +0100 2/18/99, Jochen Haeberle wrote:
>>
>>> How do I stop AutoShare from sending newly subscribed people a
>>> partial digest?
>>
>> In order to suppress partial digests with new subscriptions,
>> include the letter e in the List Stuff field in the Admin's Yet
>> More List window.
>
> The ballon-help does not reflect this
Sure it does: "'e': disable partial digests". On top of the field title.
>> (mentioned in minor improvements and bug fixes for version 2.1)
>
> sorry, yes, but I did not take the time to read the whole
> documentation again for this. And finding a special info there is a
> bit difficult.
Search for 'partial digest' on the Documentation page; as there's no
match, do the same for the Versions page. Takes no more than a few
seconds. There are links to both pages from the home page.
Date: Sat, 20 Feb 1999 08:56:43 -0800
From: Matthew Hill <happytwo at milepost1 dot com>
Subject: Re: preprocesor
Hi
Yes I still need the preprocessor. I thought I had someone to do it but
have not heard from him. So if you are still willing I have subscribe
to the autoshare-dev list.
Thanks
Matthew
Mikael Hansen wrote:
>
> At 11:52 -0800 2/13/99, Matthew Hill wrote:
>
> > What i am looking for is a preprocessor that will grab the email to the
> > list server check to be sure there is an email address, name, and user
> > number. Then to check to be sure they can subscribe to a given list.
> > If they can then subscribe them and add all the info to a data base.
>
> I may have time this weekend to do a draft, unless someone else does
> it first. Shouldn't be a difficult script and shouldn't be very
> different from some of the sample scripts. For the sake of the
> educational aspect, let's start up a discussion on the autoshare-dev
> list doing this project.
>
> ** The AutoShare-Talk archives are at:
> ** <http://frutiger.staffs.ac.uk/autoshare/archives/>
--
Date: Sat, 20 Feb 1999 12:47:23 -0800
From: Mark Hartman <mh-list at harthaven dot com>
Subject: [ANNOUNCEMENT] New mailing list: SW-ROUTERS-LIST
With more and more deployment of DSL circuits, cable modems and other
high-speed Internet access, more and more homes and small businesses
are linking their internal networks to the Internet, and many of them
are doing it via software routing.
The SW-ROUTERS-LIST has been set up to facilitate discussion, problem-
solving, comparison of products and other purposes which fall under
the general heading of software Internet routing. The list is meant
to be primarily for Macintosh products, but discussions of other
products which are to be used in a primarily-Mac environment are
encouraged.
To subscribe, go to the harthaven.com subscriptions page at
<http://www.harthaven.com/subscribe>
or send e-mail to
<mailto:sw-routers-list-sub at harthaven dot com>
Please feel free to repost this announcement where appropriate.
Date: Sun, 21 Feb 1999 12:27:50 +0100
From: Jochen Haeberle <listen at MIDRAS dot de>
Subject: Re: AutoShare List Mails to Netscape users
Hi Mikael,
thanks for looking at the file!
At 12:54 Uhr -0800 19.02.1999, Mikael Hansen wrote:
> At 14:27 +0100 2/19/99, Jochen Haeberle wrote:
> Thanks to Jochen for off the list sending me a raw message file
> processed by AutoShare. The only thing that I can find which may or
> may not be wrong is the space before the semicolon, originated by
> the sending mailer:
>
>> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>
> Looks fine otherwise.
>
...but it does not work... the message sent to you was produced by
AutoShare as an AutoReply, so I guess the extra semicolon is from
AutoShare.
Could I change any settings to produce mails that might be readable
by Netscape?
Jochen
Date: Sun, 21 Feb 1999 12:42:07 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: AutoShare List Mails to Netscape users
At 12:27 +0100 2/21/99, Jochen Haeberle wrote:
>>> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
> ...but it does not work... the message sent to you was produced by
> AutoShare as an AutoReply, so I guess the extra semicolon is from
> AutoShare.
No, the entire line is originated by the sending mailer; the original
message reflects just that. Maybe Netscape has a problem with that or
the "flowed" thing. Try with a mailer different from Eudora and
Netscape to see what happens; I just tested your message file using
Pine and had no problems.
Date: Mon, 22 Feb 1999 09:57:28 +0100
From: Jochen Haeberle <listen at MIDRAS dot de>
Subject: Re: AutoShare List Mails to Netscape users
At 12:42 Uhr -0800 21.02.1999, Mikael Hansen wrote:
> At 12:27 +0100 2/21/99, Jochen Haeberle wrote:
>
>>>> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>
>> ...but it does not work... the message sent to you was produced by
>> AutoShare as an AutoReply, so I guess the extra semicolon is from
>> AutoShare.
>
> No, the entire line is originated by the sending mailer; the
> original message reflects just that. Maybe Netscape has a problem
> with that or the "flowed" thing. Try with a mailer different from
> Eudora and Netscape to see what happens; I just tested your message
> file using Pine and had no problems.
Does AutoShare reply a different message, if an autoreply is
triggered by different mailers? But the same thing happens if a
Netscape user triggers the autoreply (This is how I noticed this - as
my girlfriend tried my vacation-service and got no body!).
My mailer is Eudora Pro 4.1b, rather common I guess. I cannot get all
my users to switch from Netscape to another mailer.
Does noone else use Netscape and has a problem with Netscape? It is a
rather common mailer these days, I guess. If not, there must be a
solution to my problem somewhere.
Regards
Jochen
From: Laine Lee <LLee at utsa dot edu>
Subject: Wrapping text (also scripting addition conflict note)
Date: Thu, 25 Feb 1999 17:02:53 -0600
I just finished getting searchable auto web archives set up with my
Autoshare and web server and I'm really happy about it, but, uh, would some
kind soul point me to the place in the documentation that will tell me how
to set the wrapping of the text in Autoshare messages to a given number of
characters? I thought it was in More Miscellaneous settings in the Admin
app. No success changing it yet, though.
BTW, I think the scripting addition conflict for the cgi's with Akua
Sweets went away with version 1.3.
Thanks.
Laine D. Lee
llee at utsa dot edu
http://www.txdirect.net/users/llee
Internet Email: llee at txdirect dot net
Date: Thu, 25 Feb 1999 17:59:18 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Wrapping text (also scripting addition conflict note)
At 17:02 -0600 2/25/99, Laine Lee wrote:
> I just finished getting searchable auto web archives set up with my
> Autoshare and web server and I'm really happy about it, but, uh, would some
> kind soul point me to the place in the documentation that will tell me how
> to set the wrapping of the text in Autoshare messages to a given number of
> characters? I thought it was in More Miscellaneous settings in the Admin
> app.
You're probably referring to the Line Format field, whose line width
applies to document files inserted into outgoing messages. No other
kind of text wrapping is done by AutoShare.
Date: Fri, 26 Feb 1999 14:28:03 +0100
From: "Hans G. Hansson" <Hans.G.Hansson at tmbl.gu dot se>
Subject: EIMS loop
Hello,
We have been running EIMS (now v. 1.3.1 together with Mac OS 8.5.1)
for more than one and a half year successfully, using the EIMS Mailing
List facility for a few lists. A short time ago (after having tested the
fun-L example list with some few members for some weeks) I thought that
it would be better to use an interactive list-user interface via
AutoShare 3.04 and transferred the content of the old lists to new
lists, just adding an -L to the list names (else following the
instruction for the fun-L example in the AutoShare documentation).
Everything went well from the beginning, but yesterday something odd
happened. A Mailing List Error -43 is showed in the Error Log of EIMS
each second and in the ServerConsole window the following message is
shown also each second: "Moving message from bounce at tmbl.gu dot se to
doktorand-l.m@tmbl.gu dot se". When it started, I found that the EIMS
account doktorand-l.m by mistake had been forwarded to a wrongly spelled
Mailing List (the non-existing doktorander-l.m instead of
doktorand-l.m), but when changed to it's correct spelling nothing new
happened. The error messages continued and is continuing even if I quit
AutoShare or if the computer is restarted. Also the account
doktorand-l.m in the EIMS mail folder is growing to a size of several
megabytes in a day.
What did I do wrong, and what can I do about it, in order to get this
annoying error to disappear? I guess it has something to do with the
starting of a bounce account, which was not there, when I tested fun-L
from the beginning. Perhaps a bounce account is not fully necessary? I
am afraid that I (beeing a biologist rather than a computer person) have
not understood more than the fundamental basics of the AutoShare
documentation.
This loop is stopping the List Server commands to be returned to the
sender, but does evidently not stop normal email messages from arriving.
Please help!!!
Hans G. Hansson
Date: Fri, 26 Feb 1999 09:21:57 -0800
From: Michael Ross <mross at antigone dot com>
Subject: Re: [ANNOUNCEMENT] New mailing list: SW-ROUTERS-LIST
>To subscribe, go to the harthaven.com subscriptions page at
>
> <http://www.harthaven.com/subscribe>
>
>or send e-mail to
>
> <mailto:sw-routers-list-sub at harthaven dot com>
Your web subscription engine isn't quite working. Here's what I got when I
clicked on "Submit" after choosing the routers list, and filling in my info:
>The requested file was not found
>
>
>Quid Pro Quo 2.1
I then sent e-mail, so I might be on the list, but not as a result of the
Web page...
---
Michael Ross
Antigone Press, Occidental CA USA
mailto:mross at antigone dot com
Date: Fri, 26 Feb 1999 12:46:27 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: EIMS loop
At 14:28 +0100 2/26/99, Hans G. Hansson wrote:
> A Mailing List Error -43 is showed in the Error Log of EIMS
-43 is file not found.
> Also the account doktorand-l.m in the EIMS mail folder is growing
> to a size of several megabytes in a day.
I would delete all related to the doktorand-l.m account in EIMS and
create it from scratch. You also want to make sure that the account
is used exclusively for the AutoShare list contributions.
From: Laine Lee <LLee at utsa dot edu>
Subject: RE: Wrapping text (also scripting addition conflict note)
Date: Fri, 26 Feb 1999 15:47:59 -0600
Thanks, it's EIMS.
Date: Fri, 26 Feb 1999 17:15:17 -0800
From: Mark Hartman <mh-list at harthaven dot com>
Subject: Re: [ANNOUNCEMENT] New mailing list: SW-ROUTERS-LIST
I was having some server problems as of a couple of days ago, but
everything seems to be working now AFAICT. If anyone else has trouble
hitting the subscription page at the URL below, please e-mail me off
the list and let me know when you tried it, and with what browser.
Thanks.
At 9:21 AM -0800 2/26/1999, Michael Ross wrote:
>>To subscribe, go to the harthaven.com subscriptions page at
>>
>> <http://www.harthaven.com/subscribe>
>>
>>or send e-mail to
>>
>> <mailto:sw-routers-list-sub at harthaven dot com>
>
>Your web subscription engine isn't quite working. Here's what I got when I
>clicked on "Submit" after choosing the routers list, and filling in my
>info:
>
>>The requested file was not found
>>
>>
>>Quid Pro Quo 2.1
Date: Sun, 28 Feb 1999 23:01:32 -0800
From: Randall Gellens <randy at pensive dot org>
Subject: Archive Rollover?
I had set the default archive rollover to 50 messages, and left the
field blank for each list. I noticed today that there are well over
50 messages in one of my lists, yet everything is still in the
current archive files (text and HTML).
Does this have to be set for each list?
If I set it for a list, will the files get rolled over on the next
contribution?
Will the index.html file in the archives folder be updated with the
rolled-over files?
--
Randall Gellens Randy at Pensive dot Org
---------------------- (randomly-selected tag) ---------------------
You see, wire telegraph is a kind of very, very long cat. You
pull his tail in New York and his head is meowing in Los Angeles.
Do you understand this? And radio operates in exactly the same
way: you send signals here, they receive them there. The only
difference is that there is no cat. --Albert Einstein
Date: Mon, 1 Mar 1999 12:34:23 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Archive Rollover?
At 23:01 -0800 2/28/99, Randall Gellens wrote:
> I had set the default archive rollover to 50 messages, and left the
> field blank for each list. I noticed today that there are well
> over 50 messages in one of my lists, yet everything is still in the
> current archive files (text and HTML).
The override value for numeric list-specific fields is -1.
> Does this have to be set for each list?
Yes, but it is also the initial setting automatically.
> If I set it for a list, will the files get rolled over on the next
> contribution?
I think so.
> Will the index.html file in the archives folder be updated with the
> rolled-over files?
Yes.
Subject: Re: Logs and digests
Date: Thu, 4 Mar 1999 12:40:56 -0500
From: Charles L. Martin <clmartin at theombudsman dot com>
I am re-sending this message, as it appears to have fallen through the
cracks.
On 2/8/99 8:49 PM, Mikael Hansen said:
>At 16:41 -0500 2/8/99, Charles L. Martin wrote:
>
>> I did it (again), but all is not well. After following these
>> instructions, I quit AutoShare and opened the log. At the bottom, it said
>> the next log/archive was in 24:00:00. Unfortunately, it still says that
>> four days later. And no log has been sent even though it is set to do so
>> at 4:00pm each day (i.e. 16:00). Any ideas?
>
>Sure looks like there's something wrong with the prefs file. I would
>shut down AutoShare, open it with ResEdit, delete STR# 204, save it
>and shut down ResEdit, then start up AutoShare and reschedule with
>Command-T. If that doesn't do it, it's a corrupt prefs file.
Well, I got around to removing the preferences file today, but the new
file just got screwed up too. I still get no logs, and the log says "Next
log in 31367:17:09". With the old preference file it said 31359:17:38. Do
I need to delete both the preferences and the preferences backup? Or is
it something else? There must be some way of getting logs to work, since
they seem to work for everyone else.
Charles L. Martin
clmartin at theOmbudsman dot com
http://www.theOmbudsman.com/Martin_Law/
Date: Thu, 4 Mar 1999 22:46:01 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Logs and digests
At 12:40 -0500 3/4/99, Charles L. Martin wrote:
>>Sure looks like there's something wrong with the prefs file. I would
>>shut down AutoShare, open it with ResEdit, delete STR# 204, save it
>>and shut down ResEdit, then start up AutoShare and reschedule with
>>Command-T. If that doesn't do it, it's a corrupt prefs file.
>
> Well, I got around to removing the preferences file today, but the new
> file just got screwed up too. I still get no logs, and the log says "Next
> log in 31367:17:09". With the old preference file it said 31359:17:38. Do
> I need to delete both the preferences and the preferences backup? Or is
> it something else? There must be some way of getting logs to work, since
> they seem to work for everyone else.
And as everyone else includes me, I can't reproduce it. Try deleting
STR# 204 once again (or did you simply delete the file?) and put a
copy aside. Then start up AutoShare, do the Cmd-T thing, shut it down
and make another copy. StuffIt the two files and send them to me, and
I'll take a look at it.
I just tried with an entirely new preferences folder, and all was well.
Date: Sun, 7 Mar 1999 02:54:55 +0800
From: Derek Tom <derek at bbdo.com dot hk>
Subject: Attachments messed up
I'm running AutoShare 2.4 with EIMS 2.1.
All attachments sent from my colleagues using MS Outlook 97/98
(Windows) going through their Exchange Server 5.5 to AutoShare get
messed up. Here's what is sent to all subscribers:
#####
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01BE6731.2CE13C20
Content-Type: text/plain;
charset="iso-8859-1"
followed by 2000 or so lines of garbage
#####
Attachments they send directly to me come through just fine. I'm
using Eudora Pro 4.0 on a Mac.
If I send an attachment through AutoShare using Eudora Pro on my Mac,
I believe some of my colleagues have problems with it while others do
not.
I recall that AutoShare only properly handled BinHexed attachments.
Is that still the case and more importantly, is there any way
AutoShare can allow my Outlook-using colleagues to properly send
attachments to our lists?
Thanks in advance for any insight!
Cheers,
Derek
. . . . . . . . . . . . . . . . . . . . . . . .
Derek Tom
IT Manager, Asia
BBDO Asia Pacific
tel: 852.9017.3050
email: derek at bbdo.com dot hk
web: http://derek.bbdo.com.hk
Date: Sat, 6 Mar 1999 12:56:40 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Attachments messed up
At 02:54 +0800 3/7/99, Derek Tom wrote:
> I'm running AutoShare 2.4 with EIMS 2.1.
>
> All attachments sent from my colleagues using MS Outlook 97/98
> (Windows) going through their Exchange Server 5.5 to AutoShare get
> messed up.
I can well imagine that. List servers often need to interpret and
sometimes change a message, and side-effects from the unknown may
take place. While it's unlikely that I can do anything about the
above, feel free to send me a relevant StuffIt'ed message file from
the Filed Mail folder, which I can take a look at.
> I recall that AutoShare only properly handled BinHexed attachments.
> Is that still the case and more importantly, is there any way
> AutoShare can allow my Outlook-using colleagues to properly send
> attachments to our lists?
DropStuff at <http://www.aladdinsys.com/dropstuff/winindex.html>?
Date: Mon, 8 Mar 1999 11:41:21 +0800
From: Derek Tom <derek at bbdo.com dot hk>
Subject: Re: Attachments messed up
Hi Mikael,
>I can well imagine that. List servers often need to interpret and
>sometimes change a message, and side-effects from the unknown may
>take place. While it's unlikely that I can do anything about the
>above, feel free to send me a relevant StuffIt'ed message file from
>the Filed Mail folder, which I can take a look at.
Thanks very much for your reply and your offer to examine the
message. I will send you a StuffIt'ed relevant message directly to
you.
>> I recall that AutoShare only properly handled BinHexed attachments.
>> Is that still the case and more importantly, is there any way
>> AutoShare can allow my Outlook-using colleagues to properly send
>> attachments to our lists?
>
>DropStuff at <http://www.aladdinsys.com/dropstuff/winindex.html>?
So, if our Outlook users Stuff their attachments first, there should
be no problem?
Thanks again!
Cheers,
Derek
Date: Tue, 9 Mar 1999 15:32:52 +0100
From: Christoph Reichenberger <chrei at unisoft.co dot at>
Subject: Wrong Errors-To: address
Hi,
sorry if this is a FAQ, I've been off this list for a while now, but...
can anyone tell me what might be configured wrong if a bouncing mail
contains such an URL?
Mime-Version: 1.0
Content-Type: text/plain
To: xxx at hotmail dot com
From: autoshare at chianti.unisoft.co dot at
Errors-To:
listmaster at chianti.chianti.chianti.chianti.chianti.chianti.chianti.chianti dot chian
ti.chianti.chianti.chianti.chianti.chianti.chianti.chianti.chianti.chianti.chian
ti.chianti.chianti.chianti.chianti.chianti.chianti.chianti.chianti.chianti.chian
ti.u
Message-Id: <604599075367892448462 at chianti.unisoft.co dot at>
Thanks in advance
Christoph
---------------------------------------------------
Christoph Reichenberger Tel: +43-7236-3338-82
UNI SOFTWARE PLUS GMBH Fax: +43-7236-3338-30
Softwarepark Hagenberg, mailto:chrei at unisoft.co dot at
A-4232 Hagenberg, Austria http://www.unisoft.co.at
Date: Tue, 9 Mar 1999 06:57:54 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Wrong Errors-To: address
At 15:32 +0100 3/9/99, Christoph Reichenberger wrote:
> can anyone tell me what might be configured wrong if a bouncing mail
> contains such an URL?
>
> Mime-Version: 1.0
> Content-Type: text/plain
> To: xxx at hotmail dot com
> From: autoshare at chianti.unisoft.co dot at
> Errors-To:
>
> listmaster at chianti.chianti.chianti.chianti.chianti.chianti.chianti dot chi
> anti.chian
>
> ti.chianti.chianti.chianti.chianti.chianti.chianti.chianti.chianti.chi
> anti.chian
>
> ti.chianti.chianti.chianti.chianti.chianti.chianti.chianti.chianti.chi
> anti.chian
> ti.u
> Message-Id: <604599075367892448462 at chianti.unisoft.co dot at>
Could you send me a StuffIt'ed copy of a message file from the Filed
Mail folder resulting in this?
Date: Tue, 9 Mar 1999 21:23:48 -0800
From: Randall Gellens <randy at pensive dot org>
Subject: Admin Error "project script could not be loaded"
Sometimes when running the admin from a different Mac, I get an error
"Unable to continue because the project script could not be loaded
-43". What file is it looking for?
--
Randall Gellens Randy at Pensive dot Org
---------------------- (randomly-selected tag) ---------------------
If people don't know what you're doing, they don't know what you're
doing wrong. --Sir Arnold Robinson, _Yes, Minister_
From: Laine Lee <LLee at utsa dot edu>
Subject: RE: Admin Error "project script could not be loaded"
Date: Wed, 10 Mar 1999 13:13:52 -0600
I have seen that error with other FaceSpan applications, and while I haven't
isolated it, I believe it may be related to some system preference or
setting. You might get around it by copying the application file from a
machine where it has already run successfully because it seems to be
associated with first run.
> ----------
> From: Randall Gellens
> Reply To: autoshare-talk at frutiger.staffs.ac dot uk
> Sent: Tuesday, March 9, 1999 11:23 PM
> To: autoshare-talk at frutiger.staffs.ac dot uk
> Subject: Admin Error "project script could not be loaded"
>
> Sometimes when running the admin from a different Mac, I get an error
> "Unable to continue because the project script could not be loaded
> -43". What file is it looking for?
>
> --
> Randall Gellens Randy at Pensive dot Org
> ---------------------- (randomly-selected tag) ---------------------
> If people don't know what you're doing, they don't know what you're
> doing wrong. --Sir Arnold Robinson, _Yes, Minister_
>
>
> ** The AutoShare-Talk archives are at:
> ** <http://frutiger.staffs.ac.uk/autoshare/archives/>
>
Date: Mon, 15 Mar 1999 01:44:31 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: AutoShare 3.1 released
The 3.1 archive (complete) has been uploaded to
<ftp://ftp.dnai.com/users/m/meh/AutoShare/>
If you use StuffIt Expander, version 5.1 is required.
This version offers minor improvements and bug fixes plus the following.
Many bells and whistles have been added to the return message used in
the handling of unknown accounts. A document entitled Unknown allows
you to customize the body of the return message. Several /= tokens
are supported including the new /=unknown which inserts a standard
'User unknown' bounce line. Several documents with a standard folder
structure may be created to take the Precedence field body into
account.
Several new standard auto-response tokens are introduced such as
/=hdr for minimal RFC headers and /=body for message body only.
A speedy built-in BinHex encoding on-the-fly is introduced for
attachments with standard auto-responses. Plus a BinHex AppleScript
command for whatever file you like to encode. Standard auto-responses
in MIME now support multiple files to be attached via the /=attach
token.
None has been added as an archive format option, if you prefer
digests but are not interested in creating archives.
A new all-in-one Default process extender saves memory by allowing
multiple standard process extender handlers of any kind. If there is
no processor extender with a standard file name available, the
Default process extender is used.
If a Subscribe process extender returns a reply, no subscription
takes place, and the reply is written to the response message
Many improvements to the monthly help file feature, including a
remote Month command to send the help file to the list or a given
address.
The Admin and the documentation have been fully updated.
Date: Mon, 15 Mar 1999 14:12:08 -0500
From: Cris Mooney <cmooney at jumpdev dot com>
Subject: Re: AutoShare 3.1 released
>The 3.1 archive (complete) has been uploaded to
> <ftp://ftp.dnai.com/users/m/meh/AutoShare/>
>If you use StuffIt Expander, version 5.1 is required.
Sadly, I went direct to the page and found the download before getting this
email message. When my stuffit expander(4.0.2 which has always worked well
for me) would not expand (without explanation, claiming only damaged or not
SIT) I assumed I had a bad download. I downloaded a 4 or 5 times on various
machines (hoping to avoid bothering anyone) before discovering that version
5.1 Expander was required.
Mikael, and any mirrored links, might want to make a note on the web sites
as well to avoid extra hits. It would have been nice is Aladdin changed the
extension or something!
As busy as Mikael's site is, obviously a number of people are downloading.
You probably don't want uninformed fools like me downloading multiple
times, eating up connections and bandwidth.
I especially love the new "/=unknown" item.
Thanks for all the great work Mikael!
Regards,
Cris Mooney
Date: Mon, 15 Mar 1999 21:25:49 +0100
From: Giedo De Snijder <igiedsn at giedsn.eunet dot be>
Subject: Questions
Hi,
I am new on this list although I am using AutoShare for more than a year.
For the moment I am running v.2.2 but dowloaded v.3.0.4 yesterday.
First I would like to say how glad I am to be able to run such an
incredible good piece of software.
Thank you Mikael Hansen for your willingness to share your work.
I have taken a subscription to this list because I have a few questions.
Questions I couldn't clear out myself after reading twice the manual
(v.3.0.4) and the faq which comes with the AutoShare archive.
Although I run AutoShare very smoothly there are a few black holes in my
understanding ,when I look at certain options in the Miscellenous"
window,"More Miscellanous" window, "Lists", "Yet More List".
1) Miscellaneous
Purge checkbox
2)More Miscellaneous
Porcess time = log (other options : none - all - message)
message ????
Misc Stuff field ?
Label ?
File lock = 60 ?
Hide Window (vs show) = enabled
3) List window for a specific list`
e-mail ?
address ?
Name ?
unquoted % = -1 ( -1 is standing for ? a negative number ?)
lines = -1 ( -1 is standing for ? a negative number ?)
subscribers = 0 ( o means unlimited ?)
Mail-Back = ? (what are the options to fill this field ?)
4) More List
suppress RFC headers (what are the options to fill this
field?dumm question this one)
5) Yet more list
approval both
options: yes - no - default (default enabled) what
is the meaning of this ?
What is the function of the "Web Entry" folder in the "Auto" folder ?
I do know it has something to do with the MINIMAl (?) web archive feature.
I am using the automated COMPLETE web archive feature.
I am sorry but the explaination in the manual about the differrence between
the two, doesn't really help me.
My last question :
In the Extras menu there is an option "analysis" with two fields : email
and sections.
I have no idea which email address one has to fill in and what to insert in
the sections field.
I hope you don't already regret my subscription ;-)
I just want to learn.
I would like to have a good knowledge of the possibilities, to understand
what I am trying to configure.
Hopefully there are a few people on this list which can help me out
answering a few of my questions.
i would really appreciate your help and I am thanking you in advance.
_giedo
=============================================================
Giedo De Snijder giedo at beaware dot be
igiedsn at giedsn.eunet dot be
be.aware : to be digital or not, that'll become the problem
=============================================================
Date: Mon, 15 Mar 1999 12:31:40 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: AutoShare 3.1 released
At 14:12 -0500 3/15/99, Cris Mooney wrote:
>>The 3.1 archive (complete) has been uploaded to
>> <ftp://ftp.dnai.com/users/m/meh/AutoShare/>
>>If you use StuffIt Expander, version 5.1 is required.
>
> Sadly, I went direct to the page and found the download before getting this
> email message. When my stuffit expander(4.0.2 which has always worked well
> for me) would not expand (without explanation, claiming only damaged or not
> SIT) I assumed I had a bad download.
I did write that StuffIt Expander 5.1 was required :-) I'll add it to
the web site though.
StuffIt Expander 5.1 is free from <http://www.aladdinsys.com/expander/>.
Date: Mon, 15 Mar 1999 15:58:32 -0500
From: Cris Mooney <cmooney at jumpdev dot com>
Subject: v3.1, 550 customization is killing me
Hello:
With version 3.1 AutoShare I am having difficulty customizing the new 550
error.
In diagnosis I have verified the following:
1) In EIMS the "<any-name>" account saves in my AutoShare "documents" folder.
2) In AutoShare Admin the Prefs-> More Misc -> Unknown Address is empty.
This results in a successful "generic" built-in unknown user error
(example at the end of this message). Likewise, all standard "auto-reponse"
documents for configured accounts are working properly. Thus my "documents"
folder is the correct one.
3) I then add a text file named "Unknown", based on the AutoShare
documentation "Unknown accounts" section, to "configure [the] alert"
response; this file includes the new "/=unknown" token, and other
customization.
Yet, I still get the standard "generic" built-in unknown user error
(example at the end of this message). Apparently my "Unknown" file in the
docs folder is not being used.
4) As an alternative, I created an "Unknown" folder in my docuemnts folder,
and put my cutomized teext file in as "default".
Yet, I still get the standard "generic" built-in unknown user error
(example at the end of this message). Apparently my "Unknown" file in the
docs folder is not being used.
Perhaps I am missing something...
Question: Any ideas how to customize the new 550 error and use "/=unkown"?
Here is a copy of the generic 550 error always generated:
>To: Cris Mooney <cmooney at jumpdev dot com>
>From: Not_A_Valid_Name at jumpdev dot com
>Subject: Test of bounced unkown user.
>
>Sorry. The user of the recipient address is not valid.
>550 <Not_A_Valid_Name at jumpdev dot com>... User unknown
>Please contact support at jumpdev dot com
>
>Return-Path: <cmooney at jumpdev dot com>
>Received: from [206.210.79.33] by jumpdev.com
> with ESMTP (Eudora Internet Mail Server 1.3.1); Mon, 15 Mar 1999 15:45:48
>-0500
>X-Sender: cmooney at mail.jumpdev dot com
>Message-Id: <v03110702b31321271482 at [206.210.79 dot 33]>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>Date: Mon, 15 Mar 1999 15:43:00 -0500
>To: Not_A_Valid_Name at jumpdev dot com
>From: Cris Mooney <cmooney at jumpdev dot com>
>Subject: Test of bounced unkown user.
>
>Body of test.
Thanks for any help,
Cris Mooney
Date: Mon, 15 Mar 1999 19:36:25 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: v3.1, 550 customization is killing me
At 15:58 -0500 3/15/99, Cris Mooney wrote:
> 1) In EIMS the "<any-name>" account saves in my AutoShare "documents" folder.
It should save message files in the Filed Mail folder.
> 3) I then add a text file named "Unknown", based on the AutoShare
> documentation "Unknown accounts" section, to "configure [the] alert"
> response; this file includes the new "/=unknown" token, and other
> customization.
>
> Yet, I still get the standard "generic" built-in unknown user error
> (example at the end of this message). Apparently my "Unknown" file in the
> docs folder is not being used.
>
> 4) As an alternative, I created an "Unknown" folder in my docuemnts folder,
> and put my cutomized teext file in as "default".
From the documentation: "Or a configurable alert may be created via
the Unknown document in the AutoShare document folder."; that is the
AutoShare folder inside the Documents folder, where your list server
documents are.
Date: Mon, 15 Mar 1999 19:43:30 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Questions
At 21:25 +0100 3/15/99, Giedo De Snijder wrote:
> Hi,
>
> I am new on this list although I am using AutoShare for more than a year.
> For the moment I am running v.2.2 but dowloaded v.3.0.4 yesterday.
> First I would like to say how glad I am to be able to run such an
> incredible good piece of software.
> Thank you Mikael Hansen for your willingness to share your work.
Thanks :-)
> I have taken a subscription to this list because I have a few questions.
> Questions I couldn't clear out myself after reading twice the manual
> (v.3.0.4) and the faq which comes with the AutoShare archive.
> Although I run AutoShare very smoothly there are a few black holes in my
> understanding ,when I look at certain options in the Miscellenous"
> window,"More Miscellanous" window, "Lists", "Yet More List".
Try turning on the balloon help. Every field header explains the
field in question. If you have questions after having read them, feel
free to post them to the list here.
Date: Mon, 15 Mar 1999 21:39:57 -0800
From: Mark Hartman <mh-list at harthaven dot com>
Subject: Banning an address?
As is my wont, I'm borrowing trouble.
I'm about to set up a list which has some potential for lots of abuse
and/or flaming. Is there any way built into AutoShare to have an address
on the list which has no privileges (i.e., can't send, doesn't get posts)
including not being able to remove themselves from the list?
In other words, a way to lock a particular user out of the list?
If not, sounds like a cue for another process extender...
On that subject, BTW, Matthew Hill and I have put together a process
extender for AutoShare which permits you as the list administrator to
specify whether a user is authorized for a particular list and/or
whether a user has paid any fees due which are associated with a
subscription to that list. A FileMaker Pro database is used to track
the information, and from all reports it seems to work well and quickly.
If anyone might have use for this process extender, please contact me.
Date: Mon, 15 Mar 1999 22:10:26 -0800
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Banning an address?
At 21:39 -0800 3/15/99, Mark Hartman wrote:
> As is my wont, I'm borrowing trouble.
:-)
> I'm about to set up a list which has some potential for lots of abuse
> and/or flaming. Is there any way built into AutoShare to have an address
> on the list which has no privileges (i.e., can't send, doesn't get posts)
> including not being able to remove themselves from the list?
That would be a shadow of a subscriber ;-)
> In other words, a way to lock a particular user out of the list?
Yes, but using filters. Create a filters file named after the list
and enter a line saying From: <user address>.
> If not, sounds like a cue for another process extender...
You can certainly expand the above using a filter process extender.
> On that subject, BTW, Matthew Hill and I have put together a process
> extender for AutoShare which permits you as the list administrator to
> specify whether a user is authorized for a particular list and/or
> whether a user has paid any fees due which are associated with a
> subscription to that list. A FileMaker Pro database is used to track
> the information, and from all reports it seems to work well and quickly.
>
> If anyone might have use for this process extender, please contact me.
Great!
Date: 16 Mar 99 08:47:39 -0600
From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us>
Subject: Re: Banning an address?
Reply to: Re: Banning an address?
Any possibility of collecting together process extenders and other "how to =
do it" kinds of things for AutoShare onto the web site? That might help =
reduce questions on the list and alos provide lots of help for folks =
without Mikael having to do it all....
Chuck Boody
Analyst/Programmer
ISD 270
=======
Mikael Hansen wrote:
>At 21:39 -0800 3/15/99, Mark Hartman wrote:
>
>> As is my wont, I'm borrowing trouble.
>
>:-)
>
>> I'm about to set up a list which has some potential for lots of abuse
>> and/or flaming. Is there any way built into AutoShare to have an =
address
>> on the list which has no privileges (i.e., can't send, doesn't get =
posts)
>> including not being able to remove themselves from the list?
>
>That would be a shadow of a subscriber ;-)
>
>> In other words, a way to lock a particular user out of the list?
>
>Yes, but using filters. Create a filters file named after the list =
>and enter a line saying From: <user address>.
>
>> If not, sounds like a cue for another process extender...
>
>You can certainly expand the above using a filter process extender.
>
>> On that subject, BTW, Matthew Hill and I have put together a process
>> extender for AutoShare which permits you as the list administrator to
>> specify whether a user is authorized for a particular list and/or
>> whether a user has paid any fees due which are associated with a
>> subscription to that list. A FileMaker Pro database is used to track
>> the information, and from all reports it seems to work well and quickly.=
>>
>> If anyone might have use for this process extender, please contact me.
>
>Great!
>
>
>
>** 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.1); Tue, 16 Mar 1999 00:27:14 -=
0600
> Received: from mercury.dnai.com (207.181.194.99) by frutiger.staffs.ac.=
uk with
> ESMTP (Eudora Internet Mail Server 2.2.1); Tue, 16 Mar 1999 06:24:35 +=
0000
> Received: from [207.181.206.25] (dnai-207-181-206-14.dialup.dnai.com =
>[207.181.206.14])
> by mercury.dnai.com (8.8.7/8.8.7) with ESMTP id WAA23746
> for <autoshare-talk at frutiger.staffs.ac dot uk>; Mon, 15 Mar 1999 22:09:46 =
>-0800 (PST)
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
> X-Sender: meh at pop.dnai dot com
> In-Reply-To: <161511477767572175809 at frutiger.staffs.ac dot uk>
> References: <785782936165922259918 at frutiger.staffs.ac dot uk>
> <161511477767572175809 at frutiger.staffs.ac dot uk>
> Date: Mon, 15 Mar 1999 22:10:26 -0800
> 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-Id: AutoShare-Talk.frutiger.staffs.ac.uk
> List-Software: AutoShare 3.2d1 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: Banning an address?
> Message-Id: <796688195757959226295 at frutiger.staffs.ac dot uk>
>
Date: Tue, 16 Mar 1999 10:53:36 -0500
From: Cris Mooney <cmooney at jumpdev dot com>
Subject: Autoshare documentation
There have been a number of comments about the difficulty in reading the
documentation for AutoShare. My comments here are meant to touch upon a
couple areas that might be fundamental issues contributing to that
difficulty. They are my attempts at constructive feedback...following my
wasting another few hours attempting to figure out how to use an AutoShare
feature, and then having to bother Mikael to get the answer.
Mikael responded to my earlier "550 customization" question with:
>From the documentation: "Or a configurable alert may be created via
>the Unknown document in the AutoShare document folder.";
To me, the words "Autoshare document folder" are at best ambiguous. Since
"AutoShare" is a proper noun, correctly capitalized in any situation, the
phrase "AutoShare document folder" might be, and was in my case, reasonably
interpreted to mean the "Documentation folder" for AutoShare. This
interpretation might have been overcome if the term "Autoshare document
folder" had been described as a proper noun commonly used throughout the
document. However, searching proves that this is not the case. And, even if
it had been overcome this way, it would have required that I read the whole
document to use the one feature; a requirement for no good reason.
Moreover, "Created via" is passive, where an active phrase is far more
effective.
Since there is no need for this ambiguity, I respectfully submit that this
documentation line be reworded to remove the ambiguity:
-----------------------------------------------
Create a custom response by putting a file named "Unknown" inside the
"AutoShare" folder inside the "Documents" folder.
-----------------------------------------------
It is not much longer, and is unambiguous.
>that is the
>AutoShare folder inside the Documents folder, where your list server
>documents are.
Here, I am once again surprised to find that a simple Auto Response (for
undeliverable mail) brings the term "list" into the answer. I don't use
AutoShare for lists, and don't see how an undeliverable Auto Response
should bring the word "list" into the discussion. Certainly, the
implication here is that I should know about lists, and that this should
make the "AutoShare document folder" obvious. But, why should I know about
lists? I don't use AutoShare for lists, nor is this undeliverable mail a
"list" feature.
Ambiguous wording, and failure to document strange interaction between
lists/auto-responses/forms, plague the documentatio. They make it very
difficult to make use this great product.
My comments certainly seem like nit-picking. However, the bitch is always
in the details. My comments address issues that are fundamental to the
reasons individuals comment that AutoShare, and the documentation, are hard
to use - despite it being a very powerful, great, product. They are the
reason I spent another 3 hours yesterday attempting to figure out how to
customize a simple 550 error, and then had to bother the list. Such a waste
of time.
I hope the comments are constructive.
What to do?
I would like to offer my help to rework the AutoShare documents. However, I
don't know much about any aspects of AutoShare but Auto Response. Thus, I
am not qualified to take on the whole manual. It would be nice if someone
who has more familiarity with the entire subject were to undertake a
documentation project - leaving Mikael to write code.
Mikael has provided us with a great product. But, respectfully, I submit
that documentation is not his strong point. It seems there are often
questions asked on this list that only he answers, problems that are mostly
the result of weak documentation, and this takes away from his coding time.
And, we would all prefer to see him focus on the code.
If anyone is interested in attempting to pull together a secondary, or with
Mikael's cooperation fix up the primary, documentation effort, I would like
to offer my help to handle the Auto-Reponse aspects of documentation.
Anyone who wants to do something about the documents, please drop me a note.
Perhaps this has already been done before, or is a doomed idea from the
start. I recognize I am an optimist in this department. So, of course,
Mikael please tell me if you want me to get lost. Because, once again, it
seems I have got AutoShare working for me and I can disappear for another 6
months...until the next episode.
Thanks for all your work Mikael.
Regards,
Cris Mooney
Date: Tue, 16 Mar 1999 17:20:21 +0000
From: James Berriman <james at dcl.co dot uk>
Subject: Re: AutoShare 3.1 released
Now available at:
<http://www.dcl.co.uk/MacOS/email/autoshare/>
<mailto:AutoShare-software at dcl.co.uk?subject=AutoShare3.1 dot sit>
( :-]) James
Date: Tue, 16 Mar 1999 16:30:53 -0500
From: "Christopher T. Payne" <CTPayne at lbl dot gov>
Subject: Re: Autoshare documentation
I too have been frustrated by the level of complexity inherent in the
AutoShare documentation. I am no stranger to the Macintosh, nor to computer
manuals, having diligently read manuals since I first started with my 128K
Mac in 1986; however, I find that I'm often left extremely confused by what
steps are necessary to implement a simple AutoShare feature. As a result, I
feel as though I'm missing out on the vast majority of the features
available via AutoShare. I've got a powerful tool here that I want to make
use of, but using it effectively is difficult.
I must confess that I know very little of AutoShare besides the rudimentary
steps necessary to get the automatic "vacation" response feature to work.
However, I'd be happy to participate in a documentation effort. Not only
would I likely learn more about AutoShare by doing so, but hopefully the
result would be a more user-friendly product. That product could then
become more prevalent.
Please count me in on this documentation effort, and let me know what I can
do to help.
-CTP
At 10:53 AM -0500 3/16/99, Cris Mooney wrote:
>There have been a number of comments about the difficulty in reading the
>documentation for AutoShare. My comments here are meant to touch upon a
>couple areas that might be fundamental issues contributing to that
>difficulty. They are my attempts at constructive feedback...following my
>wasting another few hours attempting to figure out how to use an AutoShare
>feature, and then having to bother Mikael to get the answer.
>
>Mikael responded to my earlier "550 customization" question with:
>
>>From the documentation: "Or a configurable alert may be created via
>>the Unknown document in the AutoShare document folder.";
>
>To me, the words "Autoshare document folder" are at best ambiguous. Since
>"AutoShare" is a proper noun, correctly capitalized in any situation, the
>phrase "AutoShare document folder" might be, and was in my case, reasonably
>interpreted to mean the "Documentation folder" for AutoShare. This
>interpretation might have been overcome if the term "Autoshare document
>folder" had been described as a proper noun commonly used throughout the
>document. However, searching proves that this is not the case. And, even if
>it had been overcome this way, it would have required that I read the whole
>document to use the one feature; a requirement for no good reason.
>
>Moreover, "Created via" is passive, where an active phrase is far more
>effective.
>
>Since there is no need for this ambiguity, I respectfully submit that this
>documentation line be reworded to remove the ambiguity:
>
>-----------------------------------------------
>Create a custom response by putting a file named "Unknown" inside the
>"AutoShare" folder inside the "Documents" folder.
>-----------------------------------------------
>
>It is not much longer, and is unambiguous.
>
>>that is the
>>AutoShare folder inside the Documents folder, where your list server
>>documents are.
>
>Here, I am once again surprised to find that a simple Auto Response (for
>undeliverable mail) brings the term "list" into the answer. I don't use
>AutoShare for lists, and don't see how an undeliverable Auto Response
>should bring the word "list" into the discussion. Certainly, the
>implication here is that I should know about lists, and that this should
>make the "AutoShare document folder" obvious. But, why should I know about
>lists? I don't use AutoShare for lists, nor is this undeliverable mail a
>"list" feature.
>
>Ambiguous wording, and failure to document strange interaction between
>lists/auto-responses/forms, plague the documentatio. They make it very
>difficult to make use this great product.
>
>My comments certainly seem like nit-picking. However, the bitch is always
>in the details. My comments address issues that are fundamental to the
>reasons individuals comment that AutoShare, and the documentation, are hard
>to use - despite it being a very powerful, great, product. They are the
>reason I spent another 3 hours yesterday attempting to figure out how to
>customize a simple 550 error, and then had to bother the list. Such a waste
>of time.
>
>I hope the comments are constructive.
>
>What to do?
>
>I would like to offer my help to rework the AutoShare documents. However, I
>don't know much about any aspects of AutoShare but Auto Response. Thus, I
>am not qualified to take on the whole manual. It would be nice if someone
>who has more familiarity with the entire subject were to undertake a
>documentation project - leaving Mikael to write code.
>
>Mikael has provided us with a great product. But, respectfully, I submit
>that documentation is not his strong point. It seems there are often
>questions asked on this list that only he answers, problems that are mostly
>the result of weak documentation, and this takes away from his coding time.
>And, we would all prefer to see him focus on the code.
>
>If anyone is interested in attempting to pull together a secondary, or with
>Mikael's cooperation fix up the primary, documentation effort, I would like
>to offer my help to handle the Auto-Reponse aspects of documentation.
>
>Anyone who wants to do something about the documents, please drop me a note.
>
>Perhaps this has already been done before, or is a doomed idea from the
>start. I recognize I am an optimist in this department. So, of course,
>Mikael please tell me if you want me to get lost. Because, once again, it
>seems I have got AutoShare working for me and I can disappear for another 6
>months...until the next episode.
>
>Thanks for all your work Mikael.
>
>Regards,
>Cris Mooney
Date: Tue, 16 Mar 1999 13:30:16 -0800
From: Glenn Gutierrez <kernelg at home dot com>
Subject: Re: Autoshare documentation
I think this has been the biggest stumbling block for me with the
documentation. It seems that every section assumes knowledge of the
other sections. Kind of a catch-22 for anyone but the programmer
himself.
Maybe some hyperlinks in the HTML would help, but an in-depth
explanation of each function in a specific place would be great. The
other night, I was trying to figure out exactly what I could control on
my lists with the 'set' remote email command. All I could find were
occasional references to it from other topics. One table with links
back to those sections could have helped immensely.
Of course, maybe I just missed it. Again. :)
At 7:53 -0800 990316, Cris Mooney wrote:
>Here, I am once again surprised to find that a simple Auto Response (for
>undeliverable mail) brings the term "list" into the answer. I don't use
>AutoShare for lists, and don't see how an undeliverable Auto Response
>should bring the word "list" into the discussion. Certainly, the
>implication here is that I should know about lists, and that this should
>make the "AutoShare document folder" obvious. But, why should I know about
>lists? I don't use AutoShare for lists, nor is this undeliverable mail a
>"list" feature.
Date: Tue, 16 Mar 1999 17:08:56 -0500
From: Cris Mooney <cmooney at jumpdev dot com>
Subject: Failure posting to the AutoShare list.
Hi Mikael:
I tried to post to the mailing list and got the following error. I don't
see where "The word get" is in my message. Do you know why it was rejected?
How can I post this message?
Also, as you will note, I am posting a bit on the mailing list. Please let
me know if you want me to shut up. Thanks, Cris
>To: AutoShare-Talk at frutiger.staffs.ac dot uk (Subscribers of AutoShare-Talk)
>From: Cris Mooney <cmooney at jumpdev dot com>
>Subject: Send Me Autoshare Process Extenders (was: Banning an address?)
>
>************************************************************
>ATTENTION PLEASE
>Sorry. Your message did NOT get posted or forwarded
>The word get is a list server command
>A list server command must be sent to the list server address
>The list server address is autoshare at frutiger.staffs.ac dot uk
>************************************************************
>
>Hello all:
>
>>Any possibility of collecting together process extenders and other
>>"how to do it" kinds of things for AutoShare onto the web site?
>
>I am not much for talk.
>
>I would like to immediately start to collect procees extenders and make
>them available on he web. I think that Mikael has his hands full, and would
>like to take this task on with his agreement.
>
>Starting immediately, please mail any process extenders to me at
>cmooney at jumpdev dot com. I will collect these and start making them available
>within days.
>
>Please send me mail, or visit "http://as.forus.com" (may only be available
>as "www1.forus.com" until DNS propegates within 5 hours) with:
>
>Subject: Autoshare process extender <extender name>
>---- Body ----
>Name: <extender name>
>Date: <release date>
>Author Name: <your name>
>Author EMail: <your email>
>Author URL: <your URL>
><60 char description>
><Long description>
>---------------
>
>Fill in what fields you can (that make sense), and provide a URL to
>documentation and/or required files. I would prefer URLs right now, rather
>than getting them via EMail.
>
>This is a very preliminary method for collecting this information, I will
>refine it in the future and post more information. However, I would like to
>get this started rigth now. Once started, I can look at it and see if there
>is some sensible organization, and perhaps a need to provide mirror sites
>if usage is high.
>
>The site is "http://as.forus.com" (and "autoshare.forus.com"), unless
>Mikael would like me to shut it down. FTP is "ftp://ftp.forus.com/as" (and
>"ftp://ftp.forus.com/autoshare"). Currently, my bandwidth is low (ISDN),
>but it will increase within a month or so to high volume.
>
>I don't have enough time to do much more, so please recruit authors. If you
>know someone that has written an extender, please mail them and ask them to
>send it for publication!
>
>Regards,
>Cris Mooney
>
>
>
>
>** The AutoShare-Talk archives are at:
>** <http://frutiger.staffs.ac.uk/autoshare/archives/>
Date: Tue, 16 Mar 1999 15:36:44 -0800
From: Camelot Administrator <camelot.admin at lmco dot com>
Subject: Re: AutoShare 3.1 released
At 1:44 AM -0800 on 3/15/99, Mikael Hansen wrote:
> The 3.1 archive (complete) has been uploaded to
> <ftp://ftp.dnai.com/users/m/meh/AutoShare/>
> If you use StuffIt Expander, version 5.1 is required.
>
Now mirrored at:
http://pascal-central.com/autoshare/autoshare3.1.bin
Cheers,
Bill
+----------------------------------------------------------------+
| Camelot Administrator, mailto:camelot.admin at lmco dot com |
| Lockheed Martin, Enterprise Information Systems, Sunnyvale, CA |
+----------------------------------------------------------------+
Date: Tue, 16 Mar 1999 14:33:24 -0800
From: David Baker <dbaker at mttam dot org>
Subject: 3.1 Crashing
Thanks for creating such a wonderful program! I was so excited about the
upgrade I downloaded it as soon as I found out. Unfortunately, I am now
experiencing some difficulty.
We have been using AutoShare 3.0.3 for a couple of weeks now. I downloaded
3.1 this morning and tried to do the conversion this afternoon.
Unfortunately, every time I try and configure 3.1 it either crashes the server
or the application quits. I am currently running AutoShare on a G3 server (OS
8.1) running Appleshare 5.0.3, AIMS 1.1.1, and ServerManager. After the first
system crash I replaced the autoshare 3.0.3 preferences in the system folder
with the 3.1 preferences. No longer does the system crash, but each time I
try and and configure 3.1 the application does. I realize I should upgrade to
EIMS, but haven't as I often find upgrades create other problems and it has
been working. I read your release notes about changing the mail folder
location, is there anything else I should be aware of in going with EIMS.
Thanks!
Aloha,
Dave