Hi again - I appreciate your concerns here and to be honest, I’m the messenger. The workaround that I provided is the solution available to us right now. Our engineering team is working on this (they’ve seen this thread ) and I’ll be sure to reach back out to you when I have any updates.
Is there any update expected on this within the next week? This will be an issue for several of our clients’ workflows if we cannot develop a workaround other than internal e-mail forwarding. Can we have this new e-mail security feature be made optional or whitelist certain domains, or roll back to the previous Asana version? If anyone else can share workarounds they’ve developed for their environment, that would also be helpful to us. Thank you.
Just jumping in to say that our team is affected by this too - we forward feature requests and support tickets to Asana from Freshdesk. Based on other comments/threads, my team is very concerned that this isn’t going to be fixed at all - can you confirm that it will be addressed eventually? Thank you!
We are also experiencing major setbacks due to this change.
Unfortunately, setting up mailboxes to auto-forward is very messy and not a good workaround.
We would like to see this problem resolved or at least the ability to revert to the old version.
Hi there - thanks for checking in! If you’re continuing to have issues, then I advise you to reach out to our support team at asana.com/support. The support team will be able to look into your account and explore unique troubleshooting options for you one-on-one. For more general questions we’re happy to help here in the Community, as well!
Hi everyone! I’ve just created a new post to give you more insights on this issue, you can read it here: Recent email security update. How to fix “We couldn’t process your email”. I have also listed some resources that should hopefully help you to solve this problem. As @Alexis already mentioned, feel free to reach out to our support team (asana.com/support) if you need additional assistance. Every case is unique and there isn’t just one way to fix this problem! Thanks for your patience and your understanding!
Thank you so much Marie, this is awesome and exactly what we needed to address this. Still have issues that your team did not notify us of these changes prior to rolling them out and that we have to fix the issue ourselves (are you certain that you cannot make this feature optional per domain somehow?), but at least we now have a definitive response to understand this better.
Thanks for your reply @JG_USeDirect and apologies for the late communication regarding this security update; I will make sure to pass your feedback on to the Team so we can improve our communication in the future. As far as I’m aware, we haven’t planned to make this feature optional, but I will make sure to keep you posted if I hear anything different!
Did anyone manage to resolve this if you don’t have access to your SMTP server?
Hi @Design_Team. If you don’t have access to your SMTP server, this integration https://www.jotform.com/help/470-Create-tasks-in-Asana-with-JotForm-submissions might be a solution (although note that it does not provide support for attachments).
You could also look into having your Jotform info sent to your own email address, and then auto-forward it from there to Asana.
Hope this helps!
Design_Team, we had to use the workaround of creating separate e-mail accounts for our clients to mail into. We then used forwarding rules to send to the corresponding Asana task #, making the task automatically. It was the only solution we were able to come up with as we couldn’t add our external clients as users to Asana or request that our clients modify their DNS records (Asana’s recommendation of what to do on our Sendgrid mail server). This new security feature basically broke e-mail to task for external clients and had no usable recommended workaround for us other than this. Hope that helps.