hosting

If the reseller is selling Web Hosting

Using the Email Hosting service

Once you have purchased the Email Hosting Service from , you need to take the following steps to start using it.

  • To change the Name Servers of your domain name

    1. Login to your Control Panel. See details

    2. Search for the domain name for which you have purchased the Service and proceed to the Order Details view. See details

  • Click the Name Server Details link.

  • Here, you would find the list of Name Servers you need to set for your domain name. Alternatively, if you wish to retain the Name Servers of your domain name instead of using our Name Servers, you would need to add all the Resource Records listed on this page on your Name Servers.
  • Attention

    If you do not use 's Name Servers or do not modify your domain name's MX Records to point to our servers, then you would not be able to receive email on your domain name. If someone tries to send an email to an email account on your domain name immediately after you have either modified your domain name's Name Servers or pointed your domain name's MX Records to ours, that person would encounter the following error message:

    Error: Sorry. Although I'm listed as a best-preference MX or A for that host,it isn't in my control/locals file, so I don't treat it as local. (#5.4.6)

    Also, no emails are delivered to that email account.

    This issue will get resolved automatically half an hour after either your domain name's Name Servers have been modified or your domain name's MX Records has been pointed to ours.

    Additional Information

    Note

    If you wish to deploy third party anti-spam service for your email accounts, you are required to specify the email servers as:-

    • orderid.mx1.email-hosting-name.com

    • orderid.mx2.email-hosting-name.com

    where, orderid = Order Id of your Email Hosting Order (displayed under the Order Details view of your Email Hosting Order, within the Order Information section)

    See details

    OR

    67.15.238.68 209.62.87.245

    These values need to be specified through the anti-spam service management interface.

  • Create Email Accounts

    Once the Service is activated, you should create email accounts to send and receive email. Apart from creating email accounts, you can also setup email forwards, aliases, mailing lists etc. from your Email Administration interface. See details

  • Send and Receive Email using the accounts you created

    offers you the following options while sending and receiving email using the accounts you create:

    • Configure a desktop email client to download and send email. See details

    • Login to the Web-based interface to access your email online. See details

    You can now send/receive email using your newly created email account either using a desktop email client or through the Webmail interface.

Collaboration Data Objects (CDO)

Originally known as Active Messaging, the Collaboration Data Objects (CDO) library allows users to send mails through ASP Scripts.

Collaboration Data Objects (CDO) is Microsoft's technology for building messaging or collaboration applications or adding these capabilities to existing applications. Part of the Microsoft Exchange Server
product, CDO has evolved from what Microsoft formerly called Object Linking and Embedding Messaging and, more recently, Active Messaging.

You can use the sample script provided by and tweak it a bit to your requirements, to accept feedback from your website visitors and get
the results emailed to you.

You would need to change the Email Address in the field myMail.From to any Email Address on the domain name on which you are incorporating the script.

Example:

If your Domain Name is abc.com, then you would define the From Email Address as some-name@abc.com. This Email Address need not be existing on the Mail Server of abc.com, however, the
domain name in the myMail.From field has to be yours. You may use an Email Address such as Do_Not_reply@abc.com.

The Email Address in the myMail.To field needs to be changed to your Email Address, where you wish to receive Emails submitted through the form.

Sample Script



Note

