Closed aduh95 closed 8 months ago
I don't remember ever receiving anything on this alias, so +1 if it's redundant. Am also open to redirecting to a foundation owned alias, if one exists.
There are references to this alias in the TSC onboarding/offboarding docs.
One other thing, when this was set up there was also a corresponding alias crypto-exports@nodejs.org
which forwarded to this one (crypto-exports@iojs.org
) https://github.com/nodejs/email/pull/104#issuecomment-399282141. I'm not sure if that alias still exists (it's managed by the Linux Foundation and not the Build WG) but if it does this PR will affect it (as it would be forwarding to a non-existent alias).
According to the (now deleted by https://github.com/nodejs/admin/pull/617) us-export-control.md document, it was the crypto-exports@nodejs.org
address which was used.
Lets remove this and ask @bensternthal to make sure that crypto-exports@nodejs.org no longer exists or if needed forwards to somebody at the Foundation.
crypto-exports@nodejs.org bounces, so I can confirm this is not an active email address.
There are references to this alias in the TSC onboarding/offboarding docs.
PR to remove these references: https://github.com/nodejs/TSC/pull/1499
Deployed.
Refs: https://github.com/nodejs/admin/pull/617