Recipient unable to accept calendar meeting appointment.

[Marcus]

Hi,

When sending out appointments for the meeting room the recipients receive
the appointment but are unable to accept it.

When trying to accept the appointment it is giving the following error
message:

"You do not have permission to send to the recipient."

Thanks,

PS

 

[Marcus]

I'm still trying to configure this for my client since I don't know much
about Outlook. They basically have a meeting room added to their calendar &
they can arrange meetings for it.

But when the user tries to accept the meeting, 20 seconds later they get
this error message that comes back to the receivers inbox:

Your message did not reach some or all of the intended recipients.

Subject: Accepted: Testing Megalong Appointment Response - Debby S.
Sent: 26/02/2008 9:54 AM

The following recipient(s) could not be reached:

Megalong_BW on 26/02/2008 9:54 AM
You do not have permission to send to this recipient. For
assistance, contact your system administrator.
<HWEP.xX.EA.Xxcom.au #5.7.1>

***********************************************************************************************************

The error # above relates to these notes below:

• Numeric Code: 5.7.1

Possible Causes:
• General access denied, sender access denied - the sender of the message
does not have the privileges required to complete delivery.
• You are trying to relay your mail through another SMTP server and it does
not permit you to relay.
• The recipient might have mailbox delivery restrictions enabled. For
example, a recipient's mailbox delivery restriction was set to receive from a
Distribution List only and non-members' email will be rejected with this
error.
• For Exchange Server 2003, a distribution list can be configured to
restrict mail delivery from unauthenticated users. Mail that is sent by using
an unauthenticated SMTP session are rejected.

Troubleshooting: Check system privileges and attributes for the contact and
retry the message. Also, make sure you are running Exchange 2000 Service Pack
1 or later for other potential known issues.