Vanguard,

I found the problem (and your post helped me to sniff it out) but so far the
company hasn't fixed it.

You were in fact right when you said:

"My guess is the X-SPAM-STATUS header. Was that the one you deleted (along
with its continuation lines) to get it to work?"

However, your thought about it being the length of the header wasn't it. I
changed things around so that the header was only about 30 characters and
the problem persisted.

What it ended up being was that the X-SPAM-STATUS headers are getting put in
the middle of other headers, so that most are above, but Errors-To,
X-Errors-To, REPLY-TO, and CC: all end up BELOW the X-SPAM-STATUS. When
I manually moved these headers above (with all the other headers), that
piece of mail would work just fine, even with the X-SPAM-STATUS headers
still in the email. Strangely, this ONLY affects OE and Outlook.

No resolution from the software vendor (True North Software) but I thought I
should post what I had found in case it helps anyone else.

Thanks to all for the effort to help, it is much appreciated.

Joe






"Vanguard" wrote in message
...
"Joe" wrote in message
...
Vanguard! I think you led me to where the problem was!

I took two headers, one from a working email and one from a non-working
one. The one thing I hadn't noticed was that the working mails all came
from the same server as the list and the non-working ones were all
remote. The server runs spam assassin, and doesn't look at local mail,
only incoming mail. Because of this, incoming mail has some headers that
local mail doesn't.

So.... I opened one of the non-working emails with notepad and edited out
the extra headers and then dragged it back into OE and VOILA!... it
worked as it was supposed to!

It looks like the intoduction of these headers messes up Microsoft mail
clients, even though every other client I've tried works perfectly.

I'll include a (sanitized) version of the headers below, just in case you
are curious. Thanks for the help.

Joe

(THIS IS ONE THAT WORKS)

Received: from kristen ([xxx.191.36.86]) by ddddd.net ( IA Mail Server
Version: 5.3.4. Build: 2019 ) ; Thu, 15 Dec 2005 00:38:49 -0500

Message-ID: 00cd01c6013a$6c9346c0$0302a8c0@kristen

From: "Kristen Lumsden"

To: "The Murphy Family Chat"

Subject: Meg's household?

Date: Wed, 14 Dec 2005 21:43:04 -0800

MIME-Version: 1.0

Content-Type: multipart/alternative;

boundary="----=_NextPart_000_00CA_01C600F7.5D56CE90"

X-Priority: 3

X-MSMail-Priority: Normal

X-Mailer: Microsoft Outlook Express 6.00.2900.2180

X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180

X-Antivirus: avast! (VPS 0550-2, 12/14/2005), Outbound message

X-Antivirus-Status: Clean

Errors-To:

X-Errors-To:

REPLY-TO: "The Murphy Family Chat"

CC:

List-Post: NO (We are sorry, but posting to this mailing list is
restricted.)



This is a multi-part message in MIME format.



------=_NextPart_000_00CA_01C600F7.5D56CE90

Content-Type: text/plain;

charset="iso-8859-1"

Content-Transfer-Encoding: quoted-printable







(THIS IS ONE THAT DOES NOT WORK)



Received: from web35204.mail.mud.yahoo.com ([xx.163.179.83]) by ddddd.net
( IA Mail Server Version: 5.3.4. Build: 2019 ) ; Fri, 16 Dec 2005
09:49:08 -0500

Received: (qmail 5490 invoked by uid 60001); 16 Dec 2005 14:54:45 -0000

Message-ID: .com

Received: from [xx.176.8.139] by web35204.mail.mud.yahoo.com via HTTP;
Fri, 16 Dec 2005 06:54:44 PST

Date: Fri, 16 Dec 2005 06:54:44 -0800 (PST)

From: Mary Murphy

Subject: Fw: From Jess -- please share

To: "The Murphy Family Chat"

In-Reply-To: t

MIME-Version: 1.0

Content-Type: multipart/alternative;
boundary="0-1658967278-1134744884=:5049"

Content-Transfer-Encoding: 8bit

X-SPAM-STATUS: No,SpamAssassinReport=Spam detection software, running on
the system "email", has scanned

this message. For more information contact the administrator
of that system

Content analysis details: (-196.0 points, 6.0 required)

pts rule name description

---- ---------------------- --------------------------------------------------

0.1 HTML_MESSAGE BODY: HTML included in message

2.7 FAKE_HELO_YAHOO Host HELO did not match rDNS:
yahoo.com

1.2 FORGED_YAHOO_RCVD 'From' yahoo.com does not match
'Received' headers

-100 USER_IN_WHITELIST From: address is in the user's
white-list

-100 USER_IN_WHITELIST_TO User is listed in 'whitelist_to'



Errors-To:

X-Errors-To:

REPLY-TO: "The Murphy Family Chat"

CC:

List-Post: NO (We are sorry, but posting to this mailing list is
restricted.)



--0-1658967278-1134744884=:5049

Content-Type: text/plain; charset=iso-8859-1

Content-Transfer-Encoding: 8bit






My guess is the X-SPAM-STATUS header. Was that the one you deleted (along
with its continuation lines) to get it to work? You didn't mention ones
you deleted to get it working. If that non-standard header, inserted by
SpamAssassin, I presume, cannot manage to get all of its content in one
line (and, I think, there is something like a 980-byte line-length limit)
then it should add an X-SPAM-STATUS2 header with the 2nd line, an
X-SPAM-STATUS3 header with the 3rd line, and so on. It looks like
whomever configured SpamAssassin added an informational message that is
far too huge and doesn't provide the headername: prefix on each newline.

I really doubt ANY of your users really care about YOUR listserver
checking for incoming spam. You not getting spam won't do anything about
them not getting spam, and they will have implement their own anti-spam
measures, anyway. It really is a superfluous huge message.

--
__________________________________________________
Post replies to the newsgroup - Share with others.
E-mail: Remove "NIX" and append "#LAH" to Subject.
__________________________________________________