RE: Email issue

  • From: "Matthew Martin" <mmartin@xxxxxxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 30 Aug 2002 12:36:18 +1000

Thankyou for that, the problem has been resolved.
 
Matt
 
-----Original Message-----
From: Soo, Bee Yong [mailto:by.soo@xxxxxxxxxxxxx] 
Sent: Friday, 30 August 2002 10:45 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Email issue
 
http://www.MSExchange.org/
The restriction has either been set on sender or the recipient mailbox.
 
Regards, 
Bee-Yong 
-----Original Message-----
From: Matthew Martin [mailto:mmartin@xxxxxxxxxxxxxxx] 
Sent: Friday, 30 August 2002 10:28 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Email issue
 
http://www.MSExchange.org/
Hello Listmembers,
 
The below error message was generated after sending the original message
to an external 
Recipient. 
 
 
Your message did not reach some or all of the intended recipients.
 
      Subject:             Meeting follow-up 
      Sent: 29/08/2002 10:59 AM
 
The following recipient(s) could not be reached:
 
      ' (x@xxxxxxxx)' on 29/08/2002 10:59 AM
            You do not have permission to send to this recipient.  For
assistance, contact your system administrator.
            <server1.x.au #5.7.1>
 
 
Would someone be able to explain why this may be? Any help would be
appreciated. 
Thanks in advance.
 
Matt.                                
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
by.soo@xxxxxxxxxxxxx
To unsubscribe send a blank email to
$subst('Email.Unsub') 
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
matthewm@xxxxxxxx
To unsubscribe send a blank email to
$subst('Email.Unsub') 



THIS E-MAIL IS CONFIDENTIAL. If you have received this e-mail in error,
please notify us by return e-mail and delete the document. If you are
not the intended recipient you are hereby notified that any disclosure,
copying, distribution or taking any action in reliance on the contents
of this information is strictly prohibited and may be unlawful. Bayside
Health is not liable for the proper and complete transmission of the
information contained in this communication or for any delay in its
receipt.

Other related posts: