MikeJ

What do you mean when? I live in a padded room. Don't you all?

Kevin asked a valid question, let's not jump all over him. So are you able to access your cPanel now, Kevin?

Perfectly acceptable. When you sign up, you get a welcome email after your account is created with your login info, IP address of site, and nameserver info. The nameserver info you can ignore since you want to use your own. Your mail server, web server, ftp server, and any subdomains you create, will need to point to that IP address you get in your welcome email. If you decide to sign up and have any problems, the help desk should be able to provide you assistance.

Keep in mind that the email restrictions are not there soley for the purpose of preventing spamming. Shared systems are just that... shared. If you send out a large amount of email all at once, this uses up resources that others are using (mail) which can slow down delivery for other users when you are filling up the mail queue for mail to be sent. The most effective way to manage large mailing lists would be to have multiple separate redundant mail servers to deal with the load (if it were to be supported en mass), but TCH's primary focus is on low cost webhosting, not providing mass mailing services. Even with a static IP, we wouldn't change the emailing policy for a shared host client. Your best options if the TCH email restrictions are too restrictive for your needs, is to either look into a dedicated server, or look at outsourcing options for your mailing list. I'm not making this statement because we don't want your business, or don't value you as a customer. It's because TCH has to stay focused on what currently makes sense for us to provide to our mass customer base, and what although might be nice to have, but doesn't make sense in TCH's business model at this point.

That would be a typical error you would get if the port is blocked by your companies firewall.

15 minutes and 6 views .... give us a little time to discover the post. If you cannot access 2082, you can try https://******:2083 to get to the https (SSL) port, however it's likely they will block that port as well. The most appropriate way to get it to work, though, is to have your network group allow those ports through. Circumventing their firewall rules could be hazardous to your job.

It stands for Limited Liability Company, one way of registering a business in the United States. It's just another form of business registration, like sole-proprietership and corporation. Each one has different tax and legal benefits. For more info: http://www.llcweb.com/Basics.htm

We are well aware of the owner of that site.

FYI, port 26 is also open for SMTP traffic, if you run into providers that block 25. SSL SMTP (on port 465) and SSL POP and IMAP (on port 995 and 993 respectively) are all supported. I send and get my mail that way myself.

FYI, Bruce's statement is correct. $_SERVER['DOCUMENT_ROOT'] returns the document root based on the site you are requesting, which in your case because you are using a subdomain, is "/home/squortc/public_html/santa-cruz", therefore the include fails because that directory doesn't have the inc subdirectory. Since your included files are not in your subdomain, you can use the include like you have done so (an external call using absolute domain name as Rob suggested), or if you want an abosolute path, but still flexible by using a variable, the following should effectively work: ><?php include $_SERVER['DOCUMENT_ROOT']."/../inc/menu-sa.php"; ?> The .. tells the path to go up one directory from your subdomain's document root to find the inc directory. Therefore that include should work for any subdomain you make off that primary domain.

As you pretty much figured out already, cPanel's show file contents has some issues with spaces in the file name (as in it doesn't work ). It's probably good practice to avoid spaces in filenames anyway to make things the most compatible and easiest to access.

Hi. Thought I would put your last question to rest: SMTP Auth is supported. Mail Submission Agent is not.

If that's all you are using that MT installation for, moving everything to the cgi-bin directory of that subdomain will likely make your life the easiest. If you use cPanel to define the subdomain, it will take care of configuring the cgi-bin for that subdomain for you, otherwise you may need to make changes to your httpd.conf file, or .htaccess files to get the cgi-bin directory to work.

The second part of what Lisa stated should work for you. If you are using cPanel (you don't specify, and you don't appear to be a TCH customer)... cPanel automatically defines a cgi-bin directory for each subdomain, so you could move the MT cgi files into the subdomain's cgi-bin directory. Otherwise, you will need to keep your CGIPath defined the way you originally had it using the IP address.

mms stands for Microsoft Media Server. mms:// is used for streaming .asf (Advanced Streaming Format) files which is basically windows media audio and video.

Hi Kevster, PHP itself has a 2 meg limit by default. You can change this default in your .htaccess file. Just put in your .htaccess file in your public_html directory (or the top directory of your forum software) the following line: >php_value upload_max_filesize 10M That would change the max file size allowed to 10 megs. Change the 10M if you decide you want a different file size allowed.

Dug up the specific details for this particular virus. This particular virus you are receiving email from is called the Beagle or Bagle Virus. If you scroll down to technical detail #9, you'll see the email characteristics which your above examples match one case of. That page also describes the details of how the virus spreads. Getting the email doesn't mean you are infected. It means someone else is infected and the virus on their system sent the mail to you. However, it's a good idea to make sure you have AntiVirus running on your own machine to make sure that you don't in turn get infected and propogate these viruses. I'm responding to your PM now, but this info I felt was good to repeat for the general public.

First, take a deep breath. That is the common format of a virus. It attempts to concern you by making you think something is going on with your account or address in order to get you to open the attachment which is likely a virus or an attempt to collect information for identity theft. The email was most certainly "spoofed" or faked to make it appear like it came from your domain. One unfortunate part of the Internet's current email architecture is that from addresses can easily be faked. If you look at the headers, you can find in the Received lines that the message indeed did originate somewhere else. If it'll help you feel more comfortable, PM me or forward me a copy of the email headers to mikej {at} totalchoicehosting.com (or simply post it in here) and I'll show you the information that shows where the message originated from. Bottom line, though, your email account should still be just fine. Thumbs Up

To be accurate since it's being asked... /sqmail is an "alias" to where sqmail is actually located. This alias is configured in the web server software (apache). The real sqmail directory is in a central place on the server. A symbolic link is the term used for when a file is created on the file system that points to another file or directory (same concept as "shortcuts" in Windows). Both accomplish the same thing in this particular type of case. The primary difference is that the alias is translated at the application level (web server) before any attempt to access the filesystem is made and the symbolic link is translated at the file system level. Symbolic links you would see. "www" is a symbolic link to "public_html" in your home directory, for example. Go into either and you end up in the same place.

Whether it's root or not shouldn't affect it, as long as what you have in the blog config matches. In the weblog config core setup, make sure your Site URL is correct (Should be something like http://subdomain.domain.org/blog/) and your Archive URL is correct. Your local paths should not have changed if you didn't move your blog physically to another directory. In your mt.cfg file, you will need to change CGIPath to point to where your mt.cgi file is (how you reference it as a URL using the subdomain). Depending on your setup, you may need to modify StaticWebPath as well.

Key thing for the templates problem..... take a look at how it's referencing your style sheet. It sounds like it can't find your css file. Did you rebuild all of the pages after making the changes in the MT config? That *should* fix most if not all references.

I ran across a page someone put together with a feature breakdown of several different blog engines in case someone finds it useful. I personally only have extensively used MT and WordPress, but the chart in general looks relatively accurate. You can find the chart here: http://www.asymptomatic.net/blogbreakdown.htm

BoxTrapper is part of 4 features that make up cPanel Pro. When cPanel updated it's themes, it added those options (and defaulted them to available) whether the server has cPanel Pro or not, so that's why you may see the option and it doesn't work (most of the servers do not have cPanel Pro addon). Those extra options just haven't been turned off from displaying on all of the servers yet. Due to the fact those 4 features added in cPanel Pro still are rather buggy and not really reliable, TCH isn't supporting them yet. All BoxTrapper does, btw, is require *everyone* who sends you email to opt-in, before you will receive their email (the send an email, your boxtrapper sends a response, they have to verify themselves, and only then will you start receiving their email). Not too bad in theory if you like that kind of setup, but from what I've seen so far, it (Boxtrapper in particular) hasn't worked quite so well in practice.

I personally use Transmit ( http://www.panic.com/transmit/ - not free, but free trial available ). There are other good apps, though, like even CuteFTP has a Mac version.

Hi Paulo, TCH currently doesn't support any languages other than English, plus the cpanel themes aren't exactly 100% language aware yet to my understanding. As a reseller you don't have access to create/modify language files. If you are on a dedicated server, your root WHM account has the ability to modify language files. You would likely have to do the translations yourself, however, since I'm not aware of a reliable source for cPanel language files yet.