Recent email security update. How to fix “We couldn’t process your email”

Can i add a +1 one to this for G Suite users. Very frustrating.


1 Like

Briefly describe (1-2 sentences) the Bug you’re experiencing:


When using Google(G-Suite), the mailing server and the mailing domain are different.
Please fix it quickly.

Steps to reproduce:

Browser version:

Upload screenshots below:

Hi @hisong and welcome to the Forum! This is actually an expected behaviour; you can learn more about this issue and how to resolve it in the following thread: Recent email security update. How to fix “We couldn’t process your email” :slight_smile:

Adding to the conversation to say that I’m having a similar issue. We have an outside vendor who uses forms to collect data, and I can’t have that data sent into Asana because of this change. Damijan’s solution of using SPF seems as if it would solve this issue for us, as well as maintain Asana’s desire for heightened security.

Add my company to the list of G-Suite users affected.

1 Like


It is not even alias domain, the mail is being sent from primary_domain. But Google when send the email, it is being sent from “” instead of “”.

It affects mails being sent from “” as well as “GSuite” mails.

I’ll chime in because this is becoming a real problem. I now have to copy email conversations as comments because we can’t just email to the task since we use an alias. It is at the point that even though I am an ambassador for Asana, have been using it for almost 7 years with the different positions I’ve held, I convinced my non-profit to PAY for the subscription (not an easy task at a non-profit) the extra workload this has created for me is no longer worth the program. So if it is not fixed, I’ll be convincing my superior’s to make the switch to a software that allows us to email in to it.

Really frustrated!