mail not working pointing at old server Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar Manara Come Celebrate our 10 Year Anniversary!dns mx record vs reverse dnsCannot Receive Email - Troubleshoot DNSBest way to handle a mail server's changeGlobal Reverse DNS look-ups not workingCitadel 550 Invalid recipientCatch All Email for Old Domain?Suggestion required for Mailbox migration from Mailenable 7.5 POP/SMTP to Exchange ServerRedirect mail to site with no domainHow to set reverse DNS in AWS for my private nameserver?Is it Okay for an MX Record to Differ from Incoming/Outgoing Mail Server Address?
Multi tool use
Implementing 3DES algorithm in Java: is my code secure?
What's the difference between using dependency injection with a container and using a service locator?
Is Bran literally the world's memory?
What is /etc/mtab in Linux?
What was Apollo 13's "Little Jolt" after MECO?
What ability score does a Hexblade's Pact Weapon use for attack and damage when wielded by another character?
What to do with someone that cheated their way through university and a PhD program?
Trumpet valves, lengths, and pitch
Is it OK if I do not take the receipt in Germany?
finding a tangent line to a parabola
What is it called when you ride around on your front wheel?
Is a 5 watt UHF/VHF handheld considered QRP?
What's parked in Mil Moscow helicopter plant?
How to avoid introduction cliches
Rolling Stones Sway guitar solo chord function
How long after the last departure shall the airport stay open for an emergency return?
Arriving in Atlanta after US Preclearance in Dublin. Will I go through TSA security in Atlanta to transfer to a connecting flight?
Second order approximation of the loss function (Deep learning book, 7.33)
How would this chord from "Rocket Man" be analyzed?
Expansion//Explosion and Siren Stormtamer
What is the least dense liquid under normal conditions?
What *exactly* is electrical current, voltage, and resistance?
What is this word supposed to be?
My bank got bought out, am I now going to have to start filing tax returns in a different state?
mail not working pointing at old server
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar Manara
Come Celebrate our 10 Year Anniversary!dns mx record vs reverse dnsCannot Receive Email - Troubleshoot DNSBest way to handle a mail server's changeGlobal Reverse DNS look-ups not workingCitadel 550 Invalid recipientCatch All Email for Old Domain?Suggestion required for Mailbox migration from Mailenable 7.5 POP/SMTP to Exchange ServerRedirect mail to site with no domainHow to set reverse DNS in AWS for my private nameserver?Is it Okay for an MX Record to Differ from Incoming/Outgoing Mail Server Address?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
Hoping you can help, I'll preface to say that I'm working for a small company and I'm the "IT Guy" as I'm not sure what to ask google, and I've searched here for hours, and still no closer to an answer, so I'm looking for help as I'm a bit out of my depth.
Long story short, I've migrated server for the website to a new server. As we have multiple users not all based in the same location and none are computer literate, it was decided that we would keep the old server for email for now until we can come up with a good solution to get them all onto the new one.
I changed the DNS and set the records on my new server as follows:
MX mydomain.com mail.mydomain.com 10 14400
A mail.mydomain.com xx.xx.xx.xx (Original IP) 14400
A mydomain.com xx.xx.xx.xx (New IP) 3600
I made no changes to the old server, and now I can send emails out, but now can no longer receive them getting the following error:
The mail system <useraddress@mydomain.com>: connect to mail.mydomain.com[xx.xx.xx.xx]:25: (NEW IP)
Operation timed out
I am at my wits end how to solve this. One thing I noticed is that the bouncebacks get the New IP rather than the old one, so this makes me think I've messed something up on setup.
Hoping someone can help me figure out what it should be. Please let me know if you need additional information.
Cheers
email-server reverse-dns email-bounces
asked Apr 18 at 3:00
AndrewAndrew
1
add a comment |
Hoping you can help, I'll preface to say that I'm working for a small company and I'm the "IT Guy" as I'm not sure what to ask google, and I've searched here for hours, and still no closer to an answer, so I'm looking for help as I'm a bit out of my depth.
Long story short, I've migrated server for the website to a new server. As we have multiple users not all based in the same location and none are computer literate, it was decided that we would keep the old server for email for now until we can come up with a good solution to get them all onto the new one.
I changed the DNS and set the records on my new server as follows:
MX mydomain.com mail.mydomain.com 10 14400
A mail.mydomain.com xx.xx.xx.xx (Original IP) 14400
A mydomain.com xx.xx.xx.xx (New IP) 3600
I made no changes to the old server, and now I can send emails out, but now can no longer receive them getting the following error:
The mail system <useraddress@mydomain.com>: connect to mail.mydomain.com[xx.xx.xx.xx]:25: (NEW IP)
Operation timed out
I am at my wits end how to solve this. One thing I noticed is that the bouncebacks get the New IP rather than the old one, so this makes me think I've messed something up on setup.
Hoping someone can help me figure out what it should be. Please let me know if you need additional information.
Cheers
email-server reverse-dns email-bounces
asked Apr 18 at 3:00
AndrewAndrew
1
1
It smells like someone put the wrong IP address in the wrong record. Check your actual DNS records. If you don't find the problem, show your real domain name. It is probably not possible to answer this without it.
– Michael Hampton♦
Apr 18 at 3:04
Thanks @MichaelHampton for taking the time to answer. I checked through my DNS settings, and on the old server I didn't have anything to handlemail.mydomain.com. I've put this in there, not sure if this is actually required or not, but I'm sure it can't hurt. Will let you know in a few hours if this has helped.
– Andrew
Apr 18 at 3:20
1
The error clearly shows a timeout, implying replays go to the wrong IP. Make sure your MX DNS is correct. You domain can be mydomain.com with IP 1.2.3.4 and e-mail server can be mail.mydomain.com with a different IP (1.2.3.5) but for this to work all DNS authoritive records must be correctly done. Also, if you used something like DKIM you'll have to make sure that part is OK.
– Overmind
Apr 18 at 8:38
On top of the couple of things mentioned, I want to clarify the table above just to make sure it's clear. You have "MX mydomain.com mail.mydomain.com". I'm assuming this is a table on your DNS provider in the format of "record type, record, destination"? If so you are telling everybody in the world that mail for mydomain.com is to be sent to mail.mydomain.com. The A record for mail.mydomain.com is (based on your data) pointing to the old server. Is that correct?
– Jon Angliss
Apr 18 at 17:07
add a comment |
Hoping you can help, I'll preface to say that I'm working for a small company and I'm the "IT Guy" as I'm not sure what to ask google, and I've searched here for hours, and still no closer to an answer, so I'm looking for help as I'm a bit out of my depth.
Long story short, I've migrated server for the website to a new server. As we have multiple users not all based in the same location and none are computer literate, it was decided that we would keep the old server for email for now until we can come up with a good solution to get them all onto the new one.
I changed the DNS and set the records on my new server as follows:
MX mydomain.com mail.mydomain.com 10 14400
A mail.mydomain.com xx.xx.xx.xx (Original IP) 14400
A mydomain.com xx.xx.xx.xx (New IP) 3600
I made no changes to the old server, and now I can send emails out, but now can no longer receive them getting the following error:
The mail system <useraddress@mydomain.com>: connect to mail.mydomain.com[xx.xx.xx.xx]:25: (NEW IP)
Operation timed out
I am at my wits end how to solve this. One thing I noticed is that the bouncebacks get the New IP rather than the old one, so this makes me think I've messed something up on setup.
Hoping someone can help me figure out what it should be. Please let me know if you need additional information.
Cheers
email-server reverse-dns email-bounces
asked Apr 18 at 3:00
AndrewAndrew
1
Hoping you can help, I'll preface to say that I'm working for a small company and I'm the "IT Guy" as I'm not sure what to ask google, and I've searched here for hours, and still no closer to an answer, so I'm looking for help as I'm a bit out of my depth.
Long story short, I've migrated server for the website to a new server. As we have multiple users not all based in the same location and none are computer literate, it was decided that we would keep the old server for email for now until we can come up with a good solution to get them all onto the new one.
I changed the DNS and set the records on my new server as follows:
MX mydomain.com mail.mydomain.com 10 14400
A mail.mydomain.com xx.xx.xx.xx (Original IP) 14400
A mydomain.com xx.xx.xx.xx (New IP) 3600
I made no changes to the old server, and now I can send emails out, but now can no longer receive them getting the following error:
The mail system <useraddress@mydomain.com>: connect to mail.mydomain.com[xx.xx.xx.xx]:25: (NEW IP)
Operation timed out
I am at my wits end how to solve this. One thing I noticed is that the bouncebacks get the New IP rather than the old one, so this makes me think I've messed something up on setup.
Hoping someone can help me figure out what it should be. Please let me know if you need additional information.
Cheers
email-server reverse-dns email-bounces
email-server reverse-dns email-bounces
asked Apr 18 at 3:00
AndrewAndrew
1
asked Apr 18 at 3:00
AndrewAndrew
1
asked Apr 18 at 3:00
AndrewAndrew
1
asked Apr 18 at 3:00
AndrewAndrew
1
asked Apr 18 at 3:00
AndrewAndrew
1
1
1
It smells like someone put the wrong IP address in the wrong record. Check your actual DNS records. If you don't find the problem, show your real domain name. It is probably not possible to answer this without it.
– Michael Hampton♦
Apr 18 at 3:04
Thanks @MichaelHampton for taking the time to answer. I checked through my DNS settings, and on the old server I didn't have anything to handlemail.mydomain.com. I've put this in there, not sure if this is actually required or not, but I'm sure it can't hurt. Will let you know in a few hours if this has helped.
– Andrew
Apr 18 at 3:20
1
The error clearly shows a timeout, implying replays go to the wrong IP. Make sure your MX DNS is correct. You domain can be mydomain.com with IP 1.2.3.4 and e-mail server can be mail.mydomain.com with a different IP (1.2.3.5) but for this to work all DNS authoritive records must be correctly done. Also, if you used something like DKIM you'll have to make sure that part is OK.
– Overmind
Apr 18 at 8:38
On top of the couple of things mentioned, I want to clarify the table above just to make sure it's clear. You have "MX mydomain.com mail.mydomain.com". I'm assuming this is a table on your DNS provider in the format of "record type, record, destination"? If so you are telling everybody in the world that mail for mydomain.com is to be sent to mail.mydomain.com. The A record for mail.mydomain.com is (based on your data) pointing to the old server. Is that correct?
– Jon Angliss
Apr 18 at 17:07
add a comment |
1
It smells like someone put the wrong IP address in the wrong record. Check your actual DNS records. If you don't find the problem, show your real domain name. It is probably not possible to answer this without it.
– Michael Hampton♦
Apr 18 at 3:04
Thanks @MichaelHampton for taking the time to answer. I checked through my DNS settings, and on the old server I didn't have anything to handlemail.mydomain.com. I've put this in there, not sure if this is actually required or not, but I'm sure it can't hurt. Will let you know in a few hours if this has helped.
– Andrew
Apr 18 at 3:20
1
The error clearly shows a timeout, implying replays go to the wrong IP. Make sure your MX DNS is correct. You domain can be mydomain.com with IP 1.2.3.4 and e-mail server can be mail.mydomain.com with a different IP (1.2.3.5) but for this to work all DNS authoritive records must be correctly done. Also, if you used something like DKIM you'll have to make sure that part is OK.
– Overmind
Apr 18 at 8:38
On top of the couple of things mentioned, I want to clarify the table above just to make sure it's clear. You have "MX mydomain.com mail.mydomain.com". I'm assuming this is a table on your DNS provider in the format of "record type, record, destination"? If so you are telling everybody in the world that mail for mydomain.com is to be sent to mail.mydomain.com. The A record for mail.mydomain.com is (based on your data) pointing to the old server. Is that correct?
– Jon Angliss
Apr 18 at 17:07
1
1
It smells like someone put the wrong IP address in the wrong record. Check your actual DNS records. If you don't find the problem, show your real domain name. It is probably not possible to answer this without it.
– Michael Hampton♦
Apr 18 at 3:04
It smells like someone put the wrong IP address in the wrong record. Check your actual DNS records. If you don't find the problem, show your real domain name. It is probably not possible to answer this without it.
– Michael Hampton♦
Apr 18 at 3:04
Thanks @MichaelHampton for taking the time to answer. I checked through my DNS settings, and on the old server I didn't have anything to handle
mail.mydomain.com. I've put this in there, not sure if this is actually required or not, but I'm sure it can't hurt. Will let you know in a few hours if this has helped.– Andrew
Apr 18 at 3:20
Thanks @MichaelHampton for taking the time to answer. I checked through my DNS settings, and on the old server I didn't have anything to handle
mail.mydomain.com. I've put this in there, not sure if this is actually required or not, but I'm sure it can't hurt. Will let you know in a few hours if this has helped.– Andrew
Apr 18 at 3:20
1
1
The error clearly shows a timeout, implying replays go to the wrong IP. Make sure your MX DNS is correct. You domain can be mydomain.com with IP 1.2.3.4 and e-mail server can be mail.mydomain.com with a different IP (1.2.3.5) but for this to work all DNS authoritive records must be correctly done. Also, if you used something like DKIM you'll have to make sure that part is OK.
– Overmind
Apr 18 at 8:38
The error clearly shows a timeout, implying replays go to the wrong IP. Make sure your MX DNS is correct. You domain can be mydomain.com with IP 1.2.3.4 and e-mail server can be mail.mydomain.com with a different IP (1.2.3.5) but for this to work all DNS authoritive records must be correctly done. Also, if you used something like DKIM you'll have to make sure that part is OK.
– Overmind
Apr 18 at 8:38
On top of the couple of things mentioned, I want to clarify the table above just to make sure it's clear. You have "MX mydomain.com mail.mydomain.com". I'm assuming this is a table on your DNS provider in the format of "record type, record, destination"? If so you are telling everybody in the world that mail for mydomain.com is to be sent to mail.mydomain.com. The A record for mail.mydomain.com is (based on your data) pointing to the old server. Is that correct?
– Jon Angliss
Apr 18 at 17:07
On top of the couple of things mentioned, I want to clarify the table above just to make sure it's clear. You have "MX mydomain.com mail.mydomain.com". I'm assuming this is a table on your DNS provider in the format of "record type, record, destination"? If so you are telling everybody in the world that mail for mydomain.com is to be sent to mail.mydomain.com. The A record for mail.mydomain.com is (based on your data) pointing to the old server. Is that correct?
– Jon Angliss
Apr 18 at 17:07
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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%2fserverfault.com%2fquestions%2f963594%2fmail-not-working-pointing-at-old-server%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f963594%2fmail-not-working-pointing-at-old-server%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
ehudISTwyLk,brZRpJ37l0dBO8ru6dmiXGZPCHef8jHcQ2 l3,hsWymMZPq4UtM73
1
It smells like someone put the wrong IP address in the wrong record. Check your actual DNS records. If you don't find the problem, show your real domain name. It is probably not possible to answer this without it.
– Michael Hampton♦
Apr 18 at 3:04
Thanks @MichaelHampton for taking the time to answer. I checked through my DNS settings, and on the old server I didn't have anything to handle
mail.mydomain.com. I've put this in there, not sure if this is actually required or not, but I'm sure it can't hurt. Will let you know in a few hours if this has helped.– Andrew
Apr 18 at 3:20
1
The error clearly shows a timeout, implying replays go to the wrong IP. Make sure your MX DNS is correct. You domain can be mydomain.com with IP 1.2.3.4 and e-mail server can be mail.mydomain.com with a different IP (1.2.3.5) but for this to work all DNS authoritive records must be correctly done. Also, if you used something like DKIM you'll have to make sure that part is OK.
– Overmind
Apr 18 at 8:38
On top of the couple of things mentioned, I want to clarify the table above just to make sure it's clear. You have "MX mydomain.com mail.mydomain.com". I'm assuming this is a table on your DNS provider in the format of "record type, record, destination"? If so you are telling everybody in the world that mail for mydomain.com is to be sent to mail.mydomain.com. The A record for mail.mydomain.com is (based on your data) pointing to the old server. Is that correct?
– Jon Angliss
Apr 18 at 17:07