Mailman 3 April 2003 - Mailman-Users

private vs. public archives (was hi)
by CARTER Anthony April 30, 2003

April 30, 2003

just reposting with a decent header...:) message below... Anthony ---------- Forwarded Message ---------- Subject: [Mailman-Users] hi Date: Wednesday 30 April 2003 16:57 From: CARTER Anthony <a.carter(a)cordis.lu> To: mailman-users(a)python.org we just changed our archives from public into private, but now we can't browse into the archives... This may be normal, or may not...Can you confirm what changine from public to private does, and what am I suppose to get now under /pipermail/mailinglistname? And if not here, which path is it to the new one! Anthony ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)python.org 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/ This message was sent to: a.carter(a)cordis.lu Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/a.carter%40cordis.lu -------------------------------------------------------

1 0

Mailman and Xmail
by Toby Reiter April 30, 2003

April 30, 2003

To all, I'd like to apologize upfront because I'm a completely newbie with this and will be presumably be asking a lot of questions over the next couple of days. Ok, so I'm trying to configure using MailMan with Xmail. I image that someone has done this before somewhere, so I would really prefer not to re-invent the wheel here. As much as possible, I'm going to try and limit the amount of Xmail specific issues I raise here, since this isn't the list for that. Issue #1: I'm trying to set up email to be directed to email (the way it normally would using aliases). I've pretty much figured out how this might work from the Xmail side. But I'm having trouble while invoking the wrapper. That is, I'm not getting any response, feedback, etc that something is working (i.e. no emails, no changes to the log files, nada). I guess one question might be: is /usr/local/mailman/mail/mailman the proper way to invoke the wrapper? If not, what is? I know how one might do this for Sendmail, but not for Xmail. The command line I'm trying currently, which doesn't work, is: $ cat messagefile | /usr/local/mailman/mail/mailman action list where messagefile is an email message, action is a specific action (i.e. subscribe) and list is a specific list. Issue #2: I know the big thing about mailman is that it has a great web interface, but we'd prefer for our users to use email commands, or a web interface that we would build (which would actually simply send email commands on to Mailman). We also would prefer not to run a web server on our mail server or create an NFS volume link on our currently Windows-based web server. Are there significant issues with not enabling the web aspects of Mailman? Is it possible to hide all references to the web interface from the administrative emails that are sent (i.e. subscriptions, unsubscriptions, etc). Ok, that's it for now. If people have experience with both 1 & 2 meaning that we shouldn't use Mailman, what suggestions do people have? From my research, Mailman seems to be the most robust open source (or even non-open source) mailing list solution. Thanks in advance for your help, Toby -- Toby Reiter mailto:toby@breezing.com Breezing Internet Communications http://www.breezing.com 1106 West Main St phone:434.295.2050 Charlottesville, VA 22903 fax:603.843.6931

2 1

RE: [Mailman-Users] Mailman/htdig problem
by Timothy Arnold April 30, 2003

April 30, 2003

