CC Field is populated with a hash

[zadunn]

When responding to emails and including a CC, the recipient of the email sees all hashed like values in the CC field.

example simple header:

From: Customer Service
Sent: Tuesday, June 03, 2008 10:36 AM
To: test@example.com
Cc: =?iso-8859-1?B?ZWxpc2Eud2Fsa2VyQGJpbmdoYW0uY29tOyBhbnRob255Lm 5n?=
=?iso-8859-1?B?dXllbkBiaW5naGFtLmNvbQ==?=
Subject: Re: Test


Has anyone seen this before? Or more important how do I fix this?

Thanks

[Hildy]

Have you done anything to the software related to language / characterset?

I am unable to reproduce the behavior here, but that CC line is an encoded one, but it's "encoding" regular latin-1 text.

[zadunn]

Have you done anything to the software related to language / characterset?

I am unable to reproduce the behavior here, but that CC line is an encoded one, but it's "encoding" regular latin-1 text.

I have not cahnged the character text. I did find out after some more testing is that this issue only seems to appear if a semi-colon is used to seperate email addresses in the CC or BCC line. If a space or a comma is used we do not get these odd strings.

[Hildy]

What build are you using? I recall some brief discussion recently about this issue (though possibly not specifically in connection with CCs), though I can't find the comments at this time.

Also, the semi-colon is a group identifier in the CC field, not an address separator, so you shouldn't use it as one.

[zadunn]

What build are you using? I recall some brief discussion recently about this issue (though possibly not specifically in connection with CCs), though I can't find the comments at this time.

Also, the semi-colon is a group identifier in the CC field, not an address separator, so you shouldn't use it as one.

I think when i did my last update it took me to build 603.

I think the problem is that a lot of my agents are used to using a semi-colon because most email programs support that. I have educated them not to, but we will see if that sticks.