routing info on incoming e-mail?

You can't get rid of it, because it's required to send and route your email to you. If you see all the lines in Mail, they can be shortened to basic header information by selecting it in Preferences > Viewing. In that window, there's a pop-up menu where you can select None, Default, or All for the header information to show on incoming messages.

Mulder

I'm seeing this issue too, and I think you may have misinterpreted the symptom.
What I see is that this header information appears as if it were part of the message body (which it isn't, and shouldn't). It happens intermittently, in several (but not all) inbound emails daily. It's been happening since November 7, 2008. Other symptoms can appear at the same time, such as no apparent sender, or a garbled subject line.

I've traced the proximate cause to corruption in the email headers, which then confuses the parser that displays the message in OS X Mail, MobileMe Mail, and Thunderbird (on Windows XP).
When I examine the headers, the corruption appears to be the insertion of one or more newline characters, usually in the middle of the "Authentication-Results:" line, hence the appearance of "dkim=" shortly thereafter (that is, in what the mail reader parses (erroneously) as the first line of the message body.

The reason for the missing sender and garbled subject is that these header fields are after the corruption, so the display parser doesn't see them as part of the header, but rather as part of the body. Since it can't find these fields, it does the best that it can, with varying results.

At first it seemed as though this corruption was an artifact of have email forwarded from my AT&T/Yahoo mail account to my MobileMe account. After 4 hours of patient detective work with the folks at AT&T/Yahoo 2nd tier support, they couldn't reproduce it, and sent me to see whether the problem is happening somewhere inside MobileMe mail servers. Any ideas about how we can track this problem to its real source?

Here's an example.

The following header lines are before the corruption:

Return-path: <esc1102349045082 11014131013719243@in.constantcontact.com>
Received: from smtpin129-bge351000 ([10.150.68.129]) by ms271.mac.com (Sun Java(tm) System Messaging Server 6.3-7.02 (built Jun 27 2008; 64bit)) with ESMTP id <0KBB008C8KKCIQF0@ms271.mac.com> for myname@me.com; Wed, 03 Dec 2008 13:19:24 -0800 (PST)
Original-recipient: rfc822; myname@me.com
Received: from mta240.mail.mud.yahoo.com ([68.142.202.188]) by smtpin129.mac.com (Sun Java(tm) System Messaging Server 6.3-7.03 (built Aug 4 2008; 32bit)) with SMTP id <0KBB0089SKK7WH80@smtpin129.mac.com> for myname@me.com (ORCPT rickdinitz@me.com); Wed, 03 Dec 2008 13:19:24 -0800 (PST)
From:: esc1102349045082 11014131013719243@in.constantcontact.com
X-Brightmail-Tracker: AAAAAA==
Date-warning: Date header was inserted by smtpin129.mac.com
Date:: Wed, 03 Dec 2008 13:19:20 -0800 (PST)
Message-id: <0KBB0089TKK8WH80@smtpin129.mac.com>
Return-path: <esc1102349045082 11014131013719243@in.constantcontact.com>
X-RocketTIP: 63.251.135.115: NO TIP_HEADERALLOWED
X-RocketSRV: s ip=63.251.135.115;dt=1228339154;url=constantcontact.com, http://www.constantcontact.com,papie.org,mailto:mmerchant@papie.org,rs6.net,http ://rs6.net/on.jsp?t=1102349045082.0.1101413101371.9243&ts=S0375&o=http://ui.cons tantcontact.com/images1/s.gif,yahoo.com,mailto:s myname@yahoo.com;Retro=Y;
X-YMailISG: TpE8SeQtYB35yfgsx35C1IYZcSoM2EnpU1aQ1ZPkisVT.XrphzBitfZIg6q6hcDC19h2ERt60orVCSQ k3uvhdWEWb0gmyjz37ddVbZvJb QLmbTf7Gfs2.mGgj_WpNCc_nkuabZujoSL5vN5QRKph2h11mUkV31Fo5DZYW1R5ajBMiPH_I7e9jjuZb 0BEhCYWL19Z4Sj4CBpiRECELXCNE3dPsD8ZYR5Fj9xJ753oTGUbIhmWASjPUmjKe9Xe8nlyZUX1FgNbC6E2f6fdGz88.DdfQTEHU-
X-Rocket-Track: cat=GD; info=ip:GD<ip=63.251.135.115,policy=w-w100,n0,g0,s,wgn=w-w100,n0,g0,s,rep=w-w10 0,n0,g0>;ipsh:UK<ip=63.251.135.115,policy=P=-1,X=-1,S=-1>;ipst:GD<ip=63.251.135. 115>;url2db:NN<url=rs6.net>
X-Originating-IP: [63.251.135.115]
Authentication-Results: mta240.mail.mud.yahoo.com from=papie.org; domainkeys=neutral (no sig)

The following header lines are after the corruption (seemingly in the body). The opening semicolon seems to be either part of the corruption, or interpolated by the parser:

; from=papie.org; dkim=neutral (no sig)
Received: from 63.251.135.115 (EHLO ccm09.constantcontact.com) (63.251.135.115)
by mta240.mail.mud.yahoo.com with SMTP; Wed, 03 Dec 2008 13:19:14 -0800
Received: from p2-ws510.ad.prodcc.net (unknown [10.252.0.101])
by ccm09.constantcontact.com (Postfix) with ESMTP id C66FE24C0958
for <myname@yahoo.com>; Wed, 3 Dec 2008 16:06:06 -0500 (EST)
Message-ID: <1102349045082.1101413101371.9243.10.11160002@scheduler>
Date: Wed, 3 Dec 2008 16:06:06 -0500 (EST)
From: Obfuscated Name <sendersName@papie.org>
Reply-To: sendersName@papie.org
To: myname@yahoo.com
Subject: [PiE News] Season's Greetings from Partners in Education
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="----= Part_52205207443751027.1228338366806"
X-Mailer: Roving Constant Contact 0 ( http://www.constantcontact.com)
List-Unsubscribe: http://visitor.constantcontact.com/d.jsp?p=un&v=001M6t4uPDAuUqrro6AZ1U1-jqAQnQz1 RFbG-PJ2DRPTB6DEiJ2IntnAw==
X-Return-Path-Hint: ESC1102349045082 11014131013719243@in.roving.com
X-Roving-ID: 1101413101371.9243
X-Lumos-SenderID: 1101413101371
X-Roving-CampaignId: 1102349045082
X-Roving-StreamId: 0

------= Part_52205207443751027.1228338366806
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Season's Greetings from ...

Notice that now we're in the real body of the message.

You could try rebuilding the Mail index like this:

1. Quit Mail if it's running.
2. Go to Library/Mail and delete the Envelope Index file.
3. Restart Mail and wait for it to import your existing messages, then check to see if the problem continues.

Mulder

In my case, I'm fairly sure the problem is not even on my Mac, but rather at one or more of the MobileMe servers. The symptoms subsequently appear in the following separate places:
- In Mail on my iMac (10.5.5)
- In Mail on my MacBook (10.5.5)
- In the MobileMe mail webapp on my iMac
- In the MobileMe mail webapp on my (ugh) Windows XP box at work
- In Thunderbird on my (ugh) Windows XP box at work

In all cases, the same subset of messages is affected. The fact that the problem appears in the webapp tells me that the corruption is not on one of my machines, but at an Apple server (or perhaps even earlier in the mail chain). By the time the message is deposited in my account on a MobileMe server, it has already been corrupted.

That's possible, but then it should affect everyone, not just you. Have you checked all the possible options in MobileMe for displaying headers (or not) of email? You should do that to be sure you haven't overlooked something or accidentally set a preference incorrectly. If neither of those fit the situation, then I'd close this topic and post it in the MobileMe forum, or even contact support for MobileMe to see what they can do about it.

Mulder

Just by chance do you have an iPhone and have you installed an app called 'soonr'. I installed this app and since then Mail wanted to use port 80 for rs6.net, one posable thing you could try is not allowing Mail to use port 80?