Date: Mon, 20 Apr 1998 19:48:39 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Admin 2.2 error
At 11:45 +0000 20/4/1998, John Schmit wrote:
>I keep getting the FaceSpan extension error when I run AutoShare Admin 2.2.
An oldie, but a goodie! From the AutoShare 2.2 Documentation:
Running the server
Interfaces
AutoShare Admin application
"The FaceSpan Extension is expecting to find the QuickTime and QuickTime
PowerPlug extensions in the system before it can be resolved."
Date: Tue, 21 Apr 1998 09:37:44 -0700
From: Camelot Administrator <camelot.admin at lmco dot com>
Subject: Re: Monitoring Attachments to lists...
At 12:17 PM -0700 on 4/20/98, Mikael Hansen wrote:
> At 08:53 -0700 20/4/1998, Camelot Administrator wrote:
>
> >Does Autoshare support block attachments to a list which are over a certain
> >size? I want to allow small attachments, but large attachments are killing
> >the server (and annoying a lot of people), so I'd like to cause those to
> >bounce.
>
> AutoShare can be configured to block (forward to listmaster rather than
> being posted) messages, whose lines (including raw attachments lines, if
> any) exceed a given number. See the Lines field in the List window in the
> Admin.
>
> A BinHex line for instance is around 65 characters, so a 4K attachment size
> divided by 65 lines would be around 60 lines. Then add x number of lines
> for the message header and body.
>
That'll work. Thanks.
Bill
+----------------------------------------------------------------+
| Bill Catambay, Software Developer, Webmaster |
| Lockheed Martin, Enterprise Information Systems, Sunnyvale, CA |
| WORK -> mailto:bill.m.catambay at lmco dot com |
| HOME -> mailto:bill at catambay dot com |
| |
| Pascal Central -> http://www.catambay.com/pascal-central |
| Macintosh Guild -> http://www.rahul.net/rrk/lmms/mac |
+----------------------------------------------------------------+
Date: Tue, 21 Apr 1998 10:17:10 -0800
From: Milo Sharp <milo at polarnet dot com>
Subject: Weekly Digests
I know Autoshare supports digest modes, but can you configure how
often the digests should be mailed? I have a very low volume mailing list
(maybe 2-3 messages per week), but it goes to some very busy scientists,
many of who would prefer a weekly digest rather than even 2-3 messages a
week. If anyone has any experience setting up weekly digests, I'd
appreciate a few pointers.
Milo Sharp
Technical Assistant, ARCUS
Email: milo at polarnet dot com
Phone: 907/474-1602
Fax: 907/474-1604
From: John Schmit <complab at prescott dot edu>
Subject: Re: AutoShare-Talk digest 21 Apr 1998
Date: Tue, 21 Apr 1998 09:58:41 +0000
>At 11:45 AM +0000 4/20/98, John Schmit wrote:
>>I keep getting the FaceSpan extension error when I run AutoShare Admin 2.2.
>>Every time I launch the admin application it asks for the FaceSpan
>>extension. But I'm using Autoshare 2.2 and AutoShare Admin 2.2 which
>>supposedly has this extension built in. Even when I had the 2.1 version of
>>FaceSpan extension and pointed to it, the admin application gave an error
>>saying that extention was "missing, would not open, or too old a version."
>>
>>I have looked for info on this but to no avail. I am runing these on a ppc
>>6150 with EIMS 1.2. Can anyone help?
>
>Do you have all the QuickTime extensions installed? I found (quite by
>accident) that without these present, I got the msg.
>
>
>GSz
Thanks Gary. I turned on the QuickTime extension and AutoShare Admin
finally worked.
- jas
Date: Tue, 21 Apr 1998 12:48:53 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Weekly Digests
At 10:17 -0800 21/4/1998, Milo Sharp wrote:
> I know Autoshare supports digest modes, but can you configure how
>often the digests should be mailed?
Command-T (Preferences, Times) in the server application (or the Admin).
Select Digests from the top popup, then set times from the lower popups.
Date: Wed, 22 Apr 1998 18:06:21 -0500
From: "Richard Petty" <rwvr90 at email.sps.mot dot com>
Subject: AutoShare Crashy?
I've just started using AutoShare v2.1 and have had some worrisome
reliability problems.
First, the remote admin will crash in a heartbeat unless EVERYTHING is
perfect when setting up new lists. I mean it completely locks up my computer.
Several tasks have to be completed for setting up a new mailing list before
even attempting to use the Remote Admin. I figure that occasionally some
steps may be missed in this process, but it shouldn't lock up my whole machine.
Second, AutoShare itself has locked up twice now in just a week and I
haven't even really "released" any lists on it yet (one time while it was
being accessed by the Remote Admin and the other time, this morning, all on
it's own).
This is a real problem for me since I work 17-miles away from my server
across some treacherous automobile traffic.
I do want to say that when it works it works great and I'm really looking
forward to being successful with it.
Server: PowerMac 7200/75
System 8.1
AutoShare 2.1
EIMS 1.2
QPQ 2.1
Frontier 5.0.1
NetEvents 1.0.1
24-Meg RAM
Virtual memory on (I know...)
Lots of disk space
My Mac: PowerMac 7300/200
System 8.1
Lots of RAM and disk space
Lots of software junk my company requires
Although it's running quite a few apps, the server gets very little
activity. I'm quite fastidious with it and keep it lean and clean as I can.
If there's any resource I can research for similar problems I'd be grateful
for the suggestion.
TIA,
--Richard Petty
Motorola
Austin, Texas
Date: Wed, 22 Apr 1998 18:06:26 -0500
From: "Richard Petty" <rwvr90 at email.sps.mot dot com>
Subject: AutoShare and File Attachments
My company uses Netscape Communicator for our email applications and
Netscape email server for serving (IMAP protocol).
My own server is EIMS 1.2 and I'm using it with AutoShare 1.2.
I've had peculiar results sending file attachments to the list (one of the
purposes of the list is to distribute virus definition files).
I sent an attachment sent using Netscape Communicator 4.03 and sent it to an
AutoShare list (hosted by EIMS). The message is then sent out to the Netscape
mail server and when it arrives back in Communicator it's an empty file.
I'm also running Eudora Lite 3.1 on the side (I still need a reliable email
client ;-> ) and when the message arrives here it's Base64 encoded. I'm
pretty sure Eudora doesn't decode Base64 so I'm okay with that, but I also
know that Communicator both encodes and decodes Base64.
How come the attachments arrive empty? Am I missing something?
TIA,
--Richard Petty
Motorola
Austin, Texas
Date: Thu, 23 Apr 1998 00:42:15 +0100
Subject: Re: AutoShare and File Attachments
From: "James Berriman" <J.R.Berriman at staffs.ac dot uk>
> I've had peculiar results sending file attachments to the list (one of
the
>purposes of the list is to distribute virus definition files).
>
> I sent an attachment sent using Netscape Communicator 4.03 and sent it to
an
>AutoShare list (hosted by EIMS). The message is then sent out to the
Netscape
>mail server and when it arrives back in Communicator it's an empty file.
AutoShare 2.1 only supports binhex attachments. Mikael did away with that
limitation in version 2.2.
( :-]) James
Date: Wed, 22 Apr 1998 20:26:55 -0400
From: Jonathan Shaw <jls4 at cwru dot edu>
Subject: Re: AutoShare Crashy?
> Server: PowerMac 7200/75
> System 8.1
> AutoShare 2.1
> EIMS 1.2
> QPQ 2.1
^^^^^^^
I've used QPQ within the last few months... It has a lot of nice features,
and is pretty powerful. But (you knew there was a but!), it's never been
stable for me on my 7100/80. If you turn off virtual memory, it will crash
a LOT less often, yet it will still crash sometimes. I never could figure
out why, and I was running MacsBug and providing detailed reports to the
author, but he was never able to find the problem to fix it correctly. Now,
I am running Apple's Personal Web Sharing 1.5 (don't laugh!) and it has
worked beautifully. It gets about the same speed or faster on web
transfers, it's easier to setup, and since it shows no real activity status
windows, I don't tend to think about it too much. This might be a weird
reason to like it... but, you'd have to understand my studying habits. :)
Also note that a lot of problems in QPQ stem from bugs in how it handles CGI's.
> Frontier 5.0.1
> NetEvents 1.0.1
> 24-Meg RAM
> Virtual memory on (I know...)
> Lots of disk space
>
> My Mac: PowerMac 7300/200
> System 8.1
> Lots of RAM and disk space
^^^^^^^^^^^ <- consider turning off VM then... or at least,
don't use Quid Pro Quo.
> Lots of software junk my company requires
I've never crashed while running AutoShare because of AutoShare (i.e.,
other programs have made me crash). AutoShare Admin has never crashed,
either.
Oh, I just thought of one other thing... I used to run EIMS 1.2 and it did
cause me to crash every so often, too. I am currently running SIMS and it
has never crashed. It exhibits some odd behaviors now and then, but
otherwise it has worked fine for me. You can get more info at
<http://www.stalker.com/>.
-Jonathan {;-)
Visit <http://b62968.cwru.edu/> for a good laugh.
There are 3 kinds of people: Those who make things happen, those who watch
things happen and those who wonder what happened.
Date: Wed, 22 Apr 1998 21:43:18 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: AutoShare 2.2.1b4
Version 2.2.1b4 has been uploaded to
<ftp://ftp.dnai.com/users/m/meh/AutoShare/Beta/>
The default process time yielding friendliness of the server application is
by far the main reason that the Admin may seem slow. So I applied an
approach some time ago to deal with this, but have now implemented another
method.
2.2.1b4 cancels the approach of a zero tick value being activated when the
Admin is started and deactivated when it's shut down, as it's risky for
several reasons: 1. if the Admin somehow isn't shut down in a proper
fashion or is left running, the server hogs the processor too much on a
permanent basis, 2. the Admin will not shut down when the server is not
running.
The server application now uses the approach that one AppleEvent often
(e.g. with the Admin) is followed by another shortly afterwards; the zero
tick value is enforced for 30 seconds (look for an asterisk in the server's
status window's time since run line), then the normal tick value is used as
usual (unless another AppleEvent comes around).
Subject: Re: admin 2.2 error
Date: Thu, 23 Apr 98 14:52:42 -0500
From: Jeremy Weathers <jw at blowyouaway dot com>
Has anyone had a problem with the Admin 2.2 refusing to quit? I do key
commands, menu commands - eventually just have to force quit. This first
happened on a IIci running SSW 7.5.3, SIMS 1.6, NonSequitur 0.8 and
AutoShare 2.1. I had the FaceSpan extension installed with only necessary
ext.s for TCP/IP - OpenTransport, Ethernet, AppleScript, FileSharing,
AppleShare, Network, etc. On opening it again, nothing worked.
I then took it to my PowerBase 180 and used the built-in-extension
version. The 180 was running MacOS 8.1 with lots of demo and beta junk
installed, and exhibited the exact same thing - no quit. I had to force
quit it again.
Does anyone know what's going on here? I'd like to use AutoShare, but
can't even get it setup.
Jeremy Weathers
TwIN Media Group
Date: 23 Apr 98 15:16:53 -0500
From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us>
Subject: Re: admin 2.2 error
At one point I had a similar problem. Autoshre Admin would start and I =
couldn't do anything with it and it wouldn't quit. I found that if I =
started Autoshare and did the basic setup from there and *then* ran the =
Admin to do the rest of the work the problems went away. =
BTW, you did have Autoshare running when your ran the Admin didn't you? =
If you start Autoshare 1st that also seems to help.
I don't know that these are the solutions, but perhaps they'll help.
Chuck Boody
Analyst/Programmer
ISD 270
=============
Jeremy Weathers wrote:
>Has anyone had a problem with the Admin 2.2 refusing to quit? I do key =
>commands, menu commands - eventually just have to force quit. This first =
>happened on a IIci running SSW 7.5.3, SIMS 1.6, NonSequitur 0.8 and =
>AutoShare 2.1. I had the FaceSpan extension installed with only necessary =
>ext.s for TCP/IP - OpenTransport, Ethernet, AppleScript, FileSharing, =
>AppleShare, Network, etc. On opening it again, nothing worked.
>
>I then took it to my PowerBase 180 and used the built-in-extension =
>version. The 180 was running MacOS 8.1 with lots of demo and beta junk =
>installed, and exhibited the exact same thing - no quit. I had to force =
>quit it again.
>
>Does anyone know what's going on here? I'd like to use AutoShare, but =
>can't even get it setup.
>
>Jeremy Weathers
>TwIN Media Group
>
>** The AutoShare-Talk archives are at:
>** <http://frutiger.staffs.ac.uk/autoshare/archives/AutoShare-Talk/>
>
>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.0); Thu, 23 Apr 1998 14:59:26 -0500
>Received: from blowyouaway.com (207.50.62.201) by frutiger.staffs.ac.uk =
with
> SMTP (Eudora Internet Mail Server 2.1); Thu, 23 Apr 1998 20:53:19 +0100
>Received: from [207.50.62.16] ([207.50.62.16] verified) by blowyouaway.=
com =
>(Stalker SMTP Server 1.6) with SMTP id S.0000007485 for =
><AutoShare-Talk at frutiger.staffs.ac dot uk>; Thu, 23 Apr 1998 14:52:59 -0500
>Subject: Re: admin 2.2 error
>Date: Thu, 23 Apr 98 14:52:42 -0500
>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)
>X-Sender: jw at tnt.blowyouaway dot com
>Precedence: bulk
>List-Subscribe: <mailto:autoshare-talk-on at frutiger.staffs.ac dot uk>
>List-Unsubscribe: <mailto:autoshare-talk-off at frutiger.staffs.ac dot uk>
>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 2.2.1b4 by Mikael Hansen
>X-To-Unsubscribe: autoshare at frutiger.staffs.ac dot uk, body: unsub AutoShare-=
Talk
>x-sender: jw at tnt.blowyouaway dot com
>x-mailer: Claris Emailer 1.1
>From: Jeremy Weathers <jw at blowyouaway dot com>
>To: AutoShare-Talk at frutiger.staffs.ac dot uk (Subscribers of AutoShare-Talk)
>Mime-Version: 1.0
>Content-Type: text/plain; charset="US-ASCII"
>Message-Id: <908001967208267610741 at frutiger.staffs.ac dot uk>
>
Date: Thu, 23 Apr 1998 18:37:49 -0400
From: Jonathan Shaw <jls4 at cwru dot edu>
Subject: Re: admin 2.2 error
>Has anyone had a problem with the Admin 2.2 refusing to quit? I do key
>commands, menu commands - eventually just have to force quit. This first
>happened on a IIci running SSW 7.5.3, SIMS 1.6, NonSequitur 0.8 and
>AutoShare 2.1. I had the FaceSpan extension installed with only necessary
>ext.s for TCP/IP - OpenTransport, Ethernet, AppleScript, FileSharing,
>AppleShare, Network, etc. On opening it again, nothing worked.
>
>I then took it to my PowerBase 180 and used the built-in-extension
>version. The 180 was running MacOS 8.1 with lots of demo and beta junk
>installed, and exhibited the exact same thing - no quit. I had to force
>quit it again.
>
>Does anyone know what's going on here? I'd like to use AutoShare, but
>can't even get it setup.
>
>Jeremy Weathers
>TwIN Media Group
>
>** The AutoShare-Talk archives are at:
>** <http://frutiger.staffs.ac.uk/autoshare/archives/AutoShare-Talk/>
Make sure you are using the latest version of the Admin and AutoShare. I
don't believe there is a version number associated with the admin... the
file size is 320,550 bytes, though. The latest AutoShare download is
2.2.1b4, and it includes a copy of the admin in it.
<ftp://ftp.dnai.com/users/m/meh/AutoShare/Beta/>
Previously, the AutoShare admin would tell AutoShare to set its tick level
to 0 (right?) and then when you quit the admin, it undoes this change.
However, one bug was that if the AutoShare application was quit before the
Admin is quit, then the admin can't communicate with the app to tell it to
change the value--and this communication was linked into the Quit menu
option. So, you can't quit while the AutoShare app is not running. The
current release fixes this problem.
Of course, I could be totally far off from your problem, though! It also
seems like AutoShare creates certain folders/files during its startup
procedure. So, you might try quitting AutoShare and then relaunching it if
funny stuff starts happening. This seems mostly related to when you create
a new list. It doesn't create the archive folder until restarting AutoShare
(apparently). I don't think this should affect the admin program, though.
-Jonathan {;-)
Visit <http://b62968.cwru.edu/> for a good laugh.
There are 3 kinds of people: Those who make things happen, those who watch
things happen and those who wonder what happened.
Date: Fri, 24 Apr 1998 14:35:28 -0500
From: "Richard Petty" <rwvr90 at email.sps.mot dot com>
Subject: AutoShare Crashy? Only AutoShare.
> Date: Wed, 22 Apr 1998 20:26:55 -0400
> From: Jonathan Shaw <jls4 at cwru dot edu>
> Subject: Re: AutoShare Crashy?
>
> > Server: PowerMac 7200/75
> > System 8.1
> > AutoShare 2.1
> > EIMS 1.2
> > QPQ 2.1
> ^^^^^^^
> I've used QPQ within the last few months... It has a lot of nice features,
> and is pretty powerful. But (you knew there was a but!), it's never been
> stable for me on my 7100/80. If you turn off virtual memory, it will crash
> a LOT less often, yet it will still crash sometimes. I never could figure
> out why, and I was running MacsBug and providing detailed reports to the
> author, but he was never able to find the problem to fix it correctly. Now,
> I am running Apple's Personal Web Sharing 1.5 (don't laugh!) and it has
> worked beautifully. It gets about the same speed or faster on web
> transfers, it's easier to setup, and since it shows no real activity status
> windows, I don't tend to think about it too much. This might be a weird
> reason to like it... but, you'd have to understand my studying habits. :)
>
> Also note that a lot of problems in QPQ stem from bugs in how it handles CGI's.
>
> > Frontier 5.0.1
> > NetEvents 1.0.1
> > 24-Meg RAM
> > Virtual memory on (I know...)
> > Lots of disk space
> >
> > My Mac: PowerMac 7300/200
> > System 8.1
> > Lots of RAM and disk space
> ^^^^^^^^^^^ <- consider turning off VM then... or at least,
> don't use Quid Pro Quo.
>
> > Lots of software junk my company requires
>
> I've never crashed while running AutoShare because of AutoShare (i.e.,
> other programs have made me crash). AutoShare Admin has never crashed,
> either.
>
> Oh, I just thought of one other thing... I used to run EIMS 1.2 and it did
> cause me to crash every so often, too. I am currently running SIMS and it
> has never crashed. It exhibits some odd behaviors now and then, but
> otherwise it has worked fine for me. You can get more info at
> <http://www.stalker.com/>.
I just upgraded to AutoShare 2.2 and it locked up again (menus quit working,
no list processing, etc.)
Every single other app is fine. Great.
THIS is why I'm worried about AutoShare and not QPQ or EIMS. They are fine
(and always have been.)
This is embarrassing because I've got a manager whose had me compose an
announcement for our quarterly newletter and now I've got to say, "Hold on...!"
I'm sure other people have had no problems, but I'm now on my third lockup and
some of my superiors are starting to question my judgement.
Any further suggestions would be appreciated.
--Richard
Date: Fri, 24 Apr 1998 13:06:04 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: AutoShare Crashy? Only AutoShare.
At 14:35 -0500 24/4/1998, Richard Petty wrote:
>I just upgraded to AutoShare 2.2 and it locked up again (menus quit working,
>no list processing, etc.)
There's never just AutoShare. There are also the MacOS and various types of
extensions. Try with extensions off first (shift key down while booting).
I have a 7500 at home, which is close to your 7200. And I can safely say
that I cannot reproduce your situation.
Date: Fri, 24 Apr 1998 16:20:21 -0500
From: "Richard Petty" <rwvr90 at email.sps.mot dot com>
Subject: Attachments Crashing AutoShare?
Mikael Hansen wrote:
>
> At 14:35 -0500 24/4/1998, Richard Petty wrote:
>
> >I just upgraded to AutoShare 2.2 and it locked up again (menus quit working,
> >no list processing, etc.)
>
> There's never just AutoShare. There are also the MacOS and various types of
> extensions. Try with extensions off first (shift key down while booting).
>
> I have a 7500 at home, which is close to your 7200. And I can safely say
> that I cannot reproduce your situation.
Okay, point taken. I have to set aside another 90-minute round trip in
hostile traffic to perform the investigation.
The deal is that it doesn't lock up immediately. If fact, if no messages are
send to AutoShare it'll run forever. I sent some "set" commands and things
seem to go fine.
I may have identified the event that precipitated the lockup: sent a list
message with a file attachment (a GIF file sent by a Netscape Communicator client).
The pilot list recipients said they did recieve the message with the
attachment just fine. I realized that I didn't get it because ack was off so
I sent a command to turn it back on and was going to re-send. Nothing
happened. I sent more commands. Lockup.
Are these clues valueable?
--Richard
Date: Fri, 24 Apr 1998 14:50:18 -0700
From: Camelot Administrator <camelot.admin at lmco dot com>
Subject: Re: AutoShare Crashy? Only AutoShare.
At 2:35 PM -0500 on 4/24/98, Richard Petty wrote:
>
> I just upgraded to AutoShare 2.2 and it locked up again (menus quit working,
> no list processing, etc.)
>
> Every single other app is fine. Great.
>
> THIS is why I'm worried about AutoShare and not QPQ or EIMS. They are fine
> (and always have been.)
>
>
> This is embarrassing because I've got a manager whose had me compose an
> announcement for our quarterly newletter and now I've got to say, "Hold
>on...!"
>
>
> I'm sure other people have had no problems, but I'm now on my third
>lockup and
> some of my superiors are starting to question my judgement.
>
> Any further suggestions would be appreciated.
>
For better or worse, I wanted to point out that our server is:
PowerMac 7200/90
OS 8.1
EIMS 1.2
Autoshare 2.2
It has never once crashed. Not once. It's been running for 2 years (I
always upgrade when new Autoshare comes out, and I've never had a problem).
The only problems I've had were related to questions on how to do certain
things, and the occasional bug/snare (but those have never shutdown the
server or the system... more related to admin duties).
Given the similarities between our systems, I would hazard a guess that the
problem is not with the software, but with the configuration. Perhaps
carefully going through the configuration of the EIMS accounts and the
Autoshare lists might help.
Regards,
Bill
+----------------------------------------------------------------+
| Bill Catambay, Software Developer, Webmaster |
| Lockheed Martin, Enterprise Information Systems, Sunnyvale, CA |
| WORK -> mailto:bill.m.catambay at lmco dot com |
| HOME -> mailto:bill at catambay dot com |
| |
| Pascal Central -> http://www.catambay.com/pascal-central |
| Macintosh Guild -> http://www.rahul.net/rrk/lmms/mac |
+----------------------------------------------------------------+
Date: Fri, 24 Apr 1998 19:41:01 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: In need of 68K testers!
Once in a blue moon, I upload a development version to test a very specific
issue. This time, 2.2.1b5d068K has been uploaded to
<ftp://ftp.dnai.com/users/m/meh/AutoShare/Beta/>
as I think the 68K CWPro dilemma may have been resolved. If you start it up
on a 68K Mac and the start-up completes, then all is fine. Please let me
know, either on the list or directly to my e-mail address. Please specify
your type of Mac, if you don't mind. Thank you!
PS: the official crash/freeze count doesn't apply here :-)
Date: Sun, 26 Apr 1998 21:35:08 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: AutoShare 2.3b5
Version 2.3b5 has been uploaded to
<ftp://ftp.dnai.com/users/m/meh/AutoShare/Beta/>
As a minor version would generally contain bug fixes only, 2.2.1 has been
renamed to 2.3, mostly due to the "unknown accounts" feature.
I may finally have been able to track down what appears to be a CWPro bug
in compiling 68K code, often affecting start-ups on 68K Macs. If all is
well, the CW11 68K version will soon no longer be included. Thanks to James
in particular for his unlimited patience.
The issue of bounces occasionally slipping by the preliminary processing
and thereby being treated as regular messages when configured in
conjunction with the "unknown address" feature, as noted by Jonathan, is an
area where I have implemented various enhancements. More may be needed.
Thanks here too.
The log total for test bounces has been clarified by being divided into two
categories; one is the count for test bounce batches being mailed while the
other is a new count category for individual test bounces. It is
recommended that you clear your logs (Command-T, "now") before upgrading.
Counts of zero now default to not being listed. You can have all totals
listed regardless of their values by adding the letter i in Misc Stuff
(Command-J in the Admin).
Some other improvements have been taken care of as well.
Date: Mon, 27 Apr 1998 02:09:57 -0400
From: Jonathan Shaw <jls4 at cwru dot edu>
Subject: Feature Suggestion: listname-info
Hi! I was just thinking that it'd be cool if AutoShare handled
listname-info requests as being equal to writing autoshare@ with "info
listname" in the body. Not such a huge deal since implementing
listname-info is currently done using the auto responder feature... but it
would simplify file hierarchy just a tiny little bit. :)
-Jonathan {;-)
Visit <http://b62968.cwru.edu/> for a good laugh.
There are 3 kinds of people: Those who make things happen, those who watch
things happen and those who wonder what happened.
Date: Mon, 27 Apr 1998 12:14:55 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Feature Suggestion: listname-info
At 02:09 -0400 27/4/1998, Jonathan Shaw wrote:
>Hi! I was just thinking that it'd be cool if AutoShare handled
>listname-info requests as being equal to writing autoshare@ with
>"info listname" in the body.
As info is not a command per se, I may even want to take it a step further
by simply applying the more general <list>-<command>@ scheme, which would
work for any given command (list, release...) or "command" (info, help...)
as long as there are no parameters involved. What do you think of that?
Date: Mon, 27 Apr 1998 16:04:27 -0400
From: Jonathan Shaw <jls4 at cwru dot edu>
Subject: Re: Feature Suggestion: listname-info
>At 02:09 -0400 27/4/1998, Jonathan Shaw wrote:
>>Hi! I was just thinking that it'd be cool if AutoShare handled
>>listname-info requests as being equal to writing autoshare@ with
>>"info listname" in the body.
>As info is not a command per se, I may even want to take it a step further
>by simply applying the more general <list>-<command>@ scheme, which would
>work for any given command (list, release...) or "command" (info, help...)
>as long as there are no parameters involved. What do you think of that?
Sounds cool to me! :) I suspected you would do that. :)
-Jonathan {;-)
Visit <http://b62968.cwru.edu/> for a good laugh.
There are 3 kinds of people: Those who make things happen, those who watch
things happen and those who wonder what happened.
Date: 27 Apr 98 16:39:44 -0500
From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us>
Subject: Re: Feature Suggestion: listname-info
I like it.
Chuck Boody
ISD 270
=============
Mikael Hansen wrote:
>At 02:09 -0400 27/4/1998, Jonathan Shaw wrote:
>
>>Hi! I was just thinking that it'd be cool if AutoShare handled
>>listname-info requests as being equal to writing autoshare@ with
>>"info listname" in the body.
>
>As info is not a command per se, I may even want to take it a step =
further
>by simply applying the more general <list>-<command>@ scheme, which would
>work for any given command (list, release...) or "command" (info, help...)=
>as long as there are no parameters involved. What do you think of that?
>
>** The AutoShare-Talk archives are at:
>** <http://frutiger.staffs.ac.uk/autoshare/archives/AutoShare-Talk/>
>
>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.0); Mon, 27 Apr 1998 14:23:07 -0500
>Received: from hopf.dnai.com (140.174.162.10) by frutiger.staffs.ac.uk =
with
> ESMTP (Eudora Internet Mail Server 2.1); Mon, 27 Apr 1998 20:17:10 +0100
>Received: from [207.181.206.52] (dnai-207-181-206-31.dialup.dnai.com =
>[207.181.206.31])
> by hopf.dnai.com (8.8.7/8.8.7) with ESMTP id MAA08690
> for <autoshare-talk at frutiger.staffs.ac dot uk>; Mon, 27 Apr 1998 12:16:02 =
>-0700 (PDT)
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>X-Sender: meh at pop.dnai dot com
>In-Reply-To: <299536415958936892472 at frutiger.staffs.ac dot uk>
>Date: Mon, 27 Apr 1998 12:14:55 -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-talk-on at frutiger.staffs.ac dot uk>
>List-Unsubscribe: <mailto:autoshare-talk-off at frutiger.staffs.ac dot uk>
>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 2.3b6d0 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: Feature Suggestion: listname-info
>Message-Id: <709578958585885397325 at frutiger.staffs.ac dot uk>
>
Date: Tue, 28 Apr 1998 14:25:44 -0800
From: Milo Sharp <milo at polarnet dot com>
Subject: Re: Feature Suggestion: listname-info
>Date: Mon, 27 Apr 1998 12:14:55 -0700
>From: Mikael Hansen <meh at dnai dot com>
>Subject: Re: Feature Suggestion: listname-info
>
>At 02:09 -0400 27/4/1998, Jonathan Shaw wrote:
>
>>Hi! I was just thinking that it'd be cool if AutoShare handled
>>listname-info requests as being equal to writing autoshare@ with
>>"info listname" in the body.
>
>As info is not a command per se, I may even want to take it a step further
>by simply applying the more general <list>-<command>@ scheme, which would
>work for any given command (list, release...) or "command" (info, help...)
>as long as there are no parameters involved. What do you think of that?
I'd say, make it an option, if so, since I'll soon be using
Autoshare to run a mailing list called arctic-info. It does sound like a
good idea, though, and I'd love to use arctic-info-subscribe to handle
subscriptions. If you can get arctic-info to be a list (if configured as
such) and arctic-info-<command> to work, I'd be very happy to see this
feature added.
Milo Sharp
Technical Assistant, ARCUS
Email: milo at polarnet dot com
Phone: 907/474-1602
Fax: 907/474-1604
Date: Wed, 29 Apr 1998 00:22:48 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: 2.3b6. (was Feature Suggestion: listname-info)
At 02:09 -0400 27/4/1998, Jonathan Shaw wrote:
>Hi! I was just thinking that it'd be cool if AutoShare handled
>listname-info requests as being equal to writing autoshare@ with
>"info listname" in the body.
At 12:14 -0700 27/4/1998, Mikael Hansen wrote:
>As info is not a command per se, I may even want to take it a step further
>by simply applying the more general <list>-<command>@ scheme, which would
>work for any given command (list, release...) or "command" (info, help...)
>as long as there are no parameters involved. What do you think of that?
At 16:04 -0400 27/4/1998, Jonathan Shaw wrote:
>Sounds cool to me! :) I suspected you would do that. :)
At 16:39 -0500 27/4/1998, Chuck Boody wrote:
>I like it.
At 14:25 -0800 28/4/1998, Milo Sharp wrote:
> I'd say, make it an option, if so, since I'll soon be using
>Autoshare to run a mailing list called arctic-info. It does sound like a
>good idea, though, and I'd love to use arctic-info-subscribe to handle
>subscriptions. If you can get arctic-info to be a list (if configured as
>such) and arctic-info-<command> to work, I'd be very happy to see this
>feature added.
Okay, folks. It's in 2.3b6 at
<ftp://ftp.dnai.com/users/m/meh/AutoShare/Beta/>
Date: Wed, 29 Apr 1998 00:01:45 -0500
From: Richard Petty <repetty at swbell dot net>
Subject: Got it Working -- I Think.
I finally got AutoShare running reliably on my server -- I think.
I'm not sure exactly what I did that fixed it, but here's my list:
1. Ran Norton (no problems).
2. Turned off virtual memory.
3. Turned off Frontier, Vremya, QPQ, NetEvents.
4. Disabled IdleTime INIT.
5. Disabled a couple Apple Extensions.
System software-wise, it was a lean machine already.
The cost of success was high: I sure had to sacrifice a lot of=
functionality to get it going.
I spent all day today in a closet sitting in front of the server. =
Previously, AutoShare would lock up on large file enclosures. Closer=
inspection, though, revealed something else: I could hear the drive=
accessing. I watched one of the Finder windows and saw the disk free space=
changing.
Just like before, menus refused to respond. I couldn't quit AutoShare. =
Finally, after over thirty-minutes, everything returned to normal.
I know sending attachments to listservers is generally considered a Bad=
Thing, but in my case it's necessary. Indeed, delivering Virex filters=
regularly will be one of it's main tasks.
I studied AutoShare as it processed my attachments, studied the Finder,=
and studied EIMS. It appears that the attachments may have been copied=
over and over again for each recipient (several megabytes of disk space=
disappeared and returned).
If I want to send a 600K attachment to 100 people, what can I expect to=
happen? Do I need 60-Meg of disk space?
Is SIMS an alternative?
TIA,
--Richard
Date: Wed, 29 Apr 1998 04:25:37 -0400
From: Jonathan Shaw <jls4 at cwru dot edu>
Subject: Re: Got it Working -- I Think.
> Just like before, menus refused to respond. I couldn't quit AutoShare.
>Finally, after over thirty-minutes, everything returned to normal.
AutoShare will take some time to process your attachment, but not 30
minutes for a file so small. This 30 minutes is actually your mail server
queueing up and perhaps partially sending the file to all the various
recipients. See below for ways to speed that up...
> I studied AutoShare as it processed my attachments, studied the Finder,
>and studied EIMS. It appears that the attachments may have been copied
>over and over again for each recipient (several megabytes of disk space
>disappeared and returned).
Yes, this is what is happening--but this is a function of your mail server,
not AutoShare.
> If I want to send a 600K attachment to 100 people, what can I expect to
>happen? Do I need 60-Meg of disk space?
Yes, if you are using EIMS 1.x. Perhaps if you are using EIMS 2.x, but it
depends on your recipient's mail hosts (how many unique ones).
> Is SIMS an alternative?
Interesting problem you've run into! Yes, SIMS would be a very good
alternative for your particular usage. It will store only a single copy of
the outgoing message, with a list of recipients maintained above the
message by SIMS (but stored as plain text). With EIMS 1.x, you will require
about 60 megs of space, like you said. Keep in mind though, that a 600k
file attachment is really going to balloon in size to about 750-800k when
you send it through your mail program (it will be converted to a text
representation of the binary data). So, you'd actually need about 75 or 80
megs of space with EIMS 1.x.
EIMS 2.x (is commercial) and handles the outgoing message queue much, much
better than 1.x. It will store one copy of the outgoing message for each
domain it will deliver to. If all of your recipients are at one mail host,
then this will significantly reduce your space requirements. Still, though,
SIMS will be more efficient (and faster for this particular use).
If you need help setting up SIMS with AutoShare, let us know. I highly
recommend Mikael's new feature that takes advantage of your mail server's
"unknown" address forwarding. It makes setting up SIMS for AS much quicker.
You should get the latest version of AutoShare to take advantage of this,
though.
-Jonathan {;-)
Visit <http://b62968.cwru.edu/> for a good laugh.
There are 3 kinds of people: Those who make things happen, those who watch
things happen and those who wonder what happened.
Date: Wed, 29 Apr 1998 01:21:58 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Got it Working -- I Think.
At 00:01 -0500 29/4/1998, Richard Petty wrote:
> The cost of success was high: I sure had to sacrifice a lot of
>functionality to get it going.
Probably not. It is most likely just one particular thing. It's a
time-consuming task to figure out such conflicts as you have to take it
from scratch and slowly build it all up again, but it usually works :-)
> I spent all day today in a closet sitting in front of the server.
>Previously, AutoShare would lock up on large file enclosures. Closer
>inspection, though, revealed something else: I could hear the drive
>accessing. I watched one of the Finder windows and saw the disk free
>space changing.
My tests show that a MIME list contribution with a 122K enclosure takes
around 40 seconds without the system clock display skipping seconds. This
is not fast, but it works. Auto-response enclosures are a lot faster, as a
request returning a 1.5MB file takes less than 10 seconds.
> I studied AutoShare as it processed my attachments, studied the Finder,
>and studied EIMS. It appears that the attachments may have been copied
>over and over again for each recipient (several megabytes of disk space
>disappeared and returned).
AutoShare hands over just one message with one enclosure to the mail
server. You are most likely referring to the doing of the mail server. I
highly suggest that you upgrade from EIMS 1.2 :-)
Date: 29 Apr 98 08:28:11 -0500
From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us>
Subject: RE: Got it Working -- I Think.
I think, unfortunately, that POP3 servers will always place one copy of an =
enclosure for each person it is sent to on the server. At least that is =
the case with those I have examined. Any you are correct that you would =
need the 60 Meg of disk space and that AIMS will choke a bit delivering =
the enclosures. The 2.x versions seem much better about this than the 1.x =
ones though. Post a note to the EIMS list and Glenn (AIMS-EIMS programmer)=
can discuss this further.
The choke is not an Autoshare problem, though here is a suggestion about =
how Autoshare could help you with it:
1) Set up a mailback account to deliver the enclosures in question.
2) Mail notice about the availability of each enclosure set up so that a =
replay will automatically get the enclosure mailed to the person. This =
might take a bit of thought, but I believe it could be done. Then the =
system will handle creation of individual's copy of the enclosure when =
they reply rather than handling all of the people on the listserv at once. =
That should spread out the load and remove the slowdown when AIIMS =
attempts to make those 60 copies of the 600k file.
Chuck Boody
Analyst/Programmer
ISD 270
=============
Richard Petty wrote:
>
> I finally got AutoShare running reliably on my server -- I think.
>
> I'm not sure exactly what I did that fixed it, but here's my list:
>
> 1. Ran Norton (no problems).
> 2. Turned off virtual memory.
> 3. Turned off Frontier, Vremya, QPQ, NetEvents.
> 4. Disabled IdleTime INIT.
> 5. Disabled a couple Apple Extensions.
>
> System software-wise, it was a lean machine already.
>
> The cost of success was high: I sure had to sacrifice a lot of =
>functionality to get it going.
>
> I spent all day today in a closet sitting in front of the server. =
>Previously, AutoShare would lock up on large file enclosures. Closer =
inspection, =
>though, revealed something else: I could hear the drive accessing. I =
watched one of =
>the Finder windows and saw the disk free space changing.
>
> Just like before, menus refused to respond. I couldn't quit AutoShare. =
>Finally, after over thirty-minutes, everything returned to normal.
>
> I know sending attachments to listservers is generally considered a Bad =
>Thing, but in my case it's necessary. Indeed, delivering Virex filters =
regularly =
>will be one of it's main tasks.
>
> I studied AutoShare as it processed my attachments, studied the Finder, =
>and studied EIMS. It appears that the attachments may have been copied =
over and =
>over again for each recipient (several megabytes of disk space =
disappeared and =
>returned).
>
> If I want to send a 600K attachment to 100 people, what can I expect to =
>happen? Do I need 60-Meg of disk space?
>
> Is SIMS an alternative?
>
> TIA,
>
>--Richard
>
>
Date: Wed, 29 Apr 1998 20:14:58 -0400
From: Jonathan Shaw <jls4 at cwru dot edu>
Subject: more feature requests! :)
I was just thinking about the protected address feature--this too can be
incorporated into the new Unknown address analysis. If I mail
<1323763089 at b62968.cwru dot edu> I would be sending mail which AutoShare would
reroute to the corresponding protected recipient. That would be so cool!
Don't forget about the mailback confirmation uses... Mailback confirmations
could generate random addresses just like the protected addresses, except
in this case the mailback confirmation is arriving from
<1322985089 at b62968.cwru dot edu>! So the user just hits reply, and their
request is confirmed. You wouldn't believe how many people screw this
process up right now! Some don't put the code on the first line or add tabs
before it, etc. I get lots of mails sent to <bouncer at b62968.cwru dot edu> that
should have been sent to <autoshare at b62968.cwru dot edu>. Either they are
manually typing that in, or their mail client doesn't pay attention to the
reply-to: header. If the mail came from some random address (that autoshare
records), then this would be much easier.
One other thing, sort of related, sort of not related. :) Since the new
feature arrived (what do you name that feature, btw?), I can no longer
setup multiple addresses that refer to the same autoshare server. I used to
use the SIMS router to route addresses like macjordomo, majordomo, and
listserv to the autoshare account. That "feature" (not really a feature,
but it worked!) broke with the new unknown forwarding thing. Instinct might
say that creating aliases of the AutoShare folder (in Docs folder) and
renaming the aliases to majordomo, etc. would work--but it doesn't.
-Jonathan {;-)
Visit <http://b62968.cwru.edu/> for a good laugh.
There are 3 kinds of people: Those who make things happen, those who watch
things happen and those who wonder what happened.
Date: Wed, 29 Apr 1998 17:55:25 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Lists Not Working with Autoshare and EIMS 2.1
At 11:18 +0100 29/4/1998, Jerry Thompson wrote:
>Updated our email server to EIMS 2.1 on Monday. Email works fine. Nothing
>appears to have changed except some additional features to EIMS. However,
>send email to the lists results in the following:
Upgrading to AutoShare 2.2 takes care of that.
Date: Wed, 29 Apr 1998 21:48:53 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: more feature requests! :)
At 20:14 -0400 29/4/1998, Jonathan Shaw wrote:
>I was just thinking about the protected address feature
[...]
>Don't forget about the mailback confirmation uses
[...]
Wrong season, Jonathan! Al Nino finally permitted sunny weather in CA.
>One other thing, sort of related, sort of not related. :) Since the new
>feature arrived (what do you name that feature, btw?),
The unknown accounts feature. Or the unknown addresses feature.
>I can no longer setup multiple addresses that refer to the same autoshare
>server. I used to use the SIMS router to route addresses like macjordomo,
>majordomo, and listserv to the autoshare account. That "feature" (not really
>a feature, but it worked!) broke with the new unknown forwarding thing.
If you re-create the AutoShare account, does it work?
Date: Thu, 30 Apr 1998 01:39:58 -0400
From: Jonathan Shaw <jls4 at cwru dot edu>
Subject: Re: more feature requests! :)
>Wrong season, Jonathan! Al Nino finally permitted sunny weather in CA.
Who does he think he is, anyway? :)
>At 20:14 -0400 29/4/1998, Jonathan Shaw wrote:
>>I can no longer setup multiple addresses that refer to the same autoshare
>>server. I used to use the SIMS router to route addresses like macjordomo,
>>majordomo, and listserv to the autoshare account. That "feature" (not really
>>a feature, but it worked!) broke with the new unknown forwarding thing.
>If you re-create the AutoShare account, does it work?
Yes, it does! Thanks! I'm not sure why I didn't think of doing that. :)
-Jonathan {;-)
Visit <http://b62968.cwru.edu/> for a good laugh.
There are 3 kinds of people: Those who make things happen, those who watch
things happen and those who wonder what happened.
Date: Thu, 30 Apr 1998 11:43:36 +0100
From: Jerry Thompson <jthompson at directhit dot com>
Subject: Autoshare and Facespan...
Greetings,
Got Quicktime (and QT PowerPlug) installed but Autoshare Admin (2.2b6) is
still askign for the Facespan extension. Any solutions?
Jerry.
________________________________________________
Jerry Thompson jthompson at directhit dot com
MIS/Webmaster macguru at directhit dot com
NDPC/PP List Management
- "I have seen a glimpse of the future... It's name is Macintosh."
- "Off the keyboard, thru the router, over the bridge, nothing but net!"
Date: Thu, 30 Apr 1998 12:56:36 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Autoshare and Facespan...
At 11:43 +0100 30/4/1998, Jerry Thompson wrote:
>Got Quicktime (and QT PowerPlug) installed but Autoshare Admin (2.2b6) is
>still askign for the Facespan extension. Any solutions?
Did you check that the FaceSpan extension is 2.1?
Date: Thu, 30 Apr 1998 12:58:52 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: AutoShare 2.3 released
Hi all
The beta phase is over. Thanks for your feedback!
AutoShare 2.3 has been uploaded and is available from
<ftp://ftp.dnai.com/users/m/meh/AutoShare/>
The updated web pages have been uploaded as well.
Date: 30 Apr 98 15:44:41 -0500
From: Chuck Boody <chuck_boody at hopkins.k12.mn dot us>
Subject: RE: AutoShare 2.3 released
Go have a beer or whatever Mikael. You are a bit amazing. I can barely =
keep up with updating the software given the rate you produce it. You =
need some sun and sea breeze for a while. Thanks for all the hard work =
and wonderful improvements.
Chuck Boody
ISD 270
=============
Mikael Hansen wrote:
>Hi all
>
>The beta phase is over. Thanks for your feedback!
>
>AutoShare 2.3 has been uploaded and is available from
>
> <ftp://ftp.dnai.com/users/m/meh/AutoShare/>
>
>The updated web pages have been uploaded as well.
>
>** The AutoShare-Talk archives are at:
>** <http://frutiger.staffs.ac.uk/autoshare/archives/AutoShare-Talk/>
>
>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.1); Thu, 30 Apr 1998 15:08:27 -0500
>Received: from mercury.dnai.com (207.181.194.99) by frutiger.staffs.ac.uk =
with
> ESMTP (Eudora Internet Mail Server 2.1); Thu, 30 Apr 1998 20:58:35 +0100
>Received: from [207.181.206.11] (dnai-207-181-206-11.dialup.dnai.com =
>[207.181.206.11])
> by mercury.dnai.com (8.8.7/8.8.7) with ESMTP id MAA03507
> for <AutoShare-Talk at frutiger.staffs.ac dot uk>; Thu, 30 Apr 1998 12:58:33 =
>-0700 (PDT)
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>X-Sender: meh at pop.dnai dot com
>Date: Thu, 30 Apr 1998 12:58:52 -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-talk-on at frutiger.staffs.ac dot uk>
>List-Unsubscribe: <mailto:autoshare-talk-off at frutiger.staffs.ac dot uk>
>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 2.3 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: AutoShare 2.3 released
>Message-Id: <068802807953851715521 at frutiger.staffs.ac dot uk>
>
Date: Thu, 30 Apr 1998 12:49:40 +0100
From: Bill Bedford <billbpm at mousa.demon.co dot uk>
Subject: Problems with 2.3 betas
I down loaded 2.3b5 and 2.3b6 yesterday, but cannot get them to work. Files
in the 'filed mail' or 'bounce' folders aren't processed and just sit
there. I tried increrasing the memory partions, with no effect.
I'm using SIMS and macOS 8.1 if that makes a difference
2.2 works perfectly, Any ideas?
Date: Thu, 30 Apr 1998 18:15:19 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: RE: AutoShare 2.3 released
At 15:44 -0500 30/4/1998, Chuck Boody wrote:
>Go have a beer or whatever Mikael. You are a bit amazing. I can barely
>keep up with updating the software given the rate you produce it. You
>need some sun and sea breeze for a while. Thanks for all the hard work
>and wonderful improvements.
Thanks for the kind words :-)
Date: Thu, 30 Apr 1998 21:32:48 -0400
Subject: Re: AutoShare 2.3 released
From: "William J. Suarez" <wsuarez at wal.osicom dot com>
> 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.
--MS_Mac_OE_2976816768_312206_MIME_Part
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Mikael,
I know you haven't heard from me in a while but I've been hanging around.
Let me second Chuck's motion (and you've heard me say this before) that you
have put together a wonderful product and those of us that have come to rely
on it truly appreciate your hard work.
Best regards,
Bill Suarez
------------------------------------------------
William J. Suarez
wsuarez at wal.osicom dot com
----------
>From: Mikael Hansen <meh at dnai dot com>
>To: AutoShare-Talk at frutiger.staffs.ac dot uk (Subscribers of AutoShare-Talk)
>Subject: RE: AutoShare 2.3 released
>Date: Thu, Apr 30, 1998, 9:15 PM
>
>At 15:44 -0500 30/4/1998, Chuck Boody wrote:
>
>>Go have a beer or whatever Mikael. You are a bit amazing. I can barely
>>keep up with updating the software given the rate you produce it. You
>>need some sun and sea breeze for a while. Thanks for all the hard work
>>and wonderful improvements.
>
>Thanks for the kind words :-)
>
>** The AutoShare-Talk archives are at:
>** <http://frutiger.staffs.ac.uk/autoshare/archives/AutoShare-Talk/>
--MS_Mac_OE_2976816768_312206_MIME_Part
Content-type: text/html; charset="US-ASCII"
--MS_Mac_OE_2976816768_312206_MIME_Part--
Date: Thu, 30 Apr 1998 19:01:08 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: AutoShare 2.3 released
At 21:32 -0400 30/4/1998, William J. Suarez wrote:
>I know you haven't heard from me in a while but I've been hanging around.
>Let me second Chuck's motion (and you've heard me say this before) that
>you have put together a wonderful product and those of us that have come
>to rely on it truly appreciate your hard work.
Thanks :-) Glad to have you here!
Date: Fri, 01 May 1998 12:58:04 -0500
From: "Richard Petty" <rwvr90 at email.sps.mot dot com>
Subject: Line Format Option
In the "More Miscellaneous" window there is a field labeled "Line Format".
The default value for this field is 80.
I want infinite line lengths -- no wrapping at all.
What value do I enter here to accomplish this?
TIA,
--Richard
Date: Fri, 1 May 1998 11:23:05 -0500
From: Paul DuBois <paul at snake dot net>
Subject: EIMS 1.2.1b1 warning
Just got the EIMS 1.2.1b1 beta and started it up. A message came in
for one of my AutoShare lists, and AutoShare processed it, but EIMS
did nothing. I quit it, started EIMS 1.2 and it sent out the message
to the subscribers immediately.
I dunno what's different about EIMS 1.2.1b1 and I don't have much
inclination to try to figure it out, but it seems a little caution
is in order if you're now running an earlier EIMS.
--
Paul DuBois
paul at snake dot net
Home Page: http://www.primate.wisc.edu/people/dubois
Software: http://www.primate.wisc.edu/software
Date: Fri, 1 May 1998 16:47:15 +0100
From: Jerry Thompson <jthompson at directhit dot com>
Subject: Re: Lists Not Working with Autoshare and EIMS 2.1
>Subject: Re: Lists Not Working with Autoshare and EIMS 2.1
>
>At 11:18 +0100 29/4/1998, Jerry Thompson wrote:
>
>>Updated our email server to EIMS 2.1 on Monday. Email works fine. Nothing
>>appears to have changed except some additional features to EIMS. However,
>>send email to the lists results in the following:
>
>Upgrading to AutoShare 2.2 takes care of that.
Alas... the solution was my own lack of reading readmes. :-)
Jerry.
________________________________________________
Jerry Thompson jthompson at directhit dot com
MIS/Webmaster macguru at directhit dot com
NDPC/PP List Management
- "I have seen a glimpse of the future... It's name is Macintosh."
- "Off the keyboard, thru the router, over the bridge, nothing but net!"
Date: Fri, 1 May 1998 20:15:50 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: EIMS 1.2.1b1 warning
At 11:23 -0500 1/5/1998, Paul DuBois wrote:
>I dunno what's different about EIMS 1.2.1b1
Unlike earlier versions of EIMS, 2.x versions keep the Mail folder inside
the application folder. Perhaps that could be it?
Date: Fri, 1 May 1998 20:16:18 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: Line Format Option
At 12:58 -0500 1/5/1998, Richard Petty wrote:
>In the "More Miscellaneous" window there is a field labeled "Line Format".
>The default value for this field is 80.
>
> I want infinite line lengths -- no wrapping at all.
>
> What value do I enter here to accomplish this?
As paragraphs, whose limited size is generally determined by readability,
is terminated by a hard return, the value can be set at, say, a generous
10,000.
Date: Sat, 2 May 1998 00:59:15 -0500
From: Paul DuBois <paul at snake dot net>
Subject: Re: EIMS 1.2.1b1 warning
>At 11:23 -0500 1/5/1998, Paul DuBois wrote:
>
>>I dunno what's different about EIMS 1.2.1b1
>
>Unlike earlier versions of EIMS, 2.x versions keep the Mail folder inside
>the application folder. Perhaps that could be it?
But this wasn't 2.x, it was 1.2.x. I dunno, maybe 1.2.1b1 does the
same thing. That might explain why some of my other mail appeared
to get lost. I'll have to check when I get to work Monday.
--
Paul DuBois
paul at snake dot net
Home Page: http://www.primate.wisc.edu/people/dubois
Software: http://www.primate.wisc.edu/software
Date: Sat, 2 May 1998 11:56:47 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: EIMS 1.2.1b1 warning
At 00:59 -0500 2/5/1998, Paul DuBois wrote:
>>At 11:23 -0500 1/5/1998, Paul DuBois wrote:
>>
>>>I dunno what's different about EIMS 1.2.1b1
>>
>>Unlike earlier versions of EIMS, 2.x versions keep the Mail folder inside
>>the application folder. Perhaps that could be it?
>
>But this wasn't 2.x, it was 1.2.x.
I was confused. You are correct on both accounts: it really is a 1.2.x
beta, and the file really just sits there in the old Incoming Mail folder.
I have Cc'ed Glenn.
Date: Mon, 4 May 1998 23:33:22 -0700
From: Mikael Hansen <meh at dnai dot com>
Subject: Re: EIMS 1.2.1b1 warning
At 11:56 -0700 2/5/1998, Mikael Hansen wrote:
>it really is a 1.2.x beta, and the file really just sits there in the
>old Incoming Mail folder. I have Cc'ed Glenn.
1.2.1b2 has now been uploaded to <http://www.eudora.com/betas/>.
Date: Tue, 5 May 1998 10:40:16 +0100
From: Jochen Haeberle <joh at MIDRAS dot de>
Subject: Problems getting first list to work
Hi,
sorry for the ignorance but I am totally stuck with no way out.
I am trying to get EIMS 2.1, AutoShare 2.3 and MailBurst 2.0.3 to work
together. The last part I am working on is AutoShare.
I worked my way through the quick tutorial. The AutoReply does work but the
Listserver account AutoShare does not.
When I quit AutoShare, I can see that the mail is put into the Filed Mail
Folder correctly. When starting AutoShare, the file vanishes but nothing
happens. AutoShare not even mentions processing it.
What am I doing wrong?
Regards
Jochen