Creating an email address in the control panel creates a mailbox on the server for mail to be delivered to. In some cases this might be desired if you want to maintain full control of the email you receive, however in many cases users may wish to simply create an Email Forwarder that sets up a custom email address and sends all mail sent to it on to the address of your choice. This article will show you how to setup both methods.

• Login to https://domains.skidmore.edu/dashboard using your Skidmore username and password.

• On the homepage of the control panel you will see a section titled Email that contains several tools for setting up email addresses. To get started let’s go to the Email Accounts page.

This screen will allow us to setup an email address that uses a mailbox stored on the server. You will be able to access mail sent to this email address either through a webmail client or a desktop/mobile client directly. Enter the desired email address as well as a password to associate with that email address. You can choose to set a quota for how large of a mailbox you need, or set this to unlimited (keep in mind your quota will still be dictated by the limits of the hosting account). Once you’re done click Create Account.

Your email address is created and it’s ready to be used. You have the choice of accessing it via the webmail options built into your control panel, or setting up a mail client directly from your desktop, laptop, or mobile device. To access these options you can click on the More button.

If you already have an email address you want to use like a Gmail or Hotmail account, you may wish to create an Email Forwarder instead of a mailbox. Setting up a forwarder is very simple. Start by clicking on instead of a mailbox. Setting up a forwarder is very simple. Start by clicking on Forwarders from the Mail section of your control panel homepage.

The first screen will show you any existing forwarders that you have created. To setup a new forwarding account, click Add Forwarder.

To create a new forwarding account, simply type in the desired email address as well as the email address you’d like all mail to be forwarded to. When you are done click Add Forwarder.

You have now successfully created an Email Forwarder and all email sent to your custom email address will be forwarded on to the address you entered.

Create a Self-Hosted Email Account:

Access your Self-Hosted Email Account:

There may be times when you need to place files onto your space on your Web server. There are a number of scenarios when this might be necessary:

• You’re working with an application that allows you to install plugins/extensions, but the files need to be manually moved to the server in order to add them. (Note: This is NOT required with WordPress which allows you to install plugins through the backend in your browser.)
• You’ve developed a custom site/pages using a Web design program, and you need to upload the files you created to the server
• You’re installing an application that isn’t part of the applications in Installatron.

One way to upload files is by using the File Manager that is part of cPanel. However, sometimes you’ll find it easier/necessary to use FTP, or File Transfer Protocol, to move files to the server. This can be particularly useful if you’re working with a Web space where you’re not the owner (so you don’t have access to the File Manager in cPanel) or if you need to provide file access to someone else to your space on the Web server.

