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

Re: [Mailman-Users] Apache,

On Monday 30 June 2008 2:55:08 pm Brad Knowles wrote: > On 6/29/08, Vidiot wrote: > > 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. > >

Re: [Mailman-Users] Subscriber bounced

On Monday 30 June 2008 3:14:17 pm Vidiot wrote: > >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 (the

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

After creation of the newlist mailman, I was told that the owner (me) was being sent e-mail to inform that owner. The e-mail never showed up. So, as a test, I did the simple e-mail to myself by talking directly to exim to send a test mail, just like I did when I initially installed exim. That e-

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] Apache,

On 6/29/08, Vidiot wrote: 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. We really don't want to get into this argument again. -- Brad Kn

Re: [Mailman-Users] newlist list creation error

Vidiot wrote: When I get to the step about getting mailman to start at boot time, I'll see if I can get it wedged into the Solaris 10 services system. The stuff I got to install exim should be modifiable to work with mailman. If I do manage to get it to work, I'll submit the files for future inc

Re: [Mailman-Users] Subscriber bounced

Doug Laidlaw wrote: >On Monday 30 June 2008 1:05:43 pm Mark Sapiro wrote: >> >> This probably has something to do with . > >Thank you. You were quite right. But the referenced link seems to deal with >what she sees on her screen, not with what she sends? Who knows

Re: [Mailman-Users] Subscriber bounced

On Monday 30 June 2008 1:05:43 pm Mark Sapiro wrote: > Doug Laidlaw wrote: > >One of my subscribers is using Microsoft Office Outlook. Her X-Mailer > > line is > > > >X-Mailer: Microsoft Office Outlook 11 > > > >Her messages come in a text par and a HTML part. They all come to me as > >uncaught b

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

Re: [Mailman-Users] exim testing error

Vidiot wrote: >Mark Sapiro responded: > [...] >>and the reference to >> >>domains = +mm_domains >> >>in the router definition. This is alluded to much more subtly in sec >>6.2.1 of the manual. > >Section 6.2.1 doesn't exist. [...] >I get th

Re: [Mailman-Users] Subscriber bounced

Doug Laidlaw wrote: > >One of my subscribers is using Microsoft Office Outlook. Her X-Mailer line is > >X-Mailer: Microsoft Office Outlook 11 > >Her messages come in a text par and a HTML part. They all come to me as >uncaught bounces with the advice: Because she is posting to [EMAIL PROTECTED

[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

Re: [Mailman-Users] newlist list creation error

Vidiot wrote: > >./bin/newlist mailman >Traceback (most recent call last): > File "./bin/newlist", line 99, in >from Mailman import mm_cfg > File "/usr/local/mailman/Mailman/mm_cfg.py", line 45, in >DEFAULT_URL_HOST = mrvideo.vidiot.com >NameError: name 'mrvideo' is not defined > >OK, w

[Mailman-Users] Subscriber bounced

I am running a genealogy web site. My host uses CPanel, and with it came Mailman. I am a subscriber to many lists using Mailman. One of my subscribers is using Microsoft Office Outlook. Her X-Mailer line is X-Mailer: Microsoft Office Outlook 11 Her messages come in a text par and a HTML part

[Mailman-Users] newlist list creation error

To wit: ./bin/newlist mailman Traceback (most recent call last): File "./bin/newlist", line 99, in from Mailman import mm_cfg File "/usr/local/mailman/Mailman/mm_cfg.py", line 45, in DEFAULT_URL_HOST = mrvideo.vidiot.com NameError: name 'mrvideo' is not defined OK, where is it suppo

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,

Vidiot wrote: > >It would be nice though if the two documents matched in their macro-naming, >to help reduce confusion and possibly misconfiguration. It's been on my list for a long time. Obviously, I still haven't gotten to it. -- Mark Sapiro <[EMAIL PROTECTED]>The highway is for gambl

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,

Vidiot wrote: > >Before you go too far, look at the exim STMP callback code example. >There are two {yes}{no}} lines in each section (warn and accept). exim >doesn't like that when doing the exim -bt test. Thanks. I've fixed that and also a couple of omissions in the router. I suggest you see

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,

Vidiot wrote: > >I'm confused. I installed mailman-2.1.11rc2.tgz. Mailman 2.1.11 isn't >available yet? 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. -- Mark Sapiro <[E

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,

Vidiot wrote: > >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: Command failed for t

Re: [Mailman-Users] Apache,

Vidiot wrote: > >That is what I thought I read, which is why I changed to 2.5.2, thinking >that mailman would install accordingly. Bad thinking on my part. > >Any chance this will be incorporated into future mailman configure detection >runs so that this will work cleanly? Probably not in the 2.

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,

Vidiot wrote: >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 t

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,

Vidiot wrote: > >The finding of header files and the PATH environment are mutually exclusive. >Compilers do not use PATH for finding header files. 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. -- Mark Sapiro <

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

Vidiot wrote: >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

Re: [Mailman-Users] Apache,

Vidiot wrote: >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

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] make install failure

Vidiot wrote: >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. What Python stuff didn't it do that needed to be done. All a straight 'make' does is compile all the wrappers a

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 >

Re: [Mailman-Users] make install failure

Vidiot wrote: > >The configure script runs without error, as does the initial make. BTW, >the install manual has an error: > > Page 4: % cd mailman- > % ./configure > % make install > >The "make install" should be just "make". Gotta make it before you can >instal

[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