public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Content-filter at host09.ws5.connectedcommunity.org" <postmaster@host09.ws5.connectedcommunity.org>
To: <cygwin@cygwin.com>
Subject: BANNED contents from you (.exe,.exe-ms,document.scr)
Date: Mon,  6 Nov 2023 08:47:29 +0000 (UTC)	[thread overview]
Message-ID: <VSE1URiNGuxssN@host09.ws5.connectedcommunity.org> (raw)

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

BANNED CONTENTS ALERT

Our content checker found
    banned name: .exe,.exe-ms,document.scr

in email presumably from you <cygwin@cygwin.com>
to the following recipient:
-> ebxml-msg@lists.oasis-open.org

Our internal reference code for your message is 29847-20/E1URiNGuxssN

First upstream SMTP client IP address: [10.110.0.173]:44630
  ip-10-110-0-173.ec2.internal

Received trace: ESMTP://[10.110.0.173]:44630 < ESMTP://34.233.166.49

Return-Path: <cygwin@cygwin.com>
From: cygwin@cygwin.com
Subject: Mail System Error - Returned Mail

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 a 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 avoid the most common
propagation methods used by viruses and other malware. These often
exploit automatic mechanisms and security holes in more popular
mail readers. By requiring an explicit and decisive action from a
recipient to decode mail, a danger of automatic malware propagation
is largely reduced.


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

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

Return-Path: <cygwin@cygwin.com>
Received: from ws5-mx01.kavi.com (ip-10-110-0-173.ec2.internal [10.110.0.173])
	by lists.oasis-open.org (Postfix) with ESMTP id CCE2D986708
	for <ebxml-msg@lists.oasis-open.org>; Mon,  6 Nov 2023 08:47:29 +0000 (UTC)
Received: from cygwin.com (unknown [34.233.166.49])
	by ws5-mx01.kavi.com (Postfix) with ESMTP id BD5D92B044
	for <ebxml-msg@lists.oasis-open.org>; Mon,  6 Nov 2023 08:47:29 +0000 (UTC)
From: cygwin@cygwin.com
To: ebxml-msg@lists.oasis-open.org
Subject: Mail System Error - Returned Mail
Date: Mon, 6 Nov 2023 00:47:29 -0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0000_6A1DBAB5.33F73F9D"
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:[~2023-11-06  8:47 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=VSE1URiNGuxssN@host09.ws5.connectedcommunity.org \
    --to=postmaster@host09.ws5.connectedcommunity.org \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).