Pacific Internet is proud to offer domain mail!
- Control of your own mail — manage email accounts, passwords, and aliases
- Improved spam filtering — included free of charge
- Mail-only services — you don't need a website hosted with us (though we do that too!)
- Excellent support — having a bad day? Need someone to talk to? Give us a call.
When you're ready to begin, contact us.
A Typical Setup
Say you're a business and you own your own domain - acme.com, for example. You have employees Alice and Bob. Each employee gets their own company email account, so you create the addresses firstname.lastname@example.org and email@example.com. Alice works in manufacturing and Bob works in sales, so you create two aliases for the general positions: firstname.lastname@example.org and email@example.com. Aliases aren't mailboxes themselves, they forward to another address. You set up your email so that the aliases for the positions forward to the appropriate employee. In our example, your mail scheme looks like:
- firstname.lastname@example.org –> email@example.com
- firstname.lastname@example.org –> email@example.com
The benefit to this setup is that as employees come and go in your business, it is very easy to manage your email. For instance, if Bob leaves and Cindy is hired in his place, you create a new email account for Cindy - firstname.lastname@example.org, remove the email account for Bob, and change the alias for the sales department to forward to Cindy, so that:
- email@example.com –> firstname.lastname@example.org
There is no need to worry about Bob having access to mail for email@example.com because he only had the password for his own account (which an administrator also has control of) and firstname.lastname@example.org now forwards to Cindy's email address.
If you own your own domain but don't need to manage an entire company, you can still use the same model described above; simply create an email account for yourself and set up aliases as you need them. For instance, if you owned the domain mysite.org you could create an email account email@example.com. Then you could use aliases like firstname.lastname@example.org or email@example.com to forward to your email account like so:
- firstname.lastname@example.org –> email@example.com
- firstname.lastname@example.org –> email@example.com
One of the main benefits to this setup is you only have to check one mailbox.
More on Aliases
Aliases can forward to other domains. For example, if you have a webmaster, Doug, who takes care of your site, you could also create an alias that looks like:
- firstname.lastname@example.org –> email@example.com
Aliases can be one-to-many. This means your entire sales team can get mail for firstname.lastname@example.org. While Bob is mentoring Cindy for the sales position they can both receive the mail:
- email@example.com –> firstname.lastname@example.org,email@example.com
Aliases can also be many-to-one. This means that one address can receive mail from multiple aliases. For example, Eve, the manager, might need to use several aliases:
- firstname.lastname@example.org –> email@example.com
- firstname.lastname@example.org –> email@example.com,firstname.lastname@example.org,email@example.com
- firstname.lastname@example.org –> email@example.com
There is one very important thing to notice about both of the organizational structures above—neither of them have mailboxes for a position; they only create mailboxes for people. People check mailboxes. It is not wrong to create an address for a position or department, like info, sales, manager, etc., but those should be aliases that forward to the appropriate person (or people).
There are a number of benefits to organizing your email like this.
Flexibility is one.
As employees come and go, you simply add and remove email accounts for them.
In the meantime, the aliases can always point to the correct destination.
Security is another.
Each person is only able to access their own email, and email accounts are not shared between people.
The mail administrator determines who gets what mail by managing the aliases.
Also, passwords do not need to be distributed.
Each person only needs to know their own, and the mail administrator can change them as necessary.
Ease of management is a third benefit.
There are numerous problems inherent in allowing or requiring multiple people to use the same email account.
One example would be the scenario where somebody accidentally deletes all of their mail.
By all of
their mail, we mean everybody's mail.
Improperly configured mail clients can also wreak havoc in a shared setting—something most users aren't even aware of.