-
Notifications
You must be signed in to change notification settings - Fork 302
Listserv Signup Options
listname
== the name of the list (e.g. ux-cop
)
-
listname-subscribe-request@listserv.gsa.gov
— Subscribe email -
listname-unsubscribe-request@listserv.gsa.gov
— Unsubscribe un-subscribe -
listname-request@listserv.gsa.gov
— Email to list to owners -
listname@listserv.gsa.gov
— Email the community
Google Form with fallback email (example)
This path uses a Google form. The manager is then responsible for checking that form and manually adding the list in the listerv platform. There is a fallback email for those that do not have access to Google Forms.
Specific listserv sign-up email (example)
This path uses a email associated with the listserv account. Requests sent to this account go into a moderation queue and await approval from a community manager (e.g. ux-cop-request@listserv.gsa.gov
). Many have options to populate subject, body, or both
— though those preferences seem arbitrary.
General listserv sign-up email (example)
This path uses a general email associated with the GSA listserv application (e.g. listserv@listserv.gsa.gov
). Assuming that requests sent to this address go into the right moderation queue based on the email subject, body, or both
where they await approval from a community manager.
Email inbox option (example)
This path uses an inbox or personal account to catch requests (e.g. section.508@gsa.gov
) then it is up to the person(s) behind that account to manually go in to the listserv platform and add the person to the list.
Multi-step option (example)
Requires people to signup for an account on the GSA listserv platform, then go in and sign up themselves. This is a high bar for most people, likely not very accessible, and not an ideal path for users.
What is the easiest path for someone to unsubscribe from a listserv? Can this be automated?
This page needs a review for accuracy and clarity: https://demo.digital.gov/communities/manage-your-subscription/
🎉Questions? Email digitalgov@gsa.gov