Re: Unable to Receive Email from the internet

On May 1, 12:29 pm, hooutoo <hoou...@xxxxxxxxx> wrote:
On May 1, 12:08 pm, "Bharat Suneja [MVP]" <bha...@xxxxxxxxxx> wrote:





http://www.dnsstuff.com/

Scroll to the bottom, enter email address in E-mail Test
--
Bharat Suneja
MVP - Exchangewww.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------

"hooutoo" <hoou...@xxxxxxxxx> wrote in message

news:1178033956.752212.284400@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

On May 1, 9:43 am, "Bharat Suneja [MVP]" <bha...@xxxxxxxxxx> wrote:
I've now added a send connector for the internet and am able to send
email to a yahoo account. I'm very close at this point! I just need to
get inbound email running!

1) Is your server reachable from the internet on SMTP port (tcp port 25)?
Test from outside your firewall:
telnet x.x.x.x 25
(x.x.x.x is the external IP address of your server).
- Most firewalls allow you to map an internal IP address to an external
one - known as Network Address Translation (NAT), and allow inbound SMTP
traffic to ther server - requires creating an access rule on the
firewall.

2) External DNS Zone:
- Need an A record that maps the external FQDN of the server (e.g.
exchange.yourdomain.com) to the external IP address.
- A MX record that points to the above A record.
To test - from outside your firewall:
nslookup -type=MX yourdomain.com
--
Bharat Suneja
MVP - Exchangewww.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------

"hooutoo" <hoou...@xxxxxxxxx> wrote in message

news:1177956887.626985.310030@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

On Apr 30, 1:55 pm, hooutoo <hoou...@xxxxxxxxx> wrote:
On Apr 30, 11:14 am, "Bharat Suneja [MVP]" <bha...@xxxxxxxxxx> wrote:

This may help:
Exchange Server 2007: internet email without Edge
servershttp://exchangepedia.com/blog/2006/07/exchange-server-2007-internet-e...

--
Bharat Suneja
MVP - Exchangewww.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------

"hooutoo" <hoou...@xxxxxxxxx> wrote in message

news:1177943113.919647.165450@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Please bear with me as I'm fairly inexperienced with Exchange.
I've
just installed Exchange 2007 on a new install of Longhorn Server
Beta3. It seemed to install fairly clean. I've create a couple of
mailboxes for two domain admin users and am able to email between
the
two locally. The problem is I'm unable to email to the internet,
example - x...@xxxxxxxxx, or receive any email from the outside.

Any suggestion would be greatly appreciate on where to start.

Thanks in advance

Steve- Hide quoted text -

- Show quoted text -

Bharat.. Thanks for the tip. I'm now able to telnet to port 25 with
"telnet mail.myserver.com 25". Below are the results and as you can
see I'm running into a RELAY problem.
===============================================================
telnet mail.myserver.com 25

220 server.myserver.local Microsoft ESMTP MAIL Service ready at Mon,
30 Apr
2007 13:19:19 -0400
helo server.myserver.local
250 server.myserver.local Hello [70.88.39.141]
mail from:s...@xxxxxxxxxxxx
250 2.1.0 Sender OK
rcpt to:shol...@xxxxxxxxxxxx
550 5.7.1 Unable to relay
=================================================================

I've googled "550 5.7.1 Unable to relay" and now beleive there is some
sort of policy problem and exchange is therefore unable to relay to
the Recipent. I'm just wonder is this has something to do with
relaying from "s...@xxxxxxxxxxxx" to "s...@xxxxxxxxxxxxxx". Or/and
do I need and internal relay domain.

Again, any suggestions would be helpfull.
Steve- Hide quoted text -

- Show quoted text -

I've now added a send connector for the internet and am able to send
email to a yahoo account. I'm very close at this point! I just need to
get inbound email running!

Steve- Hide quoted text -

- Show quoted text -

I'm now able to use "telnet mail.mydomain.com 25" from behind the
firewall to send a message to u...@xxxxxxxxxxxxx So telnet is
resolving the address for mail.mydomain.com via dns at godaddy which
is who I use. I'm unable to try it outside the firewall as I don't
have access to a computer on the outside. I'm thinking now your
suggestion of a firewall problem is looking pretty accurate. I'm
looking at the firewall inbound rules on my LHS. Do you know of any
other way to check this?

Steve- Hide quoted text -

- Show quoted text -

I already tried the dnsstuff and got a timeout error message.

Trying to connect to all mailservers:

mail.mydomain.com. - xx.xx.xx.141 [Could not connect: Could not
receive data: Operation timed out.]
[Note that if your mailserver takes over 30 seconds to respond, our
test will timeout, even though real mailservers will wait longer]

I was also able to test with telnet out my firewall an got the
message;

421 Cannot connect to SMTP server xx.xx.xx.141 (xx.xx.xx.141:25),
connect error 10060

????????????????????
Steve- Hide quoted text -

- Show quoted text -

Bharat

At this point I'm convinced that it's firewall problem. LHS uses
Windows Firewall with Advanced services. After much googling and
reading I'm pretty sure I need a complete set of inbound rules for
Exchange 2007. I ran a security config wizard (scw) and low and behold
I had new set of inbound rules for Exchange. The problem was it left
out all of my other rules and of course then my whole system would be
shot. I guess now I just need to enter the specific inbound rules in
WF for Exchange. Do you have a set?

Steve

.

Relevant Pages

  • Re: Unable to Receive Email from the internet
    ... Are you running this on Longhorn server? ... Test from outside your firewall: ... Exchange Server 2007: internet email without Edge ... looking at the firewall inbound rules on my LHS. ...
    (microsoft.public.exchange.setup)
  • Re: Install Exchange 2003 new hard ware
    ... You could do that as well, after you retire your old server. ... simply add additional entries in external DNS and firewall to allow new ... server to receive inbound email, *before I shut down/remove old server*. ... MVP - Exchange ...
    (microsoft.public.exchange.setup)
  • Re: Few question regarding SBS setup
    ... I am confused RE the setup...So you have 1 inbound box for the whole ... It sounds like you would need Outlook ... outbound SMTP server would be your ISP's mail server. ... the POP3 connector in Exchange. ...
    (microsoft.public.windows.server.sbs)
  • Re: Microsoft update asking for security change - SP 2 firewall operation
    ... the firewall is still an inbound-only blocker. ... inbound traffic must be a response to something that previously went out. ... * For outbound TCP, inbound replies must come from the target IP address ... When the application binds to a socket, whatever port the ...
    (microsoft.public.security)
  • Re: Networking over mains cables
    ... 'inbound and outbound, only if initiated by me' and ... the firewall so a webserver needs to allow inbound HTTP ... In this context the ports are conceptual. ...
    (comp.sys.acorn.networking)
Loading