Skip to main content

I'm using SharePoint 2013 and I have set up Lazy Approval according to the directions in the LazyApproval Guide. Incoming email is working to send mail to other mail-enabled lists. The library in question also has incoming email enabled and a workflow with a flexi-task with lazy approval enabled. The email goes out correctly. When I respond through email (from a third-party domain), it arrives at the SMTP drop folder on the SharePoint server and gets processed by SharePoint, but the workflow never continues. What I see in the ULS logs is this error:

Error result for LazyApproval handler: 'You are not permitted to respond to this task. Tasks can be delegated via the approve/reject web interface.'. (Build:3150)

According to the LazyApproval Guide, this error has the following cause: "Active Directory may have multiple entries for the email account used to reply to the

email message." The resolution is, "Remove duplicate entries from Active Directory."

I don't see duplicate entries in AD, but what is considered a duplicate? I have entries like this in AD:

LazyApproval@spserver.domain.com is a Contact

LazyApproval@domain.com is a Distribution List containing that 1 Contact

Are those considered duplicate? Is there a problem having that configuration?

When I respond to the LazyApproval task email, it goes to the DL with the simpler address. That should deliver the email to SharePoint. I see in the ULS log that an email from my domain is processed by SharePoint.

Are there other reasons for this error besides "multiple entries for the email account"?

Thanks for your suggestions.

Dan

I got a response from Nintex Support saying that the lazy approval email address should not be in AD at all:

When the guide says: "Active Directory may have multiple entries for the email account used to reply to the email message." and that the resolution is, "Remove duplicate entries from Active Directory." This means that whatever address is being used by LazyApproval should not exist in Active Directory at all.

So I removed the entries I had and I stopped getting the error, but that was how the email was being routed to the SharePoint server. We had to come up with another way of getting the email routed from a top level domain address to the SharePoint server address.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings