Exchange front-end not delivering public folder messages to back-end

We are using Exchange 2003 SP2 with a front-end and a back-end server.   I have mail-enabled a public folder located on the back-end server and set up anonymous with contributor access on this folder.  I am not replicating folders from the back-end to the front-end, but I do have the public folder store mounted on the front-end.    

Messages from external accounts are hanging in the front-end queue, but messages from internal accounts are delivered correctly.    I'm assuming that an NDR will be generated eventually, but we just started trying this and the messages haven't expired yet.

I've seen posts talking about unmounting and deleting the public folder store on the front-end server, but we are runnning OWA and it has an OWA scratch pad public folder on the front-end server.  If I unmount and/or delete the PF store on the front-end server, what effect will it have on OWA?

Who is Participating?
Has it ever worked?
You should remove the public folder store if the server is just for OWA use. This is explained in the frontend/backend white paper.

Yes.The database on front-end is supposed to be kept only when used as a bridgehead server (running SMTP connector) otherwise dismounted.
OSUFAuthor Commented:
Thanks for the comments.

The front-end is running SMTP so I need to keep at least one of the stores (private or public) in use.   I just wanted to know what will happen if there is no longer an OWA scratch pad folder on the front end server - it's my understanding it's used when making file attachments in OWA.  
The Posts are "Staged" in the OWAScratchPad until all attachments are added (or they are saved).  The size limit on the OWA scratch pad controls the size of attachments that can be added via OWA
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.