Email Help
If you are having problems related to receiving or sending email messages at your domain, this section is for you. Check through the headers below for help on the exact situation you are experiencing. Also, please be sure that your domain is registered and resolving on our nameservers before you start using the email services provided with your account.
Helpful Information
Remember to always use "mail.example.com" as the incoming (pop3) and outgoing (smtp) server in your local email client, such as Mozilla Thunderbird.
In the mail control center, the forwarding function provides forwarding to an external address. Thus, if you want you@example.net to head to a pop3 account of you@example.com, use a forward to make this happen.
You may use the forwarding function to alias two email addresses. Thus, if you want mail to you@example.com to also arrive at them@example.com, use a forward to make this happen.
If you forget the exact login of one of your pop3 accounts, simply head over to the "pop account" menu within your control panel to find out exactly what the logins are.
Your "default address" is the catch-all mailbox. It receives messages heading to all addresses which aren't setup as unique email accounts within your domain. Keep in mind that the default address account does NOT have the @example.com suffix, like other pop accounts. The login for your default address is the same as the main FTP and control panel login for your account.
If it seems that you cannot lock a pop3 account to retrieve messages for any reason, the quickest way to solve this for yourself is to delete and recreate the account with your control panel. This saves time as it bypasses asking our support staff for assistance. Changes you make to your email accounts with your control panel are done in real time.
The mailing list feature is very simple, please keep that in mind. If you require a more powerful listserv program, you should probably look elsewhere. We cannot utilize a robust listserv on our webhosting machines without causing the server's overall performance to suffer.
Remember that the mail functionality for your domain won't be available on our servers until your entire domain is registered to our nameservers. If you are having any problems with your email, and this section didn't help you, please contact support.
Can't Send Mail
Our SMTP servers are configured as secure relays. This means that you cannot simply reference "mail.yourdomain.com" as an Outgoing mailserver unless you successfully log in via one of your email accounts at "mail.example.com' before you try to send. This is a mandatory setting to prevent spammers from using our mailservers as havens for unsolicited email. If you are getting a "relaying prohibited" or "disconnected by administrator" error, it means that you haven't logged into the email server at your domain before you tried to send through the email server at your domain. To log in, you need to check for mail first and have pop authentication set.
In addition to this, you might not be able to send regardless of if you check mail successfully. Some ISPs have it set so that their users cannot use an outbound SMTP server to relay messages. If you are still experiencing problems sending through your domain, and are certain that you have logged in via pop3 to an account at your domain, you might want to contact your local ISP to see if they do allow their users to use outbound smtp servers.
Finally, we'd like to clear up a common misconception of many users: the smtp relay you use to send out your messages has absolutely no bearing on the address your recipient sees as the sender. If you do end up having to use your local ISPs SMTP server, it will not prevent you from sending messages from address @yourdomain with Positive Fusion. For example, let's say that you have the domain "example.net" hosted at Positive Fusion. You can configure your email client to send from the address "foo@example.com" even if your outgoing (smtp) mail server is set as "mail27.example.net" - your recipient will still see the message as being sent from "foo@example.com" regardless of the smtp server you use to send it. Be sure that your incoming (pop3) server is set to "mail.example.com", of course.
Your Default Email Account
Every account starts out with a default "catch-all" account for its domain. This email box will grab all mail heading to ANYNAME@example.com. The login for this box is simply the same main account login you received after signing up. Thus, if your default account is "examplec@example.com" (login of "examplec" - first 8 letters of your domain), there is no need to configure an alias to your default account, because all names under your domain already are filtered into this account.
We recommend disabling the default account through the control panel to prevent "dictionary" spam. You may do so by changing the default address to :fail:.
Can't lock account
A common cause of this is that the e-mail account is being accessed already or it is still open from another mail checking session. Solution: Retry in about 30 minutes. If it still does not work it is possible that you are using the wrong user / password combination. If you suspect this send a message to support@positivefusion.com and let them know what you are using to attempt to log into the account.
Any Username And Password Error
The main cause for this is trying to access the e-mail account with the wrong user / password. If this is not your primary e-mail account remember to apply your domain name suffix. For example if your account is homepage@example.net your email log in name will also be "homepage@example.net." If all else fails, simply remove, and then recreate the account with your mail control panel.
If none of this helps, then most likely the pop3 box in question has a received a corrupted message. Contact support and tell them to clear that box out. Usually this results in most or all of that particular mailbox's contents being erased.
Problems resolving your mailhost
If you find that you can't get "mail.example.com" to resolve as a valid SMTP or POP3 server, please be sure that your domain is registered to our nameservers. Also, try clearing out your cache and cookies and then restarting your computer. In some cases your registration was not completed by the registrar.