The body of the mail should not have bare linefeeds (\n). If a bare linefeed is detected, the SMTP service of Microsoft IIS6 (the Web Server running on
's Windows servers) will stop delivering any mail and the mails will get struck in the SMTP queue. This is because Microsoft IIS6 strictly
follows Internet e-mail standards; and these standards forbid the presence of bare linefeed characters in e-mail messages.

Additional Information

Bare LineFeeds in SMTP

Example:

myMail.TextBody="Thank you for contacting us. We shall get back to you shortly.\n

Kind regards\n

abc.com"

In the above case, bare linefeeds (\n) are being used. Instead of \n, you need to use \r\n (carriage-return, line-feed). Hence, the correct usage would be:


myMail.TextBody="Thank you for contacting us. We shall get back to you shortly.\r\n

Kind regards\r\n

abc.com"

Managing DNS, Email, Hosting, Live Chat, Website Builder Services through your SOAP API Integration

Note

The SOAP API has been deprecated. You are advised to use the HTTP API instead.

The following Services reside on separate servers from the ones you connect to, via the SOAP API Kits, due to which your Customers need to login to their (individual) Control Panels, for managing
them:

  • DNS

  • Email (Free Email Account [POP/IMAP] and Email Forwarding)

  • Web Hosting

  • Email Hosting

  • Live Chat

  • Website Builder

now provides you with another method of directly allowing access to your Customer, to manage their DNS, Email, Web Hosting,
Email Hosting, Live Chat and Website Builder Services from your interfaces itself.

To accomplish this, you need to use either of these 2 methods and pass the following parameters to the mentioned URL, via an HTTP POST method:

Method 1 (recommended)

URL: https://<Your_Control Panel_Branded_URL>/servlet/ManageServiceServletForAPI

  • orderid: The Web Services (Email Hosting, Web Hosting, Website Builder), Live Chat Service Order Id that your Customer wants to
    manage. In case of DNS/Email Service, the Order ID of the Product associated with the DNS/Email Service needs to be passed. Based on the orderid,
    the productCategory will be determined.

    Note

    For DNS and Email (Free Email Account [POP/IMAP] and Email Forwarding) that do not have any other Product associated with them, you can
    continue to pass the existing orderid to reach the DNS Management Console and Email Forwarding Management interface respectively.

  • loginid: You need to generate a Login ID, that you need to pass as the value of this parameter for allowing the Customer to
    manage his Order. This can be accomplished by calling the API method generateLoginID in the Customer class. In order to call generateLoginID, you will
    have to pass ipAddress as a parameter. This Login ID generated will be valid for a very short period of time and you should use it immediately upon generating it.

    Note

    While generating the Login ID, you need to use the Username and Password of the Customer, to whom the Order belongs.

  • service-name: This parameter needs to be passed to manage the specified service name. The value of this
    parameter needs to be either:

    • dns: For managing DNS Service.

    • mailfwd: For managing Email Forwarding Service.

    • free_email: For managing Free Email Account Service.

    • mailhosting: For managing Email Hosting Plans.

    • webhosting: For managing Web Hosting Plans.

    • websitebuilder: For managing Website Builder Plans.

This method is the most secure method of allowing your Customers to manage their DNS, Email, Web Hosting, Email Hosting, Live Chat and Website Builder Services, since it does not
expose the Customer's Username and Password in your interface.

If you choose to use this method, then you would need to create an intermediate interface to which you can provide the required parameters, and which in-turn generates a valid URL and redirects your
Customer.

You need to provide orderid and any authentication details (optional) to this interface. This interface would then call the API method
generateLoginID of the Customer class and build a URL with orderid, loginid and service-name as parameters, and then
redirect the Customer to this URL.

Example:

Let us call this interface a servlet named ManageOrderBoxControlPanel (assuming that you are using our JAVA API Kit).

  1. This interface would accept the Web Services (Email Hosting, Web Hosting, Website Builder)/Live Chat Service Order Id or the Order Id of the Product associated with DNS or Email Service as a
    parameter. So, in order to manage a Service, you will call this interface with https://<Your-Server-URL>/ManageOrderBoxControlPanel?orderid=<orderid>.

  2. Now this servlet would need to call the API method generateLoginID of the Customer class like: String loginid = API call to
    generateLoginID(username,password,role,langpref,resellerid,ipAddress);
    where,

    • username: the Username of the Customer, to whom the Order belongs.

    • password: the Password of the Customer, to whom the Order belongs.

    • resellerid: the Reseller Id associated with your Reseller Account. You can find it by clicking the icon at the top right corner within your Reseller Control Panel.

    • role: customer

  3. The final URL to which you would then redirect your Customer to, would look like:

    • For management of Live Chat Services:
      https://<Your_Branded_URL>/servlet/ManageServiceServletForAPI?loginid=<loginid>&orderid=<orderid>

    • For management of DNS Service/Email Forwarding Service/Email Hosting/Web Hosting/Website Builder/Free Email Account Service:
      https://<Your_Branded_URL>/servlet/ManageServiceServletForAPI?loginid=<loginid>orderid=<orderid>&service-name=<servicename>

Method 2

URL: https://<Your_Control Panel_Branded_URL>/servlet/ManageServiceServletForAPI

  • orderid: The Web Services (Email Hosting, Web Hosting, Website Builder)/Email Hosting/Live Chat Service Order Id that your
    Customer wants to manage. In case of DNS/Email Service, the Order ID of the Product associated with the DNS/Email Service needs to be passed. Based on the orderid,
    the productCategory will be determined.

    Note

    For DNS and Email Forwarding Orders that do not have any other Product associated with them, you can continue to pass the existing orderid to reach the DNS Management
    Console and Email Forwarding Management interface respectively.

  • username: The Username of the Customer, to whom the Order belongs.

  • password: The Password of the Customer, to whom the Order belongs.

  • resellerid: The Reseller Id associated with your Reseller Account. You can find it by clicking the icon at the top right corner within your Reseller Control Panel.

  • service-name: This parameter needs to be passed to manage the specified
    service name.

The disadvantage of using this method is that it is a bit less secure as the Customer Username and Password along with your Reseller Id can be viewed in the source of the page, from where you
post to the ManageServiceServletForAPI servlet.

Note

Do not send the above mentioned as parameters as part of a URL, or else this information will be displayed in your Customer's Browser Address Bar.

Perl-based Form Mail (Feedback) Script

Using a Perl script, you may accept feedback from your website visitors and get the results emailed to you. You can use the sample script provided by and tweak it a bit to suit your requirements.

Sample Script


#!/usr/bin/perl
print "Content-type: text/html\n\n";
#
$title='Perl Mail demo';
$to='TO_Email';
$from= 'some-name@yourdomain.com';
$subject='perl mail';

open(MAIL, "|/usr/sbin/sendmail -t");

## Mail Header
print MAIL "To: $to\n";
print MAIL "From: $from\n";
print MAIL "Subject: $subject\n\n";
## Mail Body
print MAIL "This is a test message
mail body text here\n";

close(MAIL);

print "

$title\n\n\n";

print "

$title

A message has been sent from $from to $to

";
#

Note
  • The .pl file containing the script needs to be uploaded to your web server in ASCII mode only.

  • The .pl file needs to have execute permissions for the normal web user. For example, the .pl file can have permissions 755 or 765.

Sample HTML Feedback Form

The following code needs to be added in the form which connects to the above script:

Below is the explanation about the variables in the code:

  • recipient: This would be the email address, where the email containing the data submitted through the form needs to be delivered.

  • email: You would need to change the email address in the email field to any email address on the domain name, on which you are incorporating this script. For example, if you are deploying this script on yourdomain.com, then you would define the From email address as some-name@yourdomain.com. This email address need not be existing on the Mail Server of yourdomain.com; however, the domain name in the email field has to be yours. This implies that you may use an email address such as Do_Not_reply@yourdomain.com. This email address will appear as the From email address in the email sent by the script.

  • realname: The value here indicates the name mentioned in the From section of the email, that will be sent upon submission of this form. This can be modified as per your requirement.

  • subject:The value in this field can be changed to indicate an appropriate subject for the mail to be sent. For example, you may set this as YourDomain.com Feedback Form or any other subject that would allow you to uniquely identify from which form on your website this data has been received.

  • redirect: Once the visitor provides feedback, he/she can then be redirected to another page on your website. In order to achieve this, you need to mention the path to the HTML file in the redirect field. Alternately, you can display a message to the visitor thanking him/her for the feedback. Such messages can be displayed in a new page like thanks.htm. Such a page can also contain other information as deemed necessary.

Note

In an attempt to keep a check on abuse from 's Hosting Servers, the following conditions have been set for mail scripts on 's Linux Hosting Servers:

  • The domain name in either the To or the From email address used in the script should be your domain name hosted with .

    Example: yourdomain.com is hosted with and yourotherdomain1.com and yourotherdomain2.com are hosted with some other hosting provider.

  • For mail scripts with the From email address as <user>@<server_hostname>, the To email address compulsorily should be an email address on your domain name hosted with
    .

    Example: yourdomain.com is hosted with with parent user yourdo & server name cp-00.webhostbox.net and yourotherdomain1.com is hosted with some other hosting provider.

    With the From email address as yourdo@cp-00.webhostbox.net:

PHP-based Form Mail (Feedback) Script

Using a PHP script, you may accept feedback from your website visitors and get the results emailed to you. You can use the sample script provided
by and tweak it a bit to suit your requirements.

You would need to change the email address in the field $from to any email address on the domain name on which you are incorporating this script.

Example:

If your domain name is yourdomain.com, then you would define the From email address as some-name@yourdomain.com.

This email address need not be existing on the mail server of yourdomain.com; however, the domain name in the $from field has to be yours.

You may use an email address such as Do_Not_reply@yourdomain.com.

The value in the $mailto field needs to be changed to the email address, where the email containing the data submitted through the form needs to be delivered.

Note

In an attempt to keep a check on abuse from 's Hosting Servers, the following conditions have been set for mail scripts on 's Linux Hosting Servers:

  • The domain name in either the To or the From email address used in the script should be your domain name hosted with .

    Example: yourdomain.com is hosted with and yourotherdomain1.com and yourotherdomain2.com are hosted with some other hosting provider.

  • For mail scripts with the From email address as <user>@<server_hostname>, the To email address compulsorily should be an email address on your domain name hosted with
    .

    Example: yourdomain.com is hosted with with parent user yourdo & server name cp-00.webhostbox.net and yourotherdomain1.com is hosted with some other hosting provider.

    With the From email address as yourdo@cp-00.webhostbox.net:

Once the visitor provides feedback, you can display a message to the visitor thanking them for their feedback.

Sample Script


$mailto="some-name@yourdomain.com";
$pcount=0;
$gcount=0;
$subject = "Mail from Enquiry Form";

$from="some-name@abc.com";
while (list($key,$val)=each($_POST))
{
$pstr = $pstr."$key : $val \n ";
++$pcount;

}
while (list($key,$val)=each($_GET))
{
$gstr = $gstr."$key : $val \n ";
++$gcount;

}
if ($pcount > $gcount)
{
$message_body=$pstr;
mail($mailto,$subject,$message_body,"From:".$from);
echo "Mail has been sent";
}
else
{
$message_body=$gstr;
mail($mailto,$subject,$message_body,"From:".$from);
echo "Mail has been sent";
}
?>