Jump to content

Sreiser

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sreiser

  • Rank
    Newbie
  1. Hi, I did not see anything in your FAQ saying SPAMCOP.NET blocks ISPs who happen to get blasted with viruses in email that get forwarded to an innocent unknowing end users email addresses list and then forwarded to the addresses in the last. That is the reason SpamCop.net blocked our ISP. I work for a major computer corporation IT department where we have three servers filtering all inbound email quite effectively. Hence, I am quite sick of spam and I want to see it ended as bad as you do, and if you are following what the w3 consortium is considering, there are couple options using IDs to validate either the domain or the user (one from Microsoft as well) that should do some serious damage to the SPAMMER market. Anyway, I just hope SpamCop.net blocks more REAL spam and not my whole ISP because endusers addresses get used against there will to forward viruses. Is that too unreasonable? Steve
  2. Derek, I read the FAQ and it did NOT address my issue at all. Steve
  3. Yes, it was absolutely thrilling!!!! Thank you! Actually both myself and my ISP did care and got it resolved.
  4. Hi. This is the qmail-send program at secure.wispertel.net. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <support[at]velocitywest.com>: 206.123.77.37 does not like recipient. Remote host said: 451 Blocked - see http://www.spamcop.net/bl.shtml?38.116.135.226 Giving up on 206.123.77.37. I'm not going to try again; this message has been in the queue too long. --- Below this line is a copy of the message. Return-Path: <avatar[at]wispertel.net> Received: (qmail 27923 invoked by uid 89); 12 Aug 2004 20:21:11 -0600 Delivered-To: wispertel.com-support[at]wispertel.com Received: (qmail 27921 invoked by uid 89); 12 Aug 2004 20:21:11 -0600 Delivered-To: support[at]wispertel.net Received: (qmail 27906 invoked from network); 12 Aug 2004 20:21:11 -0600 Received: from unknown (HELO ?192.168.0.100?) (38.116.140.252) by secure.wispertel.net with SMTP; 12 Aug 2004 20:21:11 -0600 Mime-Version: 1.0 X-Sender: avatar[at]wispertel.net[at]mail.wispertel.net Message-Id: <p06110402bd41d7600c67[at][192.168.0.100]> Date: Thu, 12 Aug 2004 20:27:51 -0600 To: support[at]wispertel.net From: Steven Reiser <avatar[at]wispertel.net> Subject: Hope this gets to you Content-Type: text/plain; charset="us-ascii" ; format="flowed" Hello, Lastnight I tried to email you an some site called "Spamcop.net wouldn't even let me talk to my own ISP and my email was rejected by Wispertel.net Steve
  5. Additionally, if Spamcop.net doesn't take remedial action, my next step is to contact my senators and congressmen at both the state and federal level about SpamCop.net.
  6. Hello, I just contacted the president of my ISP late tonight and emailed FTC.GOV about SPMACOP.NET. Not only did SpamCop.net prevent email to a friend but somehow interfered with me emailing to support[at]wispertel.net and I have an email account at wispertel.net. Furthermore, the reason listed here by SpamCop.net at this link: http://www.spamcop.net/w3m?action=blcheck&ip=38.116.135.226 .... is a lie. 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) DNS error: 38.116.135.226 is secure.wispertel.net but secure.wispertel.net is 66.250.22.25 instead of 38.116.135.226 Listing History It has been listed for 47 hours This is a lie because 66.250.22.25 is NOT secure.wispertel.net, but it is DNS.wispertel.net. As far as I am concerned SpamCop.net is FAR WORSE than the spam it's supposed to stop and I think Spammers belong in jail. Anyway, I would like to see action taken against such an abusive organization as SPAMCOP.NET. Steve
×