Hi Kitty, @7-Nov-2003, 13:08 -0600 (07-Nov 19:08 UK time) Kitty said:
> If the bugs are ironed out, fine. My concern is that I don't see > that anyone is even acknowledging the Base64 problem or working on > it. I don't think there's a problem in that area. That's why. We're yet to identify exactly what's going on, but I don't think that TB is sending base 64 from your system. That's why nobody will acknowledge the problem. It doesn't actually happen the way it's being reported. I'm beginning to believe that a server is translating your messages to base 64 when routing it. Why? I've had a thought about that. The posts to these lists that end up base 64 encoded are always replies, right? 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. A simple work-around is to code your reply template for the list to force the character set to Latin-1 with a %CHARSET="ISO-8859-1". > None of those things are critical to me. That said, TB has other > features that are important to me but I'm not sure yet how unique > they are to TB. Well, if you tell us what is important to you, then those in the know can make comments about that. > FWIW, Pocomail has a web forum that has been very responsive to > questions and has developer support. There are TB support forums out there too. I just think that forums are pretty lame for support because, as a support person, you have to go look for the current issues and make a great deal more effort to do so before you can help out. With a list, the questions just arrive and you can answer them at will. Much easier for a volunteer support team to handle. > However, the glitch right now is very crippling for me. The > messages I am sending to a variety of places that I post to > regularly are going in Base64 and I can't tell in advance whether > this will happen or not. Not *one* of your posts to these lists with v2 came in as base64. Even replies to non-Latin1 messages. That tells me that v2 is not the culprit. It doesn't tell me why you are being afflicted in this way though :-/. > That is more than a minor glitch or foible. It makes v. 2 unusable > for me at this time. It's a shame, because I don't even think it's TB's fault. I'd love to see a MIME forward of a before / after example of these postings - a copy of what was in your sent folder and a copy of what you received back, base64 encoded, from the list. That would tell quite a lot. Send it off-list if you can. -- Cheers -- .\\arck D Pearlstone -- List moderator SB! v2.01.28 on Windows XP 5.1.2600 Service Pack 1 '
pgp00000.pgp
Description: PGP signature
________________________________________________ Current version is 2.01.3 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
