UVLists - User contributions [en]

UVLists:In the news

2026-10-24T15:20:36Z

UVListsBot: Add Vermont Standard story of October 8, 2026

UVLists is a volunteer group that keeps the Upper Valley's community email lists running. This page collects stories about UVLists in newspapers, on radio, and in other media. For our own announcements, see [[News]].

Are you a reporter? Email [mailto:hello@uvlists.org hello@uvlists.org].

== Stories ==

If you have seen UVLists mentioned in the news, email [mailto:hello@uvlists.org hello@uvlists.org] with a link.

=== 2026 ===

==== October ====

* '''October 24, 2026''', ''Upper Valley VT/NH Musings'' (Dave Celone): [https://uppervalleyvtnh.substack.com/p/upper-valleys-listserv-superstars "Upper Valley's LISTSERV Superstars"] How volunteers formed UVLists to keep 38 town email lists running after Vital Communities, and what subscribers need to do during the move.
* '''October 8, 2026''', ''The Vermont Standard'' (Erin Scott): [https://vermontstandard-vt.newsmemory.com/?publink=24f56b610_13522b4 "Upper Valley town listservs to continue under new nonprofit"] Covers UVLists' October 1 agreement with Vital Communities to take over the 38 town lists, which move to the uvlists.org domain but otherwise work much as before.
* '''October 2, 2026''', ''WCAX'': [https://www.wcax.com/2026/10/02/nonprofit-takes-over-popular-upper-valley-online-forum/ "Nonprofit takes over popular Upper Valley online forum"] Reports that UVLists will take over the Upper Valley email lists from Vital Communities and keep them running as they do now.

==== August ====

* '''August 27, 2026''', ''WCAX'' (Adam Sullivan): [https://www.wcax.com/2026/08/27/popular-upper-valley-online-forum-will-not-shut-down/ "Popular Upper Valley online forum will not shut down"] Vital Communities drops its shutdown plan and starts working with past list managers on an independent host, the effort that became UVLists.
* '''August 25, 2026''', ''Daybreak'' (Rob Gurwitt): [https://news.daybreak.news/p/daybreak-tuesday-8-25-26 "Daybreak Tuesday, 8/25/26"], item "Listservs' future still in limbo" Vital Communities says it will keep hosting the town lists to give the moderators' group, now UVLists, time to organize, and is getting legal advice on sharing subscriber data.
* '''August 21, 2026''', ''Daybreak'' (Rob Gurwitt): [https://news.daybreak.news/p/update-on-the-listservs-vital-communities-says-it-won-t-pull-the-plug-just-yet "Update on the Listservs: Vital Communities Says It Won't Pull the Plug Just Yet"] Vital Communities keeps the town lists running past its deadline after a day of pushback, while list moderators push for another organization to take them over, the start of UVLists.
* '''August 21, 2026''', ''WCAX'' (Adam Sullivan): [https://www.wcax.com/2026/08/21/upper-valley-listserv-shutdown-postponed-amid-community-pushback/ "Upper Valley LISTSERV shutdown postponed amid community pushback"] Background, before UVLists formed: Vital Communities pauses its plan to shut down the 38 town lists after pushback from subscribers.

[[Category:News]]

UVLists:In the news

2026-10-24T15:11:29Z

UVListsBot: Add Daybreak item of August 25, 2026

UVLists is a volunteer group that keeps the Upper Valley's community email lists running. This page collects stories about UVLists in newspapers, on radio, and in other media. For our own announcements, see [[News]].

Are you a reporter? Email [mailto:hello@uvlists.org hello@uvlists.org].

== Stories ==

If you have seen UVLists mentioned in the news, email [mailto:hello@uvlists.org hello@uvlists.org] with a link.

=== 2026 ===

==== October ====

* '''October 24, 2026''', ''Upper Valley VT/NH Musings'' (Dave Celone): [https://uppervalleyvtnh.substack.com/p/upper-valleys-listserv-superstars "Upper Valley's LISTSERV Superstars"] How volunteers formed UVLists to keep 38 town email lists running after Vital Communities, and what subscribers need to do during the move.
* '''October 2, 2026''', ''WCAX'': [https://www.wcax.com/2026/10/02/nonprofit-takes-over-popular-upper-valley-online-forum/ "Nonprofit takes over popular Upper Valley online forum"] Reports that UVLists will take over the Upper Valley email lists from Vital Communities and keep them running as they do now.

==== August ====

* '''August 27, 2026''', ''WCAX'' (Adam Sullivan): [https://www.wcax.com/2026/08/27/popular-upper-valley-online-forum-will-not-shut-down/ "Popular Upper Valley online forum will not shut down"] Vital Communities drops its shutdown plan and starts working with past list managers on an independent host, the effort that became UVLists.
* '''August 25, 2026''', ''Daybreak'' (Rob Gurwitt): [https://news.daybreak.news/p/daybreak-tuesday-8-25-26 "Daybreak Tuesday, 8/25/26"], item "Listservs' future still in limbo" Vital Communities says it will keep hosting the town lists to give the moderators' group, now UVLists, time to organize, and is getting legal advice on sharing subscriber data.
* '''August 21, 2026''', ''Daybreak'' (Rob Gurwitt): [https://news.daybreak.news/p/update-on-the-listservs-vital-communities-says-it-won-t-pull-the-plug-just-yet "Update on the Listservs: Vital Communities Says It Won't Pull the Plug Just Yet"] Vital Communities keeps the town lists running past its deadline after a day of pushback, while list moderators push for another organization to take them over, the start of UVLists.
* '''August 21, 2026''', ''WCAX'' (Adam Sullivan): [https://www.wcax.com/2026/08/21/upper-valley-listserv-shutdown-postponed-amid-community-pushback/ "Upper Valley LISTSERV shutdown postponed amid community pushback"] Background, before UVLists formed: Vital Communities pauses its plan to shut down the 38 town lists after pushback from subscribers.

[[Category:News]]

UVLists:In the news

2026-10-24T15:10:10Z

UVListsBot: Add Daybreak story of August 21, 2026

UVLists is a volunteer group that keeps the Upper Valley's community email lists running. This page collects stories about UVLists in newspapers, on radio, and in other media. For our own announcements, see [[News]].

Are you a reporter? Email [mailto:hello@uvlists.org hello@uvlists.org].

== Stories ==

If you have seen UVLists mentioned in the news, email [mailto:hello@uvlists.org hello@uvlists.org] with a link.

=== 2026 ===

==== October ====

* '''October 24, 2026''', ''Upper Valley VT/NH Musings'' (Dave Celone): [https://uppervalleyvtnh.substack.com/p/upper-valleys-listserv-superstars "Upper Valley's LISTSERV Superstars"] How volunteers formed UVLists to keep 38 town email lists running after Vital Communities, and what subscribers need to do during the move.
* '''October 2, 2026''', ''WCAX'': [https://www.wcax.com/2026/10/02/nonprofit-takes-over-popular-upper-valley-online-forum/ "Nonprofit takes over popular Upper Valley online forum"] Reports that UVLists will take over the Upper Valley email lists from Vital Communities and keep them running as they do now.

==== August ====

* '''August 27, 2026''', ''WCAX'' (Adam Sullivan): [https://www.wcax.com/2026/08/27/popular-upper-valley-online-forum-will-not-shut-down/ "Popular Upper Valley online forum will not shut down"] Vital Communities drops its shutdown plan and starts working with past list managers on an independent host, the effort that became UVLists.
* '''August 21, 2026''', ''Daybreak'' (Rob Gurwitt): [https://news.daybreak.news/p/update-on-the-listservs-vital-communities-says-it-won-t-pull-the-plug-just-yet "Update on the Listservs: Vital Communities Says It Won't Pull the Plug Just Yet"] Vital Communities keeps the town lists running past its deadline after a day of pushback, while list moderators push for another organization to take them over, the start of UVLists.
* '''August 21, 2026''', ''WCAX'' (Adam Sullivan): [https://www.wcax.com/2026/08/21/upper-valley-listserv-shutdown-postponed-amid-community-pushback/ "Upper Valley LISTSERV shutdown postponed amid community pushback"] Background, before UVLists formed: Vital Communities pauses its plan to shut down the 38 town lists after pushback from subscribers.

[[Category:News]]

UVLists:In the news

2026-10-24T15:09:20Z

UVListsBot: Add WCAX story of August 27, 2026

UVLists:In the news

2026-10-24T15:06:38Z

UVListsBot: Group stories by month

News

2026-10-24T15:06:37Z

UVListsBot: Undo grouping by year and month (meant for UVLists:In the news)

== News Updates and Announcements from UVLists ==

For stories about UVLists in local newspapers, radio and other media, see [[UVLists:In the news|UVLists in the news]].

All news, updates and announcements are also published to the [https://mailman.ops.uvlists.org/postorius/lists/uvlists-announce.uvlists.org/ UVLists Announce Mailing List].

=== [[news/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists | UVLists and Vital Communities Reach An Agreement regarding transitions of Upper Valley Lists]] ===
''October 2, 2026'' 
{{:news/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists}}
 
[[news/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists|Read more →]]

=== [[news/uvlists-announce-announcement-list|UVLists-Announce Announcement List]] ===
''September 12, 2026'' 
{{:news/uvlists-announce-announcement-list}}
 
[[news/uvlists-announce-announcement-list|Read more →]]

=== [[news/committee-members-needed|Committee members needed!]] ===
''August 27, 2026'' 
{{:news/committee-members-needed}}
 
[[news/committee-members-needed|Read more →]]

=== [[news/memorandum-of-understanding|Memorandum of Understanding for Vital Communities Community Email Lists]] ===
''August 26, 2026'' 
{{:news/memorandum-of-understanding}}
 
[[news/memorandum-of-understanding|Read more →]]

=== [[news/hello-world|Hello World!]] ===
''August 26, 2026'' 
{{:news/hello-world}}
 
[[news/hello-world|Read more →]]

[[Category:news]]

News

2026-10-24T15:05:15Z

UVListsBot: Group news by year and month

== News Updates and Announcements from UVLists ==

For stories about UVLists in local newspapers, radio and other media, see [[UVLists:In the news|UVLists in the news]].

All news, updates and announcements are also published to the [https://mailman.ops.uvlists.org/postorius/lists/uvlists-announce.uvlists.org/ UVLists Announce Mailing List].

=== 2026 ===

==== October ====

===== [[news/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists | UVLists and Vital Communities Reach An Agreement regarding transitions of Upper Valley Lists]] =====
''October 2, 2026'' 
{{:news/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists}}
 
[[news/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists|Read more →]]

==== September ====

===== [[news/uvlists-announce-announcement-list|UVLists-Announce Announcement List]] =====
''September 12, 2026'' 
{{:news/uvlists-announce-announcement-list}}
 
[[news/uvlists-announce-announcement-list|Read more →]]

==== August ====

===== [[news/committee-members-needed|Committee members needed!]] =====
''August 27, 2026'' 
{{:news/committee-members-needed}}
 
[[news/committee-members-needed|Read more →]]

===== [[news/memorandum-of-understanding|Memorandum of Understanding for Vital Communities Community Email Lists]] =====
''August 26, 2026'' 
{{:news/memorandum-of-understanding}}
 
[[news/memorandum-of-understanding|Read more →]]

===== [[news/hello-world|Hello World!]] =====
''August 26, 2026'' 
{{:news/hello-world}}
 
[[news/hello-world|Read more →]]

[[Category:news]]

Contact

2026-10-24T15:04:48Z

UVListsBot: Add donate@ for donations and fundraising

== Contact UVLists ==

Have a question, need help, or want to report a problem? Email the address that best fits your message. UVLists is maintained by volunteers; messages are tracked so that the right person can follow up.

== What happens when you contact us? ==

UVLists uses '''Request Tracker (RT)''', a helpdesk system that keeps each request and its replies together in a ticket. After you email us, you may receive a reply with a ticket number in the subject line. You can simply reply to that message; keeping the ticket number in the subject helps us keep the conversation together and prevents requests from being missed or answered twice.

=== General questions and list support ===

For questions about UVLists, help using a community list, or a problem that does not fit one of the categories below, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org].

When asking about a mailing list, include the list name and the email address affected. For delivery problems, include the approximate date and time of a missing or rejected message, if known.

=== Donations and fundraising ===

To ask about donating to UVLists, a gift you have already made, or a receipt for your records, email [mailto:donate@uvlists.org donate@uvlists.org].

=== Website and wiki ===

To report a problem with this website or the UVLists wiki, suggest a correction, or request help with an editor account, email [mailto:webmaster@uvlists.org webmaster@uvlists.org].

=== Abuse, spam, or harassment ===

To report spam, harassment, misuse of a list, or another safety concern, email [mailto:abuse@uvlists.org abuse@uvlists.org]. Include the list name, relevant message headers or links, and a brief description of the issue. Please do not send passwords or other sensitive account credentials.

=== Systems and technical issues ===

For infrastructure, mail-system, or other technical operational issues, email [mailto:sysadmins@uvlists.org sysadmins@uvlists.org].

=== List-specific questions ===

For questions about the rules, moderation, or local purpose of a particular community list, use the owner-contact address shown on that list’s information page. Visit the [[:Category:Mailing lists|list directory]] to find the right page.

== A note about replies ==

Please keep the ticket reference in the subject line when replying to a UVLists support message. This keeps the conversation together and helps the volunteer team respond efficiently.

UVLists:In the news

2026-10-24T15:03:41Z

UVListsBot: Add two WCAX stories

UVLists:In the news

2026-10-24T15:01:51Z

UVListsBot: Add Dave Celone's Substack article

UVLists:About

2026-10-24T14:56:00Z

UVListsBot: Link to UVLists in the news

'''UVLists''' (short for ''Upper Valley Lists'') is a volunteer-run nonprofit based in South Royalton, Vermont. We look after the town email discussion lists that neighbors across the Upper Valley of Vermont and New Hampshire have relied on for more than twenty years.

Our mission is to preserve locally controlled online community discussion forums throughout the Upper Valley.

== What we do ==

UVLists runs 38 town discussion lists, from Barnard to Woodstock. Each list is a shared email conversation for one community: a place to find a lost pet, recommend a plumber, sell a couch, read the select board agenda, or hear about a road closure.

* '''The lists are local.''' Each list serves one town, and its guidelines ask that posts relate to that town, be signed, and stay civil.
* '''The lists are run by neighbors.''' Each list is looked after by volunteer list administrators from its own community, with support from UVLists.
* '''The lists are free and ad-free.''' There is no advertising, and subscriber information is used only to run the lists. It is never sold.
* '''The lists work through email.''' You do not need a social media account, an app, or a password. Just the email address you already have.

The lists run on open-source software (GNU Mailman) on servers maintained by UVLists volunteers.

== Our history ==

=== ValleyNet and the first lists (1994 to 2014) ===

The town lists trace their roots to '''ValleyNet''', which introduced local dial-up internet service to the Upper Valley in 1994. In 2004, ValleyNet took over the Thetford list. From there, the free discussion lists spread from town to town, eventually covering 38 towns and more than 21,000 subscribers.

The lists soon became part of everyday life, and at times much more than that:

* In '''2008''', the lists were an important tool in getting '''ECFiber''' started, when 24 towns voted at town meeting to join the community broadband network.
* After '''Tropical Storm Irene''' in 2011, the lists were critical in coordinating volunteer recovery efforts.
* Towns came to use them to post agendas, minutes, and road closures, and nonprofits and emergency services used them to reach their neighbors.

=== The Vital Communities years (2014 to 2026) ===

In '''2014''', '''Vital Communities''', a regional nonprofit, took over administration of the lists from ValleyNet and stewarded them for more than a decade. Throughout, each list continued to be run day to day by volunteer list administrators. Together, list administrators past and present have given an estimated '''75,000 hours''' of volunteer time since 2004 to keep the lists local, civil, and non-commercial.

=== UVLists is formed (2026) ===

In August 2026, word came that the town lists might close. A concerned group of list administrators, some of whom had looked after their town's list for many years, began discussing the future of the lists and how to keep them running in community hands. Longtime subscribers joined the conversation, and offers of help poured in from across the Upper Valley. That group became UVLists.

* '''August 23, 2026''': UVLists published its first website, explaining who was involved and what a handoff would take.
* '''August 24''': UVLists met with Vital Communities to talk about keeping the lists online.
* '''August 27''': An ad hoc executive committee of list administrators and volunteers sent Vital Communities a proposed [[News/memorandum-of-understanding|memorandum of understanding]] that drew on the thoughts of all 38 list administrators. The same day, UVLists put out a [[News/committee-members-needed|call for committee members]].
* '''September 12''': The [[News/uvlists-announce-announcement-list|UVLists-Announce list]] began sharing news with the public.
* '''September 30''': At its first [[Meetings|board meeting]], UVLists elected officers, adopted its bylaws, and approved a transition agreement with Vital Communities.
* '''October 1''': UVLists and Vital Communities [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists|signed the transition agreement]], under which UVLists took over administration of the 38 town lists.
* '''Late October''': UVLists began [[Vital Communities List Migration|moving each list]] to its own system. Every town list was given a new address ending in ''-discuss@lists.uvlists.org'' (see [[Vital Communities List Migration/Renaming Lists|Renaming Lists]]), and subscribers came along with their existing delivery settings.

'''ECFiber''', whose own start the lists helped make possible, became a key sponsor of UVLists.

Vital Communities continues to run its Upper Valley-wide and topic lists, which were not part of the transition.

We are grateful to ValleyNet and Vital Communities for their many years of stewardship, and above all to the volunteer list administrators who have kept these lists going all along.

== What comes next ==

For now, our first job is to keep the lists working the way people know them. Over time, we hope to help communities do more with them: for example, giving a town separate lists for announcements, discussion, or items for sale, if its residents want that.

UVLists plans to hold its first annual meeting by January 31, 2027, and to begin asking subscribers for financial support in early 2027.

== Who we are ==

UVLists, Inc. is led by a volunteer board of directors and officers, listed on the [[Executive Committee]] page. The day-to-day work is done by volunteers: list administrators, moderators, and people who help with the technical systems, this wiki, and outreach.

UVLists is always looking for more help. See [[UVLists:Get involved|Get involved]].

== Learn more ==

* [[UVLists:Governance|How decisions are made]]
* [[Meetings|Meeting agendas and minutes]]
* [[News|News and announcements]]
* [[UVLists:In the news|UVLists in the news]]
* [[UVLists:Get involved|Get involved]]
* [[Contact|Contact UVLists]]

'''Mailing address:''' UVLists, Inc., 95 S Windsor Street, P.O. Box 934, South Royalton, Vermont 05068

Welcome to UVLists

2026-10-24T14:56:00Z

UVListsBot: Link to UVLists in the news from the news box

'''Neighbors helping neighbors, one email at a time.'''

{{Warning
|title=List Migration is starting soon!
|1=As part of the [[Vital Communities List Migration|migration from Vital Communities]], we will be starting migration of existing lists hosted with Vital Communities to UVLists. Some information contained in this wiki may be slightly out of date or incomplete until migration is complete.
}}

<div class="uvlists-news">
==== UVLists News ====
* [[news/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists | October 2, 2026 - UVLists and Vital Communities Reach An Agreement]]
* [[news/uvlists-announce-announcement-list|September 12, 2026 - UVLists-Announce Announcement List]]
* [[news/committee-members-needed|August 27, 2026 - Committee members needed!]]
* [[news/memorandum-of-understanding|August 26, 2026 - Memorandum of Understanding for Vital Communities Community Email Lists]]
* [[news/hello-world|August 26, 2026 - Hello World!]]
[[News|All news and announcements →]] [[UVLists:In the news|UVLists in the news →]]
</div>

UVLists helps people across the Upper Valley stay connected through local email discussion lists. Ask for a plumber recommendation, share a community supper, find a home for something you no longer need, or catch up on what’s happening around town.

No ads. No social media account. Just email from your community.

'''[[:Category:Mailing lists|Find Your List]] · [[Help:Getting started|How it works]] · [[Help:Contents|Get help]]'''

== New here? ==

A mailing list is a shared email conversation. When someone sends a message to the list, it reaches the people subscribed to it. You can read and participate from the email account you already use.

Start with the [[:Category:Mailing lists | list directory]]. Each list has a page explaining who it serves, how to join, and its posting guidelines.

Already subscribed? Keep using your email as usual. This website is here when you need instructions, information about your list, or a little help.

== Looking for something? ==

* '''[[Help:Subscribing|Join a list]]''' - Find out how to subscribe.
* '''[[Help:Posting|Send a message]]''' - Learn how to post to your community.
* '''[[Help:Unsubscribing|Leave a list]]''' - Get unsubscribe instructions.
* '''[[Help:Delivery problems|Missing messages?]]''' - Troubleshoot email delivery.
* '''[[Help:FAQ|Common questions]]''' - Short answers to frequently asked questions.
* '''[[Contact|Contact us]]''' - Ask a question or report a problem.

== Local conversations, local care ==

Each list has its own character. Volunteer list administrators help keep conversations useful and look after the guidelines for their community.

Before posting, take a moment to read your list’s guidelines. A clear subject line, a little context, and consideration for your neighbors go a long way.

== About UVLists ==

UVLists grew out of the effort to carry forward the regional mailing lists supported by Vital Communities and keep them under community stewardship.

These lists matter because people use them: to lend a hand, exchange local knowledge, share news, and make everyday life a little easier. Our job is to keep that connection dependable and straightforward.

We aim to do our work openly. You can read about [[UVLists:About|the project]], follow [[UVLists:Governance|how decisions are made]], and find out [[UVLists:Get involved|how to help]].

== For list administrators ==

The [[ListAdmin:Overview|list administrator guide]] brings together instructions for moderation, subscriber support, and maintaining your list’s documentation. Shared guidance lives in one place, alongside the pages for each individual list.

You don’t need an account to read this site. List administrators and other authorized editors sign in to keep the information up to date.

News

2026-10-24T14:55:59Z

UVListsBot: Link to UVLists in the news

UVLists:In the news

2026-10-24T14:55:59Z

UVListsBot: Create a page for media coverage of UVLists

Vital Communities List Migration

2026-10-23T02:50:20Z

UVListsBot: Mark lists announced on October 22, 2026 as Announced

== Overview ==

As described in [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists]], UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.

Common questions are answered in the [[Vital Communities List Migration/FAQ|list migration FAQ]]. For help with a migration or a question about a particular list, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org]. Other addresses are on the [[Contact|Contact UVLists]] page.

== What subscribers need to do ==

Subscribers do not need to take action to move to the new UVLists list. Unless they unsubscribe from the Vital Communities list before its '''Cutover Date''', their subscription and delivery preference will be transferred. After the move, use the new list address shown on the list’s UVLists page.

== Before your list moves ==

A few minutes of preparation helps the new list's messages reach your inbox instead of your spam folder.

# '''Add the new list to your contacts.''' Every list has a ready-made contact card. Open the list's page from the table below, find '''VCard File''' in the '''Mailing List Info''' box, and select the link. You can also get the card from the list's short page at <code>go.uvlists.org</code> (for example, <code><nowiki>https://go.uvlists.org/norwich</nowiki></code>). With the card saved, your email program fills in the correct new address when you write to the list.
# '''Mark UVLists mail as safe.''' If your email service has a safe senders or approved senders list, add <code>lists.uvlists.org</code> to it.
# '''Check your spam folder after the cutover date.''' If a list message lands there, mark it as ''not spam''. Your email service learns from this.

For step-by-step help, see [[Help:Subscribing|Subscribing]] and [[Help:Delivery problems|Delivery problems]]. If something still is not working, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org].

== What list administrators need to do ==

List administrators should review the list’s public page for accuracy, including its purpose, guidelines, owner-contact address, and joining instructions. The [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] explains what to check and how to submit corrections.

== Migration schedule ==

The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.

The status column uses these terms:

{| class="wikitable"
! Status
! Meaning
|-
| Not migrated
| Migration has not started.
|-
| Announced
| Existing Vital Communities subscribers have been notified and can opt out before the cutover date. The new list is available for subscriptions but not yet for posting.
|-
| Migrated
| The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address.
|-
| Complete
| The prior Vital Communities list has been fully retired.
|}

{| class="wikitable sortable"
|+ Migration Schedule
|-
! VC List !! UVL List !! Announcement Date !! Cutover Date !! Current Status
|-
| barnard@lists.vitalcommunities.org || [[Lists:Barnard]] || October 20, 2026 || October 27, 2026 || Announced
|-
| bradford@lists.vitalcommunities.org || [[Lists:Bradford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| bridgewater@lists.vitalcommunities.org || [[Lists:Bridgewater]] || October 20, 2026 || October 27, 2026 || Announced
|-
| brownsville@lists.vitalcommunities.org || [[Lists:Brownsville]] || October 21, 2026 || October 28, 2026 || Announced
|-
| chelsea@lists.vitalcommunities.org || [[Lists:Chelsea]] || October 21, 2026 || October 28, 2026 || Announced
|-
| claremont@lists.vitalcommunities.org || [[Lists:Claremont]] || October 21, 2026 || October 28, 2026 || Announced
|-
| enfield@lists.vitalcommunities.org || [[Lists:Enfield]] || October 21, 2026 || October 28, 2026 || Announced
|-
| fairlee@lists.vitalcommunities.org || [[Lists:Fairlee]] || October 20, 2026 || October 27, 2026 || Announced
|-
| grafton@lists.vitalcommunities.org || [[Lists:Grafton]] || October 21, 2026 || October 28, 2026 || Announced
|-
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Announced
|-
| groton_area@lists.vitalcommunities.org || [[Lists:Groton]] || October 21, 2026 || October 28, 2026 || Announced
|-
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Announced
|-
| hartford@lists.vitalcommunities.org || [[Lists:Hartford]] || October 22, 2026 || October 29, 2026 || Announced
|-
| haverhill@lists.vitalcommunities.org || [[Lists:Haverhill]] || October 22, 2026 || October 29, 2026 || Announced
|-
| lebanon@lists.vitalcommunities.org || [[Lists:Lebanon]] || October 22, 2026 || October 29, 2026 || Announced
|-
| lyme@lists.vitalcommunities.org || [[Lists:Lyme]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| mascoma@lists.vitalcommunities.org || [[Lists:Mascoma]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| newbury@lists.vitalcommunities.org || [[Lists:Newbury]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| norwich@lists.vitalcommunities.org || [[Lists:Norwich]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| orford@lists.vitalcommunities.org || [[Lists:Orford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| piermont@lists.vitalcommunities.org || [[Lists:Piermont]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| plainfield@lists.vitalcommunities.org || [[Lists:Plainfield]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| pomfret@lists.vitalcommunities.org || [[Lists:Pomfret]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| reading@lists.vitalcommunities.org || [[Lists:Reading]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| royalton@lists.vitalcommunities.org || [[Lists:Royalton]] || October 20, 2026 || October 27, 2026 || Announced
|-
| ryegate@lists.vitalcommunities.org || [[Lists:Ryegate]] || October 20, 2026 || October 27, 2026 || Announced
|-
| sharon@lists.vitalcommunities.org || [[Lists:Sharon]] || October 22, 2026 || October 29, 2026 || Announced
|-
| strafford@lists.vitalcommunities.org || [[Lists:Strafford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| thetford@lists.vitalcommunities.org || [[Lists:Thetford]] || October 21, 2026 || October 28, 2026 || Announced
|-
| tunbridge@lists.vitalcommunities.org || [[Lists:Tunbridge]] || October 21, 2026 || October 28, 2026 || Announced
|-
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Announced
|-
| west_fairlee@lists.vitalcommunities.org || [[Lists:West Fairlee]] || October 21, 2026 || October 28, 2026 || Announced
|-
| west_lebanon@lists.vitalcommunities.org || [[Lists:West Lebanon]] || October 22, 2026 || October 29, 2026 || Announced
|-
| west_newbury@lists.vitalcommunities.org || [[Lists:West Newbury]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| west_norwich@lists.vitalcommunities.org || [[Lists:West Norwich]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Announced
|}

Each linked UVLists list page includes its new address, joining instructions, and local guidelines.

== Not yet scheduled ==

{| class="wikitable"
! Vital Communities list
! Planning status
|-
| woodstock@lists.vitalcommunities.org
| List page in preparation; schedule to be determined.
|}

== Migration process ==

Each list follows this general process. The communication templates should be reviewed and updated with the list’s specific dates, addresses, and contacts before they are sent.

# '''Announce the move.''' On the '''Announcement Date''', send the [[Vital Communities List Migration/01-move-announcement|move announcement]] to the existing list. It explains the new list, the opt-out process, and the planned cutover date.
# '''Review list information and allow opt-out.''' List administrators receive the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the '''Cutover Date'''.
# '''Cut over the list.''' On the '''Cutover Date''', send the [[Vital Communities List Migration/03-closure-announcement|closure announcement]] to remaining subscribers. Place the previous list in '''moderated mode''' so new posts are not distributed, and enable the [[Vital Communities List Migration/05-old-list-autoresponse|old-list autoresponse]] to direct senders to the new list for the period set for that migration.
# '''Transfer subscribers and welcome them.''' Import subscribers who did not opt out, including their delivery preferences. Then send the [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] with information about the list, its moderators, and where to get help.

[[Category:List Migration]]

Vital Communities List Migration/FAQ

2026-10-22T23:20:51Z

UVListsBot: Answer: old archives are migrated

Questions about the move of community email lists from Vital Communities to UVLists. For the schedule and the process, see [[Vital Communities List Migration]]. For questions about using the lists day to day, see the [[Help:FAQ|general FAQ]].

== The move ==

=== Why are the lists moving? ===
Vital Communities and UVLists agreed to move the Upper Valley community email lists to UVLists. See the [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists|announcement]].

=== Is UVLists part of Vital Communities? ===
No. UVLists is a separate Vermont nonprofit run by volunteers. See [[UVLists:About|About UVLists]].

=== Is it still the same list? ===
Yes. The subscribers, the purpose, the guidelines, and the volunteers who run it stay the same. Only the name, the address, and the service change. See [[Vital Communities List Migration/Renaming Lists|Renaming Lists]].

=== When does my list move? ===
Each list has an announcement date and a cutover date. See the [[Vital Communities List Migration#Migration schedule|migration schedule]].

== Subscribers ==

=== Do I need to resubscribe? ===
No. Unless you unsubscribe from the Vital Communities list before its cutover date, your subscription moves to UVLists automatically, along with your choice of digest or individual messages.

=== Will the old messages move too? ===
Yes. The complete archive of each Vital Communities list is being moved and added to the archive of its new list on UVLists, so past messages and new ones will be in one place.

=== I do not want to move to UVLists ===
Unsubscribe from the Vital Communities list before its cutover date. If your list has already moved, you can leave the new list at any time. See [[Help:Unsubscribing|Leave a list]].

=== What is my list's new address? ===
Town lists now end in ''-discuss''. For example, the Norwich list's address is <code>norwich-discuss@lists.uvlists.org</code>. Each list's page in the [[:Category:Mailing lists|list directory]] shows its new addresses.

=== Can I post to the new list before the cutover date? ===
Not yet. Once a list is announced you can subscribe to the new list, but posting opens on the cutover date.

=== What happens if I write to the old address? ===
After the cutover date, mail sent to the old <code>@lists.vitalcommunities.org</code> address gets an automatic reply with the new address. Your message is not passed along, so send it again to the new address and update your contacts.

=== How do I keep the new list's messages out of my spam folder? ===
Add the list to your contacts using its contact card, and mark <code>lists.uvlists.org</code> as a safe sender. See [[Vital Communities List Migration#Before your list moves|Before your list moves]].

=== I stopped getting messages after my list moved ===
Check your spam folder first. See [[Help:Delivery problems|Delivery problems]], or email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org].

== List administrators ==

=== What do list administrators need to do? ===
Review your list's page on this wiki and send any corrections. See the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] and the [[ListAdmin:Overview|list administrator guide]].

== Still need help? ==

Email '''[mailto:helpdesk@uvlists.org helpdesk@uvlists.org]'''. Please include the name of your list and the email address you subscribed with.

[[Category:List Migration]]

Vital Communities List Migration

2026-10-22T23:13:27Z

UVListsBot: Link list migration FAQ

== Overview ==

As described in [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists]], UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.

Common questions are answered in the [[Vital Communities List Migration/FAQ|list migration FAQ]]. For help with a migration or a question about a particular list, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org]. Other addresses are on the [[Contact|Contact UVLists]] page.

== What subscribers need to do ==

Subscribers do not need to take action to move to the new UVLists list. Unless they unsubscribe from the Vital Communities list before its '''Cutover Date''', their subscription and delivery preference will be transferred. After the move, use the new list address shown on the list’s UVLists page.

== Before your list moves ==

A few minutes of preparation helps the new list's messages reach your inbox instead of your spam folder.

# '''Add the new list to your contacts.''' Every list has a ready-made contact card. Open the list's page from the table below, find '''VCard File''' in the '''Mailing List Info''' box, and select the link. You can also get the card from the list's short page at <code>go.uvlists.org</code> (for example, <code><nowiki>https://go.uvlists.org/norwich</nowiki></code>). With the card saved, your email program fills in the correct new address when you write to the list.
# '''Mark UVLists mail as safe.''' If your email service has a safe senders or approved senders list, add <code>lists.uvlists.org</code> to it.
# '''Check your spam folder after the cutover date.''' If a list message lands there, mark it as ''not spam''. Your email service learns from this.

For step-by-step help, see [[Help:Subscribing|Subscribing]] and [[Help:Delivery problems|Delivery problems]]. If something still is not working, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org].

== What list administrators need to do ==

List administrators should review the list’s public page for accuracy, including its purpose, guidelines, owner-contact address, and joining instructions. The [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] explains what to check and how to submit corrections.

== Migration schedule ==

The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.

The status column uses these terms:

{| class="wikitable"
! Status
! Meaning
|-
| Not migrated
| Migration has not started.
|-
| Announced
| Existing Vital Communities subscribers have been notified and can opt out before the cutover date. The new list is available for subscriptions but not yet for posting.
|-
| Migrated
| The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address.
|-
| Complete
| The prior Vital Communities list has been fully retired.
|}

{| class="wikitable sortable"
|+ Migration Schedule
|-
! VC List !! UVL List !! Announcement Date !! Cutover Date !! Current Status
|-
| barnard@lists.vitalcommunities.org || [[Lists:Barnard]] || October 20, 2026 || October 27, 2026 || Announced
|-
| bradford@lists.vitalcommunities.org || [[Lists:Bradford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| bridgewater@lists.vitalcommunities.org || [[Lists:Bridgewater]] || October 20, 2026 || October 27, 2026 || Announced
|-
| brownsville@lists.vitalcommunities.org || [[Lists:Brownsville]] || October 21, 2026 || October 28, 2026 || Announced
|-
| chelsea@lists.vitalcommunities.org || [[Lists:Chelsea]] || October 21, 2026 || October 28, 2026 || Announced
|-
| claremont@lists.vitalcommunities.org || [[Lists:Claremont]] || October 21, 2026 || October 28, 2026 || Announced
|-
| enfield@lists.vitalcommunities.org || [[Lists:Enfield]] || October 21, 2026 || October 28, 2026 || Announced
|-
| fairlee@lists.vitalcommunities.org || [[Lists:Fairlee]] || October 20, 2026 || October 27, 2026 || Announced
|-
| grafton@lists.vitalcommunities.org || [[Lists:Grafton]] || October 21, 2026 || October 28, 2026 || Announced
|-
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| groton_area@lists.vitalcommunities.org || [[Lists:Groton]] || October 21, 2026 || October 28, 2026 || Announced
|-
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| hartford@lists.vitalcommunities.org || [[Lists:Hartford]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| haverhill@lists.vitalcommunities.org || [[Lists:Haverhill]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| lebanon@lists.vitalcommunities.org || [[Lists:Lebanon]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| lyme@lists.vitalcommunities.org || [[Lists:Lyme]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| mascoma@lists.vitalcommunities.org || [[Lists:Mascoma]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| newbury@lists.vitalcommunities.org || [[Lists:Newbury]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| norwich@lists.vitalcommunities.org || [[Lists:Norwich]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| orford@lists.vitalcommunities.org || [[Lists:Orford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| piermont@lists.vitalcommunities.org || [[Lists:Piermont]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| plainfield@lists.vitalcommunities.org || [[Lists:Plainfield]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| pomfret@lists.vitalcommunities.org || [[Lists:Pomfret]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| reading@lists.vitalcommunities.org || [[Lists:Reading]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| royalton@lists.vitalcommunities.org || [[Lists:Royalton]] || October 20, 2026 || October 27, 2026 || Announced
|-
| ryegate@lists.vitalcommunities.org || [[Lists:Ryegate]] || October 20, 2026 || October 27, 2026 || Announced
|-
| sharon@lists.vitalcommunities.org || [[Lists:Sharon]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| strafford@lists.vitalcommunities.org || [[Lists:Strafford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| thetford@lists.vitalcommunities.org || [[Lists:Thetford]] || October 21, 2026 || October 28, 2026 || Announced
|-
| tunbridge@lists.vitalcommunities.org || [[Lists:Tunbridge]] || October 21, 2026 || October 28, 2026 || Announced
|-
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| west_fairlee@lists.vitalcommunities.org || [[Lists:West Fairlee]] || October 21, 2026 || October 28, 2026 || Announced
|-
| west_lebanon@lists.vitalcommunities.org || [[Lists:West Lebanon]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| west_newbury@lists.vitalcommunities.org || [[Lists:West Newbury]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| west_norwich@lists.vitalcommunities.org || [[Lists:West Norwich]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Announced
|}

Each linked UVLists list page includes its new address, joining instructions, and local guidelines.

== Not yet scheduled ==

{| class="wikitable"
! Vital Communities list
! Planning status
|-
| woodstock@lists.vitalcommunities.org
| List page in preparation; schedule to be determined.
|}

== Migration process ==

Each list follows this general process. The communication templates should be reviewed and updated with the list’s specific dates, addresses, and contacts before they are sent.

# '''Announce the move.''' On the '''Announcement Date''', send the [[Vital Communities List Migration/01-move-announcement|move announcement]] to the existing list. It explains the new list, the opt-out process, and the planned cutover date.
# '''Review list information and allow opt-out.''' List administrators receive the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the '''Cutover Date'''.
# '''Cut over the list.''' On the '''Cutover Date''', send the [[Vital Communities List Migration/03-closure-announcement|closure announcement]] to remaining subscribers. Place the previous list in '''moderated mode''' so new posts are not distributed, and enable the [[Vital Communities List Migration/05-old-list-autoresponse|old-list autoresponse]] to direct senders to the new list for the period set for that migration.
# '''Transfer subscribers and welcome them.''' Import subscribers who did not opt out, including their delivery preferences. Then send the [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] with information about the list, its moderators, and where to get help.

[[Category:List Migration]]

Welcome to UVLists

2026-10-22T23:13:27Z

UVListsBot: Link Help:FAQ

'''Neighbors helping neighbors, one email at a time.'''

{{Warning
|title=List Migration is starting soon!
|1=As part of the [[Vital Communities List Migration|migration from Vital Communities]], we will be starting migration of existing lists hosted with Vital Communities to UVLists. Some information contained in this wiki may be slightly out of date or incomplete until migration is complete.
}}

<div class="uvlists-news">
==== UVLists News ====
* [[news/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists | October 2, 2026 - UVLists and Vital Communities Reach An Agreement]]
* [[news/uvlists-announce-announcement-list|September 12, 2026 - UVLists-Announce Announcement List]]
* [[news/committee-members-needed|August 27, 2026 - Committee members needed!]]
* [[news/memorandum-of-understanding|August 26, 2026 - Memorandum of Understanding for Vital Communities Community Email Lists]]
* [[news/hello-world|August 26, 2026 - Hello World!]]
[[News|All news and announcements →]]
</div>

UVLists helps people across the Upper Valley stay connected through local email discussion lists. Ask for a plumber recommendation, share a community supper, find a home for something you no longer need, or catch up on what’s happening around town.

No ads. No social media account. Just email from your community.

'''[[:Category:Mailing lists|Find Your List]] · [[Help:Getting started|How it works]] · [[Help:Contents|Get help]]'''

== New here? ==

A mailing list is a shared email conversation. When someone sends a message to the list, it reaches the people subscribed to it. You can read and participate from the email account you already use.

Start with the [[:Category:Mailing lists | list directory]]. Each list has a page explaining who it serves, how to join, and its posting guidelines.

Already subscribed? Keep using your email as usual. This website is here when you need instructions, information about your list, or a little help.

== Looking for something? ==

* '''[[Help:Subscribing|Join a list]]''' - Find out how to subscribe.
* '''[[Help:Posting|Send a message]]''' - Learn how to post to your community.
* '''[[Help:Unsubscribing|Leave a list]]''' - Get unsubscribe instructions.
* '''[[Help:Delivery problems|Missing messages?]]''' - Troubleshoot email delivery.
* '''[[Help:FAQ|Common questions]]''' - Short answers to frequently asked questions.
* '''[[Contact|Contact us]]''' - Ask a question or report a problem.

== Local conversations, local care ==

Each list has its own character. Volunteer list administrators help keep conversations useful and look after the guidelines for their community.

Before posting, take a moment to read your list’s guidelines. A clear subject line, a little context, and consideration for your neighbors go a long way.

== About UVLists ==

UVLists grew out of the effort to carry forward the regional mailing lists supported by Vital Communities and keep them under community stewardship.

These lists matter because people use them: to lend a hand, exchange local knowledge, share news, and make everyday life a little easier. Our job is to keep that connection dependable and straightforward.

We aim to do our work openly. You can read about [[UVLists:About|the project]], follow [[UVLists:Governance|how decisions are made]], and find out [[UVLists:Get involved|how to help]].

== For list administrators ==

The [[ListAdmin:Overview|list administrator guide]] brings together instructions for moderation, subscriber support, and maintaining your list’s documentation. Shared guidance lives in one place, alongside the pages for each individual list.

You don’t need an account to read this site. List administrators and other authorized editors sign in to keep the information up to date.

Help:Contents

2026-10-22T23:13:27Z

UVListsBot: Create help index

Help for people who use UVLists email lists. If you are new, a mailing list is a shared email conversation: you send a message to the list, and it reaches everyone subscribed to it. You use the email account you already have.

== Using a list ==

* '''[[Help:Subscribing|Join a list]]''': how to subscribe and confirm.
* '''[[Help:Posting|Send a message]]''': how to post, reply, and what happens after you send.
* '''[[Help:Unsubscribing|Leave a list]]''': how to unsubscribe, pause delivery, or get fewer emails.
* '''[[Help:Delivery problems|Missing messages?]]''': spam folders, paused delivery, digests, and other delivery problems.

== Questions ==

* '''[[Help:FAQ|Frequently asked questions]]''': short answers to common questions.
* '''[[Vital Communities List Migration/FAQ|List migration FAQ]]''': questions about the move from Vital Communities.

== Find a list ==

The [[:Category:Mailing lists|list directory]] has a page for each list, with its addresses, how to join, its guidelines, and a contact card to save in your address book.

== Contact us ==

Email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org] for help with a list. To report spam, harassment, or abuse, email [mailto:abuse@uvlists.org abuse@uvlists.org]. Other addresses are on the [[Contact|Contact UVLists]] page.

For list administrators, see the [[ListAdmin:Overview|list administrator guide]].

Vital Communities List Migration/FAQ

2026-10-22T23:13:27Z

UVListsBot: Create list migration FAQ

Questions about the move of community email lists from Vital Communities to UVLists. For the schedule and the process, see [[Vital Communities List Migration]]. For questions about using the lists day to day, see the [[Help:FAQ|general FAQ]].

== The move ==

=== Why are the lists moving? ===
Vital Communities and UVLists agreed to move the Upper Valley community email lists to UVLists. See the [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists|announcement]].

=== Is UVLists part of Vital Communities? ===
No. UVLists is a separate Vermont nonprofit run by volunteers. See [[UVLists:About|About UVLists]].

=== Is it still the same list? ===
Yes. The subscribers, the purpose, the guidelines, and the volunteers who run it stay the same. Only the name, the address, and the service change. See [[Vital Communities List Migration/Renaming Lists|Renaming Lists]].

=== When does my list move? ===
Each list has an announcement date and a cutover date. See the [[Vital Communities List Migration#Migration schedule|migration schedule]].

== Subscribers ==

=== Do I need to resubscribe? ===
No. Unless you unsubscribe from the Vital Communities list before its cutover date, your subscription moves to UVLists automatically, along with your choice of digest or individual messages.

=== I do not want to move to UVLists ===
Unsubscribe from the Vital Communities list before its cutover date. If your list has already moved, you can leave the new list at any time. See [[Help:Unsubscribing|Leave a list]].

=== What is my list's new address? ===
Town lists now end in ''-discuss''. For example, the Norwich list's address is <code>norwich-discuss@lists.uvlists.org</code>. Each list's page in the [[:Category:Mailing lists|list directory]] shows its new addresses.

=== Can I post to the new list before the cutover date? ===
Not yet. Once a list is announced you can subscribe to the new list, but posting opens on the cutover date.

=== What happens if I write to the old address? ===
After the cutover date, mail sent to the old <code>@lists.vitalcommunities.org</code> address gets an automatic reply with the new address. Your message is not passed along, so send it again to the new address and update your contacts.

=== How do I keep the new list's messages out of my spam folder? ===
Add the list to your contacts using its contact card, and mark <code>lists.uvlists.org</code> as a safe sender. See [[Vital Communities List Migration#Before your list moves|Before your list moves]].

=== I stopped getting messages after my list moved ===
Check your spam folder first. See [[Help:Delivery problems|Delivery problems]], or email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org].

== List administrators ==

=== What do list administrators need to do? ===
Review your list's page on this wiki and send any corrections. See the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] and the [[ListAdmin:Overview|list administrator guide]].

== Still need help? ==

Email '''[mailto:helpdesk@uvlists.org helpdesk@uvlists.org]'''. Please include the name of your list and the email address you subscribed with.

[[Category:List Migration]]

Help:FAQ

2026-10-22T23:13:27Z

UVListsBot: Create general FAQ

Short answers to the questions people ask most about UVLists lists. Each answer links to a help page with the full details.

Questions about the move from Vital Communities have their own page: [[Vital Communities List Migration/FAQ|List migration FAQ]].

== Getting mail ==

=== I am not getting messages from my list ===
Check your spam or junk folder first, and add the list to your contacts. If messages stopped arriving, your delivery may have been paused. See [[Help:Delivery problems|Delivery problems]] for a checklist.

=== I am not getting the digest ===
A digest is sent only when there are new messages, so on a quiet list it may not come every day. If it never arrives, check your spam folder and your delivery settings. See [[Help:Delivery problems#You are getting digests, not individual messages (or the other way around)|digests and individual messages]].

=== How do I switch between a daily digest and individual messages? ===
Change your delivery setting on the list website. See [[Help:Delivery problems#Changing your settings on the list website|Changing your settings]].

=== I am getting two copies of every message ===
You are probably subscribed with two addresses that arrive in the same inbox, or you get messages both one at a time and in a digest. See [[Help:Delivery problems#You are getting two copies of messages|two copies of messages]].

=== How do I leave a list or take a break? ===
See [[Help:Unsubscribing|Leave a list]]. You can also pause delivery or switch to a digest instead of leaving.

== Posting ==

=== My post did not appear on the list. Why? ===
The most common reasons are sending from an address that is not subscribed, using '''Reply''' instead of '''Reply All''', or a message that is waiting for a moderator. See [[Help:Posting#What happens after you send|What happens after you send]].

=== My message was held because of an attachment. Why? ===
Messages larger than about 40 KB are held for review, and a single photo or flyer is usually larger than that. Put the file online and paste a link instead. See [[Help:Posting#Keep messages small|Keep messages small]].

=== Can I include a link in my post? ===
Yes. Paste the whole web address into your message so readers can see where it goes, and avoid shortened links. See [[Help:Posting#Tips for a good post|Tips for a good post]].

=== Can a post be deleted? ===
A message cannot be recalled once it is sent; it reaches every subscriber right away. Send a short correction to the list. If private information needs to be removed from the archive, write to the list administrators at the list's <code>-owner</code> address. See [[Help:Posting#Correcting a mistake|Correcting a mistake]].

=== Can I use a list to share an emergency message? ===
No. Many subscribers read a daily digest or check email only now and then, and a post may wait for a moderator. For urgent safety matters, call 911 or contact your town directly.

== Privacy and moderation ==

=== Who can read what I post? ===
Every subscriber receives your message. On most lists, messages are also saved in a public archive on the web that anyone can read, with your name and email address. Each community decides whether its own list's archive is public or for members only. The list's page in the [[:Category:Mailing lists|list directory]] links to its archive. If you are not sure, assume your post is public.

=== What does it mean when my posts are moderated? ===
List administrators can choose to review a member's posts before they go out, usually after a guideline problem. Your messages still reach the list once a moderator approves them, but they may be delayed. In serious cases, administrators can remove a member from a list or block an address from posting. To ask about a decision, write to the list's <code>-owner</code> address.

=== How do I contact a list administrator? ===
Write to the list's <code>-owner</code> address, shown on the list's page in the [[:Category:Mailing lists|list directory]]. It reaches the volunteer administrators, not the members. You can also email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org] and we will pass your message along.

=== Someone is breaking the list's guidelines. What should I do? ===
Do not reply on the list. Write to the list administrators at the list's <code>-owner</code> address. To report spam, harassment, or abuse, email [mailto:abuse@uvlists.org abuse@uvlists.org].

== About UVLists ==

=== Who runs the lists? ===
UVLists is a Vermont nonprofit run by volunteers. Each list is looked after by volunteer administrators and moderators from its own community. See [[UVLists:About|About UVLists]].

=== How can I help run a list? ===
Email [mailto:list-requests@rt.uvlists.org list-requests@rt.uvlists.org] and tell us which town or list, and a little about yourself. You do not need to be technical. See [[UVLists:Get involved#Help run a list|Help run a list]].

=== How do I ask for a new list? ===
Email [mailto:list-requests@rt.uvlists.org list-requests@rt.uvlists.org].

== Still need help? ==

Email '''[mailto:helpdesk@uvlists.org helpdesk@uvlists.org]'''. Please include the name of the list and the email address you subscribed with.

{{Mailing List Help Footer}}

Vital Communities List Migration

2026-10-22T04:49:05Z

UVListsBot: Remove the Open status; old and new lists do not run side by side

== Overview ==

As described in [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists]], UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.

For help with a migration or a question about a particular list, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org]. Other addresses are on the [[Contact|Contact UVLists]] page.

== What subscribers need to do ==

Subscribers do not need to take action to move to the new UVLists list. Unless they unsubscribe from the Vital Communities list before its '''Cutover Date''', their subscription and delivery preference will be transferred. After the move, use the new list address shown on the list’s UVLists page.

== Before your list moves ==

A few minutes of preparation helps the new list's messages reach your inbox instead of your spam folder.

# '''Add the new list to your contacts.''' Every list has a ready-made contact card. Open the list's page from the table below, find '''VCard File''' in the '''Mailing List Info''' box, and select the link. You can also get the card from the list's short page at <code>go.uvlists.org</code> (for example, <code><nowiki>https://go.uvlists.org/norwich</nowiki></code>). With the card saved, your email program fills in the correct new address when you write to the list.
# '''Mark UVLists mail as safe.''' If your email service has a safe senders or approved senders list, add <code>lists.uvlists.org</code> to it.
# '''Check your spam folder after the cutover date.''' If a list message lands there, mark it as ''not spam''. Your email service learns from this.

For step-by-step help, see [[Help:Subscribing|Subscribing]] and [[Help:Delivery problems|Delivery problems]]. If something still is not working, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org].

== What list administrators need to do ==

List administrators should review the list’s public page for accuracy, including its purpose, guidelines, owner-contact address, and joining instructions. The [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] explains what to check and how to submit corrections.

== Migration schedule ==

The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.

The status column uses these terms:

{| class="wikitable"
! Status
! Meaning
|-
| Not migrated
| Migration has not started.
|-
| Announced
| Existing Vital Communities subscribers have been notified and can opt out before the cutover date. The new list is available for subscriptions but not yet for posting.
|-
| Migrated
| The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address.
|-
| Complete
| The prior Vital Communities list has been fully retired.
|}

{| class="wikitable sortable"
|+ Migration Schedule
|-
! VC List !! UVL List !! Announcement Date !! Cutover Date !! Current Status
|-
| barnard@lists.vitalcommunities.org || [[Lists:Barnard]] || October 20, 2026 || October 27, 2026 || Announced
|-
| bradford@lists.vitalcommunities.org || [[Lists:Bradford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| bridgewater@lists.vitalcommunities.org || [[Lists:Bridgewater]] || October 20, 2026 || October 27, 2026 || Announced
|-
| brownsville@lists.vitalcommunities.org || [[Lists:Brownsville]] || October 21, 2026 || October 28, 2026 || Announced
|-
| chelsea@lists.vitalcommunities.org || [[Lists:Chelsea]] || October 21, 2026 || October 28, 2026 || Announced
|-
| claremont@lists.vitalcommunities.org || [[Lists:Claremont]] || October 21, 2026 || October 28, 2026 || Announced
|-
| enfield@lists.vitalcommunities.org || [[Lists:Enfield]] || October 21, 2026 || October 28, 2026 || Announced
|-
| fairlee@lists.vitalcommunities.org || [[Lists:Fairlee]] || October 20, 2026 || October 27, 2026 || Announced
|-
| grafton@lists.vitalcommunities.org || [[Lists:Grafton]] || October 21, 2026 || October 28, 2026 || Announced
|-
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| groton_area@lists.vitalcommunities.org || [[Lists:Groton]] || October 21, 2026 || October 28, 2026 || Announced
|-
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| hartford@lists.vitalcommunities.org || [[Lists:Hartford]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| haverhill@lists.vitalcommunities.org || [[Lists:Haverhill]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| lebanon@lists.vitalcommunities.org || [[Lists:Lebanon]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| lyme@lists.vitalcommunities.org || [[Lists:Lyme]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| mascoma@lists.vitalcommunities.org || [[Lists:Mascoma]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| newbury@lists.vitalcommunities.org || [[Lists:Newbury]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| norwich@lists.vitalcommunities.org || [[Lists:Norwich]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| orford@lists.vitalcommunities.org || [[Lists:Orford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| piermont@lists.vitalcommunities.org || [[Lists:Piermont]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| plainfield@lists.vitalcommunities.org || [[Lists:Plainfield]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| pomfret@lists.vitalcommunities.org || [[Lists:Pomfret]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| reading@lists.vitalcommunities.org || [[Lists:Reading]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| royalton@lists.vitalcommunities.org || [[Lists:Royalton]] || October 20, 2026 || October 27, 2026 || Announced
|-
| ryegate@lists.vitalcommunities.org || [[Lists:Ryegate]] || October 20, 2026 || October 27, 2026 || Announced
|-
| sharon@lists.vitalcommunities.org || [[Lists:Sharon]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| strafford@lists.vitalcommunities.org || [[Lists:Strafford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| thetford@lists.vitalcommunities.org || [[Lists:Thetford]] || October 21, 2026 || October 28, 2026 || Announced
|-
| tunbridge@lists.vitalcommunities.org || [[Lists:Tunbridge]] || October 21, 2026 || October 28, 2026 || Announced
|-
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| west_fairlee@lists.vitalcommunities.org || [[Lists:West Fairlee]] || October 21, 2026 || October 28, 2026 || Announced
|-
| west_lebanon@lists.vitalcommunities.org || [[Lists:West Lebanon]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| west_newbury@lists.vitalcommunities.org || [[Lists:West Newbury]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| west_norwich@lists.vitalcommunities.org || [[Lists:West Norwich]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Announced
|}

Each linked UVLists list page includes its new address, joining instructions, and local guidelines.

== Not yet scheduled ==

{| class="wikitable"
! Vital Communities list
! Planning status
|-
| woodstock@lists.vitalcommunities.org
| List page in preparation; schedule to be determined.
|}

== Migration process ==

Each list follows this general process. The communication templates should be reviewed and updated with the list’s specific dates, addresses, and contacts before they are sent.

# '''Announce the move.''' On the '''Announcement Date''', send the [[Vital Communities List Migration/01-move-announcement|move announcement]] to the existing list. It explains the new list, the opt-out process, and the planned cutover date.
# '''Review list information and allow opt-out.''' List administrators receive the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the '''Cutover Date'''.
# '''Cut over the list.''' On the '''Cutover Date''', send the [[Vital Communities List Migration/03-closure-announcement|closure announcement]] to remaining subscribers. Place the previous list in '''moderated mode''' so new posts are not distributed, and enable the [[Vital Communities List Migration/05-old-list-autoresponse|old-list autoresponse]] to direct senders to the new list for the period set for that migration.
# '''Transfer subscribers and welcome them.''' Import subscribers who did not opt out, including their delivery preferences. Then send the [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] with information about the list, its moderators, and where to get help.

[[Category:List Migration]]

Contact

2026-10-22T04:45:45Z

UVListsBot: General questions and list support go to helpdesk@uvlists.org

== Contact UVLists ==

Have a question, need help, or want to report a problem? Email the address that best fits your message. UVLists is maintained by volunteers; messages are tracked so that the right person can follow up.

== What happens when you contact us? ==

UVLists uses '''Request Tracker (RT)''', a helpdesk system that keeps each request and its replies together in a ticket. After you email us, you may receive a reply with a ticket number in the subject line. You can simply reply to that message; keeping the ticket number in the subject helps us keep the conversation together and prevents requests from being missed or answered twice.

=== General questions and list support ===

For questions about UVLists, help using a community list, or a problem that does not fit one of the categories below, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org].

When asking about a mailing list, include the list name and the email address affected. For delivery problems, include the approximate date and time of a missing or rejected message, if known.

=== Website and wiki ===

To report a problem with this website or the UVLists wiki, suggest a correction, or request help with an editor account, email [mailto:webmaster@uvlists.org webmaster@uvlists.org].

=== Abuse, spam, or harassment ===

To report spam, harassment, misuse of a list, or another safety concern, email [mailto:abuse@uvlists.org abuse@uvlists.org]. Include the list name, relevant message headers or links, and a brief description of the issue. Please do not send passwords or other sensitive account credentials.

=== Systems and technical issues ===

For infrastructure, mail-system, or other technical operational issues, email [mailto:sysadmins@uvlists.org sysadmins@uvlists.org].

=== List-specific questions ===

For questions about the rules, moderation, or local purpose of a particular community list, use the owner-contact address shown on that list’s information page. Visit the [[:Category:Mailing lists|list directory]] to find the right page.

== A note about replies ==

Please keep the ticket reference in the subject line when replying to a UVLists support message. This keeps the conversation together and helps the volunteer team respond efficiently.

Vital Communities List Migration

2026-10-22T04:45:45Z

UVListsBot: Clarify status key, match Not migrated capitalization, add helpdesk@ and a Before your list moves section

== Overview ==

As described in [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists]], UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.

For help with a migration or a question about a particular list, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org]. Other addresses are on the [[Contact|Contact UVLists]] page.

== What subscribers need to do ==

Subscribers do not need to take action to move to the new UVLists list. Unless they unsubscribe from the Vital Communities list before its '''Cutover Date''', their subscription and delivery preference will be transferred. After the move, use the new list address shown on the list’s UVLists page.

== Before your list moves ==

A few minutes of preparation helps the new list's messages reach your inbox instead of your spam folder.

# '''Add the new list to your contacts.''' Every list has a ready-made contact card. Open the list's page from the table below, find '''VCard File''' in the '''Mailing List Info''' box, and select the link. You can also get the card from the list's short page at <code>go.uvlists.org</code> (for example, <code><nowiki>https://go.uvlists.org/norwich</nowiki></code>). With the card saved, your email program fills in the correct new address when you write to the list.
# '''Mark UVLists mail as safe.''' If your email service has a safe senders or approved senders list, add <code>lists.uvlists.org</code> to it.
# '''Check your spam folder after the cutover date.''' If a list message lands there, mark it as ''not spam''. Your email service learns from this.

For step-by-step help, see [[Help:Subscribing|Subscribing]] and [[Help:Delivery problems|Delivery problems]]. If something still is not working, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org].

== What list administrators need to do ==

List administrators should review the list’s public page for accuracy, including its purpose, guidelines, owner-contact address, and joining instructions. The [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] explains what to check and how to submit corrections.

== Migration schedule ==

The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.

The status column uses these terms:

{| class="wikitable"
! Status
! Meaning
|-
| Not migrated
| Migration has not started.
|-
| Announced
| Existing Vital Communities subscribers have been notified and can opt out before the cutover date. The new list is available for subscriptions but not yet for posting.
|-
| Open
| The new list accepts posts. The Vital Communities list is still running alongside it.
|-
| Migrated
| The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address.
|-
| Complete
| The prior Vital Communities list has been fully retired.
|}

{| class="wikitable sortable"
|+ Migration Schedule
|-
! VC List !! UVL List !! Announcement Date !! Cutover Date !! Current Status
|-
| barnard@lists.vitalcommunities.org || [[Lists:Barnard]] || October 20, 2026 || October 27, 2026 || Announced
|-
| bradford@lists.vitalcommunities.org || [[Lists:Bradford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| bridgewater@lists.vitalcommunities.org || [[Lists:Bridgewater]] || October 20, 2026 || October 27, 2026 || Announced
|-
| brownsville@lists.vitalcommunities.org || [[Lists:Brownsville]] || October 21, 2026 || October 28, 2026 || Announced
|-
| chelsea@lists.vitalcommunities.org || [[Lists:Chelsea]] || October 21, 2026 || October 28, 2026 || Announced
|-
| claremont@lists.vitalcommunities.org || [[Lists:Claremont]] || October 21, 2026 || October 28, 2026 || Announced
|-
| enfield@lists.vitalcommunities.org || [[Lists:Enfield]] || October 21, 2026 || October 28, 2026 || Announced
|-
| fairlee@lists.vitalcommunities.org || [[Lists:Fairlee]] || October 20, 2026 || October 27, 2026 || Announced
|-
| grafton@lists.vitalcommunities.org || [[Lists:Grafton]] || October 21, 2026 || October 28, 2026 || Announced
|-
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| groton_area@lists.vitalcommunities.org || [[Lists:Groton]] || October 21, 2026 || October 28, 2026 || Announced
|-
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| hartford@lists.vitalcommunities.org || [[Lists:Hartford]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| haverhill@lists.vitalcommunities.org || [[Lists:Haverhill]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| lebanon@lists.vitalcommunities.org || [[Lists:Lebanon]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| lyme@lists.vitalcommunities.org || [[Lists:Lyme]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| mascoma@lists.vitalcommunities.org || [[Lists:Mascoma]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| newbury@lists.vitalcommunities.org || [[Lists:Newbury]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| norwich@lists.vitalcommunities.org || [[Lists:Norwich]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| orford@lists.vitalcommunities.org || [[Lists:Orford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| piermont@lists.vitalcommunities.org || [[Lists:Piermont]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| plainfield@lists.vitalcommunities.org || [[Lists:Plainfield]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| pomfret@lists.vitalcommunities.org || [[Lists:Pomfret]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| reading@lists.vitalcommunities.org || [[Lists:Reading]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| royalton@lists.vitalcommunities.org || [[Lists:Royalton]] || October 20, 2026 || October 27, 2026 || Announced
|-
| ryegate@lists.vitalcommunities.org || [[Lists:Ryegate]] || October 20, 2026 || October 27, 2026 || Announced
|-
| sharon@lists.vitalcommunities.org || [[Lists:Sharon]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| strafford@lists.vitalcommunities.org || [[Lists:Strafford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| thetford@lists.vitalcommunities.org || [[Lists:Thetford]] || October 21, 2026 || October 28, 2026 || Announced
|-
| tunbridge@lists.vitalcommunities.org || [[Lists:Tunbridge]] || October 21, 2026 || October 28, 2026 || Announced
|-
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| west_fairlee@lists.vitalcommunities.org || [[Lists:West Fairlee]] || October 21, 2026 || October 28, 2026 || Announced
|-
| west_lebanon@lists.vitalcommunities.org || [[Lists:West Lebanon]] || October 22, 2026 || October 29, 2026 || Not migrated
|-
| west_newbury@lists.vitalcommunities.org || [[Lists:West Newbury]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| west_norwich@lists.vitalcommunities.org || [[Lists:West Norwich]] || October 23, 2026 || October 30, 2026 || Not migrated
|-
| windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Announced
|}

Each linked UVLists list page includes its new address, joining instructions, and local guidelines.

== Not yet scheduled ==

{| class="wikitable"
! Vital Communities list
! Planning status
|-
| woodstock@lists.vitalcommunities.org
| List page in preparation; schedule to be determined.
|}

== Migration process ==

Each list follows this general process. The communication templates should be reviewed and updated with the list’s specific dates, addresses, and contacts before they are sent.

# '''Announce the move.''' On the '''Announcement Date''', send the [[Vital Communities List Migration/01-move-announcement|move announcement]] to the existing list. It explains the new list, the opt-out process, and the planned cutover date.
# '''Review list information and allow opt-out.''' List administrators receive the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the '''Cutover Date'''.
# '''Cut over the list.''' On the '''Cutover Date''', send the [[Vital Communities List Migration/03-closure-announcement|closure announcement]] to remaining subscribers. Place the previous list in '''moderated mode''' so new posts are not distributed, and enable the [[Vital Communities List Migration/05-old-list-autoresponse|old-list autoresponse]] to direct senders to the new list for the period set for that migration.
# '''Transfer subscribers and welcome them.''' Import subscribers who did not opt out, including their delivery preferences. Then send the [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] with information about the list, its moderators, and where to get help.

[[Category:List Migration]]

Vital Communities List Migration

2026-10-22T04:40:25Z

UVListsBot: Mark the 10 lists announced 2026-10-21 as Announced

== Overview ==

As described in [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists]], UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.

For help with a migration or a question about a particular list, see [[Contact|Contact UVLists]].

== What subscribers need to do ==

Subscribers do not need to take action to move to the new UVLists list. Unless they unsubscribe from the Vital Communities list before its '''Cutover Date''', their subscription and delivery preference will be transferred. After the move, use the new list address shown on the list’s UVLists page.

== What list administrators need to do ==

List administrators should review the list’s public page for accuracy, including its purpose, guidelines, owner-contact address, and joining instructions. The [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] explains what to check and how to submit corrections.

== Migration schedule ==

The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.

The status column uses these terms:

{| class="wikitable"
! Status
! Meaning
|-
| Not migrated
| Migration has not started.
|-
| Announced
| Existing Vital Communities subscribers have been notified. The new list is available for subscriptions but not yet for posting.
|-
| Open
| The new list is available for subscriptions but not yet for posting. Existing Vital Communities list is still in operation.
|-
| Migrated
| The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address.
|-
| Complete
| The prior Vital Communities list has been fully retired.
|}

{| class="wikitable sortable"
|+ Migration Schedule
|-
! VC List !! UVL List !! Announcement Date !! Cutover Date !! Current Status
|-
| barnard@lists.vitalcommunities.org || [[Lists:Barnard]] || October 20, 2026 || October 27, 2026 || Announced
|-
| bradford@lists.vitalcommunities.org || [[Lists:Bradford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| bridgewater@lists.vitalcommunities.org || [[Lists:Bridgewater]] || October 20, 2026 || October 27, 2026 || Announced
|-
| brownsville@lists.vitalcommunities.org || [[Lists:Brownsville]] || October 21, 2026 || October 28, 2026 || Announced
|-
| chelsea@lists.vitalcommunities.org || [[Lists:Chelsea]] || October 21, 2026 || October 28, 2026 || Announced
|-
| claremont@lists.vitalcommunities.org || [[Lists:Claremont]] || October 21, 2026 || October 28, 2026 || Announced
|-
| enfield@lists.vitalcommunities.org || [[Lists:Enfield]] || October 21, 2026 || October 28, 2026 || Announced
|-
| fairlee@lists.vitalcommunities.org || [[Lists:Fairlee]] || October 20, 2026 || October 27, 2026 || Announced
|-
| grafton@lists.vitalcommunities.org || [[Lists:Grafton]] || October 21, 2026 || October 28, 2026 || Announced
|-
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| groton_area@lists.vitalcommunities.org || [[Lists:Groton]] || October 21, 2026 || October 28, 2026 || Announced
|-
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| hartford@lists.vitalcommunities.org || [[Lists:Hartford]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| haverhill@lists.vitalcommunities.org || [[Lists:Haverhill]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lebanon@lists.vitalcommunities.org || [[Lists:Lebanon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lyme@lists.vitalcommunities.org || [[Lists:Lyme]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| mascoma@lists.vitalcommunities.org || [[Lists:Mascoma]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| newbury@lists.vitalcommunities.org || [[Lists:Newbury]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| norwich@lists.vitalcommunities.org || [[Lists:Norwich]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| orford@lists.vitalcommunities.org || [[Lists:Orford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| piermont@lists.vitalcommunities.org || [[Lists:Piermont]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| plainfield@lists.vitalcommunities.org || [[Lists:Plainfield]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| pomfret@lists.vitalcommunities.org || [[Lists:Pomfret]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| reading@lists.vitalcommunities.org || [[Lists:Reading]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| royalton@lists.vitalcommunities.org || [[Lists:Royalton]] || October 20, 2026 || October 27, 2026 || Announced
|-
| ryegate@lists.vitalcommunities.org || [[Lists:Ryegate]] || October 20, 2026 || October 27, 2026 || Announced
|-
| sharon@lists.vitalcommunities.org || [[Lists:Sharon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| strafford@lists.vitalcommunities.org || [[Lists:Strafford]] || October 20, 2026 || October 27, 2026 || Announced
|-
| thetford@lists.vitalcommunities.org || [[Lists:Thetford]] || October 21, 2026 || October 28, 2026 || Announced
|-
| tunbridge@lists.vitalcommunities.org || [[Lists:Tunbridge]] || October 21, 2026 || October 28, 2026 || Announced
|-
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| west_fairlee@lists.vitalcommunities.org || [[Lists:West Fairlee]] || October 21, 2026 || October 28, 2026 || Announced
|-
| west_lebanon@lists.vitalcommunities.org || [[Lists:West Lebanon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| west_newbury@lists.vitalcommunities.org || [[Lists:West Newbury]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| west_norwich@lists.vitalcommunities.org || [[Lists:West Norwich]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Announced
|}

Each linked UVLists list page includes its new address, joining instructions, and local guidelines.

== Not yet scheduled ==

{| class="wikitable"
! Vital Communities list
! Planning status
|-
| woodstock@lists.vitalcommunities.org
| List page in preparation; schedule to be determined.
|}

== Migration process ==

Each list follows this general process. The communication templates should be reviewed and updated with the list’s specific dates, addresses, and contacts before they are sent.

# '''Announce the move.''' On the '''Announcement Date''', send the [[Vital Communities List Migration/01-move-announcement|move announcement]] to the existing list. It explains the new list, the opt-out process, and the planned cutover date.
# '''Review list information and allow opt-out.''' List administrators receive the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the '''Cutover Date'''.
# '''Cut over the list.''' On the '''Cutover Date''', send the [[Vital Communities List Migration/03-closure-announcement|closure announcement]] to remaining subscribers. Place the previous list in '''moderated mode''' so new posts are not distributed, and enable the [[Vital Communities List Migration/05-old-list-autoresponse|old-list autoresponse]] to direct senders to the new list for the period set for that migration.
# '''Transfer subscribers and welcome them.''' Import subscribers who did not opt out, including their delivery preferences. Then send the [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] with information about the list, its moderators, and where to get help.

[[Category:List Migration]]

Tech:Overview

2026-10-22T02:01:44Z

UVListsBot: Create technical overview: two servers, message path, software, how we chose, safety

{{Tech page
|owner=KurthBemis
|reviewed=2026-10-22
}}
This page gives a plain-language picture of the technology behind UVLists: what runs where, how a message travels from one neighbor to the rest of the list, and why things are built the way they are. It is written for volunteers, board members, and anyone curious. You do not need to be an engineer to follow it.

For help using the lists, see the [[Help:Delivery problems|help pages]] instead.

== The big picture ==

UVLists runs on two servers, each with its own job:

{| class="wikitable"
! Server
! What it does
|-
| '''The lists server''' (<code>lists.uvlists.org</code>)
| Runs the public town lists: receives messages, filters spam, sends each message to subscribers, keeps the archives, and hosts the web pages where people manage their subscriptions.
|-
| '''The organization server'''
| Runs everything else: this wiki, the <code>go.uvlists.org</code> list pages, the helpdesk, UVLists staff email, and the private lists used by the board and committees.
|}

Keeping the public lists on their own server is deliberate. A problem on one server, such as a flood of spam or a software failure, cannot take down the other. It also keeps the public lists' sending reputation (how much email providers trust our mail) separate from the organization's own email.

Each service runs in its own isolated container on its server, so that services do not interfere with one another and can be updated one at a time.

== How a message travels ==

When a neighbor sends a message to their town list, it takes this path:

# '''The message arrives''' at the lists server, addressed to the list (for example, <code>norwich-discuss@lists.uvlists.org</code>).
# '''It is checked for spam and viruses.''' Obvious spam and infected messages are refused at the door, and the sender gets an error.
# '''The list software takes over.''' It checks that the sender is subscribed and that the message follows the list's rules, such as the size limit. A message that needs a human decision is held for the list's volunteer moderators.
# '''The message is prepared for delivery.''' The list adds its subject tag (such as <code>[Norwich-discuss]</code>) and standard headers that let email programs show an '''Unsubscribe''' button.
# '''It is signed.''' The server adds a digital signature (DKIM) that lets email providers verify the message really came from UVLists and was not altered on the way.
# '''A copy goes to every subscriber''', either right away or bundled into a digest, depending on each person's settings.
# '''The message is saved in the list archive''', where members (and, for most lists, the public) can read it on the web.

If a subscriber's email provider refuses a message, the list notices. After repeated refusals it pauses delivery to that address, as described in [[Help:Delivery problems#Your delivery was paused because messages were turned away|Delivery problems]].

== The software we use ==

UVLists uses established, open-source software wherever it can, and writes its own only to fill gaps.

{| class="wikitable"
! Software
! What it does for UVLists
|-
| [https://www.list.org/ GNU Mailman 3]
| The mailing list software. It includes '''Postorius''', the web pages for managing subscriptions and lists, and '''HyperKitty''', the web archive.
|-
| [https://www.postfix.org/ Postfix]
| The mail server that receives and sends email.
|-
| [https://rspamd.com/ Rspamd] and [https://www.clamav.net/ ClamAV]
| Spam and virus filtering for incoming mail.
|-
| [https://www.mediawiki.org/ MediaWiki]
| This wiki, which is also the UVLists website.
|-
| [https://bestpractical.com/request-tracker Request Tracker]
| The helpdesk. Every message to helpdesk@ and similar addresses becomes a ticket so nothing is lost.
|-
| [https://about.gitea.com/ Gitea]
| Where volunteers keep UVLists code, server configuration, and detailed technical documentation.
|-
| [https://www.debian.org/ Debian] and [https://linuxcontainers.org/incus/ Incus]
| The operating system on the servers, and the container system that keeps each service separate.
|-
| [https://www.ansible.com/ Ansible] and [https://github.com/octodns/octodns octoDNS]
| Tools that describe our server setup and DNS records as files, so changes are reviewed, repeatable, and recorded instead of made by hand.
|}

On top of these, volunteers have written a few small additions of our own, such as the daily digest emails, the <code>go.uvlists.org</code> list pages and contact cards, and the tools used to move the lists from their previous home.

== How we chose ==

A few decisions shape everything else. The full records, with the alternatives we considered, are kept in Gitea for volunteers.

; Mailman 3 for the lists
: The lists previously ran on different software (Sympa). They now run on Mailman 3, which is open source, widely used, and actively maintained, and includes web pages for subscribers and list administrators. Subscribers' settings, including digest preferences, were carried over in the move.

; Our own servers
: The lists run on servers that UVLists operates itself, set up and maintained by UVLists volunteers.

; Public lists separate from everything else
: Explained in [[#The big picture|The big picture]] above: a problem on one server cannot take down the other, and the public lists' sending reputation stays separate.

; Configuration as code
: Server settings live in files in Gitea and are applied with Ansible. Anyone on the technical team can see exactly how a server is set up and what changed, and a server can be rebuilt from those files if it ever fails.

; New list names ending in -discuss
: See [[Vital Communities List Migration/Renaming Lists|Renaming Lists]].

== Keeping things safe ==

* '''Only what is needed is reachable.''' The web pages and mail services are open to the internet. Administrative access is restricted to the technical team, and everything else on the servers is closed to outside connections.
* '''Accounts are limited.''' Wiki editing, list administration, and server access are each granted only to the volunteers who need them.
* '''Subscriber information is used only to run the lists.''' It is never sold or shared.
* '''Email is authenticated.''' UVLists publishes SPF, DKIM, and DMARC records so that email providers can recognize real UVLists mail and reject forgeries.

Security details, such as server addresses and firewall rules, are deliberately kept off this public wiki.

== More technical pages ==

More pages in the <code>Tech:</code> section are planned, including privacy and data handling, the software we have written, email deliverability, and how to get involved on the technical side. In the meantime, see [[UVLists:Get involved#Help with the technical side|Get involved]] or email [mailto:tech-comm@uvlists.org tech-comm@uvlists.org].

Template:Tech page

2026-10-22T02:01:44Z

UVListsBot: Create Tech page header template: owner, review date, optional Gitea link, review flag after six months

<includeonly><div class="uvlists-tech-page" style="border: 1px solid #a2a9b1; border-left: 5px solid #36c; background: #f8f9fa; color: #202122; padding: 8px 14px; margin: 0 0 16px 0; font-size: 90%;">
'''Technical documentation.''' Maintained by [[User:{{{owner|KurthBemis}}}|{{{owner|KurthBemis}}}]]{{#if:{{{reviewed|}}}|, last reviewed {{#time:F j, Y|{{{reviewed}}}}}|, not yet reviewed}}.{{#if:{{{details|}}}| More detail for volunteers: [https://git.uvlists.org/uvlists/{{{details}}} {{{details}}}] in Gitea (sign-in required).}}{{#if:{{{reviewed|}}}|{{#ifexpr:{{#time:U}} - {{#time:U|{{{reviewed}}}}} > 15552000| '''This page has not been reviewed in over six months and may be out of date.'''}}}}
</div>{{#ifeq:{{NAMESPACE}}|Tech|[[Category:Tech pages]]{{#if:{{{reviewed|}}}|{{#ifexpr:{{#time:U}} - {{#time:U|{{{reviewed}}}}} > 15552000|[[Category:Tech pages needing review]]}}|[[Category:Tech pages needing review]]}}}}</includeonly><noinclude>
Place this template at the top of every page in the <code>Tech:</code> namespace. It shows who maintains the page and when it was last checked, and it can point volunteers to more detailed documentation in Gitea.

== Usage ==

<pre>
{{Tech page
|owner=KurthBemis
|reviewed=2026-10-22
|details=infrastructure/src/branch/main/docs/LISTS_HOST.md
}}
</pre>

== Parameters ==

; owner
: Wiki username of the person responsible for keeping the page accurate. Defaults to KurthBemis.
; reviewed
: Date the page was last checked against the live systems, as <code>YYYY-MM-DD</code>. Update it whenever you review the page, even if nothing changed. Pages not reviewed in six months are flagged and listed in [[:Category:Tech pages needing review]].
; details
: Optional. Path inside the <code>uvlists</code> organization on [https://git.uvlists.org/ Gitea] to the detailed runbook or decision record. Gitea requires a volunteer sign-in, so the wiki page must make sense on its own.

== What not to put on Tech pages ==

Tech pages are public. Do not include server IP addresses, internal container addresses, usernames, passwords or keys, firewall rules, or security weaknesses that have not been fixed yet. Put those details in Gitea and link to them with <code>details</code>.

Pages using this template in the Tech namespace are added to [[:Category:Tech pages]].

<templatedata>
{
"description": "Header for technical documentation pages: owner, last review date, and an optional link to detailed documentation in Gitea.",
"params": {
"owner": {
"label": "Owner",
"description": "Wiki username responsible for the page.",
"type": "wiki-user-name",
"default": "KurthBemis"
},
"reviewed": {
"label": "Last reviewed",
"description": "Date the page was last checked, as YYYY-MM-DD.",
"type": "date",
"suggested": true
},
"details": {
"label": "Gitea path",
"description": "Path under https://git.uvlists.org/uvlists/ to the detailed documentation (sign-in required).",
"type": "string"
}
},
"format": "block"
}
</templatedata>
</noinclude>

UVLists:About

2026-10-22T01:37:39Z

UVListsBot: Create About page: mission, what we do, history from ValleyNet (1994) through the 2026 transition

'''UVLists''' (short for ''Upper Valley Lists'') is a volunteer-run nonprofit based in South Royalton, Vermont. We look after the town email discussion lists that neighbors across the Upper Valley of Vermont and New Hampshire have relied on for more than twenty years.

Our mission is to preserve locally controlled online community discussion forums throughout the Upper Valley.

== What we do ==

UVLists runs 38 town discussion lists, from Barnard to Woodstock. Each list is a shared email conversation for one community: a place to find a lost pet, recommend a plumber, sell a couch, read the select board agenda, or hear about a road closure.

* '''The lists are local.''' Each list serves one town, and its guidelines ask that posts relate to that town, be signed, and stay civil.
* '''The lists are run by neighbors.''' Each list is looked after by volunteer list administrators from its own community, with support from UVLists.
* '''The lists are free and ad-free.''' There is no advertising, and subscriber information is used only to run the lists. It is never sold.
* '''The lists work through email.''' You do not need a social media account, an app, or a password. Just the email address you already have.

The lists run on open-source software (GNU Mailman) on servers maintained by UVLists volunteers.

== Our history ==

=== ValleyNet and the first lists (1994 to 2014) ===

The town lists trace their roots to '''ValleyNet''', which introduced local dial-up internet service to the Upper Valley in 1994. In 2004, ValleyNet took over the Thetford list. From there, the free discussion lists spread from town to town, eventually covering 38 towns and more than 21,000 subscribers.

The lists soon became part of everyday life, and at times much more than that:

* In '''2008''', the lists were an important tool in getting '''ECFiber''' started, when 24 towns voted at town meeting to join the community broadband network.
* After '''Tropical Storm Irene''' in 2011, the lists were critical in coordinating volunteer recovery efforts.
* Towns came to use them to post agendas, minutes, and road closures, and nonprofits and emergency services used them to reach their neighbors.

=== The Vital Communities years (2014 to 2026) ===

In '''2014''', '''Vital Communities''', a regional nonprofit, took over administration of the lists from ValleyNet and stewarded them for more than a decade. Throughout, each list continued to be run day to day by volunteer list administrators. Together, list administrators past and present have given an estimated '''75,000 hours''' of volunteer time since 2004 to keep the lists local, civil, and non-commercial.

=== UVLists is formed (2026) ===

In August 2026, word came that the town lists might close. A concerned group of list administrators, some of whom had looked after their town's list for many years, began discussing the future of the lists and how to keep them running in community hands. Longtime subscribers joined the conversation, and offers of help poured in from across the Upper Valley. That group became UVLists.

* '''August 23, 2026''': UVLists published its first website, explaining who was involved and what a handoff would take.
* '''August 24''': UVLists met with Vital Communities to talk about keeping the lists online.
* '''August 27''': An ad hoc executive committee of list administrators and volunteers sent Vital Communities a proposed [[News/memorandum-of-understanding|memorandum of understanding]] that drew on the thoughts of all 38 list administrators. The same day, UVLists put out a [[News/committee-members-needed|call for committee members]].
* '''September 12''': The [[News/uvlists-announce-announcement-list|UVLists-Announce list]] began sharing news with the public.
* '''September 30''': At its first [[Meetings|board meeting]], UVLists elected officers, adopted its bylaws, and approved a transition agreement with Vital Communities.
* '''October 1''': UVLists and Vital Communities [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists|signed the transition agreement]], under which UVLists took over administration of the 38 town lists.
* '''Late October''': UVLists began [[Vital Communities List Migration|moving each list]] to its own system. Every town list was given a new address ending in ''-discuss@lists.uvlists.org'' (see [[Vital Communities List Migration/Renaming Lists|Renaming Lists]]), and subscribers came along with their existing delivery settings.

'''ECFiber''', whose own start the lists helped make possible, became a key sponsor of UVLists.

Vital Communities continues to run its Upper Valley-wide and topic lists, which were not part of the transition.

We are grateful to ValleyNet and Vital Communities for their many years of stewardship, and above all to the volunteer list administrators who have kept these lists going all along.

== What comes next ==

For now, our first job is to keep the lists working the way people know them. Over time, we hope to help communities do more with them: for example, giving a town separate lists for announcements, discussion, or items for sale, if its residents want that.

UVLists plans to hold its first annual meeting by January 31, 2027, and to begin asking subscribers for financial support in early 2027.

== Who we are ==

UVLists, Inc. is led by a volunteer board of directors and officers, listed on the [[Executive Committee]] page. The day-to-day work is done by volunteers: list administrators, moderators, and people who help with the technical systems, this wiki, and outreach.

UVLists is always looking for more help. See [[UVLists:Get involved|Get involved]].

== Learn more ==

* [[UVLists:Governance|How decisions are made]]
* [[Meetings|Meeting agendas and minutes]]
* [[News|News and announcements]]
* [[UVLists:Get involved|Get involved]]
* [[Contact|Contact UVLists]]

'''Mailing address:''' UVLists, Inc., 95 S Windsor Street, P.O. Box 934, South Royalton, Vermont 05068

UVLists:Get involved

2026-10-22T01:29:56Z

UVListsBot: Create Get involved page: volunteering, list admins, technical and outreach help, supporting UVLists

UVLists is run entirely by volunteers. The town lists keep working because neighbors give a little time: moderating a list, answering a question, fixing a wiki page, or helping the organization make good decisions.

You do not need technical skills to help. There is room for people who can give an hour a month and for people who want to take on more. This page describes the ways you can take part and how to get started.

'''Right now we are especially looking for:'''
* '''List administrators''' and moderators for town lists.
* '''Programmers''' and other '''technical volunteers'''.
* '''Marketing and communications''' help.
* People to '''get the word out''' and help the lists grow.

== Stay informed ==

The easiest way to follow what UVLists is doing is the '''UVLists-Announce''' list. It is a low-volume, announcements-only list for news about meetings, progress on the list migration, new lists, and calls for volunteers.

* To join by email, send a blank message to [mailto:uvlists-announce-join@uvlists.org uvlists-announce-join@uvlists.org].
* Or subscribe on the [https://mailman.ops.uvlists.org/postorius/lists/uvlists-announce.uvlists.org/ UVLists-Announce web page].

You can also read the [[News|news and announcements]] on this wiki, and the agendas and minutes of [[Meetings|board meetings]].

== Be a good list member ==

Every subscriber helps keep the lists useful.

* Read your list's guidelines, and post with a clear subject and a little context.
* Answer a neighbor's question when you know the answer.
* Keep conversations civil, and take disagreements about a post to the list administrators rather than to the list.
* Report spam, harassment, or misuse to [mailto:abuse@uvlists.org abuse@uvlists.org].

See [[Help:Posting|Send a message]] for more tips.

== Spread the word and grow the lists ==

Lists are only as good as the people on them. The more neighbors who join, the more useful every list becomes. If your neighbors do not know about your town's list, tell them.

* Every list has a short, phone-friendly page at [https://go.uvlists.org/ go.uvlists.org], with a QR code you can print on a flyer or poster for the town hall, library, general store, or school.
* Share the [[:Category:Mailing lists|list directory]] with new residents.
* Forward the [[Help:Subscribing|joining instructions]] to anyone who asks how to sign up.
* Mention your list at town meetings, in newsletters, on community bulletin boards, and to local groups and businesses.
* Help people who are not comfortable with technology get signed up.

If you would like to help with outreach in a more organized way, email the executive committee at [mailto:exec-comm@uvlists.org exec-comm@uvlists.org].

== Help run a list ==

Each list is looked after by volunteer '''list administrators''' and '''moderators''' from its community. They are the people who know the town and its conversations best.

* '''Moderators''' review messages that are held for approval, such as posts from people who are not yet subscribed, and decide whether they go out.
* '''List administrators''' also help subscribers who are having trouble, look after the list's guidelines, and keep the list's page on this wiki up to date.

You do not need to be technical. UVLists provides the tools, written guides, and a helpdesk to back you up. See the [[ListAdmin:Overview|list administrator guide]] and [[ListAdmin:Services for List Administrators|Services for List Administrators]] for what the work involves.

If you would like to help administer or moderate your town's list, or you would like to request a new list, email [mailto:list-requests@rt.uvlists.org list-requests@rt.uvlists.org]. Tell us which town or list, and a little about yourself.

== Join a committee or the board ==

UVLists is a Vermont nonprofit led by a volunteer board of directors. The current officers are listed on the [[Executive Committee]] page.

We want the people who guide UVLists to reflect the communities the lists serve, and we welcome people from every town and background. Skills that would help right now include:

* '''Business, finance, and legal experience''': forms, filings, policies, and keeping the organization in good standing.
* '''Community leadership''': people who are known and trusted in their towns and can help UVLists stay connected to them.
* '''Marketing and communications''': writing announcements, editing, and helping people understand what UVLists does.
* '''Web and design''': improving this wiki and the list pages.

That list is not complete. If you have another way to contribute, we would like to hear from you. Email the executive committee at [mailto:exec-comm@uvlists.org exec-comm@uvlists.org] and introduce yourself.

== Improve this wiki ==

The help pages, list pages, and guides on this wiki are written by volunteers. If you spot something that is wrong, out of date, or hard to understand, you can help fix it.

* To suggest a correction, email [mailto:webmaster@uvlists.org webmaster@uvlists.org] with the page name and what should change.
* To edit pages yourself, email the same address to request an editor account.

Plain, friendly writing is especially welcome. Many people come to this wiki because something is not working and they need clear instructions.

== Help with the technical side ==

The lists run on open-source software, including GNU Mailman, on servers maintained by volunteers. We are looking for programmers and other technical volunteers. Experience with any of these is helpful:

* Programming, especially Python.
* Email systems and deliverability.
* Linux server administration.
* Web development and design.

If you would like to help, email the technical committee at [mailto:tech-comm@uvlists.org tech-comm@uvlists.org] and tell us a little about your background.

== Support UVLists ==

Running the lists has real costs, including servers, domain names, insurance, and the paperwork that comes with being a nonprofit. UVLists has no advertising and does not sell anyone's information, so it depends on the people and communities it serves.

You can support UVLists by:

* '''Making a financial contribution.''' To find out how to give, email the treasurer at [mailto:treasurer@uvlists.org treasurer@uvlists.org].
* '''Offering in-kind help''', such as printing flyers, providing meeting space, or professional services.
* '''Encouraging local organizations''' that rely on the lists to support them.
* '''Giving your time''' in any of the ways described on this page.

== Come to a meeting ==

The board publishes [[Meetings|meeting agendas and minutes]] on this wiki, and the first annual meeting will be held on or before January 31, 2027. Meeting announcements are sent to the UVLists-Announce list, so [[#Stay informed|subscribe]] to hear about them.

== Not sure where to start? ==

Email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org] and tell us what interests you and how much time you have. We will help you find something that fits.

Help:Delivery problems

2026-10-22T01:18:28Z

UVListsBot: Clarify which messages are held for review

Not getting list messages, or something seems wrong with the ones you do get? This page walks through the most common problems and how to fix them. You do not need any technical knowledge to follow it.

Most delivery problems come down to one of a few things: messages are being sorted into a spam or other folder, you are subscribed with a different address than you think, your email provider is turning messages away, or your list settings have changed.

If you work through this page and still need help, email '''[mailto:helpdesk@uvlists.org helpdesk@uvlists.org]'''. See [[#Still need help?|Still need help?]] at the bottom of this page for what to include.

== Start here: quick checklist ==

Before reading further, try these steps. They solve most problems.

# '''Check your spam or junk folder.''' Also check any other folders or tabs your email uses, such as ''Promotions'', ''Updates'', ''Forums'', ''Other'', or ''Clutter''.
# '''Search your mailbox''' for the list name (for example, ''Norwich-Discuss'') or for <code>lists.uvlists.org</code>.
# '''Make sure you are checking the right email account.''' If you have more than one address, the list only sends to the one you subscribed.
# '''Add the list to your contacts.''' Each list has a contact card you can download. See [[#Add the list to your contacts|Add the list to your contacts]].
# '''Check the list archive''' to see whether anyone has posted recently. Quiet lists sometimes go days without a message. The archive link is on the list's page in the [[:Category:Mailing lists|list directory]].

== Add the list to your contacts ==

Adding the list to your address book is one of the most helpful things you can do. It helps in two ways:

* '''Fewer messages go to spam.''' Many email services trust messages from addresses in your contacts.
* '''Your messages go to the right place.''' When you write to the list, your email program will fill in the correct, current posting address for you. This matters most for lists that moved from Vital Communities, because the old addresses no longer work.

Every list has a ready-made contact card (also called a ''vCard''). To get it:

# Open the list's page in the [[:Category:Mailing lists|list directory]].
# In the '''Mailing List Info''' box, find '''VCard File''' and select the link. It looks like <code><nowiki>https://go.uvlists.org/norwich-discuss.vcf</nowiki></code>.
# Your phone or computer will offer to add the contact. Accept it.

You can also reach the card from the list's short web page at <code>go.uvlists.org</code> (for example, <code><nowiki>https://go.uvlists.org/norwich</nowiki></code>), which is where the QR codes on printed flyers lead.

The card includes the list's posting address, a link to change your subscription settings, and a link to the archives.

If you already had a contact for the list under its old Vital Communities address, delete or update the old contact so your email program does not keep suggesting it.

== Messages are going to spam or another folder ==

Email services try to guess which messages you want. Mailing lists sometimes get sorted incorrectly, especially after a list changes its address.

The fix is the same everywhere: find a list message, tell your email service it is not spam, and add the list to your contacts. Doing this once or twice usually trains your email service to deliver future messages normally.

=== Gmail ===

* Open the message in your '''Spam''' folder and select '''Report not spam''' (or '''Not spam''').
* If list messages land in the '''Promotions''', '''Updates''', or '''Forums''' tab, drag one message to the '''Primary''' tab. Gmail will ask whether to do this for future messages. Select '''Yes'''.
* To make sure list messages never go to spam, create a filter:
*# In the Gmail search box, type <code>lists.uvlists.org</code>.
*# Select the filter icon at the right end of the search box (it looks like a set of sliders).
*# Select '''Create filter'''.
*# Check '''Never send it to Spam''', then select '''Create filter'''.

=== Outlook, Hotmail, Live, and MSN ===

* Open your '''Junk Email''' folder, select the list message, and choose '''Not junk'''.
* If list messages land under '''Other''' instead of '''Focused''', open one and choose '''Move to Focused''', then '''Always move to Focused'''.
* To add the list as a safe sender: go to '''Settings''', then '''Mail''', then '''Junk email'''. Under '''Safe senders and domains''', add <code>lists.uvlists.org</code> and save.

=== Yahoo Mail and AOL Mail ===

* Open the '''Spam''' folder, select the list message, and choose '''Not spam'''.
* Add the list to your contacts (see above).

=== Apple Mail and iCloud ===

* Open the '''Junk''' folder, select the list message, and choose '''Move to Inbox''' or '''Not Junk'''.
* Add the list to your contacts (see above).

=== Comcast and Xfinity ===

* In Xfinity Connect, open the '''Spam''' folder, select the list message, and choose '''Not spam'''.
* Add the list to your contacts (see above).

=== Other email services and programs ===

Look for a spam, junk, or quarantine folder and a button labeled ''Not spam'', ''Not junk'', or ''Release''. Adding the list to your contacts helps with almost every service.

If your email is provided by an employer, a school, or an internet provider's business service, messages may be held in a quarantine that only your IT staff can release. Ask them to allow mail from <code>lists.uvlists.org</code>.

== Messages stopped arriving ==

If messages used to arrive and then stopped, check the items below.

=== Your email filters or rules ===

A filter or rule in your email program may be moving or deleting list messages. This is especially likely if you set up a filter for the old Vital Communities list.

* Look at your filters (sometimes called ''rules'').
* If a filter matches an old subject tag such as <code>[Norwich]</code> or an old address ending in <code>@lists.vitalcommunities.org</code>, update it to match the new tag (such as <code>[Norwich-discuss]</code>) or <code>lists.uvlists.org</code>.
* Make sure no filter sends list messages to the trash or archive without you noticing.

See [[Vital Communities List Migration/Renaming Lists|Renaming Lists]] for how list names and addresses changed.

=== Your delivery was paused because messages were turned away ===

Sometimes an email service refuses to accept a message. This is called a ''bounce''. Common reasons include a full mailbox, an expired or closed email account, or a provider that temporarily blocked incoming mail.

The list keeps track of bounces. If messages to your address are refused on five different days, without a full week of normal delivery in between, the list pauses delivery to you. It then sends you up to three notices, one week apart. If nothing changes, your address is removed from the list about three weeks after delivery was paused.

Because those notices go to the same address that is having trouble, you may never see them.

To fix this:

# Fix the underlying problem first. For example, delete old messages if your mailbox is full, or make sure the account is still active.
# Turn delivery back on. Sign in to the list's website (see [[#Changing your settings on the list website|Changing your settings]] below) and set '''Delivery status''' to '''Enabled'''. If it shows '''Disabled by Bounces''', that confirms bounces were the cause.
# If you were already removed, [[Help:Subscribing|subscribe again]].

If you are not sure what happened, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org]. We can look up whether your address had delivery problems.

=== You paused delivery, or someone else did ===

You can pause delivery yourself, for example while on vacation. If you did this and forgot, messages will not arrive until you turn delivery back on.

Sign in to the list's website and check '''Delivery status'''. It should say '''Enabled'''. If it says:

* '''Disabled''': you (or someone using your account) paused delivery. Change it to '''Enabled'''.
* '''Disabled by Bounces''': see the section above.
* '''Disabled by Owner''': the list administrators paused your delivery. Contact them using the list administrators' address on the list's page.

=== Your email address changed ===

If you changed internet providers, closed an old email account, or started using a new address, the list is still sending to your old address.

# [[Help:Subscribing|Subscribe]] your new address.
# Once messages arrive at the new address, [[Help:Unsubscribing|unsubscribe]] the old one, if it still works.

If you can no longer get into the old address, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org] and we can remove it for you.

=== You were unsubscribed ===

You may have been unsubscribed by accident, for example by selecting an unsubscribe link while cleaning up your inbox. Or the list administrators may have removed your address.

To check, try [[Help:Subscribing|subscribing again]]. If the list says you are already subscribed, your subscription is active; look at your delivery status and filters instead. If you think the list administrators removed you, contact them using the address on the list's page.

== You are getting digests, not individual messages (or the other way around) ==

Each subscriber chooses how to receive messages. This is called the '''delivery mode'''.

* '''Regular''': each message arrives as its own email, shortly after it is posted.
* '''Digests''': messages are collected and sent together in a single email, so you receive fewer emails but each one arrives later. There are several digest styles. '''Summary Digests''' list only the subjects.

If you moved from a Vital Communities list, your old choice (individual messages or digest) was carried over.

If you are expecting individual messages but only get occasional bundles, or the reverse, change your delivery mode. See [[#Changing your settings on the list website|Changing your settings]].

== You are getting two copies of messages ==

There are a few usual reasons for duplicates:

* '''You are subscribed with two addresses''' that both end up in the same inbox. For example, an old address that forwards to your new one. Unsubscribe the one you do not need.
* '''Someone replied to you and to the list at the same time.''' You get one copy directly from them and one from the list. To avoid this, sign in to the list website and set '''Receive list copies (possible duplicates)''' to '''No'''.
* '''Your email forwards to another account''', and you read both.

== You do not see your own messages on the list ==

You post to the list and never see your own message arrive. Usually the message did go out.

* '''Gmail hides your own list messages.''' Gmail sees that the message from the list is the same as the one already in your '''Sent''' folder, so it does not show it again. Other people still received it. Check the list archive to confirm.
* '''Your setting may be turned off.''' Sign in to the list website and make sure '''Receive own postings''' is set to '''Yes'''.
* '''The message may still be waiting for review.''' See the next section.

== Your message did not appear on the list ==

If you sent something and nobody seems to have received it, check the list archive first. If it is not there, one of these is the likely cause.

=== You sent from a different address ===

The list only recognizes the address you subscribed. If you send from another address, even one that ends up in the same inbox, the list treats you as a stranger and holds your message. Send from the subscribed address.

=== You sent to the wrong address ===

Messages must go to the list's posting address, such as <code>norwich-discuss@lists.uvlists.org</code>. The address ending in ''-join'' or ''-leave'' is only for joining or leaving, and the address ending in ''-owner'' goes to the list administrators.

Messages sent to an old Vital Communities address do not reach the new list. You get an automatic reply pointing to the new address instead.

Adding the [[#Add the list to your contacts|list's contact card]] to your address book is the easiest way to always send to the right address.

=== You replied to one person instead of the list ===

On UVLists, '''Reply''' sends your answer only to the person who wrote the message. To answer the whole list, use '''Reply All''', or start a new message to the list's posting address.

This is on purpose, so that private replies do not accidentally go to everyone.

=== Your message is waiting for review ===

Volunteer moderators review some messages before they go out, for example messages from an address that is not subscribed, or messages addressed to many people at once. Your message will be sent once a moderator approves it. Because moderators are volunteers, this can take some time.

Messages are also held for review if they are too large. The limit is about 40 KB, which a single photo or a long chain of quoted replies can easily exceed. To keep your message small:

* Do not attach photos or files. Share a link instead.
* Delete old quoted text at the bottom before sending.
* Send plain text if your email program offers it, and remove large logos or images from your signature.

See [[Help:Posting|Send a message]] for more about posting.

== Messages look strange ==

* '''The subject starts with something in brackets''', such as <code>[Norwich-discuss]</code>. This is normal. The tag tells you which list the message came from.
* '''A message arrived with an attachment instead of the text''', or the formatting looks odd. Some email programs display list messages differently. Try opening it on another device or in a web browser. If it keeps happening, let us know.
* '''Links or pictures do not show.''' Many email programs block images until you allow them. Look for a button such as ''Show images'' or ''Download pictures''.

== You are getting messages you did not sign up for ==

If you do not remember subscribing, you may have been added when the list moved from Vital Communities, or someone may have subscribed you. Either way, you can leave at any time. See [[Help:Unsubscribing|Leave a list]].

A UVLists list will never ask you for your password, bank details, or other private information by email. If you get a message like that, do not reply. Report it to [mailto:abuse@uvlists.org abuse@uvlists.org].

== Changing your settings on the list website ==

Many fixes on this page involve your subscription settings. To change them:

# Open the list's page in the [[:Category:Mailing lists|list directory]] and select the '''Web Interface''' link. You can also use the link in the list's contact card.
# Select '''Sign In''' at the top of the page.
# If you have not used the site before, select '''Sign Up''' and create an account '''with the same email address you subscribed with'''. You will receive an email to confirm the account.
# Once signed in, return to the list's page and select '''Manage Subscription'''.
# Change '''Delivery status''', '''Delivery mode''', or the other options, then save.

To see all your lists at once, open the menu under your name at the top of the page and choose '''Subscriptions'''.

If you find the website difficult to use, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org] and tell us what you would like changed. We are happy to do it for you.

== Still need help? ==

Email '''[mailto:helpdesk@uvlists.org helpdesk@uvlists.org]'''. UVLists is run by volunteers, and every request is tracked so it is not lost.

To help us solve the problem quickly, please include:

* The '''name of the list''', such as Norwich-Discuss.
* The '''email address you subscribed with'''.
* '''What is happening''', for example "I stopped getting messages last week" or "my post never appeared."
* '''When it started''', and the date and time of a missing message, if you know it.
* '''Any error message''' you received. If you got a message saying your email could not be delivered, forward it to us.

You will get a reply with a ticket number in the subject line. Reply to that message to add details, and keep the ticket number in the subject.

For questions about a list's rules or a decision by its administrators, contact the list administrators using the address on the list's page.

{{Mailing List Help Footer}}

Help:Unsubscribing

2026-10-22T01:18:28Z

UVListsBot: Create unsubscribe help: leave by email, Unsubscribe button, website, alternatives, troubleshooting

You can leave a UVLists list at any time. Leaving takes a minute or two, and you do not need an account or a password.

There are three ways to leave:

* [[#Leave by email|Send an email]] to the list's leave address. This is the simplest way.
* [[#Use your email program's Unsubscribe button|Use the Unsubscribe button]] in your email program, if it shows one.
* [[#Leave through the website|Use the list's website]], if you have an account there.

Whichever way you choose, the list will ask you to confirm. This protects you from being removed by someone else.

If you only want fewer emails, or a break, you may not need to leave at all. See [[#Alternatives to leaving|Alternatives to leaving]].

== Before you leave ==

* '''Know which address is subscribed.''' You can only leave from the address you joined with. If you have more than one email address, or one address forwards to another, check which one the list messages are sent to. See [[#Finding which address is subscribed|Finding which address is subscribed]].
* '''Leaving one list does not affect others.''' If you are on several lists, leave each one separately.

== Leave by email ==

# Find the list's leave address. It is the posting address with <code>-leave</code> added before the <code>@</code>. For example:
#: <code>norwich-discuss-leave@lists.uvlists.org</code>
#: Each list's page in the [[:Category:Mailing lists|list directory]] shows its leave address in the '''Join or leave''' section.
# Send an email to the leave address '''from the address that is subscribed'''. The subject and message can be blank.
# Within a few minutes you will receive a confirmation message from the list.
# Confirm by replying to it without changing the subject, or by following the instructions in the message.
# You will receive a short goodbye message when you have been removed.

Do not send "unsubscribe" to the list's posting address. That address goes to the list (or to its moderators), not to the system that handles leaving.

== Use your email program's Unsubscribe button ==

Many email programs, including Gmail, Outlook, Yahoo Mail, and Apple Mail, show an '''Unsubscribe''' link or button near the sender's name at the top of list messages.

# Open any message from the list.
# Select '''Unsubscribe''' near the top of the message.
# Your email program sends a leave request for you.
# Watch for the confirmation message from the list, and confirm as described above.

If you do not see an Unsubscribe button, use one of the other methods.

== Leave through the website ==

If you have an account on the list website, you can leave there.

# Open the list's page in the [[:Category:Mailing lists|list directory]] and select the '''Web Interface''' link.
# Select '''Sign In''' at the top of the page and sign in with your subscribed address.
# On the list's page, select '''Unsubscribe'''.

If you do not have an account, it is easier to [[#Leave by email|leave by email]] than to create one.

To see every list you belong to, sign in and choose '''Subscriptions''' from the menu under your name.

== Please do not mark list messages as spam ==

It can be tempting to press '''Spam''' or '''Junk''' to make list messages go away. Please do not.

* '''It does not unsubscribe you.''' Messages keep coming, they just go to your spam folder.
* '''It can hurt delivery for your neighbors.''' Email services notice when people mark messages from a list as spam, and may start sending that list's messages to spam for everyone.

Use one of the methods above instead. If something is not working, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org] and we will remove you.

== Alternatives to leaving ==

If the list is useful but the volume is not, try one of these. Sign in to the list website, open the list, and select '''Manage Subscription''' to change them. See [[Help:Delivery problems#Changing your settings on the list website|Changing your settings]] for step-by-step help.

=== Get fewer emails ===

Change '''Delivery mode''' from '''Regular''' to a digest. Instead of one email per message, you get messages bundled together. '''Summary Digests''' list only the subjects, so you can skim and read just what interests you in the archive.

=== Take a break ===

Going on vacation, or just need a pause? Change '''Delivery status''' to '''Disabled'''. You stay subscribed but receive nothing. When you are ready, change it back to '''Enabled'''.

=== Read on the web instead ===

Most lists have a public archive on the web. You can turn off delivery as described above and read the archive when you like. The archive link is on each list's page.

== Changing to a new email address ==

There is no need to leave and rejoin.

# [[Help:Subscribing|Subscribe]] your new address.
# Once messages are arriving at the new address, leave the list from the old address.

If you no longer have access to the old address, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org] and we will remove it for you.

== Lists that moved from Vital Communities ==

If you were on a Vital Communities town list, your subscription moved to UVLists automatically at your list's cutover. To leave now, use the new UVLists leave address (for example, <code>norwich-discuss-leave@lists.uvlists.org</code>). The old Vital Communities unsubscribe addresses no longer apply to the new list.

See the [[Vital Communities List Migration|migration page]] for each list's dates and [[Vital Communities List Migration/Renaming Lists|Renaming Lists]] for how addresses changed.

== Common problems ==

=== I unsubscribed but I still get messages ===

* '''You may not have confirmed.''' Leaving is not finished until you confirm. Check your inbox and spam folder for the confirmation message.
* '''A message may already have been on its way.''' One or two messages, or a final digest, can arrive shortly after you leave.
* '''You may be subscribed with another address.''' See the next section.
* '''You may be on more than one list.''' Check the tag at the start of the subject, such as <code>[Norwich-discuss]</code>, to see which list a message came from.

=== Finding which address is subscribed ===

If you have several email addresses, or one forwards to another, it can be hard to tell which one is on the list. Try this:

* Look at the '''To''' line of a list message. It usually shows the list's address, not yours, so look further: in many email programs, you can view the message's details (sometimes called ''Show original'', ''View source'', or ''Message details'') and look for your own address near the top.
* Try leaving from each address you own. A request from an address that is not subscribed does no harm; you will simply be told the address is not a member.
* Or email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org], and forward one of the list messages you received. We can tell you which address it was sent to.

=== The confirmation message never arrived ===

Check your spam or junk folder, and make sure you sent the leave request from the subscribed address. If it still does not arrive, send the request again or email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org].

=== I do not remember subscribing ===

You may have been moved over from a Vital Communities list, or someone else may have subscribed your address. Either way, you can leave using any method on this page.

== Still need help? ==

If you cannot leave a list, email '''[mailto:helpdesk@uvlists.org helpdesk@uvlists.org]'''. Please include:

* The '''name of the list''', such as Norwich-Discuss.
* The '''email address''' you want removed.
* If you are not sure which address it is, '''forward one of the list messages''' you received.

We will remove you and let you know when it is done.

{{Mailing List Help Footer}}

Help:Posting

2026-10-22T01:18:27Z

UVListsBot: Create posting help: posting address, contact cards, Reply vs Reply All, size limit, moderation, etiquette

Posting to a UVLists list is just sending an email. You write a message in your usual email program, address it to the list, and the list sends a copy to every subscriber. You do not need to visit a website or sign in.

This page explains how to send a message, how to reply, what to expect after you send, and what to do if your message does not appear.

== Before you post ==

* '''You must be subscribed.''' Only subscribers can post. If you have not joined yet, see [[Help:Subscribing|Join a list]].
* '''Send from your subscribed address.''' The list recognizes you by the email address you subscribed with. If you send from a different address, even one that arrives in the same inbox, the list treats you as a stranger and holds your message.
* '''Read the list's guidelines.''' Each list's page in the [[:Category:Mailing lists|list directory]] describes what the list is for and its rules, including how often business announcements are welcome.
* '''Remember that your message is public.''' Your message goes to every subscriber. On most lists it is also saved in a public archive on the web that anyone can read. Your name and email address appear with it.

== Find the list's posting address ==

Each list has one address for posts. It looks like this:

: <code>town-discuss@lists.uvlists.org</code>

For example, the Norwich list's posting address is <code>norwich-discuss@lists.uvlists.org</code>.

You can find the posting address:

* On the list's page in the [[:Category:Mailing lists|list directory]], under '''Posting Address'''.
* In the welcome message you received when you joined.
* In the list's contact card (see below).

Other addresses belong to the list but are '''not''' for posting:

{| class="wikitable"
! Address ends in
! What it does
|-
| <code>-join</code>
| Subscribes you to the list
|-
| <code>-leave</code>
| Unsubscribes you from the list
|-
| <code>-owner</code>
| Reaches the volunteer list administrators, not the members
|}

=== Save the list to your contacts ===

The easiest way to always use the right address is to add the list to your address book. Each list has a ready-made contact card (a ''vCard'').

# Open the list's page in the [[:Category:Mailing lists|list directory]].
# In the '''Mailing List Info''' box, select the link next to '''VCard File'''. It looks like <code><nowiki>https://go.uvlists.org/norwich-discuss.vcf</nowiki></code>.
# Accept when your phone or computer offers to add the contact.

After that, start typing the list's name (for example, ''Norwich Discuss'') in the '''To''' line, and your email program will fill in the address for you. Having the list in your contacts also helps keep list messages out of your spam folder.

If you used a Vital Communities list before, delete or update your old contact for it. Old addresses ending in <code>@lists.vitalcommunities.org</code> no longer reach the list. See [[Vital Communities List Migration/Renaming Lists|Renaming Lists]].

== Send a new message ==

# Open your email program and start a new message.
# In the '''To''' line, enter the list's posting address, or choose the list from your contacts.
# Write a clear, specific subject. "Lost dog near the town green" is more useful to your neighbors than "Help!" or "Question".
# Write your message.
# Sign your message with your name. Many lists ask members to use their real names.
# Send it.

=== Tips for a good post ===

* '''One topic per message.''' If you have two unrelated things to say, send two messages with their own subjects. This makes them easier to find and reply to.
* '''Paste links in full.''' Copy the whole web address (for example, <code><nowiki>https://www.example.org/events/fall-fair</nowiki></code>) into your message so readers can see where it goes. Avoid shortened links.
* '''Do not attach photos or files.''' See [[#Keep messages small|Keep messages small]] below.
* '''Check before sending.''' A message cannot be taken back once it has gone out.
* '''Put the list in the To line by itself.''' Do not send the same message to the list and to a long list of other people at once, and do not put the list address in '''Bcc'''. Messages like that are held for review.

== Reply to a message ==

When you reply to a list message, decide who you want to reach.

* '''To answer only the person who wrote''', use '''Reply'''. Your answer goes only to them, not to the list.
* '''To answer everyone on the list''', use '''Reply All'''. Your answer goes to the list (and a copy to the person who wrote).

UVLists sends ordinary replies only to the person who wrote, so that private replies do not accidentally go to the whole community. If your reply did not show up on the list, you probably used '''Reply''' instead of '''Reply All'''.

When replying:

* Keep the original subject so others can follow the conversation. It starts with a tag in brackets, such as <code>[Norwich-discuss]</code>. You can leave the tag; the list will not add it twice.
* Delete most of the quoted message below your reply. Keep only what readers need to understand your answer.
* If you are changing the subject of the conversation, start a new message instead of replying.

== Keep messages small ==

Messages larger than about 40 KB are held for a moderator to review. That is enough for several pages of text, but a single photo, a large logo in your signature, or a long chain of quoted replies can go over it.

To keep your message small:

* Do not attach photos, flyers, or documents. Put them online (for example, on a town or organization website, or a photo or file sharing service) and paste the link into your message.
* Delete old quoted text before sending.
* Remove images from your email signature.
* If your email program offers a plain text option, use it.

== What happens after you send ==

Messages from subscribers normally go out within a few minutes. The list sends a copy to every subscriber and adds it to the archive.

Some subscribers receive messages in a ''digest'', a single email that bundles several messages together. They will see your post later than everyone else.

=== Seeing your own message ===

Most people get a copy of their own posts, so you can tell they went out. Exceptions:

* '''Gmail hides your own list messages''' because it already has the same message in your '''Sent''' folder. Other people still received it. Check the list archive to confirm.
* You may have turned off '''Receive own postings''' in your list settings. See [[Help:Delivery problems#Changing your settings on the list website|Changing your settings]].

=== When a message is held for review ===

A volunteer moderator reviews a message before it goes out when, for example:

* It was sent from an address that is not subscribed.
* It is larger than about 40 KB.
* It is addressed to many people at once, or the list address is only in '''Bcc'''.
* It looks like a request to join or leave (for example, a message with just the word "unsubscribe"). Send those to the <code>-join</code> or <code>-leave</code> address instead.
* The list administrators have chosen to review your posts.

You may receive an email saying your message is waiting for approval. You do not need to send it again. Because moderators are volunteers, a review can take some time. If the moderator declines your message, you will usually receive a note explaining why.

=== When a message is rejected ===

Occasionally a message is turned away entirely, and you receive an error message back. This can happen if the message looks like spam or contains a virus. If this happens to an ordinary message, forward the error to [mailto:helpdesk@uvlists.org helpdesk@uvlists.org].

== Correcting a mistake ==

A message cannot be recalled or edited after it is sent. It goes to every subscriber right away.

If you make a mistake, send a short follow-up to the list with the correction, using the same subject. If something must be removed from the archive, for example private information posted by accident, contact the list administrators using the <code>-owner</code> address on the list's page.

== Being a good neighbor ==

* '''Be civil and respectful.''' Disagree with ideas, not people.
* '''Stay local.''' Town lists are for matters that affect that town. For events or items that concern the whole Upper Valley, use a regional forum instead of posting to many town lists.
* '''Keep promotion occasional.''' Business announcements are usually welcome now and then, but not more than about once a month.
* '''Do not forward private messages''' to the list without permission from everyone involved.
* '''Lists are not for emergencies.''' Many subscribers read in a daily digest or check email only occasionally. For urgent safety matters, call 911 or contact the town directly.
* '''Have a concern about another member's post?''' Do not reply on the list. Write to the list administrators using the <code>-owner</code> address on the list's page. To report spam, harassment, or abuse, email [mailto:abuse@uvlists.org abuse@uvlists.org].

== Common problems ==

; My message never appeared
: Check the list archive first. If it is not there, make sure you sent from your subscribed address, to the posting address, and used '''Reply All''' when replying. It may also be waiting for review. See [[Help:Delivery problems#Your message did not appear on the list|Your message did not appear]].

; I got an automatic reply saying the list has moved
: You sent to an old Vital Communities address. Send your message again to the new address, and update your contacts.

; I got a notice that my message is waiting because I am not a member
: You sent from an address that is not subscribed. Send from your subscribed address, or [[Help:Subscribing|subscribe]] the address you want to use.

; My replies go to one person instead of the list
: Use '''Reply All'''. See [[#Reply to a message|Reply to a message]].

== Still need help? ==

Email '''[mailto:helpdesk@uvlists.org helpdesk@uvlists.org]'''. Please include the name of the list, the email address you subscribed with, the date and time you sent your message, and its subject. If you received an error message, forward it to us.

For questions about a list's rules or a moderation decision, contact the list administrators using the <code>-owner</code> address on the list's page.

{{Mailing List Help Footer}}

Help:Delivery problems

2026-10-22T01:10:46Z

UVListsBot: Create delivery help page: spam folders, contact cards, bounces, delivery settings, missing posts, helpdesk contact

Not getting list messages, or something seems wrong with the ones you do get? This page walks through the most common problems and how to fix them. You do not need any technical knowledge to follow it.

Most delivery problems come down to one of a few things: messages are being sorted into a spam or other folder, you are subscribed with a different address than you think, your email provider is turning messages away, or your list settings have changed.

If you work through this page and still need help, email '''[mailto:helpdesk@uvlists.org helpdesk@uvlists.org]'''. See [[#Still need help?|Still need help?]] at the bottom of this page for what to include.

== Start here: quick checklist ==

Before reading further, try these steps. They solve most problems.

# '''Check your spam or junk folder.''' Also check any other folders or tabs your email uses, such as ''Promotions'', ''Updates'', ''Forums'', ''Other'', or ''Clutter''.
# '''Search your mailbox''' for the list name (for example, ''Norwich-Discuss'') or for <code>lists.uvlists.org</code>.
# '''Make sure you are checking the right email account.''' If you have more than one address, the list only sends to the one you subscribed.
# '''Add the list to your contacts.''' Each list has a contact card you can download. See [[#Add the list to your contacts|Add the list to your contacts]].
# '''Check the list archive''' to see whether anyone has posted recently. Quiet lists sometimes go days without a message. The archive link is on the list's page in the [[:Category:Mailing lists|list directory]].

== Add the list to your contacts ==

Adding the list to your address book is one of the most helpful things you can do. It helps in two ways:

* '''Fewer messages go to spam.''' Many email services trust messages from addresses in your contacts.
* '''Your messages go to the right place.''' When you write to the list, your email program will fill in the correct, current posting address for you. This matters most for lists that moved from Vital Communities, because the old addresses no longer work.

Every list has a ready-made contact card (also called a ''vCard''). To get it:

# Open the list's page in the [[:Category:Mailing lists|list directory]].
# In the '''Mailing List Info''' box, find '''VCard File''' and select the link. It looks like <code><nowiki>https://go.uvlists.org/norwich-discuss.vcf</nowiki></code>.
# Your phone or computer will offer to add the contact. Accept it.

You can also reach the card from the list's short web page at <code>go.uvlists.org</code> (for example, <code><nowiki>https://go.uvlists.org/norwich</nowiki></code>), which is where the QR codes on printed flyers lead.

The card includes the list's posting address, a link to change your subscription settings, and a link to the archives.

If you already had a contact for the list under its old Vital Communities address, delete or update the old contact so your email program does not keep suggesting it.

== Messages are going to spam or another folder ==

Email services try to guess which messages you want. Mailing lists sometimes get sorted incorrectly, especially after a list changes its address.

The fix is the same everywhere: find a list message, tell your email service it is not spam, and add the list to your contacts. Doing this once or twice usually trains your email service to deliver future messages normally.

=== Gmail ===

* Open the message in your '''Spam''' folder and select '''Report not spam''' (or '''Not spam''').
* If list messages land in the '''Promotions''', '''Updates''', or '''Forums''' tab, drag one message to the '''Primary''' tab. Gmail will ask whether to do this for future messages. Select '''Yes'''.
* To make sure list messages never go to spam, create a filter:
*# In the Gmail search box, type <code>lists.uvlists.org</code>.
*# Select the filter icon at the right end of the search box (it looks like a set of sliders).
*# Select '''Create filter'''.
*# Check '''Never send it to Spam''', then select '''Create filter'''.

=== Outlook, Hotmail, Live, and MSN ===

* Open your '''Junk Email''' folder, select the list message, and choose '''Not junk'''.
* If list messages land under '''Other''' instead of '''Focused''', open one and choose '''Move to Focused''', then '''Always move to Focused'''.
* To add the list as a safe sender: go to '''Settings''', then '''Mail''', then '''Junk email'''. Under '''Safe senders and domains''', add <code>lists.uvlists.org</code> and save.

=== Yahoo Mail and AOL Mail ===

* Open the '''Spam''' folder, select the list message, and choose '''Not spam'''.
* Add the list to your contacts (see above).

=== Apple Mail and iCloud ===

* Open the '''Junk''' folder, select the list message, and choose '''Move to Inbox''' or '''Not Junk'''.
* Add the list to your contacts (see above).

=== Comcast and Xfinity ===

* In Xfinity Connect, open the '''Spam''' folder, select the list message, and choose '''Not spam'''.
* Add the list to your contacts (see above).

=== Other email services and programs ===

Look for a spam, junk, or quarantine folder and a button labeled ''Not spam'', ''Not junk'', or ''Release''. Adding the list to your contacts helps with almost every service.

If your email is provided by an employer, a school, or an internet provider's business service, messages may be held in a quarantine that only your IT staff can release. Ask them to allow mail from <code>lists.uvlists.org</code>.

== Messages stopped arriving ==

If messages used to arrive and then stopped, check the items below.

=== Your email filters or rules ===

A filter or rule in your email program may be moving or deleting list messages. This is especially likely if you set up a filter for the old Vital Communities list.

* Look at your filters (sometimes called ''rules'').
* If a filter matches an old subject tag such as <code>[Norwich]</code> or an old address ending in <code>@lists.vitalcommunities.org</code>, update it to match the new tag (such as <code>[Norwich-discuss]</code>) or <code>lists.uvlists.org</code>.
* Make sure no filter sends list messages to the trash or archive without you noticing.

See [[Vital Communities List Migration/Renaming Lists|Renaming Lists]] for how list names and addresses changed.

=== Your delivery was paused because messages were turned away ===

Sometimes an email service refuses to accept a message. This is called a ''bounce''. Common reasons include a full mailbox, an expired or closed email account, or a provider that temporarily blocked incoming mail.

The list keeps track of bounces. If messages to your address are refused on five different days, without a full week of normal delivery in between, the list pauses delivery to you. It then sends you up to three notices, one week apart. If nothing changes, your address is removed from the list about three weeks after delivery was paused.

Because those notices go to the same address that is having trouble, you may never see them.

To fix this:

# Fix the underlying problem first. For example, delete old messages if your mailbox is full, or make sure the account is still active.
# Turn delivery back on. Sign in to the list's website (see [[#Changing your settings on the list website|Changing your settings]] below) and set '''Delivery status''' to '''Enabled'''. If it shows '''Disabled by Bounces''', that confirms bounces were the cause.
# If you were already removed, [[Help:Subscribing|subscribe again]].

If you are not sure what happened, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org]. We can look up whether your address had delivery problems.

=== You paused delivery, or someone else did ===

You can pause delivery yourself, for example while on vacation. If you did this and forgot, messages will not arrive until you turn delivery back on.

Sign in to the list's website and check '''Delivery status'''. It should say '''Enabled'''. If it says:

* '''Disabled''': you (or someone using your account) paused delivery. Change it to '''Enabled'''.
* '''Disabled by Bounces''': see the section above.
* '''Disabled by Owner''': the list administrators paused your delivery. Contact them using the list administrators' address on the list's page.

=== Your email address changed ===

If you changed internet providers, closed an old email account, or started using a new address, the list is still sending to your old address.

# [[Help:Subscribing|Subscribe]] your new address.
# Once messages arrive at the new address, [[Help:Unsubscribing|unsubscribe]] the old one, if it still works.

If you can no longer get into the old address, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org] and we can remove it for you.

=== You were unsubscribed ===

You may have been unsubscribed by accident, for example by selecting an unsubscribe link while cleaning up your inbox. Or the list administrators may have removed your address.

To check, try [[Help:Subscribing|subscribing again]]. If the list says you are already subscribed, your subscription is active; look at your delivery status and filters instead. If you think the list administrators removed you, contact them using the address on the list's page.

== You are getting digests, not individual messages (or the other way around) ==

Each subscriber chooses how to receive messages. This is called the '''delivery mode'''.

* '''Regular''': each message arrives as its own email, shortly after it is posted.
* '''Digests''': messages are collected and sent together in a single email, so you receive fewer emails but each one arrives later. There are several digest styles. '''Summary Digests''' list only the subjects.

If you moved from a Vital Communities list, your old choice (individual messages or digest) was carried over.

If you are expecting individual messages but only get occasional bundles, or the reverse, change your delivery mode. See [[#Changing your settings on the list website|Changing your settings]].

== You are getting two copies of messages ==

There are a few usual reasons for duplicates:

* '''You are subscribed with two addresses''' that both end up in the same inbox. For example, an old address that forwards to your new one. Unsubscribe the one you do not need.
* '''Someone replied to you and to the list at the same time.''' You get one copy directly from them and one from the list. To avoid this, sign in to the list website and set '''Receive list copies (possible duplicates)''' to '''No'''.
* '''Your email forwards to another account''', and you read both.

== You do not see your own messages on the list ==

You post to the list and never see your own message arrive. Usually the message did go out.

* '''Gmail hides your own list messages.''' Gmail sees that the message from the list is the same as the one already in your '''Sent''' folder, so it does not show it again. Other people still received it. Check the list archive to confirm.
* '''Your setting may be turned off.''' Sign in to the list website and make sure '''Receive own postings''' is set to '''Yes'''.
* '''The message may still be waiting for review.''' See the next section.

== Your message did not appear on the list ==

If you sent something and nobody seems to have received it, check the list archive first. If it is not there, one of these is the likely cause.

=== You sent from a different address ===

The list only recognizes the address you subscribed. If you send from another address, even one that ends up in the same inbox, the list treats you as a stranger and holds your message. Send from the subscribed address.

=== You sent to the wrong address ===

Messages must go to the list's posting address, such as <code>norwich-discuss@lists.uvlists.org</code>. The address ending in ''-join'' or ''-leave'' is only for joining or leaving, and the address ending in ''-owner'' goes to the list administrators.

Messages sent to an old Vital Communities address do not reach the new list. You get an automatic reply pointing to the new address instead.

Adding the [[#Add the list to your contacts|list's contact card]] to your address book is the easiest way to always send to the right address.

=== You replied to one person instead of the list ===

On UVLists, '''Reply''' sends your answer only to the person who wrote the message. To answer the whole list, use '''Reply All''', or start a new message to the list's posting address.

This is on purpose, so that private replies do not accidentally go to everyone.

=== Your message is waiting for review ===

Volunteer moderators review some messages before they go out, particularly from new members. Your message will be sent once a moderator approves it. Because moderators are volunteers, this can take some time.

Messages are also held for review if they are too large. The limit is about 40 KB, which a single photo or a long chain of quoted replies can easily exceed. To keep your message small:

* Do not attach photos or files. Share a link instead.
* Delete old quoted text at the bottom before sending.
* Send plain text if your email program offers it, and remove large logos or images from your signature.

See [[Help:Posting|Send a message]] for more about posting.

== Messages look strange ==

* '''The subject starts with something in brackets''', such as <code>[Norwich-discuss]</code>. This is normal. The tag tells you which list the message came from.
* '''A message arrived with an attachment instead of the text''', or the formatting looks odd. Some email programs display list messages differently. Try opening it on another device or in a web browser. If it keeps happening, let us know.
* '''Links or pictures do not show.''' Many email programs block images until you allow them. Look for a button such as ''Show images'' or ''Download pictures''.

== You are getting messages you did not sign up for ==

If you do not remember subscribing, you may have been added when the list moved from Vital Communities, or someone may have subscribed you. Either way, you can leave at any time. See [[Help:Unsubscribing|Leave a list]].

A UVLists list will never ask you for your password, bank details, or other private information by email. If you get a message like that, do not reply. Report it to [mailto:abuse@uvlists.org abuse@uvlists.org].

== Changing your settings on the list website ==

Many fixes on this page involve your subscription settings. To change them:

# Open the list's page in the [[:Category:Mailing lists|list directory]] and select the '''Web Interface''' link. You can also use the link in the list's contact card.
# Select '''Sign In''' at the top of the page.
# If you have not used the site before, select '''Sign Up''' and create an account '''with the same email address you subscribed with'''. You will receive an email to confirm the account.
# Once signed in, return to the list's page and select '''Manage Subscription'''.
# Change '''Delivery status''', '''Delivery mode''', or the other options, then save.

To see all your lists at once, open the menu under your name at the top of the page and choose '''Subscriptions'''.

If you find the website difficult to use, email [mailto:helpdesk@uvlists.org helpdesk@uvlists.org] and tell us what you would like changed. We are happy to do it for you.

== Still need help? ==

Email '''[mailto:helpdesk@uvlists.org helpdesk@uvlists.org]'''. UVLists is run by volunteers, and every request is tracked so it is not lost.

To help us solve the problem quickly, please include:

* The '''name of the list''', such as Norwich-Discuss.
* The '''email address you subscribed with'''.
* '''What is happening''', for example "I stopped getting messages last week" or "my post never appeared."
* '''When it started''', and the date and time of a missing message, if you know it.
* '''Any error message''' you received. If you got a message saying your email could not be delivered, forward it to us.

You will get a reply with a ticket number in the subject line. Reply to that message to add details, and keep the ticket number in the subject.

For questions about a list's rules or a decision by its administrators, contact the list administrators using the address on the list's page.

{{Mailing List Help Footer}}

Vital Communities List Migration

2026-10-20T19:41:09Z

UVListsBot: Schedule groton_area and west_* lists; Woodstock remains unscheduled

== Overview ==

As described in [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists]], UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.

For help with a migration or a question about a particular list, see [[Contact|Contact UVLists]].

== What subscribers need to do ==

Subscribers do not need to take action to move to the new UVLists list. Unless they unsubscribe from the Vital Communities list before its '''Cutover Date''', their subscription and delivery preference will be transferred. After the move, use the new list address shown on the list’s UVLists page.

== What list administrators need to do ==

List administrators should review the list’s public page for accuracy, including its purpose, guidelines, owner-contact address, and joining instructions. The [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] explains what to check and how to submit corrections.

== Migration schedule ==

The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.

The status column uses these terms:

{| class="wikitable"
! Status
! Meaning
|-
| Not migrated
| Migration has not started.
|-
| Signup open
| Existing Vital Communities subscribers have been notified. The new list is available for subscriptions but not yet for posting.
|-
| Migrated
| The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address.
|-
| Complete
| The prior Vital Communities list has been fully retired.
|}

{| class="wikitable sortable"
|+ Migration Schedule
|-
! VC List !! UVL List !! Announcement Date !! Cutover Date !! Current Status
|-
| barnard@lists.vitalcommunities.org || [[Lists:Barnard]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| bradford@lists.vitalcommunities.org || [[Lists:Bradford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| bridgewater@lists.vitalcommunities.org || [[Lists:Bridgewater]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| brownsville@lists.vitalcommunities.org || [[Lists:Brownsville]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| chelsea@lists.vitalcommunities.org || [[Lists:Chelsea]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| claremont@lists.vitalcommunities.org || [[Lists:Claremont]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| enfield@lists.vitalcommunities.org || [[Lists:Enfield]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| fairlee@lists.vitalcommunities.org || [[Lists:Fairlee]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| grafton@lists.vitalcommunities.org || [[Lists:Grafton]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| groton_area@lists.vitalcommunities.org || [[Lists:Groton]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| hartford@lists.vitalcommunities.org || [[Lists:Hartford]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| haverhill@lists.vitalcommunities.org || [[Lists:Haverhill]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lebanon@lists.vitalcommunities.org || [[Lists:Lebanon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lyme@lists.vitalcommunities.org || [[Lists:Lyme]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| mascoma@lists.vitalcommunities.org || [[Lists:Mascoma]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| newbury@lists.vitalcommunities.org || [[Lists:Newbury]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| norwich@lists.vitalcommunities.org || [[Lists:Norwich]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| orford@lists.vitalcommunities.org || [[Lists:Orford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| piermont@lists.vitalcommunities.org || [[Lists:Piermont]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| plainfield@lists.vitalcommunities.org || [[Lists:Plainfield]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| pomfret@lists.vitalcommunities.org || [[Lists:Pomfret]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| reading@lists.vitalcommunities.org || [[Lists:Reading]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| royalton@lists.vitalcommunities.org || [[Lists:Royalton]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| ryegate@lists.vitalcommunities.org || [[Lists:Ryegate]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| sharon@lists.vitalcommunities.org || [[Lists:Sharon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| strafford@lists.vitalcommunities.org || [[Lists:Strafford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| thetford@lists.vitalcommunities.org || [[Lists:Thetford]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| tunbridge@lists.vitalcommunities.org || [[Lists:Tunbridge]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| west_fairlee@lists.vitalcommunities.org || [[Lists:West Fairlee]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| west_lebanon@lists.vitalcommunities.org || [[Lists:West Lebanon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| west_newbury@lists.vitalcommunities.org || [[Lists:West Newbury]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| west_norwich@lists.vitalcommunities.org || [[Lists:West Norwich]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Not Migrated
|}

Each linked UVLists list page includes its new address, joining instructions, and local guidelines.

== Not yet scheduled ==

{| class="wikitable"
! Vital Communities list
! Planning status
|-
| woodstock@lists.vitalcommunities.org
| List page in preparation; schedule to be determined.
|}

== Migration process ==

Each list follows this general process. The communication templates should be reviewed and updated with the list’s specific dates, addresses, and contacts before they are sent.

# '''Announce the move.''' On the '''Announcement Date''', send the [[Vital Communities List Migration/01-move-announcement|move announcement]] to the existing list. It explains the new list, the opt-out process, and the planned cutover date.
# '''Review list information and allow opt-out.''' List administrators receive the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the '''Cutover Date'''.
# '''Cut over the list.''' On the '''Cutover Date''', send the [[Vital Communities List Migration/03-closure-announcement|closure announcement]] to remaining subscribers. Place the previous list in '''moderated mode''' so new posts are not distributed, and enable the [[Vital Communities List Migration/05-old-list-autoresponse|old-list autoresponse]] to direct senders to the new list for the period set for that migration.
# '''Transfer subscribers and welcome them.''' Import subscribers who did not opt out, including their delivery preferences. Then send the [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] with information about the list, its moderators, and where to get help.

[[Category:List Migration]]

MediaWiki:Uvlists-mobile-menu

2026-10-20T18:06:51Z

UVListsBot: Mobile main menu links (read by the minerva-main-menu patch)

Links in the mobile view's main menu, after Home. Each line that starts with an asterisk is one link: the page name or web address, the label, and the icon, separated by "|". Every other line, like this one, is ignored.

Icons: article, articles, bell, book, bookmark, browser, calendar, camera, chart, clock, download, edit, feedback, flag, folderPlaceholder, globe, heart, help, history, image, imageGallery, info, key, lightbulb, link, linkExternal, listBullet, lock, map, mapPin, message, newspaper, notice, ongoingConversation, printer, search, speechBubble, speechBubbles, star, table, userAdd, userAvatar, userContributions, userGroup. Other names show as "link".

* Category:Mailing_lists|Our Mailing Lists|message
* News|News and Updates|newspaper
* Executive_Committee|Board of Directors|userGroup
* Meetings|Meeting Information|calendar

MediaWiki:Uvlists-mobile-menu

2026-10-20T18:06:44Z

UVListsBot: Test

Links in the mobile view's main menu, after Home. Each line that starts with an asterisk is one link: the page name or web address, the label, and the icon, separated by "|". Every other line, like this one, is ignored.

Icons: article, articles, bell, book, bookmark, browser, calendar, camera, chart, clock, download, edit, feedback, flag, folderPlaceholder, globe, heart, help, history, image, imageGallery, info, key, lightbulb, link, linkExternal, listBullet, lock, map, mapPin, message, newspaper, notice, ongoingConversation, printer, search, speechBubble, speechBubbles, star, table, userAdd, userAvatar, userContributions, userGroup. Other names show as "link".

* Category:Mailing_lists|Our Mailing Lists|message
* News|News TEST|bogusIcon
* Executive_Committee|Board of Directors|userGroup
* Meetings|Meeting Information|calendar

MediaWiki:Uvlists-mobile-menu

2026-10-20T18:05:41Z

UVListsBot: Test

Links in the mobile view's main menu, after Home. One per line:
* page or web address|label|icon
Icons: article, articles, bell, book, bookmark, browser, calendar, camera, chart, clock, download, edit, feedback, flag, folderPlaceholder, globe, heart, help, history, image, imageGallery, info, key, lightbulb, link, linkExternal, listBullet, lock, map, mapPin, message, newspaper, notice, ongoingConversation, printer, search, speechBubble, speechBubbles, star, table, userAdd, userAvatar, userContributions, userGroup. Other names show as "link". Lines not starting with * are ignored.

* Category:Mailing_lists|Our Mailing Lists|message
* News|News TEST|bogusIcon
* Executive_Committee|Board of Directors|userGroup
* Meetings|Meeting Information|calendar

MediaWiki:Uvlists-mobile-menu

2026-10-20T18:05:31Z

UVListsBot: Mobile main menu links (read by the minerva-main-menu patch)

Links in the mobile view's main menu, after Home. One per line:
* page or web address|label|icon
Icons: article, articles, bell, book, bookmark, browser, calendar, camera, chart, clock, download, edit, feedback, flag, folderPlaceholder, globe, heart, help, history, image, imageGallery, info, key, lightbulb, link, linkExternal, listBullet, lock, map, mapPin, message, newspaper, notice, ongoingConversation, printer, search, speechBubble, speechBubbles, star, table, userAdd, userAvatar, userContributions, userGroup. Other names show as "link". Lines not starting with * are ignored.

* Category:Mailing_lists|Our Mailing Lists|message
* News|News and Updates|newspaper
* Executive_Committee|Board of Directors|userGroup
* Meetings|Meeting Information|calendar

Vital Communities List Migration/Renaming Lists

2026-10-19T13:00:46Z

UVListsBot: Explain why migrated lists are renamed to town-discuss

As part of the [[Vital Communities List Migration|migration from Vital Communities]], each town list is getting a new name ending in ''-Discuss''. For example, the Barnard list (barnard@lists.vitalcommunities.org) becomes Barnard-Discuss (barnard-discuss@lists.uvlists.org).

This is the same community list. The subscribers, the purpose, the guidelines, and the volunteers who run it stay the same. Only the name, the address, and the service provider change.

== What is changing ==

{| class="wikitable"
!
! Before
! After
|-
| List name
| Barnard
| Barnard-Discuss
|-
| Posting address
| barnard@lists.vitalcommunities.org
| barnard-discuss@lists.uvlists.org
|-
| Subject tag
| [Barnard]
| [Barnard-Discuss]
|-
| Join address
| (Vital Communities web page)
| barnard-discuss-join@lists.uvlists.org
|-
| Leave address
| barnard-unsubscribe@lists.vitalcommunities.org
| barnard-discuss-leave@lists.uvlists.org
|}

Every migrating town list follows the same pattern. Each list's page under [[:Category:Mailing lists|Mailing lists]] shows its new addresses.

== Why the names end in -Discuss ==

=== A town can have more than one list ===
A list named only for its town leaves no room for anything else. With the old naming, Barnard's one list was simply "Barnard", so there was no good name for a second Barnard list.

Naming each list for its purpose changes that. A town can have several lists, each clearly labeled, side by side. For example, a town might have:

{| class="wikitable"
! List
! Purpose
|-
| barnard-discuss
| Open discussion among neighbors (the migrated community list)
|-
| barnard-announce
| Announcements only, with low traffic
|-
| barnard-forsale
| Items for sale, wanted, or free
|}

These examples show how the naming works. They are not lists that exist today. Whether a town gets more lists is up to its community, and adding one should not require renaming the discussion list.

Clear labels also help subscribers. You can join only the lists you want, and you can tell from the name and subject tag which list a message came from.

=== The name describes the list ===
These lists are discussion forums for neighbors. They are run by volunteers and are not official channels of any town government. A list named only for its town can be mistaken for the town's own announcements. Adding ''-Discuss'' makes clear what the list is for.

=== One pattern for every town ===
Every migrated list uses the same form: ''town''-discuss@lists.uvlists.org, with ''town''-discuss-join and ''town''-discuss-leave for joining and leaving. Once you know one list's addresses, you know them all.

== What subscribers need to do ==

* '''Nothing to rejoin.''' Unless you unsubscribe from the Vital Communities list before its cutover date, your subscription and delivery preference move automatically. See the [[Vital Communities List Migration#Migration schedule|migration schedule]] for each list's dates.
* '''Update your contacts.''' After the cutover date, send messages to the new address. Each list page offers a contact card you can download.
* '''Check your email filters.''' If you have a filter or rule that matches the old subject tag (for example, [Barnard]) or the old address, update it to match the new tag or address. Otherwise new messages may land somewhere unexpected.

For a period after cutover, messages sent to the old address receive an automatic reply that points to the new list.

== Questions ==

For help with the move or a question about a particular list, see [[Contact|Contact UVLists]].

[[Category:List Migration]]

Vital Communities List Migration

2026-10-19T06:43:30Z

UVListsBot: Add subscriber and administrator guidance and clarify migration schedule

== Overview ==

As described in [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists]], UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.

For help with a migration or a question about a particular list, see [[Contact|Contact UVLists]].

== What subscribers need to do ==

Subscribers do not need to take action to move to the new UVLists list. Unless they unsubscribe from the Vital Communities list before its '''Cutover Date''', their subscription and delivery preference will be transferred. After the move, use the new list address shown on the list’s UVLists page.

== What list administrators need to do ==

List administrators should review the list’s public page for accuracy, including its purpose, guidelines, owner-contact address, and joining instructions. The [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] explains what to check and how to submit corrections.

== Migration schedule ==

The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.

The status column uses these terms:

{| class="wikitable"
! Status
! Meaning
|-
| Not migrated
| Migration has not started.
|-
| Signup open
| Existing Vital Communities subscribers have been notified. The new list is available for subscriptions but not yet for posting.
|-
| Migrated
| The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address.
|-
| Complete
| The prior Vital Communities list has been fully retired.
|}

{| class="wikitable sortable"
|+ Migration Schedule
|-
! VC List !! UVL List !! Announcement Date !! Cutover Date !! Current Status
|-
| barnard@lists.vitalcommunities.org || [[Lists:Barnard]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| bradford@lists.vitalcommunities.org || [[Lists:Bradford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| bridgewater@lists.vitalcommunities.org || [[Lists:Bridgewater]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| brownsville@lists.vitalcommunities.org || [[Lists:Brownsville]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| chelsea@lists.vitalcommunities.org || [[Lists:Chelsea]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| claremont@lists.vitalcommunities.org || [[Lists:Claremont]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| enfield@lists.vitalcommunities.org || [[Lists:Enfield]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| fairlee@lists.vitalcommunities.org || [[Lists:Fairlee]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| grafton@lists.vitalcommunities.org || [[Lists:Grafton]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| hartford@lists.vitalcommunities.org || [[Lists:Hartford]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| haverhill@lists.vitalcommunities.org || [[Lists:Haverhill]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lebanon@lists.vitalcommunities.org || [[Lists:Lebanon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lyme@lists.vitalcommunities.org || [[Lists:Lyme]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| mascoma@lists.vitalcommunities.org || [[Lists:Mascoma]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| newbury@lists.vitalcommunities.org || [[Lists:Newbury]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| norwich@lists.vitalcommunities.org || [[Lists:Norwich]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| orford@lists.vitalcommunities.org || [[Lists:Orford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| piermont@lists.vitalcommunities.org || [[Lists:Piermont]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| plainfield@lists.vitalcommunities.org || [[Lists:Plainfield]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| pomfret@lists.vitalcommunities.org || [[Lists:Pomfret]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| reading@lists.vitalcommunities.org || [[Lists:Reading]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| royalton@lists.vitalcommunities.org || [[Lists:Royalton]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| ryegate@lists.vitalcommunities.org || [[Lists:Ryegate]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| sharon@lists.vitalcommunities.org || [[Lists:Sharon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| strafford@lists.vitalcommunities.org || [[Lists:Strafford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| thetford@lists.vitalcommunities.org || [[Lists:Thetford]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| tunbridge@lists.vitalcommunities.org || [[Lists:Tunbridge]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Not Migrated
|}

Each linked UVLists list page includes its new address, joining instructions, and local guidelines.

== Not yet scheduled ==

{| class="wikitable"
! Vital Communities list
! Planning status
|-
| groton_area@lists.vitalcommunities.org
| New list and schedule to be determined.
|-
| west_fairlee@lists.vitalcommunities.org
| New list and schedule to be determined.
|-
| west_lebanon@lists.vitalcommunities.org
| New list and schedule to be determined.
|-
| west_newbury@lists.vitalcommunities.org
| New list and schedule to be determined.
|-
| west_norwich@lists.vitalcommunities.org
| New list and schedule to be determined.
|-
| woodstock@lists.vitalcommunities.org
| List page in preparation; schedule to be determined.
|}

== Migration process ==

Each list follows this general process. The communication templates should be reviewed and updated with the list’s specific dates, addresses, and contacts before they are sent.

# '''Announce the move.''' On the '''Announcement Date''', send the [[Vital Communities List Migration/01-move-announcement|move announcement]] to the existing list. It explains the new list, the opt-out process, and the planned cutover date.
# '''Review list information and allow opt-out.''' List administrators receive the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the '''Cutover Date'''.
# '''Cut over the list.''' On the '''Cutover Date''', send the [[Vital Communities List Migration/03-closure-announcement|closure announcement]] to remaining subscribers. Place the previous list in '''moderated mode''' so new posts are not distributed, and enable the [[Vital Communities List Migration/05-old-list-autoresponse|old-list autoresponse]] to direct senders to the new list for the period set for that migration.
# '''Transfer subscribers and welcome them.''' Import subscribers who did not opt out, including their delivery preferences. Then send the [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] with information about the list, its moderators, and where to get help.

[[Category:List Migration]]

Vital Communities List Migration

2026-10-19T06:39:58Z

UVListsBot: Rewrite migration process as a clear step-by-step workflow

== Overview ==

As described in [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists]], UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.

For help with a migration or a question about a particular list, see [[Contact|Contact UVLists]].

== Migration schedule ==

The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.

The status column uses these terms:
* '''Not migrated''' - Migration has not started.
* '''Signup open''' - Existing Vital Communities subscribers have been notified. The new list is available for subscriptions but not yet for posting.
* '''Migrated''' - The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address.
* '''Complete''' - The prior Vital Communities list has been fully retired.

{| class="wikitable sortable"
|+ Migration Schedule
|-
! VC List !! UVL List !! Announcement Date !! Cutover Date !! Current Status
|-
| barnard@lists.vitalcommunities.org || [[Lists:Barnard]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| bradford@lists.vitalcommunities.org || [[Lists:Bradford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| bridgewater@lists.vitalcommunities.org || [[Lists:Bridgewater]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| brownsville@lists.vitalcommunities.org || [[Lists:Brownsville]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| chelsea@lists.vitalcommunities.org || [[Lists:Chelsea]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| claremont@lists.vitalcommunities.org || [[Lists:Claremont]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| enfield@lists.vitalcommunities.org || [[Lists:Enfield]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| fairlee@lists.vitalcommunities.org || [[Lists:Fairlee]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| grafton@lists.vitalcommunities.org || [[Lists:Grafton]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| groton_area@lists.vitalcommunities.org || || || || Not Migrated
|-
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| hartford@lists.vitalcommunities.org || [[Lists:Hartford]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| haverhill@lists.vitalcommunities.org || [[Lists:Haverhill]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lebanon@lists.vitalcommunities.org || [[Lists:Lebanon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lyme@lists.vitalcommunities.org || [[Lists:Lyme]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| mascoma@lists.vitalcommunities.org || [[Lists:Mascoma]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| newbury@lists.vitalcommunities.org || [[Lists:Newbury]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| norwich@lists.vitalcommunities.org || [[Lists:Norwich]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| orford@lists.vitalcommunities.org || [[Lists:Orford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| piermont@lists.vitalcommunities.org || [[Lists:Piermont]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| plainfield@lists.vitalcommunities.org || [[Lists:Plainfield]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| pomfret@lists.vitalcommunities.org || [[Lists:Pomfret]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| reading@lists.vitalcommunities.org || [[Lists:Reading]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| royalton@lists.vitalcommunities.org || [[Lists:Royalton]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| ryegate@lists.vitalcommunities.org || [[Lists:Ryegate]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| sharon@lists.vitalcommunities.org || [[Lists:Sharon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| strafford@lists.vitalcommunities.org || [[Lists:Strafford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| thetford@lists.vitalcommunities.org || [[Lists:Thetford]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| tunbridge@lists.vitalcommunities.org || [[Lists:Tunbridge]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| west_fairlee@lists.vitalcommunities.org || || || || Not Migrated
|-
| west_lebanon@lists.vitalcommunities.org || || || || Not Migrated
|-
| west_newbury@lists.vitalcommunities.org || || || || Not Migrated
|-
| west_norwich@lists.vitalcommunities.org || || || || Not Migrated
|-
| windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| woodstock@lists.vitalcommunities.org || Woodstock (list page in preparation) || || || Not Migrated
|}
== Migration process ==

Each list follows this general process. The communication templates should be reviewed and updated with the list’s specific dates, addresses, and contacts before they are sent.

# '''Announce the move.''' On the '''Announcement Date''', send the [[Vital Communities List Migration/01-move-announcement|move announcement]] to the existing list. It explains the new list, the opt-out process, and the planned cutover date.
# '''Review list information and allow opt-out.''' List administrators receive the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the '''Cutover Date'''.
# '''Cut over the list.''' On the '''Cutover Date''', send the [[Vital Communities List Migration/03-closure-announcement|closure announcement]] to remaining subscribers. Place the previous list in '''moderated mode''' so new posts are not distributed, and enable the [[Vital Communities List Migration/05-old-list-autoresponse|old-list autoresponse]] to direct senders to the new list.
# '''Transfer subscribers and welcome them.''' Import subscribers who did not opt out, including their delivery preferences. Then send the [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] with information about the list, its moderators, and where to get help.

[[Category:List Migration]]

Category:List Migration

2026-10-19T06:35:21Z

UVListsBot: Replace em dashes with hyphens

This category collects planning materials, communications, and reference documents for moving community email lists to UVLists. These pages record the migration process and provide reusable messages for list administrators and subscribers.

== Start here ==

[[Vital Communities List Migration|Vital Communities List Migration]] describes the overall transition and its supporting materials.

== Communication templates ==

* [[Vital Communities List Migration/01-move-announcement|Move announcement]] - advance notice for subscribers.
* [[Vital Communities List Migration/02-list-administrator-review|List administrator review]] - request for administrators to review a list’s public information.
* [[Vital Communities List Migration/03-closure-announcement|Closure announcement]] - notice sent when the previous list closes.
* [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] - welcome text for subscribers after migration.
* [[Vital Communities List Migration/05-old-list-autoresponse|Old-list autoresponse]] - automatic reply directing senders after a list has moved.

These templates may contain dates, names, addresses, or other details specific to a particular migration. Review and update them before using them for another list.

== Need help? ==

For questions about a migration or help using these materials, see [[Contact|Contact UVLists]].

Template:MailingListPartialGeneralRules

2026-10-19T06:35:21Z

UVListsBot: Replace em dashes with hyphens

This discussion list operates on the assumption that list postings will be civil and respectful to other list members. No abusive or threatening postings will be allowed. Anyone engaging in abusive language or threats directed toward another list member may have posting privileges revoked.

Because this list is set up for the convenience of the community, occasional announcements from businesses in town are okay-for example, a new business in town, information about a business service offered in conjunction with a public event taking place in town, or a one-time listing about babysitting. No business, small or large, should use the discussion list for frequent repetitive promotion. Posting commercial announcements more often than monthly may annoy your neighbors and bring a warning from the list administrators.

To keep this discussion list useful and dynamic, do not forward verbatim content that has already appeared elsewhere. If an article published on the web is relevant to a discussion on this list, summarize the relevant point and include a link to the source. It is inappropriate to post private correspondence to or from a list member without the express permission of everyone involved.

This discussion list centers on issues and events directly affecting the community. It is not a venue for general announcements about Upper Valley events from people not connected with the town. Occasional posts from neighboring towns are okay, but if an event or item may be relevant to multiple towns, please use an appropriate Upper Valley-wide forum. Subscribers who regularly cross-post to multiple town lists may be warned and eventually suspended.

UVLists reserves the right to warn, suspend, or permanently exclude any subscriber for abuse or infringement of these rules and guidelines. To report abuse or bring a specific issue to UVLists' attention, write to abuse@uvlists.org.

Vital Communities List Migration

2026-10-19T06:35:21Z

UVListsBot: Replace em dashes with hyphens

== Overview ==

As described in [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists]], UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.

For help with a migration or a question about a particular list, see [[Contact|Contact UVLists]].

== Migration schedule ==

The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.

The status column uses these terms:
* '''Not migrated''' - Migration has not started.
* '''Signup open''' - Existing Vital Communities subscribers have been notified. The new list is available for subscriptions but not yet for posting.
* '''Migrated''' - The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address.
* '''Complete''' - The prior Vital Communities list has been fully retired.

{| class="wikitable sortable"
|+ Migration Schedule
|-
! VC List !! UVL List !! Announcement Date !! Cutover Date !! Current Status
|-
| barnard@lists.vitalcommunities.org || [[Lists:Barnard]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| bradford@lists.vitalcommunities.org || [[Lists:Bradford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| bridgewater@lists.vitalcommunities.org || [[Lists:Bridgewater]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| brownsville@lists.vitalcommunities.org || [[Lists:Brownsville]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| chelsea@lists.vitalcommunities.org || [[Lists:Chelsea]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| claremont@lists.vitalcommunities.org || [[Lists:Claremont]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| enfield@lists.vitalcommunities.org || [[Lists:Enfield]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| fairlee@lists.vitalcommunities.org || [[Lists:Fairlee]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| grafton@lists.vitalcommunities.org || [[Lists:Grafton]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| groton_area@lists.vitalcommunities.org || || || || Not Migrated
|-
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| hartford@lists.vitalcommunities.org || [[Lists:Hartford]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| haverhill@lists.vitalcommunities.org || [[Lists:Haverhill]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lebanon@lists.vitalcommunities.org || [[Lists:Lebanon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lyme@lists.vitalcommunities.org || [[Lists:Lyme]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| mascoma@lists.vitalcommunities.org || [[Lists:Mascoma]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| newbury@lists.vitalcommunities.org || [[Lists:Newbury]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| norwich@lists.vitalcommunities.org || [[Lists:Norwich]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| orford@lists.vitalcommunities.org || [[Lists:Orford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| piermont@lists.vitalcommunities.org || [[Lists:Piermont]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| plainfield@lists.vitalcommunities.org || [[Lists:Plainfield]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| pomfret@lists.vitalcommunities.org || [[Lists:Pomfret]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| reading@lists.vitalcommunities.org || [[Lists:Reading]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| royalton@lists.vitalcommunities.org || [[Lists:Royalton]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| ryegate@lists.vitalcommunities.org || [[Lists:Ryegate]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| sharon@lists.vitalcommunities.org || [[Lists:Sharon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| strafford@lists.vitalcommunities.org || [[Lists:Strafford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| thetford@lists.vitalcommunities.org || [[Lists:Thetford]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| tunbridge@lists.vitalcommunities.org || [[Lists:Tunbridge]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| west_fairlee@lists.vitalcommunities.org || || || || Not Migrated
|-
| west_lebanon@lists.vitalcommunities.org || || || || Not Migrated
|-
| west_newbury@lists.vitalcommunities.org || || || || Not Migrated
|-
| west_norwich@lists.vitalcommunities.org || || || || Not Migrated
|-
| windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| woodstock@lists.vitalcommunities.org || Woodstock (list page in preparation) || || || Not Migrated
|}

== Migration process ==

Each list follows this general process:
# On the '''Announcement Date''' a notice that the list is moving is sent to the existing list, containing details for how to opt-out and the closing date of the existing list (typically 7 calendar days) ([[Vital Communities List Migration/01-move-announcement|Sample Announcement]])
#* List Administrators will receive a separate announcement with additional steps to take before the closing date ([[Vital Communities List Migration/02-list-administrator-review|Sample Admin Announcement]])
#* Existing list subscribers opt-out by unsubscribing from the existing list before the '''Cutover Date'''
# On the '''Cutover Date''' another notice will be sent to the remaining list members, stating that the list will be closing at the end of the day. ([[Vital Communities List Migration/03-closure-announcement|Sample Closing Announcement]])
#* The existing list will be moved to '''moderated mode''', so no posts will be passed to subscribers. New posts to the existing list will receive an auto-response stating the list has moved and where to find the new list. ([[Vital Communities List Migration/05-old-list-autoresponse|Sample Autoresponse]])
# Subscribers who did not opt out are imported with their delivery preferences. A welcome message with information about the list, its moderators, and how to get help is then sent. ([[Vital Communities List Migration/04-uvlists-welcome-message|Sample Welcome Message]])

[[Category:List Migration]]

Meetings/09302026/minutes

2026-10-19T06:35:20Z

UVListsBot: Replace em dashes with hyphens

== UVLists.org Meeting ==
Sept. 30, 2026 2pm via Zoom

=== Present ===
'''Directors:''' Kevin Perron, Edward (Ted) Mortimer, Miranda Clemson
Also present: Stan Williams, Benjamin Brickner, Kurth Bemis, Kerry Claffey
Kevin Perron chaired the meeting, Miranda Clemson recorded minutes
A quorum was present. No director objected to holding the meeting, and the meeting came to order.

=== Officers ===
'''Officers were elected''': Kevin (President), Miranda (Secretary), Ted and Kerry (Co-Treasurers); Vice President position left vacant pending a volunteer. ([[Executive Committee|Board Of Directors]])

=== Organizational Resolutions and Bylaws ===
The Organizational Resolutions and Bylaws were discussed:
* The UVLists.org annual meeting will be held on or before January 31, 2027.
* Fiscal year: July–June.
* Banking institution: Mascoma Bank selected; authorized signers are Kevin, Ted, and Kerry; dual-signature threshold set at $2,500.
* Budget approved for FY2026–2027 as initial draft, subject to revision as actuals emerge.

Each director acknowledged receipt of Article 8 of the Bylaws.

Miranda moved to approve and ratify the Bylaws. The vote was unanimous and the Bylaws were approved.

Miranda moved to approve and ratify the Organizational Resolutions. The vote was unanimous and the Organizational Resolutions were approved.

Each director was asked about any relationship with Vital Communities. No director disclosed a financial interest in the Transition Agreement. Each director acknowledged Section 12 (non-disparagement) of the Transition Agreement.

Ted moved, Miranda seconded to approve the Transition Agreement with Vital Communities. The vote was unanimous. The Transition Agreement was approved. Kevin is authorized to sign and seek up to a 30-day extension if needed.

The resolutions as adopted, and the approved budget, are attached to these minutes.

=== Action Items ===
* Kerry: Apply for EIN (nearly instantaneous; social security number required - do not email it).
* Ben: Send signature pages to Miranda and Kevin for organizational resolutions and transition agreement.
* Kevin: Execute and deliver transition agreement to Vital Communities; serve as primary external contact for all media and public inquiries.
* Ted: Finalize insurance quotes; binding quote expected within 14 days.
* Miranda: Prepare signed meeting minutes for Mascoma Bank account opening.
* Kurth: Build transition webpage with whitelisting instructions (target: next week).
* Executive committee: Review and finalize press release by Monday; release to coincide with subscriber notification, not agreement signing.
* All: Press release and subscriber email targeted for next week (Monday–Tuesday).

The meeting was adjourned at 3:06 PM.

Vital Communities List Migration

2026-10-19T06:34:32Z

UVListsBot: Clarify migration overview, correct links and schedule typos

== Overview ==

As described in [[News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists]], UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.

For help with a migration or a question about a particular list, see [[Contact|Contact UVLists]].

== Migration schedule ==

The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.

The status column uses these terms:
* '''Not migrated''' — Migration has not started.
* '''Signup open''' — Existing Vital Communities subscribers have been notified. The new list is available for subscriptions but not yet for posting.
* '''Migrated''' — The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address.
* '''Complete''' — The prior Vital Communities list has been fully retired.

{| class="wikitable sortable"
|+ Migration Schedule
|-
! VC List !! UVL List !! Announcement Date !! Cutover Date !! Current Status
|-
| barnard@lists.vitalcommunities.org || [[Lists:Barnard]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| bradford@lists.vitalcommunities.org || [[Lists:Bradford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| bridgewater@lists.vitalcommunities.org || [[Lists:Bridgewater]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| brownsville@lists.vitalcommunities.org || [[Lists:Brownsville]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| chelsea@lists.vitalcommunities.org || [[Lists:Chelsea]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| claremont@lists.vitalcommunities.org || [[Lists:Claremont]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| enfield@lists.vitalcommunities.org || [[Lists:Enfield]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| fairlee@lists.vitalcommunities.org || [[Lists:Fairlee]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| grafton@lists.vitalcommunities.org || [[Lists:Grafton]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| groton_area@lists.vitalcommunities.org || || || || Not Migrated
|-
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| hartford@lists.vitalcommunities.org || [[Lists:Hartford]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| haverhill@lists.vitalcommunities.org || [[Lists:Haverhill]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lebanon@lists.vitalcommunities.org || [[Lists:Lebanon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| lyme@lists.vitalcommunities.org || [[Lists:Lyme]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| mascoma@lists.vitalcommunities.org || [[Lists:Mascoma]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| newbury@lists.vitalcommunities.org || [[Lists:Newbury]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| norwich@lists.vitalcommunities.org || [[Lists:Norwich]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| orford@lists.vitalcommunities.org || [[Lists:Orford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| piermont@lists.vitalcommunities.org || [[Lists:Piermont]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| plainfield@lists.vitalcommunities.org || [[Lists:Plainfield]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| pomfret@lists.vitalcommunities.org || [[Lists:Pomfret]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| reading@lists.vitalcommunities.org || [[Lists:Reading]] || October 23, 2026 || October 30, 2026 || Not Migrated
|-
| royalton@lists.vitalcommunities.org || [[Lists:Royalton]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| ryegate@lists.vitalcommunities.org || [[Lists:Ryegate]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| sharon@lists.vitalcommunities.org || [[Lists:Sharon]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| strafford@lists.vitalcommunities.org || [[Lists:Strafford]] || October 20, 2026 || October 27, 2026 || Not Migrated
|-
| thetford@lists.vitalcommunities.org || [[Lists:Thetford]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| tunbridge@lists.vitalcommunities.org || [[Lists:Tunbridge]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not Migrated
|-
| west_fairlee@lists.vitalcommunities.org || || || || Not Migrated
|-
| west_lebanon@lists.vitalcommunities.org || || || || Not Migrated
|-
| west_newbury@lists.vitalcommunities.org || || || || Not Migrated
|-
| west_norwich@lists.vitalcommunities.org || || || || Not Migrated
|-
| windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Not Migrated
|-
| woodstock@lists.vitalcommunities.org || Woodstock (list page in preparation) || || || Not Migrated
|}

== Migration process ==

Each list follows this general process:
# On the '''Announcement Date''' a notice that the list is moving is sent to the existing list, containing details for how to opt-out and the closing date of the existing list (typically 7 calendar days) ([[Vital Communities List Migration/01-move-announcement|Sample Announcement]])
#* List Administrators will receive a separate announcement with additional steps to take before the closing date ([[Vital Communities List Migration/02-list-administrator-review|Sample Admin Announcement]])
#* Existing list subscribers opt-out by unsubscribing from the existing list before the '''Cutover Date'''
# On the '''Cutover Date''' another notice will be sent to the remaining list members, stating that the list will be closing at the end of the day. ([[Vital Communities List Migration/03-closure-announcement|Sample Closing Announcement]])
#* The existing list will be moved to '''moderated mode''', so no posts will be passed to subscribers. New posts to the existing list will receive an auto-response stating the list has moved and where to find the new list. ([[Vital Communities List Migration/05-old-list-autoresponse|Sample Autoresponse]])
# Subscribers who did not opt out are imported with their delivery preferences. A welcome message with information about the list, its moderators, and how to get help is then sent. ([[Vital Communities List Migration/04-uvlists-welcome-message|Sample Welcome Message]])

[[Category:List Migration]]

Category:List Migration

2026-10-19T06:32:00Z

UVListsBot: Add migration resource index and template guidance

This category collects planning materials, communications, and reference documents for moving community email lists to UVLists. These pages record the migration process and provide reusable messages for list administrators and subscribers.

== Start here ==

[[Vital Communities List Migration|Vital Communities List Migration]] describes the overall transition and its supporting materials.

== Communication templates ==

* [[Vital Communities List Migration/01-move-announcement|Move announcement]] — advance notice for subscribers.
* [[Vital Communities List Migration/02-list-administrator-review|List administrator review]] — request for administrators to review a list’s public information.
* [[Vital Communities List Migration/03-closure-announcement|Closure announcement]] — notice sent when the previous list closes.
* [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] — welcome text for subscribers after migration.
* [[Vital Communities List Migration/05-old-list-autoresponse|Old-list autoresponse]] — automatic reply directing senders after a list has moved.

These templates may contain dates, names, addresses, or other details specific to a particular migration. Review and update them before using them for another list.

== Need help? ==

For questions about a migration or help using these materials, see [[Contact|Contact UVLists]].

Vital Communities List Migration/05-old-list-autoresponse

2026-10-19T06:30:11Z

UVListsBot: Keep migration material out of the mailing list directory

== Sample Closed List Autoresponse ==
<pre>
<nowiki>
Subject: Automatic reply: Barnard has moved to UVLists

Barnard is closed at barnard@lists.vitalcommunities.org. The community list moved to UVLists on 10/27/2026 and is now named Barnard-Discuss.

Your message or subscription request was not forwarded or posted.

- To post, email barnard-discuss@lists.uvlists.org.
- To subscribe, manage a subscription, or unsubscribe, visit https://lists.uvlists.org/postorius/lists/barnard-discuss.lists.uvlists.org/.
- To read the list information and posting guidelines, visit https://uvlists.org/wiki/Lists:Barnard.

This automatic reply will end after 11/03/2026. Please update any saved address before then.

For transition help, contact helpdesk@uvlists.org. For questions about list topics or moderation, contact barnard-discuss-owner@lists.uvlists.org.

</nowiki>
</pre>
[[Category:List Migration]]

Vital Communities List Migration/04-uvlists-welcome-message

2026-10-19T06:30:11Z

UVListsBot: Keep migration material out of the mailing list directory

== Sample Closed List Autoresponse ==
<pre>
<nowiki>
Subject: Welcome to Barnard-Discuss at UVLists

Hello,

As of 10/27/2026, Barnard-Discuss is open at UVLists. You are receiving this message because you remained subscribed to Barnard through the 10/27/2026 unsubscribe deadline, so your subscription was transferred from Vital Communities. You do not need to subscribe again.

As part of the move, the list is being renamed from Barnard to Barnard-Discuss. This is the same Barnard community list; its name, address, and service provider are changing.

Save these addresses

- Post to the list: barnard-discuss@lists.uvlists.org
- Contact the list's owners and moderators: barnard-discuss-owner@lists.uvlists.org
- Read the list information and posting guidelines: https://uvlists.org/wiki/Lists:Barnard

Please add barnard-discuss@lists.uvlists.org to your contacts and remove barnard@lists.vitalcommunities.org. Messages sent to the old address are not forwarded to the new list.

Manage your subscription

Visit https://lists.uvlists.org/postorius/lists/barnard-discuss.lists.uvlists.org/ to review your subscription or change between individual messages and digest delivery. Use the same email address that receives list messages when signing in or creating your site account.

To unsubscribe without signing in, email barnard-discuss-leave@lists.uvlists.org and follow the confirmation instructions. You can unsubscribe at any time.

For help with the transition or your account, contact helpdesk@uvlists.org. For questions about list topics, posting rules, or moderation, contact barnard-discuss-owner@lists.uvlists.org.

Thank you for being part of Barnard's community list.

The UVLists team
</nowiki>
</pre>

[[Category:List Migration]]

Vital Communities List Migration/03-closure-announcement

2026-10-19T06:30:10Z

UVListsBot: Keep migration material out of the mailing list directory

== Sample List Closure Announcement ==

<pre><nowiki>
Subject: Barnard has moved to UVLists

Hello,

This is the final message from barnard@lists.vitalcommunities.org. As of 10/27/2026, the old list is closed and the community list is operating at UVLists.

As part of the move, the list is being renamed from Barnard to Barnard-Discuss. This is the same Barnard community list; its name, address, and service provider are changing.

If you were still subscribed to Barnard when it closed, your subscription and delivery preference have been transferred. You do not need to subscribe again. A welcome message from the new list will follow.

From now on, send posts to:

barnard-discuss@lists.uvlists.org

Please replace barnard@lists.vitalcommunities.org in your contacts and saved drafts. Messages sent to the old address are not forwarded or posted. An automatic reply will direct senders to the new list through 11/03/2026; after that date, the old address may stop responding. Attached to this message is a Contact Card (vcf) with the new list information. This file can also be downloaded directly from https://go.uvlists.org/barnard-discuss.vcf and can also be found in the UVLists Wiki at https://uvlists.org/wiki/Lists:Barnard#List_information

To manage your subscription, change between individual messages and digest delivery, or unsubscribe, visit:

https://lists.uvlists.org/postorius/lists/barnard-discuss.lists.uvlists.org/

If you did not expect to be transferred, you can unsubscribe at that page or by emailing barnard-discuss-leave@lists.uvlists.org.

For transition help, contact helpdesk@uvlists.org. For questions about list topics or moderation, contact barnard-discuss-owner@lists.uvlists.org.

Thank you,

The UVLists team

</nowiki></pre>
[[Category:List Migration]]