I have dupe install of 1.68 running inbox again, and cannot tell you why. Wish I could! I've also found another problem I'll address at a later time/date. Currently I just found a BIG problem when Arachne handles mail files. I'm viewing a message in InSight; I hit F-6 to view the whole thing in original format. I decide I want to send that file to someone else. I hit the correct button, feed in the address, write the accompanying message ... for some reason I decided to save to OutBox so I could check it out. Went to outbox, found that attachment was NOT in form of text file. Shelled out to look and see what the problem was [maybe just have to change .cnm to .txt or such] and discover that Arachne has ENCODED the damn file! This is a text e-mail file. Encoding it takes up much too much space, and it shouldn't encode in the first place! Yes, I can go back to the old way of saving the file to a temp location/name I can remember, and importing the file into my message. But I shouldn't have to. Can someone please teach InSight that .cnm files are to be treated as text, and NOT encoded?? l.d. -- This mail was written by user of Arachne, the Ultimate Internet Client -- Arachne V1.68, NON-COMMERCIAL copy, http://arachne.cz/
