Docusign - using two different email body/blurb contents - html

Hello I have setup our app using the dev/demo account and almost ready to get a paid account. I want to get a starter API account, which doesn't have Branding.
Can I remove the Resource File from the email body without having access to branding? Any other way?
I would like to setup one email body/blurb for the signing email and a different for the completed email. Again without branding would I be able to do that?
I have been able to add customize/add html into the signing email body but would like to add a new condition somehow for the completed
something like envDef.EmailBlurbCompleted =
thank you

There's only one emailBlurb field in DocuSign right now. That field is used in both the original as well as the final email that are sent out. You can customize it per recipient, which is not exactly what you're asking for.
You can change it after the envelope is created, but only if it's still in draft status.
Changing this field when an envelope is in sent status requires a correct operation. Which is also not exactly what you are asking to do.
At the moment what you're asking is not a feature that exist, you can build something to mimic this, but I'm not sure that is a good idea either.

Related

Post to Node.js Server from Within HTML e-mail

I am writing a simple mailing application, however I am not yet aware of the full capabilities of HTML editing within the mailing world.
I would like to give the website administrator the choice to accept or to refuse a reservation by sending him an overview of the reservation. Below in the mail I had 2 buttons in mind, accept & refuse.
I tried using a form within the HTML e-mail but almost every mailing client blocks this out.
Is there another method to do a http post command to let's say myserver.com/accept or myserver.com/refuse from within an e-mail without having to open an additional webpage?
If not, what is the best way to achieve such things?
This is a pretty relevant article: https://www.sitepoint.com/forms-in-email/
Basically he concludes that support is not reliable so you should not use forms in emails which I agree with.
Since you say you want to give this choice to a website administrator I think you probably want some sort of authentication. So I could see it working something like this...
Send the admin an email containing two links mysite.com/reservations/:reservation_id/accept and mysite.com/reservations/:reservation_id/refuse.
Admin clicks on one of the links
Link opens in the browser and your site(controller -> ReservationService) accepts or refuses based on the id and action in the url
You will have a few things to consider, such as authentication(I assume you already have this since you have the notion of website admin?), authorization(can this admin accept or deny the reservation?), does the reservation exist, has the admin already accepted or denied the reservation, etc.

Outlook screws up contacts added through EWS, unable to send emails as a result

Ok so that title is not the most informative, but I'm having a hard time describing whats going on.
The Context:
I have a C# application that manages a bunch of contacts. Using the Outlook/exchange web service (EWS) managed API I am able to create an exchange contact with the email addresses and phone numbers and all that.
This is as a replacement of a service based Active-Directory based person list (that was then linked to in outlook) also developed by us.
The Problem:
After removing the old active directory list this started happening.
Whenever you select a contact from my new (ews based) list (in a to: field in ta new email) it would look liked it started to auto resolve. Then it displays the message that the mail cannot be sent because the email doenst exist anymore or is not valid.
If you check the autocomplete dropdown for that contact it now displays something like this: peter keutels <8b620d77d1df4bf0b7aad23f4632a503-peterkeutels#email.adres>
and in the NDA it lists the recipient as Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=8b620d77d1df4bf0b7aad23f4632a503-Peter+20Keutels#COMPANY.OFFICE
instead of just peterkeutels#email.adress
We tried clearing autocomplete, disabling auto-resolve. recreating outlook accounts...
I am totaly lost with this. I feel like this might just be an outlook problem. And in that case I probably should post this in another website. But I created the problem by using EWS. I hope I can fix it with EWS as well..
After removing the old active directory list this started happening.
The first thing I would check is the contacts themselves if you look at the contacts with a MAPI editor like OutlookSpy of MFCMapi and take a look at the EmailAddress properties for the Contact you may find these Contacts have the Ex address of the List your removed. (In that case you need to fix the contacts).
We tried clearing autocomplete
What method did you use and what version of Outlook are you using ? on later versions of Outlook this gets stored as an FAI item in the Mailbox so you might want delete that Item eg http://www.msoutlook.info/question/backup-and-restore-autocomplete
(There also the suggested contacts folder and OWA also has a seperate AutoComplete)
Cheers
Glen

