lawless Posted March 24, 2004 Share Posted March 24, 2004 I've just successfully configured one of my accounts for Mailhosts. What I see seems like something I've asked for and apparently many others have as well: A way to white-list the inbound mail relays. What I don't understand is how Mailhosts will help SC detect forged Received: headers from implicating innocent relays. Here's the passage from the first configuration page: Why? This is being done because of ongoing problems - spammers have finally begun doing what we have known they could do all along - create really convincing mail header forgeries. These forgeries make SpamCop think spam is being sent from innocent sites where it is actually not. Clearly, this must be stopped. Currently, only a few spam forgeries cause serious problems for SpamCop, but if this problem is not solved, it will become much worse. Even now, a few mis-identified innocent sites are a big problem. This system promises to eliminate the forgery problem forever, while also avoiding problems caused by other less-drastic attempts to mitigate the forgeries. However, it does require more involvement from SpamCop users. So how will the new approach prevent the first Received: header past the trusted chain from being a convincing forgery that implicates an innocent IP address? Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.