[Resolved] Scheduled Maintenance - Parser Update

[Farelf]

From Richard W posting in Newsgroups

The SpamCop.net Reporting Service is scheduled to be offline and

unavailable for up to two (2) hours beginning at 9:00 a.m. PST (-0700)

on Tuesday February 12, 2013. The reason for the outage is to bring you

major update to the SpamCop.net Reporting Service, including the

capability for parsing and reporting IPv6 sourced spam and IPv6 address

space. The new version will show as SpamCop.net v4.7.0.111

The SpamCop.net website, including spamcop.net, www.spamcop.net,

members.spamcop.net and mailsc.spamcop.net will be down during the

upgrade. Emailed spam submissions will continue to be accepted but will

not be processed during the downtime. Once the service is brought back

online you can expect a delay of several hours as the backlog of spam is

processed.

The SpamCop mail service, newgroups and forums is not affected by this

scheduled outage and will continue to be available throughout the upgrade.

Thank you in advance for your patience

Richard

Event time announcer

[Farelf]

Started and finished on time, new version number v4.7.0.111 now heads parses, parser accepts IPv6 address headers (unallocated addresses observed going through), the stats graph picked up again without missing a beat on resumption. Looking good - Richard W replying to a query in the Newsgroups reports no issues so far.

Not sure if the RIPE query flag issue was also addressed in this update?

[Farelf]

The parser is still trundling along ... no comments about problems specific to the upgrade so, taking a leaf from the poet, "Had anything been wrong, we should certainly have heard," I'm marking this instance of the notification "Resolved". Not exactly a monument in marble ("To SpamCop v 4.7.0.111") but I echo petzl into the resounding silence "thanks to SC staff and the development engineers in Elbonia".

ENDEX

[cwg]

Not sure if the RIPE query flag issue was also addressed in this update?

Nope.

http://www.spamcop.net/sc?id=z5465566978z2...8b0f109bb1a162z

Tracking message source: 192.165.67.181:
Display data:
"whois 192.165.67.181[at]whois.arin.net" (Getting contact from whois.arin.net )
   Redirect to ripe
   Display data:
   "whois 192.165.67.181[at]whois.ripe.net" (Getting contact from whois.ripe.net)
   Lookup sasc4-ripe[at]whois.ripe.net
	  Display data:
	  "whois sasc4-ripe[at]whois.ripe.net" (Getting contact from whois.ripe.net)
	  sasc4-ripe =
   whois.ripe.net 192.165.67.181 (nothing found)
No reporting addresses found for 192.165.67.181, using devnull for tracking.

[cwg]

Still no luck fixing this?

Gets tiring to reach into the Ripe database manually and dig out the offending ip's email address's.