Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: AMaViS <virusalert@unixtech.be>
To: <linux-mips@linux-mips.org>
Subject: VIRUS (W32/Netsky.D@mm) IN YOUR MAIL
Date: Thu, 18 Mar 2004 13:36:48 +0100 (CET)	[thread overview]
Message-ID: <VSXXegqH2g@virtual> (raw)

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

VIRUS ALERT

Our virus checker found
    virus: W32/Netsky.D@mm
    banned filename: your_website.pif
in your email to the following recipient:
-> info@namurlug.org

Delivery of the email was stopped!

Please check your system for viruses,
or ask your system administrator to do so.

For your reference, here are headers from your email:
------------------------- BEGIN HEADERS -----------------------------
From: linux-mips@linux-mips.org
To: info@namurlug.org
Subject: Re: Your website
Date: Thu, 18 Mar 2004 18:05:29 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0003_0000775C.000043A7"
X-Priority: 3
X-MSMail-Priority: Normal
-------------------------- END HEADERS ------------------------------

[-- Attachment #2: Delivery error report --]
[-- Type: message/delivery-status, Size: 306 bytes --]

[-- Attachment #3: Undelivered-message headers --]
[-- Type: text/rfc822-headers, Size: 261 bytes --]

From: linux-mips@linux-mips.org
To: info@namurlug.org
Subject: Re: Your website
Date: Thu, 18 Mar 2004 18:05:29 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0003_0000775C.000043A7"
X-Priority: 3
X-MSMail-Priority: Normal

WARNING: multiple messages have this Message-ID (diff)
From: AMaViS <virusalert@unixtech.be>
To: linux-mips@linux-mips.org
Subject: VIRUS (W32/Netsky.D@mm) IN YOUR MAIL
Date: Thu, 18 Mar 2004 13:36:48 +0100 (CET)	[thread overview]
Message-ID: <VSXXegqH2g@virtual> (raw)
Message-ID: <20040318123648.r9TKlrlDmY3WN4NKnv72Xqm4_V9qDat9F6ZRbi_9dSk@z> (raw)

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

VIRUS ALERT

Our virus checker found
    virus: W32/Netsky.D@mm
    banned filename: your_website.pif
in your email to the following recipient:
-> info@namurlug.org

Delivery of the email was stopped!

Please check your system for viruses,
or ask your system administrator to do so.

For your reference, here are headers from your email:
------------------------- BEGIN HEADERS -----------------------------
From: linux-mips@linux-mips.org
To: info@namurlug.org
Subject: Re: Your website
Date: Thu, 18 Mar 2004 18:05:29 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0003_0000775C.000043A7"
X-Priority: 3
X-MSMail-Priority: Normal
-------------------------- END HEADERS ------------------------------

[-- Attachment #2: Delivery error report --]
[-- Type: message/delivery-status, Size: 306 bytes --]

[-- Attachment #3: Undelivered-message headers --]
[-- Type: text/rfc822-headers, Size: 261 bytes --]

From: linux-mips@linux-mips.org
To: info@namurlug.org
Subject: Re: Your website
Date: Thu, 18 Mar 2004 18:05:29 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0003_0000775C.000043A7"
X-Priority: 3
X-MSMail-Priority: Normal

             reply	other threads:[~2004-03-18 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18 12:36 AMaViS [this message]
2004-03-18 12:36 ` VIRUS (W32/Netsky.D@mm) IN YOUR MAIL AMaViS

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=VSXXegqH2g@virtual \
    --to=virusalert@unixtech.be \
    --cc=linux-mips@linux-mips.org \
    /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