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
... Always remember you're unique, just like everyone else.



Estate Computer Systems Limited
Westgate House, Westgate, Sleaford, Lincolnshire, NG34 7RJ
Registered in England No 1604453. VAT No. 416 2922 63

ECS are members of the following trade organisations:
The Microsoft Certified Partner Programme, The Borland User Group, and PISCES 
(Property Information System Common Exchange Standard)

To find out more about ECS why not visit our website http://www.estatecomputers.com

The information in this email (and any attachment) may be for the intended recipient 
only. If you know you are not the intended recipient, please do not use or disclose 
the information in any way and please delete this email (and any attachment from your 
system).  

See http://www.estatecomputers.co.uk/email.htm for our full E-mail communication 
conditions.

(If the above URLs do not appear as links you may need to copy the details into your 
browser address line to access these pages).

Current version is 1.62r | Using TBUDL information:
http://www.silverstones.com/thebat/TBUDLInfo.html


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 to base64

In Account properties | Mail management there's the 8 bit characters
are treated as ... I've switched mine to Quoted Printable from Base
64 to attempt to get around it.

- --
Cheers -- .\\arck D Pearlstone -- List moderator
TB! v1.63 Beta/11 on Windows XP 5.1.2600 Service Pack 1

-BEGIN PGP SIGNATURE-
Version: PGPsdk version 1.7.1 (C) 1997-1999 Network Associates, Inc. and its 
affiliated companies.

iQA/AwUBPvBJnznkJKuSnc2gEQLEFACgnDLN+proCuJ/t/IVsp2hxxsDYvYAoLFi
B6CShHJdZEOncbNpcopJ/ndi
=pCby
-END PGP SIGNATURE-




Current version is 1.62r | Using TBUDL information:
http://www.silverstones.com/thebat/TBUDLInfo.html


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
problem; that default character set had got changed although I have no
idea how.

Thanks anyway.
- --
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
... Why is there so much month left at the end of the money?

-BEGIN PGP SIGNATURE-
Version: PGP SDK 3.0

iQA/AwUBPvBLNtttnLhkydF1EQKsogCg3nVrtolSKTwav4AV9GXH3UWpUwsAn0D2
7xVI+I+tRNeSfaQR0dnLwmgK
=AOj/
-END PGP SIGNATURE-



