Re: Swen and Technet thoughts

From: helper (there)
Date: 10/01/03


Date: Tue, 30 Sep 2003 18:24:00 -0400

yes.
Don't use your primary email address, like you did now.

"Brent" <> wrote in message news:0abd01c387a1$03cf7d80$a301280a@phx.gbl...
> I was sitting around bored oneday and decided to go
> answer some questions on Technet. It was the first time I
> used technet. The day after answering 2 questions My mail
> was jammed with 150 emails that my virus detector caught
> as sween.A. Anyone else have this problem?
>
> Brent
>
> Below is a list of Headers from some of those emails:
>
> Sender: "Microsoft Network Security Center"
> <ceshdlsczmghpp@support.ms.com>
> Recipient: "MS Customer"
> <customer.sscbjqyfzd@support.ms.com>
> Subject: Current Security Upgrade
>
> Sender: "Inet Mail Storage System" <emailprogram@aol.com>
> Recipient: "net client" <receiver@yourdomain.com>
> Subject: Error Message
>
> Sender: "Postmaster" <masterautomat@puremail.com>
> Recipient: "Inet Client" <receiver@mailserver.net>
> Subject: Letter
>
> Sender: "MS Security Department"
> <khyhcrhxcuiykz_tmrbt@updates_microsoft.com>
> Recipient: "Commercial Consumer"
> <yhparou.ykkwbhlbs@updates_microsoft.com>
> Subject: Latest Net Security Pack
>
> Sender: "microsoft net message service"
> <mailerengine@yahoo.net>
> Recipient: "Network User" <client@smtpserver.com>
> Subject: Error Report
>
> Sender: "Microsoft Corporation Technical Assistance"
> <nxtxknzxjfytzy-tinqw@technet_microsoft.com>
> Recipient: "Commercial Client"
> <ebfrpddr_gswpnt@technet_microsoft.com>
>
> Sender: "Internet Security Division"
> <qezspdjfthgfh@technet_msn.net>
> Recipient: "MS Corporation Partner" <ivebons-
> fvbhzmudlr@technet_msn.net>
> Subject: Last Network Patch
>
> Sender: "Microsoft Security Center" <>
> Recipient: MS Corporation Customer
> <customer.dmchxrse@updates.com>
> Subject:
>
> Sender: "Mail Service" <mailrobot@netmail.com>
> Recipient: "Inet Client" <user@mxserver.com>
> Subject: Returned Message: Returned To Sender
>
> Sender: "Microsoft Public Bulletin"
> <exwscnxsy_fbvhnqv@technet.com>
> Recipient: "Consumer" <consumer-iqgmhm@technet.com>
> Subject: Current Internet Patch
>
> Sender: "Internet Security Center"
> <kvdzxkah_ktmdahg@support.com>
> Recipient: "Microsoft Corporation Partner" <partner-
> rxfvysis@support.com>
>
>
> Sender: "MS Corporation Program Security Division"
> <iltlfym@news.com>
> Recipient: "Client" <client_pmtbszno@news.com>
> Subject: Last Microsoft Security Patch
>
> Sender: "Microsoft Network Message Storage System"
> <mailerservice@rocketmail.com>
> Recipient: "Net Recipient" <client@homeserver.net>
> Subject: Error Notice
>
> Sender: "Security Division" <youuvnlpcq@newsletters_ms.com>
> Recipient: "Commercial Customer" <ojuh-
> stexgi@newsletters_ms.com>
> Subject: Newest Internet Upgrade
>
> Sender: "internet delivery service"
> <emailform@rocketmail.com>
> Recipient: "Email Receiver" <recipient@yourserver.net>
> Subject: Message
>
> Sender: "MS Corporation Customer Services"
> <twlgzpl_jwtry@dislyftw.msn.com>
> Recipient: "Commercial Customer"
> <exgwge.tuaebhsa@dislyftw.msn.com>
>
>
> Sender: "Inet Message Delivery Service"
> <masterautomat@rocketmail.net>
> Recipient: " " <client@emaildomain.com>
> Subject: failure advice
>
> Sender: "Microsoft" <pqjrbvqrdvol-fdlfak@confidence.com>
> Recipient: "Microsoft Corporation Customer" <customer-
> xwodxppu@confidence.com>
> Subject:
>
> Sender: "Internet Email Storage Service"
> <smailrobot@bigfoot.com>
> Recipient: "net recipient" <client@mxserver.net>
> Subject:
>
> Sender: Net System <masterprogram@microsoft.net>
> Recipient: internet receiver <receiver@mxserver.com>
> Subject: Mail User unknown
>
> Sender: "MS Internet Message Service" <>
> Recipient: "inet client" <user@yourserver.com>
> Subject:
>
> Sender: "Microsoft Customer Services"
> <khqisphb_cedu@iukus.msdn.com>
> Recipient: "Microsoft Corporation Customer"
> <tfgl@iukus.msdn.com>
> Subject: Latest Internet Security Update
>
> Sender: "Microsoft Public Bulletin"
> <pgrpogmq_wnogtvw@news.com>
> Recipient: "Commercial Partner"
> <fghvtalc.chosyeif@news.com>
> Subject: New Network Upgrade
>
> Sender: "MS Internet Security Center"
> <jbfngkm_vgasm@news.net>
> Recipient: "Microsoft Client" <hbfehe@news.net>
> Subject: newest upgrade
>
> Sender: "microsoft net delivery system"
> <smtpautomat@netmail.com>
> Recipient: "email receiver" <recipient@mxserver.com>
> Subject: Abort Report
>
> Sender: "Microsoft Corporation Internet Security Section"
> <tfameee@support.net>
> Recipient: "Customer" <customer@support.net>
> Subject: Latest Network Security Upgrade
>
> Sender: "MS Customer Support" <anafld@support.msn.net>
> Recipient: "Customer" <yqqwr_qfpgwd@support.msn.net>
> Subject: Latest Network Patch
>
> Sender: "MS Public Bulletin" <wpuiiooowcuvgo@support.net>
> Recipient: "MS Customer" <customer_aljuvwi@support.net>
> Subject: Last Security Update
>
> Sender: "MS Corporation Internet Security Division"
> <wjjtev_pwzyml@technet.msdn.net>
> Recipient: "Commercial Client" <client@technet.msdn.net>
> Subject: Current Critical Update
>
> Sender: "Microsoft Net Email Delivery System"
> <lmaildaemon@rocketmail.com>
> Recipient: "Internet Receiver" <client@maildomain.net>
> Subject: Returned Mail
>
> Sender: "Network Security Division"
> <ouejktpc@bulletin.ms.com>
> Recipient: "Commercial Customer" <>
> Subject: Latest Critical Update
>
> Sender: "Inet Message Delivery System"
> <mailerservice@rocketmail.net>
> Recipient: " " <>
> Subject: Abort Report
>
> Sender: "Microsoft Customer Services"
> <ulgiymadnqllnkz@newsletters.msdn.net>
> Recipient: "Customer" <customer-
> xspbwga@newsletters.msdn.net>
> Subject: Newest Critical Pack
>
> Sender: "Microsoft" <xsvsylmbrma@confidence.com>
> Recipient: "Microsoft Client" <client@confidence.com>
> Subject: Current Net Security Upgrade
>
> Sender: "Inet Message Delivery System"
> <mailerservice@rocketmail.net>
> Recipient: " " <>
> Subject: Abort Report
>
> Sender: "Microsoft Security Support"
> <bnkcmxrbyllgoi@confidence.net>
> Recipient: "Partner" <rquguabn-ltuyisj@confidence.net>
> Subject: current internet critical upgrade
>
> Sender: "Microsoft Internet Security Department"
> <hutlbzpbpf_rgqp@updates_msdn.com>
> Recipient: "Commercial Client" <dvbl-
> kjnqmngjyk@updates_msdn.com>
>
> Sender: "MS Delivery System" <webrobot@yahoo.net>
> Recipient: "mail recipient" <receiver@emaildomain.net>
> Subject: Failure Report
>
>



