| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
but also point to the wiki as the definitive information on
requirements. (The wiki has been updated.) Remove specific gcc
version requirements; I don't think it actually matters these days.
Also, add a simple Makefile for building the documentation.
|
| |
|
|
|
|
|
| |
admin or moderator password.
- Changed cmd_who.py public roster syntax to accept optional list admin or moderator password.
|
| |
|
|
|
| |
empty list is the appropriate value if Postfix virtual domains aren't used.
|
|
|
|
|
| |
file other than stdout. Fix a typo in getting the digest style. Update
copyright years.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
user passwords. Default is 'none' which disables passwords altogether
in the resulting XML. Other choices include:
plain -- output passwords in plain text
sha -- sha1 hash of password
ssha -- sha1 hash salted with 4 random bytes (only available if
os.urandom() works)
|
|
|
|
|
|
|
|
|
| |
upgrade from Mailman 2.1 to the trunk -- after the merge of the SQLAlchemy
code -- will need this. Note that I don't intend to implement import in
MM2.1.
This script is a little diffferent than what's on the trunk, but functionally
(and schema-wise) equivalent.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
'iso2022_jp' does not exist in japanese (but 'iso_2022_jp').
We try to test Japanese (and Korean) codecs before changing path order
and do not import japanese/korean if the codecs already exist in python
distribution. (as in 2.4 and 2.5) Importing japanese/korean is going away
in mailman-2.2.
|
| |
|
|
|
| |
details=all page.
|
|
|
|
| |
Knowles and JC Dill.
|
| |
|
|
|
|
|
| |
external the latter to get that back into the release, but I really
don't want to maintain multiple copies of the web pages.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
it's still crappy coding that should be fixed. CVE-2006-2191. Thanks go to
Karl Chen, Martin 'Joey' Schulze, and Elie Mamane.
|
|
|
|
|
| |
file and the template admindbdetails.html by Jan Veuger <info@janveuger.com>
Clytie Siddall <clytie@riverland.net.au>
|
| |
|
|
|
|
|
| |
include a new 'Community' link in the topbar that points to the COM space in
the wiki.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
yet ready to work from the trunk). Also, get rid of all the obsolete
.cvsignore directories, they're no longer needed.
Almost ready for 2.1.9rc1!
|
| |
|
|
|
|
| |
This is in prep for the 2.1.9 release.
|
|
|
|
|
| |
Moritz Naumann and most of the repair work done by Mark Sapiro (with some
additional work by Barry).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- In SecurityManager.py, fix the parsecookie() code to work with Python 2.5
generated cookie text. The latter was changed to be more RFC compliant so
it does not output trailing semicolons for each line of cookie text. This
broke the splitting rules, so now first split on newlines, then on ';\s*'.
This should work across all Python versions.
- In Python 2.5, exceptions are new-style, and thus are no longer of
ClassType. The instantiation type test in hold_for_approval() was too
naive. This one is fixed differently here than in the MM trunk because in
Python 2.1, 'type' isn't a type, it's a function and so can't be used as the
second argument to isinstance() directly.
- Raising strings generates deprecation warnings in Python 2.5. Switch the
one weird use of this in Utils.py to use a class exception. Don't call it
"quick exit" though because it's probably not.
|
| |
|
|
|
| |
The caller may want to override the list setting.
|
|
|
|
| |
"while times.has_key(key):" for execution efficiency while maintaining
Python 2.1 compatibility.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Queue/Runner.py
- Queue/Switchboard.py
Backported the gfiles backup changes from the trunk. The following comments
are from the trunk checkin. Note that the test cases are not added.
Added robustness to Switchboards and Runners so that if a runner crashes
uncleanly (e.g. segfaults the Python interpreter), messages being processed
will not be lost.
The vulnerability, ideas, and patches are credited to Richard Barrett and Mark
Sapiro. Their original work was modified by Barry for this commit and any
bugs are his fault.
The basic idea is that instead of unlinking a .pck file in dequeue(), the file
is renamed to a .bak file. The Switchboard grows a finish() method which then
unlinks the .bak file. That class's constructor also grows a 'restore'
argument (defaulting to false), which when true moves all .bak files it finds
in its hash space to .pck, thereby restoring a file lost while "in flight".
This relies on the fact that even with multiple qrunners, exactly one process
will be responsible for one hash space slice, so it's never possible (under
normal operation) for a .bak file to be renamed to .pck by some other process.
Test cases for both the new Switchboard behavior and the use of that by Runner
subclasses has been added.
There are two things to watch out for, either of which may require some
additional changes. There is some small potential to duplicate messages in
various queues, if say 'mailmanctl' were improperly started more than once by
a site admin. This usually won't happen unless an admin is overly eager with
the mailmanctl -s switch, so we can chalk this one up to operator error. I'm
not sure what more we can do about that.
There's also a possibility that if we're processing a message that continually
causes the Python interpreter to crash, we could end up duplicating messages
endlessly. This is especially troublesome for the Outgoing runner which could
conceivably cause a mail flood. I consider this the more critical issue to
defend against, probably by adding a numbering scheme to the .bak file names
and refusing to restore a .bak file more than say 3 times without human
intervention.
|
|
|
|
|
| |
Dutch.
Clytie Siddall <clytie@riverland.net.au>
|
|
|
|
|
| |
slices that could result in unprocessable queue entries. Improved FIFO
processing when two queue entries have the same timestamp.
|