[exim] 554 response showing up as a broken pipe

Hi folks,

I think I have a weird one. :)

My server acts as a spam filtering server for several clients. For one,
I occasionally get a message stuck in the queue when trying to deliver
to their server (via SMTP). The log entry looks as thus:

2005-10-05 13:32:46 1END88-00047n-Mm <= dmccluskey@???
H=mail2.lockton.com (mail1.lockton.com) [63.169.46.189] P=esmtp S=601899
id=D191045BD80840488D02A50CB25CB185D5A53A@???
T="FW: Lockton Benefits - FYI" from <dmccluskey@???> for
rmcgee@??? sturner@???

2005-10-05 13:32:47 1END88-00047n-Mm mail.ansoniacb.com [69.182.77.210]:
Broken pipe

I asked the client to check his logs and he said he didn't see anything.
Exim is treating this as a temporary failure so the message goes back
onto the queue.

So I ran a sniffer and did a flush and saw this in the output:

SMTP Response: 554 Too many header lines without null line separator for
message body

My main question is why didn't exim see the 554 response and deal with
it appropriately? Secondary question is what does the above error
really mean?

This is on Debian 3.1 w/ exim v4.50

Thanks,
mikeS

-- 
Michael F. Sprague     | mfs@???
http://www.saneinc.net | use STD::disclaimer;
System and Network Engineering (SaNE), Inc