Re: Email Server was down - Actual Problem is below Please help

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


Hello MoiToo
Thanks so much, I am sure that would have fixed our problem kind of.
Because when I updated everyone on Outlook Client from SP1 to SP3 it fixed
the external problem. So I could of changed the receipient policy. I may
still do this to always ensure this works.
However, the actual problem I found was with out network card we had two in
the pc.
1 would make the pc go very slow and take forever and nothing would open up,
but when it booted I could ping the pc from remote branches.
2. the 2nd card the pc appeared to be working fine I could ping the card
internally, but I did not realize our branches could not ping this server.

So I took out both Intel cards replaced with a 3com and the pc appears to be
working great like card #2 but also able to ping remote branches and web like
card 1.
Mail is flowing great again. :-)
Thanks for your help. Sorry for the nework card confusion it was weird how
all internal could ping fine and the card was setup ok. I think I am going
to buy more ethernet cards and have on hand as these are crucially important.
We are about out.
Thanks again and I will probably change our receipient to our external just
to eliminate the stuggles for our Outlook client users in case this happens
again.

Thanks
Dan


"Dan" wrote:

> Hello MoiToo,
> Thank you so much, You are right on every account, but I am still not
> exactly sure what to do or what I need to get from my external ISP.
>
> > When you send an external email from an outlook client
> > (user@xxxxxxxxxxxxxxxxxxxxxx), it goes via the exchange server to the real
> > world
>
> **** This is the problem now. I can make this work everytime so yeah. I
> can say that for sure. When I send out through outlook client my email go to
> real world. So Yes. I am not sure if the Exchange server is truly validating
> these or I truly believe these are going straight out through the pop account
> from our isp that I have on the Outlook client pc. So if Exchange server is
> not in the middle I know they go out for sure without a doubt.
>
> > When you send an internal email from an outlook client
> > (user@xxxxxxxxxxxxxxxxxx), it, as you would expect, is sent via the exchange
> > server for direct delivery
> *** Again this is correct perfect these deliver everytime ok no hold time
> even in queue instantly perfect.
>
> > If this is correct, can you please confirm the senders address in the
> > individual emails (i.e. user@xxxxxxxxxxxxxxxxxxxxxx or
> > user@xxxxxxxxxxxxxxxxxx)? You should do this from the queues page in ESM.
>
> The address *** Main Problem*** that is always being held in the queue now
> is the user@xxxxxxxxxxxxxxxxxx when trying to go out to an external domain.
> Such as via owa or we have some internal jobs that sole purpose is to send
> email from the user@xxxxxxxxxxxxxxxxxx to user(s)@externaldomain.com
> What is the best solution to fix this problem? I appreciate the help so much.
>
> I believe we have the clients pointing to their servers that is why the
> outlook clients are ok. I saw the smarthost text box. Would this be the IP
> of our ISP mail server or do I have to ask them for this? Can they tell me?
> Now doing this do I have to give anything of my server to the ISP? Do I need
> to open up any ports or anything, because this is really not an option. I
> can ping our mail.external.com server from our internal box if this helps?
>
> > Your mail provider should allow you to relay through their servers, in which
> > case you just point the outlook clients at their server, or the SMTP Virtual
> > Server in exchange to smarthost through their server.
> >
> > My locic for all of this is that the receiving servers are doing a reverse
> > lookup, which will not resolve for an internal domain name. This was only
> > my imediate reaction - it could be way off the mark!
>
> Do you mean receiving servers at their end. The reason I ask is I have not
> set them up anywhere on my server. My exchange server is strictly internal
> at this time. I think you are exactly correct and right on. I am just not
> sure why it was working before where our user@xxxxxxxxxxxxxxxxxx could send
> out. Just no one could reply because that would be of course
> user@xxxxxxxxxxxxxxxxxxx So is there away I can get this back or a better
> way to set this up as you mentioned. Relay with our ISP/POP3 mail or adding
> them as a smarthost?
>
> I am a little confused about the MX. I don't have to set up an mx to them or
> anything? The only MX I have is our domain controller to our exchanger server.
>
> I appreciate all the help.
> Thanks so much.
> Dan
>
> >
> > "Dan" <Dan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:635FBEA5-0214-4EDF-A77B-02D4B387D52E@xxxxxxxxxxxxxxxx
> > > Hello Everyone, thanks for the previous post, but I actually have the
> > > problem
> > > identified now so hopefully someone can give me the best solution. I am
> > > not
> > > sure why it was working before but now I would like to get the best
> > > solution
> > > in setting up our exchange server.
> > >
> > > Background: Simple company 1 domain on win2k server and 1 exchange 2000 on
> > > win2k server. We use the exchange server for all internal email. We
> > > have
> > > about 20 POP3 accounts which users use for external email. Basically we
> > > set
> > > up through outlook on their desktop to handle the pop3 from the internetl.
> > > We add the exchange server for their local email account. Our other users
> > > use OWA to send email only internally. Before our server went down things
> > > were great. Now it is all back up but one problem.
> > >
> > > Exchange confiiguration - we do not use imap or pop3. Only the smtp
> > > protocol.
> > >
> > > Problem:
> > > I am seeing remote external queues building up. Basically what happens
> > > is
> > > when an owa client sends an email to an external address now it goes in
> > > this
> > > queue. When I send an ndr back it gives the 4.3.2 error about administive
> > > policy. I can give the exact error on Monday when I am at work. Also a
> > > few
> > > of our outlook clients are now as well building up in this queue. I know
> > > how
> > > to fix the outlook client issue. However, I would like anyone with an
> > > external pop3 account who uses outlook to be able to send externally
> > > without
> > > being held in the smtp queue on exchange with their local address. Again
> > > this was working before but maybe incorrectly.
> > >
> > > Solution:
> > > I am open to any ideas and suggestions, but I need to keep our exchange as
> > > only for internal smtp messages. I do not want pop3 or mapi on our
> > > exchange
> > > yet anways. I was wondering is there away to tie our pop3 mail that we
> > > are
> > > using for the 20 external accounts to our exchange server so atleast we
> > > can
> > > send out thorough that. Would our pop3 company have any problem in giving
> > > me
> > > their mail relay or so that i could add to my server so we could send out
> > > externally again or the correct way? I do have an mx record on our main
> > > domain server that gives us dhcp and dns pointing to our mail server with
> > > a
> > > priority of 10. However, I am not sure if I can set something up with our
> > > pop3 isp that handles our 20 accounts or if I can do something on my own
> > > with
> > > out them to be able to send externally of course always without holding in
> > > the queue? So basically the only problem again is when we are sending a
> > > remote message from our smtp local queue it always holds.
> > >
> > > Thanks for reading this case scenario kind of. I am sorry for the long
> > > email, but I wanted to cover everything so I can get this up as quick as
> > > possible with the best solution. I appreciate all help.
> > > Thanks
> > > Dan
> >
> >
> >
.

Relevant Pages