BANNED CONTENTS ALERT Our content checker found banned name: .exe,.exe-ms,fax2_data.exe
in email presumably from you <bug-...@gnu.org> to the following recipient: -> emmano...@sharpmoves.com Our internal reference code for your message is 01188-13/YAYqOvC_QGxu First upstream SMTP client IP address: [85.31.195.58]:1110 cpe-et001203.cust.jaguar-network.net Received from: 85.31.195.58 < 143.132.174.155 < 133.115.172.165 Return-Path: <bug-...@gnu.org> From: bug-gcc <bug-...@gnu.org> Message-ID: <555b2f5e.fa7d8...@gnu.org> Subject: adjustment reminder 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.
Reporting-MTA: dns; gordon.sharp-consultancy.local Received-From-MTA: smtp; gordon.sharpmoves.com ([127.0.0.1]) Arrival-Date: Tue, 19 May 2015 13:41:05 +0100 (BST) Original-Recipient: rfc822;emmanoble@sharpmoves.com Final-Recipient: rfc822;emmanoble@sharpmoves.com Action: failed Status: 5.7.0 Diagnostic-Code: smtp; 554-5.7.0 Bounce, id=01188-13 - BANNED: 554 5.7.0 .exe,.exe-ms,fax2_data.exe Last-Attempt-Date: Tue, 19 May 2015 13:41:05 +0100 (BST) Final-Log-ID: 01188-13/YAYqOvC_QGxu
Return-Path: <bug-...@gnu.org> Received: from gnu.org (cpe-et001203.cust.jaguar-network.net [85.31.195.58]) by gordon.sharpmoves.com (Postfix) with ESMTP id 44AA4A44F for <emmano...@sharpmoves.com>; Tue, 19 May 2015 13:41:04 +0100 (BST) Received: from lzEe3.gnu.org (lzEe3.gnu.org [143.132.174.155]) by Qdby26.com (Postfix) with ESMTP id 57C9D40165 for <emmano...@sharpmoves.com>; Tue, 19 May 2015 14:41:02 +0100 (CEST) Received: from [133.115.172.165] by UtYb.MQ9ZVBAR.gnu.org (via HTTP); Tue, 19 May 2015 14:41:02 +0100 Date: Tue, 19 May 2015 14:41:02 +0100 From: bug-gcc <bug-...@gnu.org> Message-ID: <555b2f5e.fa7d8...@gnu.org> To: <emmano...@sharpmoves.com> Subject: adjustment reminder MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------------------030409030707030702020009"