Email Hosting Orders activated on or after 2 July, 2009, will have a separate Email management and Webmail interface. 1

• Sending Emails:

  • While configuring the email account, the appropriate option for Outgoing (SMTP) Server authentication needs to be enabled in the email client. Please refer to individual email client's configuration process mentioned in the articles below >>

  • The domain name in the email account configured (sender email address) needs to be hosted on OxyHosting's Email Server.

  If either of these two conditions are not fulfilled, you will encounter the following error message while trying to send messages:

  Sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)

• Receiving Emails:

  • Before you start using OxyHosting's Email Hosting service, you need to either:

    • modify the Name Servers of your domain name to OxyHosting's Name Servers, OR

    • create the necessary DNS Records on the existing Name Servers of the domain name. 2

    If the MX Records created on the existing Name Servers do not point to the IP addresses of OxyHosting's Email Server, anyone sending emails to email addresses using OxyHosting's Email Hosting service will encounter the following bounce back message:

    Sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)

  • OxyHosting's Email Hosting Servers have basic anti-spam protection enabled. External Email Servers sending emails to OxyHosting's Email Hosting Servers are required to have proper, fully compliant Reverse DNS Records (also referred to as FCrDNS on the Internet). This helps OxyHosting's Email Hosting Servers detect trojaned computers trying to send us spam and/or viruses. Absence of a reverse DNS entry will result in the emails being rejected with the following message:

    Client host rejected: cannot find your reverse hostname (#5.7.1)

    If emails sent to you by someone are being rejected due to a lack of a Reverse DNS Record, then the sender needs to contact their Email Service Provider. The Email Service Provider needs to add an appropriate PTR (Pointer) Record in their DNS Server. Also, a PTR Record must have a corresponding valid A Record.

    Example:

    If the sender Email Server is mail.senderdomainname.com and it is mapped to the IP Address 111.222.333.444, then the following DNS Records must exist:

    mail.senderdomainname.com. IN A 111.222.333.444
    111.222.333.444.in-addr.arpa. IN PTR mail.senderdomainname.com.

    One matching pair of PTR and A Records is sufficient. Hence, even if there are multiple A Records pointing to the same IP address, having any one of them in the PTR Record is sufficient.

Presence of a valid PTR Record does not exempt the sending Email Server from other anti-spam checks.