BANNED (P=p003,M=audio/x-wav,T=exe,T=exe-ms,N=message.scr) IN MAIL FROM YOU

BANNED (P=p003,M=audio/x-wav,T=exe,T=exe-ms,N=message.scr) IN MAIL FROM YOU

[Content-filter at sunbox]

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

BANNED CONTENTS ALERT

Our content checker found
    banned name: P=p003,M=audio/x-wav,T=exe,T=exe-ms,N=message.scr
in email presumably from you (<alsa-devel@lists.sourceforge.net>),
to the following recipient:
-> tardis@imacdonald.co.uk

Our internal reference code for your message is 23454-05.

Delivery of the email was stopped!

The message has been blocked because it contains a component
(as a MIME part or nested within) with declared name
or MIME type or contents type violating our access policy.

To transfer contents that may be considered risky or unwanted
by site policies, or simply too large for mailing, please consider
publishing your content on the web, and only sending an URL of the
document to the recipient.

Depending on the recipient and sender site policies, with a little
effort it might still be possible to send any contents (including
viruses) using one of the following methods:

- encrypted using pgp, gpg or other encryption methods;

- wrapped in a password-protected or scrambled container or archive
  (e.g.: zip -e, arj -g, arc g, rar -p, or other methods)

Note that if the contents is not intended to be secret, the
encryption key or password may be included in the same message
for recipient's convenience.

We are sorry for inconvenience if the contents was not malicious.

The purpose of these restrictions is to cut the most common propagation
methods used by viruses and other malware. These often exploit automatic
mechanisms and security holes in certain mail readers (Microsoft mail
readers and browsers are a common and easy target). By requiring an
explicit and decisive action from the recipient to decode mail,
the dangers of automatic malware propagation is largely reduced.

For your reference, here are headers from your email:
------------------------- BEGIN HEADERS -----------------------------
Return-Path: <alsa-devel@lists.sourceforge.net>
Received: from mccoy.tardis.ed.ac.uk (mccoy.tardis.ed.ac.uk [193.62.81.6])
	by mail.iwasdot.com (Postfix) with ESMTP id 706D34622C
	for <tardis@imacdonald.co.uk>; Sat,  9 Oct 2004 06:57:58 -0400 (EDT)
Received: by mccoy.tardis.ed.ac.uk (Postfix)
	id 2F0CC2AFED; Sat,  9 Oct 2004 11:57:57 +0100 (BST)
Delivered-To: ism@tardis.ed.ac.uk
Received: from tardis.ed.ac.uk (cm99069.red.mundo-r.com [213.60.99.69])
	by mccoy.tardis.ed.ac.uk (Postfix) with ESMTP id 7DCA92BAA1
	for <ism@tardis.ed.ac.uk>; Sat,  9 Oct 2004 11:57:48 +0100 (BST)
From: alsa-devel@lists.sourceforge.net
To: ism@tardis.ed.ac.uk
Subject: Mail Delivery (failure ism@tardis.ed.ac.uk)
Date: Sat, 9 Oct 2004 12:57:56 +0200
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <20041009105748.7DCA92BAA1@mccoy.tardis.ed.ac.uk>
-------------------------- END HEADERS ------------------------------

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

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

Received: from mccoy.tardis.ed.ac.uk (mccoy.tardis.ed.ac.uk [193.62.81.6])
	by mail.iwasdot.com (Postfix) with ESMTP id 706D34622C
	for <tardis@imacdonald.co.uk>; Sat,  9 Oct 2004 06:57:58 -0400 (EDT)
Received: by mccoy.tardis.ed.ac.uk (Postfix)
	id 2F0CC2AFED; Sat,  9 Oct 2004 11:57:57 +0100 (BST)
Delivered-To: ism@tardis.ed.ac.uk
Received: from tardis.ed.ac.uk (cm99069.red.mundo-r.com [213.60.99.69])
	by mccoy.tardis.ed.ac.uk (Postfix) with ESMTP id 7DCA92BAA1
	for <ism@tardis.ed.ac.uk>; Sat,  9 Oct 2004 11:57:48 +0100 (BST)
From: alsa-devel@lists.sourceforge.net
To: ism@tardis.ed.ac.uk
Subject: Mail Delivery (failure ism@tardis.ed.ac.uk)
Date: Sat, 9 Oct 2004 12:57:56 +0200
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <20041009105748.7DCA92BAA1@mccoy.tardis.ed.ac.uk>

BANNED (P=p003,M=audio/x-wav,T=exe,T=exe-ms,N=message.scr) IN MAIL FROM YOU

[SpamControl]

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

BANNED CONTENTS ALERT

Our content checker found
    banned name: P=p003,M=audio/x-wav,T=exe,T=exe-ms,N=message.scr
in email presumably from you (<netdev@oss.sgi.com>),
to the following recipient:
-> ija@icrier.res.in

Delivery of the email was stopped!

The message has been blocked because it contains a component
(as a MIME part or nested within) with declared name
or MIME type or contents type violating our access policy.

To transfer contents that may be considered risky or unwanted
by site policies, or simply too large for mailing, please consider
publishing your content on the web, and only sending an URL of the
document to the recipient.

Depending on the recipient and sender site policies, with a little
effort it might still be possible to send any contents (including
viruses) using one of the following methods:

- encrypted using pgp, gpg or other encryption methods;

- wrapped in a password-protected or scrambled container or archive
  (e.g.: zip -e, arj -g, arc g, rar -p, or other methods)

Note that if the contents is not intended to be secret, the
encryption key or password may be included in the same message
for recipient's convenience.

We are sorry for inconvenience if the contents was not malicious.

The purpose of these restrictions is to cut the most common propagation
methods used by viruses and other malware. These often exploit automatic
mechanisms and security holes in certain mail readers (Microsoft mail
readers and browsers are a common and easy target). By requiring an
explicit and decisive action from the recipient to decode mail,
the dangers of automatic malware propagation is largely reduced.


For your reference, here are headers from your email:
------------------------- BEGIN HEADERS -----------------------------
Return-Path: <netdev@oss.sgi.com>
Received: from icrier.res.in (unknown [82.124.144.60])
	by firewall.icrier.res.in (Postfix) with ESMTP id 7AEBD2687D
	for <ija@icrier.res.in>; Fri, 26 Nov 2004 22:07:47 +0530 (IST)
From: netdev@oss.sgi.com
To: ija@icrier.res.in
Subject: Mail Delivery (failure ija@icrier.res.in)
Date: Fri, 26 Nov 2004 17:28:19 +0100
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <20041126163747.7AEBD2687D@firewall.icrier.res.in>
-------------------------- END HEADERS ------------------------------

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

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

Received: from icrier.res.in (unknown [82.124.144.60])
	by firewall.icrier.res.in (Postfix) with ESMTP id 7AEBD2687D
	for <ija@icrier.res.in>; Fri, 26 Nov 2004 22:07:47 +0530 (IST)
From: netdev@oss.sgi.com
To: ija@icrier.res.in
Subject: Mail Delivery (failure ija@icrier.res.in)
Date: Fri, 26 Nov 2004 17:28:19 +0100
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <20041126163747.7AEBD2687D@firewall.icrier.res.in>