Providing Business Class
Web Hosting Since 1996
Sales Chat

My account was caught sending out spam

Monday, March 5th, 2018 - General

Have you received an email from us stating that your account has been used for spamming? That message may have looked like:

A routine security check on the server found that your account – – was being used to send out spam through the server.

Someone is using SMTP authentication with the account – – to relay out questionable mail through the server.

What does this message mean?

This means that someone (probably not you, right?) has logged into the server using the account information to send out spam. We are assuming that this person wasn’t really you (otherwise, you’d be the spammer and we’re going to err on the side that it wasn’t really you) so this means that spammers somehow got their hands on the password for

This means you likely have an information leak some where. Information, such as the password to this email account (and potentially other information that may not be affecting your web hosting account with us) is being leaked out. If you don’t stop the source of that leak, then information will continue to leak out.

How did they get their hands on the password for We don’t know. And by that we mean that we really don’t know – we haven’t been looking over your shoulder every where you have used this account or what type of password you are using.

One question we often get asked regarding these incidents is: Why didn’t you just block the IP address of the individual sending out the spam? Well, the issue isn’t necessarily WHO is sending out the spam. The issue is that your information was compromised. The IP address isn’t the common point of entry. Often times the spammers are connecting from 100s of different IP addresses, and even if we did block those IPs, they’d just connect from others. The common point of entry is the compromised email account. That is why the password to the email account has to be changed and why IP addresses are not directly blocked.

Typically hackers and spammers get your password information by one of three different ways:

• Malware, viruses, or keyloggers. Your computer or device may be infected with something that is leaking out your password information. If you have malware or a keylogger on your computer (or mobile phone, tablet, or other device) then that malware can be transmitting your password information for all of the accounts you access back to hackers and spammers. This is also how identity theft usually starts. To resolve this, you need to identify which computer or device is checking this account and which computer or device has the malware and keylogger on it, and remove the malware or keylogger. Then you need to change the password for your email account and any other account for any other business you may have logged into on this device.

• Insecure network or network probing. If you check your mail or use your computer, phone, or tablet on any public wifi or insecure network, then you are potentially leaving your data vulnerable to hacking from others on that network. Someone else sharing that public wifi hotspot may be listening in on your connection and stealing password information as you transmit it. To resolve this, you need to identify what sources of insecure networks or wifi that you are using and either secure them or stop using them and then change your email account password and any other account for any other account for any other business you may have logged into on these networks.

• Using weak and insecure passwords. We covered this a bit in detail in a previous post. Bottom line, you are responsible for choosing strong and secure passwords for your accounts. If you are using simple and easy to guess passwords for your account – then you should expect to be compromised – and you need to accept some responsibility for having your account hacked, compromised, and used to send out spam. To resolve this, you need to choose strong and secure passwords for all of your accounts.

These are just some of the scenarios that can explain how your password was compromised. It is not a conclusive list.

The bottom line is – we detected spam being sent out from your account. We are assuming that it is not you sending out the spam, so we draw the conclusion that your password has been compromised. We do not know how the password was compromised, nor can we know how the password was compromised. But you need to figure out how the password was compromised and then resolve whatever the situation was that allowed the password to be compromised. Doing nothing means that your account will probably just get compromised again and we may have to suspend your account if that happens.

PHP 7.1 broke my website

Wednesday, February 21st, 2018 - General

We are continuing to slowly push out PHP 7.1 by default on all of our servers (see this post). Some users are experiencing issues with this upgrade.

