iBurst is blacklisted !!!

[GRES]

For the past two weeks:

======================================================
The following message to <*****@mail.ru> was undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 550-'Access from ip address 196.2.97.2 blocked. Visit
http://win.mail.ru/cgi-bin/support_bl?ip=196.2.97.2
====================================================
The following message to <******@bk.ru> was undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 550-'Access from ip address 196.2.97.2 blocked. Visit
http://win.mail.ru/cgi-bin/support_bl?ip=196.2.97.2
======================================================
The following message to <****@info.kiev.ua> was undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 553-'5.3.0 Unsolicited email from 196.2.97.2 refused
=======================================================

Again iBurst can't deliver PREPAID services!
And don't have brains to fix problem.

 

[mic_y]

GRES, whats up with all the mail to Russia and Ukraine?

You also Russian?

 

[NovA]

sounds like you are having problems with your iburst.any other problems with iburst?looking for a good ISP.mines not that reat.

 

[GRES]

Somebody from iBurst clients was sending spam. (interesting - what about common SMTP server, which has to solve outgoing spam problem?) ALL mail to Russia, Ukraine and some other countries is blocked by other parties. WBS can't solve this problem during past three weeks! We loose money as we can't contact our clients!
I have 3 questions to Luis, Ed, Shaun and others:
1. Why we need these restrictions and have to use WBS SMTP, which is not working and does not restrict sending of the spam?
2. Why WBS can't change SMTP IP for OUTGOING traffic?
3. Who will cower our losses from PREPAID services?

 

[The_Unbeliever]

Now what to do? It is every sysadmin's nightmare to find that his/her email server is blacklisted... even though all reasonable steps was taken to ensure that the server did not (or can't) send any spam. (You can, of course, change your static IP to another IP, but what if you don't have any static IP's left to use?

I think the time of blacklisting (or RBL) is past, it is an idea which outlived its usefulness... although you will still need to blacklist dynamic IP addresses allocated for dial-ups, to prevent all and sundry of spamming from computers which uses dynamic IP addresses.

Also, RBL is a sure-fire way of performing a DoS - all you do is spam a lot of people using a certain domain, then forward said domain to a RBL-listing site and then get that domain's IP blacklisted.

What I would do is to trace from which IP the spam is coming from, and then contacting said client, informing said client that there is a problem with his/her computer, and that he/she should get out a technician (or somebody who knows what to do) in order to have a look at the problem, and in the meantime, block said IP from sending mail out until the issue is resolved.

I'm using dspam which is a statistical spam filter, and already it is making a huge difference in controlling the influx of spam to the mail server.

Hope iBurst can sort their problems out.

Regards

TU

 

[LandyMan]

Just to jump in from the sideline ... that IP shown in the e-mail header ... that is a dynamic IP address for an iBurst connection. iBurst mail server is 196.30.31.203. So are you trying to send e-mail via your own SMTP server?

 

[GRES]

196.30.31.203 is IP for internal routing. It is for the users to send mail TO SMTP server at iBurst. Outgoing stream comes from 196.2.97.2 and all world see THIS IP, not 196.30.31.203!

 

[kingrob]

Gres,

Are you booking some fillies for Teazers? Last time I was there, it felt like I'm in Moscow...

Then iBurst better get things sorted VERY QUICKLY.