We have about 500 lists and the archives keep growing.
We are now over 12 Gigs and are rapidly running out of
space.
How does one go about trimming back on the older archives.
Here is what I have been doing with a list with the name test
but just realized my logic was flawed.
I have a script
I am running mailman-2.1.5 on a redhat linux AS 4 system with
all the latest redhat fixes.
I just ran the mailman-2.1.6 upgrade and encountered the following messages
for each (but not all my lists)
Updating mailing list: 4h-northern^M
Updating the held requests database.^M
- updating old
/mailman/qfiles'
but the actual qfiles were in a different location
so I made the following substitution.
QUEUE_DIR = '/opt/mailman/qfiles'
The update program was using this file name which
was causing a problem.
That seemed to make things happy.
paulw
Paul Williams
Paul Williams wrote:
1). A user added a large number of subscribers by uploading
an Excel spreadsheet. Mailman accepted the file and
addresses appeared reasonable when viewed with IE but
not so good with mozilla (each alpha char was followed by
a box). I was able
I just ran into 2 problems.
1). A user added a large number of subscribers by uploading
an Excel spreadsheet. Mailman accepted the file and
addresses appeared reasonable when viewed with IE but
not so good with mozilla (each alpha char was followed by
a box). I was
I have an Umbrella list which has both
lists and subscribers as members of the list.
The default setting for an Umbrella list is
Suffix for use when this list is an umbrella for other lists,
according to setting of previous umbrella_list setting
set at
-owner
This causes a problem
Just last week I did a move all my mailmna lists
to a totally new server, I moved where mailman was installed
and had a new version of Mailman.
I needed to run
bin/withlist -l -r fix_url -a
as described in 3.4 in the Mailman FAQ
and then I encountered the apparently known problem described in
There is also an email-based interface for users (not administrators)
of your list; you can get info about using it by sending a message
with just the word `help' as subject or in the body, to:
[EMAIL PROTECTED]
Then you will receive the info that you can send the following
command
who
I couple of weeks ago I asked how people were
dealing with disk storage with mailman archives.
I didn't receive an email that I could use. In the end
we used a similar method that we were using with listproc.
If anyone is interested, I have indicated the method
in the following description.
We have over 300 lists, many are being archived and we allow
our members to send attachments.
The archives are rapidly using up all the disk space on
the partition. We could remotely mount a larger
partition, but that would just delay the problem, because
it looks like mailman archives will just
junk
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
We are running mailman-2.1.1-5 on a Redhat 9 server.
Recently, (I think on Aug 30) we started getting the following error messages
Subject: Cron [EMAIL PROTECTED] /usr/bin/python -S /var/mailman/cron/senddigests
X-Cron-Env: SHELL=/bin/sh
X-Cron-Env: HOME=/var/mailman
X-Cron-Env: PATH=/usr/bin:/bin
12 matches
Mail list logo