File Transfer Protocol is a method that allows you to remotely move files to a Web server from another location – usually your local/personal computer. Using a pre-defined FTP account (with a username and password), you can configure an FTP client (a program you run on your computer that allows you to transfer files via FTP.

There are lots of FTP clients that you can use; some are free and some are not. A few free ones you might consider:

• FileZilla (Mac & PC)
• CyberDuck (Mac & PC)

For the purpose of this tutorial, we’ll show you how to set up FTP in FileZilla, but you should be able to generalize these instructions to use in any FTP client.

If you’re FTPing to your own space on the Web server, or if you’re setting up an FTP account for someone else to use to FTP to your space, you’ll need to start by getting information about the FTP credentials from cPanel:

1. Login to domains.skidmore.edu.
2. In the Search Box at the top of the page, search for “FTP”, and click the FTP Accounts icon that appears.
3. You’ll have the option to create a new FTP account, or you can scroll down the page to find the credentials for the default FTP account. If you want to create an account, fill out the Add FTP Account form with a username and password. By default, the new FTP account will be limited to a directory with the same name as the account you’re creating. You can change this to a different directory, if you want to grant this account access to a different location.  NOTE: Make sure you know/remember the password you enter. When you’re done, click Create FTP Account. 
4. Once you’ve created the new account, you’ll see it appear in the list at the bottom of the FTP Accounts page. In addition to any accounts you’ve created, in the Special FTP Accounts section, you’ll see the default FTP Account. You’ll know this account because the username corresponds to your cPanel username. This FTP account has full privileges to access any space on your Web server. 
5. For whichever account you need credentials for, click the Configure FTP Client link.
6. Write down the username, server, and port information that appears. You will need to use this (or you will need to provide this to the person you are giving FTP access) along with the password you created in Step 3 in order to configure your FTP client. 

Below are links to tutorials for setting up both FileZilla and CyberDuck to connect to you FTP account.

• FileZilla Configuration Instructions
• CyberDuck Configuration Instructions

A subdomain is one way of organizing and separating content on your site. To create a subdomain, use the following steps:

Login to domains.skidmore.edu with your Skidmore username and password to access your cPanel.

Once logged in you’ll be at the homepage of your control panel. The easiest way to navigate the panel is using the search feature in the top right panel. Click the Search box and type “subdomains” (without the quotes). When you press enter, you will automatically be take to the Subdomains page. Or, you can scroll down and click the Subdomains button on the cPanel.

Choose a name for your subdomain and type it into the Subdomain box. Just like top-level domains (e.g. createoutestdomain.com), subdomains can only contain numbers, letters, and hyphens, and the best subdomains are simple, short, and descriptive.

Once you’ve typed in a name, cPanel will automatically populate the Document root field for you. This will create a folder to contain your subdomain’s files. You’ll usually want this folder to match the name of your subdomain, so it’s easy to identify where different files live in your account. You might want to change the document root if you already have a folder in your account that has the same name as the subdomain you are trying to create, although this should be rare. Once you’re done, click Create.

Once you’re done, click Create. If everything went well, you should see a message that your subdomain was created successfully. Your subdomain will now be available as an option for automatic installation of various software (WordPress, MediaWiki, etc). If you prefer to install web applications manually, you can do so in the document root (folder) you created in step 5.

When you’re first getting started with a new space on a new Web host, you might think of yourself as owning a small “territory” of the Web. Everything you place in your public folder on the server becomes available for anyone on the Web to see (assuming they know the address of your site and the files you’ve placed there).

If you’re just putting up a handful of static, HTML pages which you want to make available to colleagues, friends, or family by sending them links, then working with this large, unorganized space may work. But as soon as you get to the point where you want to organize your site, you’re going to need a new strategy.

Consider this scenario: you want to have a personal blog on your new Web space, where you share pictures and short written pieces with family, friends, and colleagues. In addition, you’re working on a large research project that requires you to build a Web-based repository of digital images related to your discipline. You want to use one application (say, WordPress) to manage your personal blog. For your research project, you’ve settled on another open-source application (Say, Omeka). Both of these are applications that need to be installed on your Web host, but you can’t just put them both at your main domain name – if you did, both sites would quickly experience conflicts and errors. You need to cordon off separate spaces for your different Web “properties.”

There are two primary strategies for parceling up your Web space. You can create subdomains or subdirectories. But before you can understand the difference, you need to first understand what we mean when we talk about your root domain.

Let’s say you’ve registered a new domain for domains.skidmore.edu called yourdomain.com. Anything that is stored at this core URL is considered to be at the root of your domain: Nothing comes before the address or after the address. You can certainly decide that you simply want to have a single site on your Web host (say a blog running WordPress), and you can set that blog up at your domain’s root. To get to your site in this scenario, users would simply go to yourdomain.com.

When you want to do more than just have a single site at the root of your site, you need to decide now to organize your space. One way to do so is by setting up subdomains.

You’re already familiar with the concept of subdomains, even if you don’t know it. Consider OU’s public Web site at http://ou.edu. As you browse parts of that site, you’ll notice that the domain changes. When you’re looking at your department Web site, say the site for the Chemistry & Biochemistry Department at http://chem.ou.edu, the URL is no longer just ou.edu. Now the root of the url is chem.ou.edu, indicating that you’re on the part of the site that is dedicated to the Chemistry & Biochemistry Department.

If you browse to the technology store pages at http://itstore.ou.edu, you’ll notice that the domain changes again, this time indicating that you’re in the technology store of the OU site.

As you can see the domains serve two purposes: they help to organize the site from a technical perspective, but they also serve as indications to the users that they are in a new/different space.

As you work on your site, you’re welcome to create as many subdomains as you like, and in each subdomain you can actually create a distinct, individual Web site.

The alternative for organizing your space is to simply set up subdirectories. These function much like file folders on your computer. Instead of creating a blog at blog.yourdomain.com you would place it in a subdirectory called “blog” making the address yourdomain.com/blog. Setting up subdirectory is really easy. You can create folders on the fly when installing applications (like WordPress), and you can also manually create them in your file browser.

There is one particular issue you need to be aware of. Let’s say you’ve installed WordPress to be your primary blog at yourdomain.com. Later, you decide you want to create another image gallery site on your site, and you want to place it at yourdomain.com/gallery. But, if for some reason you’ve already created a page on your WordPress site called “Gallery” then the url yourdomain.com/gallery will already be taken. If you try to create a subdirectory of the same name, you’ll get a conflict and errors.

• Subdomains are generally a cleaner, more elegant solution to organizing your site. You’re less likely to get conflicts or errors. However, when using subdomains the process is slightly more complicated: You must create subdomains first, before you can install anything in them.
• Subdirectories don’t create as pretty URLs as subdomains, but they’re easier to set up. They can, however, result in conflicts with existing Web pages.
• As soon as you create subdomains or subdirectories to organize your site, you need to consider how people are going to find them. If you’ve created a new primary blog at blog.yourdomain.com, and someone goes to just yourdomain.com, they won’t see that new site. It is possible to set up redirects to avoid this issue. You can also always create links from pages on one subdomain of your site to another.
• If you really just need one site, sometimes installing at the root of your domain is the easiest thing to do, at least as you’re getting started. You can always add more pieces to your territory later with either subdomains or subdirectories.

• Setting Up Subdomains

A subdomain is one way of organizing and separating content on your site. You’re already familiar with the concept of subdomains, even if you don’t know it. Consider OU’s public Web site at http://ou.edu.

As you browse parts of that site, you’ll notice that the domain changes. When you’re looking at your department Web site, say the site for the Chemistry & Biochemistry Department at http://chem.ou.edu, the URL is no longer just ou.edu. Now the root of the url is chem.ou.edu, indicating that you’re on the part of the site that is dedicated to the Chemistry & Biochemistry Department.

If you browse to the technology store pages at http://itstore.ou.edu, you’ll notice that the domain changes again, this time indicating that you’re in the technology store of the OU site.

As you can see the domains serve two purposes: they help to organize the site from a technical perspective, but they also serve as indications to the users that they are in a new/different space. As you work on your site, you’re welcome to create as many subdomains as you like, and in each subdomain you can actually create a distinct, individual Web site.

Additionally, we have resources that demonstrate setting up subdomains and illustrate the difference between subdomains and subdirectories.