Re: [Mailman-Users] Migrating from Lyris to Mailman - Looking forfunctionality and/or workarounds
For point 1, yes you lose this. However, I think it may be possible to get some info by configuring webalizer to read the mailman log files. I am not sure on this point though. Point 2. You will find in the templates folder (en for english) a footer.html that gets added. You may edit that as you wish. (just run arch program to update the archives with it). Point 3 I think that mailman does support virtual servers, but I have no experience of this. So don't hold me to it even being available. Anthony On Thu, 2003-07-17 at 20:08, Miles Fawcett wrote: We are in the process of migrating from Lyris to Mailman/Sendmail. We are very excited about this migration however we loose some functionality which our nonprofit list managers are concerned about. We are trying to work through/around these issues. I would appreciate any information anyone has on Mailman functionality I may be missing or work-arounds to achieve the following: - Daily, weekly, and/or monthly subscription reports to list managers with numbers of new subscriptions, unsubscribe, bounces, etc. - Footer message included in body of HTML emails (not an attachment) - Subscriber expiration dates so that a subscriber becomes in-active after specified date - Create virtual servers so Overview of Mailing Lists only include lists for a virtual domain Thanks very much. Miles Miles Fawcett, President direct 202.449.7222 - main 202.265.3700 - eFax 202.742.5704 email [EMAIL PROTECTED] - AIM:miles202 - website www.iapps.com I N T E R A C T I V E A P P L I C A T I O N S G R O U P I N C (iapps) Strategic Internet Solutions for Foundations and Nonprofits -- 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/a.carter%40cordis.lu -- 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 External Archiver
Richard Barrett wrote: On Thursday, July 17, 2003, at 06:10 PM, Olivier Carmona wrote: I am using MailMan 2.1.2 and Python 2.2.3 under Redhat 6.2 . I do not think that the kind of external archiver I use matters. When using external archiver options, I found that if the command stdout is not redirected then the archiver returns status OK and on stderr a SIGPIPE signal caught. PRIVATE_EXTERNAL_ARCHIVER = '/path/to/myarchiver /tmp/myarchiver.log' - WORKS PRIVATE_EXTERNAL_ARCHIVER = '/path/to/myarchiver /tmp/myarchiver.log' - DO NOT WORK I am not a python expert so it might that the following recommendation in Default.py, implicitly warns about it, and if this is the case, it would be very much appreciable to write it down explicitly. # being archived will be substituted for this. Please note that os.popen() is # used. Mailman simply run the external archiver command you supply using os.popen() with a single pipe connected to the STDIN of the that process through which MM pushes the message to be archived before closing the pipe. It doesn't come any more basic than that. The behaviour of the command you supply and its desires or needs for its STDOUT or STDERR to be handled in some particular way are not determined by either Mailman or Python except that, from a practical standpoint, neither can be assumed to provide an intelligent termination of the subprocess output file descriptors. Sorry my English is too bad. I do not care about logging to STDOUT or STDERR my external archiver activity. I just meant that without redirecting STDOUT, external archiver simply do not work. It stops caught by a SIGPIPE and absolutely, nothing is done. Whatever the command (/bin/ls,..) is inserted in PRIVATE_EXTERNAL_ARCHIVER, if you do not redirect STDOUT, it just stops without executing the command. If I am the only one to see that, I am afraid that Python os.open does not behave correctly on my kernel 2.2. When you choose an external archiver you take on the responsibility for understanding how to use it and, if it is going to generate output to STDOUT and/or STDERR, deciding what to do with that; /dev/null 21 comes to mind. By the way, it would be great to mention in INSTALL that Default.py can be changed but that any change to Default.py imply to restart mailman init script in order for the changes to be taken into account. Also you should not make changes in Defaults.py but in mm_cfg.py, unless you want to lose your site specific changes the next time you do an upgrade. It is worth reading all of the comments in Defaults.py Thanks for the info. As for commenting on the need to restart a server daemon after changing its configuration file; it would be quicker to list the number of server programs that do _not_ have to be restarted under these circumstances! Try changing httpd.conf without restarting Apache and see how far it gets you. I am not sure your comparison is OK because httpd.conf mention more clearly that After this file is processed, the server will look for and process meaning clearly that the program is interpreted on launch. Best regards, -- Olivier -- 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 -- Olivier Carmona __ __ K-Team S.A.| |/ /|____|___ _ ___ ___ Chemin de Vuasset, CP 111 | / __ | | _|/ _ \| \/ | 1028 Preverenges | | \| | |/ /_\ || Switzerland|__|\__\ |__|__|_/ \_|__|\/|__| [EMAIL PROTECTED] tel:+41 21 802 5472 fax:+41 21 802 5471 -- 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] Duplicate messages
On Thu, 2003-07-17 at 16:46, Ed Wilts wrote: I'm trying to discover why mailman sent the same message multiple times to the same recipients. I don't believe it happened to every recipient on my list, but as Murphy's Law would have it, some key people did get the message more than once - some got it at least 3 times. The message really was only posted to the list once. What can I look at to see why this happened, and to ensure that it doesn't happen again? I'm running Mailman 2.0.13 on Red Hat Linux 7.0. Thanks, .../Ed The most common cause for duplicates is that the users are on multiple lists (or sublists). If the original list contains other sublists then each sublist will get the message, and folks on both lists will get the message twice. Another less common cause is a resource problem on the Mail-server. If the message was very large and the amount of RAM on the Mail-server was small, you might have run out of resources while processing the message. A malformed or odd header on an email could also make earlier releases of Mailman send out duplicates. I haven't heard of that being a problem in version 2.0.13 (which is very robust). If you can look at the headers of the email that these folks got, it will help you figure out what is going on. If the headers are all identical, then the mail was duplicated, and you should mark the time when the message was processed and then check out the logs of your server for that time period. If the headers are not identical, then they should help you trace down where the duplicates are coming from. Good Luck - Jon Carnes -- 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] Heavy load...
Hi. mailman 25332 0.0 0.1 7420 276 ?SJul14 0:00 /usr/bin/python bin/mailmanctl start mailman 25333 0.0 1.4 7916 3708 ?SJul14 0:13 qrunner /usr/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 25334 0.0 1.0 7516 2784 ?SJul14 0:01 qrunner /usr/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 25335 0.0 0.5 7308 1324 ?SJul14 0:01 qrunner /usr/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 25336 0.0 1.2 7612 3180 ?SJul14 0:06 qrunner /usr/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 25337 0.0 0.5 7348 1460 ?SJul14 0:01 qrunner /usr/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 25338 95.5 1.3 7904 3428 ?RJul14 5048:09 qrunner /usr/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 25339 0.0 1.0 7612 2816 ?SJul14 0:12 qrunner /usr/mailman/bin/qrunner --runner=VirginRunner:0:1 -s This is how my mailman processes look like. I installed Mailman following instructions in tarball. I am running this on Celeron 333 with 256 MB RAM, Postfix 2.0.13, MailScanner + SpamAssassin. This is not normal behaviour, is it? I checked system logs but couldn't find anything unusual. Any ideas? Thank you in advance. Best regards. -- Nejc Skoberne Grajska 5 SI-5220 Tolmin E-mail: [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
[Mailman-Users] (no subject)
Hi, Iam facing following 2 errors while dealing withy mailman's mailing list through cpanel 1) While trying to edit an existing mailing list it is showing an internal server. The link of the error page is http://domainname/mailman/admin/board_cufcc.org 2) While trying to add a new mailing list through cpanel interface, Iam getting the error IOError: [Errno 2] No such file or directory: '/usr/local/cpanel/3rdparty/mailman/lists/mailinglistname_domainname/confif.pck' Please help me in fixing the error. I have the root access for the server. Thanks Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now ! -- 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] Heavy load...
Hello, although you don't give information about the system (OS etc), the best candidate, for the heavy load is the mailscanner - spamassasin combo. I suspect that you are noticing this when the message is being processed by these two ... I suspect you have the classic two queue configuration for mailscanner and that spamassasin is being invoked by the local mailer (Mlocal in sendmail terms ...). The best solution I can think of is moving up in the mail saga those two checks, where your MTA has done already most of the required job. I do not now mutch of postfix (yeah sendmail user/maniac here ...) but you could try something like mimedefang or anything else that is milterAPI equivalent for postfix ... -- Georgatos Evaggelos Network Operations Center Department of Informatics University of Athens Panepistimioupolis, Illisia 157 84, Athens Greece -- Cantadas Fracas Homem: Se eu pudesse te ver nua, eu morreria feliz. Mulher: Se eu pudesse te ver nu, eu morreria de rir. -- 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] (no subject)
On Fri, 18 Jul 2003 17:26:43 +0530, you wrote: Iam facing following 2 errors while dealing withy mailman's mailing list through cpanel when is cPanel going to bring out 2.1.n Mailman and WHY have they not yet done it and WHY are they still using old RHat? chas -- 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] Migrating from Lyris to Mailman - Lookingforfunctionality and/or workarounds
- Daily, weekly, and/or monthly subscription reports to list managers with numbers of new subscriptions, unsubscribe, bounces, etc. This would be extremely useful. Could we see this in a future release? -- Karen G. Schneider [EMAIL PROTECTED] http://lii.org Director,Librarians' Index to the Internet -- 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] archive - ergonomics of date
Tyrus Maynard wrote: I have questions about the way that index listings of postings is displayed in Mailman for all sorted listing ...sorted by Date,Subject/Thread or Author. This is not about search tools, only the sorted lists offered for browsing. 1. Why is date not shown for all sorted posting lists in Mailman ? (Why is date not shown for ANY sorted posting lists ) 1a Why is date not provided/shown for a list by DATE sorting? Now WHY would I want an index sorted by DATE that scrolls over more than a screenfull WITHOUT having the Date provided on each entry. How many clicks do I want to execute to find the sweet spot in a long list that approximates April 15,2002 ...Mailman archiving forces the opening of multiple irrelevant postings just to find an approximate date to begin browsing for old content. It is unthinkable to me to provide a SORTED list without the content of the SORT FIELD being displayed ...if you don't believe me try the same for a subject sort or an author sort. I really don't do games on computers except at a Mailman Date archive, where I can play hit the pinnata with multiple blind mouse clicks. 1b Why is date not shown for a listing by Thread/Subject? Let me propose that the date of a message is also important to evaluating its significance. For threads that are familiar (whether followed or particpating poster) I retain a rough chronology of the conversation. Also,when I visit a new thread, I know that sometimes an important post is an OUTLIER separated in time from the starting post. Outliers often provide thoughtful informative followup (on an active list an outlier may be hours old compared to minutes old). I don't claim that outliers are always significant, but the TIME SEQUENCE of a SUBJECT THREAD gives important clues to the conversation. Also it is important to revisiting a thread which is well remembered, because the basic FLOW of CONVERSATION may also be recalled on a revisit. Date is an important clue in a sorted listing by subject. 1c Why is date not shown for listing by Author ? Do lists have dominant Authors posting important stuff? Yes. The way I remember an old post is this: That important security issue, that I can't remember the name of (and which probably doesn't have security as a search term) Posted by Guru Joe (who knows alot about security on this list) Posted in January or February of 2002 Naturally I would like to browse the Author listing of Guru Joe and find the region around Jan Feb 2002 not much fun in a Mailman archive ...unless you enjoy ! Interestingly solving 1a,1b,1c does not require any new algorithm, ...just piping the existing data into the display ... the existing spacing of sorted list display has available whitespace. (Now at the end of my sermon, please tell me it was a wasted appeal, and that there is already an overlooked toggle setting to display date somewhere in the admin interface) This link to a long thread on Future of Pipermail is old http://mail.python.org/pipermail/mailman-developers/2000-November/007823.html This is a clue to me that the future is NOW and the archiver is languishing from developer interest ...to any developer on this user list,please post this DATE issue into the developer-list. I hope my pitch for DATE DISPLAY is well received by developers who follow this userlist and provocative enough to earn a short thread and priority in the next version. Thanks Tyrus Maynard In the hopes that this proposal for a simple change in the display of the pipermail archive will be perceived as a contribution to the mailman cause and receive further comment on this thread I am placing copy ABOVE extra comment. Some may wish to categorize my lengthy post with a reference to some historical past pipermail discussion on the developer list as an accident, but there it is, free, and reasoned by one user. If anyone wishes to wait for me to offer code, then one would not really be interested in correcting deficiency that I have described any time in the near future even for a simple fix. (If I am not qualified to add the code for even this simple fix should I still post to the developer-list?). My understanding of the role of this user-list is to develop dialogue that identifies mandates for those that do develop code. I have placed my initial content at the top of this post hoping that it will receive attention and comments on its merits. Is this a suggestion worthy of Mailman? Please add your view on the merits along with additional pointed critique. Maybe there are reasons to leave Mailman the way it is in this simple matter of display of date. Tyrus Maynard -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ:
[Mailman-Users] Path info. No list -2- error
Some time ago the archive search on tug.org got broken; while the first page with search results looks fine, attempts to access consequent pages return error: htdig Archives Access Failure Path info. No list -2- It looks like all 45+ lists are affected (I checked only four). Does anyone have a suggestion what may cause this and what to look for? We're running mailman 2.1.2 with htdig 3.1.6 under RedHat 7.2; last htdig patch applied: htdig-2.1.2-0.3.patch. Kaja -- 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] Migrating from Lyris to Mailman - Lookingforfunctionality and/or workarounds
On Fri, Jul 18, 2003 at 07:50:39AM -0700, Karen G. Schneider wrote: - Daily, weekly, and/or monthly subscription reports to list managers with numbers of new subscriptions, unsubscribe, bounces, etc. This would be extremely useful. Could we see this in a future release? And while we're begging for features, on the report I'd like to see how many subscribers actually got the postings. Example, if you have a 50K user list, but only 45K were successfully delivered, I'd like to know that. Ideally, I'd like to be able to get this for *every* posting. This would be ideal for announcement-only lists. -- 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
[Mailman-Users] RE: Mail bouncing if sent tomailman-owner@testlist.localdomain2.com
Hi Paul, Thanks for your mail, but i tried creating mailing-list on the command-line like this: $: /mailman/bin/newlist --quiet Enter the name of the list: mylist Enter the email of the person running the list: [EMAIL PROTECTED] Initial mylist password: Entry for aliases file: ## mylist mailing list ## created: 18-Jul-2003 root mylist: |/mailman/mail/wrapper post mylist mylist-admin:|/mailman/mail/wrapper mailowner mylist mylist-request: |/mailman/mail/wrapper mailcmd mylist mylist-owner:mylist-admin should i need to add the above three lines to my /etc/alaises ..?? If so any mail i address to 'mailman-owner' will be sent..?? and also i didnt find the program 'newaliases'. Thanks for your help Schalla When you create a list you get a set of aliases that need to be added to /etc/aliases. If you created via the web the aliases were mailed to the list administrator. If you created the list via SSH the aliases were listed there. Without these aliases your server has no way to process mailman addresses. And of course do newaliases if needed. Paul Hi, Im using using mailman integrated with another application. When i create a list i get a mail from [EMAIL PROTECTED] saying that mailing list has been created and the list address..and in the last part of the mail it says Please address all questions to [EMAIL PROTECTED]. Now what i did was i sent a mail to [EMAIL PROTECTED], but the mail bounces with the following content: --- Date: Thu, 17 Jul 2003 14:37:36 +0530 From: Mail Delivery System [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] unknown local-part mailman-owner in domain localdomain2.com -- This is a copy of the message, including all the headers. -- Can anyone tell me how to enable this account or where to configure, so that the mail sent to [EMAIL PROTECTED] is delieverd...?? The following are the configuration settings in the mailman/Mailman/Default.py: - # Don't change MAILMAN_URL, unless you want to point it at the list.org # mirror. MAILMAN_URL = 'http://www.gnu.org/software/mailman/mailman.html' #MAILMAN_URL = 'http://www.list.org/' # Site-specific settings DEFAULT_HOST_NAME = 'linuxroute.dev.sf.net' # DEFAULT_URL must end in a slash! DEFAULT_URL = 'http://linuxroute.dev.sf.net/mailman/' # PUBLIC_ARCHIVE_URL and PRIVATE_ARCHIVE_URL should not end in slashes! PUBLIC_ARCHIVE_URL = '/pipermail' PRIVATE_ARCHIVE_URL = '/mailman/private' HOME_PAGE = 'index.html' MAILMAN_OWNER = '[EMAIL PROTECTED]' % DEFAULT_HOST_NAME The config details in the mailman/Mailman/mm_cfg.py are: # Put YOUR site-specific settings below this line. DEFAULT_HOST_NAME = 'localdomain2.com' DEFAULT_URL = 'https://localdomain2.com/mailman/' PUBLIC_ARCHIVE_URL = '/mailman/archives' USE_CRYPT = 0 MAILMAN_OWNER = '[EMAIL PROTECTED]' Before posting this question i tried adding aliase to /etc/aliases like this: mailman-owner: root after doing this i was able to send mail to [EMAIL PROTECTED] from the same machine, but this approach fails when i try to send mail to the same id from a different machine. Can anyone help. Thanks in advance. Schalla -- 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] question
Hi there, I have attempted to use mailman to send 1 email announcment to 200 people on my mailing list, however I found that most people didn't get the email because it was filtered as junk mail by their junk mail filters since the email was not sent directly to their email address, but rather a [EMAIL PROTECTED] address. Is there a way to have mailman send 1 email announcement to each member, one at a time, so that the email is addressed to each individual specifically? Thanks, lauren -- 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] (no subject)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 schuetzen wrote: when is cPanel going to bring out 2.1.n Mailman and WHY have they not yet done it and WHY are they still using old RHat? chas They do have a mailman 2.1.2 package available. A host I use which (unfortunately) uses cPanel just upgraded to it last week. They still have the broken behavior with trying to change the case of listnames and even the guy running the host says they are pretty unresponsive to requests for details on that and other issues. So much for the GPL requirement that they make their patches available. I've sure had no joy trying to get a hold of the changes they've made to mailman. - -- Todd OpenPGP - KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp Reality is that which, when you stop believing in it, doesn't go away. -- Philip K. Dick -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE/GCtNuv+09NZUB1oRAnWsAKD2cDO0yWWe0cPSTgmYs2o7+sRYbgCfeTzI zZsRGN0c4cw3nFqqD2iWv7E= =6a3h -END 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/ 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] Path info. No list -2- error
On Friday, July 18, 2003, at 05:37 PM, Kaja P. Christiansen wrote: Some time ago the archive search on tug.org got broken; How broken? while the first page with search results looks fine, attempts to access consequent pages What do you mean by 'subsequent pages' return error: htdig Archives Access Failure Path info. No list -2- This error says that the URL being used to access the mmsearch CGI script is malformed as it does not have the name of the list being searched embedded in it. What is URL showing in the location field of the browser when you get the problem response. The URI should look something like: /mailman/mmsearch/listname It looks like all 45+ lists are affected (I checked only four). Does anyone have a suggestion what may cause this and what to look for? We're running mailman 2.1.2 with htdig 3.1.6 under RedHat 7.2; last htdig patch applied: htdig-2.1.2-0.3.patch. There is a later version of the #444884 patch but it doesn't sound as if the fix it incorporates is for your problem: htdig-2.1.2-0.4.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. The best I can suggest without further information is: 1. select one of the lists exhibiting your problem as a test list. 2. run $prefix/bin/blow_away_htdig for that list. This will remove all the htdig related stuff for the list; per-list htdig conf file and search indexes, delete search form from the list's TOC page and such. This should be non-destructive of the list archive material itself. 3. post a message to the test list. This should cause re-creation of the per-list htdig.conf file and add the search form to the list's TOC page. 4. run the nightly_htdig cron script from the command line for the test list. This should re-create the test list's search indexes. Now see if the problem still exists for the test list. If the procedure has cleared it then repeat the procedure without specifying a particular list, to do all lists, or for individual lists if you prefer. If the test list still has the problem then get back to me. If the procedure fixes the problem then also let me know. Kaja -- 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] question
On Friday, July 18, 2003, at 03:40 PM, Lauren Goldwert wrote: Hi there, I have attempted to use mailman to send 1 email announcment to 200 people on my mailing list, however I found that most people didn't get the email because it was filtered as junk mail by their junk mail filters since the email was not sent directly to their email address, but rather a [EMAIL PROTECTED] address. Sounds like a fairly brain-damaged filter if it is applying rules to the To: header. Your list member's addresses are on the SMTP envelope of the messages or they wouldn't get to the MTA which should be trying to deliver to them. SMTP delivery is not based on the headers in the message but the address on the SMTP envelope. Is there a way to have mailman send 1 email announcement to each member, one at a time, so that the email is addressed to each individual specifically? Thanks, lauren You do not say what version of MM you are running. If it is 2.1.x then you could try turning on full personalization on the on the non-digest option page of the web admin GUI for your list. I think this will lead to individual messages containing To: headers with the member addresses in them. You will pay a performance penalty but as they count of members is quite low ... If you do this you might as well turn on VERP for personalized messages and get the benefit of more precise bounce handling, given that you are expending the cost of personalization. -- 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] Heavy load...
On Friday, July 18, 2003, at 11:17 AM, Nejc Skoberne wrote: Hi. mailman 25332 0.0 0.1 7420 276 ?SJul14 0:00 /usr/bin/python bin/mailmanctl start mailman 25333 0.0 1.4 7916 3708 ?SJul14 0:13 qrunner /usr/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 25334 0.0 1.0 7516 2784 ?SJul14 0:01 qrunner /usr/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 25335 0.0 0.5 7308 1324 ?SJul14 0:01 qrunner /usr/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 25336 0.0 1.2 7612 3180 ?SJul14 0:06 qrunner /usr/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 25337 0.0 0.5 7348 1460 ?SJul14 0:01 qrunner /usr/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 25338 95.5 1.3 7904 3428 ?RJul14 5048:09 qrunner /usr/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 25339 0.0 1.0 7612 2816 ?SJul14 0:12 qrunner /usr/mailman/bin/qrunner --runner=VirginRunner:0:1 -s This is how my mailman processes look like. I installed Mailman following instructions in tarball. I am running this on Celeron 333 with 256 MB RAM, Postfix 2.0.13, MailScanner + SpamAssassin. This is not normal behaviour, is it? You fail to say what version of Mailman you are running but it looks like Mailman 2.1.x. MM 2.1.x runs a number of daemon processes, started by $prefix/bin/mailmanctl. Each of these daemons handles a different aspect of MM's operation, being responsible for handling mail that has been inserted into one a number of queues depending on what processing has to be done to it. The above looks entirely normal. What is your problem? Is something with your installation not working correctly? I checked system logs but couldn't find anything unusual. Any ideas? Yes. Maybe nothing is wrong? Thank you in advance. Best regards. -- Nejc Skoberne Grajska 5 SI-5220 Tolmin E-mail: [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] Migrating from Lyris to Mailman - Lookingforfunctionality and/or workarounds
Yes, all of this functionality is standard on the old version of Lyris we were on (4.2). And, we would be willing to pitch in some money for this enhancement ($hundreds). I wonder if there are others who would make donations to support this sort of enhancement and if that could enable some dev time to be put towards this. Is this sort of donation for feature approach appropriate on a project like this? If so, how could we determine what it would take. Thanks, Miles On Friday, July 18, 2003, at 12:40 PM, Ed Wilts wrote: On Fri, Jul 18, 2003 at 07:50:39AM -0700, Karen G. Schneider wrote: - Daily, weekly, and/or monthly subscription reports to list managers with numbers of new subscriptions, unsubscribe, bounces, etc. This would be extremely useful. Could we see this in a future release? And while we're begging for features, on the report I'd like to see how many subscribers actually got the postings. Example, if you have a 50K user list, but only 45K were successfully delivered, I'd like to know that. Ideally, I'd like to be able to get this for *every* posting. This would be ideal for announcement-only lists. -- 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/miles%40iapps.com Miles Fawcett, President direct 202.449.7222 - main 202.265.3700 - eFax 202.742.5704 email [EMAIL PROTECTED] AIM:miles202 website www.iapps.com I N T E R A C T I V E ? A P P L I C A T I O N S ? G R O U P?? I N C ??(iapps) Strategic Internet Solutions for Foundations and Nonprofits -- 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] LockFile permissions denied???
i installed the latest version of mailman on Apache and use Sendmail as the MTA, but when the automated process tries to run mailman it comes back with an error. From: [EMAIL PROTECTED] (Cron Daemon) To: [EMAIL PROTECTED] Subject: Cron [EMAIL PROTECTED] /usr/bin/python -S /var/mailman/cron/gate_news X-Cron-Env: SHELL=/bin/sh X-Cron-Env: HOME=/home/rday X-Cron-Env: PATH=/usr/bin:/bin X-Cron-Env: LOGNAME=rday Traceback (most recent call last): File /var/mailman/cron/gate_news, line 274, in ? main() File /var/mailman/cron/gate_news, line 249, in main lock.lock(timeout=0.5) File /var/mailman/Mailman/LockFile.py, line 238, in lock self.__write() File /var/mailman/Mailman/LockFile.py, line 415, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/var/mailman/locks/gate_news.lock.gal adriel.educara.net.18390.0' i checked all the permissions and the owner of all the files has write privilages. the owner of them is mailman, so i don't see how Permissions to write are being denied. any advice? --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.488 / Virus Database: 287 - Release Date: 6/5/2003 -- 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
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=detailaid=728836group_id=103atid=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] LockFile permissions denied???
On Friday, July 18, 2003, at 08:54 PM, Ryan Day wrote: i installed the latest version of mailman on Apache and use Sendmail as the MTA, but when the automated process tries to run mailman it comes back with an error. From: [EMAIL PROTECTED] (Cron Daemon) To: [EMAIL PROTECTED] Subject: Cron [EMAIL PROTECTED] /usr/bin/python -S /var/mailman/cron/gate_news X-Cron-Env: SHELL=/bin/sh X-Cron-Env: HOME=/home/rday X-Cron-Env: PATH=/usr/bin:/bin X-Cron-Env: LOGNAME=rday Traceback (most recent call last): File /var/mailman/cron/gate_news, line 274, in ? main() File /var/mailman/cron/gate_news, line 249, in main lock.lock(timeout=0.5) File /var/mailman/Mailman/LockFile.py, line 238, in lock self.__write() File /var/mailman/Mailman/LockFile.py, line 415, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/var/mailman/locks/gate_news.lock.gal adriel.educara.net.18390.0' i checked all the permissions and the owner of all the files has write privilages. the owner of them is mailman, so i don't see how Permissions to write are being denied. any advice? From the notification (To: [EMAIL PROTECTED] ) it looks as though you may have installed the mailman crontab under your own user id. If you did that might account for the problem. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.488 / Virus Database: 287 - Release Date: 6/5/2003 -- 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] PostFix virtual domain aliases integrated?
I seem to remember seeing that Mailman had integrated into it the ability to automatically create virtual domain aliases in Postfix instead of the sendmail-type aliases. I just created my first new list since updating to 2.1.2 (from 2.1b3) and they didn't get created. Am I remembering wrong? 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
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/listname/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=detailaid=728836group_id=103atid=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] Bad digest mesg
I just got the below message from Mailman. Is there any way to find out which message it's having problems with? FreeBSD 4.6.2 Mailman 2.1.1 w/ htdig Thanks, Will Begin forwarded message: Date: Fri, 18 Jul 2003 12:00:03 -0700 (PDT) From: [EMAIL PROTECTED] (Cron Daemon) To: [EMAIL PROTECTED] Subject: [Mailman] Cron [EMAIL PROTECTED] /usr/local/bin/python2.2 -S/usr/local/mailman/cron/senddigests Traceback (most recent call last): File /usr/local/mailman/cron/senddigests, line 94, in ? main() File /usr/local/mailman/cron/senddigests, line 86, in main mlist.send_digest_now() File /usr/local/mailman/Mailman/Digester.py, line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 123, in send_digests send_i18n_digests(mlist, mboxfp) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 295, in send_i18n_digests msg = scrubber(mlist, msg) File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 302, in process t = unicode(t, partcharset, 'replace') TypeError: decoding Unicode is not supported -- Will Froning Unix Sys. Admin. (209)946-7470 (209)662-4725 [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] Mailman htdig integration patch
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/listname/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=detailaid=728836group_id=103atid=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
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/listname/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=detailaid=728836group_id=103atid=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
[Mailman-Users] RE: Mail bouncing if sent tomailman-owner@testlist.localdomain2.com
Shobhan Challa wrote: Thanks for your mail, but i tried creating mailing-list on the command-line like this: $: /mailman/bin/newlist --quiet Enter the name of the list: mylist Enter the email of the person running the list: [EMAIL PROTECTED] Initial mylist password: Entry for aliases file: ## mylist mailing list ## created: 18-Jul-2003 root mylist: |/mailman/mail/wrapper post mylist mylist-admin:|/mailman/mail/wrapper mailowner mylist mylist-request: |/mailman/mail/wrapper mailcmd mylist mylist-owner:mylist-admin Looks about right. Different than what I get, but it could be the version being run. should i need to add the above three lines to my /etc/alaises ..?? Correct, although I count 4 lines. If so any mail i address to 'mailman-owner' will be sent..?? The aliases intercept the mail and redirect it to the mail Mailman program. Where the owner mail goes will depend on the setting for the list. In this case owner is redirected to admin, which is redirected to the mail man wrapper and mailowner. and also i didnt find the program 'newaliases'. It is part of Linux, and on many (most?) systems it must be run after changes are made to the aliases file in order for the changes to be registered. Check the comments at the top of your /etc/aliases file for information. 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
