This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: CVS checkout aborted


By the way, Bob, I sure hope you read the gdb list, because my e-mail
to you was blocked with this error:

<bob@brasko.net>:
216.40.250.211 does not like recipient.
Remote host said: 554 Service unavailable; Client host [209.128.65.135] blocked using l1.spews.dnsbl.sorbs.net; ! [1] ReliaHost, see http://spews.org/ask.cgi?S3046
Giving up on 216.40.250.211.

I looked into this a bit.  The spews evidence file has this in it:

1, 209.128.64.0/23, bayarea.net (promohost.org)
2, 209.128.64.0/18, bayarea.net via yipes.com feed (promohost.org)

This is absurd, since my e-mail server, at 209.128.65.135, is in a
co-location site shared by many different organizations.  It wouldn't
shock me if some of the other systems at that co-lo generate spam, but
blocking the entire range is moronic.

According to the spews FAQ, there is no way to contact them to correct
the situation.  They recommend that I contact my ISP to get them to
change their acceptable use policy, or that I change ISPs.  I will do
that, but blocking my e-mail because my e-mail server happens to be
close to one which generates spam is like blowing up a city block
because somebody on it happens to be criminal.  Damaging innocent
parties is immoral; you can't excuse it by explaining that you really
mean to damage somebody else.  In this, of course, you are being
damaged as well as me.

I strongly recommend that you stop using spews.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]