|
Home > Archive > IIS and SMTP > April 2006 > Some email relies Smart Host to deliver
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Some email relies Smart Host to deliver
|
|
|
| Hi;
My internal SMTP server is configured on one of three W2K Active Directory
domain controllers server, I found that if I do not use Smart Host; some
email cannot be delivered. For example; if my user want to send an email to
a recipient at "hotmail.com" and "sympatico.ca", etc. The email always sits
on the queue until I instruct it to send via my Smart Host in DMZ network.
Here is the ip configuration of all my server.
DC1
IP: 192.168.0.1
Primary DNS : 192.168.0.2
Secondary DNS : 192.168.0.3
DC2
IP: 192.168.0.2
Primary DNS : 192.168.0.1
Secondary DNS : 192.168.0.3
DC3
IP: 192.168.0.3
Primary DNS : 192.168.0.1
Secondary DNS : 192.168.0.2
Where DC3 is my internal SMTP server.
Smart Host in DMZ
IP : 64.x.x.1
Primary DNS : 127.0.0.1
* My Smart Host is also a DNS server itself.
I think, I can email to 80% of other domain.
When I reviewed the EventViewer, I also found these warning..
"Message delivery to the remote domain 'sympatico.ca' failed for the
following reason: The connection was dropped by the remote host"
"Message delivery to the remote domain 'hotmail.com' failed for the
following reason: The connection was dropped by the remote host"
I also tried to use the DNS servers ip address as the Primary DNS and the
Secondary DNS on DC3 but still no help, because I thought, would it be the
DNS problem.
Any idea?
Thanks!
| |
| Christopher Reed 2006-04-11, 9:52 am |
| Try using 127.0.0.1 as the smart host. If you do not have any ports block
going outside, it should work.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."
"Kane" <kane@worldwarranty.com> wrote in message
news:u3ewBWZWGHA.196@TK2MSFTNGP04.phx.gbl...
> Hi;
>
> My internal SMTP server is configured on one of three W2K Active Directory
> domain controllers server, I found that if I do not use Smart Host; some
> email cannot be delivered. For example; if my user want to send an email
> to a recipient at "hotmail.com" and "sympatico.ca", etc. The email always
> sits on the queue until I instruct it to send via my Smart Host in DMZ
> network. Here is the ip configuration of all my server.
>
> DC1
> IP: 192.168.0.1
> Primary DNS : 192.168.0.2
> Secondary DNS : 192.168.0.3
>
> DC2
> IP: 192.168.0.2
> Primary DNS : 192.168.0.1
> Secondary DNS : 192.168.0.3
>
> DC3
> IP: 192.168.0.3
> Primary DNS : 192.168.0.1
> Secondary DNS : 192.168.0.2
>
> Where DC3 is my internal SMTP server.
>
> Smart Host in DMZ
>
> IP : 64.x.x.1
> Primary DNS : 127.0.0.1
>
> * My Smart Host is also a DNS server itself.
>
> I think, I can email to 80% of other domain.
>
> When I reviewed the EventViewer, I also found these warning..
>
> "Message delivery to the remote domain 'sympatico.ca' failed for the
> following reason: The connection was dropped by the remote host"
>
> "Message delivery to the remote domain 'hotmail.com' failed for the
> following reason: The connection was dropped by the remote host"
>
> I also tried to use the DNS servers ip address as the Primary DNS and the
> Secondary DNS on DC3 but still no help, because I thought, would it be the
> DNS problem.
>
> Any idea?
>
> Thanks!
>
| |
|
| Hi Chris;
thanks for your suggestion but it is still not working after applied your
recommendation, even though, I open a NAT to this internal server from
firewall.
"Christopher Reed" <carttu@nospam.nospam> wrote in message
news:eMVXBrwWGHA.3848@TK2MSFTNGP05.phx.gbl...
> Try using 127.0.0.1 as the smart host. If you do not have any ports block
> going outside, it should work.
> --
> Christopher A. Reed
> "The oxen are slow, but the earth is patient."
>
> "Kane" <kane@worldwarranty.com> wrote in message
> news:u3ewBWZWGHA.196@TK2MSFTNGP04.phx.gbl...
>
>
| |
| Christopher Reed 2006-04-27, 7:52 am |
| Some of these mail recipients will either reject your message or have to go
through a drawn out process to "okay" your message. It is probably the
later that you are seeing. We had a problem with this. To resolve, make
sure that the From address is either your main domain name or your mail
domain name, even though it's not coming from either.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."
"Kane" <kane@worldwarranty.com> wrote in message
news:ekQ7nuOXGHA.4620@TK2MSFTNGP04.phx.gbl...
> Hi Chris;
>
> thanks for your suggestion but it is still not working after applied your
> recommendation, even though, I open a NAT to this internal server from
> firewall.
>
>
> "Christopher Reed" <carttu@nospam.nospam> wrote in message
> news:eMVXBrwWGHA.3848@TK2MSFTNGP05.phx.gbl...
>
>
|
|
|
|
|