• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 759
  • Last Modified:

Cannot send an invite to a calendar located in Public Folders

I have created a mail enabled Calendar under Public Folders. All users who need to make entries have been given Owner permissions. Some users are creating appointments and inviting CompanyCalendar@DomainName.com and appointments are being created in the mail enabled Calendar. Others are unable to with the following error:-

Your message did not reach some or all of the intended recipients. Subject: test hi Sent: 08/02/2008 09:54 The following recipient(s) could not be reached:

  MCM - Calendar on 08/02/2008 09:54
  The message reached the recipient's e-mail system, but delivery was refused. Attempt to resend the message. If it still fails, contact your system administrator.
  <servername.domain.com #5.2.1>

I have deleted the calendar and recreated it. I have recreated one of these users account/profile on another machine but am still getting this problem. We are running Exchange 2003 SP2 on Win2K3 SP2.
The clients are running XP SP2 with Office 2003 SP3.
0
macuma
Asked:
macuma
  • 4
  • 2
1 Solution
 
dlan75Commented:
Hi,
Your users do not only need owner rights but they also neet to have the delegation of the mailbox in order to add appointments.
0
 
macumaAuthor Commented:
Thanks for the quick response. This is not a mailbox. It is a mail enabled folder. I have given the users full control on the directory rights via Exchange System Manager and this is still not working.
What I can't understand is that I have not done any additional configuration for the users that are working other than make them an Owner on the folder/calendar.
0
 
dlan75Commented:
Hi,
To create a shared calendar I think you have to create a mailbox and delegate its control to your users.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
macumaAuthor Commented:
You don't need to create a mailbox as I already have this working with several users. It's certain users that are getting this smtp 5.2.1 error.
0
 
TrialWorksCommented:
Service Pack 2 for exchange is supposed to fix the issue. Moreover, there is a hotfix for it as well for pre and post SP1.  I have XCH2003 sp2 installed and just started having the same issue.  I have not tried getting and installing the hotfix on the machine yet - I doubt it will install.
0
 
macumaAuthor Commented:
We have just installed an Exchange 2007 server in the organization. We are currently in a coexistence state. We are still having the same problem. All the mailboxes have been moved over to 2007 and the Public Folder replication has been moved as well as the RUS. We have just got to remove our connectors so that the Exchange 2003 box can be decommissioned. I will let you know if this is still a problem when we are in just an Exchange 2007 environment.
0
 
macumaAuthor Commented:
Exchange 2003 removed. Exchange 2007 on SP1. All clients running Outlook 2007 SP1.

Problem resolved.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now