Re: [Mailman-Users] Python process size grows 30x in 8 hours (memory

>I'm having a hard time finding the release notes for 2.1.11 - can you please >provide a link? >(I want to see where it details any memory leak fixes since 2.1.9) >Fletcher Cocquyt >Senior Systems Administrator >Information Resources and Technology (IRT) >Stanford University School of Medicine The

Re: [Mailman-Users] Python process size grows 30x in 8 hours (memory

>Solaris 10 x86 >Python 2.5.2 >Mailman 2.1.9 (8 Incoming queue runners - the leak rate increases with this) >SpamAssassin 3.2.5 > >At this point I am looking for ways to isolate the suspected memory leak - I >am looking at using dtrace: http://blogs.sun.com/sanjeevb/date/200506 > >Any other tips ap

[Mailman-Users] Things are looking up

After the main mailman list was create, and getting some sleep, I reran the exim delivery tests a little bit ago. The result of two of them are as follows: /usr/exim/bin/exim -bt mailman [EMAIL PROTECTED] <-- [EMAIL PROTECTED] router = mailman_router, transport = mailman_transport /usr/exim

Re: [Mailman-Users] exim testing error

Mark responded: >What you said was "I'm using the printed copy, placed into a binder. >Used the text version to cut-n-paste from.", and I concluded you meant >the .txt file was in your binder. True. I failed to indicate the source of my printout. >I never noticed this before as I don't use the

Re: [Mailman-Users] newlist created - no e-mail

Mark responded: >It queues it in qfiles/virgin. From there, Mailman's qrunners have to >be running to process it further. Did you start Mailman >(bin/mailmanctl start)? Not yet. >Actually, I see this is a catch22. You can't start Mailman until after >you create the 'mailman' list, but now that

Re: [Mailman-Users] Apache,

>I do it all the time. I am using Kmail, and can configure it to reply to the >list by default. But then I get caught when something I don't want to go to >the list, goes there. It is a no-win situation. >Doug. Don't know what I am going to use to read e-mail on the Solaris 10 box. Whatever

[Mailman-Users] newlist created - no e-mail

-mail showed up in /var/mail. Exim reported that [EMAIL PROTECTED] was really a local user, me (the /etc/aliases file has an entry for vidiot to go to brown), and that it was deliverd locally. Don't know what newlist does when it sends e-mail, but it didn't work. MB -- e-mail: [EMAIL

Re: [Mailman-Users] newlist list creation error

Tim responded: >Do some searching before you sit down to write a Solaris smf (service >management facility) >manifest from scratch. You will find other examples out there. I got my >mailman manifest from >this weblog entry: http://whacked.net/2005/08/14/more-work-on-grommit and a >postfix m

Re: [Mailman-Users] Subscriber bounced

>Who knows what LookOut .. er.. outlook does when she clicks reply. >Mark Sapiro <[EMAIL PROTECTED]>The highway is for gamblers, And to think that the company I work for is converting to Outlook. Many have. Our site hasn't yet (there are thousands of employees, world wide). MB -- e-mai

Re: [Mailman-Users] newlist list creation error

Mark Sapiro responded: >It's not. It's a literal Sorry, never noticed the quote characters. Even so, not being a python user (until now), the use of quotes or doublequotes can usually be eliminated when setting variables in shell scripts. That would have been the mode I would have been in when

[Mailman-Users] exim testing error

Mark Sapiro responded: >Also note in the howto, the following > > # Domains that your lists are in - colon separated list > # you may wish to add these into local_domains as well > domainlist mm_domains=list.example.com I have the following set in my configure: domainlist mm_domains=vidiot.co

[Mailman-Users] newlist list creation error

s not defined OK, where is it supposed to be defined? I really want it to be just vidiot.com. But that didn't work either, with the error replacing mrvideo with vidiot. MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is.

Re: [Mailman-Users] Apache,

Mark Sapiro: Crap, I think I sent the last response just to you and not you and the list. I tend to forget to group reply. I personally prefer mail lists to respond to the list e-mail address and not the poster. >It's been on my list for a long time. Obviously, I still haven't gotten >to it. My

Re: [Mailman-Users] Apache,

Confusion no longer reigns. Silly me, not thinking about the variables being expanded later on in the exim config file. It would be nice though if the two documents matched in their macro-naming, to help reduce confusion and possibly misconfiguration. MB -- e-mail: [EMAIL PROTECTED]

Re: [Mailman-Users] Apache,

Mark Sapiro responded: >I suggest you see which tends >to be more complete than the Exim section of the installation manual. OK, confusion reigns. The installation manual says MAILMAN_HOME, etc, while the web page says MM_HOME, etc. Which one is correc

Re: [Mailman-Users] Apache,

Mark Sapiro responded: >No. 2.1.11rc2 is the latest released, but I'm in the process of >packaging the final 2.1.11 for release tomorrow. > >When I said I just fixed it for 2.1.11, I meant the final. I kinda wondered about that. Before you go too far, look at the exim STMP callback code example.

Re: [Mailman-Users] Apache,

Mark Sapiro responded: >I think that's my fault. I just fixed it for Mailman 2.1.11. (I broke >it for 2.1.11rc1.) Whew! It wasn't something I did this time. :-) I'm confused. I installed mailman-2.1.11rc2.tgz. Mailman 2.1.11 isn't available yet? >The problem is the bin/update in the tarball

Re: [Mailman-Users] Apache,

Mark Sapiro responded: >Probably not in the 2.1 branch. 3.0 will require Python 2.5 minimum and >won't try to install these codecs at all. > >I'll try to do something with configure for Mailman 2.2. Thanks, it will be appreciated. MB -- e-mail: [EMAIL PROTECTED]/

Re: [Mailman-Users] Apache,

Mark responded: >PACKAGES= $(EMAILPKG) OK, did that. Gets past that now. But: [...] Compiling /usr/local/mailman/Mailman/versions.py ... sh: bin/update: not found *** Error code 1 The following command caused the error: (cd /usr/local/mailman ; test -n "" || bin/update) make: Fatal error: Comm

Re: [Mailman-Users] Apache,

Mark responded: >This is not new. I tried to warn you. >. Yep, you did :-) >If you are going to be running Mailman with Python 2.5+, you don't need >the Japanese and Korean codecs anyway because they're built i

Re: [Mailman-Users] Apache,

Mark responded: >The Korean and Japanese codecs are installed by Python distutils using >a setup.py built somewhere else. It doesn't get everything from >configure. Crap, all of the modifications that I tried doing were worthless, since the damn thing keeps installing the tarball, no matter what,

Re: [Mailman-Users] Apache,

Mark responded: >I understand that. It is more subtle than that. It has to do with the >Python version that runs the Setup.py for the Korean codecs. It is getting me really pissed off. As far as I can tell, it is running the 2.5.2 version of Python. I tried --includedir with configure. Didn't

Re: [Mailman-Users] Apache,

Mark posted: >Your problem is the hangul.c file that is not compiling contains > >#include "Python.h" > >I confess, I don't fully understand the details, but Hank appears to >and he says the issue is with the order of things on your PATH. The finding of header files and the PATH environment are m

Re: [Mailman-Users] make install failure

Mark posted: >What Python stuff didn't it do that needed to be done. All a straight >'make' does is compile all the wrappers and compile the various >mailman.po message catalogs into mailman.mo files. I wiped out the directory and started over. Here is what the make install did: Creating archi

Re: [Mailman-Users] Apache,

I'm not sure that everyone looked at the posting that I did very clearly. The error I posted is totally different that the error discussed in this posting: http://mail.python.org/pipermail/mailman-users/2007-February/055640.html That was a result of the install "finding" the Sun installed python.

Re: [Mailman-Users] Apache,

Hank posted: >In particular, make sure the Mailman configure script finds your local >Python build, not the (older) version included in the Solaris >distribution. This is the root of the "Korean Codec" problem that >Mark provided a google search link to. Also make sure that the configure >scrip

Re: [Mailman-Users] make install failure

Mark Sapiro: >'make install' is sufficient. It will do the necessary 'make' actions. It didn't for me. It didn't do any of the python stuff until I ran just make. >See > >and >

[Mailman-Users] make install failure

OK, the Solaris 10 box is operational, in that root is the only user and I'm getting things up and running. While my user account exists, none of my personal stuff is there yet, as it is in a state of flux. Once I bring the system on line, then I copy over all the home directory files, etc. In t

Re: [Mailman-Users] Apache,

Hank posted: >I gave the location of the actual aliases file in /etc/mail for >Solaris. /etc/aliases is provided, but is a symlink to the file in >/etc/mail. It is the symlink that I always use, same deal for the hosts file. :-) >I will note, and think that Brad and Mark will agree, that given

