ip Blacklisted, check yours

[zanass]

Hello Everybody

Check Here---> Email Blacklist Check - See if your server is blacklisted

You might want to start checking to see if you ip is blacklisted, not 2 days after this spamassasin was removed node 81 was blacklisted, Ben said this new spam blocker would help the blacklisting issue but it has made it worse.

Now they tell me I have to wait 4 weeks to get it unlisted.

Get ready folks, the water is rising.

Greg V

FYI Ben Ticket # NLR-910064

That's via something called backscatter.org which is not used in any of our configs nor have I ever heard of it so it's not anything major like spamcop etc. Most likely someone small who tagged something as spam from a mailing list etc.

This isn't related to my install as it still would have happened since Spamassassin does not spam outgoing email.

Mailservers get blacklisted due to the outgoing email rather then incoming. ASSP was running a version that doesn't support outgoing scanning but the new version installed 1.7 does. However, we are switching to ASSP Deluxe as stated before which adds all kinds of great features into your cPanel and has all outgoing email scanning enabled.

[zanass]

Originally Posted by H9Ben

That's via Spamhaus which normally charges for the removal.

This isn't related to my install as it still would have happened since Spamassassin does not spam outgoing email.

Mailservers get blacklisted due to the outgoing email rather then incoming. ASSP was running a version that doesn't support outgoing scanning but the new version installed 1.7 does. However, we are switching to ASSP Deluxe as stated before which adds all kinds of great features into your cPanel and has all outgoing email scanning enabled.

So you expect me to wait 4 weeks for that to get unblocked, Great selling feature.

Pay the man, your abusers, your bill

[zanass]

Create a node where only 10 emails can be sent per hour and I will be on it, What would happen if that company had hostnine.com blacklisted? YOU WOULD PAY THEM

[zanass]

My response from support on this matter:

Greg,

That blacklist is a scam. We have to wait till the IP is auto removed from their list. What they say on their site.

The listing will expire automatically and free of charge 4 weeks after the last abuse is seen from that IP.
Let us know if you need anything further, we'll be happy to help!

Thank you for choosing HostNine!

Regards,
Blake
HostNine Support

[Gene]

I have used MX Toolbox from zanass link often so am quite familiar with it. They check against over 100 blacklists, some of which are more reliable than others and some can get your mail blocked by the majors like Yahoo, Gmail etc.

Is your mail being blocked zanass? Being on the Backscatter list does not usually result in blocking by another MTA.

Backscatter is a major issue and major problem on the Internet. The current version of ASSP (1.7.2.1) is supposed to reduce backscatter because it blocks the spam and non deliverable mail at SMTP time with a 550 fail. It does not send a "delivery failure" to the "envelope from" address which is almost always forged.

Backscatter happens when the spammers/hackers/infants send their garbage to sucker @ somedomain.com and forge the return as gotcha @ otherdomain.com- the MTA from somedomain.com accepts the mail and then finds it doesn't have a sucker @ somedomain.com and that domain is set to send a "fail" message to the sender so the MTA sends a bounce to the forged address gotcha @ otherdomain.com which of course never sent the message. Backscatter would stop if the MTA just sent the message to /dev/null (that is, if it just discarded the message).

[zanass]

Originally Posted by Gene

I have used MX Toolbox from zanass link often so am quite familiar with it. They check against over 100 blacklists, some of which are more reliable than others and some can get your mail blocked by the majors like Yahoo, Gmail etc.

Is your mail being blocked zanass? Being on the Backscatter list does not usually result in blocking by another MTA.

Backscatter is a major issue and major problem on the Internet. The current version of ASSP (1.7.2.1) is supposed to reduce backscatter because it blocks the spam and non deliverable mail at SMTP time with a 550 fail. It does not send a "delivery failure" to the "envelope from" address which is almost always forged.

Backscatter happens when the spammers/hackers/infants send their garbage to sucker @ somedomain.com and forge the return as gotcha @ otherdomain.com- the MTA from somedomain.com accepts the mail and then finds it doesn't have a sucker @ somedomain.com and that domain is set to send a "fail" message to the sender so the MTA sends a bounce to the forged address gotcha @ otherdomain.com which of course never sent the message. Backscatter would stop if the MTA just sent the message to /dev/null (that is, if it just discarded the message).

Charter uses Backscatter and evertime someone on Charter sends me an email to my fredbear.com email address I do not get it because it's blocked, I have had this domain for 14 years it is my main email, this is not just a little problem.

Greg V

[Gene]

You can help reduce backscatter by turning on your default delivery. I had it off for awhile but created a junkbox @ ... account then go to it via webmail a couple of times a day and delete the garbage. I have sometimes found mail intended for someone in our org when the sender mistyped the address.

Unfortunatly the problem is the shared mail server IP and you have no controll over the other users that share the server.

On another note, I see a lot of bounces back to dictionary name @ mydomain.org. The kiddies are using my domain name and putting random characters before the @. The mail admins that get the spam don't look at the IP address that sent it, they look at the domain name. The domain name gets reported and resolved back to the shared server which did NOT send the garbage.

[zanass]

Originally Posted by Gene

You can help reduce backscatter by turning on your default delivery. I had it off for awhile but created a junkbox @ ... account then go to it via webmail a couple of times a day and delete the garbage. I have sometimes found mail intended for someone in our org when the sender mistyped the address.

Unfortunatly the problem is the shared mail server IP and you have no controll over the other users that share the server.

On another note, I see a lot of bounces back to dictionary name @ mydomain.org. The kiddies are using my domain name and putting random characters before the @. The mail admins that get the spam don't look at the IP address that sent it, they look at the domain name. The domain name gets reported and resolved back to the shared server which did NOT send the garbage.

Ben is working on a solution for me, and the way it's sounds it will work.

Thanks
Greg V

[zanass]

Posted this in the wrong thread, I do not have the right to delete it or edit it.

So now it's in the right place.

Ben has not fixed the blacklist issue on node 81 closed the ticket, stopped returning emails, where Charter blocks mail from node 81, most of my customers, family and friends send from Charter. He said he could move one of my accounts for me but not 4 of them, 300mb total on 4 accounts. So here I sit all brokin hearted....

Maybe he's not getting my emails, that's the only reason I could think of.

ZOOM, ZOOM

Can't wait for a TB server.

Greg V

RE: NLR-910064 ...support has 2 tickets in queue but no response to this ticket. Maybe there is a bug in the ticket system??