I think I found what might be wrong. I checked the differences between a working public folder and a non working one using ADSI Edit. It seems the working one has the HomeMDB set and the others didn't. With Microsoft's help I am rebuilding my RUS and let's hope this takes care of it..
Thanks everyone for your help. Wilson -----Original Message----- From: Varghese, Wilson Sent: Wednesday, February 20, 2002 11:46 AM To: Exchange Discussions Subject: RE: Help with mail enabled Public folder Well they all seem to have the right permissions... I did discover something though. Only people that are having problems are the Exchange 2000 users. Exchange 5.5 users can send emails to public folders with no problem. Then 15 minutes later you see it replicated into the Exchange 2000 server. So this is where we are: 1. Exchange 5.5 users have no problem. (interesting though that since the folder is homed on the 2k server, it still goes to the 5.5 server then gets replicated to 2k. 2. Exchange 2k users can't send to public folders 3. Both 5.5 and 2k users can send to any new folders we create. Does this info help a bit? Thanks in advance Wilson -----Original Message----- From: Varghese, Wilson Sent: Wednesday, February 20, 2002 10:51 AM To: Exchange Discussions Subject: RE: Help with mail enabled Public folder Great thanks, Walt. I will check into this on my site and let everyone know if this worked. Wilson -----Original Message----- From: Walt Brannon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 4:04 AM To: Exchange Discussions Subject: RE: Help with mail enabled Public folder Wilson is alleged to have written: What I want to know is why the internal users are getting NDRs when the external clients can send to it fine. Please any info you have would be great. I have checked technet and support and can't find this error referenced anywhere. Thank you, Wilson Walt Replies: We had the exact same issue with Exchange 2000. External mail to PF was good. Internal = NDR, but only for SOME users. With us it turned out to be an over zealous Domain Admin that had broken inheritance in many places in Active Directory, and removed the Enterprise Exchange ACE. The Enterprise Exchange security group did not have permissions to all objects. Specifically: Every SG that a user is a member of, MUST have the Enterprise Exchange group ACE on that object. If not, all members of that group are affected. Walt Brannon University of New Orleans [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
