#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##rfc82

kgamarketing

New Member
I employ MaxBulk mailer to deliver press release distributions. I am currently getting bounces from all recipients at two publishers. I am getting the error message

#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##rfc822


A quick Google turns up the following links

http://www.upenn.edu/computing/email/he ... hment.html
http://www.nd.edu/~engcomp/mac/faq/faq2.html
http://zacky.cleverits.com/IT/exchange_2007.htm

All attribute the cause of this error message to Mozilla Thunderbird; e.g.

"If you are running Mozilla Thunderbird on a Microsoft Exchange Server 2007, there have been some problems reported with E-mails being returned with a message from the server. The message from the server may look something like this:

#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##rfc822

This problem occurs because Thunderbird normally sends attachments inline (as part of the message body) instead of as a real attachment. It appears that the 2007 Exchange server interprets this information incorrectly.

There is a simple way to tell Thunderbird to send all attachments as real attachments, thus fixing the problem of E-mails being returned. To do this, follow the steps below ..."

But I DON’T have Mozilla Thunderbird on my system (and no library profiles for it) - my email client is Entourage 11.4.0

Stranger still, while these emails are al bouncing when sent via MaxBulk mailer, when sent directly from Entourage, they are successfully delivered. I have 'discussed' the matter with the recipients' IT depts and with my ESMTP provider AuthSMTP, and they suggest the problem must lie with BulkMailer. Any ideas?
 

stanbusk

Administrator
Staff member
I have never heard of this. Are you using v6.7? Are you sending attachments? Inline or as standard attachments?
 

kgamarketing

New Member
Using version 5.7.1

Attachments are normal.

Mails are sent via AuthSMTP server.

Mac OS is 10.4.11

Entourage 11.4.0

The error is only happening with two recipient servers (effecting all contacts on both) - in both cases the messages get through when sent via normal Entourage.

The complete error message content is below ...

The e-mail system had a problem processing this message. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
Sent by Microsoft Exchange Server 2007


Diagnostic information for administrators:

Generating server: uk.futurenet.com

[email protected]
#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##rfc822;[email protected]

Original message headers:
Received: from relay1.futurenet.co.uk (172.18.128.21) by
batwexhtca01.uk.futurenet.com (172.23.130.3) with Microsoft SMTP Server id
8.1.263.0; Tue, 18 Aug 2009 20:14:58 +0100
Received: from ixe-mta-16.emailfiltering.com (ixe-mta-16-tx.emailfiltering.com
[194.116.198.212]) by relay1.futurenet.co.uk (Postfix) with ESMTP id
B23345945B6 for <[email protected]>; Tue, 18 Aug 2009 20:12:17
+0100 (BST)
Received: from outmail139016.authsmtp.co.uk ([62.13.139.16]) by
ixe-mta-16.emailfiltering.com with emfmta (version
4.0.0.429.1.rd-3.2.3-libc2.3.2) vanilla id 1153299668 for
[email protected]; Tue, 18 Aug 2009 20:14:36 +0100
Received: from outmail136095.authsmtp.com (outmail136095.authsmtp.com
[62.13.136.95]) by punt3.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id
n7IJEOBe092833 for <[email protected]>; Tue, 18 Aug 2009 20:14:24
+0100 (BST)
Received: from mail-c189.authsmtp.com (mail-c189.authsmtp.com [62.13.128.71])
by punt5.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n7IJEOVY034650 for
<[email protected]>; Tue, 18 Aug 2009 20:14:24 +0100 (BST)
Received: from [192.168.1.33] (69.Red-88-5-211.dynamicIP.rima-tde.net
[88.5.211.69]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp)
with ESMTP id n7IJD4A9096840 for <[email protected]>; Tue, 18 Aug
2009 20:13:54 +0100 (BST)
Date: Tue, 18 Aug 2009 20:14:00 +0100
MIME-Version: 1.0
Subject: [PR] TASCAM Launches Pro AV Sales & Support CORRECTION
From: KGa marketing&media <[email protected]>
To: Neville.Marten <[email protected]>
Message-ID: <[email protected]>
Reply-To: <[email protected]>
Original-recipient: rfc822;[email protected]
Content-Type: multipart/mixed;
boundary="--=BOUNDARY_8182014_JQWI_WUQK_DKUF_HDDW"
X-Server-Quench: 57026f2e-8c2b-11de-a90b-001f29070be2
X-AuthRoute: OCdxYAwdClZJRR8R AyYsDyBJTAw/JRBQ ABkMawBdJUwvWBpQ NkJXaH9aKkERQ3lX RiJOGQEKBRlvCjwo JQtZcnQYNVVMXwVj QEpJSFNWHgdrTxQJ GBsAUBhzaQNPZ3x1 Z0N9Xj4FWz0AAUIM S05dE2UCZSliYGEb VUcWcgRUcgUcfEpY YgN9Bm4MYDFSeytp RwV2Z2hoM28OcHsN SAxXO2Eqe3NDIhcH bDknVREmAEsORygo ZyQ8LRY1Ig4qO0E/ KhNvEWkFKwcVEBEW NGZ3OgJyG3gmYUJl
X-Authentic-SMTP: 61633230343839.kestrel.dmpriest.net.uk:1849/Kp
X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse
X-Virus-Status: No virus detected - but ensure you scan with your own anti-virus system.
Return-Path: [email protected]
 

