[Mailman-Developers] Using the correct host
I've been trying to set up a list behind my firewall on the local network. The machine hosting mailman uses 192.168.0.2 as a static IP, but the world sees me as ernest.isa-geek.org, the DNS entry I got through dyndns.org. If you try to subscribe to the list I created, the subscribe button sends the request to 192.168.0.2 instead of ernest.isa-geek.org. While that works fine from here, people out there aren't having any luck. How do I make the subscribe button use the dns name vs the IP? You can see what I'm talking about by going here and trying to subscribe to the list: http://www.ernest.isa-geek.org/mailman/listinfo/deltaflyers I just noticed that the listinfo page says that there currently are no publicly-advertised Mailman mailing lists on www.ernest.isa-geek.org. How do I make the list publicly-advertised? -- Because I can http://www.ernest.isa-geek.org/ ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] Browser stop button (revisited from 2.0.5??)
I have a problem with the Mailman servers I run related to an issue which was discussed during the 2.0.4 to 2.0.5 transition some time ago. The problem relates to people who click the stop button on their browser while Mailman is doing its stuff. If the person in question is the list admin, making changes to the list, then Mailman just aborts without saving the list changes. Like the posters in the original discussion on this list some 2 years ago I can live with these semantics, almost The problem is that Mailman always returns the content of the page, which says that everything has been done, before it saves the list. For example, see lines 236-238 of admindb.py in 2.1: print doc.Format() # Commit all changes mlist.Save() The problem with this is that mlist.Save() is taking quite a while for large lists so I have to educate my list owners to be really patient and wait for the browser to finish - with very little visual cue that it is doing anything. (OK, animated wavy windows, spinning worlds, sparkly N's apart) What would make much more sense to me (and my users) is if these two lines were done the other way around. At least the users would then understand that the system was doing something and shouldn't be interupted because they would be looking at a blank browser window. They wouldn't be told that their changes had been successfully carried out until they actually had! What do you all think? Can you see any problems with switching these two lines (similarly in the other CGI handlers)? Steve Lay ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] modifying mailman's source
All, I need to call an external script whenever a mailing list's membership changes. I'd like to pass the name of the modified list to my script. I've spent some time studying the Mailman source, and I think the file I need to modify is ~mailman/Mailman/MailList.py. I think the functions that need to be modified are functions ApprovedAddMember, ApprovedDeleteMember, and ChangeMemberAddress. Here are the two lines that I'd like to add to the above functions: metacmd= '~mailman/scripts/my-script.pl' + ' ' + self os.system(metacmd) Does this look correct? I'm using Mailman 2.1.2 in Linux. BTW, my external script is a solution for automatically maintaining nested lists, written in Perl. I'll share it with the world once I get it working. Thanks, Wes -- Wes Perdue IT Manager, Greenfield Networks ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] gpg again
On Sun, 2003-05-18 at 07:15, SteveC wrote: Please don't flame if I'm out of place, I'll go rtfm/etc but I googled for mailman+gpg and it came up with a bunch of old stuff on this list. from what I can see periodically someone would come along and say 'we want gpg support' but things don't happen. So, if anyone has a second I'd like to know why? This would have to be a Mailman 3 feature. -Barry ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] semantic errorinmailmanctlline255(Mailman2.1.2)
On Tue, 2003-05-20 at 04:23, Oliver Egginger wrote:
But further particulars:
when I comment out the line 126 in mailmanctl the error messages go away.
Here is the line
LogStdErr('error', 'mailmanctl', manual_reprime=0)
I execute this function call with python -v on command line via:
import paths
from Mailman.Logging.Utils import LogStdErr
LogStdErr('error', 'mailmanctl', manual_reprime=0)
and receive:
Mailman.Logging.MultiLogger.MultiLogger instance at 0x80fe374
without error messages.
So it seems to work.
But when I terminate the python session by typing CTRL-D (end of input)
I receive the same error messages as I get from mailmanctl during the start
and stop phase.
I have trailed them at the end of this message.
Also it seems as if the error messages came from
Mailman.Logging.Utils import LogStdErr.
Maybe by destroying the objects which gets created by
LogStdErr('error', 'mailmanctl', manual_reprime=0).
The function seems to work, none the less the shutdown of the corresponding
objects seems to fail.
But I'am no python expert.
To be honest, I'm at a loss. It seems to me like a Python problem, but
it's definitely not something I see or can reproduce. The only thing I
can recommend is to try to upgrade to Python 2.2.3 and see if that helps
at all. Other than that...?
-Barry
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] Mass subscription failed / R-sig-QAmailing list
On Sat, 2003-05-17 at 10:53, Martin Maechler wrote: I just tried again (needs a tiny bit longer when working from home), and it didn't work again -- when I tried to upload a file of new member addresses. However when I tried (the old way of) pasting the new members e-mails in to the web-interface form -- it did work. I just tested this with three names in my upload file and it worked fine for both subscribing and unsubscribing. This is with Mailman 2.1.2+ (cvs) and Python 2.2.3. How big was the upload file? Perhaps there's some size limit on your uploads? Then again, if the subscribe page tells you they were successfully subscribed, and the logs/subscribe file shows you what you'd expect, I have no idea what could be going on. You sure you didn't click Invite? -Barry ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] Is this a bug? (was semantic error...)
On Wed, 2003-05-28 at 13:27, Oliver Egginger wrote: meanwhile I set up a debian woody with MM 2.1.2, but I receive the same error messaes like under Mandrake 9.1. BTW, I use RH9 and 7.3, but I really don't think it makes any difference. What /might/ make a difference is using the distro's Python or installing Python from source. Python 2.2.3 was just released; maybe a from-source installation will solve the problem. Are these error messages normal? Will they only appear under Mandrake 9.1 and debian woody? Can they cause any harm? Can I comment out line 126? Which linux distribution I should use for Mailman 2.1.2? I think you can actually ignore these messages. They probably won't hurt anything. -Barry ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [Mailman-FR] Patchs pour la traduction FR demailman.
Hello, here are some patches for the french translation of mailman thanks to Evelyne Chatelain from the ATLF (atlf.org). Voici quelques patchs, issus des remarques d'un membre de Globenet, merci à lui ... 1. Patch pour résoudre l'impossibilité d'accéder à des archives privées de mailman. Le fichier private.html des templates fr est incorrect, apparemment à cause d'un probleme de balise en minuscule ou de balise mal fermées. J'ai repris le template original. 2. Patch du .po pour corriger l'horrible Le archive en cours n'est disponible que pour les abonnés :) mailman.po.patch Description: Binary data ___ Mailman-FR mailing list [EMAIL PROTECTED] http://listes.rezo.net/mailman/listinfo/mailman-fr ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] Default link colors
I tryed change the default page and link colors by adding relevant fields in Default.py to mm_cfg.py. Changing all of the directives worked except for WEB_LINK_COLOR which did not result in a change. I found the offending error in htmlformat.py line 326. It should read: 'link' when it reads 'alink' Changed to 'link' and default web links now change. Mailman version 2.1.2 David Blomquist Principal, Tentra IT Solutions www.tentra.com ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] PROBLEM with Administrative Requests
On Sat, 2003-05-17 at 00:12, Kory Wheatley wrote: I've sent this email twice and no one has responded to this problem, I would really appreciate a response. I receive this below error when I go into the Administrative Interface and check Preserve messsages for the site administrator and then I check the discard option. Once I click submit this is what I receive below. BUG in Mailman version 2.1.1 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File /home/mailman/scripts/driver, line 87, in run_main main() File /home/mailman/Mailman/Cgi/admindb.py, line 163, in main process_form(mlist, doc, cgidata) File /home/mailman/Mailman/Cgi/admindb.py, line 681, in process_form forward, forwardaddr) File /home/mailman/Mailman/ListAdmin.py, line 184, in HandleRequest forward, addr) File /home/mailman/Mailman/ListAdmin.py, line 262, in __handlepost msg = cPickle.load(fp) ValueError: could not convert string to float Hmm, I just tried this under MM 2.1.2+ (cvs) and Python 2.2.3 and it works okay for me. What version of Python are you using? -Barry ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
