VIRUS IN YOUR MAIL

VIRUS IN YOUR MAIL

[postmaster]

                           V I R U S  A L E R T

Our viruschecker found the

	'W32/Netsky-Q'

virus(es) in your email to the following recipient(s):

-> beijing@icpdas.com

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

For your reference, here are the headers from your email:

------------------------- BEGIN HEADERS -----------------------------
Return-Path: <linux-mtd@lists.infradead.org>
Received: from icpdas.com ([218.88.41.109])
	by maple.icpdas.com (8.11.6/8.11.6) with ESMTP id i328nOX68347
	for <beijing@icpdas.com>; Fri, 2 Apr 2004 16:49:24 +0800 (CST)
	(envelope-from linux-mtd@lists.infradead.org)
From: linux-mtd@lists.infradead.org
Message-Id: <200404020849.i328nOX68347@maple.icpdas.com>
To: beijing@icpdas.com
Subject: Delivery Error (beijing@icpdas.com)
Date: Fri, 2 Apr 2004 16:49:22 +0800
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA81.7B015D10"
X-Priority: 1
X-MSMail-Priority: High
-------------------------- END HEADERS ------------------------------

Administrivia [Re: VIRUS IN YOUR MAIL]

[David Woodhouse]

I have just reported this mail abuse to the postmaster responsible, and
to the upstream abuse contact. 

This wasn't a subscriber, but just a reminder to the rest of you -- if
you have a virus checker which can be configured to send 'bounces' to
the apparent sender of a mail to which it objects, ensure that
misfeature is turned _OFF_. 

These things are all faking the sender now, and by sending a mail like
that you're abusing an innocent third party and making yourself part of
the _problem_ rather than part of the solution.

This one was particularly broken and dangerous because it sent its
'bounce' with a non-empty reverse-path, in violation of RFC2821 and
common sense -- making it likely to cause mail loops, and meaning that
it got past the filter which prevents bounces from getting through to
the list. 

-- 
dwmw2