I want to point my MX records from my existing server (Hostgator) to Google mail, to receive in Google my new emails. If I don't delete the email addresses that I set up in Webmail, can I still access my old emails stored there, or will they be lost when I change the MX records in the DNS?
If you don't delete or cancel your eMail service with Hostgator then your existing eMails should remain in your Webmail account.
I'm guessing as I don't use Hostgator that you access your webmail via an address like webmail.yourdomain.com or directly via the Hostgator webmail (again a guess). If you use webmail.yourdomain.com then just leave this entry in your DNS and you will be able to continue accessing it as you do now once you change your MX records to Google.
Depending on how much mail you have in your current Hostgator account you could look at using Mailbox Imapsync https://imapsync.lamiral.info/X/ which will allow you to 'move' your eMails from Hostgator to Google Mail.
I've used ImapSync a few times and it works well but I have not tried to send anything to Google.
If you do try it with Google please let me know if it works for you.
Related
I was trying to sign up for a new Gmail address and noticed that Gmail has an option in which you can use your custom email address without the need for having a GSuit paid membership.
Upon filling up the details, Gmail sends an OTP/code to the custom email and upon entering the right code the user can log in using that email.
How is it possible for Gmail to just get access to an email address without even the need for entering the password?
You are creating a google account. A Google account can be associated with any email id.
If you use a custom email id, you can use all the gsuite features like docs etc from that email id, but you cannot access your email via gmail.
To use gmail on a custom domain you have to pay ( change mx servers etc also )
This is done by using MX records.
Mail Exchange (MX) records are DNS records that are necessary for delivering email to your address.
In simple DNS terms, an MX record is used to tell the world which mail servers accept incoming mail for your domain and where emails sent to your domain should be routed to. If your MX records are not pointed to the correct location, you will not receive email.
MX records consist of two parts: the priority and the domain name. For example:
0 mail.EXAMPLE.com
The ‘0’ is the priority.
The lower the number means a higher priority.
The ‘mail.EXAMPLE.com’ is the mail server to which it connects. This is different - depending on what company is hosting your email.
Outgoing email servers connect to the MX servers in order of priority.
If you use more than one MX record and both have the same priority, it picks one at random. (This in effect load balances the connections.)
Your MX records are controlled at the company where your Nameservers are pointed.
Use MX records, provided by the G Suite Setup Wizard, to verify your domain (if you haven’t already verified it) and to set up Gmail as your professional email.
After you've switched to Google's MX records, you can receive your email in your Gmail inbox or through an email client like MS Outlook.
How it works
Keep setup instructions open and sign in to your domain host in another window or tab. Your host manages technical settings for your domain.
You’ll then update the MX record settings to direct your email to your G Suite account. It’s like registering a new address with the post office so that your mail gets delivered.
If you already use email with your domain (your email address ends with #yourdomain.com), you’ll start receiving messages in Gmail instead of with your old email provider.
Read more here https://support.google.com/a/answer/140034?hl=en
I am using Gmail for business and have set the MX records for my domain to point to gmail.
I've been searching but can't find anything in regards to gmail api webhooks for posting specific emails to a specific URL route on my server.
I need to do something similar to this: https://sendgrid.com/blog/receive-inbound-email-meteorjs/ but instead of using sendgrid, I need to do it with gmail api since my MX records are pointing to Gmail.
Is this even possible with gmail api? If so can you point me in the right direction.
Basically any email sent to x#mydomain.com need to be posted to the route mydomain.com/incoming-email. Need to be able to do this with Gmail.
Right now I have dilemma with email part of my projects. I'm using Sendgrid to send and receive emails (via webhook). All email functionality is integrated in my web application and all the emails are stored in the database. I want to know is it possible to do next:
Use Google Apps to receive inbound emails for support#domain.com
Use Google Apps to send outbound emails from support#domain.com
Use SendGrid or Mandrill to send outbound transactional and news
emails from noreply#domain.com and news#domain.com
Current problem is in MX records. Both Google and SendGrid MX records are required to be set in my DNS, but as far as I understand only one of them will actually work.
What is the best solution to make it possible?
Thank you.
One possible solution:
Point your MX records to google for your top level domain, domain.com.
Create support#domain.com email
Next, create a subdomain (i.e: sub.domain.com) and point the mx records to sendgrid.
Then, set up news#domain.com to forward to news#sub.domain.com. This way those emails get sent to your application.
Nothing needs to changed for sending outgoing transactional emails with SendGrid. You can send emails from news#domain.com. I also recommend to NOT USE noreply#domain.com, this hurts your deliverability(https://sendgrid.com/blog/why-you-should-not-use-noreplydomain-com-in-your-emails/)
The easiest solution is probably to use a subdomain for either the inbound emails or the outbound emails, so that you can keep the MX records separate. Receive emails to domain.com, send from e.g. mail.domain.com
I need to be able to send emails from Google Apps (my gmail account) and from my website which is hosted on Bluehost. How do I create an SPF record that will allow me to send emails from those locations but will restrict sending emails from other locations?
Like this:
v=spf1 include:_spf.google.com a a:abc.example.org a:xyz.example.org -all
This says, include Google's SPF record (which will allow all their mail servers to send mail on behalf of your domain), and allow anything in this domain which has an A record, and specifically allow 2 other hosts by verifying their A records. Fail everything else.
For this to work, you will need to know exactly which mail servers outbound mail will come from via Bluehost. I don't know much about them, but that might be your own server, or their outbound servers. If the latter, you might also be able to use another 'include' clause to include their record so you don't have to keep up-to-date with any changes they make.
This site is a useful tool. Google offers others. http://tools.bevhost.com/spf/
I got kinda a weird scenario. I am using google apps for my domain emails so I get chobo2#mydomain.com.
I am using this instead of the my shared hosting provides email server because this gives me alot of flexibility to switch to a new hosting site and not have to transfer all my emails when I switch over. I also like using it over the one my host provides(on average I get emails faster).
Now the only downside to all this is gmail has alot lower email limit(I think like 500 a day). Where as my hosting provider allows something like 1000 an hour.
So I use google apps for my emails that I want to look at and the hosting email servers for automated messages.
What leads me to this problem
<errorMail from="noreply#mydomain.com"
to="myGoogleApssEmail#mydomian.com"
subject="Failed"
async="true"
smtpPort="25"
smtpServer="mail.mydomain.com"
userName="noreply#mydomain.com"
password="password" />
So when an elmah error occurs it should send me an email.This email gets sent through my hosting email servers but it should go to my email address that I have with google(remember they both have the same end domain name - mydomain.com).
I never get the email and I think it is because it probably thinks that they are on the same servers. So instead of sending it to google it probably goes well it must be on the same server as this domain lets try to send it there.
Any ideas on how to fix this? Is it even possible?
It is not possible as MX records are meant to be per domain not per e-mail address.
So if mydomain.com is using Google MX servers all e-mails will be delivered to google in the first place. There you could create forwarding rules to your hosting provider but it does not make sense as it would exceed the limit, too.
What you could do is specifying subdomains - i.e. elmah.mydomain.com plus an MX pointing to your provider.