L.D wrote:
> Not necessarily. Both call upon InSight to read the message; the
>problem occurs *before* that point. The problem is that Arachne cannot
>find the *.mes file and "forward" it on to InSight for processing.
I haven't paid attention, those the problem lie in:
1. Viewing a mail
2. Creating the index
I think you mean the later one. But despite that we are back to the fact
that InSight can't find the mail.
Are you using:
1. Fixed directory entries
2. Very long directory entries
Number 2 could result in that the file that Arachne wants to read from the
cache directory can't be read. I still haven't come up with a good
sollution for this well known problem.
> I didn't think it would make a difference, since I never get this far.
><G> For that line to have any effect Arachne must have found the file
>12345678.mes ... it doesn't. So changing minimum memory requirements
>[which I met anyway] didn't change the software's response.
No, for that line to have effect you need to somehow "get" to a file such
as 12345678.mes. There are several ways to do this.
Arachne (I assume we are talking about core.exe) never reads that file,
InSight does. However when you read/write/send/fetch mail you do it in
Arachne (core.exe). Insight handles converting attachments, creating HTML
files out of mails and making HTML indexes that are then processed by
Arachne (core.exe).
It really seems this above (although edited) needs to go into the FAQ. I
really really want to just answer RTFM when the question on what InSight
and Core does comes.
//Bernie
