Paranoid2000 Posted May 15, 2006 Share Posted May 15, 2006 I cannot send emails to my wife because apparently the ISP that hosts her business email account uses SpamCop, and it is blocking Yahoo's mail servers and rejecting the emails. I have sent these to Yahoo who says "it's not our fault!" and post a link to the Spamcop FAQ which says there is no way to have your server removed from the blacklist. Well in this case it is their fault since they are not bothering to configure their server to stop bouncing emails to forged sender addresses. I include with my reports the following text "spam with forged sender address bounced to third party (see http://www.spamcop.net/fom-serve/cache/329.html#bounces and http://www.spamhaus.org/faq/answers.lasso?...20Spam%20Issues ) - actual source was..." so they cannot claim ignorance on this. Of course, the key blame should lie on the spammers doing this - it is a deliberate attempt on their part to damage the credibility of blocklists like SpamCop and to try to discourage people from using them, which in turn should indicate how effective they are. However mail server administrators do need to adapt to these changes in tactics and Yahoo is (so far) refusing to do this, continuing to pollute the Internet with their bounces. In this case, the best advice is to use another email provider who is more responsive and more responsible. I think this policy is ridiculous. Millions of people use Yahoo; why blacklist the email server that passes the emails through?Why should Yahoo be given special dispensation? If they serve millions of people then they should be more aware of the problems that misdirected bounces cause. SpamCop applies a higher threshold to known email servers before adding them to a blocklist so if Yahoo is present, it is because they are attracting more spam reports (I've sent a few).Shouldn't the individuals' IP addresses be blacklisted? This is causing great headaches and is probably causing my wife customers as well.If you mean the original spam source, then yes this should be blocklisted also - however if you view the Misdirected Bounces thread, you will see why this is not currently done by SpamCop. Reporters can analyze bounces manually and add the originating ISP to the report, but this does require more time and expertise. Perhaps an interim solution for SpamCop would be to allow "experienced" reporters to flag reports as misdirected bounces and list the original IP address for blocklisting? Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.