Current version is 1.62r | Using TBUDL information:
http://www.silverstones.com/thebat/TBUDLInfo.html


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 have a customer who wants to use The Bat! for him-self, but his
| co-workers uses Outlook and Outlook Express. When they are not at
| work, he would like to keep their messages in his system, and send
| them to them, when they come back.
| 
| I have tried helping him, but it seems that Outlook (both) cannot
| import msg-files.
| 
| Is there a way to solve this problem?
`-

[1] see [EMAIL PROTECTED] on tbudl
-- 
Best regards, Carsten

The Bat! (v1.54 Beta/24) Business
Windows NT 5.0 (Build 2195) Service Pack 2, PGP 0xe2d25323


-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d
FAQ: http://faq.thebat.dutaint.com 




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 participated
  in. The program that made Digests had hiccup evey time my messages
  with 7-bit ÆØÅ in headers came through.

  I switched to Quoted Printable encoding. This works fine for this
  list, but there is trouble when people with Outlook Express shall
  answer my mail. The quotes from my message does not get properly
  marked as quotes.

  Now I will try to use 8-bits both in message body and headers. Is
  there any dangers with that?

  Is it possible to change encoding between recipients, for instance
  via a macro in a template, or is this an account property only?

-- 
Best regards,
 Ottar  mailto:[EMAIL PROTECTED]



-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d




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   answer my mail. The quotes from my message does not get properly
OG   marked as quotes.

OG   Now I will try to use 8-bits both in message body and headers. Is
OG   there any dangers with that?

Why you are not give a try :-)

IMHO,  some  Mailer  indeed not supported 8-bits in header, that's why
some  MTA equip with 8-bit conversion, I saw this feature activate for
countries that use 8-bit MIME such France, Rusia and many others.

-- 
Best regards,

- Syafril -   mailto: [EMAIL PROTECTED]


Flying with The Bat! 1.54 Beta/8
under Windows NT 5.0 Build 2195 Service Pack 2



-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d




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 encoding for these letters with The Bat is
OG   8-bit for the massage body but some kind of 7-bit translation for
OG   the headers. This created troble with a mailing list I participated
OG   in. The program that made Digests had hiccup evey time my messages
OG   with 7-bit ÆØÅ in headers came through.

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   answer my mail. The quotes from my message does not get properly
OG   marked as quotes.

This is known problem of Outlook Express of earlier versions - it does not
quote messages if they are quoted printable. People should update their
Outlook Express program.

OG   Now I will try to use 8-bits both in message body and headers. Is
OG   there any dangers with that?

I've tried to do that. Outlook Express version 6 handles that, but some
earlier versions (sorry, don't remember exact OE versions) don't. Now I am
useing 8 bit encoding for message body and Base64 for headers.

OG   Is it possible to change encoding between recipients, for instance
OG   via a macro in a template, or is this an account property only?

It seems it is not possible.

By the way, I've just noticed that this list removes header information
about charset used in message. Why?

Right now I find in my header:
Content-Type: text/plain; charset=ISO-8859-1

But I am sure that it will become just
Content-Type: text/plain when I get my message from this list.

-- 
Edvinas




-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d




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 Humanize Quote Printable on tbudl list, it
will convert QP to Plain-Text.

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.

Correct.
Humanize QP not only convert the body, the header too.
If you want to see the effect without Humanize QP, try post to tbtech
or tbbeta list instead.

-- 
Best regards,

- Syafril -   mailto: [EMAIL PROTECTED]


Flying with The Bat! 1.54 Beta/8
under Windows NT 5.0 Build 2195 Service Pack 2



-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d




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 body, the header too.
SH If you want to see the effect without Humanize QP, try post to tbtech
SH or tbbeta list instead.

But why it removes information about charset? What are the reasons to remove
it?

-- 
Edvinas


-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d




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 infact the body is plain-text, the
result is unpredictable :-)

-- 
Best regards,

- Syafril -   mailto: [EMAIL PROTECTED]


Flying with The Bat! 1.54 Beta/8
under Windows NT 5.0 Build 2195 Service Pack 2



-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d




Re: Content Transfer Encoding

2001-09-14 Thread Edvinas

Hello,

On Friday, September 14, 2001, 13:52, Syafril wrote:

SH To prevent MUA confusing :-).

Excuse my ignorance - what is MUA? :)

SH If  the  header said it is QP while infact the body is plain-text, the
SH result is unpredictable :-)

Yes, I understand that. But information about message 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 (this list removes
such information!). When someone in this list uses characters from other
charsets I can't see correct characters. I need manually to choose correct
charset. I hope you understand what I am trying to tell.

-- 
Edvinas


-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d




Re: Content Transfer Encoding

2001-09-14 Thread Syafril Hermansyah

Hi All,

On Fri, 14 Sep 2001 at 14:56:19 GMT +0200 (9/14/2001 7:56 PM GMT +0700
where you think I live) Edvinas=[E] typed the following :

SH To prevent MUA confusing :-).

E Excuse my ignorance - what is MUA? :)

Mail User Agent = Mailer.

SH If  the  header said it is QP while infact the body 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  language  charset  ir  ISO-8859-13  and  The  Bat! displays
E message  in  this  encoding  if charset is not specified in message
E header  (this list removes such information!). When someone in this
E list  uses  characters  from  other  charsets  I  can't see correct
E characters.  I  need manually to choose correct charset. I hope you
E understand what I am trying to tell.

I  can  understand  that,  but perhaps you may reconsider the names of
humanize  QP,  it  means  the  listserver  trying  to *convert* (not
*stripe out*) QP to PT, to make even dumb MUA to understand, easy to
decode.

Look  last  posting from Ottar, are your TB! having problem to display
it ?

Most  person  only  seen what's the content/body text, only if our MUA
have problem to decode or for other reason, we need to look the header
for further analysis :-)
Seems  to  me  you're  Techie person, why not join to tbtech list as I
suggest, make test there and compare it :-)

-- 
Best regards,

- Syafril -   mailto: [EMAIL PROTECTED]


Flying with The Bat! 1.54 Beta/8
under Windows NT 5.0 Build 2195 Service Pack 2



-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d




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
Ottar's message as it was supposed to be displayed.

-- 
Edvinas


-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d




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 lithuanian  characters. I had manually to set charset to ISO-8859-1
E -  only  then  I  saw  Ottar's  message  as  it  was supposed to be
E displayed.

Make test on tbtech, see the result...I will consider later.

-- 
Best regards,

- Syafril -   mailto: [EMAIL PROTECTED]


Flying with The Bat! 1.54 Beta/8
under Windows NT 5.0 Build 2195 Service Pack 2



-- 

Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d