On Saturday, November 8, 2003, 11:45:38 AM, Marck wrote on the "base64 problem":
> I don't think there's a problem in that area. That's why. <snip> > Well, one thing TB does that other mail software > doesn't is to reply in the originating character set. Perhaps the > combination of Content-Type: header and QP Encoding is causing a > routing server (outbound from your end) to convert to base 64. Maybe that's part of the explanation, and your forced character set (presumably in all or at least most reply templates) is worth a try, but your idea of a recalcitrant server en route doesn't explain why I've seen such a message in the Outbox before it went anywhere! I now often reopen messages in the Outbox to see what they look like, so have caught the one I've had since the initial embarrassment of sending such a message to a list I own. Or at least no one has since told me I'm sending them nonsense. Yes, these base64 messages obviously come about as a result of being replies to other messages, but that is more than half of what email is about. However, based on what you say, despite there being several people who experience this problem, those who don't experience it don't seem to really believe those who do. We'll go away and quietly cry... -- 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
