mslw Posted January 8, 2014 Share Posted January 8, 2014 http://www.spamcop.net/sc?track=70.33.246.10 gives a bouncing reporting address postmaster[at]hostpapasupport.com, but clicking "[refresh/show]" , i.e. http://www.spamcop.net/sc?action=rcache;ip=70.33.246.10 says that it will use abuse[at]peer1.net. Why doesn't it use the address that it finds? Link to comment Share on other sites More sharing options...
SpamCopAdmin Posted January 9, 2014 Share Posted January 9, 2014 Fixed! Thanks! - Don D'Minion - SpamCop Admin - - service[at]admin.spamcop.net - Link to comment Share on other sites More sharing options...
mslw Posted January 9, 2014 Author Share Posted January 9, 2014 Thanks, though hardwired addresses like this look very wrong to me. Is the SC code frozen forever now or is it still being improved to fix problems like this? Link to comment Share on other sites More sharing options...
Farelf Posted January 9, 2014 Share Posted January 9, 2014 Don may have a different slant on it but it seems to me that with (sometimes) over a million parses a day - over 2.5 million today! - and with many report addresses manually over-ridden for a variety of reasons, SC will always rely on sharp-eyed reporters such as yourself to get these minority instances back on track mslw. Thanks for that! Oh, and I suppose the increasing fragmentation and volatility of IPv4 address allocations isn't helping in the business of keeping up with the routing either. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.