As some of you might have already noticed, we have recently made some updates to our email security protocols in order to strengthen account security. The idea behind this security update is to prevent people from spoofing your email address and creating tasks in your Organisation/Workspace without your permission. Please note that this issue is only affecting emails sent to Asana; emails sent from Asana (such as reminders or notifications) are not affected!!
Let me give you a little bit of context: when sending an email to Asana, the email has in fact two addresses: the address that it says it’s from, and a second address that it’s really from (the “envelope-from”). Note that every email provider uses their own terminology here, so these two addresses might be named differently depending on your chosen email provider. Asana used to accept all emails, even if the address that the message says it’s from didn’t match the address it was really from.
This is no longer the case – if the two addresses are not matching, you will receive the following message: “We couldn’t process your email because it was sent by notyouremail.org, but your email domain is supercoolcompany.com. », and in order to fix this, you’ll need to re-configure your mail server so that the domain of the envelope address matches the domain of the from address. You might additionally have to update the domain settings in order to give this server permission to send emails on behalf of this domain.
Unfortunately this is not something we can modify on our end, but we have listed some resources below that you might find helpful to reconfigure your email server:
- If you’re using a G Suite alias: We’re currently working on a solution (I will make sure to edit the post as soon as we have some updates). In the meantime, we would recommend the following:
- Please make sure emails are sent from your primary G Suite domain, not an alias
- Swap the primary domain and the alias around.
If you are using Amazon SES, please see this support article: https://docs.aws.amazon.com/ses/latest/DeveloperGuide/mail-from.html
If you are using SendGrid, please see this support article: https://sendgrid.com/docs/User_Guide/Settings/Whitelabel/domains.html
If you are using Postmark, please see this support article: https://postmarkapp.com/support/article/910-how-do-i-add-a-custom-return-path
If you are using Salesforce, please see this support article: https://help.salesforce.com/articleView?id=000250391&language=en_US&type=1
If you are using Jotform, please see these support articles:
For SMTP: https://www.jotform.com/help/244-How-to-Setup-SMTP-for-a-Form (Note that setting up your sender email in Jotform using the “verified email” option will not work)
For the API integration: https://www.jotform.com/help/470-Create-tasks-in-Asana-with-JotForm-submissions
If you’re using Google Forms: Please make sure to use to use the Google Forms integration we recommend in our Guide (https://asana.com/guide/help/api/forms#gl-google-forms) as other integration may not work.
If you are using Hubspot, please see this support article: https://knowledge.hubspot.com/articles/kcs_article/cos-general/how-to-connect-your-email-sending-domain
As you can see from above, there isn’t one solution to this problem; most of the resources listed above should help you in solving this problem but if you have any questions or if you need some additional assistance, please reach out to our support team (https://asana.com/support) who will be able to assist you further.