[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 the meantime, I'm getting programs like mailman up and running. I've already replaced sendmail with exim, even getting it hooked into Solaris 10 smf control. Based on the previous discussion, I've replaced the stock python 2.4.4 on the box with a freshly compiled and installed 2.5.2 version. The configure script runs without error, as does the initial make. BTW, the install manual has an error: Page 4: % cd mailman-version % ./configure % make install The make install should be just make. Gotta make it before you can install it. :-) In any event, the following error occurs when trying to install: (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.5/distutils/dist.py:247: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /usr/local/src/mailman-2.1.11rc2/misc *** Error code 1 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 http://mail.python.org/pipermail/mailman-users/2008-June/062269.html and http://mail.python.org/pipermail/mailman-users/2008-June/062275.html. Is this the same stuff you pointed to before? If so, then I misread it. I didn't think it gave a compile error, but did something else wrong. I'll go back and read the previous e-mails about this. MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 scripts find the cc or gcc that you intend to use. Renaming the /usr/ucb/cc stub to cc.bsd will help, but Solaris 10 includes a version of gcc as well, which you may or may not want to use. If you want to use the Sun devsys, you'll have to force the configure scripts not to use gcc with command line arguments. Here is where I misunderstood. I thought by going to python 2.5.2, i.e., newer than 2.4.4, the Korean Codec problem would be resolved. It obviously wasn't. Didn't have to rename the BSD cc, as configure found gcc just fine. Now to go fix the codec problem. MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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. That is not my problem. To wit, here is the python greps out of the configure log: configure:1311: checking for --with-python configure:1330: checking for python configure:1348: found /usr/local/bin/python configure:1361: result: /usr/local/bin/python configure:1370: checking Python interpreter configure:1388: result: /usr/local/bin/python configure:1393: checking Python version configure:1434: checking that Python has a working distutils ac_cv_path_with_python=/usr/local/bin/python PYTHON='/usr/local/bin/python' with_python='/usr/local/bin/python' As can be seen, the local version was found in all cases. Take a look at the make output again: (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.5/distutils/dist.py:247: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /usr/local/src/mailman-2.1.11rc2/misc Notice that the correct python is being used. It isn't python that is bailing, it is gcc. This failure is NOT the same. MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 and compile the various mailman.po message catalogs into mailman.mo files. Almost all the Makefiles have null all: targets. The only ones that don't are those that run make in subdirectories and the ones in src/ and messages/, and those two run the all: target as part of the install: target. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 architecture independent directories... chmod o-r /usr/local/mailman/archives/private Creating architecture dependent directories... for f in mmsitepass newlist rmlist add_members list_members remove_members clone_member update arch sync_members check_db withlist check_perms find_member version config_list list_lists dumpdb cleanarch list_admins genaliases change_pw mailmanctl qrunner inject unshunt fix_url.py convert.py transcheck b4b5-archfix list_owners msgfmt.py show_qfiles discard rb-archfix reset_pw.py export.py; \ do \ .././install-sh -c -m 755 ../build/bin/$f /usr/local/mailman/bin; \ done for f in crontab.in; \ do \ .././install-sh -c -m 644 $f /usr/local/mailman/cron; \ done for f in checkdbs mailpasswds senddigests gate_news nightly_gzip bumpdigests disabled cull_bad_shunt; \ do \ .././install-sh -c -m 755 ../build/cron/$f /usr/local/mailman/cron; \ done for i in ./*.jpg ./*.png; \ do \ .././install-sh -c -m 644 $i /usr/local/mailman/icons; \ done for d in bin cron scripts tests; \ do \ dir=/usr/local/mailman/$d; \ .././install-sh -c -m 644 paths.py $dir; \ done .././install-sh -c -m 755 mailman /usr/local/mailman/scripts .././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.5/distutils/dist.py:247: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /usr/local/src/mailman-2.1.11rc2/misc *** Error code 1 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' Notice the complete lack of anything to do with python compiling. Again I started over and then did only a make: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make); \ done for d in Cgi Logging Archiver Handlers Bouncers Queue MTA Gui Commands; \ do \ (cd $d; make); \ done gcc -c -I. -DPREFIX=\/usr/local/mailman\ -DPYTHON=\/usr/local/bin/python\ -DHELPFUL -g -O2 -g -O2 -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DHAVE_SYSLOG=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VSNPRINTF=1 ./common.c gcc -c -I. -DPREFIX=\/usr/local/mailman\ -DPYTHON=\/usr/local/bin/python\ -DHELPFUL -g -O2 -g -O2 -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DHAVE_SYSLOG=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VSNPRINTF=1 ./vsnprintf.c gcc -DSCRIPT=\admindb\ -I. -DCGI_GROUP=\nobody\ -g -O2 -g -O2 -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DHAVE_SYSLOG=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VSNPRINTF=1 common.o vsnprintf.o -o admindb ./cgi-wrapper.c gcc -DSCRIPT=\admin\ -I. -DCGI_GROUP=\nobody\ -g -O2 -g -O2 -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DHAVE_SYSLOG=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VSNPRINTF=1 common.o vsnprintf.o -o admin
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 Sun installed python. That is not my problem. To wit, here is the python greps out of the configure log: configure:1311: checking for --with-python configure:1330: checking for python configure:1348: found /usr/local/bin/python configure:1361: result: /usr/local/bin/python configure:1370: checking Python interpreter configure:1388: result: /usr/local/bin/python configure:1393: checking Python version configure:1434: checking that Python has a working distutils ac_cv_path_with_python=/usr/local/bin/python PYTHON='/usr/local/bin/python' with_python='/usr/local/bin/python' As can be seen, the local version was found in all cases. Take a look at the make output again: (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.5/distutils/dist.py:247: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /usr/local/src/mailman-2.1.11rc2/misc Notice that the correct python is being used. It isn't python that is bailing, it is gcc. The Korean and Japanese codecs are installed by Python distutils using a setup.py built somewhere else. It doesn't get everything from configure. Your problem is the hangul.c file that is not compiling contains #include Python.h (and Python.h inturn includes a bunch of other stuff) gcc is not finding this header file. That is the underlying cause of the compile error. Yes, the error in your case is different, because in your case the compile is finding a working compiler, but the root problem is the same. 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. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 did: [...] The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' Note the list of subdirectories in for d in The error occurs in the 'misc' directory. The stuff that doesn't get done is in the 'src' and 'messages' directories that it never got to. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 mutually exclusive. Compilers do not use PATH for finding header files. MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 help. I tried changing the Python.h to Python.h. Didn't help. I tried adding the -I to the Korean directory Makefile CFLAGS. Didn't help. With the above Makefile change, I tried changing the Python.h to Python.h. Didn't help. Why are the actual gcc command lines not visible in the make output? I'm used to seeing the actual command lines so that debugging of a problem is made a little easier. Is there any way to not use the Korean/Japanese stuff and still get mailman to work? MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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, wiping out any local changes. Just how is someone supposed to fix this? MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 tarball, no matter what, wiping out any local changes. Just how is someone supposed to fix this? This is not new. I tried to warn you. http://www.google.com/search?q=site%3Amail.python.org+inurl%3Amailman+solaris+korean. I think Hank knows how to make it work, but I don't off hand. 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 in, so edit the misc/Makefile. Change PACKAGES= $(EMAILPKG) $(JACODECSPKG) $(KOCODECSPKG) to PACKAGES= $(EMAILPKG) -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Apache,
Mark responded: This is not new. I tried to warn you. http://www.google.com/search?q=site%3Amail.python.org+inurl%3Amailman+solaris+korean. 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 in, so edit the misc/Makefile. Change PACKAGES= $(EMAILPKG) $(JACODECSPKG) $(KOCODECSPKG) to PACKAGES= $(EMAILPKG) 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? MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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: Command failed for target `update' The update script exists in the mailman directory I am doing the make and in the /usr/local/mailman/bin directory. Just in case, because of all the issues, I cleaned out /usr/local/mailman and reran make install. No diff. Stills dies at the same location. MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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.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. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 target `update' The update script exists in the mailman directory I am doing the make and in the /usr/local/mailman/bin directory. Just in case, because of all the issues, I cleaned out /usr/local/mailman and reran make install. No diff. Stills dies at the same location. I think that's my fault. I just fixed it for Mailman 2.1.11. (I broke it for 2.1.11rc1.) The problem is the bin/update in the tarball is 'pre-configured' with #! /usr/bin/python If that isn't where your python is, it doesn't work. Fix the shebang line in bin/update in the installed tree and run it by hand. It is the very last step in 'make install', so then you're done. In fact, if this is a new installation with no existing lists, you're already done. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 is 'pre-configured' with #! /usr/bin/python If that isn't where your python is, it doesn't work. It isn't :-) In fact, if this is a new installation with no existing lists, you're already done. Yep new. OK, I'll consider it done and move on the in the installation process. MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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.
There are two {yes}{no}} lines in each section (warn and accept). exim
doesn't like that when doing the exim -bt test.
MB
--
e-mail: [EMAIL PROTECTED]/~\ The ASCII
[I've been to Earth. I know where it is. ] \ / Ribbon Campaign
[And I'm gonna take us there.Starbuck 3/25/07] X Against
Visit - URL: http://vidiot.com/ / \ HTML Email
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
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 http://www.exim.org/howto/mailman21.html which tends
to be more complete than the Exim section of the installation manual.
Also see http://wiki.list.org/x/OYA9.
--
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Apache,
Mark Sapiro responded: I suggest you see http://www.exim.org/howto/mailman21.html 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 correct? MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 list is bigger than your list :-) :-) :-) MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] newlist list creation error
To wit: ./bin/newlist mailman Traceback (most recent call last): File ./bin/newlist, line 99, in module from Mailman import mm_cfg File /usr/local/mailman/Mailman/mm_cfg.py, line 45, in module DEFAULT_URL_HOST = mrvideo.vidiot.com NameError: name 'mrvideo' is 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. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[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. They all come to me as uncaught bounces with the advice: The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s). The mention of being unable to extract the address seems strange, but it still doesn't give me the reason for the bounce. I changed my config by activating content filtering with the default settings, then asked her to re-send. It made no difference. I know that this lady subscribes to several mailing lists hosted by RootsWeb.com, but I believe that Rootsweb uses a different mailer. Two other subscriber have posted successfully, one using hotmail. The other uses Yahoo Webmail. I am probably not giving enough info. Please let me know what you need. Doug. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] newlist list creation error
Vidiot wrote: ./bin/newlist mailman Traceback (most recent call last): File ./bin/newlist, line 99, in module from Mailman import mm_cfg File /usr/local/mailman/Mailman/mm_cfg.py, line 45, in module DEFAULT_URL_HOST = mrvideo.vidiot.com NameError: name 'mrvideo' is not defined OK, where is it supposed to be defined? It's not. It's a literal DEFAULT_URL_HOST = 'mrvideo.vidiot.com' I really want it to be just vidiot.com. But that didn't work either, with the error replacing mrvideo with vidiot. Then DEFAULT_URL_HOST = 'vidiot.com' -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[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.com
domainlist local_domains = vidiot.com
The 2nd was already in the configure file.
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.
But I have the following:
begin routers
mailman_router:
driver = accept
domains = +mm_domains
require_files = MM_LISTCHK
[...]
I get the following error when I try and test:
/usr/exim/bin/exim -bt testlist-users
2008-06-29 20:53:47 Exim configuration error in line 563 of /usr/exim/configure:
option setting expected: {eq{$sender_host_address}{::1}}}{yes}{no}}
It didn't complain about this line:
condition = ${if or{{eq{$sender_host_address}{127.0.0.1}}
So, I'm guessing it isn't complaining about $sender_host_address, instead
it is complaining about the {::1} part.
My complete configure file is below, less comments and blank lines. I'd
say about half of the configuration is mailman related :-)
MB
--
e-mail: [EMAIL PROTECTED]/~\ The ASCII
[I've been to Earth. I know where it is. ] \ / Ribbon Campaign
[And I'm gonna take us there.Starbuck 3/25/07] X Against
Visit - URL: http://vidiot.com/ / \ HTML Email
MM_HOME=/usr/local/mailman
MM_WRAP=MM_HOME/mail/mailman
MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck
MM_USER=mailman
MM_GROUP=mailman
domainlist mm_domains=vidiot.com
domainlist local_domains = vidiot.com
domainlist relay_to_domains =
hostlist relay_from_hosts = 127.0.0.1 : mrvideo.vidiot.com
acl_smtp_rcpt = acl_check_rcpt
acl_smtp_data = acl_check_data
never_users = root
host_lookup = *
rfc1413_hosts = *
rfc1413_query_timeout = 5s
ignore_bounce_errors_after = 2d
timeout_frozen_after = 7d
begin acl
acl_check_rcpt:
accept hosts = :
accept hosts = 127.0.0.1
denymessage = Restricted characters in address
domains = +local_domains
local_parts = ^[.] : [EMAIL PROTECTED]/|]
denymessage = Restricted characters in address
domains = !+local_domains
local_parts = ^[./|] : [EMAIL PROTECTED] : ^.*/\\.\\./
accept local_parts = postmaster
domains = +local_domains
endpass
message = unknown user
verify= recipient
require verify= sender
accept hosts = +relay_from_hosts
control = submission
accept authenticated = *
control = submission
require message = relay not permitted
domains = +local_domains : +relay_to_domains
require verify = recipient
warn message = X-WhitelistedRCPT-nohdrfromcallback: Yes
condition= \
${if and {{match{$local_part}{(.*)-bounces\+.*}} \
{exists {MM_HOME/lists/$1/config.pck}}} \
{yes}{no}}
deny message = Recipient never sends mail so cannot cause bounces
senders = :
domains = +mm_domains
condition = ${if exists{MM_LISTCHK} {yes}{no}}
deny message = Recipient never sends mail so cannot cause bounces
senders = :
domains = +mm_domains
local_parts = \N^.*-(admin|join|leave|owner|request)$\N
deny message = Recipient never sends mail so cannot cause bounces
senders = :
domains = +mm_domains
local_parts = \N^.*-(subscribe|unsubscribe)$\N
accept condition= \
${if and {{match{$local_part}{(.*)-bounces\+.*}} \
{exists {MM_HOME/lists/$1/config.pck}}} \
{yes}{no}}
deny !local_parts = *-bounces : *-bounces+*
!verify = sender/callout=30s,defer_ok
accept
acl_check_data:
deny !condition = $header_X-WhitelistedRCPT-nohdrfromcallback:
!verify = header_sender/callout=90s
accept
begin routers
mailman_router:
driver = accept
domains = +mm_domains
require_files = MM_LISTCHK
local_part_suffix_optional
local_part_suffix = -admin : \
-bounces : -bounces+* : \
-confirm : -confirm+* : \
-join : -leave : \
-owner : -request : \
-subscribe : -unsubscribe
transport = mailman_transport
mailman_verp_router:
driver = dnslookup
condition = ${if or{{eq{$sender_host_address}{127.0.0.1}}
{eq{$sender_host_address}{::1}}}{yes}{no}}
domains = !+local_domains:!+mm_domains
ignore_target_hosts = ; 0.0.0.0; \
64.94.110.11; \
127.0.0.0/8; \
::1/128;fe80::/10;fe \
c0::/10;ff00::/8
senders = [EMAIL PROTECTED]
transport =
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] instead of [EMAIL PROTECTED] This probably has something to do with http://wiki.list.org/x/RoA9. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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.
http://www.list.org/mailman-install/node17.html
[...]
I get the following error when I try and test:
/usr/exim/bin/exim -bt testlist-users
2008-06-29 20:53:47 Exim configuration error in line 563 of
/usr/exim/configure:
option setting expected: {eq{$sender_host_address}{::1}}}{yes}{no}}
It didn't complain about this line:
condition = ${if or{{eq{$sender_host_address}{127.0.0.1}}
So, I'm guessing it isn't complaining about $sender_host_address, instead
it is complaining about the {::1} part.
[...]
condition = ${if or{{eq{$sender_host_address}{127.0.0.1}}
{eq{$sender_host_address}{::1}}}{yes}{no}}
I'm not sure what it's complaining about, but were getting a bit off
topic for Mailman. That said, unless you're actually using IPv6, try
replacing the above with
condition = ${if {eq{$sender_host_address}{127.0.0.1}}{yes}{no}}
--
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
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 setting the values. By habit, I just naturally leave off the quotes (unless I know I need then for shell sustitution reasons). 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 inclusion. MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 bounces with the advice: Because she is posting to [EMAIL PROTECTED] instead of [EMAIL PROTECTED] This probably has something to do with http://wiki.list.org/x/RoA9. 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? Doug. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 http://wiki.list.org/x/RoA9. 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 what LookOut .. er.. outlook does when she clicks reply. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 inclusion. 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 manifest for my MTA from http://cuddletech.com/opensolaris/smf/postfix.xml There is also an archive of smf examples here: http://opensolaris.org/os/community/smf/manifests/ HTH - Tim -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 manifest for my MTA from http://cuddletech.com/opensolaris/smf/postfix.xml There is a manifest that I got off the net that was used to place exim under smf. I was just going to modify that one. There is also an archive of smf examples here: http://opensolaris.org/os/community/smf/manifests/ If I can't get the exim one to work, I'll take a look. Thanks for the pointer. MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
