On Sat, 8 Nov 2003 00:45:38 +0000, Marck D Pearlstone wrote: > 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 think you are right, but it is because of something that TB is doing. I've looked at archives here and on TBBeta and there are a few others reporting it. I also have had some messages go to some lists in gibberish with weird characters that aren't Base64 (I posted an example of this the other day). > The posts to these lists that end up base 64 encoded are always > replies, right? No. For example -- not Base 64 but something weird was posted to [EMAIL PROTECTED] ��ͽ����Q������ͽ��������ѡ��P��م�Յѥ�����ȁ��ͽ����́ɕ����������ѡ�́չ�и ��M�����Ё�������͕ٕɅ������Ց�����������͵��Ѐ���������ѡ�́݅́ѡ���������� �����ѡ�����и��M������ͥ��ɕ��ѡ������͵��Ё��������ݽձ����ٔ�ɕ������������ ���Ё��ȁ����ѡ����4(4)M���ͅ�́ѡ�Ё�ɥ�ѥ����́�Ս ���ͥ�ȁ�ɽ��ѡ��Eե���A��� Aɼ���ԁ���Ё�����������%H�A�������ѡ�����Ё͕����ɥ�Ё����ѡ�����յ��Ё�ɥ��̸ ��M���ͅ�́ѡ�Ёݥ� �ѡ������͵��Ё�Ё�́�Ս ���ɔ�ѕ����̰�ɕ�եɥ���������ѡ� �՝ �͕ٕɅ������́�������х���ѥ������ͽ��݅ɔ������� ������ѕȁ�ԁ�ɔ��ɥ�ѥ� ��Ѽ���4(4)]�� ���ͽ���$�ѡ����ͥ�����������ѕ��ݽɭ́���ѕȁͼ��ٕ��ѡ�՝ �$� ������ѡ��A��ɽ���ѥ�́���ѡ��9�ѡ�͕́��́Ѽ���������ѕȁ�������4(4)!�́�� 役���͕��������䁙����������M����́ݥ������Ѽ��ɑ�ȁ�ȁ�ݥэ ���Ёչ��́������ ѡ�ȁ����ݽձ��ݽɬ����ѕȸ4(4(��4) ��Ёɕ��ɑ̰4)-�����x��x�4(4( This was not a reply. Tried it multiple times, copied it to computer guru guy on the server end. He sent me a reply as follows: === Right. Your email program (or a server between you and us) is creating base64 encoded email, for some reason. The copy you cc'ed to me was auto-converted back to USASCII by sendmail on my server. Oddly, the sample that Meredith quoted to me earlier was not base64 encoded by the time it reached me -- it was a really weird set of non-ASCII garbage! === FWIW, I then wrote the same mail to the list in Becky and it posted fine. Both original messages and replies sent to the same mailing list using Pocomail (set on plain text) go through fine. It is *only* messages I send through TB that have the problem. >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". > let me try that. >> 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. In my first message in this thread, I did that. Any comments you would have would be appreciated. > >> 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. I prefer mailing lists as well. That said, I was able to quickly get responses to question re: Pocomail so find the level of support adequate. > >> 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 :-/. I think it is defying reality to say that V2 is not the culprit. I have several mailing lists at different places that I am having this problem with -- either posting in Base64 or totally weird characters. I have been using TB for over 3 years. I have been posting to those lists for over 3 years. Never a problem. I get TB V2 and make no other changes and now have this problem posting. And, fwiw, I have TB on 2 different computers and I have the *same* problem posting to those lists from either computer. It seems pretty clear that this is something TB related. Particularly since using any other mail program other than TB v2 to post to those lists eliminates the problem. > >> 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. OK....but I want to be clear on what you want. What do you mean by sending a MIME forward? Exactly how do I do that? Is it something different from just a regular forward? ________________________________________________ Current version is 2.01.3 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
