![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
I believe that is my auth, I dont understand what is happen. Francois -----Original Message----- From: Jim Dunn <jim.dunn at BT.NET> To: Valdis.Kletnieks at vt.edu <Valdis.Kletnieks at vt.edu>; ietf at ietf.org <ietf at ietf.org> Date: Tuesday, January 18, 2000 6:36 PM Subject: RE: Is anybody else suspicious about this? >I have noticed that the Auth code is the same everytime I have been mailed >by Majordomo or someone has replied to the mail.( About 25 instances so >far ) > >Steve Coya has sent a message asking people not to respond to these >messages. >See below for original message from Steve. > >Regards > >Jim >-----Original Message----- >From: Steve Coya [mailto:scoya at ietf.org] >Sent: 12 January 2000 20:08 >To: ietf at ietf.org >Subject: Majordomo subscribe request message > > > >Folks, > >Please do NOT respond to the message from majordomo asking to confirm >adding ietf at ietf.org to ietf at ietf.org > >We're not sure where this/these messages originated, but are looking into >it right now. > >Thanks and sorry for the inconvenience. > > > >Steve > >-----Original Message----- >From: Valdis.Kletnieks at vt.edu [mailto:Valdis.Kletnieks at vt.edu] >Sent: 18 January 2000 15:42 >To: ietf at ietf.org >Subject: Is anybody else suspicious about this? > > >Last 3 e-mails to the list, from: > >From: plamen kosseff <p_kosseff at prosyst.com> >From: "Tobin, Brian" <Brian_Tobin at AFCC.com> >From: marcello at nbase.co.il (Marcello Bracha) > >All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:. > >Is this rampant cluelessness, or is that 36dbe6c3 cookie being >regenerated by a broken HTML page or something? > >In the meantime, can we fix the Majordomo filter so 'auth' gets trapped >as well as 'subscribe' so we can return to our usual silence/flaming cycle? >;) > > Valdis Kletnieks > Operating Systems Analyst > Virginia Tech
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.