On Tue, 2 Feb 2010, Mark Sapiro wrote:
Geoff Shang wrote:
I need to move a list from one domain to another. ...
Thanks for this Mark, it's exactly what I needed and went off without a
hitch.
I also put the old list address in as an acceptable alias and put a
forward into Postfix'
Hi,
I've patched 2.1.13 source with
http://www.msapiro.net/mm/2.1.13_vhost.patch, vhost_extra_patch.txt
and a patch for qrunner-slicing. I'm trying to run mailman across
multiple mail servers and web servers. /var/lib/mailman is on a shared
ISCSI mount.
Starting mailman on any given server
OK, I still feel dumb and have drank all the available coffee, so now I
will ask.
Can someone point me to where to find the info on how/where to edit the
umbrella listinfo page? (http://forktechs.com/mailman/listinfo)
Thanks in advance
Edward Tharp
[UPDATE]
Looking at the code I can find where the master-qrunner file is
created in mailmanctl, but I'm not sure where the
master-qrunner.FQDN.numeric string comes from so I didn't want to
try making changes without some idea what's defining those file names.
Made a patch for Defaults.py.in
Hello graphic designers, we have our first logo submission!
http://wiki.list.org/display/DEV/LogoSubmissions
Thanks Andrija for kicking us off. Everyone else: sharpen up those inkscapes,
gimps, or whatever other tool you use and submit some logos. If you have any
problems adding your logos
I have a new installation of Mailman 2.1.12 running on Ubuntu with Postfix.
When I create a list, it does not update my /etc/aliases file. It does update
the /var/lib/mailman/data/aliases file. This causes Postfix to reject any email
sent to the list. What have I done wrong in configuring this
Hi,
I have been using a Debian-based mailman installation for some time now,
administering a few lists, all hosted on xxx.tld. Everything worked fine.
I recently modified the underlying Exim 4 configuration to support
virtual domains, namely xxx.tld, yyy.tld and zzz.tld. I used a typical
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
UGSD wrote:
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
I wrote:
I think I may have uncovered a bug in Mailman 2.1.13. I have not
completed my research. I have a script that refreshes the subscriber
list via:
/usr/lib/mailman/bin/sync_members -w=no -g=no -d=no -a=no \
-f /e tc/mailman/generated_lists/LISTNAME LISTNAME
where
Guy wrote:
I've patched 2.1.13 source with
http://www.msapiro.net/mm/2.1.13_vhost.patch,
The current patch is http://www.msapiro.net/mm/2.1.13-1_vhost.patch
See http://www.msapiro.net/mm/_README
vhost_extra_patch.txt
This plus a fix for the 'invalid listname issue is incorporated in the
Guy wrote:
Made a patch for Defaults.py.in that seems to have resolved that problem.
Do not ever patch Defaults.py. Override the settings in mm_cfg.py
instead. See the FAQ at http://wiki.list.org/x/fIA9
I've now run into two other problems.
1) The lists have their own vhost in apache
ed wrote:
OK, I still feel dumb and have drank all the available coffee, so now I
will ask.
Can someone point me to where to find the info on how/where to edit the
umbrella listinfo page? (http://forktechs.com/mailman/listinfo)
The listinfo overview is built on the fly (there's no template)
Barry Finkel wrote:
I ran a test with a test list on my test virtual machine, and this is
what is happening. The line in the -f file for sync_members
bsf-cr...@example.com (New 1 (zzz))
is causing all of the succeeding lines in that file to be treated as
part of the parenthesized
Dan Brita wrote:
I have a new installation of Mailman 2.1.12 running on Ubuntu with Postfix.
When I create a list, it does not update my /etc/aliases file. It does update
the /var/lib/mailman/data/aliases file. This causes Postfix to reject any
email sent to the list. What have I done wrong in
Olivier Parisy wrote:
Clearly, the * rule is taking precedence on mailman delivery, which do not
even seem to get the message.
The only workaround I found is to add lines such as mylist : mylist to the
/etc/exim4/virtual/xxx.tld file (one by mailing list). This is inconvenient to
say the
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
Barry Finkel wrote:
I ran a test with a test list on my test virtual machine, and this is
what is happening. The line in the -f file for sync_members
bsf-cr...@example.com (New 1 (zzz))
is causing all of the succeeding lines in that file to be treated as
part of the parenthesized
18 matches
Mail list logo
