remay Posted June 22, 2004 Share Posted June 22, 2004 I had a particular spam email where spamcop would NOT detect the spammer's website URLs in the message body. This is NOT a MS Outlook "boundary" issue. But... there is SOMETHING in the headers of the spam email that spamcop didn't like, but I don't know what. When I used some other spam email's header, then spamcop detected the URLs just fine. I am not sure WHY spamcop wouldn't detect the links. Any ideas? It LOOKS like spamcop needs to be modified somehow, but I wasn't sure who to submit this to... Here are the URLs that spamcop eventually was able to detect in the spam, when I used a different set of email headers than the ones that came with the spam (below) to test things to see if ANY links could be detected. <snipped as results were gained with artificial headers> Here is the spam... Return-path: <ESC1011292925991_1011273013097_843[at]in.roving.com> Received: from ms-mta-03 (ms-mta-03-smtp.texas.rr.com [10.93.38.33]) by ms-mss-03.texas.rr.com (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0HZP00H569H53N[at]ms-mss-03.texas.rr.com> for x[at]houston.rr.com; Tue, 22 Jun 2004 02:43:53 -0500 (CDT) Received: from txmx03.mgw.rr.com (txmx03.mgw.rr.com [126.96.36.199]) by ms-mta-03.texas.rr.com (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0HZP007AX9H5F7[at]ms-mta-03.texas.rr.com> for x[at]houston.rr.com (ORCPT x[at]houston.rr.com); Tue, 22 Jun 2004 02:43:53 -0500 (CDT) Received: from samantha.asdf456.com ([188.8.131.52]) by txmx03.mgw.rr.com (8.12.10/8.12.8) with SMTP id i5M7hn1j021341 for <x[at]houston.rr.com>; Tue, 22 Jun 2004 03:43:49 -0400 (EDT) Received: (qmail 27431 invoked by uid 399); Tue, 22 Jun 2004 07:43:48 +0000 Received: (qmail 27416 invoked by uid 0); Tue, 22 Jun 2004 07:43:48 +0000 Received: from unknown (HELO ccm01.roving.com) (184.108.40.206) by samantha.asdf456.com with SMTP; Tue, 22 Jun 2004 07:43:48 +0000 Received: from sched2 (loghost2.roving.com [10.200.200.19]) by ccm01.roving.com (Postfix) with ESMTP id BD6C934AE0 for <x>; Tue, 22 Jun 2004 03:29:55 -0400 (EDT) Date: Tue, 22 Jun 2004 03:29:55 -0400 (EDT) From: Unicare Health Insurance <plukachekins[at]sbcglobal.net> Subject: Unicare Health Insurance of Texas To: x Reply-to: plukachekins[at]sbcglobal.net Message-id: <1011292925991.1011273013097.843.2.260342[at]scheduler> MIME-version: 1.0 X-Mailer: Roving Constant Contact 8.0.Patch805A (http://www.constantcontact.com) Delivered-to: x.x-x X-Roving-Queued: 20040622 03:43:47.657 X-Return-Path-Hint: ESC1011292925991_1011273013097_843[at]in.roving.com X-Roving-ID: 1011292925991 X-Lumos-SenderID: 1011273013097 X-Roving-CampaignId: 1011292925991 X-Roving-StreamId: 0 X-Virus-Scanned: Symantec AntiVirus Scan Engine Original-recipient: rfc822;x[at]houston.rr.com <head > <title >Unicare Health Insurance of Texas</title> </head> <body bgcolor=3D"#FFFFFF" style=3D"BACKGROUND-COLOR: #FFFFFF;MARGIN: 0px 0p= x 0px 0px;" ><!--Copyright © 1996-2004 Roving Software Incorporated d/b/a= Constant Contact. All rights reserved. Except as permitted under a separa= te written agreement with Constant Contact, neither the Constant Contact softw= are, nor any content that appears on any Constant Contact site, including but not limited to, web pages, newsletters, or templates may be r= eproduced, republished, repurposed, or distributed without the prior written permission of Constant Contact. For inquiries regarding repr= oduction or distribution of any Constant Contact material, please contact legal[at]constantcontact.com.--> <a ton of useless stuff deleted> <a href=3D" http://ccprod.roving.com/rov= ing/images/cc-logo-color-sm.gif"/></a></FooterLogo></font></td></tr><tr ><t= d colspan=3D"2" ><font face=3D"verdana,arial" size=3D"1" ><br /> www.get- healthinsurance.com | 5115 N. Galloway Ave | Suite 201 | Mesquite | TX | 75150= </font></td></tr></table></div></body> [Edited by Wazoo as the Original Poster didn't seem to want to, even after posting a Tracking URL in a later posting] Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.