OL 2003 and Decoding MIME ListServ Messages...

[krburger]

I am having a problem getting back issues from a ListServ I have
subscribed to. When I get the message I request, it comes in some
form of gobbleygook that I cannot read, and it contains a message
stating that I should change to a mail reader that understands how to
properly handle MIME multipart messages... I'll paste the relevant
info here. Can someone please tell me why OL 2003, which is
supposedly MIME aware won't let me see the damn thing?

Internet headers:
Delivered-To: [email protected]
Received: by 10.86.58.14 with SMTP id g14cs573990fga;
Wed, 29 Oct 2008 07:44:14 -0700 (PDT)
Received: by 10.100.232.10 with SMTP id e10mr3280310anh.
36.1225291451501;
Wed, 29 Oct 2008 07:44:11 -0700 (PDT)
Return-Path: <>
Received: from smtpout.michigan.gov (smtpout.michigan.gov
[136.181.195.42])
by mx.google.com with ESMTP id h16si4397169wxd.
21.2008.10.29.07.44.09;
Wed, 29 Oct 2008 07:44:11 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of
smtpout.michigan.gov designates 136.181.195.42 as permitted sender)
client-ip=136.181.195.42;
Authentication-Results: mx.google.com; spf=pass (google.com: best
guess record for domain of smtpout.michigan.gov designates
136.181.195.42 as permitted sender) smtp.mail=
Received: from corelst2 ([10.42.252.6]) by
coreosmtp3.som.ad.state.mi.us with InterScan Message Security Suite;
Wed, 29 Oct 2008 10:44:07 -0400
Date: Wed, 29 Oct 2008 10:44:07 -0400
From: "State of Michigan LISTSERV Server (14.5)"
<[email protected]>
Subject: File: "TREAS-STC-PTD LOG0810C"
To: Kenneth Burger <[email protected]>
Message-ID: <LISTSERV%[email protected]>

MIME headers:
Date: Wed, 15 Oct 2008 13:34:02 -0400
Reply-To: Kelli Sobel <[email protected]>
From: Kelli Sobel <[email protected]>
Subject: Memo from the State Tax Commission
Comments: To: Roger McEvers <[email protected]>,
Lewis Rogers <[email protected]>,
Harold Anderson <[email protected]>,
Sabrina Carr <[email protected]>,
Michael Gillett <[email protected]>,
Earl GrandChamp <[email protected]>,
Larry Griggs <[email protected]>,
Keith Kline <[email protected]>,
Sam Licavoli <[email protected]>,
Michael Markes <[email protected]>,
Patrick McCall <[email protected]>,
Roger Mcevers <[email protected]>,
Jayne Mcleod <[email protected]>,
Marie Medlock <[email protected]>,
Lori Parr <[email protected]>, Janice Rais
Cindy Reetz <[email protected]>,
Lewis Rogers <[email protected]>,
Richard Watza <[email protected]>,
Dianne Wright <[email protected]>,
Don Bode <[email protected]>
Comments: cc: Chris Gerber <[email protected]>,
[email protected], [email protected],
Alpena CED
[email protected], [email protected],
Marilyn Preztkop <[email protected]>,
John Awrey <[email protected]>,
[email protected], Benzie CED
Berrien CED <[email protected]>,
Calhoun CED <[email protected]>,
[email protected], [email protected], Charlevoix
CED
Grand Traverse CED <[email protected]>,
Lindstrom Rick <[email protected]>,
[email protected], [email protected], Sharon
Kennedy
[email protected], [email protected], Emmet CED
<[email protected]>, Emmet CED
[email protected], [email protected]-traverse.mi.us,
Gratiot CED <[email protected]>,
Hillsdale CED <[email protected]>,
[email protected], [email protected], Lake CED
[email protected], [email protected],
[email protected], [email protected],
[email protected], Muskegon CED
Muskegon CED <[email protected]>,
Newaygo CED <[email protected]>,
[email protected], [email protected], Wayne CED
Jodi Connell <[email protected]>,
Liz Pulley <[email protected]>,
[email protected], [email protected].,
Tim Vandermark <[email protected]>,
[email protected], Gladwin CED <[email protected]>,
[email protected], Schoolcraft CED
Bay CED <[email protected]>,
[email protected], John Partanen
Montmorency CED <[email protected]>, Sharyn Malone
[email protected], [email protected], Iosco CED
[email protected], Judy Niznak
[email protected], Sharon Zakrajsek
Kent CED <[email protected]>,
Kent CED <[email protected]>,
[email protected], Lapeer CED
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], Roger Chappel
Calhoun CED <[email protected]>, David Lee
Missaukee CED <[email protected]>,
Michael Woolford <[email protected]>,
Maureen Code <[email protected]>, David Hieber
Oceana <[email protected]>,
[email protected], [email protected],
Keweenaw CED
[email protected], Saginaw CED
[email protected], Shiawassee CED
[email protected], [email protected],
[email protected], [email protected], [email protected],
Ed Vandervriese <[email protected]>,
Molly Whetstone <[email protected]>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=__Part654CD69A.57__="

