| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There's a new "configure" entry in the archiver's section, which can
point to an ini-compatible configuration file (ConfigParser is used) for
additional archiver-specific configuration.
The existing archiver config have been split off schema.cfg to their own
configuration files. These shipped files can be overridden by a conf
file of the same name in $ext_dir.
The ini-file loading method should be rather generic, in case we want
the same feature somewhere else.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
-------------
* `[passlib]path` configuration variable renamed to `[passlib]configuration`.
* Postfix-specific configurations in the `[mta]` section are moved to a
separate file, named by the `[mta]configuration` variable.
* In the new `postfix.cfg` file, `postfix_map_cmd` is renamed to
`postmap_command`.
Also:
* More Python 2.7-isms, use assertMultiLineEqual() directly.
* Added external_configuration() and load_external() to mailman.config.config
* ConfigLayer does a blanket set of [postfix]postmap_command so subtests
generally won't have to.
|
| | | |
|
| |\ \ |
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | | |
subprocesses when -C was given. LP: #982551
|
| |/ /
| |
| |
| |
| | |
The code base is now also `python2.7 -3` clean, although there are still
some warnings in 3rd party dependencies. LP: #1073506
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
--------
* The `ban` table now uses list-ids to cross-reference the mailing list,
since these cannot change even if the mailing list is moved or renamed.
Interfaces
----------
* The `IBanManager` is no longer a global utility. Instead, you adapt an
`IMailingList` to an `IBanManager` to manage the bans for a specific
mailing list. To manage the global bans, adapt ``None``.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
support. Contributed by Jimmy Bergman.
* `bin/mailman aliases` loses the `--output`, `--format`, and `--simple`
arguments, and adds a `--directory` argument. This is necessary to support
the Postfix `relay_domains` support.
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| | |
list creation/removal.
Improve postfix documentation in MTA.rst by referencing the official docs.
|
| | |
| |
| |
| |
| |
| |
| | |
POST to .../addresses/<email>/verify and .../addresses/<email>/unverify
respectively. The POST data is ignored. It is not an error to verify or
unverify an address more than once, but verifying an already verified
address does not change its `.verified_on` date. (LP: #1054730)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
name or password. For passwords, you pass in the clear text password and
Mailman will hash it before storing.
Also:
* Major refactoring of validators for PUT and PATCH. Pull the common logic
out of configuration.py and put it in a PatchValidator class in
helpers.py. Also move GetterSetter to helpers.py
* Add new exception classes RESTError, UnknownPATCHRequestError,
ReadOnlyPATCHRequestError. These are used in the PatchValidator.
* Added Validator.update() which works nicely for PATCH and PUT.
|
| |\ \
| |/
|/|
| |
| |
| |
| |
| | |
Bergman).
* The canonical resource for a mailing list (and thus its self_link) is now
the URL with the list-id. To reference a mailing list, the list-id url is
preferred, but for backward compatibility, the posting address is still
accepted.
|
| | | |
|
| |/
|
|
| |
list creation/removal
|
| | |
|
| | |
|
| |\
| |
| |
| | |
Fixed by Mark Sapiro.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
- member.mailing_list -> list_id
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
(LP: #1024509)
+ 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.
- list_id added (LP: #1024509)
|
| | |
| |
| |
| | |
Sulfrian. (LP: #1039129)
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
- migration.rst needs special cleanup since the Version table is no longer
wiped by the test machinery. This only caused failures when running
the migration.rst test multiple times, and only on PostgreSQL.
- Complete the removal of archive_volume_frequency and
generic_nonmember_action for PostgreSQL.
- Remove setting archive_volume_frequency in the default style.
|
| | | |
|
| | |
| |
| |
| | |
(LP: #975696)
|
| | |
| |
| |
| | |
(LP: #1031393)
|
| | |
| |
| |
| |
| |
| | |
Also, allow doctest cleanups to be tuples, in which case the first item is the
callable and the subsequent items are the arguments. Makes for
config.pop()'ing much nicer.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
of an email address.
* Rectify an omission in the copyright assignees.
* Of course, don't use PostgreSQL by default in the test suite.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ArchivePolicy. This describes the three states of never archive, archive
privately, and archive_publicly. (LP: #967238)
Database
--------
* Schema migrations (LP: #971013)
- include_list_post_header -> allow_list_posts
- news_prefix_subject_too -> nntp_prefix_subject_too
- news_moderation -> newsgroup_moderation
- archive and archive_private have been collapsed into archive_policy.
- nntp_host has been removed.
* The PostgreSQL port of the schema accidentally added a moderation_callback
column to the mailinglist table. Since this is unused in Mailman, it was
simply commented out of the base schema for PostgreSQL.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
include_list_post_header -> allow_list_posts
Also add a bunch more migration tests.
|
| | | |
| | |
| | |
| | | |
into the hands of the database modules, by using ZCA adapters.
|
| | | |
| | |
| | |
| | | |
them.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
individual database classes themselves. This does mean that the temporary
factory must know something special about the sqlite and postgresql databases,
but I think that's an acceptable trade-off.
This should make the test code cleaner, and allow me to write better support
for temporary PostgreSQL databases.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
the testing framework.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
production database.
- Add an IDatabaseFactory interface with two named utility implementations.
The initialization subsystem will either ask for the 'testing' or
'production' factory utility depending on whether we're in the test suite or
not. The testing factory returns an IDatabase that can be _reset().
- initialize_2() now takes an optional `testing` argument, defaulting to
False. The test ConfigLayer will pass in True.
- Remove _reset() from the base database class.
- The ModelMeta now adds a PRESERVE attribute to database classes. This
defaults to False, meaning by default the test framework will reset the
table. The Version table is preserved because it records the schema
migrations.
- Because of the above, we no longer need to support pre_reset() and
post_reset() on migrations.
Also, bin/mailman should allow the standard configuration file search
algorithm to be used except when -C/--config is given.
|
| | | |
| | |
| | |
| | |
| | | |
- store.rollback() is better than store.execute('ABORT;')
- We need to do a commit after the migrations are loaded.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Improve migration logging
- Disable pre_reset() and post_reset() on migrations, which might need to be
re-enabled for SQLite support.
- Be sure to record the migration version in PostgreSQL.
- Parameterize the Error that will occur.
- Better sample data for PostgreSQL and SQLite, which have different formats.
|