Bernie,
Someone else suggested that also. <G>
What I'm going to do is set up a separate profile, and have it run
smtp.log ...
It was only because I was running smtp.log that I discovered my ISP had
arbitrarily -- without bothering to tell paying customers -- set Apache
to refuse all addresses past 35 on a mailing list. I consider that less
than professional -- the failure to tell paying clients of the
limitation -- and nefrarious. So what I'll do is set to not log on my
main profile, and on the new profile, which I'll use when I'm sending
out the newsletters, I'll keep the smtp.log activated. I don't like
being considered inconsiderate or "out of business" because of any
changes the ISP might again make in mailing list handling on the server.
l.d.
====
On Wed, 18 Oct 2000 11:02:12 +0200 (CEST), Bernie <[EMAIL PROTECTED]> wrote:
>> After running parallel for about a week, I switched over to running 1.66
>> full time. While running parallel 1.66 was on a different physical HDD
>> than 1.64; the problems with lost sectors and loose chains -- most of
>> which were connected in one way or another with smtp.log information --
>> continue to make their presense felt.
> I *am* looking into this, I'm not quite finished yet but I hope to be so
> any day so I can send Michael the changes. In the mean time why not just
> stop using the smtp.log feature?
-- Arachne V1.66, NON-COMMERCIAL copy, http://arachne.cz/
