Closed Bug 1144062 Opened 10 years ago Closed 10 years ago

Contribute to our sites — Mozilla sends welcome mail with invalid reply address

Categories

(www.mozilla.org :: Pages & Content, defect)

Production
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: anaran, Unassigned)

References

()

Details

(Whiteboard: [kb=1695004] )

See: https://www.mozilla.org/en-US/contribute/page/ Details: I send a message for [Other] and suggest to contribute typo and link fixes, requesting to work on right away. The welcome message suggests: If there's a type of activity you're interested in, please feel free to write me back and I'll be happy to help you get started on a project. David My reply to David bounces with 550 5.2.1 The email account that you tried to reach is disabled. mu1si2017965wib.99 - gsmtp I would suggest to do one of * not suggest to write back to that email address, e.g. to submit a bug instead * update to a valid, reachable email address http://mzl.la/1vxCDgA
Thanks Adrian for reporting. David left mozilla last month, the recipient for the Other category should be changed, here is where it is defined in the source code: https://github.com/mozilla/bedrock/blob/master/bedrock/mozorg/email_contribute.py#L75 (pmac, potential "good first bug"?)
Flags: needinfo?(pmac)
We definitely need to fix Bedrock, but I think we also need to update the email address on Exact Target (or whatever the system used by en-US is).
Agreed Pascal. Do we have a new email yet? I'm happy to mentor this one.
Flags: needinfo?(pmac)
Summary: Contribute to our sites — Mozilla sends welome mail with invalid reply address → Contribute to our sites — Mozilla sends welcome mail with invalid reply address
I'll get the new email address. It might take a couple of days.
Whiteboard: [kb=1695004]
We are now pointing to the get involved wiki page for mozorg and the "contribute to this page" page with the old broken form has been deprecated.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.