First of all, I want to point out that PHP 7.1 was released on December 1, 2016 (see the table directly from That was nearly 15 months ago. So to claim that PHP 7.1 is brand new, is false. It has been around for quite some time and anyone that develops or writes applications in PHP should be aware of this.

Second, we are seeing some rather significant performance gains with PHP 7.1. So it would be to your benefit to insure that your website and scripts can take advantage of PHP 7.1 so that your website can experience the performance gains.

If you are having problems after the server has been upgraded to PHP 7.1, then you fall into one of two categories:

1. You are using an outdated script (or addons/component/extension/plugin/theme/etc) on your website. Keeping your scripts (or addons/component/extension/plugin/theme/etc) up to date is important to insure that your website is patched up from any known security holes. When developers of these scripts or addons find a security hole in their code they will typically fix this and patch it up and release an updated version of the script. But if you are not using that updated version then you are not protected against that security hole. That means that if you have Example CMS version 1.0 installed on your website and a privilege escalation bug is found in Example CMS version 1.0, the developer of Example CMS fixes the security hole and releases Example CMS version 1.1 to fix it, then if you continue to use Example CMS version 1.0 you are still vulnerable to this privilege escalation bug.

Additionally developers release updated versions of their scripts to take advantage of newer technologies. Software goes end of life - we explained some of the end-of-life reasons back in this post from 2013 - and developers have to stay in step with what is current. PHP 5.6 included a lot of functions and methods that were slow, those functions and methods have been completely replaced in PHP 7.1. Developers of scripts and web applications have to be aware of this and change their code accordingly.

2. You are using an abandoned script (or addons/component/extension/plugin/theme/etc) on your website. Keeping your scripts (or addons/component/extension/plugin/theme/etc) up to date is important. But just as important is making sure that you are using reputable scripts (or addons/component/extension/plugin/theme/etc). This is probably a bit more common with script addons rather than core scripts themselves. If the developer of a script or script addon is not going to properly maintain the code in that scripts then it is of no use to you. Sure, you may be using the latest version of Example Script Addon, but if the last version of Example Script Addon was released 5 years ago, then it is not being properly maintained and the developer likely abandoned the project. We see this happening a lot.

Think of all of the security holes that may have been found in Example Script Addon in those 5 years. Those security holes are not being patched. Think of all of the poor coding that exists in that addon. That coding is not being fixed.

So if you are experiencing problems with the PHP 7.1 upgrade and all of your scripts (and addons/component/extension/plugin/theme/etc) are up to date, then you are very likely using an abandoned script or script addon and the developer is no longer concerning themselves with it. You should stop using that script or script addon.

If you continue to have issues with PHP 7.1 we can switch you back to PHP 5.6, but please understand that this is only a temporary fix. PHP 5.6 support is not going to be around forever. If your the script or script addon you are using on your website is not working with PHP 7.1 then the issue is with the script - it fits into one of the two categories from above. You need to be making arrangements to have the script or script addon updated or switched to support PHP 7.1 so that you will not be caught off guard when PHP 5.6 support is completely removed.

One of the reasons why we are doing this upgrade now is so users can identify if they fall into one of the above categories and can make arrangements to resolve those issues before PHP 5.6 support is completely lost.

Joomla! Update Issues

Thursday, February 1st, 2018 - General

(Please note – at the time of this post – February 1, 2018 – the latest version of Joomla! was version 3.8.4. If you are reading this post after February 1, 2018 then the versioning may have changed)

Updating your Joomla! script can be a hassle. Unlike a lot of other Content Management Software, Joomla! updates are typically more demanding. Depending on what version of Joomla! you are updating from, the update process may cause you some issues.

Joomla! 3.8.0 or greater – Update should go through without any issues.
Joomla! 3.6.5 – Joomla! 3.8.0 – Update should go through but you may have to sort out some issues.
Joomla! 3.6.5 or lower – The update very likely won’t go through.

Keep in mind, if you don’t keep your Joomla! script up-to-date, then it’s a matter of WHEN your website will be hacked, compromised, and abuse and not a question of IF. While updating your Joomla! script might be painstaking it is a necessary step.

We really encourage you to post any questions you have about updating your Joomla! script at the Joomla! Community Forums:

We are not all that well-versed in how Joomla! is coded and how it is maintained. The folks at the Joomla Community Forums have a much better grasp of this.

3.8.0 or greater
If you are updating from a Joomla! 3.8.0 or greater, then the update process should go on without any issues. Although I would encourage you to make sure that you have plenty of disk space on your account, and making a backup before performing the update is never a bad idea.

A version between 3.6.5 and 3.8.0
If you are updating a Joomla! script that is 3.6.5 or greater, then the update process will probably go through – although you may encounter a few issues. I would encourage you to make sure all of your themes, extensions, and addons are up-to-date before attempting an update. Again make sure you have plenty of disk space for the update process and backing up your script before performing the update is never bad idea.

From what I have read, Joomla! versions 3.6.5 and greater have very few issues with the update process, but issues are known to pop up.

A version less than 3.6.5
If you are using a Joomla! version less than 3.6.5, then chances are the update process won’t work. Depending on how far you are from Joomla! 3.6.5, you might be able to wiggle your way into an update, but it requires a lot of work and just depends on each individual case.

If you find yourself using an extremely old version of Joomla! we would really recommend that you delete that script and start your website over with a fresh, up-to-date version of Joomla! (or another CMS) and keeping the script up-to-date from now on.

If you encounter any issues with the update process, again we are going to refer you to the Joomla! Community Forum at:

If you have any other questions about the Joomla! update process, we would recommend that you discuss it on their forums.

Why do Joomla! updates fail?

Wednesday, January 31st, 2018 - General

Joomla! is a very powerful and very popular Content Management System used on many websites. However updating Joomla! and keeping it up to date is often very difficult. We know this, but unfortunately we don’t have many answers.

Why should I update my Joomla! script?
You’re kind of between a rock and a hard place when it comes to weighing the virtues of updating your Joomla! script and leaving it out of date. Joomla! is a heavily targeted CMS for exploits and abuse – this means that if you don’t keep your Joomla! script up to date the chances of your web hosting account being hacked and used for abuse goes up. However, on the flip side, attempting an update of your Joomla! site increases the chances that your website will break due to the update process. So you really are between a rock and a hard place.

Unfortunately for us, we believe security trumps everything else, so it’s really wise to keep your scripts – including Joomla! – up to date. So failing to keep your Joomla! script up to date can lead to security issues on your account and can lead to the suspension of your account. While we do recognize just how finicky Joomla! is about it’s update process, we really just can’t stand by while outdated Joomla! scripts are compromised and used for abuse.

How can I increase my odds of a successful Joomla! update process?
Keeping your Joomla! script up to date will help alleviate some of the strain in the Joomla! update process. For example, Joomla! 3.8.4 was just released this week. If you are using Joomla! 3.8.3 then the update process to Joomla! 3.8.4 is much, much more likely to go through successfully compared to a Joomla! 3.6.1 to Joomla! 3.8.4 update. Any Joomla! 3.8 script is more likely to have a successful Joomla! 3.8.4 update process compared to any previous versions.

The further down you are updating from, the less likely the update process will go through successfully. In fact, if you are using anything less than Joomla! 3.6.5 then the chances of a successful update go down rather substantially. If you are not even using Joomla! 3.x.x then an update isn’t even possible.

If you are attempting an update of your Joomla! script and you are not using any where close to a latest version of Joomla! then we highly suggest that you reach out to the Joomla! Community Forums at:

because they are much more aware of what steps need to be taken before attempting an update that can help for a smooth and successful update.

(Just a note – at the time of this post – January 31, 2018 – the latest version of Joomla! was Joomla! 3.8.4)

Why are Joomla! updates so difficult?
This is a good question, and we encourage you to ask and participate in discussions involving this at the Joomla! Community Forums

The Joomla! developers will tell you that more times than not issues related to Joomla! updates stem from the various components, themes, extensions, and plugins that end users have installed on their Joomla! site – and they’re probably not wrong. There are a ton – an uncountable number – of various Joomla! themes, extension, plugins and addons that can be added to Joomla! to extend it’s use. It is impossible for the Joomla! developers to stay in tuned with all of these addons to know how they will react to certain updates. A lot of those addons are either poorly written or were abandoned many, many years ago and are no longer receiving any updates or attention from their respective developers.

We would encourage you to keep your Joomla! addons to a minimum – this helps to alleviate potential conflicts with update processes.

We also encourage you to use well written and reputable addons on your Joomla! site. The higher the reputation is with the developer of an addon (theme, extension, plugin, etc) then the higher the chances are that the developer has released an update for the latest version of Joomla! and will be there to help you should you have any problems.

All Joomla! addons are written based on the Joomla! framework. When that framework changes between major Joomla! versions, this has an adverse affect on how those addons operate within the Joomla! update process.

This all points back to using well written and reputable addons. If you are using an addon that hasn’t been updated in years, then chances are it’s abandoned and it will cause issues during the Joomla! update process. If you have other concerns about any addons, we really recommend that you discuss all of this with the people at the Joomla! Community Forums:

Can I continue to use my outdated version of Joomla! on my site?
I suppose the best answer to this is both Yes and No.

The answer is No because using an outdated version of Joomla! on your site is a security issue. If you continue to use an outdated version of Joomla! your web hosting account will get hacked, compromised, and used for abuse. It is not a matter of IF but a matter of WHEN. And when that does happen, we will have no choice but to suspend your web hosting account and you will basically have to start your website over from scratch.

So while the answer might be Yes that you can continue to use your outdated version of Joomla! you should really realize that you are running it on borrowed time. It is only a matter of time before it will be taken down.

If you have concerns over why you should update your Joomla! site or the update process in general, again we really want to point you to the Joomla! Community Forums:

Tell them that you don’t like the Joomla! updates breaking your site. Or the fact that you have to keep your Joomla! site up to date to prevent hackings, compromises, and abuse. Voicing your concerns with the Joomla! developers and communities is the only way changes are going to be made to this process.

Net Neutrality and Internet access

Tuesday, December 12th, 2017 - General

In the US, the FCC is waging a war against Net Neutrality. On December 14th, the FCC is going to vote on how to classify Internet Service, which can lead to an end to Net Neutrality.

What is Net Neutrality?
Basically Net Neutrality is a set of rules that says Internet Service Providers (ISPs) can’t purposefully give one connection more priority over another connection. In layman’s terms it means that ISPs can’t intentionally throttle a connection to NetFlix while not throttling a connection to DirecTV Now.

What does this mean for you?
As more and more users “cut the cord” with their television viewing habits, a lot of people are replacing that with subscriptions to various video streaming services – NetFlix, Amazon Video, Hulu, Sling TV, DirecTV Now, Playstation Vue, etc. This is all due to the high carriage fees that TV providers have to pay in order to show content from your favorite TV networks. But those fees are never made public, so it’s entirely possible for TV providers to increase prices during these carriage disputes and pocket some of the profit.

A lot of the Internet Service Providers in the US are also TV Providers. When users cut the cord and don’t pay for TV from these providers, those providers lose some money that they would otherwise profit from.

If Net Neutrality is voted down on December 14th, then it may become possible for Internet Service Providers to slow down access to services like NetFlix, Amazon Video, Sling TV, etc. And if users can’t stream video from these video services, they would be forced to either pay more for an Internet package that allows for streaming or go back to subscribing to TV from their Internet Service Provider so that the TV provider can get more profit.

Bottom Line: Voting out Net Neutrality is a win for TV and Internet Service Providers and a loss for consumers. Unless those TV and Internet Service Providers turn that extra money consumers are paying them into better infrastructure and extending their coverage areas. But will they do that? Not a lot in the history of TV and Internet Service Providers says they will.

What does all of this mean for the web hosting industry?
The short answer is, we don’t know. It probably won’t affect connections to our hosting services very much. There’s just no real reason for ISPs to block or throttle connections to regular websites. Their main concern is going to be the various streaming services out there. But, without Net Neutrality rules in place – ISPs will have the opportunity to throttle connections to certain servers that host websites. If a website is extremely popular, ISPs could decide to cash in on that opportunity and charge consumers extra for the ability to access those popular websites. This would be a strict money grab, but without Net Neutrality rules in place, it would not be illegal.

How can you help?
You are encouraged to contact your congressional representatives and tell them that you want Net Neutrality rules to remain. If elected officials feel the heat from their constituents that they may not be re-elected if Net Neutrality ends, then more of those elected officials will start listening.

You can help by going to:

and seeing all of the ways you can help.

These is also more information at:

Contact Information

AMS Computer Services, Inc

Contact Sales/Billing
Submit a Support Ticket
Password Reset Link
Account Management Area

Mailing Address:
AMS Computer Services, Inc
299 Midway Rd.
Murray, Kentucky 42071

Facebook:Like us on Facebook

Twitter: @AMSCustomerCare

Latest Announcements:
Copyright AMSComputer Services, Inc. All rights reserved.

Products and Services
Datacenter Information
About Us
Policies and TOS
Open a Support Ticket
Guides and Information
Support Blog
Access Welcome Letter

logo_placeholder logo_placeholder logo_placeholder logo_placeholder

logo_placeholder       logo_placeholder       logo_placeholder