History: NewslettersDev

newsletter enhancements for 1.8 - per newsletter determine whether users can subscribe, whether the address must be validated, and whether to include an unsubscribe msg when a newsletter is sent. Removed frequency as unused.
(See CVS Doc section below for details)

We have a basic newsletter feature. We are considering partnering with phplist to replace our current newsletter feature.

phplist was approched after careful analysis of all the PHP open source newsletter apps. phplist is a mature & stable with 40+ releases over than last 3.5 years. phplist has a great number of features

We are looking for people on the Tiki team to work with Michiel Dethmers to see how we can proceed and to start work as soon as possible. If you are interested, please add your name to the team.

Michiel Dethmers
Adam C. Engst (feature requirements and analysis)

Bugs

• {SF(aid=>802223)}{SF} This may be related to the evolution of newsletter subscription (which I don't know!) after the fix of 750708 - chealer.

RFEs

• {SF(aid=>749179,tag=>rfe)}{SF}
• {SF(aid=>816328,tag=>rfe)}{SF}
• {SF(aid=>654158,tag=>rfe)}{SF}
• Thread about newsletter feature

New for 1.8:
The following options can now be set on a per newsletter basis:

Users can subscribe/unsubscribe to this list

Determines whether users can subscribe themselves

Users can subscribe any email address

Determines whether the user can subscribe alternate addresses than the one they registered with

Add unsubscribe instructions to each newsletter

Determines whether to include an unsubscribe msg when a newsletter is sent

Validate email addresses

Determines whether the address must be validated with a test email

Also removed frequency as unused.

Wishlist:
-Full and automatic integration of content from the CMS (articles, comments, forum posts, blog posts, etc.) into newsletters via include statements
-Moderation option for all content, such that an admin can choose what pieces to send out via email.
-VERP (variable envelope return processing) to ensure good bounce handling
-Tracking of bounces (with bounce details) in user accounts (good for tracking mail delivery problems)
-Date tracking of when people subscribe and unsubscribe (useful for when someone leaves an account without unsubscribing, and a new person gets it and complains because they're receiving mail they didn't request)
-ability to track the number of e-mails opened
-clickthrough tracking
-Capability to send html + text, with the user choosing which they receive on a global and per list basis
-custom field & personalized email capability
-Full online subscribe, unsubscribe, and change address capabilities, for individual users to perform on their own and for admins to perform for users.