> the thing that actually burns my hash, is when my spam > complaints or noc correspondance are robotically bounced because they > contain dangerous mime attachments of type "message/rfc822" (spam > examples) or "text/plain" (traceroute or tcpdump output). if your noc > or abusedesk has such a robot protecting it, you ought to be ashamed.
Or they may be happy thinking their NOC is more 0day virus proof rather than hoping a 3rd party will update their scanner in time Who'd want to risk the NOC falling to the same problem that's just taken out the network they're trying to fix? brandon