Hi Richard, I have found the source of the problem. Htsearch! It worked for me because I had set my environmental variables for LD_LIBRARY_PATH to the correct location but when I tried it as nobody, surprise surprise it didn't work. I have altered the system environmental variables and all is working. I am very sorry for wasting your time. Regards, Timothy. -----Original Message----- From: Richard Barrett [mailto:R.Barrett@ftel.co.uk] Sent: 30 April 2003 15:48 To: Timothy Arnold Cc: mailman-users(a)python.org Subject: RE: [Mailman-Users] Mailman/htdig problem At 14:06 30/04/2003, Timothy Arnold wrote: >Hi Richard, > >Thanks for this. I followed the instructions detailed in Operational >Information in the install notes and it now had created the indicies. >However, mmsearch still fails when I try to conduct a search. > >Mmsearch reports: > >Htdgi Archives Access Failure > >Search failed -12- > >The messages that I reported last time are still being reported in the >syslog. Any ideas what -12- means? Further to my earlier suggestions, you can try running htsearch from the command line and seeing how it responds. Try the following command: <path-to-htsearch> -c $prefix/archives/htdig/<listname>.conf answer the prompt for words with some words to seach for answer the format as short What happens? If all is well you should get back a HTTP response Content-type header of text/html, followed by a bunch of HTML, this being the search results. In total, if my earlier suggestion of the test script returns the correct results, and running htsearch from the command line returns the correct results, then you should not have a problem. Let us hope we do not end up with that contradiction to deal with. >Thanks, >Tim. > >-----Original Message----- >From: Richard Barrett [mailto:R.Barrett@ftel.co.uk] >Sent: 30 April 2003 13:51 >To: Timothy Arnold; mailman-users(a)python.org >Subject: Re: [Mailman-Users] Mailman/htdig problem > > >At 11:18 30/04/2003, Timothy Arnold wrote: > >Hiya, > > > >I have recently installed mailman 2.1.2 with the relevent htdig > >patches and I still cannot get it to work. > > > >For a given list, the search box is displayed and the configuration > >file for the list is generated but the search funtionality doesn't > >work > >- I look in the error log and I find > > > >Apr 30 10:56:39 2003 (12488) htsearch for list: test5, existatus: 1 > >Apr 30 10:56:39 2003 (12488) htsearch for list: test5, cause: > >htsearch, > >detail: -12- > > > >On the archive page, it reports that the search index has yet to be > >built - do I need to run nightly_htdig for each list when it is > >created? > >Until nightly_htdig is first run there will be no per-list htdig search >indexes for htsearch to use. It is usually a good idea to send an >initial message to a list which is being archived, which will cause >htdig to be setup for the list (per-list htdig.conf created and search >form added to the list's TOC page), and then run nightly_htdig from the >command line (as the mailman uid) to generate an initial set of htdig >indexes for the list. > >Just copy the command for running nightly_htdig in the modified mailman >crontab generated by the htdig integration patch > >Bear in mind that, in common with most search engines, htdig does not >search the web pages when a user submits a search query; rather some >part of the search engine's suite of programs (rundig in the case of >htdig) builds search indexes for the material and it is from these >indexes that a user's search query is satisfied. That is also why the >search form has the date/time indexing was last run for the list >embedded in it with the caution that more recent archive material will >not be found. > >btw: this issue is covered in the third paragraph under the heading >"Operational Information" in INSTALL.htdig-mm. > > >Thanks, > >Tim. > > > >-- > >Timothy Arnold, Server & Network Infrastructure Support Officer, > >Internet Services, > >Becta, Coventry, CV4 7JJ, UK Voice: +44 24 7684 7169 > >email: timothy.arnold(a)becta.org.uk Fax: +44 24 7641 1418 > > > > > >********************************************************************* > >* > >This email and any files transmitted with it are confidential and > >intended solely for the use of the individual or entity to whom they > >are addressed. If you have received this email in error please notify > >the system manager. This footnote also confirms that this email message > >has been swept by MIMEsweeper for the presence of computer viruses. > >www.mimesweeper.com > >********************************************************************** > > >********************************************************************** >This email and any files transmitted with it are confidential and >intended solely for the use of the individual or entity to whom they >are addressed. If you have received this email in error please notify >the system manager. This footnote also confirms that this email message >has been swept by MIMEsweeper for the presence of computer viruses. >www.mimesweeper.com >********************************************************************** ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************

1 0

mailman GUI?
by Scott Eagle April 30, 2003

April 30, 2003

Just curious how you get mailmans GUI up and running and if there is a standard mailman port, if I were to search for the GUI on an old Unix box running mailman? Thanks, Scott

2 1

Re: [Mailman-Users] httpS
by Todd April 30, 2003

April 30, 2003

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Felipe, Please direct replies to the list. Felipe Neuwald wrote: > Ok, I added the follow line to my mm_cfg.py: > > DEFAULT_URL_PATTERN = 'https://%s/mailman/' > > And when I run fix_url.py, look what I got: > > -su-2.05b# ./fix_url.py > Reset a list's web_page_url attribute to the default setting. > > This script is intended to be run as a bin/withlist script, i.e. > > % bin/withlist -l -r fix_url listname [options] [...] > Ok, what I have to do? fix_url.py -u https:/%s/mailman/ ? Firstly, you need to run the script via the withlist command as specified in the help. You should be able to run it like so: bin/withlist -l -r fix_url listname and it should pick up the new settings. I know I've done this a few times, though it's been a while so hopefully I'm not skipping anything important. - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ============================================================================ There are two kinds of light - the glow that illuminates, and the glare that obscures. -- James Thurber -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE+r+Rmuv+09NZUB1oRArqUAKCxHLomkTw/mDn/9LYehaFWl6cZXgCgxZ3i 4vU1kzjPU1NCx2lNlvDnXg8= =fEZX -----END PGP SIGNATURE-----

1 0

RE: [Mailman-Users] Mailman/htdig problem
by Timothy Arnold April 30, 2003

April 30, 2003

Hi Richard, I would really like to thank you for spending time helping me with my problem. I appreciate it!. >mailman@mailman2:/mailman/run/archives/private/rbtest2/htdig> ls >db.docdb db.wordlist rbtest2.conf >db.docs.index db.words.db rundig_last_run I can confirm that nightly_htdig returns OK and I see the same output as above. The file modification time is the same that is reported on the index page for the list. I am pretty confident that everything is working with the nightly_htdig script. >1. create a small test script, putting it anywhere convenient and making >sure that the user/group your web server runs as can access and execute the >script: >2. in your mm_cfg file, temporarily substitute the path to this test.py >script as the value of HTDIG_HTSEARCH_PATH >3. do a search from the search form for a list which you believe has all >its indexes etc. You should get back a web page telling you about the >environment that test.py found itself in when it was run by mmsearch; the >purpose is to veryify that htsearch will find itself in the correct >environment when it is run. Some things of interest are near top of the web >page returned. For example, I get the following on my test system; the >MiniFieldStorage tells me the names and values of the query; the config >field should contain the name of the list being searched and the words >field should contain what you entered in the search form. The CONFIG_DIR >value should point to $prefix/archives/htdig/. The webpage returns fine - config_dir returns what I expected. The exit status value is 1. >What version of htdig are you using? The htdig integration patches are >tested using htdig 3.1.6 stable, not the 3.2 beta, although there is no >particular reason that 3.2 should not work but some pople have reported >problems, which are not MM specific. I am running mailman 2.1.2 and htdig 3.1.6 Thanks very much for all your help. Timothy. ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************

1 0

RE: [Mailman-Users] Mailman/htdig problem
by Richard Barrett April 30, 2003

April 30, 2003

At 14:06 30/04/2003, Timothy Arnold wrote: >Hi Richard, > >Thanks for this. I followed the instructions detailed in Operational >Information in the install notes and it now had created the indicies. >However, mmsearch still fails when I try to conduct a search. > >Mmsearch reports: > >Htdgi Archives Access Failure > >Search failed -12- > >The messages that I reported last time are still being reported in the >syslog. Any ideas what -12- means? Further to my earlier suggestions, you can try running htsearch from the command line and seeing how it responds. Try the following command: <path-to-htsearch> -c $prefix/archives/htdig/<listname>.conf answer the prompt for words with some words to seach for answer the format as short What happens? If all is well you should get back a HTTP response Content-type header of text/html, followed by a bunch of HTML, this being the search results. In total, if my earlier suggestion of the test script returns the correct results, and running htsearch from the command line returns the correct results, then you should not have a problem. Let us hope we do not end up with that contradiction to deal with. >Thanks, >Tim. > >-----Original Message----- >From: Richard Barrett [mailto:R.Barrett@ftel.co.uk] >Sent: 30 April 2003 13:51 >To: Timothy Arnold; mailman-users(a)python.org >Subject: Re: [Mailman-Users] Mailman/htdig problem > > >At 11:18 30/04/2003, Timothy Arnold wrote: > >Hiya, > > > >I have recently installed mailman 2.1.2 with the relevent htdig patches > >and I still cannot get it to work. > > > >For a given list, the search box is displayed and the configuration > >file for the list is generated but the search funtionality doesn't work > >- I look in the error log and I find > > > >Apr 30 10:56:39 2003 (12488) htsearch for list: test5, existatus: 1 Apr > >30 10:56:39 2003 (12488) htsearch for list: test5, cause: htsearch, > >detail: -12- > > > >On the archive page, it reports that the search index has yet to be > >built - do I need to run nightly_htdig for each list when it is > >created? > >Until nightly_htdig is first run there will be no per-list htdig search >indexes for htsearch to use. It is usually a good idea to send an initial >message to a list which is being archived, which will cause htdig to be >setup for the list (per-list htdig.conf created and search form added to >the list's TOC page), and then run nightly_htdig from the command line (as >the mailman uid) to generate an initial set of htdig indexes for the list. > >Just copy the command for running nightly_htdig in the modified mailman >crontab generated by the htdig integration patch > >Bear in mind that, in common with most search engines, htdig does not >search the web pages when a user submits a search query; rather some part >of the search engine's suite of programs (rundig in the case of htdig) >builds search indexes for the material and it is from these indexes that a >user's search query is satisfied. That is also why the search form has the >date/time indexing was last run for the list embedded in it with the >caution that more recent archive material will not be found. > >btw: this issue is covered in the third paragraph under the heading >"Operational Information" in INSTALL.htdig-mm. > > >Thanks, > >Tim. > > > >-- > >Timothy Arnold, Server & Network Infrastructure Support Officer, > >Internet Services, > >Becta, Coventry, CV4 7JJ, UK Voice: +44 24 7684 7169 > >email: timothy.arnold(a)becta.org.uk Fax: +44 24 7641 1418 > > > > > >********************************************************************** > >This email and any files transmitted with it are confidential and > >intended solely for the use of the individual or entity to whom they > >are addressed. If you have received this email in error please notify > >the system manager. This footnote also confirms that this email message > >has been swept by MIMEsweeper for the presence of computer viruses. > >www.mimesweeper.com > >********************************************************************** > > >********************************************************************** >This email and any files transmitted with it are confidential and >intended solely for the use of the individual or entity to whom they >are addressed. If you have received this email in error please notify >the system manager. >This footnote also confirms that this email message has been swept by >MIMEsweeper for the presence of computer viruses. >www.mimesweeper.com >**********************************************************************

