[Users] Alliance Call reading material on next crowd funder: Zimbra Mailing Lists

[Noah Price]

That's great! And some of these enhancements for mailing lists would be nice additions to the basic DL features too :-) 

Similar to user management of distribution lists, could this also allow a user to manage mailing lists? 

A few key needs of a mailing list: 

* Subscription verification (covered by Mark Stone) 
* I prefer email commands for subscribe/unsubscribe, but having a form submission in addition to email for subscribe and unsubscribe is ideal 
* Posting restrictions -- able to restrict posting to subscribers only (avoids most of the spam!), or ideally able to restrict to a defined set of users (nice for announcement lists) 
* Bounce processing (evaluate bounces and automatically unsubscribe) -- yes this is complicated and is not foolproof, maybe look at what Mailman does, though I'm guessing this isn't a "1.0" feature 
* Subject tag (like our "[Users]" above) to help people identify list email 
* Customize Reply-To so a list may reply to the poster or to the list (discussion lists will want replies to list, but many lists prefer reply to sender) 
* Send "From:" list, rather than members (envelope sender described by David Sommerseth, but From must also be updated for DMARC, I also brought this up for DL in general on our last call) 

The Zeta Mailman lists are not set to rewrite the From address, so I expect you are getting bounces if anyone is sending from AOL or Yahoo. 
https://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-what-should-senders 

Mailman has an option (since shortly after Yahoo made this policy change) to use the list address. I run a list like this, and the From looks like: 
From: Member Name via List Name <listaddress at example.com> 

* One other really nice feature that I'm not sure will make the cut for "lightweight list" would be to remove attachments (including embedded images) and replace them with links to a a public Briefcase share. This avoids problems with huge attachments going out to a whole list, without just blocking them entirely. 

Some other features could be left out of a lightweight mailing list like this: 

* VERP -- send a unique message per recipient, which aids in bounce verification and allows you to figure out who sent that darn AOL/etc Feedback Loop complaint because they didn't want to figure out how to unsubscribe! :-) 
* Daily digest 
* Message archive (but see below) 
* Size restriction (avoids huge attachments going out to the list) 
* Attachment stripping (alternative solution to the above) 
* Moderation (require approval by an admin, per member or per list) 

Before you give up on a message archive... I tried to use a Zimbra mailbox as a message archive. The stumbling block was making webmail read-only. I experimented using a shared folder, but people could still create new messages so I gave that up (yes I could block sending and receiving, but they could still create messages and leave other junk in the archive account). But if there is a way to make a webmail login read-only that would make an easy message archive! 

Thanks, 

Noah 
prxy, Inc. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zetalliance.org/pipermail/users_lists.zetalliance.org/attachments/20170808/6307b435/attachment.html>