We received the following email, with an incredible number of email addresses in the cc: field. We did not even get the original message. Maybe someone has a virus on their computer? I am guessing this is every NOC email address in someone's address book. The email caused us to receive 45 auto-replies from around 5 different domains, that were forwarded to us (and all the addresses below), by digitalwest.net. Randy Received: from wiggum.snlo01.digitalwest.net ([65.164.24.67]) by communitech.net ; Mon, 25 Nov 2002 19:08:17 -0600 Received: from wiggum.snlo01.digitalwest.net (localhost [127.0.0.1]) by wiggum.snlo01.digitalwest.net (8.12.6/8.12.6/Debian-7) with ESMTP id gAQ0x0fN021784; Mon, 25 Nov 2002 16:59:08 -0800 Received: (from mail@localhost) by wiggum.snlo01.digitalwest.net (8.12.6/8.12.6/Debian-7) id gAQ0ljgR020003; Mon, 25 Nov 2002 16:47:45 -0800 ----- Original Message ----- From: "Josh Richards via RT" <noc@digitalwest.net> To: <James_Meslovich@icgcomm.com> Cc: <noc@home.net>; <noc@alink.net>; <noc@above.net>; <noc@abs.net>; <support@access.net.id>; <noc@aces.com>; <noctech@adelphia.net>; <noc@agis.net>; <noc@akamai.com>; <data-nocc@algx.com>; <support@alpha.net>; <inetnoc@aol.com>; <noc@amisp.net>; <ops@content.ameritech.net>; <trouble@ans.net>; <support@appliedtheory.com>; <noc@aracnet.com>; <trouble@ntt.net>; <noc@att.net>; <noc@cerf.net>; <noc@att-disc.net>; <noc@attens.com>; <noc@attglobal.net>; <ops@atomfilms.com>; <trouble@aucu.europe>; <trouble@att-unisource.net>; <sales@awwm.com>; <ipnoc@axxent.ca>; <it@bconnex.net>; <ops@bbnplanet.com>; <noc@bellatlantic.net>; <noc@in.bell.ca>; <nnmc@on.bell.ca>; <noc@bellsouth.net>; <noc@best.net>; <noc@mail.sprintmail.net>; <noc@cihost.com>; <noc@canet.ca>; <noc@cweurope.net>; <noc@cwix.net>; <trouble@cw.net>; <trouble@cw.net>; <noc@cableinet.net>; <noc@cv.net>; <noc@cad-net.co.uk>; <noc@cais.net>; <noc@calweb.com>; <tech@cancom.net>; <inoc@carrier1.com>; <noc@cetlink.net>; <cgsc@chello.com>; <noc@circle.net>; <noc@cnz.com>; <noc@clix.net.nz>; <ops@clear.net.nz>; <webmaster@colosource.com>; <webmaster@colosource.com>; <ops@colt.net>; <noc@fr.colt.net>; <noc@com.net>; <noc@comindico.com.au>; <noc@communitech.net>; <noc@compuhelp.com>; <noc@internex.net>; <noc@connect.com.au>; <noc@connectnet.com>; <noc@conxion.net>; <noc@cp.net>; <noc@crl.com>; <paul.witta@cubit.at>; <noc@cyberverse.com>; <noc@bora.net>; <noc@bora.net>; <noc@dtg.com>; <noc@dra.net>; <noc@dataphone.net>; <support@datapipe.com>; <noc@datapipe.net>; <noc@datapipe.com>; <support@magna.com.au>; <noc@deckpoint.ch>; <noc@deckpoint.ch>; <support@delaware.net>; <noc-fl@demon.net>; <noc@nic.dtag.de>; <noc@dialtoneinternet.net>; <support@digex.net>; <ops@digisle.net>; <NOC@digisle.net>; <noc@dn.net>; <routing@crcc.disa.mil>; <noc@dls.net>; <noc@dnai.com>; <noc@domain.net>; <noc@dpnet.net>; <support-request@dsl.net>; <noc@dxstorm.net>; <noc@Corp.EarthLink.Net>; <noc@Corp.EarthLink.Net>; <noc@earthstation.net>; <noc@east.ru>; <noc@easynet.net>; <noc@edmin.com>; <support@eli.net>; <apoio@embratel.net.br>; <noc@empireone.net>; <noc@ena.com>; <noc@energis-ecs.com>; <noc@enron.net>; <noc@ENTERZONE.NET>; <noc@ENTERZONE.NET>; <noc@ENTERZONE.NET>; <noc@eni.net>; <noc@ergogroup.net>; <noc@erols.com>; <trouble@es.net>; <noc@eu.net>; <noc@Romania.EU.net>; <noc@sweden.eu.net>; <noc@euro.net>; <hostmaster@ep.net>; <support@exodus.net>; <snvnoc@globalcenter.net>; <noc@expnet.net>; <noc@expnet.net>; <noc@fast.net>; <noc@fast.net>; <noc@fnsi.net>; <noc@flash.net>; <noc@fdt.net>; <noc@fdt.net>; <noc@flyingcroc.net>; <mike@tampabay.net>; <noc@genuity.net>; <ops@genuity.net>; <admin@geotec.net>; <noc@geotec.net>; <noc@gigabell.net>; <apardo@ipf.es>; <noc@gin.cz>; <gc-noc@gblx.net>; <noc@gnac.com>; <hostmaster@globalone.no>; <support@globix.net>; <noc@good.net>; <noc@gxn.net>; <support@hnt.com>; <noc@harvard.net>; <noc@harvard.net>; <noc@hknet.com>; <noc@hopone.net>; <noc@ibizcorp.com>; <noc@ibm.net>; <noc@noc.icg.net>; <noc@ico.com>; <noc@iconnet.net>; <noc@idc.ad.jp>; <noc@idcglobal.net>; <noc@idt.net>; <support@ihighway.net>; <noc@ihug.net>; <noc@iij.ad.jp>; <noc@cdc-inc.net>; <noc@impulse.net>; <noc@inet-solutions.net>; <noc@nuri.net>; <trouble.desk@infoave.net>; <noc@info.net>; <trouble@infonet-europe.net>; <noc@rtn.net.mx>; <noc@inow.com>; <noc@insnet.net>; <network@insync.net>; <noc@intelenet.net>; <noc@intelideas.com>; <noc@intelideas.com>; <noc@intelideas.com>; <noc@interaccess.com>; <noc@jersey.net>; <noc@unlisys.net>; <noc@icix.net>; <noc@internap.com>; <noc@i1.net>; <noc@airmail.net>; <noc@internex.net>; <noc@interpacket.net>; <smc@intira.com>; <noc@intouch.net>; <noc@ipf.net>; <noc@iphil.net>; <noc@iqonline.net>; <operations@iquest.net>; <admin@aria.nic.ir>; <noc@isi.edu>; <support@isite.net>; <noc@itv.se>; <internetnoc@ixc-comm.com>; <noc@kgns.net>; <support@kddnet.ad.jp>; <noc@kechara.net>; <sysadmin@keyconn.net>; <noc@keyconn.net>; <sysadmin@keyconn.net>; <sysadmin@keyconn.net>; <noc@kingston-internet.net>; <support@kivex.com>; <noc@kks.net>; <noc@kornet.net>; <ip-oper@kpnqwest.at>; <ip-oper@kpnqwest.no>; <noc@sri.lanka.net>; <admin@leftcoast.net>; <support@level3.com>; <noc@level3.net>; <noc@level3.net>; <noc@libertysurf.fr>; <noc@lightning.net>; <noc@lightrealm.com>; <noc@liveonthenet.com>; <support@linx.net>; <NOC@ln.net>; <noc@ln.net>; <noc@ltinet.net>; <netadm@magma.ca>; <support@magna.com.au>; <datos@mcmtelecom.com.mx>; <noc@tm.net>; <trouble@rsng.net>; <noc@mfs.net>; <trouble@merit.edu>; <msnnoc@microsoft.com>; <noc@mis.net>; <noc@mindspring.net>; <trouble@mr.net>; <noc@mne.com>; <noc@monmouth.com>; <noc@msen.com>; <noc@hotmail.com>; <noc@hotmail.com>; <noc@jsnet.com>; <noc@hotmail.com>; <noc@nacamar.net>; <noc@nanospace.net>; <noc@nap.net>; <noc@nationwide.net>; <noc@navi.net>; <nmcgroup@navinet.net>; <trouble@neo.net>; <noc@netaxs.com>; <noc@netaxs.com>; <network@nac.net>; <noc@netasset.com>; <noc@noc.netcom.com>; <noc@netcom.ca>; <noc@netconcept.com>; <noc@netmore.net>; <noc@netrail.net>; <noc@reach.net>; <noc@netreach.net>; <noc@netscalibur.co.uk>; <noc@netscalibur.co.uk>; <noc@ni.net>; <noc@netzero.net>; <noc@netzero.net>; <noc@nmix.net>; <noc@nm.net>; <noc@nextlec.net>; <ops@nmnap.net>; <support@nsn.com>; <noc@nwlink.com>; <noc@nvnw.net>; <noc@nsitel.net>; <noc@nsitel.net>; <noc@olywa.net>; <noc@onecall.net>; <help@one.net>; <trouble@onvoy.com>; <noc@onyx.net>; <noc@opusnet.com>; <noc@opusnet.com>; <noc@opusnet.com>; <trouble@pbi.net>; <trouble@pbi.net>; <noc@pacific.net.sg>; <noc@partan.com>; <noc@peak-10.com>; <admin@phenotek.com>; <noc@planet.net.uk>; <noc@power.net>; <noc@powertech.no>; <noc@primenet.net>; <noc@priori.net>; <engineering@pro-usa.net>; <noc@proxad.net>; <noc@psi.com>; <networks@uk.psi.com>; <noc@kr.psi.net>; <networks@uk.psi.com>; <noc@publichost.com>; <noc@qwest.net>; <noc@rackspace.com>; <noc@raetek.net>; <noc@cwasia.net.sg>; <noc@uunam.mx>; <noc@unam.mx>; <noc@reflexnet.net>; <noc@relcom.eu.net>; <noc@lists.rr.com>; <noc@rr.com>; <noc@rmi.net>; <noc@rt.ru>; <ncc@savvis.net>; <noc@semaphore.net>; <noc@servint.com>; <NOC@shaw.ca>; <support@shore.net>; <noc@shreve.net>; <noc@singnet.com.sg>; <dstroup@skycache.com>; <noc@solnet.ch>; <bobp@southcom.com.au>; <monitors@sover.net>; <noc@speedchoice.com>; <noc@splitrock.net>; <noc@sprint.net>; <neteng@sprintbroadband.com>; <isp@star.net.uk>; <noc@stargate.net>; <noc@megapop.net>; <noc@stealth.net>; <wmahoney@suffolk.edu>; <noc@supermedia.pl>; <noc@surfnetconnexion.com>; <noc@surfnetconnexion.com>; <noc@ip-plus.net>; <noc@switch.ch>; <noc@techline.com>; <noc@tegris.com>; <noc@tegris.com>; <staff@ip.tele.dk>; <trouble@teleglobe.net>; <noc@telerama.com>; <noc@sfo.com>; <ncc@telia.net>; <noc@telocity.net>; <trouble@the.net>; <noc@fix.net>; <support@is.co.za>; <support@is.co.za>; <operators@nally.evansville.in.us>; <noc@theplanet.com>; <noc@mediaone.net>; <noc@trivergent.net>; <noc@ttsg.com>; <noc@us.net>; <support@uunet.ca>; <noc@uunet.ca>; <noc@uunet.co.za>; <noc@uu.net>; <jpr@vcnet.com>; <noc@visi.com>; <noc@verio.net>; <noc@vianetworks.com>; <noc@viewinternet.com>; <support@villagenet.com>; <noc@vphos.net>; <noc@visi.net>; <lhamilton@vistavdi.com>; <support@vitts.com>; <noc@voicenet.com>; <noc@voyager.net>; <support@vii.com>; <noc@w3internet.net>; <noc@professionals.com>; <noc@webex.com>; <soc@corp.webtv.net>; <noc@webzone.net>; <noc@willamette.net>; <noc@wcg.net>; <support@wineasy.se>; <noc@wolfe.net>; <support@worldpath.net>; <noc@wyoming.com>; <nox@xcom.net>; <noc@xnet.com>; <stlnoc@xo.com>; <ops@xtratyme.com>; <netops@uk.yahoo-inc.com>; <info@zenon.net>; <noc@zeroknowledge.com>; <noc@ziplink.net>; <noc@zocalo.net> Sent: Monday, November 25, 2002 6:47 PM Subject: Re: [digitalwest.net #1368] Moratorium.
My guess is you are trying to reach Qwest Communications. If you got our info off of the puck.nether.net NetOps page we've been trying to get a typo fixed on there forever... :)
-jr
* ""Meslovich@wiggum.snlo01.digitalwest.net <""Meslovich@wiggum.snlo01.digitalwest.net> [20021120 10:13]:
Hello, my name is Jim I am the Transport NOC Manager at ICG Telecommunications. I would like to know if you will be working under a moratorium during the holidays? I am also interested in building a solid working relationship between our departments. Please respond with contact information so that we can begin working together.
Sincerely,
Jim Meslovich NOC Transport Manager W Ph. 303-414-8087 Pager 303-826-6931 Cell 303-915-6344 James_Meslovich@icgcomm.com <<Meslovich, James.vcf>>
-- Josh Richards - <jrichard _at_ digitalwest.net> Digital West Networks, Inc. - http://www.digitalwest.net San Luis Obispo, CA 93401 - phone://+1-{888,805}-781-9378
Looks like someone's address book or peering list. ----- Original Message ----- From: "Randy Rostie" <nanog@rostie.net> To: <nanog@merit.edu> Sent: Monday, November 25, 2002 7:31 PM Subject: virus or? We received the following email, with an incredible number of email addresses in the cc: field. We did not even get the original message. Maybe someone has a virus on their computer? I am guessing this is every NOC email address in someone's address book. The email caused us to receive 45 auto-replies from around 5 different domains, that were forwarded to us (and all the addresses below), by digitalwest.net. Randy Received: from wiggum.snlo01.digitalwest.net ([65.164.24.67]) by communitech.net ; Mon, 25 Nov 2002 19:08:17 -0600 Received: from wiggum.snlo01.digitalwest.net (localhost [127.0.0.1]) by wiggum.snlo01.digitalwest.net (8.12.6/8.12.6/Debian-7) with ESMTP id gAQ0x0fN021784; Mon, 25 Nov 2002 16:59:08 -0800 Received: (from mail@localhost) by wiggum.snlo01.digitalwest.net (8.12.6/8.12.6/Debian-7) id gAQ0ljgR020003; Mon, 25 Nov 2002 16:47:45 -0800 ----- Original Message ----- From: "Josh Richards via RT" <noc@digitalwest.net> To: <James_Meslovich@icgcomm.com> Cc: <noc@home.net>; <noc@alink.net>; <noc@above.net>; <noc@abs.net>; <support@access.net.id>; <noc@aces.com>; <noctech@adelphia.net>; <noc@agis.net>; <noc@akamai.com>; <data-nocc@algx.com>; <support@alpha.net>; <inetnoc@aol.com>; <noc@amisp.net>; <ops@content.ameritech.net>; <trouble@ans.net>; <support@appliedtheory.com>; <noc@aracnet.com>; <trouble@ntt.net>; <noc@att.net>; <noc@cerf.net>; <noc@att-disc.net>; <noc@attens.com>; <noc@attglobal.net>; <ops@atomfilms.com>; <trouble@aucu.europe>; <trouble@att-unisource.net>; <sales@awwm.com>; <ipnoc@axxent.ca>; <it@bconnex.net>; <ops@bbnplanet.com>; <noc@bellatlantic.net>; <noc@in.bell.ca>; <nnmc@on.bell.ca>; <noc@bellsouth.net>; <noc@best.net>; <noc@mail.sprintmail.net>; <noc@cihost.com>; <noc@canet.ca>; <noc@cweurope.net>; <noc@cwix.net>; <trouble@cw.net>; <trouble@cw.net>; <noc@cableinet.net>; <noc@cv.net>; <noc@cad-net.co.uk>; <noc@cais.net>; <noc@calweb.com>; <tech@cancom.net>; <inoc@carrier1.com>; <noc@cetlink.net>; <cgsc@chello.com>; <noc@circle.net>; <noc@cnz.com>; <noc@clix.net.nz>; <ops@clear.net.nz>; <webmaster@colosource.com>; <webmaster@colosource.com>; <ops@colt.net>; <noc@fr.colt.net>; <noc@com.net>; <noc@comindico.com.au>; <noc@communitech.net>; <noc@compuhelp.com>; <noc@internex.net>; <noc@connect.com.au>; <noc@connectnet.com>; <noc@conxion.net>; <noc@cp.net>; <noc@crl.com>; <paul.witta@cubit.at>; <noc@cyberverse.com>; <noc@bora.net>; <noc@bora.net>; <noc@dtg.com>; <noc@dra.net>; <noc@dataphone.net>; <support@datapipe.com>; <noc@datapipe.net>; <noc@datapipe.com>; <support@magna.com.au>; <noc@deckpoint.ch>; <noc@deckpoint.ch>; <support@delaware.net>; <noc-fl@demon.net>; <noc@nic.dtag.de>; <noc@dialtoneinternet.net>; <support@digex.net>; <ops@digisle.net>; <NOC@digisle.net>; <noc@dn.net>; <routing@crcc.disa.mil>; <noc@dls.net>; <noc@dnai.com>; <noc@domain.net>; <noc@dpnet.net>; <support-request@dsl.net>; <noc@dxstorm.net>; <noc@Corp.EarthLink.Net>; <noc@Corp.EarthLink.Net>; <noc@earthstation.net>; <noc@east.ru>; <noc@easynet.net>; <noc@edmin.com>; <support@eli.net>; <apoio@embratel.net.br>; <noc@empireone.net>; <noc@ena.com>; <noc@energis-ecs.com>; <noc@enron.net>; <noc@ENTERZONE.NET>; <noc@ENTERZONE.NET>; <noc@ENTERZONE.NET>; <noc@eni.net>; <noc@ergogroup.net>; <noc@erols.com>; <trouble@es.net>; <noc@eu.net>; <noc@Romania.EU.net>; <noc@sweden.eu.net>; <noc@euro.net>; <hostmaster@ep.net>; <support@exodus.net>; <snvnoc@globalcenter.net>; <noc@expnet.net>; <noc@expnet.net>; <noc@fast.net>; <noc@fast.net>; <noc@fnsi.net>; <noc@flash.net>; <noc@fdt.net>; <noc@fdt.net>; <noc@flyingcroc.net>; <mike@tampabay.net>; <noc@genuity.net>; <ops@genuity.net>; <admin@geotec.net>; <noc@geotec.net>; <noc@gigabell.net>; <apardo@ipf.es>; <noc@gin.cz>; <gc-noc@gblx.net>; <noc@gnac.com>; <hostmaster@globalone.no>; <support@globix.net>; <noc@good.net>; <noc@gxn.net>; <support@hnt.com>; <noc@harvard.net>; <noc@harvard.net>; <noc@hknet.com>; <noc@hopone.net>; <noc@ibizcorp.com>; <noc@ibm.net>; <noc@noc.icg.net>; <noc@ico.com>; <noc@iconnet.net>; <noc@idc.ad.jp>; <noc@idcglobal.net>; <noc@idt.net>; <support@ihighway.net>; <noc@ihug.net>; <noc@iij.ad.jp>; <noc@cdc-inc.net>; <noc@impulse.net>; <noc@inet-solutions.net>; <noc@nuri.net>; <trouble.desk@infoave.net>; <noc@info.net>; <trouble@infonet-europe.net>; <noc@rtn.net.mx>; <noc@inow.com>; <noc@insnet.net>; <network@insync.net>; <noc@intelenet.net>; <noc@intelideas.com>; <noc@intelideas.com>; <noc@intelideas.com>; <noc@interaccess.com>; <noc@jersey.net>; <noc@unlisys.net>; <noc@icix.net>; <noc@internap.com>; <noc@i1.net>; <noc@airmail.net>; <noc@internex.net>; <noc@interpacket.net>; <smc@intira.com>; <noc@intouch.net>; <noc@ipf.net>; <noc@iphil.net>; <noc@iqonline.net>; <operations@iquest.net>; <admin@aria.nic.ir>; <noc@isi.edu>; <support@isite.net>; <noc@itv.se>; <internetnoc@ixc-comm.com>; <noc@kgns.net>; <support@kddnet.ad.jp>; <noc@kechara.net>; <sysadmin@keyconn.net>; <noc@keyconn.net>; <sysadmin@keyconn.net>; <sysadmin@keyconn.net>; <noc@kingston-internet.net>; <support@kivex.com>; <noc@kks.net>; <noc@kornet.net>; <ip-oper@kpnqwest.at>; <ip-oper@kpnqwest.no>; <noc@sri.lanka.net>; <admin@leftcoast.net>; <support@level3.com>; <noc@level3.net>; <noc@level3.net>; <noc@libertysurf.fr>; <noc@lightning.net>; <noc@lightrealm.com>; <noc@liveonthenet.com>; <support@linx.net>; <NOC@ln.net>; <noc@ln.net>; <noc@ltinet.net>; <netadm@magma.ca>; <support@magna.com.au>; <datos@mcmtelecom.com.mx>; <noc@tm.net>; <trouble@rsng.net>; <noc@mfs.net>; <trouble@merit.edu>; <msnnoc@microsoft.com>; <noc@mis.net>; <noc@mindspring.net>; <trouble@mr.net>; <noc@mne.com>; <noc@monmouth.com>; <noc@msen.com>; <noc@hotmail.com>; <noc@hotmail.com>; <noc@jsnet.com>; <noc@hotmail.com>; <noc@nacamar.net>; <noc@nanospace.net>; <noc@nap.net>; <noc@nationwide.net>; <noc@navi.net>; <nmcgroup@navinet.net>; <trouble@neo.net>; <noc@netaxs.com>; <noc@netaxs.com>; <network@nac.net>; <noc@netasset.com>; <noc@noc.netcom.com>; <noc@netcom.ca>; <noc@netconcept.com>; <noc@netmore.net>; <noc@netrail.net>; <noc@reach.net>; <noc@netreach.net>; <noc@netscalibur.co.uk>; <noc@netscalibur.co.uk>; <noc@ni.net>; <noc@netzero.net>; <noc@netzero.net>; <noc@nmix.net>; <noc@nm.net>; <noc@nextlec.net>; <ops@nmnap.net>; <support@nsn.com>; <noc@nwlink.com>; <noc@nvnw.net>; <noc@nsitel.net>; <noc@nsitel.net>; <noc@olywa.net>; <noc@onecall.net>; <help@one.net>; <trouble@onvoy.com>; <noc@onyx.net>; <noc@opusnet.com>; <noc@opusnet.com>; <noc@opusnet.com>; <trouble@pbi.net>; <trouble@pbi.net>; <noc@pacific.net.sg>; <noc@partan.com>; <noc@peak-10.com>; <admin@phenotek.com>; <noc@planet.net.uk>; <noc@power.net>; <noc@powertech.no>; <noc@primenet.net>; <noc@priori.net>; <engineering@pro-usa.net>; <noc@proxad.net>; <noc@psi.com>; <networks@uk.psi.com>; <noc@kr.psi.net>; <networks@uk.psi.com>; <noc@publichost.com>; <noc@qwest.net>; <noc@rackspace.com>; <noc@raetek.net>; <noc@cwasia.net.sg>; <noc@uunam.mx>; <noc@unam.mx>; <noc@reflexnet.net>; <noc@relcom.eu.net>; <noc@lists.rr.com>; <noc@rr.com>; <noc@rmi.net>; <noc@rt.ru>; <ncc@savvis.net>; <noc@semaphore.net>; <noc@servint.com>; <NOC@shaw.ca>; <support@shore.net>; <noc@shreve.net>; <noc@singnet.com.sg>; <dstroup@skycache.com>; <noc@solnet.ch>; <bobp@southcom.com.au>; <monitors@sover.net>; <noc@speedchoice.com>; <noc@splitrock.net>; <noc@sprint.net>; <neteng@sprintbroadband.com>; <isp@star.net.uk>; <noc@stargate.net>; <noc@megapop.net>; <noc@stealth.net>; <wmahoney@suffolk.edu>; <noc@supermedia.pl>; <noc@surfnetconnexion.com>; <noc@surfnetconnexion.com>; <noc@ip-plus.net>; <noc@switch.ch>; <noc@techline.com>; <noc@tegris.com>; <noc@tegris.com>; <staff@ip.tele.dk>; <trouble@teleglobe.net>; <noc@telerama.com>; <noc@sfo.com>; <ncc@telia.net>; <noc@telocity.net>; <trouble@the.net>; <noc@fix.net>; <support@is.co.za>; <support@is.co.za>; <operators@nally.evansville.in.us>; <noc@theplanet.com>; <noc@mediaone.net>; <noc@trivergent.net>; <noc@ttsg.com>; <noc@us.net>; <support@uunet.ca>; <noc@uunet.ca>; <noc@uunet.co.za>; <noc@uu.net>; <jpr@vcnet.com>; <noc@visi.com>; <noc@verio.net>; <noc@vianetworks.com>; <noc@viewinternet.com>; <support@villagenet.com>; <noc@vphos.net>; <noc@visi.net>; <lhamilton@vistavdi.com>; <support@vitts.com>; <noc@voicenet.com>; <noc@voyager.net>; <support@vii.com>; <noc@w3internet.net>; <noc@professionals.com>; <noc@webex.com>; <soc@corp.webtv.net>; <noc@webzone.net>; <noc@willamette.net>; <noc@wcg.net>; <support@wineasy.se>; <noc@wolfe.net>; <support@worldpath.net>; <noc@wyoming.com>; <nox@xcom.net>; <noc@xnet.com>; <stlnoc@xo.com>; <ops@xtratyme.com>; <netops@uk.yahoo-inc.com>; <info@zenon.net>; <noc@zeroknowledge.com>; <noc@ziplink.net>; <noc@zocalo.net> Sent: Monday, November 25, 2002 6:47 PM Subject: Re: [digitalwest.net #1368] Moratorium.
My guess is you are trying to reach Qwest Communications. If you got our info off of the puck.nether.net NetOps page we've been trying to get a typo fixed on there forever... :)
-jr
* ""Meslovich@wiggum.snlo01.digitalwest.net <""Meslovich@wiggum.snlo01.digitalwest.net> [20021120 10:13]:
Hello, my name is Jim I am the Transport NOC Manager at ICG Telecommunications. I would like to know if you will be working under a moratorium during the holidays? I am also interested in building a solid working relationship between our departments. Please respond with contact information so that we can begin working together.
Sincerely,
Jim Meslovich NOC Transport Manager W Ph. 303-414-8087 Pager 303-826-6931 Cell 303-915-6344 James_Meslovich@icgcomm.com <<Meslovich, James.vcf>>
-- Josh Richards - <jrichard _at_ digitalwest.net> Digital West Networks, Inc. - http://www.digitalwest.net San Luis Obispo, CA 93401 - phone://+1-{888,805}-781-9378
-- On Monday, November 25, 2002 8:11 PM -0800 -- Scott Granados <scott@wworks.net> supposedly wrote:
Looks like someone's address book or peering list.
<noc@primenet.net>; <noc@priori.net>; <engineering@pro-usa.net>; ^^^^^^^^^^^^^^
A really old peering list. :) I got 46 of total, including the original. Ain't auto-reply loops fun? -- TTFN, patrick
On Monday, Nov 25, 2002, at 22:31 Canada/Eastern, Randy Rostie wrote:
We received the following email, with an incredible number of email addresses in the cc: field. We did not even get the original message. Maybe someone has a virus on their computer?
Maybe someone forwarded all the addresses to a public mailing list which is archived on the web in multiple places, and the addresses got harvested by spammers? Oh well, if not, I'm sure it will happen shortly. Joe
It appears to be caused by an someone replying to all, instead of just the originator of the message. Since most of the recipients were role accounts under a ticketing system, the auto-responders took over, creating an interesting loop; It provides a good reason why an auto-responder should strip out the Cc: when sending a response. The original message is below, although I still question its intent. Please don't reply to the message if you receive it, it should die out. Joe
Hello, my name is Jim I am the Transport NOC Manager at ICG Telecommunications. I would like to know if you will be working under a moratorium during the holidays? I am also interested in building a solid working relationship between our departments. Please respond with contact information so that we can begin working together.
Sincerely,
Jim Meslovich NOC Transport Manager W Ph. 303-414-8087 Pager 303-826-6931 Cell 303-915-6344 James_Meslovich@icgcomm.com
On Tue, 26 Nov 2002, Joe Abley wrote:
On Monday, Nov 25, 2002, at 22:31 Canada/Eastern, Randy Rostie wrote:
We received the following email, with an incredible number of email addresses in the cc: field. We did not even get the original message. Maybe someone has a virus on their computer?
Maybe someone forwarded all the addresses to a public mailing list which is archived on the web in multiple places, and the addresses got harvested by spammers?
Oh well, if not, I'm sure it will happen shortly.
Joe
*sigh* Joe has almost got it. Apparently a Jim of ICG sent an e-mail to a large collection of NOC contacts -- one of which was ours -- asking about a holiday moratorium. It hit our (digitalwest.net) ticketing system (RT2) which stripped off the Cc: line so I didn't see it when I responded via e-mail to him via the queue. I had no idea he'd Cc:'d anyone (and, by default, RT doesn't display the Cc: line in the e-mail sent to queue watchers though it does display it in the web interface). Since the recipient expansion is handled by RT and not the mail client I could not see the horrendous list of Cc:'s. When my response went back into our ticketing system to go out to Jim, RT expanded the recipients list back out to include all of the original recipients. Apparently Jim didn't know how to Bcc:... We turned off our auto-responder immediately after we discovered what had happened to mitigate NOC ticket system loops. -jr * Joe Wood <joew@accretive-networks.net> [20021125 22:29]:
It appears to be caused by an someone replying to all, instead of just the originator of the message. Since most of the recipients were role accounts under a ticketing system, the auto-responders took over, creating an interesting loop; It provides a good reason why an auto-responder should strip out the Cc: when sending a response.
The original message is below, although I still question its intent.
Please don't reply to the message if you receive it, it should die out.
Joe
Hello, my name is Jim I am the Transport NOC Manager at ICG Telecommunications. I would like to know if you will be working under a moratorium during the holidays? I am also interested in building a solid working relationship between our departments. Please respond with contact information so that we can begin working together.
Sincerely,
Jim Meslovich NOC Transport Manager W Ph. 303-414-8087 Pager 303-826-6931 Cell 303-915-6344 James_Meslovich@icgcomm.com
On Tue, 26 Nov 2002, Joe Abley wrote:
On Monday, Nov 25, 2002, at 22:31 Canada/Eastern, Randy Rostie wrote:
We received the following email, with an incredible number of email addresses in the cc: field. We did not even get the original message. Maybe someone has a virus on their computer?
Maybe someone forwarded all the addresses to a public mailing list which is archived on the web in multiple places, and the addresses got harvested by spammers?
Oh well, if not, I'm sure it will happen shortly.
Joe
-- ---- Josh Richards <jrichard@{ geekresearch.com, cubicle.net, digitalwest.net }> Geek Research, LLC - Digital West Networks, Inc - San Luis Obispo, CA KG6CYK - IP/Unix/telecom/knowledge/coffee/security/crypto/business/geek
participants (6)
-
Joe Abley -
Joe Wood -
Josh Richards -
Patrick W. Gilmore -
Randy Rostie -
Scott Granados