I'm having an issue receiving the verification email from DocuSign that is needed to create an account under my master account to connect for use with API. The emails don't appear to be hitting my firewall, nor are they showing up in my email. Does anyone know if these emails are coming from docusign.com, docusign.net, or some other domain?
In Demo emails will come from dse_demo#docusign.net and in PROD it should come from dse#docusign.net. Also please check your Spam/Junk folder if it landing on these folder as per your email server policy.
Related
I have a website that requires people to confirm their emails upon registration. My backend server is a node server. I am using nodemailer to deliver these confirmation emails.
For testing, I am currently using a gmail account to send these emails. And this is working perfectly.
Now however, I would like to upgrade and use my own domain email. And I would like to send out these emails under an email address like "no-reply#mydomain.com"
One of the requirements for my site is that it can handle sending up to 2000 confirmation emails in a day.
I have looked at email hosting like godaddy and it says that one email account with them allows only 250 emails a day, which is way less than 2000.
So, how can I achieve 2000 emails a day in the cheapest way possible? Any recommendations will be helpful.
Thank you in advance for helping me with my question.
I highly recommend GSuite by Google.
Once registered simply create a no-reply email (If I recall correctly, nodemailer needs the email to exist on the smtp server to work) and link it up. Good luck
we have an application that is using the Outlook REST API v2 to allow the users to send emails from the app.
Today one of our clients send us a bug report, that after they created a new Office365 account for their company they can't send emails through our app. The current case was for sending email to hotmail.com account. The email bounces back with error code
550 5.7.708 Service unavailable. Access denied, traffic not accepted
from this IP.
The user also reports that they are able to send the same email from the Outlook web client.
I have found this issue on the network: https://social.technet.microsoft.com/Forums/ie/en-US/608d046b-755a-4264-8cdd-fc34c72ccf8f/office-365-tenant-blacklisted-on-all-emails-sent-by-ms-outlook-2016?forum=onlineservicesexchange and am now wondering if this is just a bug on Outlook side or we have missed something on our end?
You have to go here: https://sender.office.com/ and put the incriminate ip to delete it from the list.
I'm trying to set up a delegated institutional Google Mail to forward e-mails to our JIRA Cloud instance's e-mail address so that they can be turned into JIRA issues. I do not have and cannot get the password for the Google Mail account, and when I try set up the forwarding address in Google, Google sends a confirmation e-mail address to the JIRA e-mail address.
Is there a way to check e-mails sent to jira#myorganization.atlassian.com to recover this confirmation code? If not, how can I do this?
Atlassian does not host mail server. You need to create JIRA email account in your organization mail server (or on any other mail server like gmail) and tune JIRA to connect to the account via IMAP or POP3. Please look here: https://confluence.atlassian.com/display/Cloud/Creating+Issues+and+Comments+from+Email
As of a few weeks ago, I noticed that I am unable to receive emails from my domain account. My application is deployed to the azure server and it uses SendGrid to send emails and this happens from my application. For example my application is 'myapplication.com' and the azure sendgrid configuration for the mail server is set up to use 'Jake#myapplication.com' but when I send and email to my yahoo account, let say to reset my password. The email never makes it, not even going to spam. I remember reading something like this a few weeks back http://sendgrid.com/blog/update-yahoos-dmarc-policy "Yahoo New Policy" but I don't see how that would effect me since my from account is not a yahoo account. If there is no fix for this, what is an alternative email setup
Before considering an alternate email setup, contact SendGrid through support.sendgrid.com, it's possible that Yahoo is wrongly blocking your email. If this is the case SendGrid will advocate for you and work to get it unblocked.
Disclaimer: I am a SendGrid Employee
I'd suggest looking at the sendgrid dashboard and search for that email. You will be able to see exactly what happened.
it seems that Sendgrid IP pool is being deferred by yahoo. I am not sure what Sendgrid is planing to do to rectify this issue as it is impacting their clients who uses shared pool service
I have just stumbled on this issue. And it's not only Yahoo blocking sendgrid emails. They rather complaining about the senders ip address "Send Grid" rather than senders email address. :-(
I want to use node-mailer module to send emails to registering users on app for verification and other purposes also. I am not sure which transport mechanism to use so that emails I send are not a spam and also get delivered.
I also want to use the same domain to receive emails regarding support and bugs(i.e lets say on email on support#example.com). I am planning to set-up google apps account for this. Basically I will set-up the google apps account with me being an user and having an alias support#example.com. So can I also set-up an alias with say admin#example.com and send the emails using nodemailer from my app using this email address? But obviously I don't want to store my email id and password for google apps in the code for security reasons. So how Should I do it?
Other option is to Amazon SES, I believe its a good service and would be very useful. But can I use the same domain name for serving email from AMAZON SES and google apps also being able to host my app? So how to send emails from AMAZON SES by authenticating SPF and DKIM so that these emails reach the inbox of the user.
Saransh,
You absolutely can use the same domain and email address with both Google Apps and AmazonSES without any issues. When it comes to receiving emails, all messages have to be directed to a single server (your MX records). But sending email is very different in that you can send email from many different sources without any issues.
To ensure your messages don't go to the SPAM folder just be sure to properly authenticate all your messages with SPF and DKIM. I'm not sure how this works with AmazonSES, but it was really easy with the provider that I chose for my email http://socketlabs.com