From: MMS <mms@broadcom.com>
To: netdev@oss.sgi.com
Subject: Virus Alert <MMS1>
Date: Tue, 19 Aug 2003 20:11:49 -0700 [thread overview]
Message-ID: <135C3966222784-01@MMS1> (raw)
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
A recent email you sent was not delivered. The original email headers
are attached with this email. Broadcom E-Mail policy does not allow
attachments with .vbs, .scr, .pif, .exe, and .com extensions due to the
number of email viruses spread through this fashion. Even within .zip
files these attachments are not allowed. If you need to deliver a file
of this type, rename it either by changing the extension or adding a
".txt" and let the recipient know to change it back. Please note that
renaming a .zip file that contains any of the attachments mentioned
above will not work.
Attention:
An email you recently sent to a recipient within Broadcom.com contained
a VIRUS.
The infected message was quarantined and not delivered to the intended
recipient(s).
Please run an antivirus program immediately to scan your desktop for
known viruses. After you have ensured that your desktop is virus-free,
you can resend the message.
If you need assistance, please contact your mail administrator or help
desk.
If you are a Broadcom employee, instructions are already being emailed
to you so that you may know how to eradicate these viruses from your
workstation and/or receive additional support from our helpdesk in doing
so.
Click the attachment below to view the headers of the email in question
which is the reason for this notification.
Information regarding the virus that was intercepted is as follows :
Virus Scanner found the
W32/Sobig.f@MM virus
in the attached file: wicked_scr.scr
MMS1
[-- Attachment #2: Type: message/rfc822, Size: 476 bytes --]
From: netdev@oss.sgi.com
To: investorkits@broadcom.com
Subject: Re: Thank you!
Date: Tue, 19 Aug 2003 20:16:10 --0700
reply other threads:[~2003-08-20 3:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=135C3966222784-01@MMS1 \
--to=mms@broadcom.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).