I also got such a message:
/--
----- The following addresses had permanent fatal errors -----
<[EMAIL PROTECTED]>
(reason: 554 5.7.1 Service unavailable; Client host [192.114.47.35] blocked
using rbl.eonspace.net; ;z; Dynam... blocked due to zombie infestation. See
http://rbl.eonspace.net/?rblip=192.114.44.226/21 for details)
\--
192.114.47.35 is one of our mailers. Somebody blocked a whole range
of "8 class-Cs" because of one zombie mail from a client of us.
Anyone doing such blocking in a large scale will loss much of his mail
connectivity, and I guess it may not be a good idea to have mail service
at an ISP with such a blocking policy.
http://rbl.eonspace.net/?rblip=192.114.44.226/21 (and even
http://rbl.eonspace.net or http://eonspace.net/) gives me a page with
only this sentence:
Put your new web site here
So I cannot see any more details on who blocked it and how to
unblock.
Amir
On Nov 30, 12:38, Amir Plivatsky wrote:
} Subject: Re: To: Ira / Warning: could not send message for past 10 hours (
> On Nov 30, 11:50, Oded Arbel wrote:
> } Subject: Re: To: Ira / Warning: could not send message for past 10 hours (
> > On Wed, 2006-11-29 at 22:36 +0200, Peter wrote:
> > > >> .. while talking to kelly.abramov.org.:
> > > >>>>> RCPT To:<[EMAIL PROTECTED]>
> > > >> <<< 451 ;z; Dynamic IP pool blocked due to zombie infestation. See
> > > >> http://rbl.eonspace.net/?rblip=192.114.44.226/21 for details
> > > >> <[EMAIL PROTECTED]>... Deferred: 451 ;z; Dynamic IP pool blocked due
> > > >> to zombie infestation. See
> > > >> http://rbl.eonspace.net/?rblip=192.114.44.226/21 for details
> > > >
> >
> > > One small nitpick: Some dolt blocked an IP block that is indeed zombied,
> > > but in fact it is two IP blocks. Both are in Bulgaria, and both are
> > > infested (you should see my webserver's log). BUT I am not in Bulgaria
> > > and I have an IP that is sandwiched between the Bulgarians, from Actcom.
> > > And I have no zombie here (at least not in the computer).
> >
> > I'm not sure if you are referring to the above quoted rejection, or to
> > something else, but the block 192.114.44.226/21 from which you tried to
> > send e-mail to Ira Abramov is indeed Actcom dial-up pool, which
> > rbl.eonspace.net blocks only this specific pool and nothing else (no
> > Bulgarians here).
>
> If you mean 192.114.40.0/21 (the /21 block which 192.114.44.226
> belongs to), the 192.114.44.0/24 range is indeed dynamic dialup
> (modem/ADSL). Most of the other IPs in this /21 are not dialup, so if
> somebody blocked the whole /21 it was according to a bad guess.
>
> Anyone that sends mail directly from his link needs a static IP,
> which PTR which is equal to his domain (the regular PTR
> something.broadband.actcom.net.il is blocked almost anywhere due to the
> "broadband" string and/or due to the IP in the "something" part).
>
> > > So
> > > trigger-happy blacklisters are not exactly my favorite hereoes. Never
> > > were. Who knows how many people do not get my email because of such
> > > things.
>
> If a user that needs direct mailing happens to have a blocked IP,
> we can just replace it (providing that it is a static IP). But EVERY
> IP has a very big chance to be BLOCKED SOMEWHERE (this can be even
> stated "every IP is blocked in really many places").
>
> Amir
>
> > I am personally not very happy with the situation where RBLs (mine
> > included) *need* to block dynamic IPs. I'm well aware that many people
> > (and many on this list) are running their own MTAs - and quite
> > legitimately - on their dynamic dial-up IP. Unfortunately, there is
> > simply no way to block zombies while not blocking such kosher setups,
> > and for that reason all MTAs support the option of relaying all outgoing
> > SMTP traffic through an ISP mail server, that will deliver your e-mail
> > correctly - because you already pay your ISP for this service. Not
> > taking advantage of a service you pay for and then complaining that you
> > get blocked is not, IMHO, a valid stance.
> >
> > --
> > Oded
> > ::..
> > Freshly reinstalled computers are a bit like a pair of new shoes -
> > you're happy that you've finally got a new pair, but they're awkward to
> > use for a little while.
> >
> >
> >
> > =================================================================
> > To unsubscribe, send mail to [EMAIL PROTECTED] with
> > the word "unsubscribe" in the message body, e.g., run the command
> > echo unsubscribe | mail [EMAIL PROTECTED]
>
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
