Hello,
I work for a large university and was recently put in charge of consolidating a
bunch of mailman lists from multiple domains onto 1 server.
First problem that I encountered was the single namespace issue with virtual
domains, so i removed the stock Mailman 2.1.12 that came with Ubuntu,
Before you commit too heavily to this, I suggest you look at the first
570+ lines at
http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/annotate/head%3A/NEWS
and see if you really want to be installing a 4 year old release.
The only reason i chose 2.1.7 is because the patch applied
Mark,
I made a 2.1.13 vhost patch a little differently. I made a bazaar 2.1.7
branch, applied the 2.1.7 vhosts patch, committed the result, did a
bzr merge from the 2.1.13 branch which produced 5 conflicts, the only
significant ones being in Mailman/MTA/Utils.py and Mailman/Utils.py,
and
I believe that mailing lists exist across all virtual domains listed?
Is there any way to allow for the same mailing list on different
domains with one instance of mailman?
So I could have us...@lists.domain1.net AND us...@lists.domain2.net as
two separate lists.
Currently, out of the box,
Mark,
I fixed the archiving for both private and public archives so no
rewriting is involved. private.py does the right thing with my
additional patches. I also patched the GetBaseArchiveURL() method to
include the virtual host directory in the public archive URL.
Finally, I had an issue
On Feb 3, 2010, at 5:51 AM, Guy wrote:
===
Bug in Mailman version 2.1.13
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited,
but the webmaster can find this information
Most likely an error in changes you made
add this to mm_cfg.py
DEBUG_MODE = True
There is no DEBUG_MODE switch in standard Mailman or in the vhost
patch. Putting the above in mm_cfg.py does nothing because nothing
references it.
Exceptions and tracebacks should be logged to
