Hello, Can someone tell me what has happened to cause this message to come to me from my server? I don't generally get rejected spam messages What made this message different from a simple rejected spam? What's the trick?
Here's the source version of the message: ===================== Return-Path: <MAILER-DAEMON> Delivered-To: vi...@example.net Received: from localhost (localhost [127.0.0.1]) by server.example.org (Postfix) with ESMTP id 415FF7D15 for <vi...@example.net>; Fri, 11 Dec 2009 10:50:01 -0500 (EST) Content-Type: multipart/report; report-type=delivery-status; boundary="----------=_1260546601-11071-0" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Subject: Considered UNSOLICITED BULK EMAIL, apparently from you In-Reply-To: <20091211154957.d382c7...@server.example.org> Message-ID: <ssevdi7wo0z...@server.example.org> From: "Content-filter at server.example.org" <postmas...@server.example.org> To: <vi...@example.net> Date: Fri, 11 Dec 2009 10:50:00 -0500 (EST) This is a multi-part message in MIME format... ------------=_1260546601-11071-0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit A message from <vi...@example.net> to: -> vi...@example.net was considered unsolicited bulk e-mail (UBE). Our internal reference code for your message is 11071-05/EVdi7Wo0zW8o The message carried your return address, so it was either a genuine mail from you, or a sender address was faked and your e-mail address abused by third party, in which case we apologize for undesired notification. We do try to minimize backscatter for more prominent cases of UBE and for infected mail, but for less obvious cases of UBE some balance between losing genuine mail and sending undesired backscatter is sought, and there can be some collateral damage on both sides. First upstream SMTP client IP address: [187.13.204.132] According to a 'Received:' trace, the message originated at: [187.13.204.132], 18713204132.user.veloxzone.com.br unknown [187.13.204.132] Return-Path: <vi...@example.net> Message-ID: <20091211154957.d382c7...@server.example.org> Subject: Dear vi...@example.net 82% 0FF on PFIZER ! Non-encoded 8-bit data (char AE hex): From: VIAGRA \256 Official Site [...] Delivery of the email was stopped! ------------=_1260546601-11071-0 Content-Type: message/delivery-status; name="dsn_status" Content-Disposition: inline; filename="dsn_status" Content-Transfer-Encoding: 7bit Content-Description: Delivery error report Reporting-MTA: dns; server.example.org Received-From-MTA: smtp; server.example.org ([127.0.0.1]) Arrival-Date: Fri, 11 Dec 2009 10:50:00 -0500 (EST) Original-Recipient: rfc822;vi...@example.net Final-Recipient: rfc822;vi...@example.net Action: failed Status: 5.7.0 Diagnostic-Code: smtp; 554 5.7.0 Reject, id=11071-05 - SPAM Last-Attempt-Date: Fri, 11 Dec 2009 10:50:00 -0500 (EST) Final-Log-ID: 11071-05/EVdi7Wo0zW8o ------------=_1260546601-11071-0 Content-Type: text/rfc822-headers; name="header" Content-Disposition: inline; filename="header" Content-Transfer-Encoding: 8bit Content-Description: Message header section Return-Path: <vi...@example.net> Received: from 18713204132.user.veloxzone.com.br (unknown [187.13.204.132]) by server.example.org (Postfix) with SMTP id D382C7D0E for <vi...@example.net>; Fri, 11 Dec 2009 10:49:35 -0500 (EST) From: VIAGRA ® Official Site <vi...@example.net> To: <vi...@example.net> Subject: Dear vi...@example.net 82% 0FF on PFIZER ! MIME-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20091211154957.d382c7...@server.example.org> Date: Fri, 11 Dec 2009 10:49:35 -0500 (EST) ------------=_1260546601-11071-0--
