Note on listserv membership and email addresses

Open Beginner friendly
#54 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Start by locating the documentation page for listserv membership or email-removal procedures. Verify the ServiceNow lookup and both hpc-announce deletion steps against the listed ServiceNow and listserv entry points; done when the procedure is published clearly, including the final Ops-team notification.

Written by the indexing model from the issue text.

Description

If a user is subscribed to hpc-announce using their @uab.edu email address, then it appears that emails may also be sent to their "User Supplied Email" address as well. This value can be checked in ServiceNow.

So, if you see they are requesting to have a non-UAB email removed from hpc-announce, here is the procedure. The goal of this procedure is to ensure both the requested non-UAB email and UAB email are checked and removed.

  1. Go to ServiceNow and search for the requested email.
  2. You should see one user appear, if more than one then proceed with caution and ensure you select the correct one!
  3. Open the user page.
  4. Make sure that the requested email is in the "User Supplied Email" field.
  5. Make note of their primary UAB email address.
  6. Go to listserv.uab.edu and go to the hpc-announce page.
  7. Click "Subscriber Management" in the left-hand pane.
  8. Search for the requested email. If it appears, click the "delete" button to remove it.
  9. Search for the UAB email. If it appears, click the "delete" button to remove it.
  10. Inform the Ops team to have their RC account put on hold.
Dominant language
Python
Stars
1
Forks
9
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from uabrc/devops-docs

All issues in uabrc/devops-docs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.