Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
blacklist not working
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- :
- blacklist not working
blacklist not working
03-05-2010 9:40 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hi, I have recently started receiving regular junk mail that is passing the spam filter (which I would expect as it looks like genuine mail) that is allegedly from one of my addresses, so I decided to blacklist the specific address.
My "mydomain.co.uk" is hosted at JTN with all mail forwarded to Plusnet "mydomain.plus.com" where the blacklisted address in question goes to a specific mailbox and all other addresses go to a catch-all.
According to the FAQ's reference to problem 55215, blacklisting mail destined for a specific mailbox should work. It appears to work fine if I impersonate "blacklisted@mydomain.co.uk" from an external account and send test mail to "blacklisted@mydomain.co.uk" with the same content as the spam in question (so should pass the edge filter), the mail gets blackholed. Unfortunately, it isn't working for the spam which is still getting through ... strange. Has anyone any ideas?
Header that gets past the blacklist -
**************************************************************************************************
Return-path: <jeannette.hage@akzonobel.com>
Envelope-to: blacklisted@mydomain.plus.com
Delivery-date: Mon, 03 May 2010 08:51:58 +0100
Received: from [212.159.7.103] (helo=mx.pcl-ipin04.plus.net)
by inmx22.plus.net with esmtp (PlusNet MXCore v2.00) id 1O8qRa-00059p-21
for blacklisted@mydomain.plus.com; Mon, 03 May 2010 08:51:58 +0100
Authentication-Results: mx.pcl-ipin04.plus.net; dkim=neutral (message not signed) header.i=none
Received-SPF: None identity=pra; client-ip=84.92.2.65;
receiver=mx.pcl-ipin04.plus.net;
envelope-from="xxxxxxxx@akzonobel.com";
x-sender="blacklisted@mydomain.co.uk";
x-conformance=sidf_compatible
Received-SPF: Fail identity=mailfrom; client-ip=84.92.2.65;
receiver=mx.pcl-ipin04.plus.net;
envelope-from="xxxxxxxx@akzonobel.com";
x-sender="xxxxxxxx@akzonobel.com";
x-conformance=sidf_compatible
Received-SPF: None identity=helo; client-ip=84.92.2.65;
receiver=mx.pcl-ipin04.plus.net;
envelope-from="xxxxxxxx@akzonobel.com";
x-sender="postmaster@xxxxxxxxxx.plus.net";
x-conformance=sidf_compatible
X-SBRS: 5.1
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYXALsd3ktUXAJBl2dsb2JhbAAKbgGQBQEBinxGdAEBAQEBCBUHM44tqxKCTwUZCIIdBA
X-IronPort-AV: E=McAfee;i="5100,188,5970"; a="325312136"
X-IronPort-AV: E=Sophos;i="4.52,318,1270422000";
d="scan'208,217";a="325312136"
Received: from mx.ironport.plus.net (HELO relay.pcl-ipout01.plus.net) ([84.92.2.65])
by mx.pcl-ipin04.plus.net with ESMTP; 03 May 2010 08:51:57 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am4tAIod3kvVomGh/2dsb2JhbAAKbgGQBQEBinxGgVCOLasYgk8FGQiCHQQ
Received: from just-the-name.co.uk (HELO mail.just-the-name.co.uk) ([213.162.97.161])
by relay.pcl-ipout01.plus.net with ESMTP; 03 May 2010 08:51:57 +0100
Received: from akzonobel.com (unknown [92.81.169.118])
by mail.just-the-name.co.uk (Postfix) with SMTP id 5A637404D63
for <blacklisted@mydomain.co.uk>; Mon, 3 May 2010 08:51:50 +0100 (BST)
To: <blacklisted@mydomain.co.uk>
From: <blacklisted@mydomain.co.uk>
MIME-Version: 1.0
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <20100503075150.5A637404D63@mail.just-the-name.co.uk>
Date: Mon, 3 May 2010 08:51:50 +0100 (BST)
X-PN-Virus-Filtered: by PlusNet MXCore (v5.00)
X-PN-Spam-Filtered: by PlusNet MXCore (v5.00)
**************************************************************************************************
My "mydomain.co.uk" is hosted at JTN with all mail forwarded to Plusnet "mydomain.plus.com" where the blacklisted address in question goes to a specific mailbox and all other addresses go to a catch-all.
According to the FAQ's reference to problem 55215, blacklisting mail destined for a specific mailbox should work. It appears to work fine if I impersonate "blacklisted@mydomain.co.uk" from an external account and send test mail to "blacklisted@mydomain.co.uk" with the same content as the spam in question (so should pass the edge filter), the mail gets blackholed. Unfortunately, it isn't working for the spam which is still getting through ... strange. Has anyone any ideas?
Header that gets past the blacklist -
**************************************************************************************************
Return-path: <jeannette.hage@akzonobel.com>
Envelope-to: blacklisted@mydomain.plus.com
Delivery-date: Mon, 03 May 2010 08:51:58 +0100
Received: from [212.159.7.103] (helo=mx.pcl-ipin04.plus.net)
by inmx22.plus.net with esmtp (PlusNet MXCore v2.00) id 1O8qRa-00059p-21
for blacklisted@mydomain.plus.com; Mon, 03 May 2010 08:51:58 +0100
Authentication-Results: mx.pcl-ipin04.plus.net; dkim=neutral (message not signed) header.i=none
Received-SPF: None identity=pra; client-ip=84.92.2.65;
receiver=mx.pcl-ipin04.plus.net;
envelope-from="xxxxxxxx@akzonobel.com";
x-sender="blacklisted@mydomain.co.uk";
x-conformance=sidf_compatible
Received-SPF: Fail identity=mailfrom; client-ip=84.92.2.65;
receiver=mx.pcl-ipin04.plus.net;
envelope-from="xxxxxxxx@akzonobel.com";
x-sender="xxxxxxxx@akzonobel.com";
x-conformance=sidf_compatible
Received-SPF: None identity=helo; client-ip=84.92.2.65;
receiver=mx.pcl-ipin04.plus.net;
envelope-from="xxxxxxxx@akzonobel.com";
x-sender="postmaster@xxxxxxxxxx.plus.net";
x-conformance=sidf_compatible
X-SBRS: 5.1
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYXALsd3ktUXAJBl2dsb2JhbAAKbgGQBQEBinxGdAEBAQEBCBUHM44tqxKCTwUZCIIdBA
X-IronPort-AV: E=McAfee;i="5100,188,5970"; a="325312136"
X-IronPort-AV: E=Sophos;i="4.52,318,1270422000";
d="scan'208,217";a="325312136"
Received: from mx.ironport.plus.net (HELO relay.pcl-ipout01.plus.net) ([84.92.2.65])
by mx.pcl-ipin04.plus.net with ESMTP; 03 May 2010 08:51:57 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am4tAIod3kvVomGh/2dsb2JhbAAKbgGQBQEBinxGgVCOLasYgk8FGQiCHQQ
Received: from just-the-name.co.uk (HELO mail.just-the-name.co.uk) ([213.162.97.161])
by relay.pcl-ipout01.plus.net with ESMTP; 03 May 2010 08:51:57 +0100
Received: from akzonobel.com (unknown [92.81.169.118])
by mail.just-the-name.co.uk (Postfix) with SMTP id 5A637404D63
for <blacklisted@mydomain.co.uk>; Mon, 3 May 2010 08:51:50 +0100 (BST)
To: <blacklisted@mydomain.co.uk>
From: <blacklisted@mydomain.co.uk>
MIME-Version: 1.0
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <20100503075150.5A637404D63@mail.just-the-name.co.uk>
Date: Mon, 3 May 2010 08:51:50 +0100 (BST)
X-PN-Virus-Filtered: by PlusNet MXCore (v5.00)
X-PN-Spam-Filtered: by PlusNet MXCore (v5.00)
**************************************************************************************************
Message 1 of 4
(2,257 Views)
3 REPLIES 3
Re: blacklist not working
03-05-2010 9:43 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Do you mind the x-sender being in an open forum for spammers to pick up.
Message 2 of 4
(1,135 Views)
Re: blacklist not working
03-05-2010 9:57 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hi Oldjim, I would guess that the x-sender has already been well and truly harvested but I've blanked it out to prevent further instances.
Thanks.
Thanks.

Message 3 of 4
(1,135 Views)
Re: blacklist not working
03-05-2010 5:09 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
When you say
Not sure about this, but it might help?
Chris
do you mean it is set up as an alias to that mailbox, or that the address has its own mailbox? If the latter, I suspect you will have to delete the mailbox first. Then set up the blacklisted address as an alias to abuse@..... to stop the spams going to your catch-all.
Quote the blacklisted address in question goes to a specific mailbox
Not sure about this, but it might help?
Chris
Message 4 of 4
(1,135 Views)
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page