stanbusk

Administrator
Staff member
I don't know what that error means. It looks like some kind of internal issue. Perhaps the server doesn't like to receive more than xx mails at once.
 

kgamarketing

New Member
I've checked with AuthSMTP support (my ESMTP outgoing mail server) and with both publishers whose mail servers are generating the problem (I've found another problem server - see below), and nobody can pinpoint the source of the error. All I can establish is that there appears to be a problem with MaxBulk Mail mailings and some Microsoft servers; I don't seem to be able to get beyond that.

Another server has thrown up the same problem (this time in Germany)...

Generierender Server: exchange.xchg

[email protected]
#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##rfc822;[email protected]

Ursprüngliche Nachrichtenkopfzeilen:
Received: from winxedgeeu02.exchange.xchg (172.23.1.111) by
winxhubeu04.exchange.xchg (172.23.1.66) with Microsoft SMTP Server id
8.1.393.1; Tue, 18 Aug 2009 21:14:20 +0200
Received: from moutng.kundenserver.de (212.227.17.10) by
winxedgeeu02.exchange.xchg (172.23.1.111) with Microsoft SMTP Server id
8.1.393.1; Tue, 18 Aug 2009 21:14:16 +0200
Received: from outmail139016.authsmtp.co.uk (outmail139016.authsmtp.co.uk
[62.13.139.16]) by mx.kundenserver.de (node=mxbap1) with ESMTP (Nemesis) id
0MKriK-1MdU8N2AMc-000WBd for [email protected]; Tue, 18 Aug 2009 21:14:16
+0200
Received: from punt7.authsmtp.com (punt7.authsmtp.com [62.13.128.13]) by
punt3.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n7IJEEW1092531 for
<[email protected]>; Tue, 18 Aug 2009 20:14:14 +0100 (BST)
Received: from mail-c189.authsmtp.com (mail-c189.authsmtp.com [62.13.128.71])
by punt7.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n7IJEEEB031289 for
<[email protected]>; Tue, 18 Aug 2009 20:14:14 +0100 (BST)
Received: from [192.168.1.33] (69.Red-88-5-211.dynamicIP.rima-tde.net
[88.5.211.69]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp)
with ESMTP id n7IJD4op096839 for <[email protected]>; Tue, 18 Aug 2009
20:13:37 +0100 (BST)
Date: Tue, 18 Aug 2009 20:13:44 +0100
MIME-Version: 1.0
Subject: [PR] TASCAM Launches Pro AV Sales & Support CORRECTION
From: KGa marketing&media <[email protected]>
To: <[email protected]>
Message-ID: <[email protected]>
Reply-To: <[email protected]>
Original-recipient: rfc822;[email protected]
Content-Type: multipart/mixed;
boundary="--=BOUNDARY_8182013_HVVP_AJXI_OXTI_FLUX"
X-Server-Quench: 50f37e2f-8c2b-11de-a90b-001f29070be2
X-AuthRoute: OCdxYAwdClZJRR8R AyYsDyBJTAw/JRBQ ABkMawBdJUwNUhlQ KUtyKl1UK0UYTE0f UDlWFVVcTyw0Dnx3 awpYfQddaEtKVQRp HkBBXFdMFgRpHxoI GRwbUBxtd0sYfwcK EUI9HnBSWkx5fAh/ Sk9QF2lIYGc2a2dK UhZFf1BWIh5Lf0sQ dwF2VCEQYWUGMHhp R1BrNT1rKwZnEhEd fig2Bns3CWICAzg3 Rx0ZVQ01GgUseW0I JhgrMRZSVH0MKl01 K0dpcnUiCTI5Nix5 OSl0OgJyG3gmYUJl
X-Authentic-SMTP: 61633230343839.kestrel.dmpriest.net.uk:1849/Kp
X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse
X-Virus-Status: No virus detected - but ensure you scan with your own anti-virus system.
Return-Path: [email protected]
X-Brightmail-Tracker: AAAAAA==
 

stanbusk

Administrator
Staff member
Perhaps it is something on your message that triggers a server-side anti-spam or anti-virus... not sure. As I told you I have never seen that error before.
 
Top