BANNED FILENAME ("file.txt .pif") IN MAIL FROM YOU

BANNED FILENAME ("file.txt .pif") IN MAIL FROM YOU

[amavisd-new]

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

BANNED CONTENTS ALERT

Our content checker found
    banned name: "file.txt                                                                   .pif"
in email presumably from you (<alsa-devel@lists.sourceforge.net>), to the following recipient:
-> david.vizcaino@estudiant.upc.es

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 estudiant.upc.es (14-BAR2-X8.libre.retevision.es [62.82.183.14])
	by dukas.upc.es (8.12.10/8.12.10) with ESMTP id i8PHUfFB014409
	for <david.vizcaino@estudiant.upc.es>; Sat, 25 Sep 2004 19:30:49 +0200 (MEST)
Message-Id: <200409251730.i8PHUfFB014409@dukas.upc.es>
From: alsa-devel@lists.sourceforge.net
To: david.vizcaino@estudiant.upc.es
Subject: file
Date: Sat, 25 Sep 2004 19:31:46 +0200
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
-------------------------- END HEADERS ------------------------------

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

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

Received: from estudiant.upc.es (14-BAR2-X8.libre.retevision.es [62.82.183.14])
	by dukas.upc.es (8.12.10/8.12.10) with ESMTP id i8PHUfFB014409
	for <david.vizcaino@estudiant.upc.es>; Sat, 25 Sep 2004 19:30:49 +0200 (MEST)
Message-Id: <200409251730.i8PHUfFB014409@dukas.upc.es>
From: alsa-devel@lists.sourceforge.net
To: david.vizcaino@estudiant.upc.es
Subject: file
Date: Sat, 25 Sep 2004 19:31:46 +0200
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal