[Bluehost Support Center] Recently Changed Articles

Displaying Email Headers

Thu, 19 Nov 2009 19:22:22 GMT

Problem:

How do I display the Internet email header?

Solution:

Introduction
The full Internet email headers include useful and sometimes necessary diagnostic information. Typical reasons include blocking spammers (unsolicited junk email), problems with delivery or receipt of a particular message and certain identity troubleshooting issues that involve fake "from" addresses. Displaying headers in some email programs is an easy task, however, both Outlook and Outlook Express are more difficult in this regard.
How to Display Full Headers
Select your email client from the list below:

AOL

Entourage

Eudora

Gmail

Hotmail

Mail for Mac OS X

Mozilla

Mulberry

Netscape

Outlook and Outlook Express

Pine

Thunderbird

Webmail

Show me an example of a message with full headers.

AOL:
The email files are in an html format. The objective is to save the file in html format. This can be done as follows:

Open the email message you want to save, as if you were reading it - Near the top, at the bottom of the To: / From: section, click on "Details" to reveal the header. (you could simply copy and paste this information also).

Move mouse cursor to the top tool bar, click on "File".

Move mouse cursor to "Save as..." and click.

Identify which directory you would like to save the file in. This is done using the normal save function of Windows. If you are not real comfortable with directories, save the file in "Desktop". This will have the file icon visible on you regular desktop screen and very easy to find later on.

Provide a name of the file in the "file name" box.

Select the "type" as "html" if possible. If your browser does not show "html" type, just select the type as "All Files" and add ".html" to the file name generated in step 6, such as email.html. The "dot" before the html extension is important. The objective of this step is to have the extension of the file as an "html" type file. Press "Save".

To forward the file to someone else (Bluehost support, law enforcement, lawyer, ISP):

Move cursor to the top tool bar and click on "Write"

Insert the email address you want to forward the file to

Type any info in the body of the message, if needed

To add the html file you just generated in the above steps, click on "Attachments"

When the "Attachments Window" opens, click on "Attach"

Find the file in the directory window and highlight the file name. If you followed the "Desktop" instructions, the directory name is "c:\desktop". If there are too many files that appear, type "*.html" in the file name. The use of the asterisk (also called a star by some) lists all files that are html.

Click on "open"

Click on "OK"

Click on "Send now"

The message and attached file have now been sent.

Note: Please be aware that AOL only keeps messages in your INBOX for two weeks, unless you save it as NEW or save it in a separate folder in your AOL directory on your computer. Additionally, a screen name of TOSEMAIL1 has been identified as a source of help for unacceptable email in the AOL system. Just enter tosemail1 in the "send to" screen. If you are outside of the AOL environment, the address is tosemail1@aol.com.
Entourage:
From the View menu select "Internet Headers". The full headers will appear in the box above the message text. You will need to copy and paste this information in to the message you are forwarding.

Eudora:

Select "plain text only" to turn off any HTML formatting that may be present. From the Tools menu select Options then Styled Text and click Send plain text only.

Open the message in question so you can see it on your screen.

Click on the "Blah Blah Blah" when reading the message.

Forward the message on to the appropriate staff member. i.e. "support@bluehost.com"

See the bottom of this document for an example of what a full header should look like.

Gmail:
To view the e-mail header information:

In Gmail, open 'original' email.

Click for menu button (down arrow next to the Reply button).

In menu, choose Show original.

GMail opens original email in new window or tab.

Hotmail:
To view the e-mail header information:

In the left pane, click Mail.

In the Folders list, click Inbox.

Right-click the message in the message list and then click View source.

Mail for Mac OS X: Mac OS X 10.0 through Mac OS X 10.2: Select "Show All Headers" from the View menu.

Mac OS X 10.3 and later: From the View menu, select "Message" and then "Raw Source". Select the entire contents of the window, then cut and paste it into a new message. Add a subject line, address the message to Bluehost support.

Mozilla & Netscape (all versions):

Turn off any HTML formatting that may be present. From the Edit menu select Preferences then Mail & Newsgroups. Click Send Format and select Convert the message to plain text...

Open the message in question so you can see it on your screen.

For Mozilla 1.4 and earlier: From the View menu select Headers and then All when displaying the message.

For Mozilla 1.5 and later: From the View menu select "Message Source." You can then cut and paste the full-header from the top of the message. (There is an example full-header at the bottom of this page).

Forward the message on to the appropriate staff member.

See the bottom of this document for an example of what a full header should look like.

Mulberry:

Open the message in question so you can see it on your screen.

Select "Show Header" from the "Message"menu.

Forward the message on to the appropriate staff member. Turn off any HTML formatting that may be present. In the "Forward" composition window, verify that "plain" is selected.

See the bottom of this document for an example of what a full header should look like.

Outlook and Outlook Express:

Open the message in question so you can see it on your screen.

Turn off HTML formatting. From the Tools menu select Options... then click the Mail Format tab. At the "Compose in this message format" area select Plain Text.

Outlook: From the View menu select Options... while viewing the message. Outlook Express: From the File menu select Properties, then select the "Details" tab.
Outlook:

Outlook Express:

Click anywhere inside the text frame that appears, then press the keys "CONTROL" and "A" which should select all of the text. This will make the text appear as inverse (shown below).

After the text is selected, hold down the control key, and press 'C' to copy the text to the clipboard

Compose a new message to Bluehost support and in the body of the message select paste (hold the control key and press 'V') which should paste the text into a new message. After you have pasted the text, send the message and you have completed the process.

See the bottom of this document for an example of what a full header should look like.

Pine:

Once Pine is open, press the "M" key to make sure you are at the main screen.

Select "S" or arrow down to select "Setup"

Select "C" for Config.

Find the "enable-full-header-cmd" (You may have to scroll down quite a bit). Use the "X" key to select that option, then press "E" to exit. Press "Y" when prompted to save your change.

To display full headers, press "H" when reading the message.

Forward the message on to the Bluehost support.

See the bottom of this document for an example of what a full header should look like.

Thunderbird:

Open the message in question

From the View menu select "Message Source"

From the Edit menu select "Select All"

From the Edit menu select "Copy"

Close the window: from the File menu select "Close"

From the File menu, select "New..." then "Message"

Place the cursor in the body of the new email message by clicking in the empty message body

From the File menu select "Paste"

Address the message to Bluehost support

Add a subject line

Click the "Send" button

Web Email:

Login and select the "Preferences" option.

Turn off HTML formatting.

Make sure the "Show Full Headers button" is enabled.

Click on "Show full headers" when viewing the message.

Open the message in question so you can see it on your screen.

Forward the message on to the Bluehost support.

See the bottom of this document for an example of what a full header should look like.

Macintosh users please note: The screenshots here are for Windows, but you'll find that in most cases the menu locations are the same on the Macintosh. For example, the "blah blah blah" button in Eudora for Macintosh is the same button in Eudora for Windows.

What does a full header look like? See the example below.

-----------------------Example Full Header Below----------------------------
Return-Path: <hosttech@gmail.com>
Delivered-To: support@bluehost.com
Received: (qmail 23699 invoked by uid 0); 12 Nov 2009 15:14:06 -0000
Received: from unknown (HELO psmtp.com) (64.18.2.187)
  by officemail.bluehost.com with SMTP; 12 Nov 2009 15:14:06 -0000
Received: from source ([209.85.210.177]) by exprod7mx234.postini.com ([64.18.6.14]) with SMTP;
	Thu, 12 Nov 2009 09:14:06 CST
Received: by yxe7 with SMTP id 7so2045938yxe.25
        for <support@bluehost.com>; Thu, 12 Nov 2009 07:14:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:date:message-id:subject
         :from:to:content-type;
        bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=;
        b=S5ZryZZDthVDpa+AewfoxvwgdiT4eKyEM8fR7U55kPJR5llEijqs7jGf/woOLQKkeL
         /Hls0HcojcsCxFW1Lkg5iCJQ3zXWZkvSoW7WSO88pNdzrpPIaYKSixbj2Ex0iao0w8p8
         rqEKLQPPL8HC+AFWyikBsA9o78WQtBUzZqdmM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=NTSUn5Bd+VSwoO7O2QDhm8Ut5KyAaQKdkEVT8pQ8wjZuag+Z3d/MTj2+NVrZVakqEB
         /1jOSCwyCurMMid14L4CVSF7dfCJkvla666BfdCYgLShKEK3nPec3Ap9YN2mlHPw/aRG
         rcYIJh1n60/BePZNJx6+YiQWIOgIYqoxtZXkk=
MIME-Version: 1.0
Received: by 10.150.19.4 with SMTP id 4mr5441077ybs.216.1258038842463; Thu, 12 
	Nov 2009 07:14:02 -0800 (PST)
Date: Thu, 12 Nov 2009 08:14:02 -0700
Message-ID: <53c9aa890911120714l74c69c0k7dcc6e67abd79c20@mail.gmail.com>
Subject: blah
From: Bluehost Tech <hosttech@gmail.com>
To: support@bluehost.com
Content-Type: text/plain; charset=ISO-8859-1
X-pstn-neptune: 0/0/0.00/0
X-pstn-levels:     (S:72.19780/99.90000 CV:99.9000 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:97.0282 C:98.6951 )

Keywords: internet email mail header

Understanding Email Headers

Thu, 19 Nov 2009 17:22:51 GMT

Understanding Internet email headers.

What is the value of the Internet Email Header?
Here are few reasons it may be necessary to review the headers:

Investigate possible Spoofing and determine the source of the message.

Analyze timestamps along the delivery route and identify the source of any delay.

Test any of the mail servers in the path to see if they are on a blacklist.

Review Spam Assassin score.

Determine if the message was routed through the Postini filtering server prior to arrival.

While you may think reviewing email header information is too technical, Internet investigations are NOT rocket science. As with most detective work, you know what has happened and to whom. All you need to do now is find out who or what happened by reviewing the contents of the Email header.
What is a header?
The header is a section of code that contains information about from where the e-mail came and how the message reached its destination. Headers will contain the e-mail address of the originator and/or the computer the perpetrator/sender was using.
Here is what the typical Internet email header looks like. What you are looking for in the header is the IP address, sometimes conveniently identified as the "Originating IP". We can trace to the Internet service provider (ISP) with the date and time of the offending e-mail using the IP address of the sender's computer. The IP addresses in the example below are shown in bold font.
Return-Path: <hosttech@gmail.com>
Delivered-To: support@bluehost.com
Received: (qmail 23699 invoked by uid 0); 12 Nov 2009 15:14:06 -0000
Received: from unknown (HELO psmtp.com) (64.18.2.187)
  by officemail.bluehost.com with SMTP; 12 Nov 2009 15:14:06 -0000
Received: from source ([209.85.210.177]) by exprod7mx234.postini.com ([64.18.6.14]) with SMTP;
	Thu, 12 Nov 2009 09:14:06 CST
Received: by yxe7 with SMTP id 7so2045938yxe.25
        for <support@bluehost.com>; Thu, 12 Nov 2009 07:14:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:date:message-id:subject
         :from:to:content-type;
        bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=;
        b=S5ZryZZDthVDpa+AewfoxvwgdiT4eKyEM8fR7U55kPJR5llEijqs7jGf/woOLQKkeL
         /Hls0HcojcsCxFW1Lkg5iCJQ3zXWZkvSoW7WSO88pNdzrpPIaYKSixbj2Ex0iao0w8p8
         rqEKLQPPL8HC+AFWyikBsA9o78WQtBUzZqdmM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=NTSUn5Bd+VSwoO7O2QDhm8Ut5KyAaQKdkEVT8pQ8wjZuag+Z3d/MTj2+NVrZVakqEB
         /1jOSCwyCurMMid14L4CVSF7dfCJkvla666BfdCYgLShKEK3nPec3Ap9YN2mlHPw/aRG
         rcYIJh1n60/BePZNJx6+YiQWIOgIYqoxtZXkk=
MIME-Version: 1.0
Received: by 10.150.19.4 with SMTP id 4mr5441077ybs.216.1258038842463; Thu, 12 
	Nov 2009 07:14:02 -0800 (PST)
Date: Thu, 12 Nov 2009 08:14:02 -0700
Message-ID: <53c9aa890911120714l74c69c0k7dcc6e67abd79c20@mail.gmail.com>
Subject: blah
From: Bluehost Tech <hosttech@gmail.com>
To: support@bluehost.com
Content-Type: text/plain; charset=ISO-8859-1
X-pstn-neptune: 0/0/0.00/0
X-pstn-levels:     (S:72.19780/99.90000 CV:99.9000 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:97.0282 C:98.6951 )
Which of the IP addresses above should you trace? Usually, the originating IP (in this case, 209.85.210.177) is either called that, and/or is closer to the bottom of the stack, nearer to the actual body of the message.
It is important to note that this source IP address (209.85.210.177) will not resolve on the Internet as it is within a block of IP addresses that are "reserved" private IP addresses. They are used behind corporate firewalls and proxy servers. They access the outside world through a NAT service, which stands for Network Address Translation. To find where this IP address is located, you will have to contact the network administrator responsible for the IP address 64.18.2.187, which is a legitimate internet IP address and through which this private IP address passes on its way to the internet.
RFC 1918 describes IP addressing guidelines for private networks and for which IANA (Internet Assigned Numbers Authority) has reserved for private networks. There are three sets of reserved private numbers, one respectively for each IP network Class A, B & C. They are:

10.0.0.0 to 10.255.255.255

172.16.0.0 to 172.31.255.255

192.168.00 to 192.168.255.255

Revealing extended headers in different e-mail programs

Keywords: header email IP

Understanding IP Addresses

Thu, 19 Nov 2009 15:38:39 GMT

Problem:

What is an IP address?

Solution:

What is an IP Address?
An IP (Internet Protocol) address uniquely identifies a computer/server on the Internet or on a Local Area Network (LAN). The IP address takes the form of a dotted-quad number, such as 128.175.13.92. No other computer/server on the same network or on the Internet can have the same IP address at the same time.
How does an IP address relate to a domain name?
When we use domain names to access a website or online service, we are using a human readable shortcut which corresponds with the server's IP address. DNS servers on the Internet automatically translate domain names into IP addresses each time we use a domain name.
For more in depth information on the topic of DNS, CLICK HERE

keywords: dns ip address domain

Scripted E-mails appear to come from username@box###.bluehost.com

Wed, 18 Nov 2009 19:26:24 GMT

Problem:

Why do scripted e-mails come from < username@box###.bluehost.com > when I have specified otherwise?

Solution:

This is because our servers require you (or your script) to use a properly formatted, valid From: field in the email's header. If the From: field is not formatted correctly, empty or the email address does not exist in the cPanel, the From: address will be changed to username@box###.bluehost.com. To stop this, you do one of the two options:
1. You must change the script you are using to correctly use a valid From: header.
Examples of headers that should work would be:

From: user@domain.com

From: <user@domain.com>

From: "name" <user@domain.com>

Examples of headers that will NOT work:

From: "user@domain.com"

From: user @ domain.com

2. Modify the php.ini to have a default address:
Find the php.ini file in /public_html

Search for 'sendmail_path'
Modify the variable to appear like the following:
  sendmail_path = "/usr/sbin/sendmail -t -i -f'user@domain.com' "
        
Note: The email address you use must be a valid created account in the cPanel.

Keywords: e-mail email site webpage website forms bluemail box header script php user

DNS Records (MX, CNAME, ARECORD)

Wed, 18 Nov 2009 16:58:50 GMT

Problem:

How Do I Change DNS Settings for My MX, cNAME, A RECORD, etc.?

Solution:

MX Entries:
As a Customer, you can change your MX Entries as you need. Please log into the cPanel to edit these by clicking the MX Entry icon in the Mail section. When multiple MX entries are required with same priority, please contact Tech support via a ticket as described below.
A RECORD, cNAME, TXT:
Please request DNS changes by opening a new ticket in the helpcenter. To help expedite the process, please include the last four digits of the credit card used for the most recent **WEB HOSTING** payment or last four characters of the hosting password inside the body of the ticket.

Please format the ticket as follows for quickest service:

Hello Support,
My main domain is "Insert Main Domain" and the last 4 of my credit card are as follows 0123.

A record: friends.yourdomain.com -> 74.220.195.50 (always point to an IP address)

CName: blog.yourdomain.com -> ghs.google.com

MX Entries: yourdomain.com -> 5 ALT1.ASPMX.L.GOOGLE.COM

MX Entries: yourdomain.com -> 5 ALT2.ASPMX.L.GOOGLE.COM

Note: Our servers do not support Reverse DNS Lookup. This means that a Reverse DNS Lookup will not resolve to the domain name, but instead to the server that the hosting account is on.
We do have TXT entries and PTR entries to help with SPF records when sending email. This shows the email was legitimately sent from a Bluehost server, where the domain will be listed if a Reverse DNS Lookup is done.We do allow customers to request custom TXT entries in order to help fight against spam. Both SPF records and DKIM records are TXT entries in a zone file. Unfortunately at this time we do not support custom PTR or SRV records for customers. If you require custom entries like this you will need to subscribe to a third party DNS service (examples are dyndns.com or dnsmadeeasy.com).

Keywords: DNS MX CNAME ARECORD entry record name mail google apps googleapps reverse DNS SPF

FrontPage Limitations

Tue, 17 Nov 2009 14:31:03 GMT

Problem:

Are There Any Limitations if I Choose to Publish My Site With FrontPage?

Solution:

There are three primary areas of limitation when publishing with FrontPage which you will see error messages or run into problems with.

Web size: This seems to be most critical when a "searchable event" is present in the web (Search, Discussion Forum and Table of Contents). The lengthy process of updating the indices for these functions can lead to the connection timing-out (HTTP 500 Error or 'Server' has timed-out).

Disk Usage: You may create and publish as many child webs as your disk storage space allows. However, for each child web you publish, FrontPage duplicates certain information into indices and hidden files. This adds "overhead", increasing the storage space required for your files.

Time Out: When you are publishing large pictures or have a lot of pages to your web site, often times FrontPage will time out when uploading your files to the Internet. If this should occur, simply restart the publishing feature and FrontPage will recognize what files were already placed into the directory and begin publishing only those files that were left before your connection was timed out.

Keywords: FrontPage publish limitations

DNS A:Record Definition

Mon, 16 Nov 2009 19:28:58 GMT

Problem:

What is an ARECORD?

Solution:

Like everything based on computers, the Internet needs numbers to do, find or process anything. In this case, it uses an Internet Protocol Address (IP Address) to find your site. Only problem? You don't type in numbers to find Google; you type in Google.com because that so much easier to remember than 74.125.53.100.
An Address Record (A:Record) acts as a translator from English to Computer. When you type in Google.com, your Internet Service Provider looks in their database for the number tied to it. If they cannot find it, they look to see who the domain is registered with and work from there.
Once the address is found, your computer can make the connection across the internet to the Google servers. Your browser requests and retrieves the page from their server. This process completes extremely quickly, usually within milliseconds.
A:Records are generally automatically created when you assign new domain or change your Nameservers, though there are times you might need something custom made. To get a DNS change on a domain, please Click Here for the steps.

keywords: dns record arecord a:record nameservers

MySQL Database Creation

Thu, 12 Nov 2009 18:06:58 GMT

Problem:

How do I create an empty MySQL Database

Solution:

To create the database, do the following:

Log into the cpanel

Click the MySQL Databases icon under the "Databases" category

Create a New Database (make it short best result)

Add New User (make it short best result)

Most importantly, select the user and database underneath "Add User To Database" and click "Add" (authentication will not work if you do not click this button).

After doing all these steps, you can create the database tables either via phpMyAdmin or use an online PHP or Perl script.
The username format will be: username_dbusername
The database format will be: username_dbname
The hostaddress will be: localhost
For example, if you enter the following variables:
dbusername: admin
dbname: DB1
password: password
You will end up with the following format that you would place in your connection string
Hostname: localhost
dataName: username_db01
dataUser: username_admin
Password: password
Notice the password remains the same format.
The connection string can be either of any examples below:
For example, we will use the above example variables:
Connection Strings
For PERL
$dbh = DBI->connect("DBI:mysql:username_db01:localhost","username_admin","password");
For PHP:
$dbh=mysql_connect ("localhost", "username_admin", "password") or die ('I cannot connect to the database.');
mysql_select_db ("username_db01");
To create tables and other functions, you can use the PHPMyAdmin located in the Databases section of the cPanel. For more information on how to work with PHPMyAdmin. please visit: phpmyadmin.net.

Keywords: MySQL Database Creation

Zend Optimizer

Thu, 12 Nov 2009 05:09:06 GMT

Problem:

How do I enable the Zend Optimizer on my account?

Solution:

If you are having a problem with the Zend Opimizer please ensure the file called php.ini contains the following lines.

     [Zend]
     zend_optimizer.optimization_level=15
     zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer
     zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS
     zend_extension=/usr/local/Zend/lib/ZendExtensionManager.so
     zend_extension_ts=/usr/local/Zend/lib/ZendExtensionManager_TS.so

Keywords: php optimizer zend

Domain Registry Transfer to another person

Wed, 11 Nov 2009 19:54:52 GMT

Problem:

I have sold, or transfered ownership of my domain, how do i give the domain to the new owner?

Solution:

To transfer the ownership of your domain to another person, please follow these steps:

Disable privacy and update the domain administrative contact information.

Login to your cPanel

Click on the Domain Manager tab

Select the domain that you wish to modify (on the left side of your screen)

Click on the privacy tab (on the right side)

Click the button that says to pause domain privacy

Next click on the tab labeled "contacts" (on the right side)

Update the information listed and click the button "update contact information"

UNLOCK your domain.

Following the above steps, you should still be in the Domain Manager with your domain selected

Click on the Lock tab to the right of your domain name

Click the button "Unlock Your Domain"

Retrieve the EPP or Auth code.

In the Domain Manager, select the Transfer EPP tab to the right of your domain name/li>
Copy the code which is the key to allow transfer.

Contact the new owner and provide them the EPP code. Let them know they can now request the domain to transfer to any Domain registrar of their choosing and setup domain hosting in their name.

Keywords: domain transfer ownership

Wordpress Install with Simple Scripts

Wed, 11 Nov 2009 19:42:52 GMT

Problem:

How do I use Simple Scripts to install WordPress onto my site.

Solution:

To Install WordPress using Simple Scripts:

Log into your Bluehost cPanel.

Select Simple Scripts icon from the Software/Services section.

In Simple Scripts, find the "blogs section and select WordPress link.

Select the green Install button

Follow the three step process to complete the installation

Simple Scripts will populate the default files and database for a brand new installation of Wordpress in whatever location specified in Step 1 of the install process. It will provide you the login link to the back end of Wordpress to begin managing the site. For more information how to use Wordpress script, please see Wordpress.org.

Keywords: install wordpress word press simple scripts simplescripts

URL redirect/rewrite using the .htaccess file

Wed, 11 Nov 2009 19:41:34 GMT

Problem:

How do I perform a URL redirect/rewrite using the .htaccess file?

Solution:

.htaccess Redirect/Rewrite Tutorial

Part 1 - How do I redirect all links for www.domain.com to domain.com ?

Description of the problem:
By default your website can be accessed with both www.domain.com and domain.com. Since Google penalizes this due to duplicated content reasons, you should restrict the access to either www.domain.com or domain.com. Some links may be outside of your website scope and/or the search engines may have already indexed your website under both addresses.
Solution:
Create a 301 redirect forcing all http requests to use either www.domain.com or domain.com:
Example 1 - Redirect domain.com to www.domain.com:
  RewriteEngine On
  RewriteCond %{HTTP_HOST} !^www.domain.com$ [NC]
  RewriteRule ^(.*)$ http://www.domain.com/$1 [L,R=301]
Example 2 - Redirect www.domain.com to domain.com:
  RewriteEngine On
  RewriteCond %{HTTP_HOST} !^domain.com$ [NC]
  RewriteRule ^(.*)$ http://domain.com/$1 [L,R=301]
Explanation of this .htaccess 301 redirect:
Let's have a look at the example 1 - Redirect domain.com to www.domain.com. The first line tells apache to start the rewrite module. The next line:
  RewriteCond %{HTTP_HOST} !^www.domain.com$ [NC]
specifies that the next rule only fires when the http host (that means the domain of the queried url) is not (- specified with the "!") www.domain.com.
The $ means that the host ends with www.domain.com - and the result is that all pages from www.domain.com will trigger the following rewrite rule. Combined with the inversive "!" is the result every host that is not www.domain.com will be redirected to this domain.
The [NC] specifies that the http host is case insensitive. The escapes the "." - because this is a special character (normally, the dot (.) means that one character is unspecified).
The final line describes the action that should be executed:
  RewriteRule ^(.*)$ http://www.domain.com/$1 [L,R=301]
The ^(.*)$ is a little magic trick. Can you remember the meaning of the dot? If not, this can be any character(but only one). So .* means that you can have a lot of characters, not only one. This is what we need because ^(.*)$ contains the requested url, without the domain.
The next part http://www.domain.com/$1 describes the target of the rewrite rule. This is our "final" used domain name, where $1 contains the content of the (.*).
The next part is also important, since it does the 301 redirect for us automatically: [L,R=301]. L means this is the last rule in this run. After this rewrite the webserver will return a result. The R=301 means that the webserver returns a 301 moved permanently to the requesting browser or search engine.

Part 2 - How do I redirect domain.com/ to domain.com/index.php ?

Description of the problem:
You have a website with the name domain.com and you want to redirect all incomming urls that are going to domain.com/ to domain.com/index.php
Solution:
  RewriteEngine On
  RewriteCond %{HTTP_HOST} ^domain.com$
  RewriteRule ^$ http://domain.com/index.php [L,R=301]
Explanation of this .htaccess 301 redirect:
What does this code above do? Let's have a look at Example 1 - Redirect domain.com to www.domain.com. The first line starts the rewrite module. The next line:
  RewriteCond %{HTTP_HOST} !www.domain.com$
specifies that the next rule only fires when the http host (that means the domain of the queried url) is not (- specified with the "!") www.domain.com.
The $ means that the host ends with www.domain.com - and the result is that all pages from domain.com will trigger the following rewrite rule. Combined with the inversive "!" is the result every host that is not www.domain.com will be redirected to this domain.
The [NC] specifies that the http host is case insensitive. The escapes the "." - because this is a special character (normally, the dot (.) means that one character is unspecified).
The final line describes the action that should be executed:
  RewriteRule ^(.*)$ http://www.domain.com/$1 [L,R=301].
The ^(.*)$ is a little magic trick. Can you remember the meaning of the dot? If not, this can be any character(but only one). So .* means that you can have a lot of characters, not only one. This is what we intended. ^(.*)$ contains the requested url, without the domain.
The next part http://www.domain.com/$1 [L,R=301] describes the target of the rewrite rule -this is our "final" used domain name, where $1 contains the content of the (.*).
The next part is also important, since it does the 301 redirect for us automatically: [L,R=301]. L means this is the last rule in this run. After this rewrite the webserver will return a result. The R=301 means that the webserver returns a 301 moved permanently to the requesting browser or search engine.

Part 3 - How can I migrate domain content with .htaccess ?

Description of the problem:
You have an old website that is accessible under olddomain.com and you have a new website that is accessible under newdomain.com. Copying the content of the old website to the new website is the first step - but what comes after that? You should do a 301 moved permanently redirect from the old domain to the new domain - which is easy and has some advantages:

Users will automatically be redirected to the new domain - you do not have to inform them.

Search engines will be redirected to the new domain and all related information will be moved to the new domain (but this might take some time).

Google's PageRank ™ will be transfered to the new domain, as well as other internal information that is being used to set the position of pages in the search engine result pages (serp's) - like TrustRank .

Solution:
Create a 301 redirect for all http requests that are going to the old domain.
Example 1 - Redirect from olddomain.com to www.newdomain.com:
  RewriteEngine On
  RewriteCond %{HTTP_HOST} !newdomain.com$ [NC]
  RewriteRule ^(.*)$ http://www.newdomain.com/$1 [L,R=301]
This is useful when you use www.newdomain.com as your new domain name (see also this article about redirecting www and non-www domains). If not - use the code of example 2.
Example 2 - Redirect from olddomain.com to newdomain.com:
  RewriteEngine On
  RewriteBase /
  RewriteCond %{HTTP_HOST} !newdomain.com$ [NC]
  RewriteRule ^(.*)$ http://newdomain.com/$1 [L,R=301]
