Jump to content
Sign in to follow this  
Irata

Eudora and Exchange 2000

Recommended Posts

I have been submitting spam through the web interface for several years now without a problem. My mail client is Eudora. Very recently, my company switched to Exchange 2000 and now the headers are getting mangled. (I am using the two part "Eudora" submission) And of course, because the headers are mangled, spam Cop considers the submissions bad tracking. I haven't changed anything in the way I submit so the problem has to be that Exchange 2000 is doing something to the headers even before Eudora gets them.

Any suggestions on how to fix this?

TIA

Share this post


Link to post
Share on other sites

Can you post some sample headers? Email address & other personal information should be munged of course.

Share this post


Link to post
Share on other sites
Can you post some sample headers?  Email address & other personal information should be munged of course.

Sure!

Received: from usa0300bh01.na.xxxxx.net ([xxx.129.0.48]) by usa0300ms01.na.xxxxx.net with Microsoft SMTPSVC(5.0.2195.5329); Wed, 9 Jun 2004 20:12:26 -0400

Received: from mswitch1.cinops.xxxxx.com ([xxx.250.20.171]) by xxxxx.MC.USA.xxxxx.COM with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id LAY9DQXQ; Wed, 9 Jun 2004 20:12:23 -0400

Received: from CONVERSION-DAEMON.mgate.usa.xxxxx.com by mgate.usa.xxxxx.com (PMDF V6.2-X17 #30786) id <0HZ200001GKYFS[at]mgate.usa.xxxxx.com>; Wed, 09 Jun 2004 20:12:34 -0400 (EDT)

Received: from ariel.useastgw.xxxxx.com (ariel.useastgw.xxxxx.com [xxx.142.120.25]) by mgate.usa.xxxxx.com (PMDF V6.2-X17 #30786) with ESMTP id <0HZ200LL0GKXGM[at]mgate.usa.xxxxx.com>; Wed, 09 Jun 2004 20:12:34 -0400 (EDT)

MIME-Version: 1.0

Content-Type: text/html;

charset="us-ascii"

Received: from dyn-83-152-249-47.ppp.tiscali.fr (dyn-83-152-249-47.ppp.tiscali.fr [83.152.249.47]) by ariel.useastgw.xxxxx.com (8.12.9-20030917/8.12.9) with SMTP id i5A0BaEj018999; Wed, 09 Jun 2004 20:11:45 -0400 (EDT)

Received: from [201.152.38.97] by dyn-83-152-249-47.ppp.tiscali.fr with ESMTP id 54280897; Thu, 10 Jun 2004 06:04:20 +0500

content-class: urn:content-classes:message

Return-Path: <IMCEAx400-c=US+3Ba=telemail+3Bp=xxxxx+3Bo=USA+3Bdda+3ASMTP=f88sjtlbb+40yahoo+2Ecom+3B[at]xerox.com>

X-Mailer: Microsoft Outlook Express 6.00.2462.0000

X-MimeOLE: Produced By Microsoft Exchange V6.0.6529.0

X-OriginalArrivalTime: 10 Jun 2004 00:12:26.0155 (UTC) FILETIME=[9C31F7B0:01C44E7F]

Subject: **spam** This is Really Cheap! dxm xnnjxlmikshccc

Date: Thu, 10 Jun 2004 02:04:20 -0400

Message-ID: <0m0r2-91cqrk1-z0$9y422n-c-wu5[at]2rb54ya.tm8j>

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

Thread-Topic: This is Really Cheap! dxm xnnjxlmikshccc

Thread-Index: AcROf5rbNKwgPeLKSeC1MA1JIe69rQ==

From: "Felix Mayer" <f88sjtlbb[at]yahoo.com>

To: <xxxxx.xxxxx[at]xxxxx.com>

Reply-To: "Felix Mayer" <f88sjtlbb[at]yahoo.com>

X-SpamPal: spam CBL 83.152.249.47

Share this post


Link to post
Share on other sites

The problem appears to be the Content-Type header being improperly wrapped. Notice that the charset="us-ascii" portion of the header is on another line and that line is not indented. Line continuations MUST NOT begin in the first position of the next line.

Parsing 1 is the headers parsed as posted and shows the parser balking at the headers not being complete. I corrected the Content-Type header by adding a couple of spaces at the beginning of the second line and Parsing 2 shows the parser accepting the headers.

Share this post


Link to post
Share on other sites

...As I understand it, Microsoft Exchange/Outlook is known to mangle headers. Unless you know how to "fix" them (and, if you do "fix" them, you are advised to cancel [and manually report] rather than submit the spam through SpamCop), you should probably just delete them.

Share this post


Link to post
Share on other sites

And to make it worse, the end-user can beat his/her Outlook to death trying to "solve" some problems .. but the catch is that the Exchange server has many, many configurable items (to include not sending headers at all <g>) ... so there may be cause to drag the folks in charge of the Exchange server into the mix.

Share this post


Link to post
Share on other sites

Sooooooooo, is there anything that I can do so that SpamCop can read the headers? :(

Share this post


Link to post
Share on other sites
Sooooooooo, is there anything that I can do so that SpamCop can read the headers? :(

...My guess is: no (but I'm not expert). Whatever fails, I try to submit via the web-based submission form.

Share this post


Link to post
Share on other sites

All my submissions have been through the web interface. The attempts at email submission always fail miserably!

Share this post


Link to post
Share on other sites
Did you try to
drag the folks in charge of the Exchange server into the mix.
?

Unfortunately, this mail account is my work account and a Fortune 500 company. It would probably be easier to mate a Chiauau and a Great Dane together than to get them to modify their exchange server!

Share this post


Link to post
Share on other sites
Did you try to
drag the folks in charge of the Exchange server into the mix.
?

Unfortunately, this mail account is my work account and a Fortune 500 company. It would probably be easier to mate a Chiauau and a Great Dane together than to get them to modify their exchange server!

...FWIW, Irata is not alone in this regard! :( <frown>

Share this post


Link to post
Share on other sites
All my submissions have been through the web interface. The attempts at email submission always fail miserably!

...Bummer! :( <frown> Mine are more than 50% successful, I would say.

Share this post


Link to post
Share on other sites
Did you try to
drag the folks in charge of the Exchange server into the mix.
?

Unfortunately, this mail account is my work account and a Fortune 500 company. It would probably be easier to mate a Chiauau and a Great Dane together than to get them to modify their exchange server!

Then you are probably not going to ba able to report the spam you are receiving.

You started saying you have reported successfully prior to the Exchange servers being introduced, so I have to assume you know how to get the full headers. The only logical conclusion is that the headers are broken by that server to the point the parser can not parse them.

Spamcop has stated they need RFC compliant headers as a bare minimum starting pont for the parsing. If you can not provide those, spamcop will not work for you.

Share this post


Link to post
Share on other sites

Thanks, everyone. I guess I'll just keep trying and maybe some day possibly get lucky! :blink::(

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×