"null@topcoder.com" in "Contact Managers" link in OnlineReview

[maxceem]

If a challenge is created using Work Manager, and then someone is using link in Online Review "Contact Managers" an email is also sent to "null@topcoder.com":

As a result, when we "reply all" to such an email Topcoder Mail Server returns an error:

This happens because we are adding tcwebservice as a Manager and Online Review lists emails of all the managers when sending emails.

I'm not sure if there is any way to fix this.

Expected behavior

Don't get an error email when "reply all" to the email generated by the "Contact Managers" link.

[vikasrohit]

@mtwomey @rootelement fyi

[rootelement]

@maxceem what did you create? a task or a challenge? Did you use Work Manager or Topcoder X?

[maxceem]

I have created a challenge using Work Manager. Here is the link to the challenge https://challenges.topcoder.com/projects/14269/challenges/d57c6f7c-2e17-4021-8d5e-5f6c2cc7c97f/view

This is not the first time. For this challenge, I had the same issue https://challenges.topcoder.com/projects/26232/challenges/41c6290b-466f-42b5-b335-1441ddcf9f1b/view

[rootelement]

I've searched:

• All the code related to v5 challenge/resources
• All the code for Work Manager
• All the configs in production

None mention tcwebservice. It's added to the project by the challenge api m2m, which means, i believe, that it's added by legacy v4 challenge api when the challenge is created. Will keep looking

[mtwomey]

We don't have an email address that is valid, but goes nowhere. For example when registering - those emails come from noreply@topcoder.com. However if you reply to it or send an email there you'll get an error.

Is the only expression of this issue is the one described above (someone in OR clicking contact managers)?

[rootelement]

I've confirmed that tcwebservice user is either added by the v4 api when the challenge is created, or by OR/legacy itself, none of the v5 challenge systems. You can see in this log from the v4->v5 sync that the sync noticed that the tcwebservice user that existed in legacy was not in v5, so it added it to v5.