That's what happens when ISP's aren't careful about what happens on their
network. Getting your IP's on the black list is probably one of the worst
things you can let happen as an ISP. They warn you and give you time to
rectify the situation (cancel accounts/access of offenders) before they
actually add you to the list, which is impossible to get removed from.
Many sysadmins rely on the black list to keep their users from getting tons
of spam. It's funny to see the current list of ISP's who ignored the
warnings and got added. Another example of how clueless some of these big
companies really are.
I am totally surprised to see rackspace on the list. I always thought they
ran a pretty tight ship since they are probably one of the only large collo
companies actually making profit.
That is a drag! You shouldn't give up on the list though. It's not like
php.net has anything against rackspace users. They are just one of many who
make use of the blacklist. Use another email account or get a hotmail
account or something. The list needs you! :-)
----- Original Message -----
From: "Miguel Cruz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 27, 2002 2:24 PM
Subject: [PHP] failure notice (fwd)
> Is this for real? Rackspace hosts an awful lot of good-hearted people
> (including myself). Is there a specific reason why the entire ISP's
> customer base has been blocked from posting to php-general? I guess I have
> to give up participating on the PHP list...
> ---------- Forwarded message ----------
> Date: 27 Jul 2002 19:21:15 -0000
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: failure notice
> Hi. This is the qmail-send program at stoic.net.
> I'm afraid I wasn't able to deliver your message to the following
> This is a permanent error; I've given up. Sorry it didn't work out.
> <[EMAIL PROTECTED]>:
> 18.104.22.168 does not like recipient.
> Remote host said: 553 22.214.171.124/18 blocked by rackspace.blackholes.us
> Giving up on 126.96.36.199.
> --- Below this line is a copy of the message.
> Return-Path: <[EMAIL PROTECTED]>
> Received: (qmail 22694 invoked by uid 508); 27 Jul 2002 19:21:11 -0000
> Received: from localhost ([EMAIL PROTECTED])
> by localhost with SMTP; 27 Jul 2002 19:21:11 -0000
> Date: Sat, 27 Jul 2002 14:21:11 -0500 (CDT)
> From: Miguel Cruz <[EMAIL PROTECTED]>
> To: Tony Harrison <[EMAIL PROTECTED]>
> cc: [EMAIL PROTECTED]
> Subject: Re: [PHP] Re: Date() Problem
> In-Reply-To: <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> On Sat, 27 Jul 2002, Tony Harrison wrote:
> > I tried using UNIX stamps but it dont work, and why the hell does it
> > to that date anyway? I thought it was supposed to default to the current
> > time?
> Be very happy it works the way it does. Since it defaults to an
> easily-recognizable date and time, you can quickly tell when you've messed
> up your code.
> If you don't provide a second argument to date() at all, then it'll
> default to the current date and time.
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php