PDA

View Full Version : SpamCop Blocking Futurequest email server


ultra
06-17-2005, 10:34 AM
I sent an emil this morning to an individual I have been writing without problem- when all of a sudden it was returned:

Remote host said: 550-Message rejected because rasmus.futurequest.net [69.5.3.3] is
blacklisted
550 at bl.spamcop.net see Blocked - see http://www.spamcop.net/bl.shtml?69.5.3.3
Giving up on


When I go to that site:

69.5.3.3 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 6 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)


What is going on- is my email no longer deliverable to anyone using such a program???????????

Deb
06-17-2005, 10:39 AM
* System has sent mail to SpamCop spam traps in the past week (spam traps are secret, no reports or evidence are provided by SpamCop) As stated in their notice... no method for us to do anything about it has been provided. We have no way of knowing what was sent to their secret spam trap, who sent it, or any other details for us to do anything. All we can do is wait for them to release the server.
What is going on- is my email no longer deliverable to anyone using such a program??????????? For anyone with an IP that spamcop is blocking for "whatever reason" trying to send to someone who uses the spamcop blacklist that does not have you whitelisted, then no, email to them will not get through. RBLs carry a double edged sword in that area. However, as a temporary work around to cover the next "6 hours" as the case should be, you can send email out using QuestMail since to my knowledge it is not blocked.

Deb
- Accused, Tried, Found Guilty but no one sent us an invitation to the trial :(

Deb
06-17-2005, 10:44 AM
P.S. it's not blocking all of the mail servers etc... just the RASMUS Community Server...the rest are still clear. If your package is not on RASMUS this would not affect it.

ultra
06-17-2005, 10:58 AM
The site is on RASMUS...I hope it does clear up within 6 hours-
I did see that the email server admin can delist it 1 time if they contact that site link.
I am using Qwest till then...

Melissa
06-17-2005, 07:18 PM
Just as a note... RASMUS has been cleared from the SpamCop block.

teach1st
07-11-2005, 06:06 PM
I just got one: 69.5.6.150 is in the spamcop data base.

To: PHP@tuff-teach.com
From: MAILER-DAEMON@hvm01.futurequest.net
Subject: failure notice

Hi. This is the qmail-send program at hvm01.futurequest.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.

<XX@places.pcsb.org>:
168.213.3.18 does not like recipient.
Remote host said: 571 - MAIL REFUSED - IP (69.5.6.150) is in RBL black list bl.spamcop.net
Giving up on 168.213.3.18.

--- Below this line is a copy of the message.

Return-Path: <PHP@tuff-teach.com>
Received: (qmail 7568 invoked from network); 11 Jul 2005 19:58:47 -0000
Received: from hanna.futurequest.net (69.5.16.3)
by hvm01.futurequest.net (69.5.6.150) with QMQP; 11 Jul 2005 19:58:46 -0000
Date: 11 Jul 2005 19:58:46 -0000
To: XX.pcsb.org
Subject: Action Required to Activate Membership for Tuff-Teach Forums!
From: "Tuff-Teach Forums Forums" <pcs@tuff-teach.com>
Message-ID: <200507111946.99c4a1119207@www.tuff-teach.com>
X-Priority: 3
X-Mailer: vBulletin Mail via PHP
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

sheila
07-11-2005, 06:14 PM
Hello Fred,

Yes, our HVM01 (High Volume Mailing 01) server is in the spamcop blacklist.

The information that SpamCop provides about this can be viewed here:

http://www.spamcop.net/w3m?action=checkblock&ip=69.5.6.150
69.5.6.150 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 3 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)

Basically, because *some* email was sent through the HVM01 server to a SpamCop spamtrap, they listed the server and will provide NO information to us whatsoever regarding the source of the email.

So there is nothing we can do except wait it out until the listing expires. :(

Believe me, we've tried to get SpamCop to provide us with details over these types of listings in the past, and they simply will not.

At least it looks like the listing will expire in about 3 hours. :\

sheila
07-11-2005, 06:15 PM
P.S. As an alternative, try sending the email by an alternate means (i.e. not via a PHP script). As long as it is sent by one of our other mail servers, it should not have this problem. Only the HVM01 server is blacklisted by SpamCop. The other servers are not.

teach1st
07-11-2005, 06:20 PM
P.S. As an alternative, try sending the email by an alternate means (i.e. not via a PHP script). As long as it is sent by one of our other mail servers, it should not have this problem. Only the HVM01 server is blacklisted by SpamCop. The other servers are not.
Thanks, Sheila. This is for vBulletin's automatic verification for new registrants. I have been e-mailing the new people by hand until spamcop expires.

Is there anything the FutureQuest community can do? Would it help if we complained to spamcop?

sheila
07-11-2005, 06:24 PM
This is for vBulletin's automatic verification for new registrants.
Yep...noticed that.

Is there anything the FutureQuest community can do? Would it help if we complained to spamcop?
Well, you know...sometimes when a person has tried and tried and tried, and no results from the effort have come, you just want to say to others "don't bother" or "give up". Because, believe me, we (FutureQuest staff) have tried (in the past). Also, there are many others who have voiced their opinions on this situation to SpamCop via their forums, newsgroups, and email.

And so far SpamCop hasn't changed on this position.

So...will it help if the FutureQuest community gets involved? I remain skeptical.

However, I guess you never know if you don't try. And who knows...if we did keep beating on their door, maybe eventually it would do some good.
:dunno: