Re: [Mailman-Users] Mailman Htdig integration with Nginx - Path variables

[Mark Sapiro]

On 10/23/2014 01:56 AM, Andrew Hodgson wrote:
> 
> The second issue is that the htdig CGI needs to be using HTTP and not HTTPS.  
> I made this available under the HTTP context so nightly_htdig can crawl the 
> archives.  The htdig script is now not available under HTTPS.


At one point I ran into this on my own site when trying to
unconditionally use HTTPS. I looked at it at the time, and I think htdig
can be made to use HTTPS, but I never followed up with it.

Maybe I'll look again.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman Htdig integration with Nginx - Path variables

[Andrew Hodgson]

Hi,

Sorry to reply to my own post.

The issue was actually twofold:

There was an issue with the HTTP to HTTPS redirection on the site, and because 
I hadn't set the public archives parameter in mm_cfg.py to HTTPS, the system 
was offering up HTTP URLS.  I did this and rebuilt the archives for all lists.

The second issue is that the htdig CGI needs to be using HTTP and not HTTPS.  I 
made this available under the HTTP context so nightly_htdig can crawl the 
archives.  The htdig script is now not available under HTTPS.

I can post my current config if required.

Thanks.
Andrew.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman Htdig integration with Nginx - Path variables

[Andrew Hodgson]

Hi all,

Wonder if someone could take a look at this for me?

I have moved our Mailman installation to Nginx.  Everything is working 
correctly, however, I am using the Htdig patch to get search functionality.

I got the split_path_info set up to work with Mailman, but I am having issues 
getting a working installation with the mmsearch script.  The initial page 
loads up, but when you refine the search or go to the next page, I get an error 
with the path splitting which causes the CGI to error.  I tried altering the 
path variable for the mmsearch script specifically, but the issue I am having 
is getting Nginx to split the path in the right place, since the scripts don't 
have an extension to work with (like I can use with PHP scripts etc.).  It's 
probably a simple fix, and I can set the location for the mmsearch script so it 
doesn't mess up the path variable for the other Mailman scripts if required.

My config is below, sorry for the formatting in my mailer.

Andrew.

# HTTP redirects - I had to use separate servers for each domain to stop 
redirecting to the wrong host
server {
listen 80;
server_name lists.domain1.com;
access_log off;
error_log off;
rewrite ^ https://$server_name$request_uri?$query_string permanent;
}

server {
listen 80;
server_name lists.domain2.com;
access_log off;
error_log off;
rewrite ^ https://$server_name$request_uri?$query_string permanent;
}

server {
listen 443 ssl;
server_name lists.domain1.com lists.domain2.com;
 access_log  /var/log/nginx/lists-access.log main;
error_log  /var/log/nginx/lists-error.log warn;
root /var/www/lists;
ssl_certificate /path/to/cert.pem
ssl_certificate_key /path/to/key.key
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers 
ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS;
ssl_prefer_server_ciphers on;
add_header Strict-Transport-Security "max-age=31536000; 
includeSubdomains";
ssl_stapling on;
ssl_stapling_verify on;

# Redirect to the listinfo page by default
location = / {
rewrite ^ /listinfo permanent;
}

# Send the requests to the various scripts to the correct location. URL 
https://server/listinfo etc.
location ~ 
^/(admin|confirm|edithtml|listinfo|options|rmlist|subscribe|admindb|create|htdig|private|roster|mmsearch)
 {
fastcgi_split_path_info (^/[^/]*)(.*)$;
fastcgi_param SCRIPT_FILENAME 
/usr/local/mailman/cgi-bin/$fastcgi_script_name;
fastcgi_param PATH_INFO $fastcgi_path_info;
fastcgi_pass  unix:/var/run/fcgiwrap.socket;
include /etc/nginx/fastcgi_params;
}

location /icons {
alias /usr/local/mailman/icons;
}

location /pipermail {
alias /usr/local/mailman/archives/public;
}
location /htdigimages {
alias /var/lib/htdig/www;
}
}
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman/Htdig integration

[Mark Sapiro]

Andrew Hodgson  wrote:

>Hi,
>
>This is a Debian specific issue, look at:
>
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506448
>
>Andrew.

Aaah!  Thanks for the info.


-- 
Mark Sapiro 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman/Htdig integration

[Andrew Hodgson]

Hi,

This is a Debian specific issue, look at:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506448

Andrew.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman/Htdig integration

[Andrew Hodgson]

From: Mark Sapiro [mailto:m...@msapiro.net] 
Sent: 18 May 2012 20:27
To: Andrew Hodgson; mailman-users@python.org
Subject: RE: [Mailman-Users] Mailman/Htdig integration

>Andrew Hodgson wrote:
>>
>>One other question if I may:
>>
>>/bin/mv: 
>>`/usr/local/mailman/archives/private/bcab-board/htdig/synonyms.db' and 
>>`/usr/local/mailman/archives/private/bcab-board/htdig/synonyms.db' are 
>>the same file

>The nightly_htdig script runs the rundig shell script pointed to by 
>mm_cfg.HTDIG_RUNDIG_PATH

>My version (3.2.0b6 + some patches from
><ftp://ftp.ccsf.org/htdig-patches/3.2.0b6/>) of that script doesn't look like 
>it does those mv commands.

Weird. I am using the Debian version but have downloaded the source and it has 
the following in the rundig script:

case "$alt" in
-a)
  ( cd $DBDIR && test -f db.docdb.work &&
for f in *.work
do
mv -f $f `basename $f .work`
done
test -f db.words.db.work_weakcmpr &&
mv -f db.words.db.work_weakcmpr db.words.db_weakcmpr) ;;
esac

The nightly_htdig script doesn't I believe seem to use the -a option but it 
looks as though that is being done anyway.  The patch on the FTP site for the 
rundig command seems to fix another issue with the script.

Andrew.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman/Htdig integration

[Mark Sapiro]

Andrew Hodgson wrote:
>
>One other question if I may:
>
>When I run nightly_htdig -v to get the search engine updated, I get the 
>following output:
>
>htdig'ing archive of list: bcab-board
>/bin/mv: `/usr/local/mailman/archives/private/bcab-board/htdig/root2word.db' 
>and `/usr/local/mailman/archives/private/bcab-board/htdig/root2word.db' are 
>the same file
>/bin/mv: `/usr/local/mailman/archives/private/bcab-board/htdig/word2root.db' 
>and `/usr/local/mailman/archives/private/bcab-board/htdig/word2root.db' are 
>the same file
>/bin/mv: `/usr/local/mailman/archives/private/bcab-board/htdig/synonyms.db' 
>and `/usr/local/mailman/archives/private/bcab-board/htdig/synonyms.db' are the 
>same file


The nightly_htdig script runs the rundig shell script pointed to by
mm_cfg.HTDIG_RUNDIG_PATH

My version (3.2.0b6 + some patches from
) of that script doesn't
look like it does those mv commands.

-- 
Mark Sapiro 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
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman/Htdig integration

[Andrew Hodgson]

Hi,

One other question if I may:

When I run nightly_htdig -v to get the search engine updated, I get the 
following output:

htdig'ing archive of list: bcab-board
/bin/mv: `/usr/local/mailman/archives/private/bcab-board/htdig/root2word.db' 
and `/usr/local/mailman/archives/private/bcab-board/htdig/root2word.db' are the 
same file
/bin/mv: `/usr/local/mailman/archives/private/bcab-board/htdig/word2root.db' 
and `/usr/local/mailman/archives/private/bcab-board/htdig/word2root.db' are the 
same file
/bin/mv: `/usr/local/mailman/archives/private/bcab-board/htdig/synonyms.db' and 
`/usr/local/mailman/archives/private/bcab-board/htdig/synonyms.db' are the same 
file

Any suggestions?
Thanks.
Andrew.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman/Htdig integration

[Andrew Hodgson]

From: Mark Sapiro [m...@msapiro.net]
Sent: 17 May 2012 23:43
To: Andrew Hodgson; mailman-users@python.org
Subject: Re: [Mailman-Users] Mailman/Htdig integration

>Andrew Hodgson wrote:
>>
>>Everything works fine, but if someone posts to a list it appears that the 
>>archive page gets re-generated without the search box at the top.  I feel I 
>>have missed something blindingly obvious and I am going to >kick myself when 
>>I find out what it is but at the moment I am still searching!


>Did you restart Mailman? If not, the old archtoc(nombox).html template
>is cached in ArchRunner.

That was it, once it was restarted everything worked fine!

Thanks for that, I knew it was something simple!
Andrew.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman/Htdig integration

[Mark Sapiro]

Andrew Hodgson wrote:
>
>Everything works fine, but if someone posts to a list it appears that the 
>archive page gets re-generated without the search box at the top.  I feel I 
>have missed something blindingly obvious and I am going to kick myself when I 
>find out what it is but at the moment I am still searching!


Did you restart Mailman? If not, the old archtoc(nombox).html template
is cached in ArchRunner.

-- 
Mark Sapiro 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
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman/Htdig integration

[Andrew Hodgson]

Hi,

Following comments on this list over the last few days I thought I would try 
out Mailman/Htdig integration on my setup.  I tried this on a sandbox VM I have 
here and everything seemed to go well, I did have to change some of the values 
for the URLs etc as I don't use the /mailman path in the URLs.  Everything 
worked in test so I pushed the changes out to the production system.

I did the following to enable:

Set the Htdig integration to enabled in mm_cfg.py
Run the arch command on the lists to generate the relevant pages with the 
search links at the top.
Run the nightly_htdig script to generate the search indexes.

Everything works fine, but if someone posts to a list it appears that the 
archive page gets re-generated without the search box at the top.  I feel I 
have missed something blindingly obvious and I am going to kick myself when I 
find out what it is but at the moment I am still searching!

Here is the relevant part of mm_cfg.py:
USE_HTDIG = 1
HTDIG_FILES_URL = '/htdigimages/'
HTDIG_HTSEARCH_PATH = '/usr/lib/cgi-bin/htsearch'
HTDIG_RUNDIG_PATH = '/usr/bin/rundig'

Any suggestions greatfully received.
Thanks.
Andrew.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + htdig problems

[Glenn Sieb]

Peter DeVries said the following on 8/21/2006 11:10 AM:
> My problem is that the archive page of any newly created lists looks like this

It looks like you might be missing:

ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
Alias /pipermail/ "/usr/local/mailman/archives/public/"

in your httpd.conf ... if it's there, have you restarted Apache?

Best,
--Glenn
--
Mailman-Users mailing list
Mailman-Users@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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Mailman + htdig problems

[Peter DeVries]

I have an installation of mailman 2.1.8 that I patched with:

htdig-2.1.7-0.1.patch
indexing-2.1.7-0.1.patch
mhonarc-2.1.7-0.1.patch

My problem is that the archive page of any newly created lists looks like this

 %(indexing_disable)s
The Index-test Archives

You can get more information about this list.
%(htsearch)s
Archive   View by:   Downloadable version   
August 2006:[ Thread ]   [
Subject ]   [ Author ] %(indexing_enable)s[ Date ]
%(indexing_disable)s  [ Text 282 bytes ]
 %(indexing_enable)s

The %(htsearch)s doesn't seem to be properly calling TOC_htsearch and
the indexing_enable parts appear on the page which I don't believe the
should.

Any info would be greatly appreciated.

Peter
--
Mailman-Users mailing list
Mailman-Users@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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] mailman / htdig integration problem

[Sruli Shaffren]

Hi.  I'm runniing Mailman 2.1.6 and have installed htdig 3.1.6, and
integrated with mailman as per directions in HOWTOs I have found on this
list and elsewhere.
 
The installation of htdig itself seems okay, as does mailman.  I'm able to
use htdig standalone. and mailman runs fine.  But when I try to access 
http://www.my_list_domain.com/mailman/htsearch/mylistname
I get a 404 error.  
 
All the normal mailman functions in that directory work fine, just the ones
added by the htdig integration come up not found.  I've checked ownership
and permissions of the .pyc files in /Mailman/Cgi and it seems
fine.  Also /cgi-bin contains mmsearch and htdig, seemingly correct
ownership and permissions,
 
I'd love to get this to work.  I bet I left out a step somewhere.  Any
suggestions?

Sruli Shaffren
Also Networks
[EMAIL PROTECTED]

--
Mailman-Users mailing list
Mailman-Users@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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Mailman/Htdig with Swedish, time problem

[Hugo Hugo]

Hi all !
   
  I am trying to make a Swedish version of the Htdig search features used with 
mailman. I have the mailman/Htdig patch. For some reason nightly_htdig sets the 
date in "lastrun" wrong. It is set in English, but I have set locale correctly 
in the configuration file to sv_SE.iso885915, so Htdig should know better. The 
dates mailman sets are correct. The mailman Htdig patch changes the setting of 
this date in Hyperarch.py. 
   
  Can someone say if this is a bug or if I have done something wrong ? Any idea 
of what could be wrong ?
   
  Cheers,
   
  Hugo


-
 Yahoo! Personals
 Let fate take it's course directly to your email.
 See who's waiting for you Yahoo! Personals
--
Mailman-Users mailing list
Mailman-Users@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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Mailman HTdig error

[Con Wieland]

I got everything up and it seems to be working as expected. But when  
I run the cron job I get the following:

terminate called after throwing an instance of 'std::bad_alloc'
   what():  St9bad_alloc
/opt/www/htdig/bin/rundig: line 53: 13454 Aborted  
$BINDIR/htnotify $opts


However everything seems to be working. I don't understand the  
std::bad_alloc'  what():  St9bad_alloc error.


I assume I'm receiving this because I don't have htnotify configured.  
Do most folks use it, if not can I just comment it out of rundig? If  
you use it how do you configure it.

/opt/www/htdig/bin/rundig: line 53: 13454 Aborted  
$BINDIR/htnotify $opts

running
mailman-2.1.6
htdig-3.1.6
with the companion patches

As always TIA

Con Wieland
Network and Academic Computing Services
University of California at Irvine
--
Mailman-Users mailing list
Mailman-Users@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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Mailman htdig problem

[Jim Tittsler]

On May 3, 2005, at 06:07, Chris Serenil wrote:

> I have just installed Mailman 2.1.15 with the htdig
> patch 444884 and 444879. The search fails when I have
> a list name with a dot in it. (Example
> fa.dl-testlist). I will get these errors when doing a
> search. If there is no dot it works fine.
>
> htdig Archives Access Failure
> The requested list cannot be accessed. No list -3-

I don't use those patches, but a quick look suggests that the problem  
you are having is related to this line in sub doit:
if ($query->param('config') =~ /^([^\.]+)(|\.htsearch)$/) {

I'm guessing it is looking for either a bare listname or  
listname.htsearch.  The first group which looks for a string of  
characters that aren't in the set of '.' and '\' isn't a good choice  
for a listname with a dot in it.  (I'm guessing that the author  
didn't really want a \ there, since IIRC '.' isn't special inside a  
Perl character class and so doesn't warrant escaping... but that  
isn't the problem you are encountering.)  My Perl-foo has weakened  
over years of disuse, so it is risky to suggest something I can't  
test.  But since I didn't see any other replies, you might try  
something like:
if ($query->param('config') =~ /^(.*?)(\.htsearch)?$/) {
No warranty is expressed or implied.  If it breaks, you get to keep  
all the pieces.

I don't know if there are other places in the patches that assume  
there are no dots in the listname once you get past this hurdle.


-- 
Jim Tittsler http://www.OnJapan.net/  GPG: 0x01159DB6
Python Starship  http://Starship.Python.net/crew/jwt/
Mailman IRC  irc://irc.freenode.net/#mailman



--
Mailman-Users mailing list
Mailman-Users@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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Mailman htdig problem

[Chris Serenil]

I have just installed Mailman 2.1.15 with the htdig
patch 444884 and 444879. The search fails when I have
a list name with a dot in it. (Example
fa.dl-testlist). I will get these errors when doing a
search. If there is no dot it works fine. 

htdig Archives Access Failure
The requested list cannot be accessed. No list -3-

If you want to make another attempt to access a list
archive then go via the list users information page.

If this problem persists then please e-mail the
following information to the
[EMAIL PROTECTED]:

   
http://mailman.fa.example.com/pipermail/fa.dl-testsearch2/
/mailman/mmsearch/fa.dl-testsearch2

--
Mailman-Users mailing list
Mailman-Users@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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] mailman-htdig returns blank page

[Toby Wahlers]

I can no longer get mmsearch htdig searches to work. It's been working for 
a long time, suddenly just gives blank pages on the results page. No errors 
in the mailman or apache or htdig logs. The htdig cron job runs fine, the 
indexes appear to be fine. I ran blow_away_htdig and the nightly cron job 
to rebuild everything, which went fine. But still get nothing when I 
search--just an absolutely blank page. I'm running Mailman 2.1.2, htdig 
3.20b4, Apache2. Haven't updated anything in several months. I ran a test 
cgi in place of htsearch, to display environment settings,and it seems as 
though things are set correctly.

--
Mailman-Users mailing list
Mailman-Users@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/

Re: [Mailman-Users] Mailman-htdig bug or configuration error

[Joe Kissell]

On Apr 21, 2004, at 5:26 PM, George Theall wrote:

Traceback (most recent call last):
  File "/usr/share/mailman/scripts/driver", line 87, in run_main
main()
  File "/usr/share/mailman/Mailman/Cgi/mmsearch.py", line 211, in main
child.tochild.close()
IOError: [Errno 32] Broken pipe
Something tells me this may be due to some trivial configuration 
issue,
such as an error in mm_cfg.py, but I'm stumped. Can anyone offer any
guidance?
I've seen this if permissions on htsearch (pointed to by
HTDIG_HTSEARCH_PATH in mm_cfg.py) don't permit it to be executed by the
web user / group.
Aha! Looks like it also occurs when one has a typo in mm_cfg.py 
(HTDIG_SEARCH_PATH instead of HTDIG_HTSEARCH_PATH). Oops. But thanks 
for the tip--it pointed me in the right direction! Everything's working 
now.

Joe

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] Mailman-htdig bug or configuration error

[George Theall]

On Wed, Apr 21, 2004 at 04:22:01PM -0700, Joe Kissell wrote:

> Traceback (most recent call last):
>   File "/usr/share/mailman/scripts/driver", line 87, in run_main
> main()
>   File "/usr/share/mailman/Mailman/Cgi/mmsearch.py", line 211, in main
> child.tochild.close()
> IOError: [Errno 32] Broken pipe
> 
> Something tells me this may be due to some trivial configuration issue, 
> such as an error in mm_cfg.py, but I'm stumped. Can anyone offer any 
> guidance?

I've seen this if permissions on htsearch (pointed to by
HTDIG_HTSEARCH_PATH in mm_cfg.py) don't permit it to be executed by the
web user / group. 

George
-- 
[EMAIL PROTECTED]


pgp0.pgp
Description: PGP signature
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

[Mailman-Users] Mailman-htdig bug or configuration error

[Joe Kissell]

Hello all,

I have a fully functional installation of Mailman 2.1.4 (with patch 
#444884 for htdig integration) running on Mac OS X Server 10.3.3. The 
Mailman lists themselves work correctly, as does htdig by itself. On 
the TOC page for any list's archives, I get the Search box and 
indicator of when the index was last rebuilt, just as I should. 
However, when I perform a search on any term, I get the following:

Traceback (most recent call last):
  File "/usr/share/mailman/scripts/driver", line 87, in run_main
main()
  File "/usr/share/mailman/Mailman/Cgi/mmsearch.py", line 211, in main
child.tochild.close()
IOError: [Errno 32] Broken pipe
Something tells me this may be due to some trivial configuration issue, 
such as an error in mm_cfg.py, but I'm stumped. Can anyone offer any 
guidance?

Thanks,

Joe Kissell

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] mailman-htdig integration and rundig after post

[Richard Barrett]

Jörg

rundig is run automatically to build/rebuild search indices by 
whichever one of the nightly_htdig series of cron scripts you choose to 
use: see the INSTALL.htdig-mm file installed by the patch. The 
integration patch adds an entry to MM's default crontab 
($prefix/Mailman/cron/crontab.in) which runs $prefix/cron/nightly_htdig 
every 24 hours.

If you want to run nightly_htdig more frequently then you can change 
the crontab entry that runs it. The script can also be run from the 
command line or any other means that you want to set up.

The patched Mailman does NOT perform htdig reindexing every time a new 
piece of mail is added to a list's archive, that is why the patched 
code adds and updates a note like this to a list's Archive TOC web 
page, below the search form:


Note:The archive search index was last rebuilt at . Any postings after that will not be 
found by a search. Index rebuild is usally done once every 24 hours for 
this list. You can use a "View by date" link below to access more 
recent postings.


Hope that resolves you query. Let me know if not.

Richard

On Wed Feb 18 03:36:50 EST 2004 Joerg Fries said:


Hello All,
yesterday I've integrated htdig into mailman successfully. My archives 
are
searchable now.

When I read the docs, I've expected the following: When a new mail 
(post)
arrived, the archiver qrunner should update the archives *and* run 
rundig to
update the database files in
/var/lib/mailman/archives/private//htdig. Am I right? But on 
my
site there is no update of the htdig files.

I am running mailman-2.1.4 and htdig-3.1.6 on SuSE 8.2 with all the 
patches
provided by Richard Barrett applied (thanks for all, Richard). Here is 
my
mm_cfg.py file:

[...]
USE_HTDIG = 1
HTDIG_RUNDIG_PATH = '/usr/bin/rundig'
HTDIG_HTSEARCH_PATH = '/srv/www/cgi-bin/htsearch'
HTDIG_FILES_URL = '/htdig/images/'
No entries in log files error and qrunner (I've restarted qrunner 
before I
posted)

Thanks for any help

Joerg

---
Richard Barrett   http://www.openinfo.co.uk
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] mailman-htdig integration and rundig after post

["Fries, Jörg"]

Hello All,

yesterday I've integrated htdig into mailman successfully. My archives are
searchable now.

When I read the docs, I've expected the following: When a new mail (post)
arrived, the archiver qrunner should update the archives *and* run rundig to
update the database files in
/var/lib/mailman/archives/private//htdig. Am I right? But on my
site there is no update of the htdig files.

I am running mailman-2.1.4 and htdig-3.1.6 on SuSE 8.2 with all the patches
provided by Richard Barrett applied (thanks for all, Richard). Here is my
mm_cfg.py file:

[...]
USE_HTDIG = 1
HTDIG_RUNDIG_PATH = '/usr/bin/rundig'
HTDIG_HTSEARCH_PATH = '/srv/www/cgi-bin/htsearch'
HTDIG_FILES_URL = '/htdig/images/'

No entries in log files error and qrunner (I've restarted qrunner before I
posted)

Thanks for any help

Joerg

**
** eSafe scanned this email for viruses, vandals and malicious content **
**


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman-HTdig integration

[Paul H Byerly]

Richard wrote:
But the real problem is that no consensus has been reached on
committing Mailman to use of the HTdig search engine for archive
search. With posts to mailman-users and mailman-developers lists by
some subscribers that express negative views about HTdig, this
consensus is not likely to be reached. Also, I believe the main MM
developers are not keen on bundling HTdig with MM or tying MM too
tightly to HTdig.
 It seems to me that it could be built into the Mailman system with a 
"switch" to turn it on for those who desire it - either by list or for the 
server.  If I understand it properly, the bit of code in archtoc.html would 
server this function.  Breaking archtoc.htm into two pieces would allow one 
to not have htdig by blanking the code in that template.  It would also 
make it easier to modify htdig, and all the code for the text could be in 
that new template for easy modification or addition.

<>< Paul 
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + htDig

[Rich West]

Ok.. I think I know what I did.. I didn't restart the qrunner.  As I 
wrote the previous email to you, I realized that I had _thought_ about 
restarting the qrunner, but didn't.  I went through the whole process again:
o Edit mm_cfg.py to set USE_HTDIR=1
o python -c 'from compileall import *; 
compile_dir("/Mailman",10,"/Mailman")'
o /etc/init.d/mailmanctrl restart
o bin/rmlist test
o bin/newlist test
o bin/arch test
o Entered additional recipients via the web interface.
o Sent a test message to the test list
o /usr/bin/python -S /cron/nightly_htdig -v test  (it complained 
about not having the centralized db files, but that seemed ok)
o Pointed my browser at the test archives, and viola!  The search 
ability was there!  And searching worked!

I'm not sure if it was the fact that I recompiled the mm_cfg.py file or 
restarting the qrunner which started things working, though.

Now, I just have to go through and migrate the existing lists. :)  
Hopefully, that won't be too difficult. :)

Thanks for all of your help!
-Rich
Rich West wrote:

Ok.. I blew away my test list, set USE_HTDIG=1, restarted the qrunner, 
created the list with newlist, ran blow_away_htdig test, ran arch 
test, and sent a message to the list.

It seems likeit does everything BUT create update the index.html file 
with the search info..

Perhaps I should start over from scratch...

-Rich


Wait a sec... if I am reading that correctly, then existing lists 
would have been created using the standard templates which did not, 
obviously, have the htdig patch.  Newly created lists would be 
created against the now-patched htdig templates, and they should work 
properly.  Existing lists would have to have their templates patched 
accordingly.

Is that right?

If so, then it is likely that my installation IS working as 
expected.  I will have to delete my test list and recreate it, then 
run some tests and observe the results.

I'll let you know if I have any troubles there.

Thanks for your help!!

-Rich



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman + htDig

[Rich West]

I realize this has come up often in the list, but hit a snag and was not 
sure where else to turn.  I couldn't find much in the archives that 
addressed this, but if it is a duplicate, please accept my apologies.

I've applied the htDig patches :
http://www.openinfo.co.uk/mailman/patches/728836/templates-2.1.2-0.1.patch
http://www.openinfo.co.uk/mailman/patches/732366/tz-2.1.2-0.2.patch
http://www.openinfo.co.uk/mailman/patches/730769/tcache-2.1.2-0.3.patch
http://www.openinfo.co.uk/mailman/patches/444879/indexing-2.1.2-0.1.patch
http://www.openinfo.co.uk/mailman/patches/444884/htdig-2.1.2-0.4.patch
And all were applied happily.

The indexing appears to be happening correctly on the filesystem level 
since the htdig directory is being created, the conf file is being 
created, and if I manually perform a search (htsearch -c ), I do 
get output and results.  However, I am not getting the search form at 
the top of the index.html page as is supposed to happen.  So, as 
expected, I cannot search via the web interface. :(

The index.html file *IS* being updated, but nothing is getting added to 
it (no search form)...

I *believe* I followed the htdig docs to the letter, but it seems as if 
I am still missing something.

Any help would be much appreciated!

Thanks!
-Rich
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + htDig

[Richard Barrett]

On Saturday, August 9, 2003, at 04:06  pm, Rich West wrote:

Ok.. I think I know what I did.. I didn't restart the qrunner.  As I 
wrote the previous email to you, I realized that I had _thought_ about 
restarting the qrunner, but didn't.  I went through the whole process 
again:
o Edit mm_cfg.py to set USE_HTDIR=1
o python -c 'from compileall import *; 
compile_dir("/Mailman",10,"/Mailman")'
o /etc/init.d/mailmanctrl restart
o bin/rmlist test
o bin/newlist test
o bin/arch test
o Entered additional recipients via the web interface.
o Sent a test message to the test list
o /usr/bin/python -S /cron/nightly_htdig -v test  (it 
complained about not having the centralized db files, but that seemed 
ok)
I think you can resolve this by reference to the section under the 
heading "htdig Permissions Considerations" in INSTALL.htdig-mm

When rundig is being run by 'mailman' cron as the 'mailman' uid it 
probably does not have permissions to create the 'shared' htdig db's. 
My hack is to give the 'mailman' group group ownership and write 
permission over the the common and db subdirectories of the htdig 
install (/opt/www/htdig/ or wherever yout htdig is installed), and the 
files there contained.

o Pointed my browser at the test archives, and viola!  The search 
ability was there!  And searching worked!

I'm not sure if it was the fact that I recompiled the mm_cfg.py file 
or restarting the qrunner which started things working, though.

Now, I just have to go through and migrate the existing lists. :)  
Hopefully, that won't be too difficult. :)

Best of luck.

Thanks for all of your help!
No problem. Pleased you are up and running.

-Rich

Rich West wrote:

Ok.. I blew away my test list, set USE_HTDIG=1, restarted the 
qrunner, created the list with newlist, ran blow_away_htdig test, ran 
arch test, and sent a message to the list.

It seems likeit does everything BUT create update the index.html file 
with the search info..

Perhaps I should start over from scratch...

-Rich


Wait a sec... if I am reading that correctly, then existing lists 
would have been created using the standard templates which did not, 
obviously, have the htdig patch.  Newly created lists would be 
created against the now-patched htdig templates, and they should 
work properly.  Existing lists would have to have their templates 
patched accordingly.

Is that right?

If so, then it is likely that my installation IS working as 
expected.  I will have to delete my test list and recreate it, then 
run some tests and observe the results.

I'll let you know if I have any troubles there.

Thanks for your help!!

-Rich





--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + htDig

[Rich West]

Can you confirm you mean that the per-list htdig directories of the  
following form are being created:

$prefix/archives/private//htdig are being created

and that inside each of them there is a file named .conf

Is there also a file called rundig_last_run and a bunch of ,db files 
in  any of these per list directories?


Yes, all of that did get created.

and if I manually perform a search (htsearch -c )


While htsearch is used for index searching, it is not called directly  
from the form on the list TOC page with the integration but via the  
$prefix/Mailman/Cgi/mmsearch.py script.

When you run htsearch -c are you specifying the configuration file 
path  as:

$prefix/archives/private//htdig/.conf 


Yes.

, I do get output and results.


How have the search indexes being used by htsearch when you run it by  
hand been built? Did you run nightly_htdig by hand?


Yes.

What form do the URLs of search hits in the response returned by  
htsearch take? 


Well, they look like:
htsearch -c htdig/test.conf
Enter value for words: test
Content-type: text/html
Enter value for format:

Search results for 'test'



 http://lists.wesmo.com/mailman/htdig/test/2003-August/29.html";>[Test] 
test 


However, I am not getting the search form at the top of the 
index.html  page as is supposed to happen.  So, as expected, I cannot 
search via  the web interface. :(


The trigger for this form to be added to a list's archive TOC page is 
a  new message being sent to that particular list. And until 
nightly_htidg  has been run (which can be done from the command lien 
as well as by  cron) no per-list search indexes will be in existence. 
Are these  criteria being met and yet still the form does not appear 
on a list's  archive TOC page? 


Yes.  I first added the following to my mm_cfg.py:
USE_HTDIG = 0# 0 - don't use integrated htdig, 1 - use it
HTDIG_FILES_URL = '/htdig/'
HTDIG_CONF_LINK_DIR = os.path.join(VAR_PREFIX, 'archives', 'htdig')
HTDIG_HTSEARCH_PATH = '/usr/bin/htsearch'
HTDIG_RUNDIG_PATH = '/usr/bin/rundig'
Then I changed "USE_HTDIG" to 1 and restarted the qrunner (just for the 
sake of sanity. :).  I then sent a message to the test list.  At once I 
got the message that was sent to the test list, I checked out the 
archives/private/test directory and saw that the timestamp on index.html 
was updated, that a directory called htdig was created, and there were a 
bunch of files (db.*, rundig_last_run, and test.conf) in that htdig 
directory.

Does line 757 (or thereabouts) of 
$prefix/Mailman/Archiver/HyperArch.py  contain the following text:

d["htsearch"] = quick_maketext('TOC_htsearch.html', dict=h,

This is the code that generates the form that is added to the html of  
the list's TOC page a few lines further on. If this line is missing  
then the patching has failed somehow. 


I just checked, and it is there.  Is the TOC_htsearch.html file supposed 
to be in a particular location?  It is in templates/en/ right now...

I *believe* I followed the htdig docs to the letter,


Do you mean the INSTALL.htdig-mm document in the Mailman build  
directory? 


Yup.. that, and the docs on the website.

I swear it seems like I missed something simple (and stupid) here.. I 
even confirmed that the permissions on the directory and all files were 
set correctly (owner & group, too!).

Thanks!
-Rich
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + htDig

[Rich West]

Assuming you are using en as the list language and standard templates, 
can you take a look at the file

$prefix/templates/en/archtoc.html

line 16 should read:

%(htsearch)s 


Yup.. it is there..

This is where the results of the quick_maketext() on 
TOC_htsearch.html, that is the search form, get inserted into the list 
TOC page.

This line should have been inserted into archtoc.html by the 
htdig-2.1.2-0.4.patch

One possibility is that you may be using site, host or list specific 
templates and you generated these from the standard installed 
templates before applying the mailman-htdig and kindred patches. If so 
then these will not have been/could not be patched by the 
htdig-2.1.2-0.4.patch. In this case you will have to take a look at 
the  htdig-2.1.2-0.4.patch file for the template changes made by the 
patch and apply these by hand to your local variants of the templates. 
The patch file is a unified diff format and quite human legible.


Wait a sec... if I am reading that correctly, then existing lists would 
have been created using the standard templates which did not, obviously, 
have the htdig patch.  Newly created lists would be created against the 
now-patched htdig templates, and they should work properly.  Existing 
lists would have to have their templates patched accordingly.

Is that right?

If so, then it is likely that my installation IS working as expected.  I 
will have to delete my test list and recreate it, then run some tests 
and observe the results.

I'll let you know if I have any troubles there.

Thanks for your help!!

-Rich

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + htDig

[Richard Barrett]

On Friday, August 8, 2003, at 09:57  pm, Rich West wrote:



Yes.  I first added the following to my mm_cfg.py:
USE_HTDIG = 0# 0 - don't use integrated htdig, 1 - use it
HTDIG_FILES_URL = '/htdig/'
HTDIG_CONF_LINK_DIR = os.path.join(VAR_PREFIX, 'archives', 'htdig')
HTDIG_HTSEARCH_PATH = '/usr/bin/htsearch'
HTDIG_RUNDIG_PATH = '/usr/bin/rundig'
Then I changed "USE_HTDIG" to 1 and restarted the qrunner (just for 
the sake of sanity. :).  I then sent a message to the test list.  At 
once I got the message that was sent to the test list, I checked out 
the archives/private/test directory and saw that the timestamp on 
index.html was updated, that a directory called htdig was created, and 
there were a bunch of files (db.*, rundig_last_run, and test.conf) in 
that htdig directory.

Does line 757 (or thereabouts) of 
$prefix/Mailman/Archiver/HyperArch.py  contain the following text:

d["htsearch"] = quick_maketext('TOC_htsearch.html', dict=h,

This is the code that generates the form that is added to the html of 
 the list's TOC page a few lines further on. If this line is missing  
then the patching has failed somehow.


I just checked, and it is there.  Is the TOC_htsearch.html file 
supposed to be in a particular location?  It is in templates/en/ right 
now...

Assuming you are using en as the list language and standard templates, 
can you take a look at the file

$prefix/templates/en/archtoc.html

line 16 should read:

%(htsearch)s

This is where the results of the quick_maketext() on TOC_htsearch.html, 
that is the search form, get inserted into the list TOC page.

This line should have been inserted into archtoc.html by the 
htdig-2.1.2-0.4.patch

One possibility is that you may be using site, host or list specific 
templates and you generated these from the standard installed templates 
before applying the mailman-htdig and kindred patches. If so then these 
will not have been/could not be patched by the htdig-2.1.2-0.4.patch. 
In this case you will have to take a look at the  htdig-2.1.2-0.4.patch 
file for the template changes made by the patch and apply these by hand 
to your local variants of the templates. The patch file is a unified 
diff format and quite human legible.

Let me know what you find out/conclude.

I *believe* I followed the htdig docs to the letter,


Do you mean the INSTALL.htdig-mm document in the Mailman build  
directory?


Yup.. that, and the docs on the website.

I swear it seems like I missed something simple (and stupid) here.. I 
even confirmed that the permissions on the directory and all files 
were set correctly (owner & group, too!).

Thanks!
-Rich


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + htDig

[Richard Barrett]

On Friday, August 8, 2003, at 06:34  pm, Rich West wrote:

I realize this has come up often in the list, but hit a snag and was  
not sure where else to turn.  I couldn't find much in the archives  
that addressed this, but if it is a duplicate, please accept my  
apologies.

I've applied the htDig patches :
http://www.openinfo.co.uk/mailman/patches/728836/templates-2.1.2- 
0.1.patch
http://www.openinfo.co.uk/mailman/patches/732366/tz-2.1.2-0.2.patch
http://www.openinfo.co.uk/mailman/patches/730769/tcache-2.1.2-0.3.patch
http://www.openinfo.co.uk/mailman/patches/444879/indexing-2.1.2- 
0.1.patch
http://www.openinfo.co.uk/mailman/patches/444884/htdig-2.1.2-0.4.patch

And all were applied happily.

The indexing appears to be happening correctly on the filesystem level  
since the htdig directory is being created, the conf file is being  
created,
Can you confirm you mean that the per-list htdig directories of the  
following form are being created:

$prefix/archives/private//htdig are being created

and that inside each of them there is a file named .conf

Is there also a file called rundig_last_run and a bunch of ,db files in  
any of these per list directories?

and if I manually perform a search (htsearch -c )
While htsearch is used for index searching, it is not called directly  
from the form on the list TOC page with the integration but via the  
$prefix/Mailman/Cgi/mmsearch.py script.

When you run htsearch -c are you specifying the configuration file path  
as:

$prefix/archives/private//htdig/.conf

, I do get output and results.
How have the search indexes being used by htsearch when you run it by  
hand been built? Did you run nightly_htdig by hand?

What form do the URLs of search hits in the response returned by  
htsearch take?

However, I am not getting the search form at the top of the index.html  
page as is supposed to happen.  So, as expected, I cannot search via  
the web interface. :(
The trigger for this form to be added to a list's archive TOC page is a  
new message being sent to that particular list. And until nightly_htidg  
has been run (which can be done from the command lien as well as by  
cron) no per-list search indexes will be in existence. Are these  
criteria being met and yet still the form does not appear on a list's  
archive TOC page?

The index.html file *IS* being updated, but nothing is getting added  
to it (no search form)...

Does line 757 (or thereabouts) of $prefix/Mailman/Archiver/HyperArch.py  
contain the following text:

d["htsearch"] = quick_maketext('TOC_htsearch.html', dict=h,

This is the code that generates the form that is added to the html of  
the list's TOC page a few lines further on. If this line is missing  
then the patching has failed somehow.

I *believe* I followed the htdig docs to the letter,
Do you mean the INSTALL.htdig-mm document in the Mailman build  
directory?

 but it seems as if I am still missing something.

Check out my questions and get back to me.

Any help would be much appreciated!

Thanks!
-Rich


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + Htdig integration

[Richard Barrett]

On Thursday, July 24, 2003, at 09:00 AM, Chinbaatar Anar wrote:

Thank you, Richard

Now our mailing list with Htdig working great.

And we have about 4 mail customers.
They's addresses in our MySQL database server. If possible, I want to 
all of
these addresses subscribe to mailing list automatically.
Is this possible?
Any Idea?, any scripts?

With MM 2.1.2 there is a capability for integrating a database such as 
MySQL for membership management via the MemberAdaptor class defined in 
Mailman/MemberAdaptor.py

I have not gone with this sort of approach yet but it might be worth 
searching the mailman-users and mailman-developers list archives for 
posts on the topic if you are interested.

The "old-fashioned" way would be to extract your user list from the 
database and use the $prefix/bin/sync_members script, mayber do this 
using a cron script. How you implement this approach will depend on 
which is the "master" membership list, that held by Mailman or that 
held in the database. But thesync_members,ad_members, remove_members 
and list_members scripts give you the raw ability to manipulate list 
memberships.

Again check mailman list archives for posts on this topic.

Thank you,
Anar.Ch


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + Htdig integration

[Chinbaatar Anar]

Thank you, Richard

Now our mailing list with Htdig working great.

And we have about 4 mail customers.
They's addresses in our MySQL database server. If possible, I want to all of
these addresses subscribe to mailing list automatically.
Is this possible?
Any Idea?, any scripts?

Thank you,
Anar.Ch



- Original Message - 
From: "Richard Barrett" <[EMAIL PROTECTED]>
To: "Anar" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, July 24, 2003 9:58 AM
Subject: Re: [Mailman-Users] Mailman + Htdig integration


>
> On Thursday, July 24, 2003, at 01:22 AM, Anar wrote:
>
> > Hi,
> >
> > Thank you  Richard Barrett for your immediately answer.
> > I have fixed this error.
> >
> > Now mailman working properly. But in Archive page no search forms.
> > May i edit some html codes?
> >
>
> The htdig integration patch will not do anything until the USE_HTDIG
> Mailman configuration variable is set to true in
> $prefix/Mailman/mm_cfg.py
>
> The other htdig related MM configuration variables also need to be
> assigned in mm_cfg.py if the defaults set in Defaults.py do not match
> your system' setup.
>
> Do not forget to use mailmanctl restart after making these changes.
>
> Once USE_HTDIG is on then the first message to each list for which
> archiving is enabled will trigger:
>
> 1. the setup of the per-list htdig related setup for the list.
>
> 2. adding the search form to the list archive TOC page.
>
> Even with the search form in place, the list will not be searchable
> until the nightly_htdig cron job has been run to build the list's htdig
> search databases. You can run this script from the command line to get
> things started.
>
> If things do not work out like this then get back to me.
>
> Do check out the notes under the heading "htdig Permissions
> Considerations" in INSTALL.htdig-mm as this can cause problems when
> htdig's  rundig script is run for the first time.
>
> > Thank you,
> > Anar.Ch
>
>
>


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + Htdig integration

[Richard Barrett]

On Thursday, July 24, 2003, at 01:22 AM, Anar wrote:

Hi,

Thank you  Richard Barrett for your immediately answer.
I have fixed this error.
Now mailman working properly. But in Archive page no search forms.
May i edit some html codes?
The htdig integration patch will not do anything until the USE_HTDIG 
Mailman configuration variable is set to true in 
$prefix/Mailman/mm_cfg.py

The other htdig related MM configuration variables also need to be 
assigned in mm_cfg.py if the defaults set in Defaults.py do not match 
your system' setup.

Do not forget to use mailmanctl restart after making these changes.

Once USE_HTDIG is on then the first message to each list for which 
archiving is enabled will trigger:

1. the setup of the per-list htdig related setup for the list.

2. adding the search form to the list archive TOC page.

Even with the search form in place, the list will not be searchable 
until the nightly_htdig cron job has been run to build the list's htdig 
search databases. You can run this script from the command line to get 
things started.

If things do not work out like this then get back to me.

Do check out the notes under the heading "htdig Permissions 
Considerations" in INSTALL.htdig-mm as this can cause problems when 
htdig's  rundig script is run for the first time.

Thank you,
Anar.Ch


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman + Htdig integration

[Anar]

Hi, 

Thank you  Richard Barrett for your immediately answer.
I have fixed this error.

Now mailman working properly. But in Archive page no search forms.
May i edit some html codes? 

Thank you,
Anar.Ch




--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + Htdig

[Richard Barrett]

On Wednesday, July 23, 2003, at 05:01 AM, Chinbaatar Anar wrote:

Hello,

I want to install mailman with htdig integration.
And I patched mailman source by patches located in Source forge.
But after installation an error occuired and I  can't create new list.
Any help?

Thank you,
Anar.Ch
It looks as though you are running MM 2.1.2



Enter the email of the person running the list: [EMAIL PROTECTED]
Initial mailman password:
Traceback (most recent call last):
  File "/usr/local/mailman/bin/newlist", line 219, in ?
main()
  File "/usr/local/mailman/bin/newlist", line 160, in main
mlist.Create(listname, owner_mail, pw)
  File "/usr/local/mailman/Mailman/MailList.py", line 450, in Create
self.InitVars(name, admin, crypted_password)
  File "/usr/local/mailman/Mailman/MailList.py", line 368, in InitVars
baseclass.InitVars(self)
  File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 116, in 
InitVars
}, mlist=self))
  File "/usr/local/mailman/Mailman/Utils.py", line 497, in maketext
return findtext(templatefile, dict=dict, raw=raw, lang=lang, 
mlist=mlist)[0]
NameError: global name 'findtext' is not defined
Did you have any problems applying the tcache-2.1.2-0.3.patch patch 
file?

Did the patch program output any warning when you applied that patch to 
your MM build directory?

Can you confirm that line 384 of the file 
/usr/local/mailman/Mailman/Utils.py reads as follow patching of the 
build directory and install:

def findtext(templatefile, dict=None, raw=False, lang=None, mlist=None):

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman + Htdig

[Chinbaatar Anar]

Hello,

I want to install mailman with htdig integration.
And I patched mailman source by patches located in Source forge.
But after installation an error occuired and I  can't create new list.

Any help?

Thank you,
Anar.Ch



Enter the email of the person running the list: [EMAIL PROTECTED]
Initial mailman password:
Traceback (most recent call last):
  File "/usr/local/mailman/bin/newlist", line 219, in ?
main()
  File "/usr/local/mailman/bin/newlist", line 160, in main
mlist.Create(listname, owner_mail, pw)
  File "/usr/local/mailman/Mailman/MailList.py", line 450, in Create
self.InitVars(name, admin, crypted_password)
  File "/usr/local/mailman/Mailman/MailList.py", line 368, in InitVars
baseclass.InitVars(self)
  File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 116, in InitVars
}, mlist=self))
  File "/usr/local/mailman/Mailman/Utils.py", line 497, in maketext
return findtext(templatefile, dict=dict, raw=raw, lang=lang, mlist=mlist)[0]
NameError: global name 'findtext' is not defined
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman & htdig integration patch

[Richard Barrett]

On Friday, July 18, 2003, at 05:00 PM, Rob Brandt wrote:

I created a link from /apache/cgi-bin/htsearch to /opt/www/htdig/bin/  
and now it
works.  If this is not the right thing to do, let me know.

Rob


As long as the MM config variable HTDIG_HTSEARCH_PATH points to  
htsearch, all is well.

The need for this and other configuration issues is fully explained in  
the INSTALL.htdig-mm file added to your MM build directory by patch  
#444884

Quoting Rob Brandt <[EMAIL PROTECTED]>:

hmm, I have no file "/opt/www/htdig/bin/htsearch".  There's a bunch  
of other
stuff there, but not htsearch.

I had already made the change in $prefix/Mailman/mm_cfg.py, but hadn't
verified
that this file existed.
The log file says cause: htsearch

Rob

Quoting Richard Barrett <[EMAIL PROTECTED]>:

On Friday, July 18, 2003, at 02:01 PM, Rob Brandt wrote:

OK, I have it mostly installed and working.  Sending a message to my
test list
creates the search form at the top of the archives.  I've run the  
cron
job
manually, and the db's have been created without error in
/opt/www/htdig/common.
Have list specific db's also been created in:

  $prefix/archives/private//htdig.

But when I try to run a search, I get:

htdig Archives Access Failure
search failed -12-
This error is because mmsearch is not getting back any output from  
the
STDOUT of an htsearch instance that is has run as a sub-process to
search the list-specifc indexes.

Have you checked MM's error log ($prefix/logs/error) for some
indication of the problem?
Are you certain that the MM config variable HTDIG_HTSEARCH_PATH has  
the
right value assigned to match your htdig installation? I think you  
will
find the default value in $prefix/Mailman/Defaults.py is
'/usr/local/bin/htsearch' and you might want to re-assign that to
'/opt/www/htdig/bin/htsearch' in $prefix/Mailman/mm_cfg.py if you  
have
installed htdig in /opt/www/htdig.

Let us know how you get on.

If you want to make another attempt to access a list archive then go
via the
list users information page.
If this problem persists then please e-mail the following  
information
to the
[EMAIL PROTECTED]:

http://www.example.org/pipermail/testlist/
/mailman/mmsearch/testlist
What now?

Rob

Quoting Richard Barrett <[EMAIL PROTECTED]>:

On Thursday, July 17, 2003, at 03:12 PM, Rob Brandt wrote:

I am attempting to apply Richard Barrett's htdig integration  
patch to
my mailman
2.1.2 installation and am running into difficulties.

The patch pages say that I need to apply the "Archive indexer  
control
to improve
index" before applying the htdig patch, and the Archive patch  
says I
have to
apply  bug fix patch #728836 first. But I can't find any  
reference to
a #728836
anywhere in the tracking system, including patches, bugs or  
feature
requests.

Try looking here:

http://sourceforge.net/tracker/
index.php?func=detail&aid=728836&group_id=103&atid=100103
Has this been incorporated in 2.1.2?  I tried applying the Archive
indexer patch
directly, but it failed.
At times patches, including #728836, get included in the CVS in
preparation for the next MM release (2.1.3 I guess) and are marked  
as
closed although they are still necessary for the current stable
release
(2.1.2 in the case of #728836). The patches are still on  
sourceforge.

The INSTALL.htdig-mm file in the #444884 patch contains the URLs of
all
the necessary precursor patches on soruceforge. You can also view  
that
file content here:

http://www.openinfo.co.uk/mailman/patches/444884/install.html

Help?

Thanks

Rob








--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/bronto%40csd- 
bes.net



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/ 
r.barrett%40openinfo.co.uk



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman & htdig integration patch

[Rob Brandt]

I created a link from /apache/cgi-bin/htsearch to /opt/www/htdig/bin/ and now it
works.  If this is not the right thing to do, let me know.

Rob



Quoting Rob Brandt <[EMAIL PROTECTED]>:

> hmm, I have no file "/opt/www/htdig/bin/htsearch".  There's a bunch of other
> stuff there, but not htsearch.
>
> I had already made the change in $prefix/Mailman/mm_cfg.py, but hadn't
> verified
> that this file existed.
>
> The log file says cause: htsearch
>
> Rob
>
>
> Quoting Richard Barrett <[EMAIL PROTECTED]>:
>
> >
> > On Friday, July 18, 2003, at 02:01 PM, Rob Brandt wrote:
> >
> > > OK, I have it mostly installed and working.  Sending a message to my
> > > test list
> > > creates the search form at the top of the archives.  I've run the cron
> > > job
> > > manually, and the db's have been created without error in
> > > /opt/www/htdig/common.
> >
> > Have list specific db's also been created in:
> >
> >   $prefix/archives/private//htdig.
> >
> > > But when I try to run a search, I get:
> > >
> > > htdig Archives Access Failure
> > > search failed -12-
> > >
> >
> > This error is because mmsearch is not getting back any output from the
> > STDOUT of an htsearch instance that is has run as a sub-process to
> > search the list-specifc indexes.
> >
> > Have you checked MM's error log ($prefix/logs/error) for some
> > indication of the problem?
> >
> > Are you certain that the MM config variable HTDIG_HTSEARCH_PATH has the
> > right value assigned to match your htdig installation? I think you will
> > find the default value in $prefix/Mailman/Defaults.py is
> > '/usr/local/bin/htsearch' and you might want to re-assign that to
> > '/opt/www/htdig/bin/htsearch' in $prefix/Mailman/mm_cfg.py if you have
> > installed htdig in /opt/www/htdig.
> >
> > Let us know how you get on.
> >
> > > If you want to make another attempt to access a list archive then go
> > > via the
> > > list users information page.
> > >
> > > If this problem persists then please e-mail the following information
> > > to the
> > > [EMAIL PROTECTED]:
> > >
> > > http://www.example.org/pipermail/testlist/
> > > /mailman/mmsearch/testlist
> > >
> > > What now?
> > >
> > > Rob
> > >
> > >
> > > Quoting Richard Barrett <[EMAIL PROTECTED]>:
> > >
> > >>
> > >> On Thursday, July 17, 2003, at 03:12 PM, Rob Brandt wrote:
> > >>
> > >>> I am attempting to apply Richard Barrett's htdig integration patch to
> > >>> my mailman
> > >>> 2.1.2 installation and am running into difficulties.
> > >>>
> > >>> The patch pages say that I need to apply the "Archive indexer control
> > >>> to improve
> > >>> index" before applying the htdig patch, and the Archive patch says I
> > >>> have to
> > >>> apply  bug fix patch #728836 first. But I can't find any reference to
> > >>> a #728836
> > >>> anywhere in the tracking system, including patches, bugs or feature
> > >>> requests.
> > >>>
> > >>
> > >> Try looking here:
> > >>
> > >> http://sourceforge.net/tracker/
> > >> index.php?func=detail&aid=728836&group_id=103&atid=100103
> > >>
> > >>> Has this been incorporated in 2.1.2?  I tried applying the Archive
> > >>> indexer patch
> > >>> directly, but it failed.
> > >>>
> > >>
> > >> At times patches, including #728836, get included in the CVS in
> > >> preparation for the next MM release (2.1.3 I guess) and are marked as
> > >> closed although they are still necessary for the current stable
> > >> release
> > >> (2.1.2 in the case of #728836). The patches are still on sourceforge.
> > >>
> > >> The INSTALL.htdig-mm file in the #444884 patch contains the URLs of
> > >> all
> > >> the necessary precursor patches on soruceforge. You can also view that
> > >> file content here:
> > >>
> > >> http://www.openinfo.co.uk/mailman/patches/444884/install.html
> > >>
> > >>> Help?
> > >>>
> > >>> Thanks
> > >>>
> > >>> Rob
> > >>
> > >>
> > >
> > >
> >
> >
>
>
>
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> 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: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/bronto%40csd-bes.net
>



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman & htdig integration patch

[Rob Brandt]

hmm, I have no file "/opt/www/htdig/bin/htsearch".  There's a bunch of other
stuff there, but not htsearch.

I had already made the change in $prefix/Mailman/mm_cfg.py, but hadn't verified
that this file existed.

The log file says cause: htsearch

Rob


Quoting Richard Barrett <[EMAIL PROTECTED]>:

>
> On Friday, July 18, 2003, at 02:01 PM, Rob Brandt wrote:
>
> > OK, I have it mostly installed and working.  Sending a message to my
> > test list
> > creates the search form at the top of the archives.  I've run the cron
> > job
> > manually, and the db's have been created without error in
> > /opt/www/htdig/common.
>
> Have list specific db's also been created in:
>
>   $prefix/archives/private//htdig.
>
> > But when I try to run a search, I get:
> >
> > htdig Archives Access Failure
> > search failed -12-
> >
>
> This error is because mmsearch is not getting back any output from the
> STDOUT of an htsearch instance that is has run as a sub-process to
> search the list-specifc indexes.
>
> Have you checked MM's error log ($prefix/logs/error) for some
> indication of the problem?
>
> Are you certain that the MM config variable HTDIG_HTSEARCH_PATH has the
> right value assigned to match your htdig installation? I think you will
> find the default value in $prefix/Mailman/Defaults.py is
> '/usr/local/bin/htsearch' and you might want to re-assign that to
> '/opt/www/htdig/bin/htsearch' in $prefix/Mailman/mm_cfg.py if you have
> installed htdig in /opt/www/htdig.
>
> Let us know how you get on.
>
> > If you want to make another attempt to access a list archive then go
> > via the
> > list users information page.
> >
> > If this problem persists then please e-mail the following information
> > to the
> > [EMAIL PROTECTED]:
> >
> > http://www.example.org/pipermail/testlist/
> > /mailman/mmsearch/testlist
> >
> > What now?
> >
> > Rob
> >
> >
> > Quoting Richard Barrett <[EMAIL PROTECTED]>:
> >
> >>
> >> On Thursday, July 17, 2003, at 03:12 PM, Rob Brandt wrote:
> >>
> >>> I am attempting to apply Richard Barrett's htdig integration patch to
> >>> my mailman
> >>> 2.1.2 installation and am running into difficulties.
> >>>
> >>> The patch pages say that I need to apply the "Archive indexer control
> >>> to improve
> >>> index" before applying the htdig patch, and the Archive patch says I
> >>> have to
> >>> apply  bug fix patch #728836 first. But I can't find any reference to
> >>> a #728836
> >>> anywhere in the tracking system, including patches, bugs or feature
> >>> requests.
> >>>
> >>
> >> Try looking here:
> >>
> >> http://sourceforge.net/tracker/
> >> index.php?func=detail&aid=728836&group_id=103&atid=100103
> >>
> >>> Has this been incorporated in 2.1.2?  I tried applying the Archive
> >>> indexer patch
> >>> directly, but it failed.
> >>>
> >>
> >> At times patches, including #728836, get included in the CVS in
> >> preparation for the next MM release (2.1.3 I guess) and are marked as
> >> closed although they are still necessary for the current stable
> >> release
> >> (2.1.2 in the case of #728836). The patches are still on sourceforge.
> >>
> >> The INSTALL.htdig-mm file in the #444884 patch contains the URLs of
> >> all
> >> the necessary precursor patches on soruceforge. You can also view that
> >> file content here:
> >>
> >> http://www.openinfo.co.uk/mailman/patches/444884/install.html
> >>
> >>> Help?
> >>>
> >>> Thanks
> >>>
> >>> Rob
> >>
> >>
> >
> >
>
>



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman & htdig integration patch

[Richard Barrett]

On Friday, July 18, 2003, at 02:01 PM, Rob Brandt wrote:

OK, I have it mostly installed and working.  Sending a message to my 
test list
creates the search form at the top of the archives.  I've run the cron 
job
manually, and the db's have been created without error in
/opt/www/htdig/common.
Have list specific db's also been created in:

 $prefix/archives/private//htdig.

But when I try to run a search, I get:

htdig Archives Access Failure
search failed -12-
This error is because mmsearch is not getting back any output from the 
STDOUT of an htsearch instance that is has run as a sub-process to 
search the list-specifc indexes.

Have you checked MM's error log ($prefix/logs/error) for some 
indication of the problem?

Are you certain that the MM config variable HTDIG_HTSEARCH_PATH has the 
right value assigned to match your htdig installation? I think you will 
find the default value in $prefix/Mailman/Defaults.py is 
'/usr/local/bin/htsearch' and you might want to re-assign that to 
'/opt/www/htdig/bin/htsearch' in $prefix/Mailman/mm_cfg.py if you have 
installed htdig in /opt/www/htdig.

Let us know how you get on.

If you want to make another attempt to access a list archive then go 
via the
list users information page.

If this problem persists then please e-mail the following information 
to the
[EMAIL PROTECTED]:

http://www.example.org/pipermail/testlist/
/mailman/mmsearch/testlist
What now?

Rob

Quoting Richard Barrett <[EMAIL PROTECTED]>:

On Thursday, July 17, 2003, at 03:12 PM, Rob Brandt wrote:

I am attempting to apply Richard Barrett's htdig integration patch to
my mailman
2.1.2 installation and am running into difficulties.
The patch pages say that I need to apply the "Archive indexer control
to improve
index" before applying the htdig patch, and the Archive patch says I
have to
apply  bug fix patch #728836 first. But I can't find any reference to
a #728836
anywhere in the tracking system, including patches, bugs or feature
requests.
Try looking here:

http://sourceforge.net/tracker/
index.php?func=detail&aid=728836&group_id=103&atid=100103
Has this been incorporated in 2.1.2?  I tried applying the Archive
indexer patch
directly, but it failed.
At times patches, including #728836, get included in the CVS in
preparation for the next MM release (2.1.3 I guess) and are marked as
closed although they are still necessary for the current stable 
release
(2.1.2 in the case of #728836). The patches are still on sourceforge.

The INSTALL.htdig-mm file in the #444884 patch contains the URLs of 
all
the necessary precursor patches on soruceforge. You can also view that
file content here:

http://www.openinfo.co.uk/mailman/patches/444884/install.html

Help?

Thanks

Rob






--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman & htdig integration patch

[Rob Brandt]

OK, I have it mostly installed and working.  Sending a message to my test list
creates the search form at the top of the archives.  I've run the cron job
manually, and the db's have been created without error in
/opt/www/htdig/common.  But when I try to run a search, I get:

htdig Archives Access Failure
search failed -12-

If you want to make another attempt to access a list archive then go via the
list users information page.

If this problem persists then please e-mail the following information to the
[EMAIL PROTECTED]:

http://www.example.org/pipermail/testlist/
/mailman/mmsearch/testlist

What now?

Rob


Quoting Richard Barrett <[EMAIL PROTECTED]>:

>
> On Thursday, July 17, 2003, at 03:12 PM, Rob Brandt wrote:
>
> > I am attempting to apply Richard Barrett's htdig integration patch to
> > my mailman
> > 2.1.2 installation and am running into difficulties.
> >
> > The patch pages say that I need to apply the "Archive indexer control
> > to improve
> > index" before applying the htdig patch, and the Archive patch says I
> > have to
> > apply  bug fix patch #728836 first. But I can't find any reference to
> > a #728836
> > anywhere in the tracking system, including patches, bugs or feature
> > requests.
> >
>
> Try looking here:
>
> http://sourceforge.net/tracker/
> index.php?func=detail&aid=728836&group_id=103&atid=100103
>
> > Has this been incorporated in 2.1.2?  I tried applying the Archive
> > indexer patch
> > directly, but it failed.
> >
>
> At times patches, including #728836, get included in the CVS in
> preparation for the next MM release (2.1.3 I guess) and are marked as
> closed although they are still necessary for the current stable release
> (2.1.2 in the case of #728836). The patches are still on sourceforge.
>
> The INSTALL.htdig-mm file in the #444884 patch contains the URLs of all
> the necessary precursor patches on soruceforge. You can also view that
> file content here:
>
> http://www.openinfo.co.uk/mailman/patches/444884/install.html
>
> > Help?
> >
> > Thanks
> >
> > Rob
>
>



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman & htdig integration patch

[Richard Barrett]

On Thursday, July 17, 2003, at 03:12 PM, Rob Brandt wrote:

I am attempting to apply Richard Barrett's htdig integration patch to  
my mailman
2.1.2 installation and am running into difficulties.

The patch pages say that I need to apply the "Archive indexer control  
to improve
index" before applying the htdig patch, and the Archive patch says I  
have to
apply  bug fix patch #728836 first. But I can't find any reference to  
a #728836
anywhere in the tracking system, including patches, bugs or feature  
requests.

Try looking here:

http://sourceforge.net/tracker/ 
index.php?func=detail&aid=728836&group_id=103&atid=100103

Has this been incorporated in 2.1.2?  I tried applying the Archive  
indexer patch
directly, but it failed.

At times patches, including #728836, get included in the CVS in  
preparation for the next MM release (2.1.3 I guess) and are marked as  
closed although they are still necessary for the current stable release  
(2.1.2 in the case of #728836). The patches are still on sourceforge.

The INSTALL.htdig-mm file in the #444884 patch contains the URLs of all  
the necessary precursor patches on soruceforge. You can also view that  
file content here:

http://www.openinfo.co.uk/mailman/patches/444884/install.html

Help?

Thanks

Rob


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman & htdig integration patch

[Rob Brandt]

I am attempting to apply Richard Barrett's htdig integration patch to my mailman
2.1.2 installation and am running into difficulties.

The patch pages say that I need to apply the "Archive indexer control to improve
index" before applying the htdig patch, and the Archive patch says I have to
apply  bug fix patch #728836 first. But I can't find any reference to a #728836
anywhere in the tracking system, including patches, bugs or feature requests.

Has this been incorporated in 2.1.2?  I tried applying the Archive indexer patch
directly, but it failed.

Help?

Thanks

Rob

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] mailman-htdig integration patch update

[Richard Barrett]

Following input from and a fine diagnosis of a problem by Barry Shaw 
<[EMAIL PROTECTED]> I have uploaded to sourceforge an update to my 
mailman-htdig integration patch #444884 as file htdig-2.1.2-0.4.patch.gz:

http://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103

The problem was introduced with patch version htdig-2.1.1-0.2.patch.gz.

It does not affect MM 2.0.x versions of the patch.

The problem is only visible if you are not using the http scheme (typically 
because you are using https) in the URLs for accessing Mailman.

In that case, htdig archives searches lead to mmsearch.py reporting an 
error citing the "" and ".htaccess" in the output.

Luckily, or maybe unluckily, the problem is not visible with http URLs 
which is why I missed it. The fault is present but does manifest any 
undesirable effects

Sorry for the sloppy testing. Hopefully I won't have broken anything else 
fixing this latest problem. Let me know if you spot any other problems with 
the patch.

--
Richard Barrett  http://www.openinfo.co.uk
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] mailman-htdig integration patch update

[Richard Barrett]

I have posted on sourceforge revisions of these two patches for application 
to MM 2.1.1. There are no functional changes and the changes is only to 
stop warnings about offsets in files when the 2.1 versions of the patches 
are applied

Patch #444879: Improved archiver indexcontrol
Patch #444884: Mailman/htdig integration

The following two precursor patches have not been updated and the 2.1 final 
versions of them should not generate any warning when being applied to MM 
2.1.1:

Patch #661138: Corrects HTML template defects

Patch #668685: Corrects an error in SystemExit exception handling by 
$prefix/script/driver


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman/htdig Success and a question or 3..

[Richard Barrett]

At 05:18 08/01/2003, Glenn Sieb wrote:

First I just want to say:

MAILMAN ROCKS! :)

I managed to get 2.1 and htdig all running together and working 
peachykeen... :) it's a beautiful thing! My monthly mailers all work now, 
creating lists from the webinterface works, etc!

However--a suggestion? In Defaults.py, once all the patches are added, we 
now see:

ARCHIVE_INDEXING_ENABLE = ''
ARCHIVE_INDEXING_DISABLE = ''
# htdig integration parameters
# if you set USE_HTDIG then you must also set HTDIG_MAILMAN_LINK
# and HTDIG_RUNDIG_PATH to suit your htdig installation, for instance:
# HTDIG_MAILMAN_LINK = 'htdig-mailman'
# HTDIG_RUNDIG_PATH = '/usr/bin/rundig'
USE_HTDIG = 0# 0 - don't use integrated htdig, 1 - use it
HTDIG_ARCHIVE_URL = '/mailman/htdig/' # must end in a slash
HTDIG_SEARCH_URL = '/cgi-bin/htsearch'
HTDIG_FILES_URL = '/htdig/'
HTDIG_CONF_LINK_DIR = os.path.join(VAR_PREFIX, 'archives', 'htdig')
HTDIG_MAILMAN_LINK = 'htdig-mailman'
HTDIG_RUNDIG_PATH = '/usr/local/bin/rundig'

Now.. as far as I can tell, HTDIG_ARCHIVE_URL is just wrong. 
/mailman/htdig/ isn't the location of archives using Pipermail.. it's 
/mailman/pipermail ... So I'm wondering:

1) Am I just reading this wrong? Is my setup somehow b0rken? I had to set 
HTDIG_ARCHIVE_URL = '/mailman/pipermail/' in mm_cfg.py

/mailman/htdig/ is correct. This is explained in the file 
$build/INSTALL.htdig-mm installed by the #444884 patch. In part it says:


$prefix/cgi-bin/htdig
$prefix/Mailman/Cgi/htdig.py

these are a CGI script and its wrapper, which is always on the path
of URLs returned from searches of htdig indices. The script provides
secure access to such URLs in the same way that the
$prefix/cgi-bin/private and $prefix/Mailman/Cgi/private.py. htdig.py
ensures private archives are kept private, applying the same
criteria for permitting access as private.py, and delivering
material from public archives without demanding any authentication.



2) What about private archives? Can there be (maybe in a future version) 
HTDIG_PRIVATE_ARCHIVE_URL ? As it stands, I have to manually edit the 
.conf to fix it for private archives... hardly a big deal, but 
I'm just the curious type...

3) I'm using the postfix-to-mailman.py (modified to work with 2.1--easy 
enough, if anyone would like a copy, I'll happily post it), and do not use 
mailman's aliases file--is there a way to stop mailman from writing to 
this data/aliases file? Not a biggie, I'm still just a curious guy :)

Again... you guys rock!!! :)

Thanks,
Glenn
---


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] Mailman/htdig Success and a question or 3..

[Glenn Sieb]

At 07:21 AM 1/8/2003 +, Richard Barrett posted the following...

/mailman/htdig/ is correct. This is explained in the file 
$build/INSTALL.htdig-mm installed by the #444884 patch. In part it says:

*duck* sorry, my bad :)



$prefix/cgi-bin/htdig
$prefix/Mailman/Cgi/htdig.py



Ok.. I've removed my HTDIG_ARCHIVE_URL from my mm_cfg.py.. now I've 
restarted Apache, and gone to a list with archives...

When I search, I get htdig's nice search results.. and when I hover over a 
link:

https://www.wingfoot.org/mailman/htdig/testing5/2003-January.txt

That's the link that shows.. but when I click on it I get:


Internal Server Error

The server encountered an internal error or misconfiguration and was unable 
to complete your request.

Please contact the server administrator, [EMAIL PROTECTED] and 
inform them of the time the error occurred, and anything you might have 
done that may have caused the error.

More information about this error may be available in the server error log.

My /var/log/httpd-error.log shows:

[Thu Jan  9 00:30:34 2003] [error] [client 67.85.96.168] Premature end of 
script headers: /usr/local/mailman/cgi-bin/htdig

I've searched the FAQ with no luck.. :-/

(This is all why I thought I "fixed" it by changing 
HTDIG_ARCHIVE_URL...sorry for the confusion...)

Anyway--I really do appreciate all the help you all have been :) This list 
is a great resource!

Glenn


---
The original portions of this message are the copyright of the author
(c)1998-2002 Glenn E. Sieb.ICQ UIN: 300395IRC Nick: Rainbear

"Religion is for those who do what they are told regardless of what is right.
Spirituality is for those who do what is right regardless of what
they are told." -- unattributed



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman/htdig Success and a question or 3..

[Glenn Sieb]

First I just want to say:

MAILMAN ROCKS! :)

I managed to get 2.1 and htdig all running together and working 
peachykeen... :) it's a beautiful thing! My monthly mailers all work now, 
creating lists from the webinterface works, etc!

However--a suggestion? In Defaults.py, once all the patches are added, we 
now see:

ARCHIVE_INDEXING_ENABLE = ''
ARCHIVE_INDEXING_DISABLE = ''
# htdig integration parameters
# if you set USE_HTDIG then you must also set HTDIG_MAILMAN_LINK
# and HTDIG_RUNDIG_PATH to suit your htdig installation, for instance:
# HTDIG_MAILMAN_LINK = 'htdig-mailman'
# HTDIG_RUNDIG_PATH = '/usr/bin/rundig'
USE_HTDIG = 0# 0 - don't use integrated htdig, 1 - use it
HTDIG_ARCHIVE_URL = '/mailman/htdig/' # must end in a slash
HTDIG_SEARCH_URL = '/cgi-bin/htsearch'
HTDIG_FILES_URL = '/htdig/'
HTDIG_CONF_LINK_DIR = os.path.join(VAR_PREFIX, 'archives', 'htdig')
HTDIG_MAILMAN_LINK = 'htdig-mailman'
HTDIG_RUNDIG_PATH = '/usr/local/bin/rundig'

Now.. as far as I can tell, HTDIG_ARCHIVE_URL is just wrong. 
/mailman/htdig/ isn't the location of archives using Pipermail.. it's 
/mailman/pipermail ... So I'm wondering:

1) Am I just reading this wrong? Is my setup somehow b0rken? I had to set 
HTDIG_ARCHIVE_URL = '/mailman/pipermail/' in mm_cfg.py

2) What about private archives? Can there be (maybe in a future version) 
HTDIG_PRIVATE_ARCHIVE_URL ? As it stands, I have to manually edit the 
.conf to fix it for private archives... hardly a big deal, but 
I'm just the curious type...

3) I'm using the postfix-to-mailman.py (modified to work with 2.1--easy 
enough, if anyone would like a copy, I'll happily post it), and do not use 
mailman's aliases file--is there a way to stop mailman from writing to this 
data/aliases file? Not a biggie, I'm still just a curious guy :)

Again... you guys rock!!! :)

Thanks,
Glenn
---

The original portions of this message are the copyright of the author
(c)1998-2002 Glenn E. Sieb.ICQ UIN: 300395IRC Nick: Rainbear

"Religion is for those who do what they are told regardless of what is right.
Spirituality is for those who do what is right regardless of what
they are told." -- unattributed



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman htdig integration patches

[Richard Barrett]

If anyone wants them, I have just posted MM 2.1b5 compatibility updates to 
the Mailman htdig integration patches

http://sourceforge.net/tracker/index.php?func=detail&aid=444879&group_id=103&atid=300103

http://sourceforge.net/tracker/index.php?func=detail&aid=444884&group_id=103&atid=300103


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman + htdig integration howto

[Odhiambo Washington]

* curt brune <[EMAIL PROTECTED]> [20020828 03:29]: wrote:
> Is there a HOWTO for integrating htdig with Mailman ?

Yes, there is, although I don't remember where it resides, but I have attached
it.



cheers
   - wash 
+--+-+
Odhiambo Washington, [EMAIL PROTECTED]  . WANANCHI ONLINE LTD (Nairobi, KE)  |
http://ns2.wananchi.com/~wash/  . 1ere Etage, Loita Hse, Loita St.,  |
GSM: (+254) 722 743 223 . # 10286, 00100 NAIROBI |
+-+--+
"Oh My God! They killed init! You Bastards!"  
 --from a /. post


Installing and Using the Mailman-htdig Integration
==

This patch:

http://sourceforge.net/tracker/index.php?func=detail&aid=444884&group_id=103&atid=300103

Contents


Prereqisites
Compatibility
History
Introduction
Installing and Building Mailman with this patch
What is Installed by the Patch
Configuration of Mailman-htdig Integration
Health Warning on the packet!
Starting from Scratch (Again)
General
htdig Permissions Considerations
Local htdig Configuration
Remote htdig Configuration
Upgrading an Existing Standard Mailman Installation
Changing from local to remote htdig or vice versa
Coping with htdig Upgrades
Changing the Addressing Scheme of your web_page_url
Operational Information
Notes and Warnings
Contributors
Appendices
Appendix 1 -Technique for htdigging when Mailman's DEFAULT_URL uses the
https 

Prerequisites


Prior to installing this patch you should also have installed the patch that 
provides enhanced indexing of Mailman archives see:

http://sourceforge.net/tracker/index.php?func=detail&aid=444879&group_id=103&atid=300103

You must have a working installation of htdig with htsearch available via CGI on 
your HTTP server installed on either the machine on which you are running 
Mailman or on another machine which has access to Mailman list archives via NFS 
or some similarly competent network file sharing scheme.

Regardless of how you configure things to provide Mailman's Web UI, if its gives 
normal operation of the /mailman/private CGI script for providing access to 
private list archives, it should also support access to htdig search results via 
the /mailman/htdig CGI script.

Compatibility
=

htdig-2.0.12-0.1.patch - Mailman 2.0.12

htdig-2.0.11-0.1.patch - Mailman 2.0.11

htdig-2.0.10-0.2.patch - Mailman 2.0.10

htdig-2.0.10-0.1.patch - Mailman 2.0.10

htdig-2.0.9-0.1.patch - Mailman 2.0.9

htdig-2.0.8-0.1.patch - Mailman 2.0.8, 2.0.7, 2.0.6 and probably 2.0.3, 2.0.4
and 2.0.5

History
===

Previous versions - original versions of this patch provided most of the 
features described here with the main exception being support for remote htdig, 
that is running htdig on a different system to Mailman. They were also baked in 
some configuration assumptions, which are now configurable.

htdig-2.0.12-0.1.patch - latest version:

1. Rebuilt patch to get no-comment application on Mailman 2.0.12

2. Added HTDIG_EXTRAS facility to allow arbitrary htdig configuration
   parameters to be specified for addition to every htdig.conf file
   created i.e. site wide additions. See comments below on the use of
   HTDIG_EXTRAS.

htdig-2.0.11-0.1.patch:

1. No substantive change. Simply rebuilt patch to get no-comment application
   on Mailman 2.0.11

htdig-2.0.10-0.2.patch:

1. Python 2.2 compatibility fixes to nightly_htdig cron script and its
   relatives. Doing import * inside a function removed.

2. Added note on potential problems with htdig and file permissions.

htdig-2.0.10-0.1.patch:

1. change in src/Makefile.in to get clean patch application to MM 2.0.10

htdig-2.0.9-0.1.patch:

1. minor cosmetic changes to get clean patch application to MM 2.0.9

htdig-2.0.8-0.1.patch:

1. resolves a problem with the integration of htdig when the web_page_url
for a list, which is usually the same as DEFAULT_URL from either
$prefix/Mailman/Defaults.py or $prefix/Mailman/mm_cfg.py, doesn't use the http
addressing scheme. This arises because htdig will only build indices if the URLs
for pages use the http addressing scheme. There is a work-around for this
problem posted in htdig's mail archives - see the copy in Appendix 1 to this
document.

2. This patch revision implements the solution documented in that e-mail. If
non-http URLs are used by the web_page_url of a list an additional htdig
configuration file for use by htsearch is generated.

3. In all other respects the operation of the Mailman-htdig integration
remains unchanged. There is no benefit in upgrading to this revised patch unless
you need to use other than http addressing in your DEFAULT_URL or set other than
http addressing in the

Re: [Mailman-Users] Mailman + htdig integration howto

[Richard Barrett]

At 10:51 27/08/2002 -0700, curt brune wrote:
>Is there a HOWTO for integrating htdig with Mailman ?
>
>Please cc me.
>
>Cheers,
>Curt

See 
http://www.python.org/cgi-bin/faqw-mm.py?query=htdig&querytype=simple&casefold=yes&req=search
 
for general search suggestions.

Applied together the following two MM patches do a fairly comprehensive job 
of adding htdig search to mail archives produced by MM's internal archiver.

The second patch - 444884 - adds a file INSTALL.htdig-mm you may find useful

http://sourceforge.net/tracker/index.php?func=detail&aid=444879&group_id=103&atid=300103
 

http://sourceforge.net/tracker/index.php?func=detail&aid=444884&group_id=103&atid=300103


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

[Mailman-Users] Mailman + htdig integration howto

[curt brune]

Is there a HOWTO for integrating htdig with Mailman ?

Please cc me.

Cheers,
Curt

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

[Mailman-Users] mailman-htdig integration patch for MM 2.1b3

[Richard Barrett]

The first version of this MM 2.1b3 compatible patch (htdig-2.1b3-0.1.patch) 
that I uploaded yesterday introduces a syntax error at line 721 of 
$prefix/Mailman/Archiver/HyperArch.py

The effect of this error may be to introduce copious error logging from the 
ArchRunner qrunner.

Anybody affected has my apologies.

A revised patch (htdig-2.1b3-0.2.patch) has now been uploaded which fixes 
this error.

See 
http://sourceforge.net/tracker/index.php?func=detail&aid=444884&group_id=103&atid=300103


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] Mailman + HTDig cron issue

[Richard Barrett]

At 08:40 26/07/2002 +0300, Odhiambo Washington wrote:

>Since I am not a python coder, I thought I may ask the list about this:
>
>
>- Forwarded message from Cron Daemon  -
>
>Subject: Cron  /usr/local/bin/python2.2 -S 
>/usr/local/mailman/cron/nightly_htdig
>
>Traceback (most recent call last):
>   File "/usr/local/mailman/cron/nightly_htdig", line 52, in ?
> from Mailman.Archiver import HyperArch
>   File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 855
> "htdig_extras" = mm_cfg.HTDIG_EXTRAS,
>^
>SyntaxError: invalid syntax
>
>- End forwarded message -
>

This is coding error that crept into the initial version of the 
mailman-htdig integration patch 444884 when it was built.  There is a 
replacement version posted as htdig-2.0.12-0.2.patch at 
http://sourceforge.net/tracker/index.php?func=detail&aid=444884&group_id=103&atid=300103
 
and a comment saying the earlier version htdig-2.0.12-0.1.patch has an 
error in it and should not be used.

Alternatively edit the line in error to read:

 "htdig_extras": mm_cfg.HTDIG_EXTRAS,


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] Mailman + HTDig cron issue

[Odhiambo Washington]

* John W Baxter <[EMAIL PROTECTED]> [20020728 09:01]: wrote:
> At 8:40 +0300 7/26/2002, Odhiambo Washington wrote:
> >  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 855
> >"htdig_extras" = mm_cfg.HTDIG_EXTRAS,
> 
> The quotes around htdig_extras to the left of the = are highly suspect.
> 
> But I don't use htdig with Mailman, so I don't know what I'm talking about.
> (I do know Python, which is what makes me suspect the quotes.)

I did not get any errors after I substitued : for the = so I guess it's okay
but again I don't know Python.



cheers
   - wash 
--+-
 Odhiambo Washington, [EMAIL PROTECTED] . WANANCHI ONLINE LTD (Nairobi, KE)
 http://ns2.wananchi.com/~wash/ . 1ere Etage, Loita Hse, Loita St.,
 GSM: (254) 722 743 223 . # 10286, 00100 NAIROBI
--+-
"Oh My God! They killed init! You Bastards!"  
 --from a /. post

++
``That Ariel Sharon. Boy, he sure is controversial.
  Most Western countries would have to have a military coup
  before they enjoyed a leader of that caliber.'' (Sydney Webb)

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] Mailman + HTDig cron issue

[John W Baxter]

At 8:40 +0300 7/26/2002, Odhiambo Washington wrote:
>  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 855
>"htdig_extras" = mm_cfg.HTDIG_EXTRAS,

The quotes around htdig_extras to the left of the = are highly suspect.

But I don't use htdig with Mailman, so I don't know what I'm talking about.
(I do know Python, which is what makes me suspect the quotes.)

  --John

-- 
John Baxter   [EMAIL PROTECTED]  Port Ludlow, WA, USA

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] Mailman + HTDig Intergration

[Richard Barrett]

At 09:34 25/07/2002 -0700, bronto wrote:
>>Use the versions of these patches for MM 2.0.11 ...
>
>
>Is there a solution for v2.1b2 yet?

I've posted several versions of the patches 444879 and 444884  for MM 2.1 
but keeping up the CVS changes was becoming unworkable.

I'll try and rebuild versions of the patches that are compatible with the 
MM 2.1b2 from sourceforge over the next 24 hours and upload them.

I'll email you when I have done this.



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] Mailman + HTDig Intergration

[bronto]

>Use the versions of these patches for MM 2.0.11 ...


Is there a solution for v2.1b2 yet?

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] Mailman + HTDig Intergration

[Richard Barrett]

At 19:47 24/07/2002 +0300, Odhiambo Washington wrote:

>Hello List Managers,
>
>Does anyone know where I can find a clean HOWTO on intergrating Mailman
>and HTDig for searchable archives. I am running Mailman-2.0.12 from
>today ;-) but would like to go right ahead and have a searchable archive
>like the one list.org has. Or am I being over ambitious?
>
>Thanking you.
>
>
>-Wash

The following patches integrate the htdig (http://www.htdig.org/) search 
engine with Mailman.

http://sourceforge.net/tracker/index.php?func=detail&aid=444879&group_id=103&atid=300103

http://sourceforge.net/tracker/index.php?func=detail&aid=444884&group_id=103&atid=300103

Use the versions of these patches for MM 2.0.11 When you apply them to MM 
2.0.12 build directory you will get one complaint from patch 444884 which 
you I think you can safely ignore. When I have time I'll build and upload a 
revision of 444884 for 2.0.12 to get rid of this complaint. Output from 
applying both patches should look something like this:

mailman@mailman2:/mailman/build/mailman-2.0.12> patch -p1 < 
../patches/current/indexing-2.0.11-0.1.patch
patching file Mailman/Archiver/HyperArch.py
patching file Mailman/Defaults.py.in
mailman@mailman2:/mailman/build/mailman-2.0.12> patch -p1 < 
../patches/current/htdig-2.0.11-0.1.patch
patching file INSTALL
Hunk #1 succeeded at 355 (offset 22 lines).
patching file INSTALL.htdig-mm
patching file Mailman/Archiver/HyperArch.py
patching file Mailman/Cgi/htdig.py
patching file Mailman/Cgi/updateTOC.py
patching file Mailman/Defaults.py.in
patching file Makefile.in
patching file bin/Makefile.in
patching file bin/blow_away_htdig
patching file cron/Makefile.in
patching file cron/crontab.in.in
patching file cron/nightly_htdig
patching file cron/remote_nightly_htdig
patching file cron/remote_nightly_htdig.pl
patching file cron/remote_nightly_htdig_noshare
patching file src/Makefile.in

You will find that patch 444884 adds a file INSTALL.htdig-mm to the MM 
2.0.12 build directory that has a fairly detailed description of how to set 
up the MM-htdig integration.

Also see 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.011.htp for 
alternative solutions.




--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] Mailman + HTDig Intergration

[Odhiambo Washington]

* Larry Goodwin <[EMAIL PROTECTED]> [20020724 20:19]: wrote:

Sorry for the top posting:


These patches are against 2.0.6.

I do run 2.0.12. I am surprised someone hasn't seen the need to intergrate
them as a standard in Mailman. However, I am still looking for pointers
to patch 2.0.12  - I see Mailman's own site runs 2.0.12 and it has all thes
facilities.

Let me hope the gurus will see this and help me out.



> I just went through this, It works good for new lists. I am having some 
> trouble with some of the old very large lists. mailman/bin/arch has a 
> memory error and htdig htmerge is haveing problems. I hope the the 
> folks at mailman and htdig will give me some help today.
> 
> Apply patches 444879 and 444884 to mailman.
> 
> The  are at SourceForge.net
> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.011.htp
> has the pointers.
> 
> 
> On Wednesday, July 24, 2002, at 09:47  AM, Odhiambo Washington wrote:
> 
> >
> >Hello List Managers,
> >
> >Does anyone know where I can find a clean HOWTO on intergrating Mailman
> >and HTDig for searchable archives. I am running Mailman-2.0.12 from
> >today ;-) but would like to go right ahead and have a searchable 
> >archive
> >like the one list.org has. Or am I being over ambitious?
> >
> >Thanking you.
> >
> >
> >-Wash
> >
> >-- 
> >Odhiambo Washington  <[EMAIL PROTECTED]>"The box said 'Requires
> >Wananchi Online Ltd.  www.wananchi.com  Windows 95, NT, or better,'
> >Tel: 254 2 313985-9   Fax: 254 2 313922 so I installed FreeBSD."
> >GSM: 254 72 743 223   GSM: 254 733 744 121  This sig is McQ!  :-)
> >
> >
> >If I had any humility I would be perfect.
> > -- Ted Turner
> >
> >--
> >Mailman-Users mailing list
> >[EMAIL PROTECTED]
> >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/

-Wash

-- 
Odhiambo Washington  <[EMAIL PROTECTED]>"The box said 'Requires
Wananchi Online Ltd.  www.wananchi.com  Windows 95, NT, or better,'
Tel: 254 2 313985-9   Fax: 254 2 313922 so I installed FreeBSD."   
GSM: 254 72 743 223   GSM: 254 733 744 121  This sig is McQ!  :-)


All other things being equal, a bald man cannot be elected President of
the United States.
-- Vic Gold

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

[Mailman-Users] Mailman + HTDig Intergration

[Odhiambo Washington]

Hello List Managers,

Does anyone know where I can find a clean HOWTO on intergrating Mailman
and HTDig for searchable archives. I am running Mailman-2.0.12 from
today ;-) but would like to go right ahead and have a searchable archive
like the one list.org has. Or am I being over ambitious?

Thanking you.


-Wash

-- 
Odhiambo Washington  <[EMAIL PROTECTED]>"The box said 'Requires
Wananchi Online Ltd.  www.wananchi.com  Windows 95, NT, or better,'
Tel: 254 2 313985-9   Fax: 254 2 313922 so I installed FreeBSD."   
GSM: 254 72 743 223   GSM: 254 733 744 121  This sig is McQ!  :-)


If I had any humility I would be perfect.
-- Ted Turner

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

RE: [Mailman-Users] mailman + htdig error/warning messages

[Matt Shirel]

Thanks Richard...  I changed /var/lib/htdig (and below) to being owned by
root.mailman and gave the folder group write permisions.  This cleared the
error report I had ben recieving.

Original:
drwxr-xr-x2 root root 4096 Mar 23 16:19 htdig
New:
drwxrwxr-x2 root mailman  4096 Mar 23 16:19 htdig





--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] mailman + htdig error/warning messages

[Richard Barrett]

At 15:33 19/05/2002 -0500, Matt Shirel wrote:
>Sorry if this is off topic, but I'm not sure where else to look for answers
>since my use of HTDig is entirely Mailman driven...  Any
>thoughts/suggestions would be greatly appreciated...
>
>When the nightly_htdig cron job runs, it generates the following message:
>
>DB2 problem...: /var/lib/htdig/db.metaphone.db: Permission denied
>DB2 problem...: /var/lib/htdig/db.soundex.db: Permission denied
>
>Mailman 2.0.8 w/ htdig patches applied
>htdig-3.2.0-1.b4.0.72 (RedHat 7.2 RPM)
>htdig-web-3.2.0-1.b4.0.72 (RedHat 7.2 RPM)
>python-1.5.2-35 (RedHat 7.2 RPM)
>
>TIA.
>
>MATT

For those using the mailman-htdig integration patch:

http://sourceforge.net/tracker/index.php?func=detail&aid=444884&group_id=103&atid=300103

I am about to upload a minor revision of the patch, primarily to stop 
Python 2.2 generating a warning about the use of import * below the module 
level in some cron scripts added by the patch. In that revised patch I have 
also added the following note to the $build/INSTAL.htdig-mm file that the 
patch adds. It deals with issue raised by the original post which I believe 
is best dealt with at the htdig installation end of things rather than at 
the Mailman-htdig integration point.


htdig Permissions Considerations


Python scripts added by this patch (nightly_htdig and its relatives) run the
htdig rundig script identified by HTDIG_RUNDIG_PATH to build search indices
for Mailman archives. Code added by this patch generates per list htdig
configuration files which are passed as a parameter to the rundig script.
These configuration files identify a list specific directory
($prefix/archives/private//htdig) in which list specific data files
generated by and used by htdig are to be placed.

However, the rundig script identified by HTDIG_RUNDIG_PATH may attempt to
generate some files in htdig's COMMON_DIR when it is first run by 
nightly_htdig;
the files concerned are likely to be root2word.db, word2root.db, 
synonyms.db and
possibly some others generated by htidg's htfuzzy program. The standard rundig
script generates these files selectively if they do not already exist. 
Depending
on how you have installed htdig and how the rundig script is first run, there
may be a permissions problem when nightly_hdig executes rundig under the 
mailman
UID if it tries to generate these files.

You may need to either give the mailman UID write permission over htdig's
COMMON_DIR or, before the nightly_htdig script is first run, run htdig's 
htfuzzy
executable with a sufficiently privileged UID in the manner that the rundig 
script
would run htfuzzy, to create any necessary files in COMMON_DIR.

See htdig's documentation for further information on this topic.




--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] mailman + htdig error/warning messages

[Richard Barrett]

At 15:33 19/05/2002 -0500, Matt Shirel wrote:
>Sorry if this is off topic, but I'm not sure where else to look for answers
>since my use of HTDig is entirely Mailman driven...  Any
>thoughts/suggestions would be greatly appreciated...
>
>When the nightly_htdig cron job runs, it generates the following message:
>
>DB2 problem...: /var/lib/htdig/db.metaphone.db: Permission denied
>DB2 problem...: /var/lib/htdig/db.soundex.db: Permission denied

If you are using the MM-htdig integration patch 444884 off sourceforge, 
this is a 'feature'. Not a good one I'll grant you.

I'm just about to post a revised version of this MM-htdig patch for 2.0.10 
(should be OK for 2.0.8 too), which should remove the feature.

In the interim I think you can get rid of it by setting permissions on the 
htdig's default COMMON_DIR (see under the General:Configuration link on 
http://htdig.org for further explanation) so that the mailman UID has write 
permissions to that directory.

I'll let you know when the revised patch is posted.

>Mailman 2.0.8 w/ htdig patches applied
>htdig-3.2.0-1.b4.0.72 (RedHat 7.2 RPM)
>htdig-web-3.2.0-1.b4.0.72 (RedHat 7.2 RPM)
>python-1.5.2-35 (RedHat 7.2 RPM)



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] mailman + htdig error/warning messages

[Jon Carnes]

After you installed htdig, did you follow the htdig install directions for 
generating the metaphone and soundex databases?

Do the databases in fact exist on your system?  Named properly?

If you are not using sound-alikes etc, then you shouldn't have it configured 
in your htdig configuration file.  If you are allowing the "sound alike" 
options then you need to generate those databases and set the locations for 
them correctly in the htdig configuration file.

Good Luck
 --- Original Message: Sunday 19 May 2002 04:33 pm ---
> Sorry if this is off topic, but I'm not sure where else to look for answers
> since my use of HTDig is entirely Mailman driven...  Any
> thoughts/suggestions would be greatly appreciated...
>
> When the nightly_htdig cron job runs, it generates the following message:
>
> DB2 problem...: /var/lib/htdig/db.metaphone.db: Permission denied
> DB2 problem...: /var/lib/htdig/db.soundex.db: Permission denied
>
> Mailman 2.0.8 w/ htdig patches applied
> htdig-3.2.0-1.b4.0.72 (RedHat 7.2 RPM)
> htdig-web-3.2.0-1.b4.0.72 (RedHat 7.2 RPM)
> python-1.5.2-35 (RedHat 7.2 RPM)
>
> TIA.
>
> MATT
>
>
>
>
>
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

[Mailman-Users] mailman + htdig error/warning messages

[Matt Shirel]

Sorry if this is off topic, but I'm not sure where else to look for answers
since my use of HTDig is entirely Mailman driven...  Any
thoughts/suggestions would be greatly appreciated...

When the nightly_htdig cron job runs, it generates the following message:

DB2 problem...: /var/lib/htdig/db.metaphone.db: Permission denied
DB2 problem...: /var/lib/htdig/db.soundex.db: Permission denied

Mailman 2.0.8 w/ htdig patches applied
htdig-3.2.0-1.b4.0.72 (RedHat 7.2 RPM)
htdig-web-3.2.0-1.b4.0.72 (RedHat 7.2 RPM)
python-1.5.2-35 (RedHat 7.2 RPM)

TIA.

MATT





--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] Mailman + Htdig

[Richard Barrett]

At 10:26 14/03/2002 -0600, Kelly Corbin wrote:
>I'm setting up Mailman with Htdig integration, and have 1 final 
>problem.  Mailman works fine, htdig works fine, but together the searches 
>fail with a 'htdig Archives Access Failure  The requested document cannot 
>be found. %s'

Assuming you are using the mailman-htdig integration patches (444879 and 
444884) off sourceforge, the error is being generated by the script 
$prefix/Mailman/Cgi/htdig.py when it tries to display a piece of archived mail.

It is saying that it has a problem with finding the html page from the 
archives that was identified by the URL returned by the search.

The URL should be cited further down the response page below what you have 
quoted above.

>I get no errors in any logs anywhere, so what is the %s?  Also, when 
>Mailman creates the htdig conf file for a list, how does it determine the 
>search URL?  If the .db files are not accessible, I get a different error 
>(a more obvious one) so I know that's not the problem.
>
>Is there a better way to trace this error?  I've been banging my head 
>against the wall for the past 3 days on this...

It would be useful to know the following:

A. what versions of python, and Mailman you are running

B. what were the name of the patch files you downloaded from sourceforge to 
do the mailman-htdig integration

First things to check are:

1. what was the URL returned by the search engine.

2. the last item in the URL path is the name of the html file that was 
being accessed.

3. the second to last item in the URL path is the particular archive that 
html file was in when the archives were last indexed by htdig.

4. third to last item in the URL patch should be the name of the list.

5. now look in the directory $prefix/archives/private/.

6. is the an archive directory from the URL in the directory.

7. if the archive directory is there is the html file in it.

If the answer to either 4 or 5 is no then that is why you are getting the 
problem and we have to identify:

either (a) why the file that was indexed by htdig is no longer where it was 
when it was indexed.

or (b) what went wrong with the indexing that lead to the wrong URL being 
stored in the index, i.e. is there something wrong in the list's htdig conf 
file.

Things to consider:

1. have you manually manipulated the list's archives since cron last ran 
the $prefix/cron/nightly_htdig script. The modification time on the file 
$prefix/archives/private//htdig/rundig_last_run will tell you 
when the script was last run.

2. you can try running $prefix/cron/nightly_htdig -v  (i.e. with 
the verbose flag) from the command line and see if fixes things.

3. as a more extreme measure you can run the $prefix/bin/blow_away_htdig -v 
 command from the command line to remove the htdig stuff 
associated with the list. Then:

 a. post a message to the list, which should recreate the list's htdig 
conf file etc

 b. run $prefix/cron/nightly_htdig -v  from the command line 
to recreate the htdig indexes for the list

 c. try the list search again

If it is still not working then get back to me and I'll tell you what other 
information I need off your installation to diagnose the problem.










































3.

Basic questions:

1. which version of Mailman.

2. which version of Python.

3. are you using the mailman-htdig integration patches (444879 and 444884) 
off sourceforge.

4. so what are names of the files you downloaded.

5. have you either run $prefix/cron/nightly_htdig from the command line or 
has it recently been run by cron.

Again if the answers to questions 3 to 10 are yes:

11. Where does the error message you cite appear? Is it on the response you 
got from filling in the search form on the lists' TOC page clicking the 
search button?

12. select a list that is being archived and has had posts to it since 
installing the the mailman-htdig integration patches.

12. look in the directory  $prefix/archives/private//htdig/

13. if there a file call .conf in the directory.

14. are ther

>Thanks!
>
>Kelly


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

[Mailman-Users] Mailman + Htdig

[Kelly Corbin]

I'm setting up Mailman with Htdig integration, and have 1 final problem. 
  Mailman works fine, htdig works fine, but together the searches fail 
with a 'htdig Archives Access Failure  The requested document cannot be 
found. %s'

I get no errors in any logs anywhere, so what is the %s?  Also, when 
Mailman creates the htdig conf file for a list, how does it determine 
the search URL?  If the .db files are not accessible, I get a different 
error (a more obvious one) so I know that's not the problem.

Is there a better way to trace this error?  I've been banging my head 
against the wall for the past 3 days on this...

Thanks!

Kelly

-- 

-- Kelly Corbin
-- Systems Administrator
--
-- http://www.theiqgroup.com
-- The Future of eServices...
--
-- The IQ Group, Inc.
-- 6740 Antioch Suite 110
-- Merriam, KS 66204
-- (913)-722-6700 x105
-- Fax (913)722-7264



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] Mailman & Htdig integration (with external archiver)

[J C Lawrence]

On Tue, 15 Jan 2002 12:13:33 +0100 (CET) 
Sasa Janiska <[EMAIL PROTECTED]> wrote:

> I'm a newbie for Mailman and have to setup Mailman with external
> archiver...

http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.003.htp
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.004.htp

> (which one goes better with Mailman: Mhonarc or
> Hypermail?) 

That rather depends on what you want to do and what features your
require.  I like/use MHonArc.

> The search engine should serve searching of the whole site +
> different mailing list which will be created for the students for
> the different courses.

I do this with MnoGoSearch -- but it has nothing to do with mailman
per se.

-- 
J C Lawrence
-(*)Satan, oscillate my metallic sonatas. 
[EMAIL PROTECTED]   He lived as a devil, eh?  
http://www.kanga.nu/~claw/  Evil is a name of a foeman, as I live.

--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

Re: [Mailman-Users] Mailman & Htdig integration (with external archiver)

[Richard Barrett]

At 14:33 15/01/2002 +0100, Sasa Janiska wrote:
>On Today, -, Richard Barrett wrote:
>
>Hi Richard!
>Thank you very much for your reply.
>
> > This is a straight htdig configuration issue. At the minimum you will have
> > to add start_url directives to htdig's conf file for each of the list
> > archives or ensure that links from one of the start_url directives in
> > htdig's conf file eventually lead to each of the list archives. You will
> > also have to have some sort of cron job to rebuild htdig's search indices
> > regularly (probably daily) to include new archived material.
>
>That's easy.
>
> > The following patches can be applied to the mailman 2.0.8 (and earlier
> > vesions of 2.0.x) to integrate htdig with Mailman and provide search of
> > archives generated by the internal (pipermail) archiver.
>
>Do you have soemthing ready for V2.1?

I have already posted on sourceforge versions of the patch for MM 2.1a3 and 
MM2.1cvs. The latter is for the MM cvs at the date and time noted in the 
posting but this may need updating depending on what change in the CVS 
since my posting. It is my intention to publish a version of the patch for 
the beta and final versions of MM 2.1 as soon as I can after they are 
available. Just check sourceforge for Mailman patches 444879 and 444884 
read the notes I post with each patch file.


> > The patches are not of direct relevance if you have opted to use an
> > external archiver.
>
>If pipermail can do the job, it isn't necessary. I am thinking about
>external archiver seeing that pipermail is no longer maintained ..

In the context of Mailman I think it can be said that pipermail is still 
being maintained. MM contains its own copy of pipermail code in python and 
if you search the developer archives you will see there is ongoing work and 
discussion about its future. The archiver will certainly be enhance by and 
maintained through MM 2.1 albeit the enhancements may not be that major. Do 
you do python? Maybe you could make a contribution!


> > The benefit of the integration of htdig with Mailman archives generated by
> > pipermail is that it provides per list search facilities with a search form
> > on each list's archive TOC page and uses Mailman's security mechanism for
> > limiting access to private mail archives via search responses; in fact you
> > can only access a private list archive's search form if you are authorised
> > to access the list. The patches also automatically builds htdig config
> > files for each archived list and provides cron scripts for maintaining
> > htdig's search indices.
>
>That's very important to limit access for private list archives.
>Actually, only students should have access to the mailing lists, and
>only for those courses they are enrolled in.

If you go with the external archiver I guess you will have to apply 
authentication and access control via the web server used to access the 
archives produced. You may want to consider how you can automate keeping 
the access control data for each private list's archives, in a format for 
use by the web server, and the subscription information held by MM in step.

As an aside, the htdig/MM integration I produced uses per list search forms 
embedded in the list archive TOC page in association with per list htdig 
config files and per list search indexes. The primary reason is that this 
gives user authentication before the search is done and inhibits 
unauthorised users having access to links and synopsis information which 
they are not entitled to access.

The approach I adopted helps overcome a problem with having search indexes 
that contain information about both private and public data. If you have 
this you have to do one of following:

1. if you are serious about security, use your own search script to run the 
search engine's search and then filter the results returned by it to remove 
links and their associated synopsis information which the user is not 
authorised to see. The problem with this is that if you have a large search 
space then checking all the returned results is going to be demanding of 
system performance.

2. if you don't mind if people can read the snippets of data they are not 
authorised to see in the synopsis returned in association with each link 
you let the user see all the results returned. Having aroused their 
interest you then annoy by refusing to let them follow one of the links 
that the search just returned to them.

My approach sidesteps both these issues reasonably neatly but I'm sure 
there are a dozen other ways of achieving the same objectives suing any 
combination of list manager/archive/search engine.

>I'll definitely try with your suggestion.
>
>Since Pipermail is no longer developed, do you think about some patch
>with external archivers like Mhonarc or Hypermail?

I'm looking at producing a more generalised patch to simply producing 
closer integrations of other search engines with Mailman archives. I guess 
it might be worth expa

Re: [Mailman-Users] Mailman & Htdig integration (with external archiver)

[Sasa Janiska]

On Today, -, Richard Barrett wrote:

Hi Richard!
Thank you very much for your reply.

> This is a straight htdig configuration issue. At the minimum you will have
> to add start_url directives to htdig's conf file for each of the list
> archives or ensure that links from one of the start_url directives in
> htdig's conf file eventually lead to each of the list archives. You will
> also have to have some sort of cron job to rebuild htdig's search indices
> regularly (probably daily) to include new archived material.

That's easy.

> The following patches can be applied to the mailman 2.0.8 (and earlier
> vesions of 2.0.x) to integrate htdig with Mailman and provide search of
> archives generated by the internal (pipermail) archiver.

Do you have soemthing ready for V2.1?

> The patches are not of direct relevance if you have opted to use an
> external archiver.

If pipermail can do the job, it isn't necessary. I am thinking about
external archiver seeing that pipermail is no longer maintained ..

> The benefit of the integration of htdig with Mailman archives generated by
> pipermail is that it provides per list search facilities with a search form
> on each list's archive TOC page and uses Mailman's security mechanism for
> limiting access to private mail archives via search responses; in fact you
> can only access a private list archive's search form if you are authorised
> to access the list. The patches also automatically builds htdig config
> files for each archived list and provides cron scripts for maintaining
> htdig's search indices.

That's very important to limit access for private list archives.
Actually, only students should have access to the mailing lists, and
only for those courses they are enrolled in.

I'll definitely try with your suggestion.

Since Pipermail is no longer developed, do you think about some patch
with external archivers like Mhonarc or Hypermail?

Sincerely,
Sasa



--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

Re: [Mailman-Users] Mailman & Htdig integration (with external archiver)

[Richard Barrett]

At 12:13 15/01/2002 +0100, Sasa Janiska wrote:
>Hi!
>
>I'm a newbie for Mailman and have to setup Mailman with external
>archiver (which one goes better with Mailman: Mhonarc or Hypermail?) and
>Htdig search engine for one non-profit web-oriented educational
>institution.
>
>The search engine should serve searching of the whole site + different
>mailing list which will be created for the students for the different
>courses.
>
>I'm interested if there is some HOWTO document for the above mentioned
>scenario which seems to me as a very common usage of the Mailman?

This is a straight htdig configuration issue. At the minimum you will have 
to add start_url directives to htdig's conf file for each of the list 
archives or ensure that links from one of the start_url directives in 
htdig's conf file eventually lead to each of the list archives. You will 
also have to have some sort of cron job to rebuild htdig's search indices 
regularly (probably daily) to include new archived material.

>Also, I have seen in FAQ that there is a patch for htdig integration with
>Mailman. Is this patch already included in 2.0.8 source tarball?

The following patches can be applied to the mailman 2.0.8 (and earlier 
vesions of 2.0.x) to integrate htdig with Mailman and provide search of 
archives generated by the internal (pipermail) archiver.

The patches are not of direct relevance if you have opted to use an 
external archiver.

The benefit of the integration of htdig with Mailman archives generated by 
pipermail is that it provides per list search facilities with a search form 
on each list's archive TOC page and uses Mailman's security mechanism for 
limiting access to private mail archives via search responses; in fact you 
can only access a private list archive's search form if you are authorised 
to access the list. The patches also automatically builds htdig config 
files for each archived list and provides cron scripts for maintaining 
htdig's search indices.

http://sourceforge.net/tracker/index.php?func=detail&aid=444879&group_id=103&atid=300103

http://sourceforge.net/tracker/index.php?func=detail&aid=444884&group_id=103&atid=300103


>Sincerely,
>Sasa
>
>
>
>--
>Mailman-Users maillist  -  [EMAIL PROTECTED]
>http://mail.python.org/mailman/listinfo/mailman-users


--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

[Mailman-Users] Mailman & Htdig integration (with external archiver)

[Sasa Janiska]

Hi!

I'm a newbie for Mailman and have to setup Mailman with external
archiver (which one goes better with Mailman: Mhonarc or Hypermail?) and
Htdig search engine for one non-profit web-oriented educational
institution.

The search engine should serve searching of the whole site + different
mailing list which will be created for the students for the different
courses.

I'm interested if there is some HOWTO document for the above mentioned
scenario which seems to me as a very common usage of the Mailman?

Also, I have seen in FAQ that there is a patch for htdig integration with
Mailman. Is this patch already included in 2.0.8 source tarball?

Sincerely,
Sasa



--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users