|
Server : Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 System : Linux server.jackjohnson.com 2.6.32-279.5.2.el6.x86_64 #1 SMP Fri Aug 24 01:07:11 UTC 2012 x86_64 User : jackjohn ( 502) PHP Version : 5.3.17 Disable Function : NONE Directory : /home/jackjohn/mail/.jackjohnson@jackjohnson_com/cur/ |
Upload File : |
Return-Path: <MAILER-DAEMON@jackjohnson.nethosting.com>
Received: from localhost (localhost)
by jackjohnson.nethosting.com (8.14.4/8.13.6) id p3D4jmPw047897;
Tue, 12 Apr 2011 22:45:51 -0600 (MDT)
Date: Tue, 12 Apr 2011 22:45:51 -0600 (MDT)
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <201104130445.p3D4jmPw047897@jackjohnson.nethosting.com>
To: postmaster
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="p3D4jmPw047897.1302669951/jackjohnson.nethosting.com"
Subject: Postmaster notify: see transcript for details
Auto-Submitted: auto-generated (postmaster-notification)
This is a MIME-encapsulated message
--p3D4jmPw047897.1302669951/jackjohnson.nethosting.com
The original message was received at Thu, 7 Apr 2011 22:40:46 -0600 (MDT)
from localhost
with id p384ekrE045227
----- The following addresses had permanent fatal errors -----
<apache@exodus.piercedmedia.com>
----- Transcript of session follows -----
<apache@exodus.piercedmedia.com>... Deferred: Connection refused by exodus.piercedmedia.com.
Message could not be delivered for 5 days
Message will be deleted from queue
--p3D4jmPw047897.1302669951/jackjohnson.nethosting.com
Content-Type: message/delivery-status
Reporting-MTA: dns; jackjohnson.nethosting.com
Arrival-Date: Thu, 7 Apr 2011 22:40:46 -0600 (MDT)
Final-Recipient: RFC822; apache@exodus.piercedmedia.com
Action: failed
Status: 4.4.7
Remote-MTA: DNS; exodus.piercedmedia.com
Last-Attempt-Date: Tue, 12 Apr 2011 22:45:51 -0600 (MDT)
--p3D4jmPw047897.1302669951/jackjohnson.nethosting.com
Content-Type: message/rfc822
Return-Path: <MAILER-DAEMON>
Received: from localhost (localhost)
by jackjohnson.nethosting.com (8.14.4/8.13.6) id p384ekrE045227;
Thu, 7 Apr 2011 22:40:46 -0600 (MDT)
Date: Thu, 7 Apr 2011 22:40:46 -0600 (MDT)
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <201104080440.p384ekrE045227@jackjohnson.nethosting.com>
To: <apache@exodus.piercedmedia.com>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="p384ekrE045227.1302237646/jackjohnson.nethosting.com"
Content-Transfer-Encoding: 8bit
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)
This is a MIME-encapsulated message
--p384ekrE045227.1302237646/jackjohnson.nethosting.com
The original message was received at Thu, 7 Apr 2011 22:40:45 -0600 (MDT)
from 172.68.90.68.piercedmedia.colo.epconline.net [68.90.68.172]
----- The following addresses had permanent fatal errors -----
<hcerny@jackjohnson.com>
(reason: 550 Recipient Rejected: No account by that name here)
----- Transcript of session follows -----
... while talking to ismtp.livebooks.everyone.net.:
>>> DATA
<<< 550 Recipient Rejected: No account by that name here
550 5.1.1 <hcerny@jackjohnson.com>... User unknown
<<< 554 No valid recipients specified
--p384ekrE045227.1302237646/jackjohnson.nethosting.com
Content-Type: message/delivery-status
Reporting-MTA: dns; jackjohnson.nethosting.com
Received-From-MTA: DNS; 172.68.90.68.piercedmedia.colo.epconline.net
Arrival-Date: Thu, 7 Apr 2011 22:40:45 -0600 (MDT)
Final-Recipient: RFC822; Hans@bryanbowenarchitects.com
Action: failed
Status: 5.1.1
Remote-MTA: DNS; ismtp.livebooks.everyone.net
Diagnostic-Code: SMTP; 550 Recipient Rejected: No account by that name here
Last-Attempt-Date: Thu, 7 Apr 2011 22:40:46 -0600 (MDT)
--p384ekrE045227.1302237646/jackjohnson.nethosting.com
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit
Return-Path: <apache@exodus.piercedmedia.com>
Received: from exodus.piercedmedia.com (172.68.90.68.piercedmedia.colo.epconline.net [68.90.68.172])
by jackjohnson.nethosting.com (8.14.4/8.13.6) with ESMTP id p384ejrE045220
for <hcerny@jackjohnson.com>; Thu, 7 Apr 2011 22:40:45 -0600 (MDT)
Received: from exodus.piercedmedia.com (localhost.localdomain [127.0.0.1])
by exodus.piercedmedia.com (8.13.8/8.13.8) with ESMTP id p384eThA024952
for <hcerny@jackjohnson.com>; Thu, 7 Apr 2011 23:40:29 -0500
Received: (from apache@localhost)
by exodus.piercedmedia.com (8.13.8/8.13.8/Submit) id p384eTnZ024951;
Thu, 7 Apr 2011 23:40:29 -0500
Date: Thu, 7 Apr 2011 23:40:29 -0500
Message-Id: <201104080440.p384eTnZ024951@exodus.piercedmedia.com>
To: hcerny@jackjohnson.com
Subject: Recent Attack on RevitCity.com
From: mailer@revitcity.com
MIME-Version: 1.0
Content-Type: text/plain
Content-Disposition: inline
This email was sent by an automated mailer. DO NOT REPLY to this email, no one will receive it.
Dear RevitCity.com User,
Recently RevitCity.com was the victim of a hacker who was able to successfully bypass the security measures we had in place. After discovering this security breach, we moved as quickly as possible to isolate and contain the problem. In order to best protect the server from additional harm and perform a full security examination, it was necessary to temporarily take RevitCity offline.
In order to protect your own privacy, it is always a good idea to change your password as frequently as possible. Although all passwords are protected using an advanced one-way encryption method, it is technically possible that your password was compromised during the security breach, especially if the password is a word that can be found in the dictionary. Therefore, we encourage you to change your password as soon as possible. You may change your password by logging in, and then clicking “Edit User Profile” under Member Options. Alternatively, you may elect to have a randomly generated new password sent to you by going to: http://www.RevitCity.com/forgotpassword.php
Despite our best efforts to protect the RevitCity.com community from this kind of attack, it nevertheless is a common risk we take by providing a valuable sharing platform, and you take by becoming a member. Although we cannot guarantee that this will not happen again, we have made extensive security upgrades to the system.
We are amazed at the resiliency and support of our members who, during the short time the website was down, began helping each other on our Facebook page. For this reason we endeavor to keep RevitCity.com running well into the future.
All the best,
Hiroshi & Jeremy Jacobs
--p384ekrE045227.1302237646/jackjohnson.nethosting.com--
--p3D4jmPw047897.1302669951/jackjohnson.nethosting.com--