Re: weired exchange transport problem
From: Paul Nadeau [MSFT] (pnadeau_at_online.microsoft.com)
Date: 05/06/04
- Next message: Don Young: "Event ID 4283"
- Previous message: Patrick Genova [MSFT]: "Re: weired exchange transport problem"
- In reply to: Dhaval Brahmbhatt: "weired exchange transport problem"
- Next in thread: Kirill S. Palagin: "Re: weired exchange transport problem"
- Reply: Kirill S. Palagin: "Re: weired exchange transport problem"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 6 May 2004 10:44:02 -0400
Hi Dhaval,
If you are using the ISP as a smart host, we will want to use an smtp
connector and not the SMTP virtual server properties for the smart host.
You can enter either the FQDN of the ISP or the IP address in [] . You may
want to check and ensure you are not using ext resolvers on the
Delivery\advanced tab's "External DNS". We work best when you point
Exchange to internal DNS that has forwarders configured out to the external
DNS (Properties of DNS server\forwarders tab).
ETRN is a way to dequeue mail. The ISP would have an smtp mailbag or
container that your smtp mail goes to should your mail server go down. Some
ISPs require a command be sent when the server comes back on line and in the
case of Exchange we use the ETRN command. The ISP would be the place to
start on finding out if they require etrn and if that requirement involves a
specific user name and password. It sounds like the ISP doesn't accept mail
after a certain time and it queues up. The test would be to telnet to port
25 and see if you can connect. The queue that you see the mail queuing up
in means there is no internet connection available at that time. Setting
the connection to USE DNS, will bypass the smart hosting which seems to be a
problem with your ISP because you are able to make direct telnet connections
to the domains you are sending to when DNS queries and responds with an IP
address.
Please review these articles:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;294736
http://support.microsoft.com/default.aspx?scid=KB;EN-US;319426
http://support.microsoft.com/default.aspx?scid=KB;EN-US;153119
-- Regards, Paul Nadeau Microsoft PSS Please do not send email directly to this alias. This alias is for newsgroup purposes only. This posting is provided "AS IS" with no warranties, and confers no rights. "Dhaval Brahmbhatt" <dhaval001@hotmail.com> wrote in message news:eyAk8lvMEHA.624@TK2MSFTNGP11.phx.gbl... > Hello dear friends, > > I am wondering if someone has seen this kind of problem. > > There are 2 main question in this post that I have. > > 1. I have a single server setup, Windows 2000, Exchange 2000 with all > patches. I have configured the SMTP service to use the smart host and smart > host is the mail server of our ISP. So that for all outbound emails, the > server forwards all the emails to our ISP's mail server and our ISP has an > SMTP feed for our domain so all the emails for our domains are being > forwarded to our email server (which is actualled NATed from the firewall). > > is this ideal single server setup or I should use an SMTP connector to send > outbound emials? this is becuase the setup that I described earlier works > fine for me. > > > > 2. The main problem is this. I have just taken over from old administrator > who has left the company and has not left enough documentation for me. He > had configured an SMTP connector and on the General tab, he specified the > ISP's mail server as the smart host and on Advanced tab, he had some > settings relating to the ETURN etc, which I don't understand unfortuntely. > Now the problem we had, which I actually worked around in the end, was that > today after 5 pm, all the outbound emails were being queued, but not going > out. We have default settings on the SMTP server's properties so the delay > notification timeout is 12 hours so the user who sent an email out would > receive an delay notification after 12 hours and the email would time out > after 2 days so after 2 days the email will go to the "undelieverable > emails" queue. But, interestingly, any email that I send from my outlook, > goes from my outbox, but doesn't actually go out, but just goes straight to > the "undelieverable emails" queue. When I looked at the queue at 6 PM, there > were 681 emails which actually timed out and were in the undelieverable > emails queue, including the test email that I sent out from my mailbox at > 5.30 PM. Clearly, those timeouts on the SMTP server's properties are not > working since my email should be in the outbound queue for at least 2 days, > instead, it instantly timed out. I am not sure why this happenes and want to > ask you if anyone has seen this kind of weired problem at all. What the old > administrator told me that this happens quite often that the emails sits in > the outbound queue (not the undelieverable queue) and all I have to do to > resolve this is to restart the SMTP service, which didn't help in this case > where the emails had timed out and gone into the "undelieverable emails" > queue. Please remember that he had this SMTP connector setup. I could telnet > to the smart host from the email server. > > The way I worked it around is by selecting "Use DNS to deliever the emails" > on the SMTP connector instead of the smart host. And then restarted the SMTP > service, and instantly, all the emails went to the outbound quque and after > a while all emails were gone. > > Can please someone give me some suggestions? > > Dhaval > > >
- Next message: Don Young: "Event ID 4283"
- Previous message: Patrick Genova [MSFT]: "Re: weired exchange transport problem"
- In reply to: Dhaval Brahmbhatt: "weired exchange transport problem"
- Next in thread: Kirill S. Palagin: "Re: weired exchange transport problem"
- Reply: Kirill S. Palagin: "Re: weired exchange transport problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
