The SiteHost Control Panel will not let you create accounts with these aliases as they are reserved by the system.
Why are they reserved? In the email world these aliases have special significance and are required to meet the mail RFCs (standards). The RFCs require that email domains have these two aliases defined, postmaster@[xxx.xxx.xxx.xxx] and abuse@[xxx.xxx.xxx.xxx]. Anyone should be able to send email to these addresses and expect that it will be delivered. For example from RFC 2821:
Any system that includes an SMTP server supporting mail relaying or delivery MUST support the reserved mailbox "postmaster" as a case-insensitive local name.
One of the most common uses for these aliases is that they are typically required as part of the process of removing your email domain from a blacklist which has flagged your address as sending spam.
There are basically two ways of accessing your email:
Yes you can. Please refer to our article on Catch-All Addresses.
This works the same way as the NZ Post mail redirection. If you tell a mailbox to forward all email to another address, no copy is kept in the current mailbox. It simply sends the email on to the new address.
Receiving email and sending email are two different processes:
If you are a SiteHost mail customer, you can use our Authenticated SMTP server.
If you're a SiteHost VPS customer and you're in our IP space, you can relay mail from your VPS directly through
If you're a SiteHost Mail customer, you have two options for your SMTP. Your ISP's SMTP Server, and SiteHost's Authenticated SMTP server.
We have listed some of the more popular New Zealand ISPs and their SMTP Servers below. This is believed to be accurate at the time of publishing. If unsure please contact your ISP.
If your ISP is not listed above please contact them directly.
POP and IMAP are two different protocols used to retreive emails from a remote server. Most email software today supports both protocols - so which one you use depends on which one is most suited to your usage requirements.
POP stands for "Post Office Protocol" and can be regarded as an older protocal optimised for users downloading email messages from the server onto a local device. Emails are typically removed from the server when downloaded, thus requiring the user to access and read their emails from the same device.
IMAP stands for "Internet Message Access Protocol". IMAP offers two-way communication between the mail server and your device-bound email client. So actions you perform in your desktop email software, such as creating folders and moving emails, will automatically happen on the server as well. Or if you delete an email on the server the email will be deleted from your desktop email client as well.
IMAP also provides a better method to access your mail from multiple devices. If you check your email at work, on your mobile phone, and again at home, IMAP ensures that new mail is accessible from any device at any given time. You can also access your IMAP email from anywhere with just a browser using SiteHost Webmail.
Finally, IMAP offers a more stable experience overall. Whereas POP is prone to losing messages or downloading the same messages multiple times, IMAP avoids this through two-way syncing capabilities between your mail clients and the server.
We recommend that you use IMAP if:
A Sender Policy Framework (SPF) record is a DNS TXT record that identifies which email servers are permitted to send emails on behalf of your domain. It can help fend off spammers who forge the sent from or _reply to _address to send spam.
An example of an SPF record:
"v=spf1 a mx ~all"
If your website is hosted with SiteHost and you are sending email from the website, whether it be from a contact us form or from an order page, we would recommend adding our SiteHost SPF “include:” record ( include:_spf.sitehost.co.nz ) to your existing SPF record. This include will cover our current and future mail systems.
An example of an SPF record that contains SiteHost’s SPF include:
"v=spf1 a mx include:_spf.sitehost.co.nz ~all"
If your DNS is also hosted with SiteHost you can learn how to add or update your SPF record from our DNS Records knowledge base article.