Content-transfer-encoding

2003-06-18 Thread Stuart Hemming
Is this set manually in TB!? That is, is it possible that I've done something that has caused my messages to start going out with Content-transfer-encoding set to base64 -- Stuart Using The Bat! v1.63 Beta/11 on Windows XP 5.1 Build 2600 Service Pack 1 PGP Key available from ldap://keys.pgp.com

Re: Content-transfer-encoding

2003-06-18 Thread Marck D Pearlstone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Stuart, @18-Jun-2003, 11:44 Stuart Hemming [SH] in mid:[EMAIL PROTECTED] said SH Is this set manually in TB!? That is, is it possible that I've SH done something that has caused my messages to start going out SH with Content-transfer-encoding set

Re: Content-transfer-encoding

2003-06-18 Thread Stuart Hemming
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 MDP In Account properties | Mail management there's the 8 bit characters MDP are treated as ... I've switched mine to Quoted Printable from Base MDP 64 to attempt to get around it. Mine's set to 'Without Changes'. However I think I've found the

Content-Transfer-Encoding stripped from mail

2002-01-05 Thread Carsten Thnges
Hi list, hi list admins, Content-Transfer-Encoding: ... seems to be cut from mails[1]. Is this a technical problem on the list server? I added Content-Transfer-Encoding: base64 to Britt's Mail and got: ,- [ you wrote in base 64 ] | lørdag, den 5. januar 2002, 11:56 | | Hello list, | | I

Content Transfer Encoding

2001-09-14 Thread Ottar Grimstad
Hello TBUDL, I am norwegian and uses the norwegian letters æøåÆØÅ a lot, even in subjects. It seem that the standard encoding for these letters with The Bat is 8-bit for the massage body but some kind of 7-bit translation for the headers. This created troble with a mailing list I

Re: Content Transfer Encoding

2001-09-14 Thread Syafril Hermansyah
Hi All, On Fri, 14 Sep 2001 at 11:58:49 GMT +0200 (9/14/2001 4:58 PM GMT +0700 where you think I live) Ottar Grimstad=[OG] typed the following : OG I switched to Quoted Printable encoding. This works fine for this OG list, but there is trouble when people with Outlook Express shall OG

Re: Content Transfer Encoding

2001-09-14 Thread Edvinas
Hello, On Friday, September 14, 2001, 11:58, Ottar wrote: OG Hello TBUDL, OG I am norwegian and uses the norwegian letters æøåÆØÅ a lot, even in OG subjects. Similar situation with me - I'm lithuanian ad I am also using specific lithuanian letters a lot. OG It seem that the standard

Re: Content Transfer Encoding

2001-09-14 Thread Syafril Hermansyah
Hi All, On Fri, 14 Sep 2001 at 13:05:18 GMT +0200 (9/14/2001 6:05 PM GMT +0700 where you think I live) Edvinas=[E] typed the following : [...] E By the way, I've just noticed that this list removes header E information about charset used in message. Why? Because I have activate

Re[2]: Content Transfer Encoding

2001-09-14 Thread Edvinas
Hello, On Friday, September 14, 2001, 13:37, Syafril wrote: E Right now I find in my header: E Content-Type: text/plain; charset=ISO-8859-1 E But I am sure that it will become just E Content-Type: text/plain when I get my message from this list. SH Correct. SH Humanize QP not only convert the

Re: Content Transfer Encoding

2001-09-14 Thread Syafril Hermansyah
Hi All, On Fri, 14 Sep 2001 at 13:41:02 GMT +0200 (9/14/2001 6:41 PM GMT +0700 where you think I live) Edvinas=[E] typed the following : E But why it removes information about charset? What are the reasons E to remove it? To prevent MUA confusing :-). If the header said it is QP while

Re: Content Transfer Encoding

2001-09-14 Thread Edvinas
encoding type is kept in Content-Transfer-Encoding header field. Content-Type has nothing to do with it. You may wonder why it is so important for me :) Thing is that my native language charset ir ISO-8859-13 and The Bat! displays message in this encoding if charset is not specified in message header

Re: Content Transfer Encoding

2001-09-14 Thread Syafril Hermansyah
is plain-text, the SH result is unpredictable :-) E Yes, I understand that. But information about message encoding type E is kept in Content-Transfer-Encoding header field. Content-Type E has nothing to do with it. E You may wonder why it is so important for me :) Thing is that my E native

Re: Content Transfer Encoding

2001-09-14 Thread Edvinas
Hello, On Friday, September 14, 2001, 15:22, Syafril wrote: SH Look last posting from Ottar, are your TB! having problem to display SH it ? Yes it had. Instead of Ottar's norvegian characters TB!displayed lithuanian characters. I had manually to set charset to ISO-8859-1 - only then I saw

Re: Content Transfer Encoding

2001-09-14 Thread Syafril Hermansyah
Hi All, On Fri, 14 Sep 2001 at 15:49:52 GMT +0200 (9/14/2001 8:49 PM GMT +0700 where you think I live) Edvinas=[E] typed the following : SH Look last posting from Ottar, are your TB! having problem to display SH it ? E Yes it had. Instead of Ottar's norvegian characters TB!displayed E