MM 2.1.3 version Mailman-htdig integration patches available
![](https://secure.gravatar.com/avatar/632bc87a86b0db6153c56defac0ba682.jpg?s=120&d=mm&r=g)
I have uploaded updated files to sourceforge for the following patches and bugs I maintain, which include my Mailman-HTdig integration patches. You can reach them through:
http://sourceforge.net/tracker/?group_id=103
Mailman - Patches
#444879 - Archive indexer control to improve index
#444884 - Integration of Mailman & htdig for archi
#644797 - Revised mailer exit status
#644810 - Sendmail mailer in Python
#760567 - moderation request message content
Mailman - Bugs
#777444 - mailmanctl doesn't setgroups when run as root
They are also available through:
http://www.openinfo.co.uk/mailman/index.html
If you encounter any problems with downloading or using these patches then let me know.
Richard Barrett http://www.openinfo.co.uk
![](https://secure.gravatar.com/avatar/6af53106eba96baffa28cca99fbd221f.jpg?s=120&d=mm&r=g)
Richard Barrett (r.barrett@openinfo.co.uk) wrote:
Is there any chance for these patches to become integrated in the official distribution.
We are just configuring one server which runs Gentoo and it is a pain to always manually patch Mailman, instead of plain "emerge".
Sincerely, Gour
-- Gour gour@mail.inet.hr Registered Linux User #278493
![](https://secure.gravatar.com/avatar/632bc87a86b0db6153c56defac0ba682.jpg?s=120&d=mm&r=g)
On Wednesday, October 1, 2003, at 07:22 am, Gour wrote:
A perfectly reasonable question.
It is pain for me too, as the author and maintainer of these patches, particularly #444879 and #444884. I have to retest and, if necessary, rework and again retest them against each new MM release. Yes, I would have to do some of this work as I use the patches on systems I manage but the time and effort to try an deliver a trouble free and documented patch to a wider community arguably doubles the effort I expend.
As I write, the sourceforge page for patch #444884 appears to be broken (again), probably because the number of files associated with the patch has hit some PHP limit when rendering the page - that was the problem the last time this occurred.
All these files have accumulated to cater for the numerous releases of MM since I first developed the patch (and some fixing of my bugs introduced by my patched code). But I do not have the necessary privileges to delete the older, obsolete files from sourceforge.
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.
I have a half completed rework of the #444884 patch to make it more of a "search framework", so that a variety of search engines could be plugged in more readily, but finding the time and effort to complete this is a problem for me. And, if I am honest, I doubt that even this would be admitted to the core MM code before MM 3. Take patch #444879, which has been entirely search engine agnostic and configured to do nothing be default for some considerable time, and that has not been accepted into the CVS. To cap it all, MM 3 is supposed to get a better built-in archiver (than the current pipermail implementation) incorporating built-in search; so why waste my time and effort on figuring out enhanced changes to obsolescent code.
Others must speak to their view but I doubt you will see this problem resolved before MM 3.
Richard Barrett http://www.openinfo.co.uk
![](https://secure.gravatar.com/avatar/d4258e6caa5b231603e992b430199997.jpg?s=120&d=mm&r=g)
Richard, I love your patches and install them regularly for each version of Mailman. In fact, I wait for your patches to come out before upgrading!
<Where should I send the beer?>
It is really a shame that they are not included in the original Source Code. I think in our last straw poll of the users, the consensus of the group was overwhelmingly in favor of rolling your code into the Source.
We may simply need to provide an alternate download location that has your code already patched into the source - and an rpm made from that source. I believe some folks have already done this on a piece-meal basis.
Jon Carnes
On Wed, 2003-10-01 at 06:50, Richard Barrett wrote:
![](https://secure.gravatar.com/avatar/8a174901c78fcb5f9f0b8fb3e235bf3f.jpg?s=120&d=mm&r=g)
On Wed, 2003-10-01 at 09:13, Jon Carnes wrote:
I imagine that Barry has not included the htdig patch because it has not been determined whether htdig is the optimum solution. Just wondering if anyone has done a comparison of htdig to other search tools such as mnogosearch? But I also sense that Barry is reluctant to merge a completely separate package period. Another case in point, MHonarc. And on reflection I don't think this is completely unreasonable. It might be better to find ways to get Mailman to *more easily cooperate* with external packages such as htdig and MHonarc for those who wish to use those tools.
But I do not see any reason why Richard's patch to allow the editing of messages sent to a moderated list has not been rolled into Mailman. This is a feature that many people would like to see and it does not involve the integration of a standalone product.
Barry, whaddaya say about the "edit moderated messages" patch? Can this be done?
- Kevin
![](https://secure.gravatar.com/avatar/632bc87a86b0db6153c56defac0ba682.jpg?s=120&d=mm&r=g)
On Wednesday, October 1, 2003, at 04:25 pm, Kevin McCann wrote:
I cannot claim credit for a patch "to allow editing of messages sent to a moderated list". Sounds neat but it is not one of mine.
Barry, whaddaya say about the "edit moderated messages" patch? Can this be done?
Probably best to identify the patch with its sourceforge tracker number if you want to get BW to act.
Richard Barrett http://www.openinfo.co.uk
![](https://secure.gravatar.com/avatar/8a174901c78fcb5f9f0b8fb3e235bf3f.jpg?s=120&d=mm&r=g)
On Wed, 2003-10-01 at 12:43, Richard Barrett wrote:
I cannot claim credit for a patch "to allow editing of messages sent to a moderated list". Sounds neat but it is not one of mine.
???
Strange ... I thought I read about such a patch on your web site yesterday when I went to download the MM/Mhonarc patch you mentioned on the list. Hmmm. Maybe I read it somewhere else (I've been doing a lot of poking around hewre and there in the last couple of days)
Heck, I have to find the thing first ;-) ... I coulda *sworn* I saw it on you site ....
- Kevin
![](https://secure.gravatar.com/avatar/632bc87a86b0db6153c56defac0ba682.jpg?s=120&d=mm&r=g)
On Wednesday, October 1, 2003, at 02:13 pm, Jon Carnes wrote:
Thanks for the kind words and thought.
As a first step I have done what you suggested and built some patched
MM source distributions. They are posted on my own web site at
http://www.openinfo.co.uk/mailman/prepack.html
If you were interested in cooking an RPM version to post there too ...
Originally, the only reason I set up my www.openinfo.co.uk site with
Mailman patches on it was because of problems a release or two back,
when uploading the revised #444884 patch to sourceforge broke some
configured in memory limit on their PHP page rendering code.
The problem recurred on 1st October when I uploaded the revised #444884
patch for MM 2.1.3 and I am still waiting for something other than a
canned response from the support folks at sourceforge. See:
http://sourceforge.net/tracker/ ?func=detail&aid=815621&group_id=1&atid=200001
Jon Carnes
Richard Barrett http://www.openinfo.co.uk
![](https://secure.gravatar.com/avatar/a9f40a9a9f3f642084b5310b3d8fc338.jpg?s=120&d=mm&r=g)
Enclosed please find a mailman.spec file for building mailman 2.1.3 with your htdig and mhonarc integration patches (plus the others you include in your prepacked sources). This spec file is for Mandrake. It could be easily changed for other distributions. One note that is is critical to put the correct path for mhonarc MHONARC_ARCHIVER_PATH in your mm_cfg.py.
![](https://secure.gravatar.com/avatar/6af53106eba96baffa28cca99fbd221f.jpg?s=120&d=mm&r=g)
Richard Barrett (r.barrett@openinfo.co.uk) wrote:
At the moment htdig patches provides nice add-on functionality for Mailman, and there are no better (read: simpler) ways to add search capability to the archives.
I can agree that neither pipermail, nor htdig are the best one's, but they at least work -- now, and are easy to setup.
Others must speak to their view but I doubt you will see this problem resolved before MM 3.
Afaik, before MM 3, we must 1st wait for MM 2.2, so it looks like it won't happen tomorrow, and it is a pity not to have some replacement in between :-)
Sincerely, Gour
ps. Anyway, thank you Richard for your hard work in providing and maintaining these patches.
-- Gour gour@mail.inet.hr Registered Linux User #278493
![](https://secure.gravatar.com/avatar/6af53106eba96baffa28cca99fbd221f.jpg?s=120&d=mm&r=g)
Richard Barrett (r.barrett@openinfo.co.uk) wrote:
Is there any chance for these patches to become integrated in the official distribution.
We are just configuring one server which runs Gentoo and it is a pain to always manually patch Mailman, instead of plain "emerge".
Sincerely, Gour
-- Gour gour@mail.inet.hr Registered Linux User #278493
![](https://secure.gravatar.com/avatar/632bc87a86b0db6153c56defac0ba682.jpg?s=120&d=mm&r=g)
On Wednesday, October 1, 2003, at 07:22 am, Gour wrote:
A perfectly reasonable question.
It is pain for me too, as the author and maintainer of these patches, particularly #444879 and #444884. I have to retest and, if necessary, rework and again retest them against each new MM release. Yes, I would have to do some of this work as I use the patches on systems I manage but the time and effort to try an deliver a trouble free and documented patch to a wider community arguably doubles the effort I expend.
As I write, the sourceforge page for patch #444884 appears to be broken (again), probably because the number of files associated with the patch has hit some PHP limit when rendering the page - that was the problem the last time this occurred.
All these files have accumulated to cater for the numerous releases of MM since I first developed the patch (and some fixing of my bugs introduced by my patched code). But I do not have the necessary privileges to delete the older, obsolete files from sourceforge.
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.
I have a half completed rework of the #444884 patch to make it more of a "search framework", so that a variety of search engines could be plugged in more readily, but finding the time and effort to complete this is a problem for me. And, if I am honest, I doubt that even this would be admitted to the core MM code before MM 3. Take patch #444879, which has been entirely search engine agnostic and configured to do nothing be default for some considerable time, and that has not been accepted into the CVS. To cap it all, MM 3 is supposed to get a better built-in archiver (than the current pipermail implementation) incorporating built-in search; so why waste my time and effort on figuring out enhanced changes to obsolescent code.
Others must speak to their view but I doubt you will see this problem resolved before MM 3.
Richard Barrett http://www.openinfo.co.uk
![](https://secure.gravatar.com/avatar/d4258e6caa5b231603e992b430199997.jpg?s=120&d=mm&r=g)
Richard, I love your patches and install them regularly for each version of Mailman. In fact, I wait for your patches to come out before upgrading!
<Where should I send the beer?>
It is really a shame that they are not included in the original Source Code. I think in our last straw poll of the users, the consensus of the group was overwhelmingly in favor of rolling your code into the Source.
We may simply need to provide an alternate download location that has your code already patched into the source - and an rpm made from that source. I believe some folks have already done this on a piece-meal basis.
Jon Carnes
On Wed, 2003-10-01 at 06:50, Richard Barrett wrote:
![](https://secure.gravatar.com/avatar/8a174901c78fcb5f9f0b8fb3e235bf3f.jpg?s=120&d=mm&r=g)
On Wed, 2003-10-01 at 09:13, Jon Carnes wrote:
I imagine that Barry has not included the htdig patch because it has not been determined whether htdig is the optimum solution. Just wondering if anyone has done a comparison of htdig to other search tools such as mnogosearch? But I also sense that Barry is reluctant to merge a completely separate package period. Another case in point, MHonarc. And on reflection I don't think this is completely unreasonable. It might be better to find ways to get Mailman to *more easily cooperate* with external packages such as htdig and MHonarc for those who wish to use those tools.
But I do not see any reason why Richard's patch to allow the editing of messages sent to a moderated list has not been rolled into Mailman. This is a feature that many people would like to see and it does not involve the integration of a standalone product.
Barry, whaddaya say about the "edit moderated messages" patch? Can this be done?
- Kevin
![](https://secure.gravatar.com/avatar/632bc87a86b0db6153c56defac0ba682.jpg?s=120&d=mm&r=g)
On Wednesday, October 1, 2003, at 04:25 pm, Kevin McCann wrote:
I cannot claim credit for a patch "to allow editing of messages sent to a moderated list". Sounds neat but it is not one of mine.
Barry, whaddaya say about the "edit moderated messages" patch? Can this be done?
Probably best to identify the patch with its sourceforge tracker number if you want to get BW to act.
Richard Barrett http://www.openinfo.co.uk
![](https://secure.gravatar.com/avatar/8a174901c78fcb5f9f0b8fb3e235bf3f.jpg?s=120&d=mm&r=g)
On Wed, 2003-10-01 at 12:43, Richard Barrett wrote:
I cannot claim credit for a patch "to allow editing of messages sent to a moderated list". Sounds neat but it is not one of mine.
???
Strange ... I thought I read about such a patch on your web site yesterday when I went to download the MM/Mhonarc patch you mentioned on the list. Hmmm. Maybe I read it somewhere else (I've been doing a lot of poking around hewre and there in the last couple of days)
Heck, I have to find the thing first ;-) ... I coulda *sworn* I saw it on you site ....
- Kevin
![](https://secure.gravatar.com/avatar/632bc87a86b0db6153c56defac0ba682.jpg?s=120&d=mm&r=g)
On Wednesday, October 1, 2003, at 02:13 pm, Jon Carnes wrote:
Thanks for the kind words and thought.
As a first step I have done what you suggested and built some patched
MM source distributions. They are posted on my own web site at
http://www.openinfo.co.uk/mailman/prepack.html
If you were interested in cooking an RPM version to post there too ...
Originally, the only reason I set up my www.openinfo.co.uk site with
Mailman patches on it was because of problems a release or two back,
when uploading the revised #444884 patch to sourceforge broke some
configured in memory limit on their PHP page rendering code.
The problem recurred on 1st October when I uploaded the revised #444884
patch for MM 2.1.3 and I am still waiting for something other than a
canned response from the support folks at sourceforge. See:
http://sourceforge.net/tracker/ ?func=detail&aid=815621&group_id=1&atid=200001
Jon Carnes
Richard Barrett http://www.openinfo.co.uk
![](https://secure.gravatar.com/avatar/a9f40a9a9f3f642084b5310b3d8fc338.jpg?s=120&d=mm&r=g)
Enclosed please find a mailman.spec file for building mailman 2.1.3 with your htdig and mhonarc integration patches (plus the others you include in your prepacked sources). This spec file is for Mandrake. It could be easily changed for other distributions. One note that is is critical to put the correct path for mhonarc MHONARC_ARCHIVER_PATH in your mm_cfg.py.
![](https://secure.gravatar.com/avatar/6af53106eba96baffa28cca99fbd221f.jpg?s=120&d=mm&r=g)
Richard Barrett (r.barrett@openinfo.co.uk) wrote:
At the moment htdig patches provides nice add-on functionality for Mailman, and there are no better (read: simpler) ways to add search capability to the archives.
I can agree that neither pipermail, nor htdig are the best one's, but they at least work -- now, and are easy to setup.
Others must speak to their view but I doubt you will see this problem resolved before MM 3.
Afaik, before MM 3, we must 1st wait for MM 2.2, so it looks like it won't happen tomorrow, and it is a pity not to have some replacement in between :-)
Sincerely, Gour
ps. Anyway, thank you Richard for your hard work in providing and maintaining these patches.
-- Gour gour@mail.inet.hr Registered Linux User #278493
participants (6)
-
Gour
-
Jim Drash
-
Jon Carnes
-
Kevin McCann
-
Mark Dadgar
-
Richard Barrett