[NRVR-Members] Switching our "dsitro list" over to a real email-list (listserve)

[Thomas Weeks]

No no man. this needed to be done anyway. 

Some others had complained about constant bounce issues.. and I needed to make 
this "in-case-I-get-hit-by-a-bus-proof" anyway :)  Plus.. now all of our deep, 
meaningful discussions are archived for posterity:
	http://nrvr.org/pipermail/nrvr-members/

It's all good. :)

Tweeks



On Saturday 01 November 2014 03:31:21 Chris Maier wrote:
> Sorry TWeeks, my intention wasn't to make you work this weekend on the
> mail list.
> 
> Chris
> 
> On Sat, Nov 1, 2014 at 12:18 AM, Thomas Weeks <tweeksjunk2 at theweeks.org> 
wrote:
> > Hey all..
> >
> > TL;DR:
> > I'm changing the nrvr-members at nrvr.org from being a server-side, CC-alias
> > distro list, to a legit RFC 2919  complain email list (aka "listserve"
> > around VT).  **If you don't know how any of this is significant, don't
> > worry about it. Nothing will change ;) No email continuity or message
> > deliverability will be impacted.
> >
> > Background:
> > I originally set up the NRVR email list (nrvr at nrvr.org) and the
> > launches/announcement (only) email list (nrvr-launches at nrvr.org) as full
> > blown email lists that people can self-sign-up on, and which takes care
> > of itself. Here are each of those lists and their related archives:
> >         http://nrvr.org/mailman/listinfo/nrvr
> >         http://nrvr.org/mailman/listinfo/nrvr-launches
> >
> > They're nice in that they take care of themselves, auto-handle spam, non-
> > member posting, and address-bounce management... however they don't allow
> > large file attachments (pictures) and big giant CC lists or tons of
> > embedded HTML content.
> >
> > When I created the "members" list, I did so not as a mailman email list,
> > but as a distribution list run as a type of "internal CC" alias on my
> > mail server. Literally, a big CC alias list that sends the message out to
> > all your inboxes (no smarts, auto-sigh-up, bounce management, etc). It
> > was easy for me.. and no one complained.
> >
> > Problem:
> > Since the nrvr-members distro list is dumb.. it can't handle bounces
> > properly and some of you may have been getting them from time to time..
> > and I'm tired of manually keeping up with it. Plus, if I want to be able
> > to delegate owner ship of these things out to Bob or other folks (like
> > webmasters, etc), then I should not be the single point of failure w/some
> > esoteric, server side, root managed CC distro list.
> >
> > Solution:
> > I'm changing nrvr-members to a full blown mailman/RFC compliant email
> > list, but with moderated sign-ups so that only valid members who have
> > sent in their signed yearly membership form (and dues) will be added..
> > and both Bob and I (or anyone else who wants to help) can.
> >
> > Another advantage this will give you geek-types is the ability to filter
> > messages on the RFC 2919 defined email header field "List-ID: " field
> > that will look something like this:
> >         List-Id: <nrvr-members.nrvr.org>
> >
> > This should be done this weekend without any interruptions in message
> > deliveries. And the subject lines should all start beginning with [nrvr-
> > members] or the like.  If interested.. that's how you'll know the change
> > is complete.
> >
> > If anyone has any questions or concerns, please let me know.
> >
> > Tweeks
> > Head IT Geek or NRVR.ORG
>