Hello Marck, On Wednesday, November 5, 2003, 2:06:38 PM, you wrote:
> Well, your message to *this* list was not base64 encoded. It was > actually 7 bit according to the headers. And that is part of our combined problem. It only happens with certain replies to messages, and is impossible to reproduce, from what each of us have said. In my case the message which caused this problem was some copy from another email pasted into an email to a list which allows only ASCII text to pass through (and I'm one of the list administrators, but it appeared in the list acknowledgement back to me as being in the base64 coding, so it is just as well it happened to me or I'd have not believed my lame excuse for why it happened). I'm using the MicroEd editor with "Account properties | Mail management", set to "8 bit characters are treated" to "Quoted printable". I could variously get the sent messages to have a header reading other than base64, but there were the base64 codes. I've also got line length set to less than 70. Whatever is causing this problem it is very persistent on those rare occasions when it happens. Fortunately it only seems to happen rarely. The one thing we all seem to have in common is v.2. If a message comes in which is base64 encoded, it is presumably translated to appear on screen, but does The Bat's editor carry that encoding with it if the text is pasted into a new message, even if that message is set to use "printed quotable" or 7-bit? If so, why? -- Gordon Woolf The Worsley Press Hastings, Victoria, Australia www.worsleypress.com [EMAIL PROTECTED] New Book: Success in Store - How to Start or Buy a Retail Business, Enjoy Running It and Make Money ________________________________________________ Current version is 2.01.3 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
