All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Content-filter at mail.vrlogistic.com"  <postmaster@mail.vrlogistic.com>
To: <linux-watchdog@vger.kernel.org>
Subject: BANNED contents from you (.exe,vrlogistic.com)
Date: Tue,  7 Dec 2021 07:40:59 +0530 (IST)	[thread overview]
Message-ID: <VS64KBiY-UA-_4@mail.vrlogistic.com> (raw)

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

BANNED CONTENTS ALERT

Our content checker found
    banned name: .exe,vrlogistic.com

in email presumably from you <linux-watchdog@vger.kernel.org>
to the following recipients:
-> kapil@vrlogistic.com
-> renuka@vrlogistic.com

Our internal reference code for your message is 21322-12/64KBiY-UA-_4

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

Return-Path: <linux-watchdog@vger.kernel.org>
From: linux-watchdog@vger.kernel.org
Subject: kapil@vrlogistic.com

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.


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

[-- Attachment #3: Message header section --]
[-- Type: text/rfc822-headers, Size: 608 bytes --]

Return-Path: <linux-watchdog@vger.kernel.org>
Received: from vger.kernel.org (unknown [192.168.1.1])
	by mail.vrlogistic.com (Postfix) with ESMTP id E824AF4316F
	for <kapil@vrlogistic.com>; Tue,  7 Dec 2021 07:40:54 +0530 (IST)
From: linux-watchdog@vger.kernel.org
To: kapil@vrlogistic.com
Subject: kapil@vrlogistic.com
Date: Tue, 7 Dec 2021 10:07:43 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0004_CB231B6D.813E7456"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

                 reply	other threads:[~2021-12-07  2:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=VS64KBiY-UA-_4@mail.vrlogistic.com \
    --to=postmaster@mail.vrlogistic.com \
    --cc=linux-watchdog@vger.kernel.org \
    /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 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.