| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
remove held message files for a list with regexp special characters in
its name.
|
|
|
|
|
| |
the 2.1 branch for release with 2.1.19. The 2.2 branch is now no different
from the 2.1 branch and will no longer be maintained.
|
| |
|
| |
|
|
|
|
| |
bin/newlist. (LP: #1200763)
|
|
|
|
| |
determined to be truly stale. (LP: #1189558)
|
|
|
|
| |
bin/add_members as the source. (LP: 1161642)
|
| |
|
|
|
|
| |
(LP: 1082711)
|
|
|
|
| |
mm_cfg.py setting MASTER_LOCK_FILE. (LP: 1082308)
|
|
|
|
| |
by admin. (LP: 1070574)
|
| |
|
|
|
|
| |
MTA = 'Postfix'. Bug #266408.
|
|
|
|
| |
fixed a problem with removal of stale locks for the list. Bug #700528.
|
|
|
|
|
|
|
| |
Bug #670988.
- Fixed the host name in the From: address of the owner notification from
bin/add_members. Bug #666181.
|
| |
|
|
|
|
| |
Bug #587657.
|
|
|
|
|
|
| |
allow bin/newlist and the the create CGI to pass urlhost so the host
will be correct in the listinfo link on the emptyarchive page.
Bug #529100.
|
| |
|
|
|
|
| |
Mailman's lists/ directory was not a directory. Bug #265613.
|
| |
|
| |
|
| |
|
|
|
|
| |
I've modified the patch to improve some of the stylistic issues.
|
|
|
|
| |
Launchpad bug #280418.
|
|
|
|
| |
Launchpad bug #284802.
|
| |
|
|\ |
|
| | |
|
| | |
|
|/
|
|
|
|
| |
templates/xx to lists/xx if a list has the same name as a language
code. Also fixed the absolute path to lists/ (1418670 ).
|
|
|
|
|
| |
available_languages if it is other than the server's default language
(1906368).
|
|
|
|
| |
MembershipIsBanned exception and report appropriately.
|
| |
|
| |
|
| |
|
|
|
|
| |
to begin with.
|
| |
|
| |
|
|
|
|
| |
This has been broken since 2.1.5!
|
| |
|
|
|
|
|
|
| |
directories to make sure they didn't have certain 'other' permissions, but it
didn't check these directories for the necessary user and group permissions.
This is now fixed.
|
|
|
|
|
| |
paths more deeply nested than 1 level. IOW, -r package.package.module.func
now works as intended.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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.
|