Re: [Mailman-Users] Mailman + htDig
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/listname/htdig are being created
and that inside each of them there is a file named listname.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 blah)
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/listname/htdig/listname.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] Replaced sendmail with qmail - kaaputz
Peter, It's a FreeBSD 4.8-RELEASE box. All the necessary five processes are running for qmail: qmail-send, splogger, qmail-lspawn, qmail-rspawn, qmail-clean. The aliases are setup correctly, as follows: |preline /home/mailman/mail/wrapper post test in .qmail-test Yeha, I always see the mail in the admin page, but after I approve it, it doesn't go anywhere. And for some reason log/bounces notes all the members as bouncing, don't know why. I don't ever see any attempts to actually deliver the message in maillog. It has this kind of message Aug 07 11:57:20 2003 (16657) Test: [EMAIL PROTECTED] - 3 more allowed over 431385 secs for all the members of the test list. And the log/post always has Aug 07 11:57:20 2003 (16657) post to test from [EMAIL PROTECTED], size=141, 3 failures, notice the failures at the end. It always fails. I have not a single clue about whats going on. I tried about 10 reinstalls. I disabled sendmail totally. What changes do I need to make to Mailman when I change an MTA? I didn't make any changes to mailman. Maillog shows messages coming into the list server, but never shows any messages going out after I have approved them from the admin interface. Jas -Original Message- From: Peter Tattersall [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 10:57 PM To: Jaswinder S. Hayre Subject: Re: [Mailman-Users] Replaced sendmail with qmail - kaaputz Which OS? I'm running qmail with Mac OS X 10.2.6 and Mailman 2.0.13 with no major problems. Just off the top of my head, if I shut qmail down incorrectly I'm sometimes left with locks which prevent qmail from starting up properly. Try 'ps -waux | grep qmail' from the command line to check on qmail status. There should be four qmail processes running. Make sure your aliases are set up properly so that mail can be delivered to your lists - though if you see the mail in the admin pages I guess they must be delivered properly. Did you disable sendmail? Did you change the MTA settings in Mailman? What does mail.log show? On Wednesday, August 6, 2003, at 05:01 PM, Jaswinder S. Hayre wrote: Guys, I had Mailman working with Sendmail for a pretty long time, but today I decided to move to qmail. Once I installed qmail, that's when thing went downhill. First I had to recompile Mailman because of the change in GIDs. After recompiling and reinstalling I dropped my old lists into the lists directory, and now nothing is being sent out. My logs/post file says Aug 06 15:52:15 2003 (6867) post to announcementshtml from [EMAIL PROTECTED], size=1321, 1 failures And another piece of strange behavior: my logs/bounce says Aug 06 15:52:15 2003 (6867) Announcementshtml: [EMAIL PROTECTED] - first but I can succesfully send email from the list server to [EMAIL PROTECTED] from the command line. It fails each and every time. The post shows up in the administrative page, I approve the posting but nothing ever goes out. The members of the list never get it, and the maillog doesn't have any record of the post going out either. This is Mailman version 2.0.13. I have been tweaking with things for hours on end without any good results, got any solutions? Regards, Jas -- 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] Public/private archives problem.
Hi Tokio,
I checked out Rob's bug report and he says that he tried fix_url, but it only
worked for private archives, not for the public ones :(
Thanks for the suggestion though.
Tony
Quoting Tokio Kikuchi [EMAIL PROTECTED]:
Hi,
You should state your urlhost/emailhost pairs in mm_cfg.py like;
add_virtualhost('www.virtual.dom', 'mail.virtual.dom')
then use fix_url.py.
Rob Brandt wrote:
I recently submitted a bug report on that:
https://sourceforge.net/tracker/?
func=detailaid=784888group_id=103atid=100103
No response yet.
Rob
Quoting [EMAIL PROTECTED]:
Hi,
I hope someone can help me with this:
I am a web space reseller on a shared server.
One of the features we get is mailman, which we offer to our clients.
One thing I have noticed about it is that if a mailing list has a has a
private archive, the address is
http://clientdomain.com/mailman/private/listname, which is fine, but if
the archive is public, then the address is
http://myhostingprovidersservername.com/pipermail/listname - which is
not fine :(
This means that my clients can see the domain name of the underlying
provider I am buying space off, and potentially they might jump ship.
Is this something that can be fixed by me/the hosting provider, and if
so, how?
Many thanks,
Tony
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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/tony-mm%
40arielbusiness.com
--
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] qrunner with over 90% CPU
On Sun, 2003-08-10 at 22:09, Paul H Byerly wrote: Jon Carnes wrote: Paul, I have never seen this on a sendmail install. Maybe your problem is a different one. Perhaps I miss read the issue. Give that my runaway is Python I suspect this is the case. Sorry. I posted about my problem a while back, see http://www.mail-archive.com/[EMAIL PROTECTED]/msg18201.html. It seems MM is a little over eager about retrying messages when sendmail (or any MTA) reports a temporary failure. Richard said a change had been made in the CVS, and wondered if a patch was available. what version of python are your running, and what is the OS? Mailman 2.1.2 Redhat 7.1 Python 2.2.2 Paul Are you running NFS or NIS on the server? How big are your volumes? Are the errors always on trying to open /etc/mail/access.db or do they occur for other files as well? Finally, what modifications (if any) have you made to Sendmail? -- 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] Too many HOPS update
-Original Message- Behalf Of Daniel A. Creed Subject: [Mailman-Users] Too many HOPS update It appears to be doing this on ALL e-mail's where I have sent an invitation to someone to join. They get the invitation and it is the reply that has problems.. it keeps repeating until it gets the too many hops message.. This sounds more like a server configuration MTA issue than Mailman settings... What type of server OS are you using? On the Enism's we've hit this problem in that placing the domain name in the approved relay file ends up causing the hops error. The solution was to remove relaying as the OS handled it for all domains on the server without an extra entry needed. So it would relay between the original OS entry and the approved relay entry until the max was exceeded. Drop the dupe, it flows perfectly. David J. Duffner VP Operations NWC Corporation NWCWEB.com http://www.nwcweb.com NWCWEB.com - Your design, hosting and e- commerce solution! Featuring Miva Merchant e-commerce Ensim Pro/Linux based platforms NWC Corporation - Global e-Pay Solutions POSA terminals, Merchant Accounts, E-payment solutions, Gift Cards and much more! -- 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] Public/private archives problem.
Hi,
You should state your urlhost/emailhost pairs in mm_cfg.py like;
add_virtualhost('www.virtual.dom', 'mail.virtual.dom')
then use fix_url.py.
Rob Brandt wrote:
I recently submitted a bug report on that:
https://sourceforge.net/tracker/?func=detailaid=784888group_id=103atid=100103
No response yet.
Rob
Quoting [EMAIL PROTECTED]:
Hi,
I hope someone can help me with this:
I am a web space reseller on a shared server.
One of the features we get is mailman, which we offer to our clients.
One thing I have noticed about it is that if a mailing list has a has a
private archive, the address is
http://clientdomain.com/mailman/private/listname, which is fine, but if
the archive is public, then the address is
http://myhostingprovidersservername.com/pipermail/listname - which is
not fine :(
This means that my clients can see the domain name of the underlying
provider I am buying space off, and potentially they might jump ship.
Is this something that can be fixed by me/the hosting provider, and if
so, how?
Many thanks,
Tony
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] Importing subscribers
--On Donnerstag, 7. August 2003 11:59 -0400 John DeCarlo [EMAIL PROTECTED] wrote: Hindy, You certainly can. Either via the web or via the command line. Mailman will accept various formats, too. I just use the format: Joe Smith [EMAIL PROTECTED] Which works fine via the web or the command line. Chinn, Hindy wrote: Can one subscribe a list of email addresses with their corresponding names (one email + name per line)? I imported a text filewith one email address per line (almost 400 addresses / lines) via the web interface (mass subscription under membership management) without any major problems (except many bounces because some email addresses were not reachable). Amardeo. -- Amardeo Sarma [EMAIL PROTECTED] -- 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] Public/private archives problem.
Richard;
Thanks for your help in this. I am going to email you a link to my testlist,
which you can log into as an administrator and see for yourself what the
problem is. My server does not run CPanel, so I don't think that's an issue
here. My server is sitting here next to my desk, so I have full control if you
need any information.
Best Regards
Rob
Quoting Richard Barrett [EMAIL PROTECTED]:
Tony
The questions I am asking are to elicit information that will
distinguish between and identify whether there is a problem with (a)
Mailman or (b) misconfiguration of Mailman or (c) third party
modifications made to Mailman or (d) other aspects of the host system
configuration such as the Apache server.
You are complaining about links but I can interpret that in several
ways:
1. whether the URL of concern is accepted and served by the Apache
server when you think/prefer it should or should not be.
2. whether the URL of concern is found embedded in the HTML text of a
web page generated by Mailman as either a static page or by a Mailman
CGI script.
3. whether the URL of concern is found embedded in the HTML text of a
web page generated by something other than Mailman as either a static
page or as one delivered by a CGI script.
I must have been having a stupid day as I was not entirely clear from
either the referenced bug report or your initial post about which of
these interpretations I should adopt.
Now see further comments below.
Richard
On Monday, August 11, 2003, at 01:14 pm, Tony wrote:
Hi Richard,
Quoting Richard Barrett [EMAIL PROTECTED]:
Rob's bug report, as with yours, lack precision in specifying exactly
which Mailman generated pages have links on them which contain (in the
HTML text), absolute URLs referring to the wrong hostname. See my
comments below on the broadfer questions that need to be answered in
order to attack the perceived problem.
Sorry, I thought it was clear enough. I will elaborate.
I do not work with it myself, but I believe that the CPanel virtual
hosting support software, which your hosting provider may be using,
does perform some trickery to help avoid conflicts between list names
on different virtual hosts. If your hosting provider is using that and
something related to it is misconfigured then this may be contributing
to the problem.
Correct. The list directory gets names listname_domain to avoid
conflicts
with any other similarly named lists. CPanel is what is being used in
this
case.
This means that any other virtual host on the server can access the
mail
archives by providing the correct path name to the list.
When you say if the archive is public, then the address is
http://myhostingprovidersservername.com/pipermail/listname; what
precisely do you mean?
What I mean is that the link to the archives, and only this link, from
what I
can see, shows the hosting provider's server name and not the virtual
domain
for the client.
Example:
I have a list called test on clientdomain1.
The path to the list and all the admin pages etc is
http://clientdomain1/mailman/whatever/test_clientdomain1/
This list could also be accessed by another virtual domain on the same
server
as:
http://clientdomain2/mailman/whatever/test_clientdomain1/
When the archives are set to public, the archive address is:
http://clientdomain1/mailman/private/test_clientdomain1/
Did you mean the statement immediately above or are you just reflecting
on the fact that a public list is still available through its private
list URL?
When the list archives are set to public, then the archive address is:
http://hostingproviderservername/pipermail/test_clientdomain1/
I would expect this to read:
http://clientdomain1/pipermail/test_clientdomain1/
or similar.
This appears the same on both the main page for the list and in the
admin
interface.
Just to confirm; do you mean the web pages returned by the URLs
http://clientdomain1/mailman/listinfo/test_clientdomain1 and
http://clientdomain1/mailman/admin/test_clientdomain1?
I am now talking about plain vanilla, unmodified, MM 2.1.2 code. The
GetBaseArchiveURL() function used to generate the links to both public
and private list archives. Its operation is subtly different in two
cases although both depend upon the values in the VIRTUAL_HOSTS
dictionary which is conventionally constructed by calls to the
add_virtualhosts() function in the MM configuration file mm_cfg.py.
In the case of a public archive, the function does a lookup for the
list's host_name attribute (visible/editable on the General Options
page of the list) in an inversion of the VIRTUAL_HOSTS dictionary. The
actual statement that forms the URL is:
url = mm_cfg.PUBLIC_ARCHIVE_URL % {
'listname': self.internal_name(),
'hostname': inv.get(self.host_name, mm_cfg.DEFAULT_URL_HOST),
}
This works
[Mailman-Users] Howto on front ending exchange ?
Anyone written or know of a HowTo on frontending exchange servers ? Thanks in advance Mike -- 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] Hotmail and Yahoo sending mail straight tojunk folders.
Raquel Rice at [EMAIL PROTECTED] wrote: It seems that hotmail and yahoo are sending mail from mailman straight to junk folders, this is REAL bad, especially because it's possible to delete junk folders without actually looking in them. Why is this, is this because there is a bulk mail setting in the mail header? If so, how can I stop this being written into the mail? Look at the mail headers to see. Write to the abuse dept. of Yahoo and Hotmail to get their responses. This is very likely because of the mail server the messages originate from being whitelisted and not from headers in the messages themselves. Ask me how I know. - Mark -- [EMAIL PROTECTED] -- 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] Public/private archives problem.
Forgot to copy list on this: Begin forwarded message: From: Richard Barrett [EMAIL PROTECTED] Date: Mon Aug 11, 2003 6:09:10 pm Europe/London To: Tony [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Public/private archives problem. Tony On Monday, August 11, 2003, at 04:50 pm, Tony wrote: Hi Richard, Quoting Richard Barrett [EMAIL PROTECTED]: I must have been having a stupid day as I was not entirely clear from either the referenced bug report or your initial post about which of these interpretations I should adopt. Nah, I'm sure it's down to the way I wrote it :/ We all have off days. Example: I have a list called test on clientdomain1. The path to the list and all the admin pages etc is http://clientdomain1/mailman/whatever/test_clientdomain1/ This list could also be accessed by another virtual domain on the same server as: http://clientdomain2/mailman/whatever/test_clientdomain1/ When the archives are set to public, the archive address is: http://clientdomain1/mailman/private/test_clientdomain1/ Did you mean the statement immediately above or are you just reflecting on the fact that a public list is still available through its private list URL? No, I was being stupid. The above statement should have read: When the archives are set to public, the archive address is: http://hostingproviderservername/pipermail/test_clientdomain1/ This appears the same on both the main page for the list and in the admin interface. Just to confirm; do you mean the web pages returned by the URLs http://clientdomain1/mailman/listinfo/test_clientdomain1 and http://clientdomain1/mailman/admin/test_clientdomain1? Yes, these are the pages that report the archive location to br the hostingproviderservername address. I am now talking about plain vanilla, unmodified, MM 2.1.2 code. The GetBaseArchiveURL() function used to generate the links to both public and private list archives. Its operation is subtly different in two cases although both depend upon the values in the VIRTUAL_HOSTS dictionary which is conventionally constructed by calls to the add_virtualhosts() function in the MM configuration file mm_cfg.py. [] What is happening in the case of a private archive that the 'correct' host name is being returned? When generating a reference to a private archive the GetBaseArchiveURL() function uses a different list attribute called web_page_url. The standard MM 2.1.2 web creation scripts, both web and command line, set web_page_url and host_name in a compatible way. So too does the the fix_url script referred to by earlier posts on this subject. Is there a reason the two are different? If I am honest, it is not immediately obvious to me why the difference in computing the hostname used in private and public archive URLs. But with a properly configured vanilla Mailman installation, the results should be same in either case. What would happen if they were both the same? Unfortunately, I am not in a position to check out what is being done on the server, since I am merely a client and have bugger all access to the server :( But you could check the 'Host name this list prefers for email' option on the General Options page of one of your problem lists (3rd from last option with MM 2.1.2). Does this look to be correct? I would expect it to. As you say, it could be how CPanel have integrated mm, or it could be a configuration issue with how they set it up. There is fresh news. There is good news and there is bad news. The good news is that you are not alone. I have just fooled around with a demo CPanel facility of a web hosting supplier. Lo and behold the the links to the list archives - the /pipermail URLs - switch from the virtual host name to the base server host name; see: http://free-try-before-buy.com/mailman/listinfo/delist_free-try- before-buy.com and follow the list archive link. Lo and behold you get to: http://server.6np.net/pipermail/delist_free-try-before-buy.com/ although the 'desired' URL works OK: http://free-try-before-buy.com/pipermail/delist_free-try-before- buy.com/ The bad news is that this looks like a built in 'feature' of the current CPanel implementation. My guess is that the CPanel's own scripts are used by CPanel in place of the standard Mailman scripts to create new lists and that these scripts set the list web_page_url and host_name attributes directly but without adding any matching add_virtualhost() calls to mm_cfg.py to expand the VIRTUAL_HOSTS dictionary. This would not be a major surprise as the VIRTUAL_HOSTS dictionary stuff now in Mailman is a MM 2.1.x introduction and CPanel basic implementation predates it with MM 2.0.x. If I can find time I will look at the issue a bit harder but right now I cannot see any easy solution for you. Basically it looks to me like a rough edge on the CPanel implementation rather than a bug in Mailman. Can you suggest anywhere I can look (or point the hosting provider at)
[Mailman-Users] I can't get my mail list to work
Hello, I have a mailing list at www.hcmcnurses.org we are a non-profit association and our web host, webmanix.com, is not very helpful. We cannot the mailing list to work. The mailing list [EMAIL PROTECTED] does not work. When I create a mailing list I get the text below. I didn't find an option on the Control Panel for editing the etc/aliases or running 'newalises'. I tried making folders named etc/aliases and adding a text file named text.txt to that folder with the information below, but it did not work. --- Account Created The mailing list test on hcmcnurses.org with password test was sucessfully created. To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## test_hcmcnurses.org mailing list test_hcmcnurses.org: |/usr/local/cpanel/3rdparty/mailman/mail/mailman post test_hcmcnurses.org test_hcmcnurses.org-admin: |/usr/local/cpanel/3rdparty/mailman/mail/mailman admin test_hcmcnurses.org test_hcmcnurses.org-bounces: |/usr/local/cpanel/3rdparty/mailman/mail/mailman bounces test_hcmcnurses.org test_hcmcnurses.org-confirm: |/usr/local/cpanel/3rdparty/mailman/mail/mailman confirm test_hcmcnurses.org test_hcmcnurses.org-join: |/usr/local/cpanel/3rdparty/mailman/mail/mailman join test_hcmcnurses.org test_hcmcnurses.org-leave: |/usr/local/cpanel/3rdparty/mailman/mail/mailman leave test_hcmcnurses.org test_hcmcnurses.org-owner: |/usr/local/cpanel/3rdparty/mailman/mail/mailman owner test_hcmcnurses.org test_hcmcnurses.org-request: |/usr/local/cpanel/3rdparty/mailman/mail/mailman request test_hcmcnurses.org test_hcmcnurses.org-subscribe: |/usr/local/cpanel/3rdparty/mailman/mail/mailman subscribe test_hcmcnurses.org test_hcmcnurses.org-unsubscribe: |/usr/local/cpanel/3rdparty/mailman/mail/mailman unsubscribe test_hcmcnurses.org Hit enter to notify test_hcmcnurses.org owner... Updated List test hcmcnurses.org Thanks for your help, Rick Cheney 651-227-9166 -- 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
On Friday, August 8, 2003, at 09:57 pm, Rich West wrote:
snip
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
[Mailman-Users] Script Alternative to Radio Buttons?
We need a command line script alternative to the web page radio buttons, and we are willing to pay for it! We have ten mailman mailing lists that we use very effectively with our customers and internal staff. Every day, our Administrator has to go to the Pending Administrative Requests for mailing list ... to get rid of all the spam posts. Often there are fifty or so per mailing list, so 500 unwanted administrative pieces of mail. It takes a very long time (one or more hours per day) to click the discard radio button for each mail message per mailing list, and then finally click on the Submit All Data button. Our administrator would like to quickly skim the pending messages, see if there are any that are bonafide messages that should be posted to the mailing list, and then discard all the rest in one fell swoop. If someone could write us a script that we could run from the Red Hat Linux command line, we are willing to pay for the development and resubmit to the community. We would like to do something like this: linux prompt% discard pendingmsgs mailinglistone where discard is the command, pendingmsgs is an argument, and mailinglistone is the name of the mailing list to get the treatment. We use Mailman 2.1.2 and RedHat Linux 9.x. We compiled our own version of Mailman because the one that shipped with RedHat did not work right. Our network administrator who set this all up says he is too busy to write the script for us, so that is why we are asking for help from the community. Thanks in advance. --- ==--==- Chris Wellens President CEO InterWorking Labs --==--= 108 Whispering Pines Dr, Ste 115, Scotts Valley, CA 95066-4792 ==--==- [EMAIL PROTECTED] +1 831 430 3610 +1 831 430 9144 Fax --- __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- 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] Re: qrunner with over 90% CPU
Jon Carnes wrote: Sorry to pepper you with so many questions.. Hey, anything that might help. What do you get when you type: cat /proc/sys/fs/file-max 65000 cat /proc/sys/kernel/threads-max 4086 On one of my well-running RH 9 boxes, I'm on 7.1. I get: cat /proc/sys/fs/file-max 26208 I'm more than double that. Is more too many? cat /proc/sys/kernel/threads-max 4095 I'm very close to that. You can adjust these values by becoming root and typing in something like: echo 16384 /proc/sys/fs/file-max echo 2048 /proc/sys/kernel/threads-max Note: this is not a recommendation (well it is, but it's not *my* recommendation...) Both of which are well less than what I have. What would this do? BTW: I'm guessing that you are not running either NFS or NIS (NIS is a way of sharing user information amoung a lot of unix servers) Sounds right. I also guess that hda1 is your /boot and that hda3 is / Correct That indicates that your install is using one IDE drive. Right again. I hope your mail traffic is not too high! Not yet, but it will be in time as I move more lists. I am way over due for some upgrades and the box no longer covers what I need, so I'm looking to move to a new server. I'm thinking a two HD box running C-panel, and I'm looking to run a better MTA than sendmail. You might want to drop the Open Relay checks for a week and see if that makes a difference. I'm not sure, but Sendmail may be holding open the access.db file while it does these checks. Could be, but my lists are currently announcement lists that send at a low mail time. I once let the runaway process go for 15 minutes to see if it would clear, it did not. The open relay checks cut my mail volume substantially, and I suspect I'd hear from some customers if I stop them. Thanks for the help. 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] I can't get my mail list to work
On Sun, Aug 10, 2003 at 09:35:55AM -0500, Rick Cheney wrote: Hello, I have a mailing list at www.hcmcnurses.org we are a non-profit association and our web host, webmanix.com, is not very helpful. We cannot the mailing list to work. The mailing list [EMAIL PROTECTED] does not work. When I create a mailing list I get the text below. I didn't find an option on the Control Panel for editing the etc/aliases or running 'newalises'. I tried making folders named etc/aliases and adding a text file named text.txt to that folder with the information below, but it did not work. newaliases needs to be run by your mail host. It's not a mailman function - it's dependent on the MTA. The mailing list test on hcmcnurses.org with password test was sucessfully created. To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## test_hcmcnurses.org mailing list test_hcmcnurses.org: |/usr/local/cpanel/3rdparty/mailman/mail/mailman post test_hcmcnurses.org Something's quite broken since it's combining your list name with your host name. test_hcmcnurses.org isn't a valid DNS name. It looks like webmanix doesn't have mailman configured properly. If they're not going to help you with this, then you may need to find a different mailman host. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] -- 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
