I'm trying to send an email in a 2.0 suitescript (scheduled). My code is very simple:
email.send
({
author: 123,
recipients: 123,
subject: 'Errors',
body: 'Please see attachment'
})
That's it. The email shows up in the Sent Email list, which seems to show everything fine:
Sent Date 04/27/2021 17:21
Log Date 04/27/2021 17:21
From "<my name> (<my email address>)" <system#sent-via.netsuite.com>
Subject [SANDBOX] Errors
To Recipients <my name> (<my email address>)
CC Recipients
BCC Recipients
Message-ID <fknhf2pr4jqaxt5dmqc56ab2353384v9zj0qr1i6ke5fz9n3o7u6w0o8alojgm0w#netsuite.com>
Status Not Sent
Unchecked Compliance Verified
Body Please see attachment
I note, however, that in the sent email the RECIPIENT list is empty - my email does not appear; no emails do.
The email doesn't arrive. So no apparent errors - it just doesn't arrive, and NetSuite says it was not sent, although it doesn't seem to say why.
Check Sandbox "email delivery preferences". As an Administrator go to Setup > Company > Email > Email Preferences > Sandbox and Release Preview subtab (Sandbox Options heading). There are options there to dictate who Sandbox emails are sent to. You can reference Suite Answer Id 20152 for more information. If there's still as issue confirm the specified employee internal id actually has an email address stored in the record.
Related
I am using the sample code provided by docusign, but there is no indication in response if the envelope is actually sent or not.
If the email does not exists, it still generates the envelope id and there is no error.
here's the response:
Please enter the signer's name: saf
Please enter the cc email address: scisaif1#gmail.com
Please enter the cc name: saif
{'bulk_envelope_status': None,
'envelope_id': 'bd7781a5-ea9e-472d-b087-90baa12b573f',
'error_details': None,
'recipient_signing_uri': None,
'recipient_signing_uri_error': None,
'status': 'sent',
'status_date_time': '2022-08-14T10:02:02.9400000Z',
'uri': '/envelopes/bd7781a5-ea9e-472d-b087-90baa12b573f'}
Your envelope has been sent.```
this is the response when email does not exist, i get an email that says
Documents you sent for electronic signature could not be delivered to this email address: adfasasdfasdgasddf#gmail.com
The internet email system is a weak creature. If DocuSign receives a negative delivery report, then the envelope status will be updated. (Try a bad email on the DocuSign web app.)
But there are bad email addresses that don't result in a negative report to DocuSign.
For these cases, the envelope's expiration tells you that there was no response.
I suggest that you ask the signers for both their email and sms mobile number. DocuSign can then deliver the signing invite to both.
Suggest you use DocuSign Connect and set a webhook. This will give you an event if email bounced, or opened. You can use these events to decide what to do in your system.
I have experienced very weird behaviour from DocuSign account.
There are Two roles for my Template:
A. Contractor : Signer, Routing Order 1
B. Employer : CC (Receives a Copy), Routing Order 2
When Employer sends sign request to contractor, contractor declines it.
Person in CC is the actual employer, who is using my DocuSign account to send contract for signature.
Person in CC receives Signed documents, but not the declined ones.
Once it is declined, contractor and DocuSign account owner(Docusign Admin) gets declined email notification but not employer person in (CC).
Employer status still shows "Awaiting", while all parties must have received declined email notification
This was working previously but not today as 15th Feb 2022
I tested this via manually creation of templates and sent for sign
I have tested it on demo and production account,
NOTE: There are no changed in settings under :
1.Recipients
2.Sending
3.Signing
4.Notification
[![Please find the attached screenshot]
: https://i.stack.imgur.com/ghkJj.jpg
I faced the same issue today as CC email only getting signing completed notification.
After searching in DocuSign documentation, I noticed the Routing Order feature.
This answer has a better explanation of Routing Order.
After reading about Routing Order, I just set a "1" routing order in the CC email object (The same "1" routing order was set for the signer) and it starts sending all communication notifications to the CC email including decline.
Because you have the same issue, so you just need to set the routing order against CC.
Using DocuSign C# Sdk code example:
EnvelopeDefinition env = new EnvelopeDefinition
{
EmailSubject = "Test",
Status = "sent",
Documents = new List<DocuSign.eSign.Model.Document>(),
Recipients = new Recipients
{
Signers = new List<Signer>
{
signer
}
}
};
env.Recipients.CarbonCopies = new List<CarbonCopy>
{
new CarbonCopy (
Email: "test#abc.com",
Name: "Sender",
RecipientId: "2",
RoutingOrder: "1")
};
API JSON request example:
"recipients": {
"carbonCopies": [
{
"email": "test#abc.com",
"name": "Sender",
"recipientId": "2",
"routingOrder": "1"
}
],
"signers": [...]
}
When Employer sends sign request to contractor, contractor declines
it.
Once it is declined, contractor and DocuSign account owner(person who
owns this account) gets declined email notification but not employer.
Here is the issue, you said the "employer sends" but later you said someone else is the account owner. What you meant is someone else actually sends, not the employer, right?
In this scenario:
Person A sends an envelope to Person B and Person C is CC in routing order 2. If person B declines, Person C will receive no email. Nothing. It never reached routing order 2. Person A will get the email, because they are the sender.
The reason the employer got the emails was because he was the sender, not because of the CC. If the sender is still the employer (or whoever else it is) they will get the email. The CC in this case will never get an email.
Hope this clarifies this. You need to check who your sender is, it's not who you think it should be.
I've set up some google apps mailing groups, but emails from nodemailer to the groups are always getting 'bounced' (but no bounce-back email).
Individual gmail addresses receive the same nodemail fine. The admin email log looks like this for successful email to individual gmail user address. The email headers from the successful email show no issues (eg no spf failures).
The groups do receive emails from external users (including from the same address nodemailer uses) when sent through the gmail web client, so it it isn't a group permission issue. Successful emails to the group yields an admin log like this.
The group is set to forward all spam to users.
Nodemailer is using a gmail account, and the GApps are using a Google domain hosted address, so it shouldn't be an issue with routing or conflicting servers
What am I missing here?
This was resolved by reconfiguring the 'from' field in the nodemailer message.
// Nodemailer ignores the bad `from` value (not a valid email)
// Nodemailer sends with from ==''
// This gets bounced by google group addresses
var msg = {
from: "System",
to: "usergroupaddress#gmail.com,
subject: "Your generated email",
text: "Hello user",
html: "<p>Hello user</p>"
};
I had thought 'from' would define the name displayed on the email. It didn't do that, but it didn't cause any problems either for most email recipients. But google groups was bouncing those emails.
Nodemailer was just leaving 'from' as blank (rather than using my dummy string). Apparently this field must be a valid email address. Set it to an email address, and nodemailer will include it in the message envelope, which google groups will then stop bouncing.
// Nodemailer accepts and forwards the valid `from`
// google groups address will accept the email
var msg = {
from: "system#myserver.com",
to: "usergroupaddress#gmail.com,
subject: "Your generated email",
text: "Hello user",
html: "<p>Hello user</p>"
};
The google apps email also hints at this: emails with an empty 'from' envelope have a blank 'sender' in the google apps email log search. But as soon as I corrected nodemailer, the 'sender' started populating in email log search, and google stopped bouncing the emails. See the email log here.
I have a Google Group setup called tes#domain.com on my G-mail Account.
In that group, I have 8 members email addresses.
If I send mail to that group from "send-grid", the mail is not been received.
$url = 'https://api.sendgrid.com/';
On Send-grid when I check status of this group-email(tes#domain.com) its show its been "Delivered" and "Opened" as well.
And I also get this SendGrid {"message":"success"} json response
Your group email alias is probably not enabled to receive emails from external sources. You need to update your settings to allow posts from 'anyone'
Not received email that was typed in textbox "Email Address" using dialog "Save your Copy" in "In Person" signing.
While signing the envelope in In-Person mode there is an window (popup) to send a copy of the document in an email. We have entered the email (many times and different email services) but no email received. Checked settings in the DocuSign portal account but not able to find any setting for this. Please let us know how to enable the save a copy email in DocuSign.
We using DocuSign SOAP API under C#.
For InPererson Recipient we add :
new Recipient
{
Email = "email of host recipient",
UserName = "name of host recipient",
SignerName = "name of current recipient",
ID = "id current recipient",
Type = RecipientTypeCode.InPersonSigner,
RoutingOrder = 2,
RequireIDLookup = false,
CaptiveInfo =
new RecipientCaptiveInfo {ClientUserId = "special id of current recipient"}
};
And we open docusign token url (RequestRecipientToken method) in new browser window without iframe we open it in IE 8-11 and Google Chrome
What we have to specify in addition to this , when creating and sending envelope or in account preferences of main account in docusign.com?
First, keep in mind that the email you're describing will only be sent upon Completion of the Envelope -- so if there are other recipients after the In-Person signer in the routing order for the Envelope, the In-Person signer wouldn't receive the email until all recipients have completed their required actions and the Envelope is complete.
Second, you might want to verify (in Preferences >> Features within the DocuSign web console) that these two settings are set as shown here:
These settings control whether or not emails are sent to "embedded/captive" recipients. Even though you're using "In-Person" signing -- it sounds like you're launching the host's signing session using "Embedded Signing" (i.e., RequestRecipientToken), so these settings might be affecting whether or not the email actually gets sent to the signer.