Emailing Public Folders

[jemckinney]

I have two exchange 2003 servers which share a public folder store on exch1. The issue is I have a public folder set up to accept email. All users on exch1 where the public folder resides can email the pf just fine. However, users on exch2 are unable to send this public folder emails. The email they send sits in the exch2 local delivery queue. If I delete the email and tell it to send an NDR, the users receives this:


This message was rejected due to the current administrative policy by the destination server. Please retry at a later time. If that fails, contact your system administrator

I have checked to ensure I have no policies set, DNS is correct with MX records and pointer records for both servers. Public folder referals are set to routing groups. Both servers are part of the same site and routing group. I have no clue why this is happening. Anyone else seen this before or have any idea of what I may check?

TIA!

 

[jmorr34]

I am currently trying to find out how to email a Public Folder from an external email. Hopefully someones answer can lead me closer to finding out how. My message gets stuck in the Queue on my Front End exchange server.

 

[ntinlin]

jmorr34, I presume firstly that you have mail enabled the public folder in question and that RUS has stamped it with an e-mail address.


Make sure that anonymous has contributor rights to the PF. If it doesn't then no mail will be received. This is different from XC5.5 which let anything in.

Neill

 

[jmorr34]

ntinlin,

yes the PF has been mail enabled, it has an email address, and the client permision for anonymous is set to contributor.

thanks

....jemckinney, i didnt mean to jack your thread either, i was just hoping a similiar answer for your problem would help me with mine.

 

[jemckinney]

No problem. But that doesn't help me unfortunately since all senders are internal. I have the user that is unable to send to the PF listed on the Exchange General tab having the ability to send and she is also an owner of the PF itself. But because her mailbox resides on my second exchange server, the email just sits in the queue. I cannot figure out what is blocking it.

 

[kbrussel]

jem-

Just to make sure--both Exchange servers are in the same organization/admin group, correct?

I'd try probably enabling the anonymous client permission to contributor.

One other thing to try--try adding a replica to the public folder store on the second Exchange server.

 

[jemckinney]

Thanks for the ideas. I did try the anon client permissions as stated with no luck. I also cannot seem to get a replica on the second exchange server. But yes, they are in the same organization/admin group. My account is the enterprise admin/domain admin/exchange admin so I know the replica issue cannot be permissions. I moved these public folders from our old 5.5 server when I decomissioned it. I have to be missing something.

 

[xmsre]

Sounds like either problems with the acl, or you didn't wit for the hierarchy to replicate before backfill started. Can you tell us how you migrated the folders from 5.5, What was the process and which tools did you use?

 

[jemckinney]

It was in May of 2004 when I brought our forest up to 2003 and exchange from 5.5 to 2003. I used the pfmigrate tool and followed the Microsoft instructions to a T. That went very smoothly. Even taking down 5.5 went well. I spaced it out over several days to allow for any replication.

The second exchange server I am having this issue with I brought up just over six months ago.

 

[xmsre]

Take a look at the acl on the public folder. Do you have any dead DNs that didn't convert?

 

[jemckinney]

none. As a matter of fact, this is a new public folder that I created just two weeks ago for this department. I only actually need three people to be able to email to it, two are on the same server and have no issue, the third on the new server is the only one having the issue. But at moment it is open.

 

[xmsre]

Has hierarchy replication completed to the new server? Could very well be content trying to deliver before hierarchy replication has completed. Check and see if items are queuing up for local delivery on the new server. These would be replication messages for content backfill. that can't go through until the hierarchy replication has finished.

 

[jemckinney]

The hierarchy has replicated successfully and that happened several months ago. This is why I am just so totally confussed. I created a new public folder today and let it sync to the new server. Once replication status for both servers for that PF was synced, I had her try to send to it's email address and queued again. I'm at a loss.