Part 4 - How can I add a trailing slash to requested URLs ?

Description of the problem:
Some search engines remove the trailing slash from urls that look like directories - e.g. Yahoo does it. However it could result into duplicated content problems when the same page content is accessible under different urls. Apache gives some more information in the Apache Server FAQ.
Let's have a look at an example: enarion.net/google/ is indexed in Yahoo as enarion.net/google - which would result in two urls with the same content.
Solution:
The solution is to create a .htaccess rewrite rule that adds the trailing slashes to these urls. Example - redirect all urls that do not have a trailing slash to urls with a trailing slash:
  RewriteEngine On
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_URI} !example.php
  RewriteCond %{REQUEST_URI} !(.*)/$
  RewriteRule ^(.*)$ http://domain.com/$1/ [L,R=301]
Explanation of the add trailing slash .htaccess rewrite rule:
The first line tells Apache that this is code for the rewrite engine of the mod_rewrite module of Apache. The 2nd line sets the current directory as page root. But the interesting part is:
  RewriteCond %{REQUEST_FILENAME} !-f 
makes sure that existing files will not get a slash added. You shouldn't do the same with directories since this would exlude the rewrite behaviour for existing directories. The line
  RewriteCond %{REQUEST_URI} !example.php
exludes a sample url that should not be rewritten. This is just an example. If you do not have a file or url that should not be rewritten, remove this line. The condition:
  RewriteCond %{REQUEST_URI} !(.*)/$ 
finally fires when a url does not contain a trailing slash. Now we need to redirect the urls without the trailing slash: pre> RewriteRule ^(.*)$ http://domain.com/$1/ [L,R=301] does the 301 redirect to the url, with the trailing slash appended. You should replace domain.com with your url. Make sure that you stick with the right domain name; if unsure, have a look at this article.
This article was referenced with gratitude from enarion.net.

Keywords: htaccess URL rewrite redirect .htaccess

Hosting Sub Domains

Wed, 11 Nov 2009 19:22:25 GMT

Problem:

How can I host only a sub-domain on my hosting service provided by Bluehost?

Solution:

If you need to host just a subdomain of another domain you have hosted elsewhere, follow these instructions.

Create the account with the name of the domain you host elsewhere. **Example** If you are setting up the domain "subdomain.domain.com", sign up your account with the name as "domain.com"

In your account's cPanel create the subdomain you need to host with us, (ie: "subdomain.domain.com" .)

Contact the host of your domain name's zone file and have them point the A record for the subdomain to the IP of your BlueHost server.

This should take somewhere between 24-48 hours to propagate and your subdomain will be live on our servers.

Keywords: host use sub-domain subdomain

Character sets in PHP

Wed, 11 Nov 2009 19:20:14 GMT

Problem:

How to Set different character sets with PHP and HTML to display correctly.

Solution:

There is a character encoding setting inside of your php.ini file. By default, this is set to the standard Latin encoding (ISO-8859). If you would like to encode your page with different characters, like Arabic or Hindi, you will need to change this.
Most character sets will display correctly with UTF-8 encoding. If you're using an Asian character set, you may need to select a different encoding standard. To find out specific information about which character encoding will display your characters correctly Click Here.
You can find your php.ini file in this directory:
/public_html/php.ini
To change the character encoding in your php.ini file, find the following line and input your preferred character encoding. In the example below, UTF-8 is the character set.
default_charset = "UTF-8"
Note: By default, the default_charset option is commented out. Be sure to delete the leading semi-colon so it does not look like this:

;default_charset = "UTF-8"

Keywords: PHP character sets arabic chinese japanese language languages mysql collation phpmyadmin

Email Attachments - Blocked File Extensions

Wed, 11 Nov 2009 19:13:48 GMT

Problem:

Why can I not send/receive certain types of attachment?

Solution:

Here is a list of file extensions which are not allowed to be sent to any email address on the server. If someone attempts to send an email to a Bluehost account with an attachment that has one of these extensions, the email will be returned to the sender and they will be notified that the attachment cannot be sent.
The reason behind this is because files with these extensions can be used to run a program that will install viruses or seriously damage your computer. Spammers and hackers often send emails with these attachments trying to get users to open the attachment. Once it is opened, the computer is infected.

File extensions:

bat

chm

cmd

com

cpl

crt

exe

hlp

hta

inf

ins

isp

jse?

lnk

mdb

ms[cipt]

pcd

pif

reg

scr

sct

shs

vb[se]

ws[fhc])

Keywords: blocked virus malware trojan email attachment block .exe

PHP Virtual Directory support

Wed, 11 Nov 2009 19:11:18 GMT

Problem:

Virtual directory support for PHP.

Solution:

