Failed to add new host: Client host [184.94.240.112] blocked using rep.mailspike.net

[Bernhard 0]

I tried to register the new mailhost sr30.firestorm.ch but the mail from spamcop was blocked using rep.mailspike.net (see screenshot)

I checked at mailspike.net:

Anything you can do about it?

Regards,

 Bernhard

 

 

[Lking 0]

Sense the blocking of spamcop mail to you is being blocked on your end by your software or your ISP's email applications, not sure what you expect spamcop to do.

There are many blocklist in use. Each BL has its own criteria for which IPs are on their list and for how long.  Perhaps you can work with your ISP to white list SpamCop.

[lisati 0]

@Bernhard:

I'm not sure why your server is blocking based on the mailspike "rep" (reputation) list. I had a look at their web page, and get the impression that it's not a general purpose list suitable for blocking everything from a listed IP address.

Mailspike's "bl" and "z" lists seem better suited to blocking/rejecting unwanted incoming emails.

[Bernhard 0]

Thanks for the answers.

I agree, that using bl.mailspike.org would make more sense than using rep.mailspike.org. However this wouldn't make any difference as the rating of vmx.spamcop.org is the same for both lists.

Trying to white list SpamCop with my ISP would only be a very partial solution. In my opinion SpamCop should take action to get delisted from rep.mailspike.org and bl.mailspike.org (just checked: 184.94.240.112 has still "Worst possible reputation" on both lists). Correct me, if I'm mistaken, but I reckon the whole process of reporting spam to SpamCop is crippled, if mail from SpamCop is not delivered to the corresponding site administrators due to SpamCop being blocked by other blacklists.

By the way: I just checked at mxtoolbox.com: SpamCop is currently also blacklisted with Backscatterer, Casa Cbl and Spfbl Dnsbl...

Edited August 17 by Bernhard