From: amavisd-new <postmaster@pnjpolmx04-0208.pol.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: BANNED FILENAME (Info.pif) IN MAIL FROM YOU
Date: Fri, 19 Mar 2004 13:47:59 -0500 (EST) [thread overview]
Message-ID: <VS14681-03@pnjpolmx04-0208> (raw)
In-Reply-To: <tehfduphcsifprcemxf@pol.net>
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
BANNED FILENAME ALERT
Our content checker found
banned name: Info.pif
in email presumably from you (<linux-fbdev-devel@lists.sourceforge.net>), to the following recipient:
-> adaplas@pol.net
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.
With a little effort it is still 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: <linux-fbdev-devel@lists.sourceforge.net>
Received: from strummer (unknown [10.250.10.1])
by mx04.pol.net (Postfix) with SMTP id 0186D2441C5
for <adaplas@pol.net>; Fri, 19 Mar 2004 13:47:52 -0500 (EST)
Date: Fri, 19 Mar 2004 19:46:33 +0100
To: adaplas@pol.net
Subject: E-mail account security warning.
From: management@pol.net
Message-ID: <tehfduphcsifprcemxf@pol.net>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="--------lrtsphsxxchgiwesbvwk"
-------------------------- END HEADERS ------------------------------
[-- Attachment #2: Delivery error report --]
[-- Type: message/delivery-status, Size: 358 bytes --]
[-- Attachment #3: Undelivered-message headers --]
[-- Type: text/rfc822-headers, Size: 426 bytes --]
Received: from strummer (unknown [10.250.10.1])
by mx04.pol.net (Postfix) with SMTP id 0186D2441C5
for <adaplas@pol.net>; Fri, 19 Mar 2004 13:47:52 -0500 (EST)
Date: Fri, 19 Mar 2004 19:46:33 +0100
To: adaplas@pol.net
Subject: E-mail account security warning.
From: management@pol.net
Message-ID: <tehfduphcsifprcemxf@pol.net>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="--------lrtsphsxxchgiwesbvwk"
parent reply other threads:[~2004-03-19 18:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tehfduphcsifprcemxf@pol.net>]
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=VS14681-03@pnjpolmx04-0208 \
--to=postmaster@pnjpolmx04-0208.pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).