At 12/1/02 8:28 AM, Paul Gordon wrote: > >Received a bounce for a renewal reminder email from openSRS to a client who >obviously is running SpamCop on their server... > >>>>> MAIL From:<[EMAIL PROTECTED]> >><<< 550 Mail from 216.40.33.45 refused by blackhole site bl.spamcop.net > >Someone care to bitch-slap Spamcop?
The problem is not SpamCop per se, but one or more idiot SpamCop users who are reporting their domain expiration notices as spam: http://spamcop.net/w3m?action=checkblock&ip=216.40.33.45 The solution for this is for OpenSRS to make sure they're receiving the SpamCop notices, then take the action described here: http://spamcop.net/fom-serve/cache/167.html This will remove the idiot users from SpamCop, and the problem will go away. Someone at TUCOWS had better start reading, and handling, e-mail sent to [EMAIL PROTECTED] and [EMAIL PROTECTED] TUCOWS is also at fault here; this problem would not happen if that mail was properly handled. In particular, there is an entry in the SpamCop listing at: http://spamcop.net/sc?track=216.40.33.45 ... that indicates that 137 of the last 273 messages SpamCop has sent to [EMAIL PROTECTED] have bounced. (This is not a good sign for a company that aims to run a public e-mail service.) ------------------------------------ Robert L Mathews, Tiger Technologies
