[Mailman-Users] This I hate

2004-06-06 Thread Mel Sojka
Well recently I installed a second version of python and got MailMan 
2.1.4 up and running.  I did this using a post or a FAQ entry.  This was 
on a remote clients machine and I guess I left my notes there.  Whoever 
made that post about installing a second version of Python please do so 
again or point me to it in the FAQ. I need to do it again.

Thanks Mel

--
System Janitor/Network Plumber http://www.nwla.com
Linux User #25446Linux 2.4.22
--
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/


[Mailman-Users] Adding Subs-criptions by Email Rather than Web Interface

2004-06-06 Thread Mike Phillips
I posted this message before, but it was held by the administrator thinking
it was an admin request. If it ever made it to the list, I did not see it,
so I'll try again.

Is there a way to send a subs-cribe request to the list via email, or do all
of the subs-cribes have to be through the web interface? The help email
indicates that there is a subs*cribe option, but I cannot get it to work.

Excuse the hyphens -- I'm trying to outsmart the list server.


--
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/


Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

2004-06-06 Thread Alex Dupont
Hello Tokio,


[sorry, this got only mailed to you personally; again to the list;
strange list setting btw...]

 Have you done 'bin/update' after moving the backup config.pck file
 into the newly installed list directory ?

No updates are necessary. The more I think about it I get the
feeling that my backup-files somehow got screwed up... Still, can no
one tell me where I can at least find the subscribed addresses? That
information has to be stored _somewhere_??

 I think every packager should disclose their configure options so
 that upgrading can be done through our source distribution and the
 list dbs automatically updated !

Agreed. However, using an update script provided by the distribution -
specifically made for that application - should do _all_ the necessary
work without screwing anything up. That's how it works in about 95% of
the time. Errors can always happen. Yet it is beyond my comprehension
how any script performing an upgrade would delete any file without
making an automatic backup of it. And this has absolutely nothing to
do with the fact that one should always backup before any such
operation. Because sometimes the upgrade is performed by accident.
Believe me, that happens...

Greetings
Alex


--
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/


Re: [Mailman-Users] Upgrade to 2.1.4 failed - user lost - recover via backup unsuccessful - any ideas?

2004-06-06 Thread Tokio Kikuchi


Have you done 'bin/update' after moving the backup config.pck file
into the newly installed list directory ?

No updates are necessary. The more I think about it I get the
feeling that my backup-files somehow got screwed up... Still, can no
one tell me where I can at least find the subscribed addresses? That
information has to be stored _somewhere_??
Have you also tried bin/update --force ?
Another useful script in the bin directory may be dumpdb.
It will dump all the data in your backup file if the format is not
corrupted.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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/


Re: [Mailman-Users] change language name

2004-06-06 Thread Barry Warsaw
On Thu, 2004-05-27 at 11:35, Brad Knowles wrote:
 At 10:06 AM +0200 2004/05/27, Urska Colner wrote:
 
   i have just noticed on your page
   http://www.gnu.org/software/mailman/i18n.html
 
   I think the official page is actually at http://www.list.org/i18n.html.
 
   that Slovenian (sl_SI) is written as Solvenian. please correct this.
 
   However, this page has the same error.  I believe that this will 
 need to be corrected by Barry Warsaw.

Fixed in cvs.  This will be corrected on the web pages the next time I
push them out.

Thanks,
-Barry



signature.asc
Description: This is a digitally signed message part
--
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/

[Mailman-Users] why is the queue runner taking 75 seconds per transaction?

2004-06-06 Thread Andrew Beals
I just installed mailman and I'm getting funny behavior in that it takes the 
queue runner 75 seconds per transaction to process.  This can't be right or a 
high-usercount mailing list wouldn't be practical.

What am I missing?


aTdHvAaNnKcSe

Andy

ps.  A sample from /usr/local/mailman/logs/smtp:
Jun 03 11:16:32 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.088 seconds
Jun 03 11:17:48 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.265 seconds
Jun 03 11:19:03 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.263 seconds
Jun 03 11:20:18 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.185 seconds
Jun 03 11:21:33 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.172 seconds
Jun 03 11:22:49 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.155 seconds
Jun 03 11:24:04 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.141 seconds
Jun 03 11:25:19 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.140 seconds
Jun 03 11:26:34 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.287 seconds
Jun 03 11:27:49 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.197 seconds
Jun 03 11:29:05 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.095 seconds


-- 
The mind is not a vessel to be filled, but a fire to be lighted. - Plutarch
http://cinnamon.com/~bandy/  DoD#1005



--
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/


Re: [Mailman-Users] why is the queue runner taking 75 seconds per transaction?

2004-06-06 Thread Tokio Kikuchi
Check your MTA for timeout parameters. ;-)
Andrew Beals wrote:
I just installed mailman and I'm getting funny behavior in that it takes the 
queue runner 75 seconds per transaction to process.  This can't be right or a 
high-usercount mailing list wouldn't be practical.

What am I missing?
aTdHvAaNnKcSe
Andy
ps.  A sample from /usr/local/mailman/logs/smtp:
Jun 03 11:16:32 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.088 seconds
Jun 03 11:17:48 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.265 seconds
Jun 03 11:19:03 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.263 seconds
Jun 03 11:20:18 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.185 seconds
Jun 03 11:21:33 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.172 seconds
Jun 03 11:22:49 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.155 seconds
Jun 03 11:24:04 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.141 seconds
Jun 03 11:25:19 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.140 seconds
Jun 03 11:26:34 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.287 seconds
Jun 03 11:27:49 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.197 seconds
Jun 03 11:29:05 2004 (2657) [EMAIL PROTECTED] 
smtp
 for 1 recips, completed in 75.095 seconds


--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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/


Re: [Mailman-Users] why is the queue runner taking 75 seconds per transaction?

2004-06-06 Thread Andrew Beals
Aha!  It's because I have a IPv6 address for localhost in /etc/hosts and 
that's what's timing out.  [TCP timeout]


-- 
The mind is not a vessel to be filled, but a fire to be lighted. - Plutarch
http://cinnamon.com/~bandy/  DoD#1005



--
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/