Auto-fill gmail BCC line based on To field

I am trying to augment my CRM that I have. The high level problem is that I've to enter multiple email addresses every time I want to write a message. This becomes a particular problem when replying to a message and forgetting to enter a special BCCed email address. I'd like to not have to remember to do that. I want, when I am using gmail, for an address in the To/CC line to trigger an auto-population of an address in the BCC line.
Here is how I think I would do this now:
My idea is to do, implement a map/dict/whatever by using two columns in a google spreadsheet (sheet) document. (Using the sheet means an easy visualization to my dict and an easy ability to share with permissions etc.)
The first column would be the To/CC email address and the second column would be the auto-populated BCC email address.
Then I'd like to have code run on my computer that allows me to use gmail as you would without having to think about whatever will automatically go into the BCC field. (Bonus points for figuring out a way for me to code something up that allows me to not have to think about this when sending email from the gmail app on my iPhone.)
It may seem from my abstract description that I would need to hire someone to do this but I know I can code this myself. I just need to be pointed to the correct APIs and be notified of any gotchas that I should avoid.
Currently I was going to write a google contextual gadget to handle auto populating the field. Is that the best way? Or is a greasemonkey/whatever script better? What is the general approach I should take to tackling the problem?
To fix the phone/other-email-frontend problem would a Google Apps Script that acts like a cron job to check the most recent sent emails and if they don't have the proper bcc then just forward those emails with an appropriate bcc be reasonable?
Basically, am I off base or on track with my solution? If I am on track give me a bit more information on appropriate plan of attack. If I am off base then point me in the right direction.
I would appreciate your help.
I don't think you are going to be able to do this inside of gmail. You could save a bunch of Drafts with the correct BCC emails, and put the TO: email in the subject line so that you could see who that draft was meant for, then change the subject line.
You could have a dialog box in your spreadsheet that you designed to look like an email compose screen. That would be the most straight forward approach. You could have a stand alone App, that had an input screen that was designed to look like an email compose screen.
Basically, you'd need to design your own user interface rather than using gmail. But the gmail compose window isn't anything very complicated, so if it's just a plain text email, it should be easy enough.
Your question would be more understandable with a concrete example of the problem (I'm not sure I entirely understand it). But Gmail supports mailto: URLs quite well. Perhaps that is the answer to what you want to do.
There are various scripts to help you generate a mailto: the way you want, so have a look at something like http://sislands.com/coin70/week6/mailtoCreator.htm

Keeping Email Message from Grouping into Conversation View in Gmail

I'm working on a feature for a client to send them email updates whenever a specific event occurs on their site. When the message shows up in Gmail, the messages get grouped together in conversation view even through they aren't the same conversation. It appears that this is due to the fact that Gmail groups based only on the subject. The client is adamant that we not change the subject line (don't get me started).
Does anyone know how I can disable this by sending a special header in the mail or am I out of luck?
There appears to be no way to prevent this, short of turning off conversation view (have you considered that?).
My guess is that Gmail is actually threading based on its own Thread-Topic header field, which it adds (overwriting any value you pass; it just copies the Subject field) - there's no way of telling, though, unless you can change that field after the fact. Which leads to the suggestion of writing an IMAP application to download the message, edit the headers, and re-upload it again. You'd need to investigate the feasibility of this, though.

Authenticating incoming email sender

I want to develop a system with which users interact by sending in email. Very much like most email discussion groups or like posterous.
What checks should I apply to incoming email to make sure it comes from the address it claims to be?
There is no method of authenticating email in a reliable, universally available and easy to use fashion.
The best way of handling this is probably by giving your users a unique, hard to guess email address to send their emails to (something like 459f71b01809458adfe17a7d838dcb19#postbymail.yourdomain.com). You authenticate them based on the assumption that they're the only ones who know that address. When you do this, you also need to add a way for users to invalidate the address and generate a new one (in case it was compromised). And don't forget to make it easy for them to get the address in places where they can't easily copy & paste it, like on a mobile phone (easiest done by adding a button that sends them an email with the generated address as sender).