I'm concerned about losing emails during changeing my domain nem, Lets say I have domain1.com and there's an email associated with this domain info#domain1.com .. If I want to change my domain and purchase a new one domain2.com,
Is it possible to keep old emails the received on info#domain1.com and change it to info#domain2.com ?
I'm all set to change the Nameservers on the domain, but I'm not sure that I'm safe with the emails sent to these accounts during the transfer process.
Assuming that both info#domain1.com and info#domain2.com are separate IMAP accounts then you can use a service like https://www.yippiemove.com/ to migrate emails/directories between the two. Once everything has migrated to domain2.com then you can close down domain1.com
Related
Recently I have created a website for a client using Laravel/PHP. and then hosted on a cloud hosting provider vultr.com, the client didn't give me access to their domain (abc.com). they just pointed the domain to new hosting and the site is live.
The problem came when I wanted to configure email SMTP. I am using Mailgun for the emails. but for using service like mailgun you have to changes the nameservers in the domain setting. in my case, the client doesn't want to use the domain (abc.com) for emails because the domain is in their owner's name. so they are not changing the nameservers.
So my question is their anyways that I use some other domain or service for sending emails but
not the domain abc.com which is pointed to my hosting.
Also, they don't want to add the A record in the domain. the client just doesn't want to use the same domain for emails.
I hope I made my point clear.
Thanks
Case 1, You can create a subdomain and use dedicated for email like mail.domain.com, in subdomain update DNS recode and use for delivery its also not affect your main domain, in case you use sub email as abc#mail.domain.com for your emails.
Case 2, also an option to use the different domain name for emails and update DNS recode like PTR and DKIM, PTR, SPF
I want to make a mail redirect from www.domain1.com to www.domain2.com. The problem is that domain2.com mail is hosted by Google Apps. All my employees have two mails, employeeX#domain1.com hosted in my office and employeeX#domain2.com hosted by GApps. I will turn off office servers when I'm sure that all the mail is redirected, so they only need to use one mail.
I don't know if changing domain1.com MX register to mail.domain2.com will work.
Any suggestion or ideas to make this happens?
Are you planning to shut down domain1.com? If so, I would suggest adding it as a domain alias on your Google Apps account. This will walk you through domain ownership verification as well as updating your MX records.
Once completed, all users in Apps will automatically have an alias #domain1.com. Because of this and the change to MX records, they will continue to receive emails sent to their username#domain1.com right in their inbox for #domain2.com.
We have custom cms that currently sits on a vendor's subdomain, such as cms.vendor.com. It sends email out as coming from user#vendor.com and it seems to be working fine (using Email Queuing + SwiftMailer)
Our vendor asked us to put in the functionality for his users to be able to select from a dropdown, 3-4 other emails address associated with them from other domains he owns. Basically we need to be able to send out emails from our server labeled as being sent from #hisdomains.com, multiple domains.
I am a web programmer and have no clue when it comes to relaying messages. How would I go about being able to send out emails from his other domains? Does he need to setup permissions on his mail servers, or do I need to get into his SMTP servers to send out?
What are some things I should look out for when it comes to SPAM and gmail trusting us?
EDIT:
Not sure if my original question was clear enough. Vendor owns three domains: mysite.com, myothersite.com, mythirdsite.com. He wants a user from our crm to be able to send emails he has on those domains. So my dedicated server will be trying to send an email out as user#mysite.com, user#myothersite.com, and user#mythirdsite.com in the FROM: header.
As long as your server is allowed to send on behalf of a domain your vendor owns, you should not have a problem; just change the From: header to something else when you send out the e-mail.
Stuff like SPF, Sender ID and DKIM have to be properly configured to allow your server to send on behalf of any domain.
See also: http://en.wikipedia.org/wiki/E-mail_authentication
Any domain where the mx record resolves to the same server will work. so user#any.domain will email the same user on the mx contingent server.
To answer your question - just make sure that the mx records in the DNS zone file for each domain name points to the same server as the domain you want to share emails on.
also dependent on server configuration (like shared or whatever) I'm assuming it's dedicated with a simple email server installed. I'm not sure on cPanel/shared servers. but possibly the same.
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.
I have a registered domain name where the emails are handled by windows live admin center having a single mx record for my domain. I also have access to modify the dns records any time.
We have around 20 email registered in windows live for my domain. for e.g. user1#example.com, user2#example.com etc.
Some users want to go in for google app accounts as they say there are lots of features in it, and therefore I think I need more than one mail server in my organization.
Is it possible that i can have some emails redirected to windows live and some to google apps, provided that I have access to change the dns and mx records?
So you want different users for the same domain to go to different mail servers?
You can't do this by manipulating the DNS records - the mail will be delivered to the server(s) defined by your MX record for the domain without any reference to the user name.
However, there's nothing stopping that mail server being an application that forwards mail onto several other servers based on the user name of the recipient...
This can't be done within the DNS - mail routing is done on the domain part only.
You'll need to arrange for all of the mail to arrive at one central place, and for it to be then forwarded-on depending on who it's for.
Do note that that isn't completely trivial, although any decent mail server should be able to do it. This is because in some cases (cc:, etc) that forwarding will need to result in two copies being forwarded, i.e. if there are multiple recipients and they're not all on the same service.