Re: [Mailman-Users] Apache,

>The only "gimmick" specific to running Mailman with sendmail is to >include the alias pipes for Mailman in /etc/mail/aliases (and run >newaliases after changing the file). Thanks for the info, but the last time I looked, aliases was in /etc, not /etc/mail. In any event, thanks for the info. M

Re: [Mailman-Users] Apache,

>The CGI and MTA interface wrappers are written in C, but they're >really really simple (as anything security-critical should be). > >It's not going to make any difference what they're compiled with. I'll install the GNU C compiler tools. MB -- e-mail: [EMAIL PROTECTED]

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as

Brad Knowles responded: >Following our standard installation procedure works just fine for >Solaris 10. I've done it. Thanks, great news. >Moreover, the Mailman code is written in Python, so there shouldn't >be any need to compile anything with any C compiler. D'oh! >If there was anything t

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

>The results of > >may interest you. >Mark Sapiro <[EMAIL PROTECTED]>The highway is for gamblers, Thanks, so noted. The Solaris 10 installed. The proc temp stayed low enough to not get Solaris mad and want t

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

>That's because you're installing a RedHat package, and the RPM already >installed /etc/httpd/conf.d/mailman.conf which contains that >ScriptAlias. Oh crap. Another reason I am going toward Solaris 10. The last thing I'd do is stick a web server confing file in another directory and include it.

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

>Why do you think that? ScriptAlias /cgi-bin/ "/home/httpd/cgi-bin/" ScriptAlias /mailman/ "/usr/lib/mailman/cgi-bin" mrvideo.vidiot.com.ZROOT <406> /etc/init.d/httpd restart Stopping httpd:[ OK ] Starting httpd: [Wed Jun 25 18:59:28 2008] [war

[Mailman-Users] David Champion Sendmail files not available

FedoraCore7. Mailman installed with FC7. As a result, the David Champion files listed on page 16 of the Installation Manual do not exist on my system. Is there a location from which they can be downloaded? I have no idea if the stuff in his guides has been done on this system until I actually ve

[Mailman-Users] Apache, mailman and ScriptAlias - not as documented

I've looked at the installation page over at the Wiki and there is nothing regarding the problem I've run up against. See page 6 of the Installation Manual (pdf). It states the following should be added: ScriptAlias /mailman/ $prefix/cgi-bin/ I already have ScriptAlias defined: