|
May 17 |
Mail Server Upgrade
Posted by Tegan King on 17 May 2011 06:42 PM |
|
Type of Work: Mail Server Upgrade Location: FADC, San Diego, CA 92123 Purpose: EPhost Web Administrators will be working on the EPhost Network performing a mail server software upgrade. Window Start: 5/19/2011 - 5:00pm PST Window End: 5/19/2011 - 6:00pm PST Service Impact: This work is not expected to be web service impacting, but will effect mail service intermittently during the allotted maintenance window. Schedule: The window for Network Maintenance is scheduled to begin at 5:00pm on Thursday, May 19, 2011, and end at 6:00pm on Thursday, May 19, 2011. Should additional time be required, notice will be provided and the work window will be expanded. Testing & Planning: All testing and planning being conducted during this window is part of a pre-defined checklist designed by the EPhost Web Administrator team. Regression Planning: The EPhost Web Administrator team will be on-site managing this window. As with any Network Maintenance, while highly unlikely, there is a possibility that something unexpected may occur during the work process. Should any issues arise, all equipment will be placed back into standard operation and the work will be postponed until the issue is resolved. Read more » | |
|
Feb 16 |
Regisite.com interface is migrating Domain Name Registrations management to EPhost.com
Posted by Tegan King on 16 February 2011 10:05 AM |
|
RegiSite has always been owned/operated by EPhost, and was only used for domain name registrations at a time when we did not have this capability in our Control Panel system. EPhost Support Team Read more » | |
|
Sep 24 |
ASP.NET Security Advisory
Posted by Joe Rebis (Import) on 24 September 2010 09:57 AM |
|
We urge owners of ASP.NET websites to implement the changes described in the work-around below. You know that you have an ASP.NET website if your pages have even one page with a .aspx extension. Other open-source applications such as DotNetNuke use ASP.NET and would need the security update. Once Microsoft releases a security update we will apply the update to all of our shared web hosting servers and dedicated/virtual servers as necessary. Since this update may come tomorrow or in 30 days, we suggest implementing the work around below. The workaround fix can be found here. It is not highly technical but use of FTP and page editing is required. http://weblogs.asp.net/scottgu/archive/2010/09/18/important-asp-net-security-vulnerability.aspx If you have trouble applying the workaround fix above please call (858-433-2818) or email (support@ephost.com) for assistance. More information about this vulnerability can be found here: http://www.microsoft.com/technet/security/advisory/2416728.mspx Read more » | |
|
Apr 6 |
AuthorizeNet: New MasterCard and Discover Card Processing Requirements
Posted by Joe Rebis (Import) on 06 April 2010 12:56 PM |
|
MasterCard and Discover are modifying their rules concerning the processing of debit, prepaid and gift cards. THIS E-MAIL INCLUDES IMPORTANT INFORMATION ABOUT THE NEW REQUIREMENTS AND THE TIMELINES REGARDING AUTHORIZE.NET'S SUPPORT OF THE REQUIREMENTS, SO PLEASE READ IT THOROUGHLY. MasterCard's rule changes go into effect May 1, 2010, and Discover's rule changes go into effect April 16, 2010. However, Authorize.Net, MasterCard and Discover have worked together to extend these dates for all merchants using Authorize.Net solutions. OUR MERCHANTS WILL NOW HAVE UNTIL JUNE 30, 2011, TO IMPLEMENT SUPPORT FOR THE REQUIREMENTS WITHIN THEIR SYSTEMS. What are the requirements? MasterCard and Discover are requiring that all merchants support the following: - Balance response transactions - For prepaid and gift cards, once the card has been used, the remaining account balance will be transmitted along with the authorization response. The remaining balance must be printed on the customer receipt, displayed on the Web page or point-of-sale terminal, or both. - Partial authorization transactions - When a customer's transaction amount exceeds the balance available on their debit, prepaid or gift card, instead of declining the transaction, a partial authorization for the amount available to the customer will be returned. This will allow the customer to pay for the remaining amount with another form of payment. This is called a split-tender transaction. - Authorization reversals - An authorization reversal is a real-time transaction initiated when the customer decides that they do not want to proceed with the transaction, or if the merchant cannot complete the transaction for any reason. Authorization reversals free up the customer's available balance on their debit, prepaid or gift card. What steps is Authorize.Net taking to support these requirements? Authorize.Net will be updating our systems over the coming months to support the requirements, but will be dependent on each processor's readiness. For a table of when we anticipate we will support the requirements with each processor, please visit http://www.authorize.net/support/pafaqs/#when. What do I need to do to support the requirements? The steps that you will need to take to support the requirements depend on how you connect to the payment gateway. For example, if you connect using a shopping cart, point-of-sale device, or other solution, you will need to contact your solution provider to confirm that they will be supporting the requirements. If you connect using a direct integration, you should contact your Web developer for assistance. Please direct your Web developer to http://www.authorize.net/support/pafaqs/#do for information on the changes they will need to make. Do I have to support the requirements? MasterCard and Discover are requiring all merchants to support the requirements with the exception of merchants that exclusively process transactions via batch uploads, mail order/telephone order (MOTO), or recurring payment transactions. Your Merchant Service Provider (MSP) is ultimately responsible for determining if the requirements apply to your business, so please contact them for assistance in determining if your company is exempt. Once again, these requirements will not be enforced for Authorize.Net merchants until June 30, 2011. However, we wanted to bring them to your attention now so that you have plenty of time to plan for their implementation. For more information on the requirements, including how they affect our value-adding services, please visit our FAQ page at http://www.authorize.net/support/pafaqs/. Thank you for your attention to these important changes and for being an Authorize.Net merchant. Sincerely, Authorize.Net ***You have opted to receive Administrative Announcements for your payment gateway account. To unsubscribe, log into the Merchant Interface and click Settings in the main menu on the left. Then click Manage Contacts in the Business Settings section and click Edit next to your name. (If the Manage Contacts setting is not available for your account, click User Profile in the main menu and then click Edit Profile Information.) Uncheck the e-mail types you do not want to receive. Click Submit to save any changes. Authorize.Net does not send spam. Ever. For information on Authorize.Net communications and how we handle customer information, please see our Spam Policy at http://www.authorize.net/company/spampolicy/ and Privacy Policy at http://www.authorize.net/company/privacy/. Read more » | |
|
Mar 17 |
Mail Service Update
Posted by Joe Rebis (Import) on 17 March 2010 07:00 PM |
|
We apologize for the inconvenience, but it was necessary to complete this task, which was previously scheduled for next week, tonight. If you have any questions, please call 888-374-6781 Option 2 for updates.
Read more » | |
|
Feb 25 |
Anti-Spam Whitelist Change
Posted by Joe Rebis (Import) on 25 February 2010 04:39 PM |
|
If you have Chinese business associates so I wanted to make you aware as it may affect you due to the poor rating of email from China. If you would like us to globally whitelist MISSION CRITICAL email addresses from China we would be happy to do so. However, we will only whitelist PRIVATE domains or SPECIFIC full email addresses. We will not be able to accommodate a large or ongoing list of domains or emails. In these cases, it is best for you to whitelist using the Trusted Sender’s list in each individual email account you have. See: http://www.ephost.com/support/index.php?_m=troubleshooter&_a=steps&troubleshootercatid=1&parenttroubleshooterid=31 We apologize the inconvenience but it was a necessary step to stop huge amounts of spam. Read more » | |