How do I verify a
3.0 beta 3 -- "Here Again"
* Python 2.7 is now required. Python 2.6 is no longer officially supported.
The code base is now also `python2.7 -3` clean, although there are still
some warnings in 3rd party dependencies. (LP: #1073506)
* **API change**: The JSON representation for held messages no longer
includes the `data` key. The values in this dictionary are flatted into
the top-level JSON representation. The `key` key is remove since it's
redundant. Use `message_id` for held messages, and `address` for held
subscriptions/unsubscriptions. The following `_mod_*` keys are inserted
without the `_mod_` prefix:
- `_mod_subject` -> `subject`
- `_mod_hold_date` -> `hold_date`
3.0 beta 2 -- "Freeze"
* The link between members and the mailing lists they are subscribed to, is
now via the RFC 2369 `list_id` instead of the fqdn listname (i.e. posting
address). This is because while the posting address can change if the
mailing list is moved to a new server, the list id is fixed.
- IListManager.get_by_list_id() added.
- IListManager.list_ids added.
- IMailingList.list_id added.
- Several internal APIs that accepted fqdn list names now require list ids,
e.g. ISubscriptionService.join() and .find_members().
- IMember.list_id attribute added; .mailing_list is now an alias that
retrieves and returns the IMailingList.
* `passlib`_ is now used for all ...
3.0 beta 1 -- "The Twilight Zone"
* Schema migrations have been implemented.
* Implement the style manager as a utility instead of an attribute hanging
off the `mailman.config.config` object.
* PostgreSQL support contributed by Stephen A. Goss. (LP: #860159)
* Separate out the RFC 2369 header adding handler.
* Dynamically calculate the `List-Id` header instead of storing it in the
database. This means it cannot be changed.
* Major redesign of the template search system, fixing LP: #788309. $var_dir
is now used when search for all template overrides, site, domain, or
mailing list. The in-tree English templates are used only as a last
* Support downloading templates by URI, includi...
3.0 alpha 8 -- "Where's My Thing?"
* Factor out bounce detection to `flufl.bounce`.
* Unrecognized bounces can now also be forwarded to the site owner.
* mailman.qrunner log is renamed to mailman.runner
* master-qrunner.lck -> master.lck
* master-qrunner.pid -> master.pid
* Four new events are created, and notifications are sent during mailing list
- ListCreatingEvent - sent before the mailing list is created
- ListCreatedEvent - sent after the mailing list is created
- ListDeletingEvent - sent before the mailing list is deleted
- ListDeletedEvent - sent after the mailing list is deleted
* Four new events are created, and notifications are sent during domain
3.0 alpha 7 -- "Mission"
* Significant updates to the subscription model. Members can now subscribe
with a preferred address, and changes to that will be immediately reflected
in mailing list subscriptions. Users who subscribe with an explicit
address can easily change to a different address, as long as that address
is verified. (LP: #643949)
* IUsers and IMembers are now assigned a unique, random, immutable id.
* IUsers now have created_on and .preferred_address properties.
* IMembers now have a .user attribute for easy access to the subscribed user.
* When created with add_member(), passwords are always stored encrypted.
* In all interfaces, "email" refers to the textual email address while
3.0 alpha 6 -- "Cut to the Chase"
* The functionality of 'bin/list_members' has been moved to
* 'bin/mailman info' -v/--verbose output displays the file system
layout paths Mailman is currently configured to use.
* You can now configure the paths Mailman uses for queue files, lock files,
data files, etc. via the configuration file. Define a file system 'layout'
and then select that layout in the [mailman] section. Default layouts
include 'local' for putting everything in /var/tmp/mailman, 'dev' for local
development, and 'fhs' for Filesystem Hierarchy Standard 2.3 (LP #490144).
* Queue file directories now live in $var_dir/queues.
3.0 alpha 5 -- "Distant Early Warning"
* Add REST API for subscription services. You can now:
- list all members in all mailing lists
- subscribe (and possibly register) an address to a mailing list
- unsubscribe an address from mailing list
* 'bin/dumpdb' is now 'bin/mailman qfile'
* 'bin/unshunt' is now 'bin/mailman unshunt'
* Mailman now properly handles the '-join', '-leave', and '-confirm' email
commands and sub-addresses. '-subscribe' and '-unsubscribe' are aliases
for '-join' and '-leave' respectively.
* devmode settings now live in their own [devmode] section.
* Mailman now searches for a configuration file using this search order. The
3.0 alpha 4 -- "Vital Signs"
* 'bin/inject' is now 'bin/mailman inject', with some changes
* 'bin/mailmanctl' is now 'bin/mailman start|stop|reopen|restart'
* 'bin/mailman version' is added (output same as 'bin/mailman --version')
* 'bin/mailman members' command line arguments have changed. It also
now ignores blank lines and lines that start with #. It also no longer
quits when it sees an address that's already subscribed.
* 'bin/withlist' is now 'bin/mailman withlist', and its command line
arguments have changed.
* 'bin/mailman lists' command line arguments have changed.
* 'bin/genaliases' is now 'bin/mailman aliases'
* A near complete rewrite of the low-level SMTP delivery machi...