How to setup inbound email correctly? MX settings?
up vote
0
down vote
favorite
Summary
So I have mostly set up hosting emails. I can send mails from my phone through IMAP with my new server however I never receive any mail. I have tried the following:
telnet localhost 2525
ehlo f.com
mail from: eric
rcpt to: eric@f.com
data
Subject: Test
This is a test
.
This shows that the email queries correctly however running the following shows 0 emails received:
telnet localhost 173
a login user pass
b select inbox
At this point I see no new emails:
0 EXISTS
0 RECENT
c logout
However if I do the same but send it to an external email address (like gmail) then it works. This leads me to believe that I simply can't receive incoming emails right now. I have also verified this through sending from a gmail address but it still shows 0 EXISTS
.
What I think is wrong
So I have an ISP that does block port 25, and for that reason I use dynu.com to redirect port 25 to port 2525 instead. The outbound traffic is getting redirected correctly as I am able to send emails out so my thought is that my MX record is not setup correctly.
I have my MX setup as follows:
I just redirect it to the dynu account basically. Is this done correctly? Isn't this basically where e@f.com gets redirected to the dyndns service of dynu then back to my actual server?
Dynu Settings:
email dns postfix dovecot
add a comment |
up vote
0
down vote
favorite
Summary
So I have mostly set up hosting emails. I can send mails from my phone through IMAP with my new server however I never receive any mail. I have tried the following:
telnet localhost 2525
ehlo f.com
mail from: eric
rcpt to: eric@f.com
data
Subject: Test
This is a test
.
This shows that the email queries correctly however running the following shows 0 emails received:
telnet localhost 173
a login user pass
b select inbox
At this point I see no new emails:
0 EXISTS
0 RECENT
c logout
However if I do the same but send it to an external email address (like gmail) then it works. This leads me to believe that I simply can't receive incoming emails right now. I have also verified this through sending from a gmail address but it still shows 0 EXISTS
.
What I think is wrong
So I have an ISP that does block port 25, and for that reason I use dynu.com to redirect port 25 to port 2525 instead. The outbound traffic is getting redirected correctly as I am able to send emails out so my thought is that my MX record is not setup correctly.
I have my MX setup as follows:
I just redirect it to the dynu account basically. Is this done correctly? Isn't this basically where e@f.com gets redirected to the dyndns service of dynu then back to my actual server?
Dynu Settings:
email dns postfix dovecot
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Summary
So I have mostly set up hosting emails. I can send mails from my phone through IMAP with my new server however I never receive any mail. I have tried the following:
telnet localhost 2525
ehlo f.com
mail from: eric
rcpt to: eric@f.com
data
Subject: Test
This is a test
.
This shows that the email queries correctly however running the following shows 0 emails received:
telnet localhost 173
a login user pass
b select inbox
At this point I see no new emails:
0 EXISTS
0 RECENT
c logout
However if I do the same but send it to an external email address (like gmail) then it works. This leads me to believe that I simply can't receive incoming emails right now. I have also verified this through sending from a gmail address but it still shows 0 EXISTS
.
What I think is wrong
So I have an ISP that does block port 25, and for that reason I use dynu.com to redirect port 25 to port 2525 instead. The outbound traffic is getting redirected correctly as I am able to send emails out so my thought is that my MX record is not setup correctly.
I have my MX setup as follows:
I just redirect it to the dynu account basically. Is this done correctly? Isn't this basically where e@f.com gets redirected to the dyndns service of dynu then back to my actual server?
Dynu Settings:
email dns postfix dovecot
Summary
So I have mostly set up hosting emails. I can send mails from my phone through IMAP with my new server however I never receive any mail. I have tried the following:
telnet localhost 2525
ehlo f.com
mail from: eric
rcpt to: eric@f.com
data
Subject: Test
This is a test
.
This shows that the email queries correctly however running the following shows 0 emails received:
telnet localhost 173
a login user pass
b select inbox
At this point I see no new emails:
0 EXISTS
0 RECENT
c logout
However if I do the same but send it to an external email address (like gmail) then it works. This leads me to believe that I simply can't receive incoming emails right now. I have also verified this through sending from a gmail address but it still shows 0 EXISTS
.
What I think is wrong
So I have an ISP that does block port 25, and for that reason I use dynu.com to redirect port 25 to port 2525 instead. The outbound traffic is getting redirected correctly as I am able to send emails out so my thought is that my MX record is not setup correctly.
I have my MX setup as follows:
I just redirect it to the dynu account basically. Is this done correctly? Isn't this basically where e@f.com gets redirected to the dyndns service of dynu then back to my actual server?
Dynu Settings:
email dns postfix dovecot
email dns postfix dovecot
edited Nov 26 at 17:57
asked Nov 26 at 16:40
Eric F
2,73631131
2,73631131
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Your DNS settings look odd. Normally, given an address of foo@example.com
, the MX entry of example.com
should contain the hostname to contact (at port 25) for delivering mail (say, mail.example.com
). Whoever wants to deliver to example.com
will then know to do an IP address (A
record) lookup for mail.example.com
and then, ultimately, to connect to this IP address (again, at port 25) for opening an SMTP dialog.
You can emulate this process using the following (Linux) console commands:
% host -t MX example.com
example.com mail is handled by 10 mail.example.com.
% host -t A mail.example.com.
mail.example.com has address 1.2.3.4
% telnet 1.2.3.4 25
220 mail.example.com ESMTP ...
QUIT
Thanks for the response. I changed the Mail server address to: relay.dynu.com. When running your example I get: f.com mail is handled by 10 relay.dynu.com > relay@dynu.com has address 168.235.105.136 (not my IP address)
– Eric F
Nov 26 at 17:23
I did try changing it so it points to f.dynu.net instead and then when I do host -t f.dynu.net it does show my ipaddress... so I will have to see if that works. I need to wait until my MX change actually goes through
– Eric F
Nov 26 at 17:26
I am guessing that a connection torelay.dynu.com
port 25 does not reach your server at port 2525. Most likely dynu.com is not doing what you hoped it would do (give you a hostname that forwards every connection to its port 2525 to your port 25). I would guess that the best service they offer is to host a mail relay for you (accepting all email and then forwarding it on to your server, likely using ETRN instead of SMTP then)
– Christoph Sommer
Nov 26 at 17:36
See my edit to my question. It shows outgoing ports should goto 25, 26, an 2525 so I think it should be doing its job of forwarding emails to port 2525 as far as I can tell..
– Eric F
Nov 26 at 17:43
The settings you posted are listed as outgoing ports, so I am guessing this is for sending mail from your computer.
– Christoph Sommer
Nov 26 at 17:46
|
show 2 more comments
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',
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%2f1378508%2fhow-to-setup-inbound-email-correctly-mx-settings%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
up vote
0
down vote
Your DNS settings look odd. Normally, given an address of foo@example.com
, the MX entry of example.com
should contain the hostname to contact (at port 25) for delivering mail (say, mail.example.com
). Whoever wants to deliver to example.com
will then know to do an IP address (A
record) lookup for mail.example.com
and then, ultimately, to connect to this IP address (again, at port 25) for opening an SMTP dialog.
You can emulate this process using the following (Linux) console commands:
% host -t MX example.com
example.com mail is handled by 10 mail.example.com.
% host -t A mail.example.com.
mail.example.com has address 1.2.3.4
% telnet 1.2.3.4 25
220 mail.example.com ESMTP ...
QUIT
Thanks for the response. I changed the Mail server address to: relay.dynu.com. When running your example I get: f.com mail is handled by 10 relay.dynu.com > relay@dynu.com has address 168.235.105.136 (not my IP address)
– Eric F
Nov 26 at 17:23
I did try changing it so it points to f.dynu.net instead and then when I do host -t f.dynu.net it does show my ipaddress... so I will have to see if that works. I need to wait until my MX change actually goes through
– Eric F
Nov 26 at 17:26
I am guessing that a connection torelay.dynu.com
port 25 does not reach your server at port 2525. Most likely dynu.com is not doing what you hoped it would do (give you a hostname that forwards every connection to its port 2525 to your port 25). I would guess that the best service they offer is to host a mail relay for you (accepting all email and then forwarding it on to your server, likely using ETRN instead of SMTP then)
– Christoph Sommer
Nov 26 at 17:36
See my edit to my question. It shows outgoing ports should goto 25, 26, an 2525 so I think it should be doing its job of forwarding emails to port 2525 as far as I can tell..
– Eric F
Nov 26 at 17:43
The settings you posted are listed as outgoing ports, so I am guessing this is for sending mail from your computer.
– Christoph Sommer
Nov 26 at 17:46
|
show 2 more comments
up vote
0
down vote
Your DNS settings look odd. Normally, given an address of foo@example.com
, the MX entry of example.com
should contain the hostname to contact (at port 25) for delivering mail (say, mail.example.com
). Whoever wants to deliver to example.com
will then know to do an IP address (A
record) lookup for mail.example.com
and then, ultimately, to connect to this IP address (again, at port 25) for opening an SMTP dialog.
You can emulate this process using the following (Linux) console commands:
% host -t MX example.com
example.com mail is handled by 10 mail.example.com.
% host -t A mail.example.com.
mail.example.com has address 1.2.3.4
% telnet 1.2.3.4 25
220 mail.example.com ESMTP ...
QUIT
Thanks for the response. I changed the Mail server address to: relay.dynu.com. When running your example I get: f.com mail is handled by 10 relay.dynu.com > relay@dynu.com has address 168.235.105.136 (not my IP address)
– Eric F
Nov 26 at 17:23
I did try changing it so it points to f.dynu.net instead and then when I do host -t f.dynu.net it does show my ipaddress... so I will have to see if that works. I need to wait until my MX change actually goes through
– Eric F
Nov 26 at 17:26
I am guessing that a connection torelay.dynu.com
port 25 does not reach your server at port 2525. Most likely dynu.com is not doing what you hoped it would do (give you a hostname that forwards every connection to its port 2525 to your port 25). I would guess that the best service they offer is to host a mail relay for you (accepting all email and then forwarding it on to your server, likely using ETRN instead of SMTP then)
– Christoph Sommer
Nov 26 at 17:36
See my edit to my question. It shows outgoing ports should goto 25, 26, an 2525 so I think it should be doing its job of forwarding emails to port 2525 as far as I can tell..
– Eric F
Nov 26 at 17:43
The settings you posted are listed as outgoing ports, so I am guessing this is for sending mail from your computer.
– Christoph Sommer
Nov 26 at 17:46
|
show 2 more comments
up vote
0
down vote
up vote
0
down vote
Your DNS settings look odd. Normally, given an address of foo@example.com
, the MX entry of example.com
should contain the hostname to contact (at port 25) for delivering mail (say, mail.example.com
). Whoever wants to deliver to example.com
will then know to do an IP address (A
record) lookup for mail.example.com
and then, ultimately, to connect to this IP address (again, at port 25) for opening an SMTP dialog.
You can emulate this process using the following (Linux) console commands:
% host -t MX example.com
example.com mail is handled by 10 mail.example.com.
% host -t A mail.example.com.
mail.example.com has address 1.2.3.4
% telnet 1.2.3.4 25
220 mail.example.com ESMTP ...
QUIT
Your DNS settings look odd. Normally, given an address of foo@example.com
, the MX entry of example.com
should contain the hostname to contact (at port 25) for delivering mail (say, mail.example.com
). Whoever wants to deliver to example.com
will then know to do an IP address (A
record) lookup for mail.example.com
and then, ultimately, to connect to this IP address (again, at port 25) for opening an SMTP dialog.
You can emulate this process using the following (Linux) console commands:
% host -t MX example.com
example.com mail is handled by 10 mail.example.com.
% host -t A mail.example.com.
mail.example.com has address 1.2.3.4
% telnet 1.2.3.4 25
220 mail.example.com ESMTP ...
QUIT
answered Nov 26 at 17:05
Christoph Sommer
1813
1813
Thanks for the response. I changed the Mail server address to: relay.dynu.com. When running your example I get: f.com mail is handled by 10 relay.dynu.com > relay@dynu.com has address 168.235.105.136 (not my IP address)
– Eric F
Nov 26 at 17:23
I did try changing it so it points to f.dynu.net instead and then when I do host -t f.dynu.net it does show my ipaddress... so I will have to see if that works. I need to wait until my MX change actually goes through
– Eric F
Nov 26 at 17:26
I am guessing that a connection torelay.dynu.com
port 25 does not reach your server at port 2525. Most likely dynu.com is not doing what you hoped it would do (give you a hostname that forwards every connection to its port 2525 to your port 25). I would guess that the best service they offer is to host a mail relay for you (accepting all email and then forwarding it on to your server, likely using ETRN instead of SMTP then)
– Christoph Sommer
Nov 26 at 17:36
See my edit to my question. It shows outgoing ports should goto 25, 26, an 2525 so I think it should be doing its job of forwarding emails to port 2525 as far as I can tell..
– Eric F
Nov 26 at 17:43
The settings you posted are listed as outgoing ports, so I am guessing this is for sending mail from your computer.
– Christoph Sommer
Nov 26 at 17:46
|
show 2 more comments
Thanks for the response. I changed the Mail server address to: relay.dynu.com. When running your example I get: f.com mail is handled by 10 relay.dynu.com > relay@dynu.com has address 168.235.105.136 (not my IP address)
– Eric F
Nov 26 at 17:23
I did try changing it so it points to f.dynu.net instead and then when I do host -t f.dynu.net it does show my ipaddress... so I will have to see if that works. I need to wait until my MX change actually goes through
– Eric F
Nov 26 at 17:26
I am guessing that a connection torelay.dynu.com
port 25 does not reach your server at port 2525. Most likely dynu.com is not doing what you hoped it would do (give you a hostname that forwards every connection to its port 2525 to your port 25). I would guess that the best service they offer is to host a mail relay for you (accepting all email and then forwarding it on to your server, likely using ETRN instead of SMTP then)
– Christoph Sommer
Nov 26 at 17:36
See my edit to my question. It shows outgoing ports should goto 25, 26, an 2525 so I think it should be doing its job of forwarding emails to port 2525 as far as I can tell..
– Eric F
Nov 26 at 17:43
The settings you posted are listed as outgoing ports, so I am guessing this is for sending mail from your computer.
– Christoph Sommer
Nov 26 at 17:46
Thanks for the response. I changed the Mail server address to: relay.dynu.com. When running your example I get: f.com mail is handled by 10 relay.dynu.com > relay@dynu.com has address 168.235.105.136 (not my IP address)
– Eric F
Nov 26 at 17:23
Thanks for the response. I changed the Mail server address to: relay.dynu.com. When running your example I get: f.com mail is handled by 10 relay.dynu.com > relay@dynu.com has address 168.235.105.136 (not my IP address)
– Eric F
Nov 26 at 17:23
I did try changing it so it points to f.dynu.net instead and then when I do host -t f.dynu.net it does show my ipaddress... so I will have to see if that works. I need to wait until my MX change actually goes through
– Eric F
Nov 26 at 17:26
I did try changing it so it points to f.dynu.net instead and then when I do host -t f.dynu.net it does show my ipaddress... so I will have to see if that works. I need to wait until my MX change actually goes through
– Eric F
Nov 26 at 17:26
I am guessing that a connection to
relay.dynu.com
port 25 does not reach your server at port 2525. Most likely dynu.com is not doing what you hoped it would do (give you a hostname that forwards every connection to its port 2525 to your port 25). I would guess that the best service they offer is to host a mail relay for you (accepting all email and then forwarding it on to your server, likely using ETRN instead of SMTP then)– Christoph Sommer
Nov 26 at 17:36
I am guessing that a connection to
relay.dynu.com
port 25 does not reach your server at port 2525. Most likely dynu.com is not doing what you hoped it would do (give you a hostname that forwards every connection to its port 2525 to your port 25). I would guess that the best service they offer is to host a mail relay for you (accepting all email and then forwarding it on to your server, likely using ETRN instead of SMTP then)– Christoph Sommer
Nov 26 at 17:36
See my edit to my question. It shows outgoing ports should goto 25, 26, an 2525 so I think it should be doing its job of forwarding emails to port 2525 as far as I can tell..
– Eric F
Nov 26 at 17:43
See my edit to my question. It shows outgoing ports should goto 25, 26, an 2525 so I think it should be doing its job of forwarding emails to port 2525 as far as I can tell..
– Eric F
Nov 26 at 17:43
The settings you posted are listed as outgoing ports, so I am guessing this is for sending mail from your computer.
– Christoph Sommer
Nov 26 at 17:46
The settings you posted are listed as outgoing ports, so I am guessing this is for sending mail from your computer.
– Christoph Sommer
Nov 26 at 17:46
|
show 2 more comments
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1378508%2fhow-to-setup-inbound-email-correctly-mx-settings%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