On Sun, 17 Feb 2002 23:08:04 -0400, Clarence Verge wrote: > On Mon, 11 Feb 2002 09:19:09 +0000, "Edenyard" <[EMAIL PROTECTED]> wrote: > (A LONG TIME AGO)
>> After what seems like YEARS of running 1.70r3, here's a problem >> that's just started to occur in the last week. Sometimes when I click on >> Send Unsent Mail, the status line at the bottom of the screen runs >> through each message VERY quickly and then (leaving me thinking that the >> messages have gone) returns to the Outbox index with all messages still >> there. >> <snip> >> Any clues, please? Thanks! This sometimes happens to me on a few very rare occasions. When this happens the first thing I do is to very carefully examine the message(s) I was trying to send. In every case I always find that there is something not perfectly Kosher about the manner in which a message is prepared and formatted. This happens sometimes as a result of a typo or a glitch due to operator error. I then edit the message so as to make it comply with the RFC standards. After the needed corrections are made I can always send the message(s) with no problems. One RFC-related problem I have discovered with Arachne is the problem of having a line in an email message beginning with the word "begin". Arachne will interpret the word "begin" as a keyword signalling the beginning of an inserted UUENCODED file. This problem we have discussed on the list a very long time ago. Don't start a line beginning with "begin" unless you want to send an inserted UUENCODED file. Don't begin the beguine unless it's your kind of dance and you know all the right steps. You will get tripped up by your fair lady and you will fall on your face. Maybe some other email client programs have similar problem in this regard. Sam Heywood -- This mail was written by user of The Arachne Browser - http://arachne.cz/
