jdigalbo
asked on
public folders not receiving external email
i have a front end server and 3 exchange 2003 sp2 servers and are replicating the public folders to 2 servers. When i create a public folder and mail enable it, i can receive email internally but can not receive email externally. We have used public folders in the past and they have worked internally and externally, now when you create a new one it doesn't work externally but existing folders still work.
adamskiangel
http://www.experts-exchang
ASKER
we are not using clustering and we haven't changed anything on our servers. The public store is mounted on our frontend server.
check the permissions on the new public folder
the anonymous account must be set to contributor for the PF to receive external email
also, public folders should not be on the front-end server. it is not a best practice.
the anonymous account must be set to contributor for the PF to receive external email
also, public folders should not be on the front-end server. it is not a best practice.
ASKER
it does have create permission
what about contributor permission?
are the external emails to this PF stuck in some queue on the front-end server?
are the external emails to this PF stuck in some queue on the front-end server?
ASKER
yes they sit in the local delivery queue on the front end server and you receive this error.
This is an automatically generated Delivery Status Notification.
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipients has been delayed.
but the message is never delivered.
This is an automatically generated Delivery Status Notification.
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipients has been delayed.
but the message is never delivered.
remove the public folders from the front-end server and the mail delivery to the PFs will start again.
ASKER
why would i have to remove the public folders from the front end server.
public folders are not recommended on front end servers.
in your case emails to public folders are getting stuck on the front-end server
if you run exchange best practice analyizer, it would also give you a warning that public folders are on the front-end server and are not recommended
in your case emails to public folders are getting stuck on the front-end server
if you run exchange best practice analyizer, it would also give you a warning that public folders are on the front-end server and are not recommended
ASKER
ok, i removed the public folders from the front end server and some emails came through but now they are sitting in one of the member servers queue.
how did you remove the public folders from the front-end server?
did you delete the public folder store from the front-end server ?
do you have public folders replicated to all your exchange servers or do you have a dedicated public folder server?
the member server that you have mentioned, are there any public folders on it?
did you delete the public folder store from the front-end server ?
do you have public folders replicated to all your exchange servers or do you have a dedicated public folder server?
the member server that you have mentioned, are there any public folders on it?
ASKER
yes we deleted the public folders from the front end server and yes the other server has public folders. we are jsut replicating to 2 servers.
did you delete the public folder store from the front-end server or the public folders from the front-end server?
ASKER
the store
if the FE has no PF store then the mail flow must be fine.
are you sure that the messages in the queue are the emails sent to the PFs and not PF replication messages?
if you send a new test mail, is it delivered to the PFs?
are you sure that the messages in the queue are the emails sent to the PFs and not PF replication messages?
if you send a new test mail, is it delivered to the PFs?
ASKER
They are working now. We had a test exchange box and we removed it and now they seem to be delivering. Is it best practices to have a replica on all servers for public folders or it shouldn't matter?
having a replica on all the servers can sometimes be disk space consuming if the public folders are quite large.
having on a single server is fine as the users are "reffered" to the server holding the content by exchange.
i have a single public folder server.
having on a single server is fine as the users are "reffered" to the server holding the content by exchange.
i have a single public folder server.
ASKER
ok thank you very much
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.