• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2730
  • Last Modified:

Message from Groupwise cannot be read in Outlook

I am running Outlook 2003 under XP Pro.

A message was sent from X-Mailer: Groupwise 6.5
The subject, to field, from field can be
read.
The message is completely garbled with letters and numbers instead of words
and sentences, etc.

I asked the sender to send aagin when this happened first, but the second
message has the same garbled message.

I have searched, but cannot find any reference to this problem.

I would really appreciate some help.

Here is a sample of what I received.  I have deleted the To and From fields to safeguard identities.

X-Mailer: Groupwise 6.0.3.Beta
Message-ID: <20070806T121855Z_A1BD00050000@homeproperties.com>
From: Subject: Re: Regional for Kettler
To:
Content-Type: multipart/alternative;
boundary="____STZOCYISXQNHAHBUPYTN____"
Return-Path:
X-OriginalArrivalTime: 06 Aug 2007 16:19:19.0079 (UTC)
FILETIME=[8A77AB70:01C7D845]


--____STZOCYISXQNHAHBUPYTN____
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

c2hlJ3Mgb24gdmFjLi4uc29ycnkgZGVhci4gSWYgaXQgY2FuIHdhaXQgdW50aWwgVHVlcywg
c2hl
J2xsIGJlIGJhY2suDQoNCj4+PiAiVmlja2llIExlaXRoIiA8VkxlaXRoQE5hdGlvbmFsQ29y
cG9y
YXRlSG91c2luZy5jb20+IDA4LzA2LzA3IDEyOjEyIFBNID4+Pg0KDQpEb2VzIExlbyBrbm93
IHdo


0
gmckfn
Asked:
gmckfn
  • 4
  • 2
1 Solution
 
ShineOnCommented:
Aargh.  The sender is using a beta version of an obsolete version of GroupWise...

That said, I think I've seen this before.  I noticed that it has a content type of text/plain followed by base64-encoded data.  It's my understanding that base64-encoding is for various attachment types and should be preceded by a content type of application, specifying the app the file is encoded for.

They should first of all update their GroupWise to the last SP for their version instead of running on a beta.  Secondly, they need to determine what this user is sending.  

Can you get anything readable from any other user from that location?  Are they using any kind of mail proxy on their side, or is their GWIA sending directly to the Internet?
0
 
gmckfnAuthor Commented:
This problem is that if they send it to my personal hotmail account, I can read it just fine.  i had even had the user send a black email and it still showed up like this.  And in a bizzare twist, i just had another user call me with the same issue.  I have worked in IT for 3 years, not having this issue once and in 2 days it pops up twice.  This is the second email that was having issues.  As you can see the sender is not using beta but GroupWise 6.5.  

-----Original Message-----
From:
Sent: Tuesday, August 07, 2007 10:10 AM
Subject:

X-Mailer: Groupwise 6.5
Message-ID: <20070807T100953Z_C85C00090000@cwshousing.com>
From:
Subject: Re: August Availability - National
To:
Content-Type: multipart/alternative;
boundary="____SECIHZXQSAWPRXKZUYPU____"
Return-Path:
X-OriginalArrivalTime: 07 Aug 2007 15:09:32.0603 (UTC)
FILETIME=[F58BE0B0:01C7D904]

--____SECIHZXQSAWPRXKZUYPU____
Content-Type: text/plain; charset=utf-8
Content-Language:
Content-Transfer-Encoding: base64

SGV5IGxhZHkuLi4NCg0KV2UgaGF2ZSBhbGwga2luZHMgb2YgaW52ZW50b3J5IGluIE5vcnRo
IEF1
c3RpbiBhbmQgUm91bmQgUm9jayByaWdodCBub3cgaWYgeW91IG5lZWQgYW55dGhpbmcuDQoN
ClRy

0
 
ShineOnCommented:
Hmmmm.  What version of Exchange are you running?

There was a relatively recent hotfix for Ex not properly interpreting base64 encoded messages  (this was a critical security patch, by the way, with a possible vulnerability involved, with the potential of giving full access to the server.)   I wonder if that hotfix broke some base64 encoding interpretation.

In other words - if it works OK with hotmail, and these correspondents don't have this issue with other folks, maybe it's not GroupWise.  Maybe it's your Ex.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
gmckfnAuthor Commented:
Thats what I am thinking...its something to do with our exchange server.  I am running exchange 2003.  I have looked all over microsoft for answers and I have seen alot of people with the same issue,  just no answers.
0
 
ShineOnCommented:
This old hotfix fixed your problem:
http://support.microsoft.com/kb/885419

I wonder if this new hotfix broke the old hotfix:
http://www.microsoft.com/technet/security/bulletin/ms07-026.mspx
0
 
mpaullCommented:
Acutally, The problem is because GroupWise malforms the header. it is supposed to specify a MIME type and does not.

where there should be a MIME type there is just a blank line. Because of this exchange interprets it as RFC822 plain text.

I have done every mentioned fix for this particular issue and have found none except to have the IT staff on the sending end to modify their groupwise configuration to specify a MIME type. Of course no one is happy to hear about that kind of request when it works just fine for others.
0
 
ShineOnCommented:
Have them change their default compose view and default read view to match, either both plain-text or both html.  When the defaults don't match you can have this happen, in certain versions of the client anyway...
0

Featured Post

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now