Relevant Pages

  • Swen and Technet thoughts
    ... >Subject: Current Security Upgrade ... >Subject: Abort Report ... >Subject: Current Critical Update ...
    (microsoft.public.security.virus)
  • Re: Swen and Technet thoughts
    ... You posted via a web interface to an Internet newsgroup. ... > Subject: Current Security Upgrade ... > Subject: Abort Report ...
    (microsoft.public.security.virus)
  • Re: Access to "unsafe attachment" in e-mail
    ... something like what you did for file attachment security with the checkbox ... > on hyperlinks in emails you receive as well. ... >> an attachment might be unsafe. ... At present, after upgrade ALL e-mail ...
    (microsoft.public.security)
  • Re: [Fwd: Re: How secure is Preupgrade? Answer: Not.]
    ... But it's not being marketed as an alternative to an Anaconda HTTP install with less downtime as the only improvement. ... It's being marketed as a safer alternative to a live upgrade with Yum, and as a faster, more convenient and less bandwidth-wasting alternative to downloading and burning DVD images. ... The article talks a lot about how Preupgrade is better than both a Yum upgrade and a DVD-based upgrade, but says very little about network-based Anaconda upgrades, and it's completely silent about the security aspect. ...
    (Fedora)
  • Re: IE6 vs IE& vs IE8 on SBS
    ... But you'd have to be executing that code, either by downloading it or by installing it and in such cases I doubt IE7 will help you much. ... If true, this makes me wonder if there isn't some of the aforementioned security problems present in any OS that has IE6 or earlier installed, active or not. ... But I tend to always ask the inverse of any question like this: Is there a solid reason *to* upgrade? ...
    (microsoft.public.windows.server.sbs)