linux-kernel - BANNED contents from you (application/octet-stream,.exe,.exe-ms,TEXT.SCR)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <VSbi4CtDs_ldbK@natalya.videolan.org>
Date:   Wed, 16 Jun 2021 05:04:45 +0000 (UTC)
From:   "Content-filter at natalya.videolan.org" 
        <postmaster@...alya.videolan.org>
To:     <linux-kernel@...r.kernel.org>
Subject: BANNED contents from you
 (application/octet-stream,.exe,.exe-ms,TEXT.SCR)

BANNED CONTENTS ALERT

Our content checker found
    banned name: application/octet-stream,.exe,.exe-ms,TEXT.SCR

in email presumably from you <linux-kernel@...r.kernel.org>
to the following recipient:
-> pdherbemont@...eolan.org

Our internal reference code for your message is 28719-09/bi4CtDs_ldbK

First upstream SMTP client IP address: [103.117.36.105] 
According to a 'Received:' trace, the message apparently originated at:
  [103.117.36.105], vger.kernel.org unknown [103.117.36.105]

Return-Path: <linux-kernel@...r.kernel.org>
From: linux-kernel@...r.kernel.org
Subject: Returned mail: Data format error

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.

Download attachment "dsn_status.dsn" of type "message/delivery-status" (497 bytes)

View attachment "header.hdr" of type "text/rfc822-headers" (629 bytes)