Hi all,
We are having a strange problem that crops up when we email people who are on MS Exchange servers. The recipients get a generic error message from their Exchange server and the email is then included --only as a .txt attachment. Below is a sample error message and my short plain text message. Is it possible that SIMS is somehow adding something that confuses MS Exchange? In the past I've never attributed incompatibilities to SIMS and MS isn't know for robustness, but I'd figured I ask the extensive expertise on the SIMS list if anyone else gets this. Note this SIMS server is on Stanford University's campus, which now requires all outgoing SMTP connections to go through their smtp server. (An infuriatingly lame response to an incident where someone in the Administration did not update their virus protections this summer and had bugbear email out embarrassing files with people's salary information.)
I wonder, aside from MS having a brain dead server, could be doing something strange?
Thanks for any hints,
Here are the clues...
--error message-- From: Joe Wagner [mailto:[EMAIL PROTECTED] Sent: Monday, December 29, 2003 To: [deleted] Subject: RE: Accurint batching
This message uses a character set that is not supported by the Internet Service. To view the original message content, open the attached message. If the text doesn't display correctly, save the attachment to disk, and then open it using a viewer that can display the original character set.
In other words, Exchange is misdesigned, and when it sees a message whose character set it does not understand, it freaks out and does this. There's no good reason for an MTA to care about what character set a message uses, but Exchange does.
--the attached file with my message--
RReceived: from dmz-mx2.seisint.com ([209.243.48.21]) by PONYEXPRESS.br.seisint.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
id Z5MXAKX7; Mon, 29 Dec 2003 16:43:58 -0500
Received: from smtp2.Stanford.EDU (smtp2.Stanford.EDU [171.67.16.116])
by DMZ-MX2.seisint.com (8.12.8/8.12.8) with ESMTP id hBTLhjee012251
for <[deleted]>; Mon, 29 Dec 2003 16:43:46 -0500
Received: from altmail.rehabrobotics.org (FpatAirport.Stanford.EDU [171.64.252.176])
by smtp2.Stanford.EDU (8.12.10/8.12.10) with SMTP id hBTLhisC003450
for <[deleted]>; Mon, 29 Dec 2003 13:43:44 -0800
Received: from [171.64.252.183] (HELO latitude.hypertouch.com)
by altmail.rehabrobotics.org (Stalker SMTP Server 1.8b9d14)
with ESMTP id S.0000030970 for <[deleted]>; Mon, 29 Dec 2003 13:43:44 -0800
Message-Id: <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Mon, 29 Dec 2003 13:37:32 -0800
To: [deleted]
From: Joe Wagner <[EMAIL PROTECTED]>
Subject: RE: Accurint batching
In-Reply-To: <[EMAIL PROTECTED]
isint.com>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset="0"; format=flowed
Oh really? What is the '0' charset???
X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.39
Something, either MIMEDefang (doubt it) or Windows Eudora (likely) or one of the sendmail hops (extremely unlikely) is putting 'charset="0"' into the Content-Type header and screwing this mail up. That should say something like 'charset="us-ascii"' or 'charset="iso-8859-1"' or leave out the charset altogether, but something is putting a bogus charset there. Whatever is doing that is bad and wrong and needs a spanking.
--
Bill Cole [EMAIL PROTECTED]
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
