..
..
Clarence
1. Your strategy is excellent ... that is, copy over
new versions of various Arachne components, until the
@FILE mechanism starts to work again. At that point,
the last copied components was the cause of the problem.
2. I'll advise of my progres.
3. By the way, there actually was a report "syntax
error". It displayed for a micro-second after all the
RCPT errors and was visible ... despite my drug-induced
haze. The haze is never a problem, because I'm used
to it after these many years.
Ross Virgin
Toronto, Ontario
..
..
..
On Sat, 12 May 2001 23:35:09 -0400, Clarence Verge wrote:
> On Sat, 12 May 2001 22:32:39 +0000, Ross Virgin wrote:
>> 3. The error message is actually being reported, within
>> Arachne, at the bottom of the Arachne screen, on the
>> "progress reporting line" (if that is what the bottom line
>> might be called.
>> The "progress reporting line" starts reporting that Arachne
>> has linked to the SMTP server with the following series of
>> statements on the "progress reporting line". Some of these
>> lines include (something else) because the statements change
>> so fast, just flashing for a second, that it is impossible
>> to fully read some of them:
>> Copyright (c) 1996-2000 Michael Polak, Arachne Labs
>> processing form
>> asking domain (and something else)
>> connecting to SMTP (port 25)
>> HELO (and something else)
>> RCPT TO: <(null)>
>> RCPT TO: <(null)>
>> RCPT TO: <(null)>
>> RCPT TO: <(null)>
>> 4. The "RCPT TO: <(null)>" repeats and repeats, very rapidly,
>> until I exit/crash Arachne. Otherwise, it would continue in
>> that loop forever.
> Hello Ross;
> My original suggestion that it was a DOS error message was due to you
> reporting a message like: "Syntax error".
> I have searched core.exe and insight.exe for both A1.66 and A1.70 and
> find there is no message similar to this in either. It was DOSlike tho.
> I will assume now that that message never appeared except in a drug
> induced haze, <G> and offer a couple of suggestions based on the
> above.
> 1) Something has gone wrong with your "@" files - possibly something
> invisible to your current text editor. In place of <(null)> above,
> you should be seeing sequential recipients I'm guessing.
> 2) Something has happened to Insight and it isn't actually looking at
> the "@"file. Copy over a new version.
> 3) Something could have changed at your email provider. Try a different
> one temporarily.
> Good luck.
> - Clarence Verge
> - Back to using Arachne V1.62 ....
-- Arachne V1.66, NON-COMMERCIAL copy, http://arachne.cz/
