Skip to main content
Super User

Return to Answer

added 17 characters in body
Source Link
Peter Mortensen
Peter Mortensen
  • 12.2k
  • 23
  • 72
  • 90

First, that IP address itself is not going to be listed as a DNS MX record (even if you used the mail server's correct IP address), as the others said, so it is not going to find the server in the first place (it is also not going to route based on that IP address as the @thedomain@thedomain is just used for lookups). Even if you used telnet to connect to the server directly (this is how experts test email directly) directly, it would still fail for the following reason:

Whenever I configure a mail system, and I do a lot of them, with Microsoft Exchange or others, you always have to tell it what are the domains it will accept. I always enter @thedomain.com@thedomain.com, which means it will only accept emails for that domain. Since @74.125.235.55@74.125.235.55 is not a domain, and certainly not in the accepted domains list, even if you were directly connected to the mail server, it will still reject it.

First, that IP itself is not going to be listed as a DNS MX record (even if you used the mail server's correct IP address), as the others said, so it is not going to find the server in the first place (it is also not going to route based on that IP address as the @thedomain is just used for lookups). Even if you used telnet to connect to the server (this is how experts test email directly) directly it would still fail for the following reason:

Whenever I configure a mail system, and I do a lot of them, with Microsoft Exchange or others, you always have to tell it what are the domains it will accept. I always enter @thedomain.com, which means it will only accept emails for that domain. Since @74.125.235.55 is not a domain, and certainly not in the accepted domains list, even if you were directly connected to the mail server, it will still reject it.

First, that IP address itself is not going to be listed as a DNS MX record (even if you used the mail server's correct IP address), as the others said, so it is not going to find the server in the first place (it is also not going to route based on that IP address as the @thedomain is just used for lookups). Even if you used telnet to connect to the server directly (this is how experts test email directly), it would still fail for the following reason:

Whenever I configure a mail system, and I do a lot of them, with Microsoft Exchange or others, you always have to tell it what are the domains it will accept. I always enter @thedomain.com, which means it will only accept emails for that domain. Since @74.125.235.55 is not a domain, and certainly not in the accepted domains list, even if you were directly connected to the mail server, it will still reject it.

Source Link
KCotreau
KCotreau
  • 25.5k
  • 6
  • 49
  • 72

First, that IP itself is not going to be listed as a DNS MX record (even if you used the mail server's correct IP address), as the others said, so it is not going to find the server in the first place (it is also not going to route based on that IP address as the @thedomain is just used for lookups). Even if you used telnet to connect to the server (this is how experts test email directly) directly it would still fail for the following reason:

Whenever I configure a mail system, and I do a lot of them, with Microsoft Exchange or others, you always have to tell it what are the domains it will accept. I always enter @thedomain.com, which means it will only accept emails for that domain. Since @74.125.235.55 is not a domain, and certainly not in the accepted domains list, even if you were directly connected to the mail server, it will still reject it.