noreply@ no longer bounces

[SkyeHa]

News to me: replying to a "noreply@" email from your Workfront instance (e.g. noreply@workfront.com/noreply@attask.com) no longer produces a bounce-back. System is working as designed (i.e. they removed the existing bounce message). Any thoughts? Much as it pains me to admit, some of my users still do not know the difference between responding to a Workfront email and responding to a regular email. I've fielded a couple of emails from baffled people who want to know why other users are not receiving their emailed responses. -skye

[VincentGo]

I've noticed that too. To me, it's a problem for our reviewer/requestor licensed people who aren't super familiar with Workfront. I've had a few ask me, "Why didn't you get my response?" If the user replies directly to the email, it goes to noreply@attask.com, which is an email address that none of us monitor (or have access to). We do not receive their reply. There is also no communication sent to sender that their reply was not received. I don't have any measure on how big of a problem this is, but I do believe it is a risk. POTENTIAL SOLUTION: According to this Workfront support procedure (

[SkyeHa]

my IT department tried this with us 3 years ago when we launched, and we were not able to get it to work at all. I'll ask them during our next week's meeting if they remember why but at the time my understanding was that the feature didn't work the way we thought it would/should. Thanks tho! -skye