This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.

--=__Part654CD69A.57__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Please see the attached memo from the State Tax Commission regarding =
classification.

Kelli Sobel, Executive Secretary
Michigan State Tax Commission
(517) 241-0917
Email: [email protected]


--=__Part654CD69A.57__=
Content-Type: application/pdf; name="Assesors on Exposure Draft.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Assesors on Exposure
Draft.pdf"

 

[Brian Tillman [MVP - Outlook]]

I am having a problem getting back issues from a ListServ I have
subscribed to. When I get the message I request, it comes in some
form of gobbleygook that I cannot read, and it contains a message
stating that I should change to a mail reader that understands how to
properly handle MIME multipart messages... I'll paste the relevant
info here. Can someone please tell me why OL 2003, which is

--
Brian Tillman [MVP-Outlook]

supposedly MIME aware won't let me see the damn thing?

No one is going to appreciate your having posted their mail addresses in
plain text on a newsgroup because not they'll all get a spate of spam and
viruses because their addresses will be harvested from your message.

Are you running on Vista or XP?

 

[krburger]

I am having a problem getting back issues from a ListServ I have
subscribed to.  When I get the message I request, it comes in some
form of gobbleygook that I cannot read, and it contains a message
stating that I should change to a mail reader that understands how to
properly handle MIME multipart messages... I'll paste the relevant
info here.  Can someone please tell me why OL 2003, which is

--
Brian Tillman [MVP-Outlook]

supposedly MIME aware won't let me see the damn thing?

No one is going to appreciate your having posted their mail addresses in
plain text on a newsgroup because not they'll all get a spate of spam and
viruses because their addresses will be harvested from your message.

Are you running on Vista or XP?

XP.

 

[Brian Tillman [MVP - Outlook]]

XP.

Do you receive current messages from the group properly that are in HTML?
I.e., is it just the archived messages you're requesting that are malformed?
If you can access your mailbox via a web browser, do the messages look OK
that way? What type of account are you using in Outlook - POP, IMAP,
Exchange, or HTTP?

 

[krburger]

Do you receive current messages from the group properly that are in HTML?
I.e., is it just the archived messages you're requesting that are malformed?
If you can access your mailbox via a web browser, do the messages look OK
that way?  What type of account are you using in Outlook - POP, IMAP,
Exchange, or HTTP?

Current messages come through just fine. Only archived messages seem
to have this problem. I know that if I view it in gmail I have the
same problem. I haven't tried using mail2web or any of the other
services like that yet. The account is currently set up as POP3.

 

[Brian Tillman [MVP - Outlook]]

Current messages come through just fine. Only archived messages seem
to have this problem. I know that if I view it in gmail I have the
same problem.

This pretty well indicates you don't have an Outlook problem. It's more
indicative of the listserv not correctly packaging the archive messages.