After sending a mail from a workstation thats conected to the exchanage server, i recived this bounce message > The following recipient(s) could not be reached: > > on 29/10/2007 10:43 > 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. > < #5.2.0 smtp;550 5.2.0 STOREDRV.Deliver: The > Microsoft Exchange Information Store service reported an error. The > following information should help identify the cause of this error: > "MapiExceptionNoAccess:16.18969:69000000, > 17.27161:000000007C000000000000000F00000000000000, 255.23226:00000000, > 255.27962:7A000000, 255.27962:56000000, 255.17082:05000780, > 0.16993:80030400, 4.21921:05000780, 255.27962:FA000000, > 255.1494:15000000, 255.26426:56000000, 4.6363:0F010480, > 2.31229:00000000, 4.1091:05000780, 4.4603:05000780, 4.5323:05000780, > 255.1750:0F010480, 0.26849:2D000000, 255.21817:05000780, > 0.24529:0F280000, 4.18385:05000780".> the exchange server dose have the service pack 1 (beta) installed on it and i was wondering if that or anything else was causing the problem Thanks

Are both users internal? Does it work with OWA to OWA? try running system health checks and mailflow analyzer. Running beta in production enviroments ruins the spirit of beta software and hurts us all.

I found the solution to my own problem thankfully. All it was, was the permissions for the everyone group on ORG level was incorrect. So I added permission entries for everyone having special rights (Allow only List contents, Read All Properties and Read Permissions) for msExchprivateMDB and msExchpublicMDB objects respectively. Also I edited the named properties in the information store, and for public folder and under "Apply onto" selected "This object and all child objects" Running beta in production environments is the way forward as it highlights all the problems in the software, which is the true spirit of beta software and enlightens us all.