ARACHNE TODOLIST  - PROPOSED SOFTWARE CHANGE DETAILS
-----------------------------------------------------------------------------------------------------
Item numbers refer to the 2DoList table.


ITEM_59 Tolerate Abnormal Emails

The presence of an email with 258 addresses on the 'To' line
for total line-length of almost 13,000 characters, stopped insight from
correctly showing other emails in the inbox.
When this happens, users might not realise there are real emails under
no subject/zero bytes links, and just delete them thinking they are 
aborted downloads.

 
ITEM_60 Posting long Form Messages

A couple of times, when posting a particularly long message in one of
the Senac.com forums, I noticed that Arachne will not be able to
successfully send it. The message text is entered into a form text
field, and when I click the submit button, I get something displayed
like "xxxx bytes sent, waiting for reply", but nothing happens. After a
while, the "no connection" screen follows, indicating that Arachne has
been waiting for a response which apparently did not arrive.

I wondered if this is some kind of limitation on Senac's side, so I
tried to send the same text that Arachne failed to send with Mozilla on
a Linux box, which had no problems sending it.

So it is something that Arachne does differently, and since the form
text is probably sent via the POST method, I suspect a bug in one of the
related routines. If it is one, then it is probably an old one because I
already had encountered the same problem years ago. I would therefore
suggest to add a request to fix this problem to the Arachne2DoList.

Testing this is probably easy, since it would only require to set up a
new forum at www.senac.com and post some messages of various length. The
messages I had problems with were always more than 1000 bytes long.


ITEM_61 Recover from Cache Index File problems

I *did* have an email problem yesterday, which is why I
had been unable to reply.
In any and all of my mail folders, Arachne just briefly displayed
"Invalid directory" when I either tried to read a mail or reply to it;
I also could not move the mails, either. I do not know what was causing
this, but deleting the cache fixed the problem. I suspect either a
corrupted cache index file, or running out of free entries in it, or
something like that. Perhaps the cache handling should be changed to
delete entries if accessing them resulted in an error, and to
automatically retry the operation afterwards.


ITEM_62 Read Receipts for Email

HI, I SUGGEST TO AD IN ARACHNE NEW RELEASE A 
"RETURN-RECEIPT-TO" OPTION IN INSIGHT MAIL CLIENT.

The Message Headers Return-Receipt-To may be a de facto standard.

Some time ago the Network Working Group RFC 2076 - Common 
Internet Message Headers, referred to Return-Receipt-To as Not 
Internet standard.

Note that some mailing lists BOUNCE all messages containing a 
"Return-Receipt-To:" header. Alternatively some recommend that 
IF YOU RECEIVE mail on ANY mailing list and are asked whether to 
provide return receipt or to notify the sender in any way that you have 
received the email, say NO! (To avoid multiple messages)


ITEM_63 Avoid KeepAlive "BAD REQUEST"

I always keep HTTPKeepAlive Yes, until I hit one of the sites
that gives me back "BAD REQUEST" then manually set HTTPKeepAlive
to No.
Couldn't this be toggled automatically, so Arachne, on getting a 
BAD REQUEST response, tried a second request with the HTTPKeyAlive
set to N for that instance?