Skip to main content

Hi,

I’m working with a sandbox to integrate docusign in my web app. My service is able to create the envelopes and, checking on the docusign developer page all appear to work properly. The problem is that the mail never get to the recipients.

@Ivan.Dinkov

 

I need help! :)


We’ve started seeing this as well. Here are other symptoms:

  • Emails with routingOrder of 1 are usually delivered
  • Emails with higher routingOrders are not, but the webhook callback from Docusign suggests that they were sent. Sometimes one of these emails will arrive hours after the fact. But even those have stopped.
  • Before this started happening, the content of the notification emails sent by docusign got less friendly:

Do you recognize this signature request? 

We have received a request to send you a document for signature.

Do you recognize the sender and approve the document for signature? If yes, please confirm by clicking "Continue". If you do not recognize the sender or have any concerns, please click "Report Abuse". 

Your security is our top priority and we appreciate your prompt attention to this matter.

Seems like the two things might be related but we’re at a loss. I spent most of the day yesterday making sure it wasn’t a code issue on our end but I don’t really know how to address this.


@Moving.Overalls 
@Ivan.Dinkov 

In our case, none of the recipients are receiving the emails, even though they were receiving them during previous tests. Unfortunately, support hasn’t been helpful, and we’re stuck — we have no way to move forward with the integration or use DocuSign services.


Hello Tatiana,
 
Thank you for contacting our Docusign Community.

Please look at this list of possible reasons why emails are not delivered:

Why aren't my signers receiving Docusign Notification emails?
 
Best regards,
 
Adrian | Docusign Support

@Adrian Dev 

We have experienced this even to our Land O’Lakes email accounts.  None of what is in your list applies.  It does not send, sorry to report.


@Adrian Dev 
Unfortunately, the list you shared does not apply to our situation and does not help solve the issue.