I'm running Exchange 5.5 SP4, and when users are working remotely they
sometimes get the error message No Transport Provider Was Available.
Microsoft's Q166163 states to do a registry hack, however doesn't cleary
say what it does. Does anyone have any information on this problem or
what this
Have Exchange 5.5 Server on NT 4.0 SP6A, clients are Outlook 98 and also
2000 - problem is occuring with both.
Basically we have users who are trying to send large attachments, in this
example 14mb, to an outside address. The system administrator returns the
message as undeliverable, stating a
D,
That is what I was thinking. How can our users tell that it is coming
from the remote system?
Thanks,
Rob
_
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives:
Okay, so what part of this contains the info I'm looking for?
(This is a test message to an aol address)
Your message did not reach some or all of the intended recipients.
Subject: TEST
Sent: 12/18/01 3:08 PM
The following recipient(s) could not be reached:
'[EMAIL
I would have never guessed...;) Thank you for enlightening me! ;)
_
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe:
Hi,
Running Exchange 5.5 SP3 on NT server. We backup the server nightly using
client agent from InnoculateIT.
Unfortunately one of our users has misplaced or lost a large amount of
mail and it is nowhere to be found. We are curious what restoration
options are available with Exchange as we
Barry
-Original Message-
From: Robert V [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 10:55 AM
To: Exchange Discussions
Subject: Restoration Solutions?
Hi,
Running Exchange 5.5 SP3 on NT server. We backup the server nightly using
client agent from InnoculateIT
7 matches
Mail list logo