[Mailman-Users] Upgrading from 2.1.3 to 2.1.4 ?
Hi! What is the easiest way to upgrade to 2.1.4 from 2.1.3 ? Sasa -- 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
FW: [Mailman-Users] Upgrading from 2.1.3 to 2.1.4 ?
oeps, forgot this one again -- Kind regards, Remko Lodder Elvandar.org/DSINet.org www.mostly-harmless.nl Dutch community for helping newcomers on the hackerscene -Oorspronkelijk bericht- Van: Remko Lodder [mailto:[EMAIL PROTECTED] Verzonden: zondag 25 januari 2004 17:16 Aan: Sasa Stupar Onderwerp: RE: [Mailman-Users] Upgrading from 2.1.3 to 2.1.4 ? ew in your body tekst is a typo (: I upgraded my ML by ./configure --$my-settings make make install.. cheers -- Kind regards, Remko Lodder Elvandar.org/DSINet.org www.mostly-harmless.nl Dutch community for helping newcomers on the hackerscene -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sasa Stupar Verzonden: zondag 25 januari 2004 17:12 Aan: [EMAIL PROTECTED] Onderwerp: [Mailman-Users] Upgrading from 2.1.3 to 2.1.4 ? Hi! What is the easiest way to upgrade to 2.1.4 from 2.1.3 ? Sasa -- 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/mailman-users%40lists.e lvandar.org ___ Mailman-users mailing list [EMAIL PROTECTED] http://lists.elvandar.org/mailman/listinfo/mailman-users -- 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] Upgrading from 2.1.3 to 2.1.4 ?
Didn't know it was so easy. Allready done it and it is working like a charm. Thank you. Sasa Remko Lodder pravi: ew in your body tekst is a typo (: I upgraded my ML by ./configure --$my-settings make make install.. cheers -- Kind regards, Remko Lodder Elvandar.org/DSINet.org www.mostly-harmless.nl Dutch community for helping newcomers on the hackerscene -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sasa Stupar Verzonden: zondag 25 januari 2004 17:12 Aan: [EMAIL PROTECTED] Onderwerp: [Mailman-Users] Upgrading from 2.1.3 to 2.1.4 ? Hi! What is the easiest way to upgrade to 2.1.4 from 2.1.3 ? Sasa -- 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/mailman-users%40lists.e lvandar.org ___ Mailman-users mailing list [EMAIL PROTECTED] http://lists.elvandar.org/mailman/listinfo/mailman-users -- 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: Too Many Headers
Dan Phillips wrote: From: Dan Phillips [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Too Many Headers To: Brad Knowles [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII; format=flowed On Jan 23, 2004, at 10:17 AM, Brad Knowles wrote: Brad Knowles wrote: What version of Eudora has this problem? I'm using Eudora 6, and while I have it configured to hide all List-* headers by default, when I click on the button to show all headers, the List-* headers are properly displayed, correctly highlighted, and will Do The Right Thing when you click on the highlighted portion -- 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 Headers
At 8:07 AM -0500 2004/01/24, Steve Burling wrote: There's a slightly easier (and more Mac-like :-) way to do this. Follow step 1 to find the original application icon. Then: Okay, I've been using Unix for about twenty years, and a Mac fanatic for the same length of time. I've also been using MacOS X since 10.1. And you've taught me something new. Cool. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++) -- 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] Unsubscribe without a password
I am very interested in the topic of configuring Mailman to allow subscribe/unsubscribe requests without a password. From the archives Simon White offered something of a solution and was willing to share it, but his email was not in the message (as it should be). I would be interested in Simon's or any other's solutions or thoughts on a solution. archive If you make your own subscribe page which takes the email address and adds it to a text file, you can schedule a task every night to read that file and unsubscribe the addresses in it. I have a version of this theory working on a server using PHP, a little shell script, and cron. Let me know if it's of any use to you. Regards, -- Simon White. Internet Consultant, Linux/Windows Server Administration. email, dns and web servers; php javascript perl asp; MySQL MSSQL Access Bridging the gap between management, HR and the tech team. /archive Thanks! Brian Haines -- 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] Unsubscribe without a password
On Sun, Jan 25, 2004 at 11:17:34PM -0500, Brian Haines wrote: I am very interested in the topic of configuring Mailman to allow subscribe/unsubscribe requests without a password. From the archives Simon White offered something of a solution and was willing to share it, but his email was not in the message (as it should be). I would be interested in Simon's or any other's solutions or thoughts on a solution. ~mailman/bin/add_members and ~mailman/bin/remove_members. These require privs. You should be aware that there are morons out there that will try to spam your lists with messages and probably fake subscribe/unsubscribe messages. If you allow for an Internet-wide subscribe without confirmation, you could easily be classified a spammer and end up on blackhole lists. You better know what you're doing before you dig into this. It isn't that hard for a user to subscribe or unsubscribe themselves. Admins, of course, can do it for them with the utilities I listed above or via the web pages. -- 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] recovering from total loss
I'm trying to recover froma total server loss. This means the lists are now re-setup on a new server adn the only form of remaining backup are the personal mailfiles, containing all the lists files, one user with 2 text based files of the list's archives and one with several digest. what is the easiest way, if any, to restore the archives, any idea or shortcut will be welcome, we are talking several thousand emails here. kind regards abel -- Outgoing mail is certified Virus Free. Checked by AVG Anti-Virus (http://www.grisoft.com). Version: 7.0.211 / Virus Database: 261.7.4 - Release Date: 24/01/2004 -- 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] 403 Forbidden error (problem resolved)
I have been having problems getting access to my public archives from a browser. I have been getting 403 Forbidden error accessing public archives errors. This seems to be a particularly popular problem with many requests for advice, yet only few posts with helpful suggestions. Fortunately, I was able to piece them together to solve my problem. In the past, I have received much help and advice (not to mention excellent software) from the good people at list.org and the people on the Mailman-Users mailing list. So, I thought that I might be able to pay some of that generosity back by offering a short summary of what caused my problem and how I fixed it. Either someone will be able to search the Mailman-Users archives and find this message or else someone more articulate and knowledgeable than me about Mailman could polish it up and find a place for it in the Mailman FAQ located at http://www.python.org/cgi-bin/faqw-mm.py?req=all. Symptom: 403 Forbidden error accessing public archives Platform: FreeBSD 4.6-RELEASE Mailman Version: Currently 2.1.3. I first installed mailman about 2 years ago. So, this version has been upgraded and updated to 2.1.3. This was, I think, part of my problem. Solution: The first thing I did was navigate to the /usr/local/mailman/bin directory and run ./check_perms. I found that not all of my permissions were set correctly. So, I re-ran ./check_perms -f (for fix). This fixed the permissions. But, I still was being denied access. The second step was to verify my settings were correct in Apache. I played around with httpd.conf for a little. But, nothing seemed to help. Remember that if you modify httpd.conf that you need to restart Apache with apachectl restart for your changes to work. It turns out that there was nothing wrong with my file. Here is what I currently use: ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ Directory /usr/local/mailman/cgi-bin/ AllowOverride None Options FollowSymLinks ExecCGI Order allow,deny Allow from all /Directory Alias /pipermail/ /usr/local/mailman/archives/public/ Then, I stumbled upon a thread at http://mail.python.org/pipermail/mailman-users/2003-June/029602.html that pointed me to the solution of my problem. I was able to get access to my archives by making the following changes. # ** The following line was added DEFAULT_URL_PATTERN = 'http://%s/mailman/' # ** The following line was replaced by the line after it. # PUBLIC_ARCHIVE_URL = '/pipermail' PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/pipermail/%(listname)s' One thing that I might point out here is that you can put the above lines in mm_cfg.py literally. You do not have to make substitutions for (hostname) and (listname). Just copy and paste. This is something that was not clear to me in the thread. I often run into that issue when trying to follow online docs. I thought it would be helpful to point it out. * IMPORTANT ** After you make changes to your mm_cfg.py file, you need to run ./withlist -l -r fix_url (your list name) on every existing list. Here, you do need to make substitutions for (your list name). You can get a list of your lists with ./list_lists. Also, you need to stop and restart Mailman with, mailmanctl restart. It is possible that only certain changes to your mm_cfg.py necessitate the running of withlist and Mailman restart. But, I don't see where it hurts to run them anyway (unless of course your want old lists to remain untouched and new lists to incorporate your changes). Finally, this may shed some light on things for other FreeBSD users. Earlier I stated that part of my problem was due to the fact that Mailman has been upgraded on my system. This is why I believe that. The PUBLIC_ARCHIVE_URL used to work the way it was (see above). And, I noticed a few months back when I created a new mailing list that things like default paths and default email addresses didn't work on my new lists. If I'm not mistaken, the old lists continued to work though. I am just now associating the two problems. Apparently, the jump from 2.0.x to 2.1.x made some serious changes in how the mm_cfg.py file works. I upgrade my system with portupgrade, and I rarely have any issues. This time, the new requirements went unnoticed. I hope this helps someone. darren -- 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] recovering from total loss
On Sun, 2004-01-25 at 23:24, Abel Wisman wrote: I'm trying to recover froma total server loss. This means the lists are now re-setup on a new server adn the only form of remaining backup are the personal mailfiles, containing all the lists files, one user with 2 text based files of the list's archives and one with several digest. what is the easiest way, if any, to restore the archives, any idea or shortcut will be welcome, we are talking several thousand emails here. kind regards abel The archives are stored in an mbox format. If your email stores it's files in that format, then your very close to having exactly what you need. If you need to move the mail over to an mbox format from an email client, then you should consider bringing up an IMAP server on your Mailman server - just long enough to transfer your local mail up to the server (via your email clients IMAP connection). 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
