/defaultcharset=iso-8859-1

[Useless Guru]

Does this gwia.cfg switch actually work??

 

We are on GroupWise 7 SP2 (Release).

 

We were hoping that this parameter would solve our umlaut problem.

Here is how to produce the issue:

 

---

myhost:~ # telnet 100.101.102.102
Trying 100.101.102.103...
Connected to 100.101.102.103.
Escape character is '^]'.
220 myhost.mydomain.dom ESMTP Postfix
helo guest
250 myhost.mydomain.dom
mail from: sen...@fromdomain.com

250 Ok
rcpt to: reci...@todomain.com

250 Ok
data
354 End data with <CR><LF>.<CR><LF>
Subject: Umlaute
öäüéàè
.
250 Ok: queued as 587D87342EB1A
quit

Connection closed by foreign host.

---

The umlauts in this message will not get displayed properly in the GroupWise client, regardless whether the /defaultcharset=iso-8859-1 is set or not.

 

Can anyone help?

 

Thanks

Stephan

[Massimo Rosen]

Hi,

> Useless Guru wrote:
>
> Does this gwia.cfg switch actually work??

Well, I know this works:

/defaultcharset=ISO-8859-15

However, please not that the defaul gwia.cfg lists this setting with a
hyphen instead of the equal sign, e.g:

/defaultcharset-ISO-8859-15
^

And that does *NOT* work (been there, done that). So make sure you have
a equal sign in the option. Also, I did not try ISO-8859-1, only
ISO-8859-15.

> 220 myhost.mydomain.dom ESMTP Postfix

Upps. Can you test this directly against your GWIA please, and not an
upstream postfix? This might well dilute the results you get.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de

[Useless Guru]

Hi Massimo

 

Thanks for your hints.

 

First of all: What is the diff between ISO-8859-1 and ISO-8859-15? Which one should we use. We are mostly dealing with german, french and italian special characters. I have set it to /defaultcharset=ISO-8859-15 now.

>> 220 myhost.mydomain.dom ESMTP Postfix

>

>Upps. Can you test this directly against your GWIA please, and not an
>upstream postfix? This might well dilute the results you get.

 

Nope, that does not make a diff. I tried sending the msgs directly to gwia with the same results.

 

However I have discovered that it makes a difference from what system I send the message:

- If I send a message from windows telnet, then the umlauts will be displayed properly.

- If I send a message from a unix telnet, then I see garbage.

Any ideas??? I will try to get a trace of the stream as it goes over the wire to find out more.

[Massimo Rosen]

Hi,

> Useless Guru wrote:
>
> Hi Massimo
>
> Thanks for your hints.
>
> First of all: What is the diff between ISO-8859-1 and ISO-8859-15?

The latter supports the Euro sign. Other than that, they're identical.

> Which one should we use. We are mostly dealing with german, french and
> italian special characters. I have set it to
> /defaultcharset=ISO-8859-15 now.

And, does it work?

[Michael Bell]

Good. Never should have made that the default to begin with. Darn europeans
have to learn. RFC 2047 it or friggin use good AMERICAN!

"Morris Blackham" <mbla...@gw.novell.com> wrote in message
news:bF7Yh.517$%D1....@prv-forum2.provo.novell.com...
> The /defaultcharset option only works for MIME files. It does not work
> for RFC822 messages.
>
> For SP1 IR1, we changed GWIA's default charset from ISO-8859-1 to
> USASCII (which it should be anyway) to address a Japanese escape character
> encoding issue. This is why the scenario you described does not work any
> more. Furthermore..... this should not work strictly according to RFCs,
> which state all RFC822 messages should be USASCII only characters.
>
> That said however, because this did work prior to IR1, we have recently
> added yet another GWIA startup option; /DefaultNonMimeCharset option.
> Same criteria apply that Massimo stated, use / /DefaultNonMimeCharset
> =ISO-8859-1 (or 15). However, I've never seen an issue with the "-"
> instead of the "=".
>
> We just made this change late last week. I'm not sure when a hotpatch
> would be available with this.
>
> Morris
>
>

[Morris Blackham]