Bug 153256 - mailman and list search (htdig) integration
mailman and list search (htdig) integration
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mailman (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Smetana
Depends On:
Blocks: 153663
  Show dependency treegraph
Reported: 2005-04-04 01:22 EDT by Karl Latiss
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 15:05:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
diff to mailman.spec to include indexing and htdig patches (6.03 KB, patch)
2005-04-04 01:24 EDT, Karl Latiss
no flags Details | Diff
Unified output format diff of current mailman.spec and htdig enabled mailman.spec (2.21 KB, patch)
2006-09-01 11:07 EDT, John Airey
no flags Details | Diff

  None (edit)
Description Karl Latiss 2005-04-04 01:22:09 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.4.4) Gecko/20050318 MultiZilla/

Description of problem:
RHEL 3 comes with mailman however private lists are not searchable (Public ones can use external engines like Google). To make private (and public) lists searchable htdig can be used (also included in RHEL 3) along with the following 2 patches applied to the SRC RPM:


Note that the supplied diff uses the above patches renamed to the standards used by the mailman SRPM of mailman-2.1.5-indexing.patch and mailman-2.1.5-htdig.patch respectively.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.install mailman
2.post messages to list
3.try to search lists


Actual Results:  no search facility

Expected Results:  after applying the patches and re-compiling the SRPM the lists's archives are searchable

Additional info:
Comment 1 Karl Latiss 2005-04-04 01:24:37 EDT
Created attachment 112640 [details]
diff to mailman.spec to include indexing and htdig patches

requires indexing and htdig patches
Comment 2 Karl Latiss 2005-04-04 01:27:55 EDT
Forgot to mention: htdig configuration not addressed in above patch
Comment 3 Suzanne Hillman 2005-04-04 15:58:37 EDT
Internal RFE bug #153663 entered; will be considered for future releases.
Comment 4 John Airey 2006-09-01 10:39:52 EDT
Have you run "rundig" on the server after installing htdig? That's what stopped
it working for me. Also, I've discovered that you have to put this in root's crontab

19 2 * * * /usr/bin/python -S /var/mailman/cron/nightly_htdig

For some reason it didn't work from /etc/cron.d/mailman, so i've commented out

I will check what you've posted here to see if it matches the htdig.spec file
that I've created.
Comment 5 John Airey 2006-09-01 10:40:40 EDT
Sorry, I meant the mailman.spec file...
Comment 6 John Airey 2006-09-01 10:45:51 EDT
I remember something else that stopped it working. I needed a symlink from
/var/www/html/htdig to /usr/share/htdig. After that was in place the searching
worked fine. 

Are you getting the htdig databases created?
Comment 7 John Airey 2006-09-01 11:07:43 EDT
Created attachment 135383 [details]
Unified output format diff of current mailman.spec and htdig enabled mailman.spec
Comment 8 John Airey 2006-09-01 11:17:33 EDT
Comment on attachment 135383 [details]
Unified output format diff of current mailman.spec and htdig enabled mailman.spec

Make sure to have the necessary extra files in the source directory -


These are the htdig-2.1.5-0.1.patch.gz and	 indexing-2.1.5-0.1.patch.gz
files that are on sourceforge (at the time of writing)
Comment 10 RHEL Product and Program Management 2007-10-19 15:05:30 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.