Can i add a +1 one to this for G Suite users. Very frustrating.
Thanks.
4 Likes
Briefly describe (1-2 sentences) the Bug you’re experiencing:
Hi
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” 
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
Hi,
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 “google.com” instead of “primary_domain.com”.
It affects mails being sent from “gmail.com” 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!
We switched from self-hosted Postfix to AWS-SES. We use a verified SES identity domain with DKIM and Custom FROM domain, as suggested in your post. However, we still see this error. Happy to share example email headers via PM.
Clearly there are steps or checks missing from this guide when using SES. What other considerations must be taken?
This is crazy. 2020 and this still has not been given a whitelisting option? Switching my alias and primary accounts is not an option.
2 Likes
Any solutions for emails sent from NetSuite?
" We couldn’t process your email because it was sent by netsuite.com but your email domain is XXXXXXX. Please contact your email admin to update your mail server’s email settings."
Another Gsuite user. Weird thing is that it’s been working fine for months before today. Did no changes on Gsuite.
3 Likes
I’m a GSuite user too I have been using this non-stop for about 12 months then suddenly today it is not working.
2 Likes
This has changed for us today when we’ve been fine using it for months. Did we receive another update that is preventing the emails from being sent?
1 Like
Same here. We have been using for 2 years on GSuite and suddenly doesn’t work. No aliases being used and no changes on our end
same here!
Well, seems like all good things come to an end! Can’t get tasks created via simple forwarding
Hi, I was experiencing the same problem today (May 1st, 2020) I went to Check MX: Check MX and SPF Records. as another user in this thread suggested (Neal),. There was indeed a problem with our SPF record in our DNS zone. Followed the instructions mentioned in Help prevent spoofing and spam with SPF - Google Workspace Admin Help and it works now.
6 Likes
I’m not following the GSuite option. I have a G-Suite account. There is one email address associated with that account (mine). I only send emails to Asana from that address.
As ubiquitous as Gsuite is, I’m surprised that this isn’t fixed yet.
2 Likes
It seems to have worked for me as well
1 Like
thanks for this! working now
1 Like