Message delivery failuer: Reason 500 Line too long

Discussion forum for Enterprise Edition.
Post Reply
MainStWebGuy
Posts: 7
Joined: Fri Oct 10, 2008 1:33 pm

Message delivery failuer: Reason 500 Line too long

Post by MainStWebGuy » Fri Oct 10, 2008 1:38 pm

I'm getting this message when trying to send an email. I'm sending to a customer, who i've mailed in the past, before using mailenable, but now, with this system, i get this error. What could it be?

sorry i'm not giving a ton of info here... i'm new to Mail Enable and if there's any more info i can provide to help, let me know!
here's the error:

Code: Select all

MailEnable: Message could not be delivered to some recipients.
The following recipient(s) could not be reached:

Recipient: [SMTP:XXXXX@XXXXXX.COM]
Reason: 500 Line too long


Message contents follow:

Received: from ([208.40.7.10]) by HostDomain.com with MailEnable WebMail; Thu, 9 Oct 2008 13:26:19 -0400
To: <XXXX@XXXX.COM>
From: <Sender@XXXXX.com>
Subject: **SENDER** RETURNS
Date: Thu, 9 Oct 2008 13:26:19 -0400
Message-ID: <B70154AA20F541B5B7CFF3B212FFA741.MAI@HOSTDOMAIN.com>
MIME-Version: 1.0
X-Mailer: MailEnable WebMail.NET
X-MimeOLE: Produced By MailEnable WebMail.NET V3.03.0.0
X-Read: 0
Content-Type: multipart/mixed;
boundary="--=_Part_CF9B5146133C4FCC80650CF1DAE2FF62"
X-Priority: 3
X-MSMail-Priority: Medium
X-ME-Bayesian: 40.000000

This is a multi-part message in MIME format.

----=_Part_CF9B5146133C4FCC80650CF1DAE2FF62
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<P><FONT face=3D'courier new,courier,arial,helvetica,sans-serif'>XXXXX RETURNS     **SENDER**     10/09/2008     FAX#419-420-7970</FONT></P>
<P><FONT face=3D'courier new,courier,arial,helvetica,sans-serif'><A  href=3D'mailto:XXXX@XXXX.COM' target=3D'_blank'>XXXXX@XXXXX.COM</A></FONT></P>
<P><FONT face=3D'courier new,courier,arial,helvetica,sans-serif'> PART #   INVOICE #  DATE   PRICE</FONT></P>
<P><FONT face=3D'courier new,courier,arial,helvetica,sans-serif'> <BR>1.DB10130  SO#457604  09/24  201.89<BR>2.DD10857  SO#459704  10/01/08 $59.90<BR>3.DD7716  SO#459704  10/01/08 $50.30<BR>4.DQ9540YP  SO#460212  10/02/08 $65.24<BR>5.DD9510  SO#461026  10/06/08 $45.71 <BR>6.DD8264  SO#460562  10/03/08 $177.82 <BR>7.FW801   SO#430212  10/02/08 $48.42<BR>8.DW1179  SO#459704  10/01/08 $49.66<BR>9.DL4717 x2  SO#459704  10/01/08 $83.56<BR>10.DD7833GTN  SO#461660  10/07/08 $41.79<BR>11.FW823GGN  SO#461660  10/07/08 $59.30 <BR>12.DW1297  DISTORTED DEBBIE KNOWS     X1<BR>13.FW753GBN  DISTORTED DEBBIE KNOWS     X2<BR>14.DW1626GBN  DISTORTED DEBBIE KNOWS    X3</FONT></P>


----=_Part_CF9B5146133C4FCC80650CF1DAE2FF62--

MailEnable-Ben
Posts: 5858
Joined: Fri Jan 16, 2004 6:49 am
Location: Melbourne

Post by MailEnable-Ben » Mon Oct 13, 2008 1:45 am

Looks like the error is returned by the remote server, possibly something changed on their end or the way you are sending has changed ie what client you are using. You can check this further by checking the details of the outbound message in the SMTP activity/debug logs as this may supply more information. Also if you are not already please ensure that you are using the latest version of MailEnable as if you are sending using the web mail client which it appears that you are, then there may be a change that helps here already implemented.
Regards,

Product Services
MailEnable Pty Ltd

To keep track of all ME company updates and version releases you should subscribe to the MailEnable list at http://www.mailenable.com or the RSS feed http://www.mailenable.com/rss.

Post Reply