The Microsoft Exchange Server received an Internet message that could not be processed.
I have an Exchange 5.5 server with SP4 running on and NT 4.0 OS with the latest patches. I’ve just run across a problem that doesn’t seem to be well addressed in the Microsoft Tech Net site.
We have recently implemented a Barracuda SPAM solution, but this problem has been periodically occurring.
The pertinent header data follows:
Received: from barracuda.ci.mtnview.ca.us ([10.1.2.223]) by cmv-ch-email.ci.mtnview.ca.us with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
id XFXZ2K4H; Wed, 8 Dec 2004 08:43:32 -0800
X-ASG-Debug-ID: 1102524210-23745-58-0
X-Barracuda-URL: http://barracuda.ci.mtnview.ca.us:8000/cgi-bin/mark.cgi
Received: from cmv-ch-smail.ci.mtnview.ca.us (mailhost.ci.mtnview.ca.us [209.155.146.199])
by barracuda.ci.mtnview.ca.us (Spam Firewall) with ESMTP id 3BE24203FD32
for
Received: from samourai1.co.santa-clara.ca.us (samourai1.co.santa-clara.ca.us [146.74.221.105])
by cmv-ch-smail.ci.mtnview.ca.us (8.12.11/8.12.11) with ESMTP id iB8GhDdx030696
for
Received: from dns-cvc.CO.Santa-Clara.CA.US (localhost [127.0.0.1])
by samourai1.co.santa-clara.ca.us (8.12.1 – patch: 12.8, 12.9, 12.10/8.12.1) with ESMTP id iB8GfrZA020472
for
Received: from sccsrv60.co.santa-clara.ca.us (sccsrv60 [146.74.2.71])
by dns-cvc.CO.Santa-Clara.CA.US (8.12.1 – patch: 12.8, 12.9, 12.10/8.12.1) with ESMTP id iB8Ggslm009558
for
To: john.spalding@ci.mtnview.ca.us
X-ASG-Orig-Subj:
Subject:
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
Message-ID:
From: janet.hayton@cnt.sccgov.org
Date: Wed, 8 Dec 2004 08:42:26 -0800
X-MIMETrack: Serialize by Router on SCCSRV60/SRV/SCC(Release 6.5.1|January 21, 2004) at
12/08/2004 08:42:28
Content-Type: multipart/mixed; boundary=”=_mixed 005BAE3C88256F64_=”
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Virus-Scanned: by Barracuda Spam Firewall at ci.mtnview.ca.us
X-Barracuda-Spam-Score: -1001.00
X-Barracuda-Spam-Status: No, SCORE=-1001.00 using global scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=4.9 KILL_LEVEL=6.9
–=_mixed 005BAE3C88256F64_=
Content-Type: multipart/related; boundary=”=_related 005BAE3C88256F64_=”
–=_related 005BAE3C88256F64_=
Content-Type: multipart/alternative; boundary=”=_alternative 005BAE3C88256F64_=”
–=_alternative 005BAE3C88256F64_=
Content-Type: text/plain; charset=”US-ASCII”
Yes, there are three files and a cut/pasted map of Saratoga Fire that you
should be receiving.
Information for you before the meeting Thursday, Dec 9, at Saratoga Fire.
[IMAGE]
– December 2004 TO Agenda.doc – 2005 meeting schedule.doc
–=_alternative 005BAE3C88256F64_=
Content-Type: text/html; charset=”US-ASCII”
Yes, there are three files and a cut/pasted
map of Saratoga Fire that you should be receiving.
Information for you before the meeting
Thursday, Dec 9, at Saratoga Fire.
| [IMAGE] |
–
December 2004 TO Agenda.doc – 2005 meeting schedule.doc
–=_alternative 005BAE3C88256F64_=–
–=_related 005BAE3C88256F64_=
Content-Type: image/gif
Content-ID: <_1_03505FF003504C18005BAE3B88256F64>
Content-Transfer-Encoding: base64
We suspect but are not sure it is a problem from the sender’s end using bin encoding vice Mime encoding….
any insights is appreciated.