The original message came to me with the file still encoded in the message. It was never decoded as an attachment - so maybe not everyone else was confronted with it as an attached file.
This incident raises a logical question. Can this list itself be protected by Declude Virus so messages with infected attachments would get blocked and not distributed? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry Sent: Friday, March 29, 2002 3:51 PM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] NJABL:Is this a virus >Is this a virus? For those that got this, it apparently did contain a virus. More information will be posted later about it. And, for anyone else out there that is clueless, *NEVER* send a virus *ANYWHERE* unless it is specifically requested. Sending a virus to a mailing list is an extremely stupid thing to do. The *only* address that we have that viruses may be sent to is [EMAIL PROTECTED] (we do not actively view the mail sent to that address, so a separate E-mail is required to let us know that a virus was sent to it). -Scott --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com . --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
