:
>
>Hi,
>
>thanks for the response
>
>Shouldn't that be srm.conf ???
>
>Not that I am a expert at this, but that's what I read??
>
>Regards
>
>Erik
>
> - Original Message -
> From: Anna Fong
> To: [EMAIL PROTECTED] ; [EM
Go to your installation for apache and update the httpd.conf file (~/apache/conf/httpd.conf)
You'll need to add two entries in that file -- an alias for the archives and an alias to the mailman scripts.
Locate the aliases section in the httpd.conf file. Add this for the archives. Be sure to ins
_archive_file_dir
m.public_archive_file_dir='$newroot/archives/public'
m.archive_directory
m.archive_directory='$newroot/archives/private/$list'
m.Save()
EOF
---snip---
On Thu, Apr 11, 2002 at 10:24:41AM -0700, Anna Fong wrote:
> #!/bin/sh
>
> newroot='/var/m
François,
Try this from
http://mail.python.org/pipermail/mailman-users/1999-August/002009.html
---snip---
#!/bin/sh
newroot='/var/mailman'
for list in `ls $newroot/lists/detente`
do
python -i $newroot/bin/withlist -l $list <
m.private_archive_file_dir
m.private_archive_file_dir='$newroot/arch
I had the same experience you mentioned. For my recent migration from MM 1.1 to MM 2.0.8, I created new lists on the new server, copied from the old server the subdirectories for my lists under ~mailman/lists and ~mailman/archives to the new server. Then updated the config.db manually using the
2002 at 11:17:39AM -0800,
> Anna Fong <[EMAIL PROTECTED]> wrote
> a message of 20 lines which said:
>
>> I remember reading a post a while ago about migrating a Mailman list from
>> one server to another, but I can't find it through search.python.org
>> Anyon
move_list doesn't update config.db correctly. Is this a known bug? If so,
is there a patch?
Recently tried migrating lists from Mailman 1.1 on one server to Mailman
2.0.8 on different server.
Noticed that move_list was not correctly updating path in config.db for
archives which causes the list
Recently tried migrating lists from Mailman 1.1 on one server to Mailman
2.0.8 on different server.
Noticed that move_list was not correctly updating path in config.db for
archives which causes the list not to post mail. (Mailman 2.0.8 on
different server)
When doing `strings config.db` on old c
There are no posts after migrating Mailman list.
Help!
Our organization has two versions of Mailman on two
different servers, both running production lists. I
wanted to move my production lists off of my server
which is running an older version of Mailman to my
colleague's server.
Before I act
There are no posts after migrating Mailman list.
Help!
Our organization has two versions of Mailman on two
different servers, both running production lists. I
wanted to move my production lists off of my server
which is running an older version of Mailman to my
colleague's server.
Before I act
I remember reading a post a while ago about migrating a Mailman list from
one server to another, but I can't find it through search.python.org
Anyone know how I can find it?
I want to migrate a list from one server running Mailman 1.1 to another
server running Mailman 2.08. What's the best way t
> Can anyone just tell me if it is possible put this solution to work?
> IPLANET+MAILMAN+SOLARIS
Yes, I have Mailman on Solaris working with iPlanet. However, I am using
sendmail as the mail server.
Anna Q. Fong, Webmaster
California Dat
I also am interested in setting up my list as a 'moderator post only' list.
The option mentioned by Jesse doesn't seem to exist in Mailman 1.1
Am I missing something or is there a way to do this in Mailman 1.1? (I can
restrict to members only but not to key email addresses under Privacy
Options)
I have two lists running with Mailman. One works, the other broke. The
one that is broken seems not able to recover a lockfile.
I've sent a bug report to SourceForge but I need to get the list running
again ASAP.
Has anyone seen this before?
Bug in Mailman vers
14 matches
Mail list logo