1 0

RE: [Mailman-Users] Mailman/htdig problem
by Richard Barrett April 30, 2003

April 30, 2003

At 14:06 30/04/2003, Timothy Arnold wrote: >Hi Richard, > >Thanks for this. I followed the instructions detailed in Operational >Information in the install notes and it now had created the indicies. >However, mmsearch still fails when I try to conduct a search. First thing to check is the $prefix/archives/private/<listname>/htdig directory If it looks something like this then nightly_htdig's execution of rundig worked approximately as planned: mailman@mailman2:/mailman/run/archives/private/rbtest2/htdig> ls db.docdb db.wordlist rbtest2.conf db.docs.index db.words.db rundig_last_run The db.* files are generated by the htdig programs called by rundig. If these are missing then something went wrong with rundig's execution. The rundig_last_run file is a zero length file whose modification time is set by nightly_htdig. the <listname>.conf is the per list htdig conf file. There should also by a symlink to <listname>.conf in the directory $prefix/archives/htdig/ You didn't say whether the list's TOC page has an index updated date/time in it after running nightly_htdig. If nightly_htdig worked correctly the date/time group on the list TOC page should match the modification time on rundig_last_run for the list. If the TOC page hasn't been updated then rundig did not run cleanly and an error should have been printed out by nightly_htdig. Things you can try: 1. try running nightly_htdig from the command line with the -v (verbose) option. This should print out the name of each list and whether or not it is running rundig. If it says it is skipping a list because of no recent posts this is because the modification time of a list's rundig_last_run is after the last recorded post to the list. 2. you can "force" nightly_htdig to run for a list by deleting the list's $prefix/archives/private/<listname>/htdig/rundig_last_run file. Is anything unexpected being output when you run nightly_htdig with the -v option? If you are sure you have everything configured correctly then we can try and explore how mmsearch is running htsearch by proceeding as follows: 1. create a small test script, putting it anywhere convenient and making sure that the user/group your web server runs as can access and execute the script: test.py -------------------------------------- #! /usr/local/bin/python # make sure the line above has the correct path for you python installation import cgi cgi.test() end of test.py ------------------------------- 2. in your mm_cfg file, temporarily substitute the path to this test.py script as the value of HTDIG_HTSEARCH_PATH 3. do a search from the search form for a list which you believe has all its indexes etc. You should get back a web page telling you about the environment that test.py found itself in when it was run by mmsearch; the purpose is to veryify that htsearch will find itself in the correct environment when it is run. Some things of interest are near top of the web page returned. For example, I get the following on my test system; the MiniFieldStorage tells me the names and values of the query; the config field should contain the name of the list being searched and the words field should contain what you entered in the search form. The CONFIG_DIR value should point to $prefix/archives/htdig/. extract for page retuned by test.py---------------------- Command Line Arguments: ['/usr/local/httpd/cgi-bin/test.py'] Form Contents: config: <type 'instance'> MiniFieldStorage('config', 'rbtest2') format: <type 'instance'> MiniFieldStorage('format', 'short') method: <type 'instance'> MiniFieldStorage('method', 'and') sort: <type 'instance'> MiniFieldStorage('sort', 'score') words: <type 'instance'> MiniFieldStorage('words', 'htdig search for words) Shell Environment: CONFIG_DIR /mailman/run/archives/htdig end extract for page returned by test.py------------------ If that gives the expected results then mmsearch is doing the right thing but htsearch is failing for some reason I've not yet seen. . The exit status being returned by htsearch is the one shown in MM's $prefix/logs/error entry written when the failure occurs. What value are you seeing? What version of htdig are you using? The htdig integration patches are tested using htdig 3.1.6 stable, not the 3.2 beta, although there is no particular reason that 3.2 should not work but some pople have reported problems, which are not MM specific. Try the above and get back to me. >Mmsearch reports: > >Htdgi Archives Access Failure > >Search failed -12- > >The messages that I reported last time are still being reported in the >syslog. Any ideas what -12- means? The mmsearch can fail for a number of reason, which are numbered 1, 2 ... Error 12 is when execution of htsearch fails. If things are working as planned users should not see these cryptic diagnostics. They just tie the failure, definitively, to a point in the mmsearch source code. >Thanks, >Tim. > >-----Original Message----- >From: Richard Barrett [mailto:R.Barrett@ftel.co.uk] >Sent: 30 April 2003 13:51 >To: Timothy Arnold; mailman-users(a)python.org >Subject: Re: [Mailman-Users] Mailman/htdig problem > > >At 11:18 30/04/2003, Timothy Arnold wrote: > >Hiya, > > > >I have recently installed mailman 2.1.2 with the relevent htdig patches > >and I still cannot get it to work. > > > >For a given list, the search box is displayed and the configuration > >file for the list is generated but the search funtionality doesn't work > >- I look in the error log and I find > > > >Apr 30 10:56:39 2003 (12488) htsearch for list: test5, existatus: 1 Apr > >30 10:56:39 2003 (12488) htsearch for list: test5, cause: htsearch, > >detail: -12- > > > >On the archive page, it reports that the search index has yet to be > >built - do I need to run nightly_htdig for each list when it is > >created? > >Until nightly_htdig is first run there will be no per-list htdig search >indexes for htsearch to use. It is usually a good idea to send an initial >message to a list which is being archived, which will cause htdig to be >setup for the list (per-list htdig.conf created and search form added to >the list's TOC page), and then run nightly_htdig from the command line (as >the mailman uid) to generate an initial set of htdig indexes for the list. > >Just copy the command for running nightly_htdig in the modified mailman >crontab generated by the htdig integration patch > >Bear in mind that, in common with most search engines, htdig does not >search the web pages when a user submits a search query; rather some part >of the search engine's suite of programs (rundig in the case of htdig) >builds search indexes for the material and it is from these indexes that a >user's search query is satisfied. That is also why the search form has the >date/time indexing was last run for the list embedded in it with the >caution that more recent archive material will not be found. > >btw: this issue is covered in the third paragraph under the heading >"Operational Information" in INSTALL.htdig-mm. > > >Thanks, > >Tim. > > > >-- > >Timothy Arnold, Server & Network Infrastructure Support Officer, > >Internet Services, > >Becta, Coventry, CV4 7JJ, UK Voice: +44 24 7684 7169 > >email: timothy.arnold(a)becta.org.uk Fax: +44 24 7641 1418 > > > > > >********************************************************************** > >This email and any files transmitted with it are confidential and > >intended solely for the use of the individual or entity to whom they > >are addressed. If you have received this email in error please notify > >the system manager. This footnote also confirms that this email message > >has been swept by MIMEsweeper for the presence of computer viruses. > >www.mimesweeper.com > >********************************************************************** > > >********************************************************************** >This email and any files transmitted with it are confidential and >intended solely for the use of the individual or entity to whom they >are addressed. If you have received this email in error please notify >the system manager. >This footnote also confirms that this email message has been swept by >MIMEsweeper for the presence of computer viruses. >www.mimesweeper.com >**********************************************************************