We do not support Virtual directories (in the traditional sense). These are setup using a VirtualHost container in the httpd.conf file for Apache. We do not provide support for any client's requests for modifying the httpd.conf. Therefore, it is not a possibility on our servers. You can, however, emulate a "Virtual Directory" build using mod_rewrite to rewrite input to a script in another location. See mod_rewrite tutorial for more tips how to use it.

Keywords: Virtual directory support PHP.

phpBB Installation (Simple Scripts)

Wed, 11 Nov 2009 19:04:27 GMT

Problem:

How do I install the forum software phpBB3?

Solution:

To install forum software phpBB3:

Login to your Bluehost cPanel.

Click on the "Simple Scripts" icon listed under the category "Software/Services".

Inside of Simple Scripts, click on "phpBB" under the category "Forums".

Click the install button and follow the prompts.

Keywords: phpbb install forum SimpleScripts Simple Scripts

Spam Assassin version

Wed, 11 Nov 2009 18:59:24 GMT

Problem:

What version of Spam Assassin are you running?

Solution:

Spam Assassin 3.002.004. is currently installed on our servers.
More information about Spam Assassin can be found at: http://spamassassin.apache.org

Keywords: spam assassin version assasin sa spamd

FrontPage will not publish and my Wordpress is not working

Wed, 11 Nov 2009 18:56:40 GMT

Problem:

Have FrontPage extensions and Wordpress installed on account. Was working fine in the past, but now cannot connect with FrontPage and Wordpress does not link properly.

Solution:

Normally, on a Linux/Unix server with the Microsoft FrontPage Server extensions installed Wordpress works just fine and you are able to edit and publish pages (with MS FrontPage) UNTIL you make a change to the permalinks (for example to the date based kind like /2005/04/etc).
Now, the problem is that MS FrontPage uses the .htaccess file (which the Wordpress mod_rewrite rules must go into also) for it is "publishing" and "web authoring" configuration. As soon as the Wordpress mod_rewrite code is added to the file, two things happen:

The permalinks do not work.

The MS FrontPage Server extensions become corrupted.

The solution is actually quite simple.

If you are using or wish to use MS FrontPage along with Wordpress, you'll need to take the following simple steps on your server.
MS FrontPage creates the following directory _vti_bin. Nested within that it creates both _vti_adm and _vti_aut.

In addition to in your website (or Wordpress) root folder in all of those directories, you will find additional .htaccess files.

In all three of these directories AND in the root directory, at the TOP of ALL of the .htaccess files you simply need to add one line:
    Options +FollowSymlinks
There may or may not already be a line in each. Regardless, add the Symlinks line and save each .htaccess file and you are done. Now everything works perfectly, including MS FrontPage AND the permalinks of your choosing.

Keywords: FrontPage wordpress htaccess .htaccess

ASX media formats

Wed, 11 Nov 2009 18:50:00 GMT

Problem:

Do you support the ASX media format on your web hosting?

Solution:

Unfortunately, because the ASX format is specific to Windows Media Servers and Bluehost is a Linux/Unix based company, these Windows Media Formats are not able to run on our servers.
However, you can embed these files for DOWNLOAD ONLY, but your local computer system must support that file format.

Keywords: ASX Streaming Embedding Media Windows

Allow_url_include

Wed, 11 Nov 2009 18:48:31 GMT

Problem:

In the newer versions of PHP, they have included a new directive to control and handle remote includes. We disable this option, by default, which may affect some of your PHP scripts.

Solution:

In your php.ini, put the following line:
  allow_url_include = 1
This enables remote includes.
Note: This requires allow_url_fopen =1 as well, so you may want to search through your php.ini and make sure that is enabled.
Note: You will need to copy your php.ini into the directory on your server where the script is which is calling this directory. For example, if you have a script in public_html/blog/ that needs this setting, then copy the php.ini into public_html/blog.

Keywords: php allow url include allow_url_include remote

PHP Version

Wed, 11 Nov 2009 18:32:23 GMT

Problem:

What version of PHP are you running?

Solution:

Bluehost currently runs PHP 5.2.x. If you would like to see the exact current version, please log into the cPanel and view the PHP version on left column or log into SSH and type the following:
  php --version

Keywords: php version

Python Version

Wed, 11 Nov 2009 18:29:29 GMT

Problem:

What version of Python are you running?

Solution:

Bluehost currently runs Python 2.4.3.
To determine if we have upgraded, please log into SSH and type the following:
  python -V

Keywords: python version

PostgreSQL Version

Wed, 11 Nov 2009 18:23:39 GMT

Problem:

What version of PostgreSQL are you running?

Solution:

Bluehost currently runs PostgreSQL 8.1.11.
To determine if we have upgraded, please log into SSH and type the following:
  psql --version

Keywords: postgres psql postgresql version

Perl Version

Wed, 11 Nov 2009 18:22:18 GMT

Problem:

What version of Perl are you running?

Solution:

Bluehost currently runs Perl 5.8.8.
To determine if we have upgraded, please log into SSH and type the following:
  perl --version

Keywords: perl version