| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
| |
- As the most common interface for adding new members (and users), adapt the
password storing bit to storing only encrypted passwords in the database.
schema.cfg:
- Remove the creator_pw_file and site_pw_file as they are obsolete.
- Add password_schema key for defining the default password encryption scheme.
mailman.sql, user.py:
- Store the password as a binary blob instead of as unicode text.
|
| |
|
|
| |
useful for ensuring current functionality.
|
| | |
|
| |
|
|
|
| |
due to _() interpolation) and a few other problems that did not have
immediately obvious fixes.
|
| |
|
|
| |
* Make sure all paths are absolute
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
var_dir in the config file is a relative path, the bin/master and bin/qrunner
subprocesses end up creating another hierarchy under $VAR_DIR. This is
because 'bin/mailman start' chdirs to $VAR_DIR before starting master.
The fix involves putting the absolute path to $VAR_DIR in the $MAILMAN_VAR_DIR
environment variable. If the configuration file reader sees this, it uses the
value instead of $var_dir from the configuration file.
Another change is to remove qrunner's --subproc/-s option and stick this in
the environment as well, using $MAILMAN_UNDER_MASTER_CONTROL.
Other fixes here include:
* Deciphering the master lock file contents correctly
* Reformatting the error message so that it fits in 79 columns when prefixed
by argparse error info.
|
| |
|
|
|
|
|
|
| |
support the Filesystem Hierarchy Standard. This is done through the
configuration file.
* add a --paths/-p option to 'bin/mailman info'
* PIDFILE -> PID_FILE
|
| | |
|
| |
|
|
|
|
|
|
| |
* Fix a few small typos in exception handlers.
* Move the initialization of the Zope Component Architecture into the first
initialization step. The only reason we couldn't do that previously was
because the domain object referenced the config, causing a circularity
problem. Refactor the Domain implementation to avoid that.
|
| |
|
|
| |
package.
|
| |
|
|
|
|
|
|
| |
Add an IDomainManager and a global domain manager which can be gotten by
adapting the global config object.
Add an IDomainCollection interface for exposing the domain manager onto the
API.
|
| |
|
|
|
|
|
| |
* Get rid of in-Python adapter registration in favor of ZCML. Eventually, I'd
like to get rid of the ZCML.
* Set the view_permission to None, but it's still not right.
* Add IDomainSet and an adapter from Configuration to IDomainSet.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This lets you run a bit of Python at various stages of the initialization
process.
Move the warnings filters to the top mailman package __init__.py so you always
get it. lazr.restful is too chatty.
The environment variable $MAILMAN_CONFIG_FILE now overrides -C. Hmm, I think
we really want it the original way.
|
| |
|
|
|
|
|
|
|
|
|
| |
Add logging to the RESTRunner.
Also, use pkg_resources.resource_stream() instead of .resource_string() where
appropriate.
Add a bunch of XXX comments for things I need to figure out about the Zope-ish
parts of the lazr.restful implementation. Change __getitem__() api to
_lookup().
|
| |
|
|
|
|
|
| |
language manager stuff into a separate Language class, and be clearer in the
APIs about whether we want a language code or a Language instance.
The impetus to this was to get rid of Utils.GetCharSet(), which is done.
|
| | |
|
|
|
correctly regardless of how it's used.
|
