B
bzysblat
We were running about 30 work stations off Exchange Server 5.5 and NT
4.0. We recently switched to a 3rd party hosted POP3 mail service.
There was no problem adding the POP3 email account to everyone's
Outlook and setting it as the default. There was also no problem moving
the company's DNS to the 3rd party provider. We had no problem
designating the old inbox to be the location new mail is deposited, so
the programs occasionally worked well together.
However, we immediately had both send and receive problems. Sent mail
was not always getting to the delivery location and people were getting
bounce-back sending mail to us. Inter-office mail did not work between
some individuals. When we removed the Exchange server from everyone's
Outlook, things worked perfectly. But, of course, no one was able to
see their old mail file folders. When we added the Exchange Server back
to the email accounts in Outlook, Outlook would begin to act
erratically again. It would often try to send mail thru the old server
in spite of the fact that it was not the default. We also removed the
Exchange Server as a send/receive option in Outlook, but that didn't
help. Many other mail problems also developed. When it was removed
again, everything worked fine again.
I know we can export everyone's folders to their local drive, but
then we are unable to back them up every night and Outlook will not
find them if you work remotely. Remote access to our folders is
important to us.
I'm looking for a way our Exchange Server can continue to hold and
file mail but not send or receive and not try to take over the process
when mailboxes are added to Outlook. Is their either a service in
Exchange that I can shut down or a setting in each users Outlook that
will accomplish this?
We did try stopping or pausing many of the Exchange services. In every
case, either Outlook did not see the machine (the server and its
folders) or, if it did, the mail problems came back.
Any ideas or suggestions would be greatly appreciated.
4.0. We recently switched to a 3rd party hosted POP3 mail service.
There was no problem adding the POP3 email account to everyone's
Outlook and setting it as the default. There was also no problem moving
the company's DNS to the 3rd party provider. We had no problem
designating the old inbox to be the location new mail is deposited, so
the programs occasionally worked well together.
However, we immediately had both send and receive problems. Sent mail
was not always getting to the delivery location and people were getting
bounce-back sending mail to us. Inter-office mail did not work between
some individuals. When we removed the Exchange server from everyone's
Outlook, things worked perfectly. But, of course, no one was able to
see their old mail file folders. When we added the Exchange Server back
to the email accounts in Outlook, Outlook would begin to act
erratically again. It would often try to send mail thru the old server
in spite of the fact that it was not the default. We also removed the
Exchange Server as a send/receive option in Outlook, but that didn't
help. Many other mail problems also developed. When it was removed
again, everything worked fine again.
I know we can export everyone's folders to their local drive, but
then we are unable to back them up every night and Outlook will not
find them if you work remotely. Remote access to our folders is
important to us.
I'm looking for a way our Exchange Server can continue to hold and
file mail but not send or receive and not try to take over the process
when mailboxes are added to Outlook. Is their either a service in
Exchange that I can shut down or a setting in each users Outlook that
will accomplish this?
We did try stopping or pausing many of the Exchange services. In every
case, either Outlook did not see the machine (the server and its
folders) or, if it did, the mail problems came back.
Any ideas or suggestions would be greatly appreciated.