If, like many of our clients, you like the convenience of receiving all of your <span id="urn:enhancement-f1ebc86d-4525-7b2a-dbf6-468d695e8a0f" class="textannotation disambiguated wl-thing wl-no-link" itemid="http://data.wordlift.io/wl0226/entity/email">emails</span> over at gmail.com, you may well have signed up for <span id="urn:enhancement-0ebb299d-3693-e64d-1541-dccdf45a22ec" class="textannotation disambiguated wl-organization wl-no-link" itemid="http://data.wordlift.io/wl0226/entity/google_2">Google</span> Apps, and wish to use Gmail to get your "firstname.lastname@example.org" emails.
In order to do so, Google tells you that you must update your MX servers at your host, our guide below will show you how to do so on the most popular of control panels - cPanel.
Login to cPanel at https://yourdomainname.com:2082
Now, under the 'Mail' header, click on 'MX Entry':
You will now see a list of different options available to you. For most people, it's probably set to 'Local Mail Exchanger' this means your web host has been handling your emails. The option we want to change it to is 'Remote Mail Exchanger' so go ahead and change it, and click on 'Change'
Now in the box below, you need to create a record for each of the following:ASPMX.L.GOOGLE.COM with a priority of 1
ALT1.ASPMX.L.GOOGLE.COM with a priority of 5
ALT2.ASPMX.L.GOOGLE.COM with a priority of 5
ASPMX2.GOOGLEMAIL.COM with a priority of 10
ASPMX3.GOOGLEMAIL.COM with a priority of 10Enter the priority and domain in the boxes, like below:
Do this for each of the above records, and once you're done, you may need to delete the record for your web host if it is still there:
Once you've done this, all of your emails will now be sent to, and processed by Google's servers, and accessed through Gmail.
Truth be told, it’s difficult for a web application that doesn’t have some kind of identification, even if you don’t see it as a security measure in and of itself. The Internet is a kind of lawless land, and even on free services like Google’s, authentication ensures that abuses will...
Although data persistence is almost always a fundamental element of applications, Node.js has no native integration with databases. Everything is delegated to third-party libraries to be included manually, in addition to the standard APIs. Although MongoDB and other non-relational databases are the most common choice with Node because if you...