Error while sending email to mail enabled public folder
Hi,
We are having issue while sending emails to mail enabled public folder.
Error desc as below :
CNAM@domain.com
#554 5.2.0 STOREDRV.Deliver.Exception:AccessDeniedException.MapiExceptionNotAuthorized; Failed to process message due to a permanent exception with message Cannot complete delivery-time processing.
We are having public folder hosted on Ex 2007 server.
Any help / pointers will be appreciated.
Thanks.
Thanks
November 1st, 2011 9:26am
On Tue, 1 Nov 2011 13:26:33 +0000, ex_ad wrote:
>We are having issue while sending emails to mail enabled public folder.
Who is "we"? Is it Outlook users, or is it SMTP e-mail from the
Internet or an application?
>Error desc as below :
>
>CNAM@domain.com #554 5.2.0 STOREDRV.Deliver.Exception:AccessDeniedException.MapiExceptionNotAuthorized; Failed to process message due to a permanent exception with message Cannot complete delivery-time processing.
>
>We are having public folder hosted on Ex 2007 server.
>
>Any help / pointers will be appreciated.
Check the client permission on the folder. The sender must have at
least the role of "Contributor".
If it's SMTP e-mail, you'll have to assign the contributor role to the
Anonymous user.
---
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
November 1st, 2011 12:33pm
Hi Rich,
We have assigned the contributor role to the anonymous user already.Thanks
November 1st, 2011 1:59pm
All users having issues or some? Issue with this PF or others too? Create a new PF, same issue? What about the Default user, give that permission to contribute, Is the sender internal or external Sukh
Free Windows Admin Tool Kit Click here and download it now
November 1st, 2011 4:33pm
n Tue, 1 Nov 2011 17:59:32 +0000, ex_ad wrote:
>We have assigned the contributor role to the anonymous user already.
Okay, but is the person sending the message an authenticated user or
not? You don't provide a lot of information so all I (or anyone) can
do give you "this is a common problem" type of answer.
---
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP
November 1st, 2011 6:04pm
Hi,
Based on my research, in most cases, the issue is caused by old unused Exchange server still in Exchange 2003 Administrative group. If we migrated
from Exchange sever 2003 to Exchange server 2007 and Exchange server 2003 has been decommissioned, please go to use the following path using ADSIEDIT.msc to remove the servers contains and then check:
CN=configuration, \CN=Services\CN=Microsoft Exchange\CN=Organization Name\CN=Administrative Groups\CN=Exchange 2003 Administrative
Group\CN=Servers
If the above still doesn’t work, I suggest you check whether it is caused by incorrect public folder permissions. To
check it, you need to run the following commands in the EMS on the mailbox server that hosts the public folder and the commands should set the default permissions on the public folder, which you can refer to the article ‘Add-PublicFolderClientPermission’:
Add-PublicFolderClientPermission -Identity <PublicFolderIdParameter> -User default -AccessRights
“Author”
Add-PublicFolderClientPermission
-Identity <PublicFolderIdParameter> -User anonymous -AccessRights “createitems"
If you encounter any difficulties, please let us know.
Thanks
Sophia Xu
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2011 3:58am
well this is disappointing because the users on my end are not running outlook 2003, i am an domain admin running office 2010, my servers are 2008r2 RU5 (working on updating to SP2) and i still get this error....
June 1st, 2012 1:23pm
I also have the same problem. We have an exchange 2010 environment. A separate IIS SMTP service on a windows 2003 server relays the incoming emails to the exchange. All outbound emails are relayed out through the same IIS SMTP server.
A spam filter runs on the W2K3 and sends the emails flagged as spam to a public folder on the exchange server. The anonymous on that PF has only the write (create items) permission. It works fine but time to time some users receive an NDR email
like the one posted by the OP.
I checked the logs. Looks like these emails are always spam with the same sender and recipient addresses. Here are the SOURCE and EVENT-ID entries for these emails in the exchange routing logs.
SMTP-------->RECEIVE (Sender-address: joe@mycompany.com)
failure DSN--------->DSN (Sender-address: MicrosoftExchange329e71ec88a@mycompany.com)
STOREDRIVER->FAIL (Sender-address: joe@mycompany.com)
ROUTING----->EXPAND (Sender-address: MicrosoftExchange329e71ec88a@mycompany.com)
STOREDRIVER->DELIVER (Sender-address: MicrosoftExchange329e71ec88a@mycompany.com)
Because the return-path of the spam email is the same as the sender address. The legitimate user gets the email in his/her inbox.
Free Windows Admin Tool Kit Click here and download it now
July 17th, 2012 4:09pm
I also have the same problem. We have an exchange 2010 environment. A separate IIS SMTP service on a windows 2003 server relays the incoming emails to the exchange. All outbound emails are relayed out through the same IIS SMTP server.
A spam filter runs on the W2K3 and sends the emails flagged as spam to a public folder on the exchange server. The anonymous on that PF has only the write (create items) permission. It works fine but time to time some users receive an NDR email
like the one posted by the OP.
I checked the logs. Looks like these emails are always spam with the same sender and recipient addresses. Here are the SOURCE and EVENT-ID entries for these emails in the exchange routing logs.
SMTP-------->RECEIVE (Sender-address: joe@mycompany.com)
failure DSN--------->DSN (Sender-address: MicrosoftExchange329e71ec88a@mycompany.com)
STOREDRIVER->FAIL (Sender-address: joe@mycompany.com)
ROUTING----->EXPAND (Sender-address: MicrosoftExchange329e71ec88a@mycompany.com)
STOREDRIVER->DELIVER (Sender-address: MicrosoftExchange329e71ec88a@mycompany.com)
Because the return-path of the spam email is the same as the sender address. The legitimate user gets the email in his/her inbox.
If yours is spam then consider setting up a SPF record for your SMTP and use SPF.Sukh
July 17th, 2012 4:34pm