SpamCop 98 Posted October 20, 2012 Posted October 20, 2012 This parse reports "IPv6 addresses are not supported" yet there does not appear to be any IPv6. I believe it comes from this construction: Received: from rcboe-smtpfe.boe.richmond.k12.ga.us ([168.11.144.100]:47011 helo=MailGW1.richmond.k12.ga.us) Ideas?
SpamCopAdmin Posted October 21, 2012 Posted October 21, 2012 >- Received: from RCBOE-MAILBOX2.richmond.k12.ga.us ([fe80::acea:344a:a343:5a70]) That is the IPv6 line from the headers. The next SpamCop version will support IPv6. It should be out in a couple of months. - Don D'Minion - SpamCop Admin - - Service[at]Admin.SpamCop.net -
SpamCop 98 Posted October 21, 2012 Author Posted October 21, 2012 Thx! >- Received: from RCBOE-MAILBOX2.richmond.k12.ga.us ([fe80::acea:344a:a343:5a70]) That is the IPv6 line from the headers. The next SpamCop version will support IPv6. It should be out in a couple of months.
techie Posted December 27, 2012 Posted December 27, 2012 Thx! I wouldn't hold my breath. I expect that we'll see an attempt in a couple of months, which will fail, and be rolled back for another six months before they try again, which will be yet another failure. Given their current track record, I don't expect SC to have IPv6 working until at least March 2014. After all, SC has been unnecessarily broken with regards to IPv6 for 21 months now, and it needn't have been broken at all for many/most reports. The majority of the current problems with IPv6 reporting could be solved by changing where in the parsing process the IPv6 checking takes place, which I have pointed out several times before.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.