After a gap where I ran out of disk space and had to swap the raw spam archives out to another computer before I had time to collect IP numbers, but then that other computer admin deleted all my files, here are slightly later collections, in sequence (duplicates not removed, so there's a separate copy of the same IP number for each spam I got from that same IP number), no leading zeroes: uE uF uG uH uI uJ uK uL uM uN uO
The following is the current such feeder and is not yet complete: uP

For all the above, received on my ISP Unix shell account, I ran the whole process of sending a spam complaint to all known complaint addresses for that IP address block, and also sent slightly different complaint to single-upstream complaint address. If no CTW address was known, my softare automatically contacted SpamCop and/or ARIN/RIPE/APNIC to try to get the CTW address, and then automatically tested each such address to see whether it really accepted e-mail, before updating my CTW database. Only after it got at least one valid address did it then send the spam complaint. Often it required manual intervention to fix the info for one IP number before it could send that one complaint and move on to the next spam, causing many hours delay from when spam arrived until it was finally complained about. Furthermore, my complaints were sent through the usual means, so I had no way to hide my e-mail address from admins at spam havens, and no way to prevent the resultant flood of automatic acknowledgements of complaints and followup denials that they were at fault even when they clearly were. See later below for a better way.

Spam came to my AT&T wireless cellphone from the following IP numbers that I collected manually by re-keying from the screen of my cellphone: uatt

For the following spam that came to my ISP Unix shell account, I used a new quick-bounce method to automatically send my complaint to the already-known CTW address for the last-relay, or if that's not known then to the first upstream for which it's known, and using not my ISP address but a YahooGroups address so I wouldn't be flooded by auto-acks. Whenever the traceroute info is out of date by more than one week, it'd re-do the traceroute before proceeding with the spam complaint: 2002-A05 2002-B05 2002-C10 2002-C29 2003-111 2003-215 2003-308 2003-319 2003-410 2003-419 2003-425 2003-502 2003-507 2004-426

Above are complete sets. Below is the current unfinished set, which will be renamed whenever it's full: u-bounced

.

.

.