All of lore.kernel.org
 help / color / mirror / Atom feed
* BANNED FILENAME (test.pif) IN MAIL FROM YOU
       [not found] <20051225091235.6307F30006D9@mailgate2.zdv.Uni-Mainz.DE>
@ 2005-12-25  9:13 ` amavisd-new
  0 siblings, 0 replies; only message in thread
From: amavisd-new @ 2005-12-25  9:13 UTC (permalink / raw)
  To: alsa-devel

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

BANNED CONTENTS ALERT

Our content checker found
    banned name: test.pif
in email presumably from you (<alsa-devel@lists.sf.net>), to the following recipient:
-> plass@thep.physik.uni-mainz.de

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.sf.net>
Received: from lists.sf.net (unknown [218.17.227.216])
	by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 6307F30006D9
	for <plass@thep.physik.uni-mainz.de>; Sun, 25 Dec 2005 10:12:35 +0100 (CET)
From: alsa-devel@lists.sf.net
To: plass@thep.physik.uni-mainz.de
Subject: hello
Date: Sun, 25 Dec 2005 17:12:34 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0013_B9E968DE.3A90A4F8"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <20051225091235.6307F30006D9@mailgate2.zdv.Uni-Mainz.DE>
-------------------------- END HEADERS ------------------------------

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

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

Received: from lists.sf.net (unknown [218.17.227.216])
	by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 6307F30006D9
	for <plass@thep.physik.uni-mainz.de>; Sun, 25 Dec 2005 10:12:35 +0100 (CET)
From: alsa-devel@lists.sf.net
To: plass@thep.physik.uni-mainz.de
Subject: hello
Date: Sun, 25 Dec 2005 17:12:34 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0013_B9E968DE.3A90A4F8"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <20051225091235.6307F30006D9@mailgate2.zdv.Uni-Mainz.DE>

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-12-25  9:13 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20051225091235.6307F30006D9@mailgate2.zdv.Uni-Mainz.DE>
2005-12-25  9:13 ` BANNED FILENAME (test.pif) IN MAIL FROM YOU amavisd-new

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.