{"id":65976,"date":"2022-08-19T03:47:06","date_gmt":"2022-08-19T09:47:06","guid":{"rendered":"https:\/\/www.scalahosting.com\/blog\/?p=65976"},"modified":"2023-03-16T02:29:16","modified_gmt":"2023-03-16T08:29:16","slug":"email-hosting-with-unlimited-aliases","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/blog\/email-hosting-with-unlimited-aliases\/","title":{"rendered":"Email Hosting With Unlimited Aliases"},"content":{"rendered":"\n

Email communication<\/strong> has become a staple of our everyday online lives. It’s suitable for formal and non-formal settings and can be used for anything from arranging a meeting to organizing a marketing campaign.<\/strong><\/p>\n\n\n\n

However, email’s popularity has brought about an unpleasant \u2013 though not unexpected \u2013 side effect. The flow of information passing through our inboxes is enormous, and keeping track of the messages’ source and destination can be challenging.<\/p>\n\n\n\n

Over the years, we’ve developed quite a few tools to try and solve this problem. Email aliases are among them, and today, we’ll show you how they work.<\/p>\n\n\n\n

What is an Email Alias?<\/strong><\/h2>\n\n\n\n

An email alias is often described as a <\/strong>forwarding email address<\/strong><\/a>. Unfortunately, this may create some confusion.<\/p>\n\n\n\n

You have probably seen the Forward<\/strong> option in your email client. Many of you have used it, as well. With it, messages sent to your email address can also arrive at another destination.<\/p>\n\n\n\n

For example, bob@example.com sends alice@example2.com<\/em> an email. Alice’s email client then sends the message to john@example2.com<\/em>. We have email forwarding, but this doesn’t mean that alice@example2.com<\/em> is an alias of john@example2.com<\/em>.<\/p>\n\n\n\n

These are two separate email accounts with individual users managing the mailboxes. The forwarded message arrives at John’s address, but it’s also saved in Alice’s inbox.<\/p>\n\n\n\n

An email alias is different. It doesn’t have an inbox, and you don’t need to create an account for it. Instead, you tell the mail server that messages sent to address1@example.com<\/em> should be forwarded to address2@example.com<\/em>.<\/p>\n\n\n\n

This allows you to have a single inbox with multiple addresses<\/strong>.<\/p>\n\n\n\n

When Would You Need an Email Alias?<\/strong><\/h2>\n\n\n\n

Having more than one address for a single account may seem a bit pointless, but if you think about it, you’ll see that it makes a lot of sense.<\/p>\n\n\n\n

Imagine, for example, that your name is John Stephenson, and your primary email address is john.stephenson@domain.com<\/em>. Less observant users can easily make the mistake of sending their messages to john.ste<\/em>v<\/em><\/strong>enson@domain.com<\/em>. Normally, this would result in bounced emails and missed business opportunities. However, if you set the commonly mistaken address as an alias<\/strong>, you will receive every single email sent to it.<\/p>\n\n\n\n

While you’re at it, you may want to consider setting up other aliases like john@domain.com<\/em> or john.s@domain.com<\/em>. People prefer shorter, easier-to-remember email addresses, so this will definitely help ease communication.<\/p>\n\n\n\n

Speaking of easing communication<\/strong>, you can set up an alias with your job title (e.g., ceo@company.com, marketing.manager@company.com<\/em>, etc.) or create addresses for departments in your organization (sales@company.com, marketing@company.com<\/em>, etc.). This way, potential customers<\/strong> won’t waste time looking for contact information, and all messages will arrive in the correct inbox.<\/p>\n\n\n\n

International businesses with multiple regional domains<\/strong> can also benefit from email aliases. For example, you can have jane@domain.co.uk as an alias for jane@domain.com<\/em>.<\/p>\n\n\n\n

There are more trivial scenarios, as well. If you want to sign up for a service without revealing your actual email address<\/strong>, you can set up an alias and use it during registration. The online service can still send you things like a welcome email and a password reset link, but should you decide, you can stop any incoming communication from the provider by dropping the alias<\/strong>.<\/p>\n\n\n\n

It’s a great way of filtering the messages that arrive in your inbox, and, more importantly, it gives you more control over who has your real email address.<\/p>\n\n\n\n

How Do Email Aliases Work?<\/strong><\/h2>\n\n\n\n

Email aliases use server-side forwarding. You usually get a graphical interface for creating aliases, which saves your forwarding settings in a file. In the case of Unix-based systems, the file in question is etc\/aliases<\/em><\/strong>.<\/p>\n\n\n\n

To set up an alias, you need to have a <\/strong>registered domain<\/strong><\/a> correctly pointed to a mail server. However, you don’t need to forward the alias to an address on the same domain. You can, for example, forward emails sent to jane@domain.com to jane@gmail.com<\/em>.<\/p>\n\n\n\n

The sender can’t tell whether the message is about to be forwarded by an alias. In fact, even the recipient isn’t necessarily sure<\/strong> which address was used exactly.<\/p>\n\n\n\n

Forwarded emails retain what’s known as their SMTP envelope<\/strong>. This means that information on who sent them and what email address they used is attached to the message. However, this information doesn’t always coincide with what people see in their email clients, meaning an alias isn’t 100% reliable<\/strong> when it comes to controlling the flow of messages in your inbox.<\/p>\n\n\n\n

There’s one more thing to bear in mind. The recipient server sees the IP of the forwarding system only<\/strong>. For example, if joe@domain.com is an alias of joe@gmail.com<\/em>, Gmail will only see the IP of the server hosting domain.com<\/strong>.<\/p>\n\n\n\n

Hence, if someone sends a large volume of spam to joe@domain.com<\/strong>, it will automatically be forwarded to Gmail, and Google<\/strong> will think it’s coming from domain.com’s server. The IP could then be blocked<\/strong>, leading to lost legitimate communication.<\/p>\n\n\n\n

Now that we know how aliases work, let’s find out how to set them up.<\/p>\n\n\n\n

Creating an Email Alias On an SPanel Server<\/strong><\/h2>\n\n\n\n

Setting up an email alias on an SPanel<\/strong> server takes just a couple of mouse clicks and less than a minute.<\/p>\n\n\n\n

The Forwarders <\/strong>tool is located near the top of the User Interface’s homepage.<\/p>\n\n\n\n

\"Email<\/a><\/figure>\n\n\n\n

Open it, and at the bottom of the page, you’ll see a list of the forwarders you’ve already set up. Above it is the form you’ll use to create a new one.<\/p>\n\n\n\n

To create an alias, pick an address by entering the username and choosing a domain <\/strong>from the drop-down menu on the right. All the domains and subdomains added to your account are in there.<\/p>\n\n\n\n

\"Email<\/a><\/figure>\n\n\n\n

Then, enter the final destination for the messages into the Forward to Email Address<\/strong> field and click Add Forwarder<\/strong>.<\/p>\n\n\n\n

cPanel’s interface may be slightly different, but the steps are pretty much identical<\/strong>.<\/p>\n\n\n\n

Limitations With Using Aliases<\/strong><\/h2>\n\n\n\n

Forwarders take up so little server resources, most hosting companies<\/strong><\/a> impose no limits on the number of aliases you can set up. ScalaHosting is no exception. You can create as many aliases as you want and set up an unlimited number of email inboxes <\/strong>with all but our cheapest email hosting plans<\/strong>.<\/p>\n\n\n\n

One thing you need to remember is that the more forwarders you set up<\/strong>, the more difficult it will be to figure out where each email is coming from and where it’s supposed to go.<\/p>\n","protected":false},"excerpt":{"rendered":"

Email communication has become a staple of our everyday online lives. It’s suitable for formal and non-formal settings and can …<\/p>\n","protected":false},"author":113,"featured_media":65980,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_robots_primary_cat":"none","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","_seopress_analysis_target_kw":"","footnotes":""},"categories":[123],"tags":[],"class_list":["post-65976","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-email-hosting"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts\/65976","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/users\/113"}],"replies":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/comments?post=65976"}],"version-history":[{"count":5,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts\/65976\/revisions"}],"predecessor-version":[{"id":67233,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts\/65976\/revisions\/67233"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/media\/65980"}],"wp:attachment":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/media?parent=65976"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/categories?post=65976"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/tags?post=65976"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}