Re: [Mailman-Users] This is unixstuff warning
On Thu, Jun 14, 2001 at 12:44:10AM -0700, J C Lawrence wrote: Do some Google searches on Chuq. He's earned, not claimed, his laurels. You're preaching to the choir. :) -- Linux Now! ..Because friends don't let friends use Microsoft. phil stracchino -- the renaissance man -- mystic zen biker geek Vr00m: 2000 Honda CBR929RR -- Cage: 2000 Dodge Intrepid R/T Previous vr00mage: 1986 VF500F (sold), 1991 VFR750F3 (foully murdered) -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] This is unixstuff warning
Some wisdom posted on the exim list a while back (on the subject of trying to persuade people that its not some person with good typing skills sending out bounce messages) may fit into the current discussion. See http://www.exim.org/pipermail/exim-users/Week-of-Mon-2710/019372.html Nigel. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Announcement only
Newbie question: Can I ensure that my list: - can only receive posts from the administrator - will not pass unauthorised posts for moderation, but just rejects them - is nice and secure generally (maybe a posting password or something?) ? TIA Jeremy SharpTechnical Director Twang.Net Ltd+44 1635 239000 - Switchboard+44 1635 239009 - Direct+44 1635 239001 - Fax
Re: [Mailman-Users] Announcement only
On Thu, 14 Jun 2001, Jeremy Sharp wrote: Can I ensure that my list: - will not pass unauthorised posts for moderation, but just rejects them This is not possible in any released version of the software. -- ROGER B.A. KLORESE [EMAIL PROTECTED] PO Box 14309San Francisco, CA 94114 Go without hate. But not without rage. Heal the world.-- Paul Monette -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] aliases.py + wrapper script
When I make a new list with the bin/newlist command, I want it to update the /etc/aliases list and run the newaliases command (use sendmail as MTA). aliases.py says: # TODO: # - fix this file! /etc/alias hacking no longer works # Write a wrapper program w/ root uid that allows the mailman user # only to update the alias database. Have anyone done this, and can give me a link to an example wrapper program. And does the newlist script need any changes in order to make this work? -- Jørgen Ruud [EMAIL PROTECTED] -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Moving mailman to a new machine
Hi all, I need to move mailman to a new machine. Is there any reason I can't just tar up the mailman home directory and unpack it on the new machine?? The original machine will be taken out of service and the new machine will be given the same name. My mailman installation is small at this point. Only about 10 lists without much activity. -- _ Gedaliah Wolosh, Ph.D. 973 596-5437 New Jersey Institute of Technology Fax 596-2306 323 King Blvd GITC 2203 [EMAIL PROTECTED] Newark, NJ 07102 -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Can You Delete A Message From an Archive?
JF == Jim Fannin [EMAIL PROTECTED] writes: JF We have a unique circumstance in which a mail message was JF posted, approved and sent to a list which turned out to have JF erroneous information in it. Management would like to remove JF the message from the archive which is public. Anyone know how JF to do this without killing the archive? Just manually edit the message out of the .mbox file and re-run bin/arch. Take care when you edit .mbox though; you want to remove the envelope-from header of the offending message too. -Barry -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Sending without implicit approval
MF == Martin Foster [EMAIL PROTECTED] writes: MF This normally would not be a problem, as we could simply do MF this manually. However, in time this may get to be a rather MF large hassle. Is there a way to keep all of the lists MF synchronized in such a way that they all have the same MF implicit sending list? I would even gladly write a script if MF I knew how to directly modify the list to take on this option. You could write a bin/withlist script to add that list of addresses to the `posters' attribute of every mailing list. Shouldn't be more than a few lines of Python to keep that in sync. -Barry -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Announcement only
I wouldn't think you'd want to do it, either... half the time people are posting to moderated lists, they are actually trying to email the list administrator, who *should* see their messages. You could always add a header to the bounce message explaining where to reach that person, and then write a script to clean out the messages waiting for approval... On Thu, Jun 14, 2001 at 03:26:28AM -0700, Roger B.A. Klorese wrote: On Thu, 14 Jun 2001, Jeremy Sharp wrote: Can I ensure that my list: - will not pass unauthorised posts for moderation, but just rejects them This is not possible in any released version of the software. -- ROGER B.A. KLORESE [EMAIL PROTECTED] PO Box 14309 San Francisco, CA 94114 Go without hate. But not without rage. Heal the world.-- Paul Monette -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] This is unixstuff warning
On Thu, 14 Jun 2001 10:41:48 -0400, JT wrote: [deletia] users (like web *and* mail-command use). Perhaps an install-time or list-creation-time option to choose standard templates or 'newbie' templates would be a good idea. If I get time to write an alternate template, or if I write one for a list I'm managing, I'll send it in with a patch to newlist for this... An expert and newbie template, Yum! You could also solve a FAQ by making a Discussion vs Distribution template. - H -- Harold Paulson Sierra Web Design [EMAIL PROTECTED] http://www.sierraweb.com VOICE: 775.833.9500 FAX: 810.314.1517 -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] This is unixstuff warning
On Thu, 14 Jun 2001 07:55:22 -0700 Chuq Von Rospach [EMAIL PROTECTED] wrote: On Thursday, June 14, 2001, at 12:44 AM, J C Lawrence wrote: Maintaining good will and earnestness in the face of continual unresponsive blunt assault tends to be dehumanising. You even see it on this list, both at the people who come here to ask questions, and among the regular residents. Yup. I see it in myself and my willingness to launch into explanations of solutions versus snap answers which point to only the root of the problem and nothing else. I don't know that there are any elegant answers when you spend human capital that way, I'll tell you what two of the answers are: 1) really damn good documentation. Write the best docs you possibly can, then go make them better. Good user interfaces, clear explanation, solid navigation, and serious ease of use. Make the system so easy it's hard to get lost or confused -- and then document everything for those that get lost and confused anyway. 2) automate as much as you can for the admins. The more grunt work the admin has to do, the less likely it'll get done, and the more likely the admin will be grumpy about doing his work. Admins ought to be there to handle the out-of-bounds cases, errors and emergencies. The easier you make a system for the admin, the better for everyone. Translation: 1) If possible make the Right Thing the obvious default for users. If not possible, make the Right Thing as close as you can to a Duh! thing (for them). 2) If you don't need to think about what to do, you shouldn't have to do it -- the system should do it for you. Humans are there because they are intelligent, not because they can emulate machines. Unfortunately, hacking code is fun-work. Writing docs, user testing, interviewing typical users, more user testing, navigation design, good UIs -- that stuff is all work-work, and it tends to be left until late in the process, if ever. I'm especially bad in that regard, and I haven't helped the situation WRT Mailman. And I note for the record that my suggestion that everyone stop blaming mailman's problems on stupid users and instead go fix mailman fell on deaf ears -- but it seems to have shut down the thread at the same time. I'd translate the reaction, as: Umm, oh yeah. Well he's right you know, it kinda isn't a stupid luser problem, its uhh, that we didn't make the system help the user when we know we could have. The tricky bit is ensuring that they (of COURSE this doesn't enclude me) don't shuffle off embarrassed until the next time its easier to blame someone else rather than looking closer to home. Its all his fault officer! He ran into my car! You were stopped in the middle of the intersection with your lights off in the middle of the night during a blackout right? Yeah, but he could have seen me if he'd looked! Because it's easy/fun to blame users and call them stupid, but fixing mailman is hard work. And it seems most people here are interested in taking the easy road, and not deal with the real problem. I'm not surprised. Putting the self-destruct button in the middle of the steering wheel of the car I think I've earned one (and I don't care if you agree, actually. grin). If I've not been sufficiently clear to date: I/we'll miss you. Go relax. Enjoy. Get some RR. Take a deep breath. Please. Then hurry back -- there's a war on ya' know. But the first trick to building really good systems is to stop building things geeks like, and blaming non-geeks when they don't show interest in becoming a geek so they can use it. Until people figure that out and are willing to do the (hard) work of figuring out what REAL people need instead of what you want to give them, this chasm will still exist. It's an attitude thing more than anyhting else -- and the my users are stupid schitck is key to its existance. AOL has how many million susbcribers? What MLM has a control and configuration interface that would appeal to the average AOL user? Would an MLM whose interface did appeal to the average AOL user be necessarily inherently broken/torqued/crippled in some way? In terms of geekdom there's more of Joe Redneck than there are of us. And, of course, if you do the hard work, you run the risk of getting tired and needing a break... It's easier to slack off and blame others for not being good enough to understand what you've done. One of my semi-regular rants (well, to myself) for one of my hobby lists that lies close to my heart is that the users obviously don't understand what I'm trying to do with the list and are fighting me and making it more difficult. Are they so stupid that they can't see what I'm doing here? The rest of the analysis of that statement and its implications is all pretty obvious, AND rote, AND predictable, and yes, the obvious conclusions are also true. Its not a thing that helps me sleep at night. And thus
Re: [Mailman-Users] This is unixstuff warning
On Thursday, June 14, 2001, at 09:43 AM, Harold Paulson wrote: Perhaps an install-time or list-creation-time option to choose standard templates or 'newbie' templates would be a good idea. An expert and newbie template, Yum! Or, with a little more work, do both. New subscribers get the newbie template -- and for users who want a more expert version, allow them to set an option to turn it on. That's a classic way to make a system easy without turning it into a massive hassle for the more expert users. That ALSO allows you to make decisions what options are safe for new users to tweak, and what you ought to hide until they define themselves as experts. -- Chuq Von Rospach, Internet Gnome http://www.chuqui.com [[EMAIL PROTECTED] = [EMAIL PROTECTED] = [EMAIL PROTECTED]] Yes, yes, I've finally finished my home page. Lucky you. To the optimist, the glass is half full. To the pessimist, the glass is half empty. To the engineer, the glass is twice as big as it needs to be. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] This is unixstuff warning
On Thu, Jun 14, 2001 at 07:55:22AM -0700, Chuq Von Rospach wrote: And I note for the record that my suggestion that everyone stop blaming mailman's problems on stupid users and instead go fix mailman fell on deaf ears -- but it seems to have shut down the thread at the same time. Because it's easy/fun to blame users and call them stupid, but fixing mailman is hard work. And it seems most people here are interested in taking the easy road, and not deal with the real problem. I'm not surprised. But by that same token of being hard work, it takes a little time and thought. -- Linux Now! ..Because friends don't let friends use Microsoft. phil stracchino -- the renaissance man -- mystic zen biker geek Vr00m: 2000 Honda CBR929RR -- Cage: 2000 Dodge Intrepid R/T Previous vr00mage: 1986 VF500F (sold), 1991 VFR750F3 (foully murdered) -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Announcement only
My apologies to all for bad formatting. -Ben --- Original Copy --- Subject: Fw: Re: [Mailman-Users] Announcement only Date: 06/14/2001 10:37 AM From: Ben Burnett[EMAIL PROTECTED] To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] On Thu, 14 Jun 2001, Jeremy Sharp wrote: Can I ensure that my list: - will not pass unauthorised posts for moderation, but just rejects them Jeremy, Ralf Laue has come up with a way to do this under very specific circumstances. If you can configure your Mailman installation the way he outlines it will work, but it isn't a simple thing to do. Below is an email he sent to me describing the process. I hope you find it useful. -Ben --- Original Copy --- Hello, Some weeks ago, you have posted a useful document about how to setup announce only mailman lists to the Mailman-Developers list. If you should write something like a HOWTO about this topic, you should consider one additional point: You describe how to configure a list to allow only certain addresses to post. However, these sender addresses can be faked very easily. If you really have to avoid unauthorized posting, I suggest another way: 1) Mailman and your mail server run on two different machines. 2) A firewall does not allow SMTP connections to the Mailman machine from the outside. SMTP is only possible to the mail server. 3) We must allow administrative requests to be sent to the Mailman machine from the outside. To do this: - point the MX entry for mailman.you.com from your external DNS to the mailserver - Set up an internal DNS that cannot be accessed from the outside and define a host entry (and MX) for realmailman.you.com, pointing to the Mailman server. - Create some forwardings on the mail server: [EMAIL PROTECTED] will be forwarded to [EMAIL PROTECTED] [EMAIL PROTECTED] will be forwarded to [EMAIL PROTECTED] (sendmail users could use virtusertable) Be sure that mail to [EMAIL PROTECTED] will NOT be forwarded to [EMAIL PROTECTED]! Note that your mail server as an internal server has access to the internal DNS server. For this reason it can send mail to realmailman.you.com. A user from the outside has not, so that realmailman.you.com is not visible from the outside. This is a much stronger solution, because nobody with a faked sender address can send mail to the Mailman server. However, it is still not safe enough if you have to be afraid of internal users sending unauthorized e-mail to the list. Best Wishes, Ralf Laue -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] aliases.py + wrapper script
i == iso [EMAIL PROTECTED] writes: i When I make a new list with the bin/newlist command, I want it i to update the /etc/aliases list and run the newaliases command i (use sendmail as MTA). aliases.py says: This will be supported in MM2.1. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] This is unixstuff warning
On Thursday, June 14, 2001, at 07:41 AM, JT wrote: Any job that brings you into contact with the general public is going to bring you to the inescapable conclusions that a good percentage of the population might as well walk around dressed in animal skins, dragging a human femur. A small percentage. maybe 1/2 of 1%. The problem is that their hassle factor is way out of proportion to their numbers. This is one of the classic reasons why things like usenet groups and mail lists don't scale well -- if you have a 500 member list and one dweeb on it, that's tolerable. If you have 5000 members and 10 dweebs, you and your members are going crazy from the noise. And it doesn't matter what size your list is, if a troll moves in. One is enough. Try working a cash register for a couple months and you'll see how true this is. or a telephone as a support person. For some reason (I'd guess the real power that technical competency brings), technical folks seem to have a little less patience to bring to dealing with the troublemakers. Partly, I think, because computers tend to attract people who aren't necessarily socially adept. Which probably sounds like more of a slap than I intend it to be, so I'll apologize for it up front. But computers have moved out of the raise-floor room and into the living room, so even the people who build the things can no longer get away with just dealing with other geeks... 1) Include the subscription address in the body of administrative mails sent to the individual user. Truly half the people who can't unsubscribe don't even know what address is subscribed. Majordomo suffers this flaw too - and To headers don't cut it, forget about Received. This should be in default installations. And the reason this was done was performance and resources. In other words -- it makes it easier for the MLM and the server, not the user. Which, when majordomo was designed and the user base was primarily small and technical, wasn't a bad design choice. Remember, majordomo's design goes back to the days of UUCP, 2400 baud modems and really slow networks. All of that changed, but the underlying designs haven't. This is one place where Lyris really has some good ideas, FWIW. We need to get out of the mindset of doing things to make it easier for the computer/software/network/admin, and put the end-users (i.e. customer) first. 2) Simplify the 'unsubscribe' option for people who've forgotten the passwords One of the things I'm working on is creating a one-click unsubscribe for my systems. It'll encode enough user information in the URL to be able to auto-search for the user and bring that user record up on the web page; and also extend the email side to use the plus notation ([EMAIL PROTECTED]) to pre-encode that as well, and get away from trying to use the From: line on email unsubs, since that's bogus on 5-7% of the email requests I see these days, thanks to hotmail, yahoo, corporate naming systems and people's wide use of .forwards... and passwords on unsubs are silly (sorry, Barry). Users who want to unsubscribe want off. they don't want to play games, they just want to leave. I have, in the last decade, seen ONE instance of forged unsubs on my mail lists, and that was a guy who was trying to make a point and so unsubsribed me from my own lists. Let's just say he didn't appreciate the response. -- Chuq Von Rospach, Internet Gnome http://www.chuqui.com [[EMAIL PROTECTED] = [EMAIL PROTECTED] = [EMAIL PROTECTED]] Yes, yes, I've finally finished my home page. Lucky you. You know, I Remember When I Used To Speak In Capitals, Too. It's addictive. It also encourages people to poke sticks at you. Justifiably. (chuq, 1992) -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
RE: [Mailman-Users] Allowing users to join without specifying passwords
Hmmm, the README says that script only currently works with unsubscribe requests, but does not handle subscribe requests. Is there any way to subscribe without supplying a password? It looks like Mailman is designed from the ground up with the assumption that passwords will be used. Is that correct? Thanks again for the help! -Joel This message, and any attachments which may accompany it, are for the sole use of the intended recipient(s) and may contain information that is confidential, privileged and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message. -Original Message- From: Satya [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 13, 2001 7:27 PM To: '[EMAIL PROTECTED]' Subject: Re: [Mailman-Users] Allowing users to join without specifying passwords On Jun 13, 2001 at 16:52, Joel Votaw wrote: I need to allow people to join and use the lists without specifying a password at all. I've dug through the docs including with the distribution, archives of this mailing list, and a number of Google searches and can't turn up the answer (however I've found plenty of information about turning off password reminder messages!). Actually, this is a FAQ. Try http://satya.virtualave.net/download.html#mailmanw -- Satya. URL:http://satya.virtualave.net/ US-bound grad students! For pre-apps, see URL:http://quickapps.cjb.net/ Computer lie #1: you'll never use all that disk space. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] This is unixstuff warning
On Thu, Jun 14, 2001 at 11:04:00AM -0700, Chuq Von Rospach wrote: [snip] A small percentage. maybe 1/2 of 1%. The problem is that their hassle factor is way out of proportion to their numbers. Agreed. [snip] Try working a cash register for a couple months and you'll see how true this is. or a telephone as a support person. *shudder* I was trying not to remember that one. [snip] 2) Simplify the 'unsubscribe' option for people who've forgotten the passwords One of the things I'm working on is creating a one-click unsubscribe for my systems. It'll encode enough user information in the URL to be able to auto-search for the user and bring that user record up on the web page; and also extend the email side to use the plus notation ([EMAIL PROTECTED]) to pre-encode that as well, and get away from trying to use the From: line on email unsubs, since that's bogus on 5-7% of the email requests I see these days, thanks to hotmail, yahoo, corporate naming systems and people's wide use of .forwards... Woohoo! This is better. Ultimately, anything harder than click here to unsubscribe isn't taking that extra step for the user. and passwords on unsubs are silly (sorry, Barry). Users who want to unsubscribe want off. they don't want to play games, they just want to leave. I have, in the last decade, seen ONE instance of forged unsubs on my mail lists, and that was a guy who was trying to make a point and so unsubsribed me from my own lists. Let's just say he didn't appreciate the response. I see both sides to that one, actually. It is, of course, far more interesting to annoy people by *subscribing* them to lists than unsubscribing them (easy enough on corporate sites, if not Mailman ones ;-), but still don't want it done to me - most users won't have the time or information to bother making the forger un-appreciate his action. There must be some way of doing this relatively low-impact and safe, like sending out a crypt of a piece of private user info. Of course, this means customized emails for each user, which is not zero-impact, but... 1) Don't provide an unsubscribe link 2) Accept the possibility of spoofing 3) Accept higher delivery costs (customized mail) The current flavor is 1), which does entail more work for users and admins... Geez, I'd better shut up before I find any more cats to bell. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] This is unixstuff warning
On Thursday, June 14, 2001, at 12:37 PM, J C Lawrence wrote: On three occasions we had unsub wars rather than admit defeat in an argument. I love that kind of person. Hell, when I was young and had to win fights, I was that person. it's kinda weird to be doing the in the Good Old days, when I was a young phart crap on the mailman list, because I just found out that an old friend from the Good Old Days, someone I've been estranged from for years for reasons that I won't go into, just died. Puts a whole bunch of things into perspective. I think I'm gonna go find a tree to sit under. I'll be back later. -- Chuq Von Rospach, Internet Gnome http://www.chuqui.com [[EMAIL PROTECTED] = [EMAIL PROTECTED] = [EMAIL PROTECTED]] Yes, yes, I've finally finished my home page. Lucky you. You know, I Remember When I Used To Speak In Capitals, Too. It's addictive. It also encourages people to poke sticks at you. Justifiably. (chuq, 1992) -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] SMTP All recipients refused: host not found (question)
I am running RH 7.1 , Sendmail , and Mailman 2.0.5 Basically I recieve this message in SMTP under /home/mailman/logs/smpt and a number of ignores in smtp-failure The strange part is that the list works fine from 3:00 am (or so (inconsistant)) untill 7:00pm or so.. it's only in the times between 7 and 3 that these messages crop up. crond is not running any unusual jobs, in fact qrunner is chuggin' away. The only thing I was able to dig up via the archives here was that the mm_cfg.py has to have the correct SMTPHOST = 'localhost' setting - I changed my localhost name. Could this be the only cause? The qued messages are sent as soon as the hiccup period is over Do You Yahoo!? Yahoo! Buzz Index - Spot the hottest trends in music, movies, and more.
[Mailman-Users] SMTP All recipients refused: host not found (question)
I am running RH 7.1 , Sendmail , and Mailman 2.0.5 Basically I recieve this message in SMTP under /home/mailman/logs/smpt and a number of ignores in smtp-failure The strange part is that the list works fine from 3:00 am (or so (inconsistant)) untill 7:00pm or so.. it's only in the times between 7 and 3 that these messages crop up. crond is not running any unusual jobs, in fact qrunner is chuggin' away. The only thing I was able to dig up via the archives here was that the mm_cfg.py has to have the correct SMTPHOST = 'localhost' setting - I changed my localhost name. Could this be the only cause? The qued messages are sent as soon as the hiccup period is over __ Do You Yahoo!? Spot the hottest trends in music, movies, and more. http://buzz.yahoo.com/ -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] stop email
I wish to stop getting email from you ! thank you!
Re: [Mailman-Users] This is unixstuff warning
On Thursday, June 14, 2001, at 12:43 PM, Chuq Von Rospach wrote: I think I'm gonna go find a tree to sit under. I'll be back later. sorry, folks. That was meant to go privately, not to the entire list. I pushed the wrong button. -- Chuq Von Rospach, Internet Gnome http://www.chuqui.com [[EMAIL PROTECTED] = [EMAIL PROTECTED] = [EMAIL PROTECTED]] Yes, yes, I've finally finished my home page. Lucky you. Shroedinger: We can never really be sure which side of the road the chicken is on. It's all a matter of chance. Like a game of dice. Einstein, refuting Schroedinger: God does not play dice with chickens. Heisenburg: We can determine how fast the chicken travelled, or where it ended up, but we cannot determine why it did so. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Moving mailman to a new machine
On Thursday 14 June 2001 08:39 am, Gedaliah Wolosh wrote: I need to move mailman to a new machine. Is there any reason I can't just tar up the mailman home directory and unpack it on the new machine?? The original machine will be taken out of service and the new machine will be given the same name. I've done this twice. It's not trivial (at least it wasn't for me), but it can be done. There are a couple of things you need to watch for. First, make sure the file owners and protections are properly set. This usually gets tricky if you're building a new system since your uids/gids probably changed. You may find it easier to see what they were when you started and set them to be the same on the new machine. Secondly, the archives are all done with links, and you need to make sure that they're set back properly. I ended up moving from one system that had the mailman tree in /home/mailman to another that was /var/mailman so I fought with it for a while to get it right, but eventually it all worked. If you've got good Unix skills to begin with, it shouldn't take you too long. If you don't, plan on killing an hour or two to get it right. Good luck, .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
