Emails being routed to old mailboxes, three weeks after changing MX records
We have moved our email hosting from our old hosting provider to Office 365; however, we still use the old provider for website hosting... so it is imperative that we receive the invoices from our old hosting company in our new (i.e. Office 365) mailboxes.
I changed our MX records three weeks ago to point to Office 365 and was just about to go back to delete the old mailboxes to free up space (for our website) but noticed that our billing notifications from our old service provider are still going to the old mailboxes, which we no longer check.
It doesn't look like a DNS replication issue as it has been nearly a month now. It seems to me that the original hosting company's mail servers are simply not checking our MX records as they still think the account is hosted by them.
If I log in to our old webmail system and email one of our email accounts, the email goes to the corresponding mailbox in the old system, rather than to Office 365. If I delete one of our old mailboxes then attempt to send an email from old webmail system to the deleted mailbox, there is a delivery failure "I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out." error.
The billing notifications we receive are from "billing@(OldHostingProvider).com", most likely managed by the same mail server as our old mailboxes used to be on.
Is it normal to see emails sent from an old mailbox not go to the mailbox on the new system, and what would be the best way to ensure our billing notifications go to our new mailboxes in future?
email dns
asked Aug 24 '14 at 11:14
Austin ''Danger'' PowersAustin ''Danger'' Powers
5,004113758
add a comment |
We have moved our email hosting from our old hosting provider to Office 365; however, we still use the old provider for website hosting... so it is imperative that we receive the invoices from our old hosting company in our new (i.e. Office 365) mailboxes.
I changed our MX records three weeks ago to point to Office 365 and was just about to go back to delete the old mailboxes to free up space (for our website) but noticed that our billing notifications from our old service provider are still going to the old mailboxes, which we no longer check.
It doesn't look like a DNS replication issue as it has been nearly a month now. It seems to me that the original hosting company's mail servers are simply not checking our MX records as they still think the account is hosted by them.
If I log in to our old webmail system and email one of our email accounts, the email goes to the corresponding mailbox in the old system, rather than to Office 365. If I delete one of our old mailboxes then attempt to send an email from old webmail system to the deleted mailbox, there is a delivery failure "I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out." error.
The billing notifications we receive are from "billing@(OldHostingProvider).com", most likely managed by the same mail server as our old mailboxes used to be on.
Is it normal to see emails sent from an old mailbox not go to the mailbox on the new system, and what would be the best way to ensure our billing notifications go to our new mailboxes in future?
email dns
asked Aug 24 '14 at 11:14
Austin ''Danger'' PowersAustin ''Danger'' Powers
5,004113758
I wanted to check here first in case I was missing something. I'll check with them and update this with their response.
– Austin ''Danger'' Powers
Aug 25 '14 at 2:21
add a comment |
We have moved our email hosting from our old hosting provider to Office 365; however, we still use the old provider for website hosting... so it is imperative that we receive the invoices from our old hosting company in our new (i.e. Office 365) mailboxes.
I changed our MX records three weeks ago to point to Office 365 and was just about to go back to delete the old mailboxes to free up space (for our website) but noticed that our billing notifications from our old service provider are still going to the old mailboxes, which we no longer check.
It doesn't look like a DNS replication issue as it has been nearly a month now. It seems to me that the original hosting company's mail servers are simply not checking our MX records as they still think the account is hosted by them.
If I log in to our old webmail system and email one of our email accounts, the email goes to the corresponding mailbox in the old system, rather than to Office 365. If I delete one of our old mailboxes then attempt to send an email from old webmail system to the deleted mailbox, there is a delivery failure "I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out." error.
The billing notifications we receive are from "billing@(OldHostingProvider).com", most likely managed by the same mail server as our old mailboxes used to be on.
Is it normal to see emails sent from an old mailbox not go to the mailbox on the new system, and what would be the best way to ensure our billing notifications go to our new mailboxes in future?
email dns
asked Aug 24 '14 at 11:14
Austin ''Danger'' PowersAustin ''Danger'' Powers
5,004113758
We have moved our email hosting from our old hosting provider to Office 365; however, we still use the old provider for website hosting... so it is imperative that we receive the invoices from our old hosting company in our new (i.e. Office 365) mailboxes.
I changed our MX records three weeks ago to point to Office 365 and was just about to go back to delete the old mailboxes to free up space (for our website) but noticed that our billing notifications from our old service provider are still going to the old mailboxes, which we no longer check.
It doesn't look like a DNS replication issue as it has been nearly a month now. It seems to me that the original hosting company's mail servers are simply not checking our MX records as they still think the account is hosted by them.
If I log in to our old webmail system and email one of our email accounts, the email goes to the corresponding mailbox in the old system, rather than to Office 365. If I delete one of our old mailboxes then attempt to send an email from old webmail system to the deleted mailbox, there is a delivery failure "I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out." error.
The billing notifications we receive are from "billing@(OldHostingProvider).com", most likely managed by the same mail server as our old mailboxes used to be on.
Is it normal to see emails sent from an old mailbox not go to the mailbox on the new system, and what would be the best way to ensure our billing notifications go to our new mailboxes in future?
email dns
email dns
asked Aug 24 '14 at 11:14
Austin ''Danger'' PowersAustin ''Danger'' Powers
5,004113758
asked Aug 24 '14 at 11:14
Austin ''Danger'' PowersAustin ''Danger'' Powers
5,004113758
edited Aug 24 '14 at 11:31
Austin ''Danger'' Powers
asked Aug 24 '14 at 11:14
Austin ''Danger'' PowersAustin ''Danger'' Powers
5,004113758
asked Aug 24 '14 at 11:14
Austin ''Danger'' PowersAustin ''Danger'' Powers
5,004113758
asked Aug 24 '14 at 11:14
Austin ''Danger'' PowersAustin ''Danger'' Powers
5,004113758
5,004113758
I wanted to check here first in case I was missing something. I'll check with them and update this with their response.
– Austin ''Danger'' Powers
Aug 25 '14 at 2:21
add a comment |
I wanted to check here first in case I was missing something. I'll check with them and update this with their response.
– Austin ''Danger'' Powers
Aug 25 '14 at 2:21
I wanted to check here first in case I was missing something. I'll check with them and update this with their response.
– Austin ''Danger'' Powers
Aug 25 '14 at 2:21
I wanted to check here first in case I was missing something. I'll check with them and update this with their response.
– Austin ''Danger'' Powers
Aug 25 '14 at 2:21
add a comment |
1 Answer
1
active
oldest
votes
Most probably, you'll only have problems with mails from your old provider (and any other hosts on the same "shared hosting" system)
This is because you didn't inform your old provider that you're moving your MX (and you should have), so in their local configuration they're still configured as authorative for your domain. So, any mail originating from that system will just "know" they need to deliver mails locally on oldprovider mail server, instead of routing them out to the internet.
Which happens to be wrong, because you made an error of not informing them.
So what you need to do is contact your oldprovider, and tell them you will continue using their web services, but that you have moved mail elsewhere, so they need to remove mail configuration for your domain.
After that, their mail servers will consider your domain as external (same as any other one not being their customer), and will route it out to the net, where it will reach your new hosts.
answered Aug 27 '14 at 0:15
Matija NalisMatija Nalis
1,608816
I told them yesterday and they deleted our old mailboxes (after giving me time to check them). The problem is now solved.
– Austin ''Danger'' Powers
Aug 27 '14 at 8:25
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f802282%2femails-being-routed-to-old-mailboxes-three-weeks-after-changing-mx-records%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Most probably, you'll only have problems with mails from your old provider (and any other hosts on the same "shared hosting" system)
This is because you didn't inform your old provider that you're moving your MX (and you should have), so in their local configuration they're still configured as authorative for your domain. So, any mail originating from that system will just "know" they need to deliver mails locally on oldprovider mail server, instead of routing them out to the internet.
Which happens to be wrong, because you made an error of not informing them.
So what you need to do is contact your oldprovider, and tell them you will continue using their web services, but that you have moved mail elsewhere, so they need to remove mail configuration for your domain.
After that, their mail servers will consider your domain as external (same as any other one not being their customer), and will route it out to the net, where it will reach your new hosts.
answered Aug 27 '14 at 0:15
Matija NalisMatija Nalis
1,608816
I told them yesterday and they deleted our old mailboxes (after giving me time to check them). The problem is now solved.
– Austin ''Danger'' Powers
Aug 27 '14 at 8:25
add a comment |
Most probably, you'll only have problems with mails from your old provider (and any other hosts on the same "shared hosting" system)
This is because you didn't inform your old provider that you're moving your MX (and you should have), so in their local configuration they're still configured as authorative for your domain. So, any mail originating from that system will just "know" they need to deliver mails locally on oldprovider mail server, instead of routing them out to the internet.
Which happens to be wrong, because you made an error of not informing them.
So what you need to do is contact your oldprovider, and tell them you will continue using their web services, but that you have moved mail elsewhere, so they need to remove mail configuration for your domain.
After that, their mail servers will consider your domain as external (same as any other one not being their customer), and will route it out to the net, where it will reach your new hosts.
answered Aug 27 '14 at 0:15
Matija NalisMatija Nalis
1,608816
I told them yesterday and they deleted our old mailboxes (after giving me time to check them). The problem is now solved.
– Austin ''Danger'' Powers
Aug 27 '14 at 8:25
add a comment |
Most probably, you'll only have problems with mails from your old provider (and any other hosts on the same "shared hosting" system)
This is because you didn't inform your old provider that you're moving your MX (and you should have), so in their local configuration they're still configured as authorative for your domain. So, any mail originating from that system will just "know" they need to deliver mails locally on oldprovider mail server, instead of routing them out to the internet.
Which happens to be wrong, because you made an error of not informing them.
So what you need to do is contact your oldprovider, and tell them you will continue using their web services, but that you have moved mail elsewhere, so they need to remove mail configuration for your domain.
After that, their mail servers will consider your domain as external (same as any other one not being their customer), and will route it out to the net, where it will reach your new hosts.
answered Aug 27 '14 at 0:15
Matija NalisMatija Nalis
1,608816
Most probably, you'll only have problems with mails from your old provider (and any other hosts on the same "shared hosting" system)
This is because you didn't inform your old provider that you're moving your MX (and you should have), so in their local configuration they're still configured as authorative for your domain. So, any mail originating from that system will just "know" they need to deliver mails locally on oldprovider mail server, instead of routing them out to the internet.
Which happens to be wrong, because you made an error of not informing them.
So what you need to do is contact your oldprovider, and tell them you will continue using their web services, but that you have moved mail elsewhere, so they need to remove mail configuration for your domain.
After that, their mail servers will consider your domain as external (same as any other one not being their customer), and will route it out to the net, where it will reach your new hosts.
answered Aug 27 '14 at 0:15
Matija NalisMatija Nalis
1,608816
answered Aug 27 '14 at 0:15
Matija NalisMatija Nalis
1,608816
answered Aug 27 '14 at 0:15
Matija NalisMatija Nalis
1,608816
answered Aug 27 '14 at 0:15
Matija NalisMatija Nalis
1,608816
1,608816
I told them yesterday and they deleted our old mailboxes (after giving me time to check them). The problem is now solved.
– Austin ''Danger'' Powers
Aug 27 '14 at 8:25
add a comment |
I told them yesterday and they deleted our old mailboxes (after giving me time to check them). The problem is now solved.
– Austin ''Danger'' Powers
Aug 27 '14 at 8:25
I told them yesterday and they deleted our old mailboxes (after giving me time to check them). The problem is now solved.
– Austin ''Danger'' Powers
Aug 27 '14 at 8:25
I told them yesterday and they deleted our old mailboxes (after giving me time to check them). The problem is now solved.
– Austin ''Danger'' Powers
Aug 27 '14 at 8:25
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f802282%2femails-being-routed-to-old-mailboxes-three-weeks-after-changing-mx-records%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I wanted to check here first in case I was missing something. I'll check with them and update this with their response.
– Austin ''Danger'' Powers
Aug 25 '14 at 2:21