1 0

Problems with Mailman + FreeBSD 4.8-Stable
by Felipe Neuwald April 30, 2003

April 30, 2003

Hello Folks, I've installed Mailman via ports tree in a FreeBSD Box. Look what I did: cd /usr/ports/mail/mailman make make install Ok, after it, I try to run it, and look what I got: -su-2.05b# ./mailmanctl start Site list is missing: mailman Ok, let's try another way: -su-2.05b# /usr/local/etc/rc.d/./mailman.sh start Site list is missing: mailman Ok... What are wrong? Anyone knows? Let me show to you more info about my system: -su-2.05b# uname -a FreeBSD xxx.xxx.xxx 4.8-STABLE FreeBSD 4.8-STABLE #0: Wed Apr 23 10:51:56 BRT 2003 root@xxx.xxx.xxx:/usr/src/sys/compile/KERNEL2 i386 --- Felipe Neuwald neuwald(a)rudah.com.br Rudah On-Line SysAdm

3 2

httpS
by Felipe Neuwald April 30, 2003

April 30, 2003

Hello again Folks, Now I have other problem. I only use HTTPS on my Apache that are running on my mail server. The targets of all links on Mailman appoint to one address that user HTTP, not HTTPS. The question is the "s" of the HTTP. Have a way that I can change the targets of the links automatically? Sincerly Thanks, --- Felipe Neuwald neuwald(a)rudah.com.br Rudah On-Line SysAdm

2 1