Public Folder Email Bounces from Primary Email Address
Hi, I have created and email enabled a public folder. It has 2 email addresses (from Default policy). The Primary email address won't work, emails bounce back with the following message: Your message did not reach some or all of the intended recipients. Subject: test Sent: 06/08/2007 11:46 The following recipient(s) could not be reached: xxxxxon 06/08/2007 11:46 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <intsalexch01.server1.com #5.1.1> The public folder recieves to the secondary email address fine. However i need users to be able to send from this folder so i need to have the primary address working. I have deleted the folder and recreated it, without any luck. Any pointers on this issue would be most appreciated. Many Thanks Mike
August 6th, 2007 1:53pm

Mike, Have you double checked the obvious, like the spelling on both the addresses and when typing it to send to it. And when you are sending, are you manually typing the address to send to it, or are you picking it from the Global Address List? And if you are seeing it in the GAL, if you look at the properties of it does it show the email addresses as you expect to see them? If you've been through all that, then one thing youmay want to try is a manual approach with the folder's email address... Go into the properties of the public folder. Tell it not to automatically update based on recipient policy. Then delete the primary address, create a new address, and set that one back to primary. Depending on the size of your AD infrastructure, you may need to let replication finish, then try sending to it again. Obviously there should be no issue with having multiple addresses for a folder, so hopefully there is something minor that is throwing this off for you. Hope this helps. Lee
Free Windows Admin Tool Kit Click here and download it now
August 6th, 2007 11:16pm

Hi, Sorry for the delay. It has been discovered to the pre-SP1 Exchange Installation permissions problem (where exchange server group was added to admin group then removed an hour later). I have a micosoft support company having a look at this so i am going to close this now. Many Thanks forall your help. Mike
August 8th, 2007 1:55pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics