View Full Version : Email Servers On Spamcop blacklist
Hi
Just to let you know that some (not all) of NTL's email servers are on spamcops blacklist. So a % (somebody like to hazard a guess, ive been told maybe above 50%) of your email will never be delivered to its recipent (unless there on the NTL network) are ntl going to get this sorted.
Toytown
Charlie_Bubble
17-02-2004, 01:24
Doesn't surprise me. Spam seems to be a long way down NTL's 'things to be the least bit bothered about' list. The amount of spam I get is ridiculous and it's not just directed at me. I see dozens of other ntlworld.com email addresses in the 'to' box. A lot of these spam emails are faked to look like they come from NTL emails so it's not surprising that the servers are going to start showing up on anti-spam listings.
It's hardly surprising - ntl's mail servers are some of the busiest in the UK.
However, they don't accept smtp connections from IP ranges *outside* their own network blocks, (i.e aren't open relays), and employ a spam harvesting algorithm to stop customers using dictionary attacks.
quoting from the Spamcop website: "This blocking list is somewhat experimental. This system and most other spam-filtering systems should not be used in a production environment where legitimate email must be delivered."
"The description of the algorithm used for deciding whether to block a host may be out of date, and is subject to change without notice.There is no warranty associated with using this system. It is provided as is."
It appears that mta08-svc.ntlworld.com has been placed on the blacklist due to the amount of email it sends. It's a mail server for one of the UK's largest ISPs, it always sends a huge volume of emails a day.
If you find your emails being bounced/blocked I'd recommend talking with the admins of the receiving ISP.
Who's been a naughty boy then?
Reason: 212.250.162.8 listed at bl.spamcop.net212.250.162.8 PTR record: mailhost.ntl.com. [TTL 86400s] [A=212.250.162.8, 212.250.162.6]
This is a might inconvenient - will have to resort to old dog-and-bone now!
I've also had legitimate mails blocked because of Spamcop blacklisting though interestingly one address is mainly accepted, sometimes rejected. How does that work then?!
212.250.162.8 not listed in bl.spamcop.net
not any more ;)
Many automated lists expire blocks after some time, it saves having to administer removals.
Some do only clear it on request, and some (personal, not recommended for production use) make highly opinionate judgements on large address blocks and whole ISP's (actually, for personal use, blocking the entire APNIC administered address range and the entire 24.x.x.x US cable ISP range would nuke 99% of spam, though possibly some wanted stuff too).
Mike Harrison
17-01-2005, 13:43
I've had a few messages from ntl users today that Mailwasher shows as blacklisted by spamcop.
yup the mail servers have been blacklisted by spamcop again :rolleyes:
212.250.162.8 listed in bl.spamcop.net (127.0.0.2)
If there are no reports of ongoing objectionable email from this system it will be delisted automatically in approximately 22 hours.
Causes of listing
* System has sent mail to SpamCop spam traps in the past week (spam traps are secret, no reports or evidence are provided by SpamCop)
Additional potential problems
(these factors do not directly result in spamcop listing)
* System administrator has already delisted this system once
Because of the above problems, express-delisting is not available
Listing History
In the past 72.1 days, it has been listed 18 times for a total of 4.0 days
Other hosts in this "neighborhood" with spam reports
212.250.162.16
Dispute Listing
If you are the administrator of this system and you are sure this listing is erroneous, you may request that we review the listing. Because everyone wants to dispute their listing, regardless of merit, we reserve the right to ignore meritless disputes.
Dispute listing of 212.250.162.8
taken from: http://www.spamcop.net/w3m?action=checkblock&ip=212.250.162.8
This is having a serious effect on my emails. Is there no one able to sort this out?
Oh hell, here we go, better get the dust off Bertie the carrier pidgeon.
212.250.162.8 not listed in bl.spamcop.netWell done someone!
Now can we shoot the customer who's causing all this grief? :D
If there are any spamtraps (or do they mean user reports) on the NTL network, it seems that an innocent "intermediate" mailhost is being tagged...
Return-Path: <dykhu@lostcitadel. (dykhu@lostcitadel.com)>
Received: from aamta02-winn.mailhost.ntl.com ([212.250.162.8])
by mta10-winn.mailhost.ntl.com with ESMTP
id <20050116194927.KZHQ15581.mta10-winn.mailhost.ntl.com@aamta02-winn.mailhost.ntl. (20050116194927.KZHQ15581.mta10-winn.mailhost.ntl.com@aamta02-winn.mailhost.ntl.com)>
for <*****@ntlworld. (*****@ntlworld.com)>; Sun, 16 Jan 2005 19:49:27 +0000
Received: from lostcitadel.com ([69.40.140.63])
by aamta02-winn.mailhost.ntl.com with SMTP
id <20050116194926.QBNG3760.aamta02-winn.mailhost.ntl.com@lostcitadel. (20050116194926.QBNG3760.aamta02-winn.mailhost.ntl.com@lostcitadel.com)>
for <*****@ntlworld. (*****@ntlworld.com)>; Sun, 16 Jan 2005 19:49:26 +0000
Return-path: <dykhu@lostcitadel. (dykhu@lostcitadel.com)>
From: Barbara Vieger <dykhu@lostcitadel. (dykhu@lostcitadel.com)>
To: <*****@ntlworld. (*****@ntlworld.com)>
Subject: Barbara Samurai MNEI St0ck Info raunchy
Date: Sun, 16 Jan 2005 13:51:45 -0600
Reply-To: <dykhu@lostcitadel. (dykhu@lostcitadel.com)>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: plain
Message-Id: <20050116194926.QBNG3760.aamta02-winn.mailhost.ntl.com@lostcitadel. (20050116194926.QBNG3760.aamta02-winn.mailhost.ntl.com@lostcitadel.com)>
X-Antivirus: AVG for E-mail 7.0.300 [265.6.13]
The source IP does not tally:
69.40.140.63 = h63.140.40.69.ip.alltel.net (Proxy/Trojan according to CBL - abuseat.org )
Munged my email, and every ".com", to avoid giving spam harvesters targets that are reachable, if not valid
As anyone who has read any of my other posts regarding anything vaguely technical will know, I'm a bit thick in this area. So can anyone explain the mail failure message from the NTL postmaster below, preferably in words of on syllable! Does Spamcop have a problem with NTL or the recipent, telegraph.co.uk?!
Cheers,
Andy
Reporting-MTA: dns; mta10-winn.maildmz.private.ntl.com
Arrival-Date: Fri, 21 Jan 2005 10:33:42 +0000
Received-From-MTA: dns; aamta04-winn.mailhost.ntl.com (212.250.162.8)
Final-Recipient: RFC822; <robert.peston@telegraph.co.uk>
Action: failed
Status: 5.1.3
Remote-MTA: dns; relay2.telegraph.co.uk (193.115.165.42)
Diagnostic-Code: smtp; 553 5.3.0 Spam blocked, see: http://spamcop.net/bl.shtml?212.250.162.18
As anyone who has read any of my other posts regarding anything vaguely technical will know, I'm a bit thick in this area. So can anyone explain the mail failure message from the NTL postmaster below, preferably in words of on syllable! Does Spamcop have a problem with NTL or the recipent, telegraph.co.uk?!
Cheers,
Andy
Reporting-MTA: dns; mta10-winn.maildmz.private.ntl.com
Arrival-Date: Fri, 21 Jan 2005 10:33:42 +0000
Received-From-MTA: dns; aamta04-winn.mailhost.ntl.com (212.250.162.8)
Final-Recipient: RFC822; <robert.peston@telegraph.co.uk>
Action: failed
Status: 5.1.3
Remote-MTA: dns; relay2.telegraph.co.uk (193.115.165.42)
Diagnostic-Code: smtp; 553 5.3.0 Spam blocked, see: http://spamcop.net/bl.shtml?212.250.162.18
Spamcop has the problem with ntl-> details from spamcops site:
212.250.162.18 listed in bl.spamcop.net (127.0.0.2)
If there are no reports of ongoing objectionable email from this system it will be delisted automatically in approximately 20 hours.
Causes of listing
* System has sent mail to SpamCop spam traps in the past week (spam traps are secret, no reports or evidence are provided by SpamCop)
* SpamCop users have reported system as a source of spam about 30 times in the past week
Cheers Monkey,
I've contacted Spamcop to register dissatisfaction. Isn't there something NTL could do about this, like to take legal action. Spamcop is interfering with the operations of a legitimate business.... and hacking me off!
Andy
Wahey! Success! OK, it might be short lived, but this message (plus the irate one I sent to prompt it) from Spamcop.....
The problem with the new NTL servers has been resolved. Your mail should
go through OK now.
- Don -
>STOP BLACKLISTING NTL'S MAIL SERVERS. NTL HAS MILLIONS OF CUSTOMERS IN
>THE
>UK AND YOU ARE NOT ENDEARING YOURSELVES TO THEM. WE ALL WANT TO CUT SPAM
>BUT THIS IS NOT THE WAY TO DO IT.
>--
>This email generated by SpamCop web support form
>
Wahey! Success! OK, it might be short lived, but this message (plus the irate one I sent to prompt it) from Spamcop.....
The problem with the new NTL servers has been resolved. Your mail should
go through OK now.
- Don -
>STOP BLACKLISTING NTL'S MAIL SERVERS. NTL HAS MILLIONS OF CUSTOMERS IN
>THE
>UK AND YOU ARE NOT ENDEARING YOURSELVES TO THEM. WE ALL WANT TO CUT SPAM
>BUT THIS IS NOT THE WAY TO DO IT.
>--
>This email generated by SpamCop web support form
>
Nice.
Spamcop, not a bad bunch of folks, well intentioned, and they will admit that their current blocking script should not be used as an absolute benchmark for preventing spam.
:)
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.