Jump to content
Sign in to follow this  
RadicalDad

Has SpamCop stopped working with OL 2016?

Recommended Posts

SpamCop has not been my primary spam defense in years, though I still think it is helpful for items that get through my first line of defense.  As such I no longer use it often.  However, lately it doesn't seem to work at all anymore.  I currently use Outlook 2016 with an hosted Exchange email account from Rackspace.  I use the "Outlook work-around" submission form, as I have for years.  Over the last few months, every email I submit comes back with a chain error and then lists my email server as the source of the spam.  This happens despite the fact that a manual inspection of the headers seems to easily locate the source of the spam.  What's up?  How would I get the good folks at SpamCop to look at this problem and fix it?

I have included a sample header below that SpamCop failed to identify correctly.  (I've munged my own email address.)

Received: from MBX01D-ORD1.mex09.mlsrvr.com (172.29.128.27) by
 MBX01A-IAD3.mex09.mlsrvr.com (172.29.64.20) with Microsoft SMTP Server (TLS)
 id 15.1.466.34 via Mailbox Transport; Thu, 11 Aug 2016 09:23:31 -0400
Received: from MBX08D-ORD1.mex09.mlsrvr.com (172.29.128.37) by
 MBX01D-ORD1.mex09.mlsrvr.com (172.29.128.27) with Microsoft SMTP Server (TLS)
 id 15.1.466.34; Thu, 11 Aug 2016 08:23:30 -0500
Received: from gate.forward.smtp.dfw1a.emailsrvr.com (98.129.184.12) by
 MBX08D-ORD1.mex09.mlsrvr.com (172.29.128.37) with Microsoft SMTP Server (TLS)
 id 15.1.466.34 via Frontend Transport; Thu, 11 Aug 2016 08:23:30 -0500
Return-Path: Margaret.airbnb@web.de
X-spam-Threshold: 95
X-spam-Score: 0
X-spam-Flag: NO
X-Virus-Scanned: OK
Authentication-Results: smtp23.gate.dfw1a.rsapps.net x-tls.subject="/C=DE/O=1&1 Internet AG/ST=Rhineland-Palatinate/L=Montabaur/emailAddress=server-certs@1und1.de/CN=mout.kundenserver.de"; auth=pass (cipher=DHE-RSA-AES256-GCM-SHA384)
X-MessageSniffer-Scan-Result: 0
X-MessageSniffer-Rules: 0-0-0-9938-c
X-CMAE-Scan-Result: 0
X-CNFS-Analysis: v=2.2 cv=f/oKP66M c=1 sm=1 tr=0 a=J9iW0BsQKmAMyByeQJRqVw==:117 a=dPpJLUqbF35K/rvetBMnag==:17 a=kj9zAlcOel0A:10 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=ZZnuYtJkoWoA:10 a=7z1cN_iqozsA:10 a=8UQbOP9E4OwA:10 a=8UxHENTbAAAA:8 a=iULj8VCxAAAA:8 a=t-IPkPogAAAA:8 a=vkfOdcL3zsWbAprsECEA:9 a=OTMKNByFX4mrIdDY:21 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=DFKM4597GOBYINfd19fC:22 a=lhJ1iG1LLmzY52WcPWSZ:22 a=TwOW_m0CY6OjrxjWeTv9:22
X-Orig-To: xxx@xxx.com
X-Originating-Ip: [212.227.126.135]
Authentication-Results: smtp23.gate.dfw1a.rsapps.net; iprev=pass policy.iprev="212.227.126.135"; spf=pass smtp.mailfrom="Margaret.airbnb@web.de" smtp.helo="mout.kundenserver.de"; dkim=none (message not signed) header.d=none; dmarc=pass (p=nil; dis=none) header.from=web.de
Received: from [212.227.126.135] ([212.227.126.135:50090] helo=mout.kundenserver.de)
 by smtp23.gate.dfw1a.rsapps.net (envelope-from <Margaret.airbnb@web.de>)
 (ecelerity 4.2.1.51128 r(Core:4.2.1.5)) with ESMTPS (cipher=DHE-RSA-AES256-GCM-SHA384
 subject="/C=DE/O=1&1 Internet AG/ST=Rhineland-Palatinate/L=Montabaur/emailAddress=server-certs@1und1.de/CN=mout.kundenserver.de")
 id 55/A8-04197-15C7CA75; Thu, 11 Aug 2016 09:23:29 -0400
Received: from icpu1654.kundenserver.de (infong691.kundenserver.de [212.227.29.23])
 by mrelayeu.kundenserver.de (node=mreue007) with ESMTP (Nemesis)
 id 0MSCaM-1besQH3bWk-00TA7N; Thu, 11 Aug 2016 15:23:27 +0200
Received: from 213.233.103.12 (IP may be forged by CGI scri_pt)
    by icpu1654.kundenserver.de with HTTP
    id 00pceB-1aswho3PUh-00pgMa; Thu, 11 Aug 2016 15:23:27 +0200
X-Sender-Info: <631182478@icpu1654.kundenserver.de>
Precedence: bulk
Date: Thu, 11 Aug 2016 15:23:27 +0200
To: <xxx@xxx.com>
From: =?UTF-8?Q?Airbnb?= <Margaret.airbnb@web.de>
Subject: =?UTF-8?Q?Margaret_shared_a_message_with_you?=
Message-ID: <480e3179694b5bb31c7c4c22f6ba3202@huchtemeier64.de>
X-Priority: 3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="us-ascii"
X-Provags-ID: V02:K0:Ma/Ac8g3zv5SBujKvpScUL0GbMSmOlSViwx1LnGyibR
 zFrM/AceXlYYjtyCLelvcqWlmAwffOR8OW7/sYEC62AJSLn8zg
 KHb99SIvFrvxY4bjuMvT5QsudUSd5g3YRo/FnGj58OXQ1c2K4A
 3p0v+LOBtVDlAENQluNT8bAMttLHYDmlDG84ie2BmstRBCLBl0
 9IfdMfJQg4oWCuq7OU1IBuLL0EChD0E2bPfjD5dxiX7iDI0rmk
 nU5bo9Yo+ii5rnPtTII1PugbuMgj+IMyDWts91CVRckv+G2EnD
 Ii6HQ5K7MhRrrRvqp535tHmLw1VmHJD219jSIfYeZwDmFH0W89
 edKOOr++w067/DPqujTfq7AmwP7Hm09pC2bDIkq7Ts5/oBOUGK
 IXv7Xc7d55hmBbyQO/6K9FZlrt79wQ5/Xbm9FmHnT1woHf9UqE
 FSRYk
X-UI-Out-Filterresults: notjunk:1;V01:K0:rFyF6mr3dnE=:y6bUMGMOgMGjuwX6cdNFLa
 fCxP3brxIg4GU0U+nDy+EAkHJgNQZZ8Q54aYkk38apNfpi/Q8Uxs5PfM/R1ZOZ4PQYYhvjTEt
 +RW0mn2W2EgEv93lm+SrCkGYE/fpqU2LONqUguQIL92P9xUq5YWddDvpqtHfd+Zh3NSYqYT7O
 UD/0Kx3cAzQ+fMvyRYSdneW16RlMOV+KgL6y3y9NpguJuEQ6q/Ccyg26qTl8f/G6ZTpiRj3rW
 RH0wVRWXlRYTyXplX76BStuy8KBgxk+R9IFlAjcAzba2yriUhzh+9z9oJ4=
X-MS-Exchange-Organization-Network-Message-Id: c8a1db1a-3714-4790-37a3-08d3c1eaafe5
X-MS-Exchange-Organization-AVStamp-Mailbox: SMEXw]nP;1270700;0;This mail has
 been scanned by Trend Micro ScanMail for Microsoft Exchange;
X-MS-Exchange-Organization-SCL: 0
X-MS-Exchange-Organization-AuthSource: MBX08D-ORD1.mex09.mlsrvr.com
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Transport-EndToEndLatency: 00:00:01.1034958
 

Share this post


Link to post
Share on other sites

I'm guessing you need to update your mailhost configuration.  SpamCop doesn't have any magical powers to know which servers are or aren't "your ISP".  It works by sending an email to you directly, and noting which servers are involved.  If anything in your mailflow has changed, you'll need to redo your mailhost config to make SpamCop aware of the new setup.

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  

×