-----Original Message-----
From: Thomas T. Evans,III <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Wednesday, October 29, 1997 1:49 PM
Subject: off topic - novell and ms outlook


You have received the great Microsoft "Catch-All" message from Outlook and
Exchange...  It could be one of a number of problems, most likely UNrelated
to attachments.... see below:

>Your message did not reach some or all of the intended recipients.
>
>      Subject:  attachment - txt
>      Sent:     10/29/97 10:20 AM
>
>The following recipient(s) could not be reached:
>
>      [log in to unmask] on 10/29/97 10:23 AM
>            No transport provider was available for delivery to this
>recipient.


1.  The most likely cause is that your SMTP server, which is receiving the
message from your client, is not responding in the way Outlook is expecting.
We have found that Outlook has problems  with several SMTP servers, where
other mail clients would not.  The test here is to try another client such
as Outlook Express, Pegasus 32 for Windows or Eurdora.  If any of these
work, especially Pegasus or Eudora, then it's the client, and I would change
it.

2.  You do not have a TCP/IP stack running or it's failing, another common
cause.  The test?  Open an MS-DOS box and enter:  PING 127.0.0.1   If you
get an ICMP echo, you should be OK.  To double-check, get an IP address of
another PC, or your 3000, and PING it.  If you get ICMP echos back, TCP/IP
is running...

3.  Firewalls:  Do you have one between your client and the SMTP server?  If
you do, ensure that ports 25 and 110 are open through the firewall.  This
too, is a common mistake, where the SMTP server is placed outside the
firewall to completely protect the insides, but then the ports are not
opened to allow mail traffic to pass.

4.  Lastly - traffic timeouts.  If network traffic is particularly heavy,
and the server times out too soon, then you will get this problem.  PING
your SMTP server...and if the response time of the ICMP echo is high (the
higher the number of milliseconds, the slower the response), then this could
be your problem.  Normal response of a reasonably configured server on a
10mb LAN should be in the 10ms to 50 ms range, although it could be 100ms on
occasion.

Hopefully, this helps...  Good Luck.

Joe

Joe Geiser - CSI Business Solutions, LLC
** Your Client-Server and Internetworking Specialists
140 Bristol-Oxford Valley Road, Suite 102
Langhorne, PA  19047-3083, USA
Phone: +1 215.945.8100   Fax: +1 215.943-8408
[log in to unmask]            http://www.csillc.com