[Jesus-post] BANNED contents from you (.exe, .exe-ms, Factura4.doc__________________________________________________________________________________________.exe)

[Content-filter at gauss.cosmomedia.es]

BANNED CONTENTS ALERT

Our content checker found
    banned name:
      .exe,.exe-ms,Factura4.doc__________________________________________________________________________________________.exe

in email presumably from you <jesus-post at lists.ourproject.org>
to the following recipients:
-> m_x9 at telefonica.es
-> m_x9a at telefonica.es
-> m_x9b at telefonica.es
-> m_x_a at telefonica.es
-> m_xa at telefonica.es
-> m_xaa at telefonica.es
-> m_xac at telefonica.es
-> m_xb at telefonica.es
-> m_xc at telefonica.es
-> m_xd at telefonica.es

Our internal reference code for your message is 16738-05/jzebhy7ybFH9

First upstream SMTP client IP address: [88.191.35.175] sd-5293.dedibox.fr
According to a 'Received:' trace, the message apparently originated at:
  [212.187.12.1], [212.187.12.1]

Return-Path: <jesus-post at lists.ourproject.org>
From: <jesus-post at lists.ourproject.org>
Message-ID: <009d01ca4d18$48d5b780$010cbbd4.203}@sd-5293.dedibox.fr>
Subject: Re: Deuda pendiente!

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 more popular mail readers (Microsoft
mail readers and browsers are a common target). By requiring an explicit
and decisive action from the recipient to decode mail, the danger of
automatic malware propagation is largely reduced.

-------------- next part --------------
Skipped content of type message/delivery-status-------------- next part --------------
A non-text attachment was scrubbed...
Name: header
Type: text/rfc822-headers
Size: 614 bytes
Desc: Message header section
Url : /pipermail/jesus-post/attachments/20091014/eb86b1bd/header-0001.bin