[Mailman-Users] RELEASED Mailman 2.1.3
I have released Mailman 2.1.3, a bug fix release which also contains support for four new languages: Ukrainian, Serbian, Euskara (Basque), and Danish. This release also contains a fix for a cross-site scripting vulnerability in the 'create' cgi script, as well as improved performance of the bounce and outgoing queue runners. I recommend all sites running versions of the 2.1.x line upgrade to the new version. The full source tarball has been made available from the usual sites (although the gnu.org sites have not yet been updated). Sorry, there is no patch available, but you should be able to install 2.1.3 over your existing 2.1.x installation. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to download all the patches and the source tarballs. After installing, be sure you restart your Mailman daemon by doing a mailmanctl restart. See also: http://www.gnu.org/software/mailman http://www.list.org (not yet updated) http://mailman.sf.net Cheers, -Barry snip snip 2.1.3 (28-Sep-2003) Performance, Reliability, Security - Closed a cross-site scripting exploit in the create cgi script. - Improvements in the performance of the bounce processor. Now, instead of processing each bounce immediately (which can cause severe lock contention), bounce events are queued. Every 15 minutes by default, the queued bounce events are processed en masse, on a list-per-list basis, so that each list only needs to be locked once. - When some or all of a message's recipients have temporary delivery failures, the message is moved to a retry queue. This queue wakes up occasionally and moves the file back to the outgoing queue for attempted redelivery. This should fix most observed OutgoingRunner 100% cpu consumption, especially for bounces to local recipients when using the Postfix MTA. - Optional support for fsync()'ing qfile data after writing. Under some catastrophic system failures (e.g. power lose), it would be possible to lose messages because the data wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True in Mailman/Queue/Switchboard.py, you can force Mailman to fsync() queue files after flushing them. The benefits are debatable for most operating environments, and you must ensure that your Python has the os.fsync() function defined before enabling this feature (it isn't, even on all Unix-like operating systems). Internationalization - New languages Ukrainian, Serbian, Danish, Euskara/Basque. - Fixes to template lookup. Lists with local overriding templates would find the wrong template. - .mo files (for internationalization) are now generated at build time instead of coming as part of the source distribution. Documentation - A first draft of member documentation by Terri Oda. There is also a Japanese translation of this manual by Ikeda Soji. Archiver / Pipermail - In the configuration variables PUBLIC_EXTERNAL_ARCHIVER, and PRIVATE_EXTERNAL_ARCHIVER, %(hostname)s has been added to the list of allowable substitution variables. - The timezone is now taken into account when figuring the posting date for an article. Scripts / Cron - Fixes to cron/disabled for NotAMemberError crashes. - New script bin/show_qfiles which prints the contents of .pck message files. New script bin/discard which can be used to mass discard held messages. - Fixes to cron/mailpasswds to account for old password-less subscriptions. - bin/list_members has grown two new options: --invalid/-i prints only the addresses in the member database that are invalid (which could have snuck in via old releases); --unicode/-u prints addresses which are stored as Unicode objects instead of as normal strings. Miscellaneous - Fixes to problems in some configurations where Python wouldn't be able to find its standard library. - Fixes to the digest which could cause MIME-losing missing newlines when parts are scrubbed via the content filters. - In the News/Mail gateway admin page, the configuration variable nntp_host can now be a name:port pair. - When messages are pulled from NNTP, the member moderation checks are short-circuited. - email 2.5.4 is included. This fixes an RFC 2231 bug, among possibly others. - Fixed some extra spaces that could appear in the List-ID header. - Fixes to ensure that invalid email addresses can't be invited. - WEB_LINK_COLOR in
Re: [Mailman-Users] __init__.py line 51 Empty module name
S == Sumeet [EMAIL PROTECTED] writes: S I seem to be getting alot (about 700) of these all of the S sudden w no changes to my Rhat 8.0/MM2.1.1 and sendmail S 8.11.6. Can someone please point me in the right S direction. thx, sumeet. S /usr/src/build/143041-i386/install/usr/lib/python2.2/encodings/__init__.py S , line 51, in search_function ValueError: Empty module name What version of Python are you using and did you install it from source or from RPM (e.g. it came with RH 8.0 when you installed the system)? If the latter, then the most likely cause is that RH's done it again, by splitting the standard Python distro and not including the standard encodings package with the basic Python RPM. You choices are to install all the other Python related RPMs or build Python 2.2.2 from source. It would be nice to know what RPM ends up fixing this and what Python packages it adds so that I can add the appropriate assertions to Mailman's installation scripts. -Barry -- 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] incorrect padding from senddigests
DE == Dwight Ernest [EMAIL PROTECTED] writes: DE binascii.Error: Incorrect padding I believe this is fixed in cvs and will be part of Mailman 2.1.2. No definite ETA on that yet though. -Barry -- 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] Lock aquired in future
TG == Thomas Guettler [EMAIL PROTECTED] writes: TG The locks seem to be requested in the future. This is by design. The lock's atime/mtime specifies the point in the future when the lock would time out. By default the lock lifetime is 5 hours. This is normal. -Barry -- 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] list.org down ??
ES == EnviroLink Support [EMAIL PROTECTED] writes: ES Does anyone know why list.org is down? This certainly makes ES me hesitate before making a decision about using Mailman. list.org's problems have nothing to do with the Mailman software. The machine (which hosts several other domains) had a meltdown. Please use the mailman.sf.net mirror for the time being. Cheers, -Barry -- 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] How can we ask for new features?
s == schuetzen [EMAIL PROTECTED] writes: s May dislike a lot about YHGroups but the programming they have s done on their mix of mailman, qmail and Lord knows what else - s is quite nice. Support sucks but... and there needs to be a s lot more batch operation capability on the member database s ... but it is still the friendliest interface out there. Really? Does YHG use Mailman? I find that surprising since I'm (un)fortunately on a number of YHG lists and I find their message and digest formatting absolutely abysmal. s Addressing one point - NoMail and Special Notices. s with Mailman, we have a NoMail feature but not the SN. s Personally, if I could do it, (but I take so much morphine I s have lost all logical thought progression so I can obviously s not program any longer), I would simply change the NoMail to a s version of both. ie, it would stop mail but would still allow s the member to receive emergency/admin messages. s is this a possible change? I'm not positive what SpecialNotices are but if you join me for a ride in my time machine (okay, okay, it's Guido's but he's not looking), I think we can come close. Mailman 2.1 has an Urgent feature. If your message has an Urgent header with a list admin or moderator password, the message is sent to all the list members regardless of their nomail or digest settings. Digest members will actually get the message twice, once as a regular delivery and once in the digest, but that's fine. s again, I have no idea what kind of language Python is nor do I s wish to try to learn as I do too much self abusing every day by s just looking at the scale, the mirror, yada G Python is guaranteed to improve your self confidence, grow hair on your head, lose 60 pounds, and add inches to the parts of your body you want to add inches to. It's low-carb, great tasting, environmentally friendly, and occasionally likes to go out on weekends and party in a family-appropriate way. s would appreciate any info on where we could send our ideas for s improvements of the software. really wish this had been s around 20 yrs ago!!! sigh chas Anything's possible with Guido's time machine! The best place to lodge new feature requests is the SourceForge RFE tracker: http://sourceforge.net/tracker/?group_id=103atid=350103 -Barry -- 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] Approved: Header
L == LuKreme [EMAIL PROTECTED] writes: L I checked the FAQ for info on the Approved header, but although L I found references to using it, I didn't find references to L exactly HOW to use it. L All I want is for a poster to a list to put an Approved line as L the first line of the body and then have that line stripped L before the message is passed to the list. L How do I set this up and what needs to be on the approved line? You don't need to do anything to set this up. Say you have a list with an admin password of geddy. If a non-member (or otherwise unapproved poster) sends a message to the list with a regular mail header of Approved: geddy then the message, which normally would be held or bounced, goes through to the list without moderation. Putting that line as the first non-whitespace line in the body of the message is equivalent. In both cases, the header and/or body line is removed before the message is forwarded. Approve: passwd is a synonym. Both the list admin password and the moderator password is accepted. Note that there's a related feature; if the header is Urgent: with the appropriate password, then the message is sent to all members immediately, including digest members (who get it twice -- once immediately and once in the digest). -Barry -- 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] EFF Mailing List Query
FYI, From the latest EFF mailer... -Barry snip snip * Mailing List Headaches? Contact us. EFF believes that delivery of legitimate e-mail needs to be carefully protected as a fundamental part of any solution to the spam problem. Unfortunately, we've lately learned that more and more opt-in mailing lists are being mislabeled as spam and wrongly blocked. EFF is looking for people who administer opt-in e-mail mailing lists and have had difficulty because their messages have been mislabeled as spam, causing delivery to fail. Our hope is to connect the folks facing this problem so that they can work together to find a global solution that both respects the Internet as a place of free speech (and e-mail as a vital organizing tool) while protecting Internet users and sysadmins from the problems that *real* spam causes. Contact [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] configuring Mailman
JH == Jim Hodson [EMAIL PROTECTED] writes: JH We want a very simple mailing list system, and Mailman can do JH a lot more than we need. I'm trying to find out how to best JH configure Mailman for our needs. Here is what we want to do: JH 1. Send e-mail news updates to our list. We do not want users JH to be able to send to the list. Some other suggestions: - Turn on the moderation flag for all your users. For existing users, go to the membership management page, and use the Additional Member Tasks to turn on the mod flag for all users. Then go to Privacy Options - Sender filters and set the default_member_moderation flag to Yes. - Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box. Say something like this is an announcement list, to reach the band, please email [EMAIL PROTECTED] - Set the generic_nonmember_action to Reject. - Go to the General options and scroll down to Reply-To munging. Turn on first_strip_reply_to and set reply_goes_to_list to Explicit Address. Set reply_to_address to [EMAIL PROTECTED] This way anyone following up to an announcement will send the message to your band contact address. - Scroll down on the General options and set include_list_post_header to No, but leave include_rfc2369_headers to Yes. - For those of you allowed to post to the list, turn off their moderation flag so their postings go straight through. Alternatively, you can add an Approved header to your postings. - I'd also recommend turning on personalization under the NonDigest section, and disabling digests under the Digest section, but these are optional. That's everything I can think of for a general announcement-only list. Mailman can handle these kinds of lists quite well, although as you can see, it's not completely obvious everything you need to set. That's something I'd really like to improve for future releases (probably through something like List Styles). -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Removing To post to this list . . . from confirmation e-mail
JH == John Hughes [EMAIL PROTECTED] writes: JH I'm trying to set up Mailman to use as a vehicle for JH distributing a newsletter. I don't want anyone to think they JH can post messages to the list address. JH I have figured out how to modify the HTML for the public list JH pages. How do I remove the To post to this list, send your JH email to... from the registration confirmation e-mail? See my recent (two) postings about Jim's band announcement list. These are general recommendations for any one-way (e.g. announce-only) list. I'd really appreciate it if someone could finesse those two postings into a FAQ item! -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mass Subscription - setting digest as default
T == Todd [EMAIL PROTECTED] writes: T Let me preface this by saying that I am *not* a python hacker T nor do I know Mailman all that well... but I was curious. Don't underestimate yourself! Your patch was perfect; now applied to cvs. Thanks, -Barry P.S. Give me a full name for the ACKKNOWLEDGEMENTS file. :) -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] configuring Mailman
JH == Jim Hodson [EMAIL PROTECTED] writes: JH Hello, I am working on setting up a Mailman mailing list for JH our web site at http://www.jenniferonsunday.com. We are a JH band and already have many people on an exisiting list (done JH manually), which we want to migrate to Mailman. Our site is JH hosted by Webanimotion, and they have Mailman on their server JH for us. Jim, I've been going through some back email, and I came across this message. Talk about interesting coincidences: You guys are from the DC area, and if I'm not mistaken, recently did some work at Recording Arts w/ Marco Delmar? I saw your flier on the wall there a week or so ago, if I'm not mistaken. I've worked with Marco on two projects now, one with the Nancy Dougherty Band, and another just recently with Billy Coulter. Awesome producer, and great guy. Another weird coincidence -- my main band is the Cravin' Dogs, whose last record was called Root Rock Paper Scissors. :) You're also playing many of our haunts. Dang, I see I missed your CD release party at IOTA. Great venue, huh? Hope the show went well. We should definitely hook up musically some time. Okay, back to Mailman... As to your mailing list questions, well, I run the Dog's list and Nancy's list off my own servers, on Mailman of course. So it can definitely be done. Here are some hopefully useful answers. JH We want a very simple mailing list system, and Mailman can do JH a lot more than we need. I'm trying to find out how to best JH configure Mailman for our needs. Here is what we want to do: JH 1. Send e-mail news updates to our list. We do not want users JH to be able to send to the list. Yep, that's how we do it. JH 2. Users subscribe from our JH website. Currently they enter their e-mail address on the JH site, and click Join, which sends the appropriate e-mail. Yep, although most of the joining we see is still us entering email addresses gathered from gigs. JH 3. Users UNsubscribe as well. Yep. JH The problem I've run into seems to revolve around the JH password, and the Welcome E-mail. The Welcome E-mail has a JH lot more information in it than we need. For instance, that JH e-mail tells users that they can post to the list, which I do JH not want them to be able to do. I know I can turn off the JH feature about sending them the Welcome E-mail, but then they JH won't have their password. In Mailman 2.1.x the way to customize the welcome message is to create a directory lists/yourlist/en (assuming English :) and copy templates/subscribeack.txt to this directory. Then edit the file for your specific wording. Mailman will always this specialized template for the English welcome messages. JH Also, when I migrate our current users to our Mailman list, I JH don't want them to know about the migration. However, if they JH don't get a Welcome E-mail, they also will not have a JH password, and will be unable to unsubscribe automatically. In that case, I'd turn on personalization. For the Cravin' Dogs lists, I've disabled monthly password reminders, but I've turned on personalization, so at least people get a message with their options page in every footer. It's probably still a good idea to manually run the reminders once in a while if just to help cull the dead addresses. JH Is there a way to modify the Welcome E-mail (besides just the JH introduction to it)? Is there a way to avoid having to use a JH password to unsubscribe? While not totally avoiding the use of a password, most unsubs won't need them. The easiest instructions are to send a message to yourlist[EMAIL PROTECTED], and then simply reply to the confirmation message. They never need to know their password. JH Thanks for any help you can provide. We really just want a JH simple mailing list to get information to our fans. Hope that helps, -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] bin/newlist - ImportError: No module named None
MJ == Matthias Juchem [EMAIL PROTECTED] writes: MJ MTA = 'None' Whoops! None is a special value in Python and shouldn't be quoted. Change that to MTA = None and you should be good to go. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] RELEASED Mailman 2.1.1
MD == Matthew Davis [EMAIL PROTECTED] writes: | -rw-rw-r--1 mailman2 mailman2 1281185 Feb 8 19:41 | mailman-2.1-2.1.1-diff.txt MD 1.2 meg for a patch, yikes! Looks like the majority of the MD patch is the language updates. Unfortunately so. At some point I'll get separate distros, but I haven't had time. :/ -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Normal mails changed to MIME mail
MJ == Matthias Juchem [EMAIL PROTECTED] writes: MJ So setting a list to e.g. 'German' implies ISO-8859-1? Am I MJ getting this right? Yes. MJ I thought that the language setting only affects the language MJ and not the charset... It has to because the character set used must match the characters available in the selected language. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Newbie Questions
JC == Jon Carnes [EMAIL PROTECTED] writes: JC Aside: The part that is still missing from Mailman is an SQL JC connector. Once that is in place then it will be very easy to JC add all sorts of personalization variables - allowing you to JC run mail merges that are the envy of Marketing groups the JC world-over! Something like this is definitely on my wish list -- eventually. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] bin/newlist - ImportError: No module named None
MJ == Matthias Juchem [EMAIL PROTECTED] writes: MJ When doing a bin/newlist, I get an 'ImportError: No module MJ named None'. Did you set the MTA variable in mm_cfg.py or Defaults.py? -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Error: Incorrect padding???
DG == David Gibbs [EMAIL PROTECTED] writes: DG I'm getting a huge amount of these messages ... any ideas? Not off hand, but I have an idea. Can you please submit a bug report and include one of the shunted messages? Thanks, -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] RE;Cron/senddigests bug
DP == Dan Phillips [EMAIL PROTECTED] writes: DP Tried that and it reported no problems. The problem definitely DP seems to be in digest.mbox, although I can't see anything DP wrong. If it isn't too late, can you submit a bug report with the mbox file attached? If you don't want to attach the mbox (say it has sensitive information), you can still submit the bug report and send me the mbox file. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] after 2.0.13-2.1 upgrade, files needed?
JAE == Jeff A Earickson [EMAIL PROTECTED] writes: JAE I've noticed that mailing lists that I've created after the JAE upgrade only contain config.pck, config.pck.last, and JAE request.db. Can I assume that the config.db and html files JAE are left over from 2.0.x and can now be deleted? Yes. Back 'em up first though. ;) -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Another upgrade problem (2.0.13 - 2.1); pending admin request page hosed
EO == Ed Osinski [EMAIL PROTECTED] writes: EO I upgraded from 2.0.13 to 2.1, and I run into a problem when EO trying to access the Tend to pending moderator requests page EO of a pre-existing list. I get: EO ValueError: unpack tuple of wrong size I believe I finally fixed this. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Mailman Security.
d == dino [EMAIL PROTECTED] writes: d Actually he did it this way: d Noticed that mydomain/mailman was browsable. d Telneted to port 80 and sent a get request from there...ouch. d Sorting that now More details, please. E.g. exactly what url did he get? -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman Security.
d == dino [EMAIL PROTECTED] writes: d I was just wondering what kind of security mailman offers, as d far as protecting user passwords goes? User passwords are considered a lower value asset, so while it should not be possible for unauthorized users or list admins to get them, they can still be transmitted in the clear (either via the monthly reminders -- which can be turned off, or by unprotected http login). To support the monthly reminders, user passwords are kept in the database in cleartext. Anyone with shell access and permissions to the Mailman installation can get them. d A techy friend of mine has just kindly emailed me a list of all d users and their passwords! Looking at my server logs it would d appear that he snuck in somehow via anonymous ftp. This must have been a local system vulnerability. Mailman doesn't use ftp, anonymous or otherwise. d Would closing the anon. ftp service stop mailman working in d anyway, or dya reckon he got in some place else? On your system, sure, if that's how he got in. But this isn't an attack inherent to Mailman, AFAIK. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman Security.
A == Adam [EMAIL PROTECTED] writes: A The fact that telnet is open pretty much says everything about A this sysadmin's approach to security. Actually, using the telnet /client/ to connect to port 80 is a pretty natural thing to do. It should connect to the web server running on port 80. (I don't know where ftp comes into the picture.) -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Attention Mailman Hosting Sites
A long while ago, I offered to put up a page listing sites that offered commercial Mailman list hosting services. Sadly, I don't have the time to maintain this or even put it together. However, there is a MoinMoin page (think: Wiki) listing general Python hosting services, of which Mailman is included. I encourage all Mailman hosting facilities to add entries to the page: http://www.python.org/cgi-bin/moinmoin/PythonHosting There is currently only one Mailman hosting site listed. The MoinMoin is on the honor system, and you don't need a password to add content to it. If you do add an entry, be sure to include the word Mailman so the page is easy to search. Cheers, -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman 2.1 mailpasswds error
jam == John A Martin [EMAIL PROTECTED] writes: jam ,[ Google ] | Your search - Warsaw's 4th Law - did not jam match any documents. ` jam :-) Try Warsaw's Fourth Law :) -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman 2.1 mailpasswds error
MB == Matt Brown [EMAIL PROTECTED] writes: MB With 2.1 you need to create a site-wide mailing list called MB mailman. Note BTW, that I've just modified mailmanctl to refuse to start if the site list doesn't exist. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Language setup problem
RI == Rostyk Ivantsiv [EMAIL PROTECTED] writes: RI but how can I set the whole mailman site to be in Russian, not RI just the lists??? RI P.S. I tried setting DEFAULT_SERVER_LANGUAGE = 'ru' in RI mm_cfg.py, but it just brought to server error. You did exactly the right thing. The traceback when viewing the admin overview appears to be a buglet in the Russian catalog. Seemed easy to fix so I did it (to be committed to cvs momentarily). Maybe Mikhail can double check it. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman 2.1 mailpasswds error
IVL == Ivan Van Laningham [EMAIL PROTECTED] writes: IVL Thanks! That would have saved me an hour or so of poking IVL around on Feb 1;-) I can definitely relate -- see Warsaw's 4th Law. :) -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailman 2.1: lotsa language options problems...
CVR == Chuq Von Rospach [EMAIL PROTECTED] writes: CVR it boiled down to problems with some of the language codecs, CVR the multi-byte languages. So evidently that isn't really CVR fixed on OS X, but I'll deal with that later. I bet you're still having problems building Python extension modules (i.e. C modules) on OSX. The other language related issues are real, and we're going to have to tease them out one by one. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
PyCon, Sprints, and IRC (was Re: [Mailman-Users] IRC)
JL == Jim LaSalle [EMAIL PROTECTED] writes: JL Is there an IRC for users of this mail list? irc.freenode.net #mailman But I haven't had much time to hang out there lately. :( BTW, is anybody planning on coming to PyCon? http://www.python.org/pycon/ If there is enough interest and participation, I'd be willing to chair a Mailman sprint. I can think of several topics that might be useful to sprint on: - documentation - bug fix day - improving the archiver (adding searching, or webmail) - Mailman 3.0 sprints (member mgt, backing database) - improve admindb interface I'm of course open to other suggestions. Anybody interested and planning on attending? -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] [Bug] Cookie from older version
SW == Simon White [EMAIL PROTECTED] writes: SW Kinda tough if you don't have the mailman version in the SW cookie. A good reason to put it in there, from now on, if it SW isn't there. SW Any other parameter in the cookie which has changed could be SW detected by the new version and force an expiration of the SW cookie immediately so that the problem will go away. That's not really the problem. The issue is that there are Apache rewrite rules you can use to map most of your MM2.0 lists and MM2.1 lists to the same url space. That means your browser will return both cookies in the http request because it doesn't know that they're really separate urls. You don't want to expire your MM2.0 cookies since you may still have to admin that older list. You just don't want those other cookies to cause a false error in the cookie parsing code. Try the patch; I'm pretty confident it'll work. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] FAQ entry: Who should deal with DNS errors?
ST == Samuel Tardieu [EMAIL PROTECTED] writes: ST I was going to add this FAQ entry, but I realize that I don't ST have a password to do that and I have to leave for a meeting ST right now. Folks, remember that the FAQwiz is on the honor system. Look at the front page of the FAQwiz, down at the bottom of the page. The password is right there in plain text. :) -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] footer
TN == Tom Neff [EMAIL PROTECTED] writes: TN I don't know of any way to do what you want without patching TN Mailman. You're right that there currently is no way to do this. The security implications would have to be worked out, but it might be an interesting feature -- feel free to submit a feature request. Probably, you want to allow site admins to add new substitution variables for headers and footers, and then allow your list admins to use those additional variables. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Getting mailman to use the same smtp connectionfor messages sent to the same domain
SW == Simon White [EMAIL PROTECTED] writes: SW You have a point. Mailman is injecting to the MTA so if it SW does connect/disconnect etc then this will affect even SW Postfix. So, there does need to be a way to have Mailman open SW a single connection to the server for each domain, and then do SW RCPT TO: several times. SW I *thought* that was what it did anyway... can anyone else SW prove me wrong / right? The chunking algorithm for sending messages to the mta is defined by variables such as SMTP_MAX_SESSIONS_PER_CONNECTION and SMTP_MAX_RCPTS. The latter specifies the maximum size of the RCPT TO chunks in each handoff to the mta. Set it to a negative number to not chunk at all. When chunking, Mailman first sorts by these tlds: .com, .net, .org, .edu, .us, .ca. Everything else goes into a separate bucket. Yeah, this is pretty North America-centric :/. Note that Mailman does not chunk based on MX or on 2nd level domain names. SMTP_MAX_SESSIONS_PER_CONNECTION determines how many chunks it sends down the same socket connection to the mta. Again, a negative number means blast all the chunks down the same connection. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] footer
FS == Fernando Schapachnik [EMAIL PROTECTED] writes: FS If I come up with something tidy, I like to contrib it FS back. What is the standard way to do that? Use the SourceForge patch manager: http://sourceforge.net/tracker/?group_id=103atid=300103 and if you want, add it to the Mailman wiki: http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/UnofficialMailman21Patches -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 2nd request: migrating a list from 1.1 to 2.1hosts?
Let me start off by saying that I have never personally done an upgrade from 1.1 straight to 2.1, so that all this as my best guess, not as gospel. It may in fact, be better to upgrade from 1.1 to 2.0(.13) and then from there to 2.1. That's more work of course, and it may be unnecessary work. TN == Tom Neff [EMAIL PROTECTED] writes: TN A: Clone the MM1.1 directory somewhere (on either the TN original or new host) and then upgrade that clone to 2.1. TN Copy the resulting config into the real 2.1 tree as a new TN list. (I should probably pre-create the migrated lists on the TN 2.1 host first, so I can do selective file overwrites without TN missing some of the structure. The upgraded clone directory TN can be deleted afterwards. I would do something more like A, although I wouldn't pre-create the lists. Simply copy the config to a test area, do an upgrade, then run something like bin/list_lists to touch all the lists and get them upgraded. From there it should be an easy process to move the lists to your production 2.1 site (see below). TN I hope that the developer(s) understand that with the TN continued spread of Mailman, situations were listowners need TN to *migrate*, rather than upgrading in place, will be more TN common. It would be great to have some kind of robust export TN capability that was more or less version independent. This totally doable, as covered in the UPGRADING INDIVIDUAL LISTS section in the UPGRADING file. It's actually fairly simple if you discount the mta and Apache cruft. HTH, -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Where is HandlerAPI?
AEW == Albert E Whale [EMAIL PROTECTED] writes: AEW I am having problems getting Mailman 2.1 installed on LM 8.2 AEW using the Stock Python distributions. Here is the Error I am AEW encountering: AEW ImportError: No module named pythonlib.StringIO AEW Does this follow with the missing Python 2.2 Development RPM AEW (Note that LM 8.2 does not have a Python-development rpm). AEW Do these errors shed any additional light on the matter? You're mixing your MM2.0 and MM2.1 installations. There's no HandlerAPI.py in Mailman 2.1, nor is there a StringIO.py in pythonlib, nor is qrunner invoked from cron any more. Did you update your crontab? -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Getting mailman to use the same smtp connectionfor messages sent to the same domain
SW == Simon White [EMAIL PROTECTED] writes: SW Chunking like this means that you're actually sending RCPT TO: SW based on TLD, and then only US TLDs, right? So SMTP_MAX_RCPTS SW set to 50 could mean several different second level domains in SW the same chunk, but for every TLD outside the US there will be SW separate sessions for each mail sent? Not exactly. All the other tlds get dropped in the same bucket and the chunks are filled from the buckets. There are at most 4 buckets: 0 == everything else 1 == .com 2 == .org .net 3 == .edu .us .ca SW Not exactly easy in real code, but if what you say about the SW algorithm is true, then I could seriously improve performance SW for my lists by doing this. Right now, my MTA takes over 3 SW hours to deliver the bulk of my 12000 subscriber list (not SW including bounces and poor receiving MX hosts). I'm highly doubtful that the chunking algorithm is your problem. More likely its an mta issue. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] HTML interface to set DEFAULT_URL
MP == Marc Perkel [EMAIL PROTECTED] writes: MP In Mailman 2.0 there was a setting for the default URL. I MP can't seem to find it in 2.1. It was too dangerous to leave in the web interface. MP I need to change the default URL for all my lists. Any easy MP way to do this? bin/fix_url.py and/or bin/withlist -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] [Bug] Cookie from older version
WY == Will Yardley [EMAIL PROTECTED] writes: WY If you have an old cookie from Mailman 2.0.x, you'll have to WY re-login for every page until you manually clear the cookie WY from your browser (after upgrading to 2.1). WY Is there any way to fix this in the future? With some WY browsers, it's not simple to remove an individual cookie. This isn't a browser bug, it's a misfeature of Python's Cookie.py module, which Mailman uses. There /will/ be a fix in Mailman 2.1.1 but I haven't worked the patch out yet. -Bary -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Re: Bundling HTDIG
bob == [EMAIL PROTECTED] writes: bob While I can understand why one might not want to bundle HTDIG bob with Mailman, I do think it is entirely appropriate to bob integrade the HTDIG patches into Mailman, making the adding bob of HTDIG much easier. Especially since the patch author has bob made the patch such that the default usage does not affect bob normal Pipermail operation (if HT:Dig is not installed/used). +1 (eventually). bob P.S. The subject index in the digest are wrapping in a very bob odd way. For example, the first line shows: Fixed in CVS I believe. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] MS Exchange as a relay computer?
RH == Ralf Hildebrandt [EMAIL PROTECTED] writes: RH * alex wetmore [EMAIL PROTECTED]: The Mailman FAQ still recommends setting MAX_SMTP_RCPTS to 10 for performance reasons, but doesn't explain why. RH This should definitely go! That's in the FAQwiz, right? Feel free to update that (it's on the honor system). -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] MS Exchange as a relay computer?
RH == Ralf Hildebrandt [EMAIL PROTECTED] writes: RH Excellent. I got no password :( Go to http://www.python.org/cgi-bin/faqw-mm.py and look at the bottom of the page. :) -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] How to delete messages from private archives
JP == Jim Popovitch [EMAIL PROTECTED] writes: JP I too use HTDig, but this doesn't really help with external JP search engines or deep-linkers. The best solution, is JP MHonarc, but I keep holding out for Pipermail to catchup. ;) Wanna help? :) I keep looking for motivated hackers to help work on Pipermail. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] X-Loop
GH == Gareth Hopkins [EMAIL PROTECTED] writes: GH So is there anywhere I can add this then in mailman or change GH the X-Beenthere settings? I still don't quite understand what you're trying to accomplish. I wouldn't recommend changing the X-BeenThere header -- this is an internal header that Mailman uses to prevent loops. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: Using mailman without passwords WAS Re: [Mailman-Users] Mailman
MD == Matthew Davis [EMAIL PROTECTED] writes: MD Now my 2 disclaimers. 1. Do with this information as you see MD fit, its not the recommended way to setup a list. 2. Take it MD for what its worth, it was free. Actually, it's a fine way to run your lists, because your members still have to perform the opt-in-with-confirmation step, but they don't need to remember their passwords to either subscribe or unsubscribe. Yes, they'll need them to change their options, but most users will rarely need to do that, and in 2.1, they can simply log into their options page and get a password reminder when they need it (you could disable montly passwords for the list). -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] can't access private archives when changingdefault lang
TA == The Anarcat [EMAIL PROTECTED] writes: TA Many thanks! TA That is great.. Pointers for a patch? http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/templates/fr/private.html.diff?r1=texttr1=2.3r2=texttr2=2.2diff_format=h Cheers, -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] How to delete messages from private archives
JP == Jim Popovitch [EMAIL PROTECTED] writes: JP Actually my suggestion would be to remove Pipermail (and not JP insert MHonarc, Hypermail, etc.) MM doesn't include a search JP engine, why a mail archive? IMHO MM should focus on what it JP already does very very well. Pipermail isn't horrible any more, and I don't think it would be /that/ much work to implement a simple search engine. Simplicity is the key here -- I'd love a basically functional search feature that works out of the box. It needs to be modular so that more advanced sites can swap in a different search engine (e.g. htdig), just like they now can do with the archiver. I don't think we buy much by /removing/ functionality. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: Bundle Htdig with Pipermail? -was- How to delete messages fromprivate archives
JC == Jon Carnes [EMAIL PROTECTED] writes: JC Is there a reason you wouldn't want to simply include Htdig as JC part of the out of the box install? If we bundle it with Mailman, we're making a commitment to maintain it. JC Are you thinking that we can port ht://dig over to Python and JC then improve it performance? :-) Sure, I can't wait wink. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Bundle Htdig with Pipermail? -was- How to deletemessages from private archives
MD == Matthew Davis [EMAIL PROTECTED] writes: MD -rw-rw-r-- 1 mailman2 mailman2 5466939 Dec 30 23:55 MD mailman-2.1.tgz Eventually, I want to split Mailman into a sumo distro and a lite distro, where the latter includes just the English distro. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] X-Loop
GH == Gareth Hopkins [EMAIL PROTECTED] writes: GH So is there anywhere I can add this then in mailman or change GH the X-Beenthere settings? I'm not sure what you're trying to accomplish, but sure you can add it to Mailman. Pick a module in Mailman/Handlers, or make up your own that just adds the header with whatever value you think will help you accomplish your goal wink. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Re: Problems with content filtering
DG == David Gibbs [EMAIL PROTECTED] writes: DG To fix the problem, we have to change the temporary directory DG that lynx uses. DG Change the HTML_TO_PLAIN_TEXT_COMMAND to the following ... | HTML_TO_PLAIN_TEXT_COMMAND = 'export LYNX_TEMP_SPACE=/tmp | /usr/bin/lynx -force_html -dump %(filename)s' DG This causes the temporary directory that lynx will use to be DG /tmp (which, btw, is the default for a freshly built lynx). DG Now, this works fine ... I just tested it and got fine DG results... HOWEVER, I really don't like the way lynx formats DG the dumped html file... it's got extra spaces between each DG line. Don't know why. DG I'm going to stick with links for now. :) This would make a nice FAQwiz entry! -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] List, user, and site passwords
PK == Paul Kleeberg [EMAIL PROTECTED] writes: PK Are all the passwords used by mailman encrypted? I am PK migrating from Listproc where user and list passwords appear PK in plain text so that the list and site managers could read PK them. I thought that was bad and would warn my users not to PK use passwords that would cause problems if disclosed. User passwords are kept in plaintext, otherwise we couldn't do password reminders (some would say that'd be a good thing :). List and site admin passwords are kept sha1 hashed (in MM2.1). -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Confirmation + Moderation
ST == Samuel Tardieu [EMAIL PROTECTED] writes: ST I host several mailing lists with both mailman and sympa, and ST I miss a feature in mailman that I implemented in sympa using ST their scenarii model: when a mail arrives on a list from a ST non-subscriber or with the list address absent (even if it ST comes from a subscriber), then a confirmation request is sent ST to the (alleged) sender. If the sender confirms that she wants ST the mail delivered, then the mail is systematically held for ST moderation. If it is not confirmed, the moderators don't see ST the mail at all. ST With those settings, I had to discard only one spam (that the ST sender confirmed) manually in months on a moderately busy ST mailing-list (ten posts a day), without even using any spam ST filter in front of the list. ST Any idea on how to do that with mailman? It wouldn't be hard to add, actually. Please add this to the feature request tracker on SourceForge. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] X-Loop
GH == Gareth Hopkins [EMAIL PROTECTED] writes: GH I have just upgraded to version 2.1. Apparently in GH this version I can add an X-loop header. Where abouts do I do GH this? Huh? What's an X-loop header? Mailman doesn't use or add this header. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] upgrade from 2.1beta3 to 2.1 final
MS == Marius Scurtescu [EMAIL PROTECTED] writes: MS I am running Maiman 2.1 beta 3 and I would like to MS upgrade to the final release. MS Could someone point me to the proper documentation or MS just quickly tell me what I need to do? MS Any information is more than welcome. That's an easy upgrade. Just stop mailmanctl, then configure and make install right over 2.1b3. Then start mailmanctl again and you should be good to go. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Personalization
RBP == Richard B Pyne [EMAIL PROTECTED] writes: RBP I found the mention of VERP_PASSWORD_REMINDERS, RBP VERP_PERSONALIZED_DELIVERIES, VERP_DELIVERY_INTERVAL, and RBP VERP_CONFIRMATIONS in the FAQ and added them to my mm_cfg.py RBP file, but I still see no difference in the footers or To: RBP header of the emails or in the options in the admin RBP interface. You have to add this to Non-Digest - msg_footers. See the personalize option for detailed description. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] X-Loop
CVR == Chuq Von Rospach [EMAIL PROTECTED] writes: Huh? What's an X-loop header? Mailman doesn't use or add this header. CVR It's a procmail convention, so that procmail recipes can tell CVR they've already seen a message and break a potential mail CVR loop. Ah, like Mailman's X-BeenThere header. Thanks for the info. -B -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] RE: Machine in unresponsive
jsingh == [EMAIL PROTECTED] writes: jsingh Why is qrunner sending mail to the mailman user every jsingh minute. That means with the cron job it is creating an jsingh email for the mailman user. It is because of the jsingh deprication issue. Be sure you're using the latest versions of Mailman, either 2.0.13 or 2.1.0. Both should be immune to deprecation warnings in any released version of Python (and even Python 2.3 alpha, but that isn't tested as thoroughly). -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Help with sending HTML mail and using externalweblinks for images
MC == Mark C [EMAIL PROTECTED] writes: Yes. Marketing folks do it all the time. If you want a live example of an email that does this, just open up some spam from your mailbox and peruse the source/content of the email. MC But this does sound silly, how would I put that link into the MC html? As I presuem the only way to get Mailman to send the MC html format mail, would be to copose it in youre email client, MC and if I referance a http address, it will diplay that rather MC than an image? This isn't really a Mailman issue, other than to configure the list to pass the MIME content you want to pass through. I'm sure there's some MIME goo you can add to your attachments to get (some) mail readers to display the image inline, but off-hand I don't remember what they are and I don't have access to the RFCs at the moment. I'm guessing some kind of multipart/related with a Content-Disposition: inline thingie. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] implicit addressing
SB == Sarah Baker [EMAIL PROTECTED] writes: SB How can I get the mailman mailing list to accept SB the other mailing list name as acceptible SB for the list in the To: or cc: (ie not requiring explicit SB administrative approval)? In Mailman 2.1: Privacy - Recipient Filters - acceptable_aliases -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Re: Odd error in smtp-failure log
DG == David Gibbs [EMAIL PROTECTED] writes: DG Ordinarily I would agree with you ... but this came from DG mailman's smtp mailer, not my sendmail. Mailman uses your local smtpd to do the sending so it /is/ coming from your sendmail. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Upgrade problems (2.0.13 - 2.1);Incoming qrunner dies
EO == Ed Osinski [EMAIL PROTECTED] writes: EO I've upgraded from 2.0.13 to 2.1, and am having problems: EO When running bin/mailmanctl start, I get a series of errors: EO EOFError : EOF read where object expected EO This is repeated 11 times. When I run ps to look for qrunner EO processes, I find: If you still have the offending .db file, please try bin/dumpdb on it and see what you get. You'll probably get the EOF error. If so, send it to me. Also, what version of Python are you using? -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] qrunner troubles after install: Uncaught runner exception
ANV == A N Varady [EMAIL PROTECTED] writes: ANV ./configure --with-cgi-gid=99 --with-mail-gid=mailman ANV --prefix=/home/mailman --with-python=/usr/local/bin/python2.2 ANV TypeError: isinstance() arg 2 must be a class or type Be sure that the python2.2 above points to Python 2.2.2. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members UPDATE
Steve, You're first problem looks like a classic permission denied problem. I'd suggest running bin/check_perms to see if that clears up your problems. The second issue you had (no module name time) looks like your Python installation is broken. You should be able to do something like the following at the command line: % python Python 2.2.2 (#1, Oct 14 2002, 19:51:36) [GCC 2.96 2731 (Red Hat Linux 7.3 2.96-112)] on linux2 Type help, copyright, credits or license for more information. import time time.__file__ '/usr/local/lib/python2.2/lib-dynload/time.so' If not, go back to your Python source dir, and run make test. Check your compilation output carefully. Mailman 2.1 should work with Python 2.1.3 or later. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailinglists for multiple domains on one server
RBP == Richard B Pyne [EMAIL PROTECTED] writes: RBP However, the create cgi will not permit including the RBP @dom.ain in the list name and therefore defaults to the RBP default domain (which mailman appears to allow only to be the RBP domain listed in the PTR dns record for the IP address of the RBP machine). Not true. New lists will inherit the domain that you used to visit the create cgi. E.g. If I go to http://mail.python.org/mailman/create to create my new list, it'll show up in the python.org domain. If instead I use http://lists.zope.org/mailman/create, it'll show up in the zope.org domain. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] user feedback on plain digests
BF == Bryan Fullerton [EMAIL PROTECTED] writes: BF When I get a chance later today I'll be trying the patch Tokio BF Kikuchi sent to mailman-developers - hopefully it will resolve BF the excess headers issue. I'm off the net at the moment so I can't look at the patch, but I can guess what it does. If I'm right wink will it bother folks that reducing the number of headers in the plain text digest will also reduce the number of headers in the MIME digest? One of my goals for the digester was that either digest could be burst and the individual messages would look exactly as if they had arrived independently. Or at least, they'd be useable to do follow ups back to the list. Maybe that's unreasonable for plain text digests. If so, the current code may need a more invasive surgery. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Can users request old digests?
EL == Ed Leafe [EMAIL PROTECTED] writes: EL I recently received a request from a user who receives and EL archives the digest version of the list, and due to ISP EL problems he recently missed a few issues. He has used lists EL where you can send email to the list requesting specific EL digest back issues; is such a capability part of Mailman? No, but it's a good idea. Please submit a feature request. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Sub-lists and authorized posting
NN == Nathan Neulinger Neulinger writes: NN I managed to make a patch to do this based on the NN list_exploder patch that is in the sourceforge patches area NN for 2.0. NN I've got a patch against 2.1 if anyone is NN interested. Basically lets you put: NN +list@thisdomain NN in the *_these_nonmembers boxes, and it will expand that to NN the contents of that list when checking for authorization to NN post/etc. Please submit a SF patch for this. It sounds like a useful patch! Maybe it'll make it into MM2.2. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] BCC allowed?
CH == Carl Holtje [EMAIL PROTECTED] writes: CH While the power of denying a list to be specified in a BCC CH field is certainly undeniable, I'd like the ability to accept CH a post that has the list BCCd if the sender is a list member CH -- is this possible? For MM2.1, look under Privacy - Recipient filters. You might want to edit either require_explicit_destination or acceptable_aliases. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailpasswds
sp == sean pambianco [EMAIL PROTECTED] writes: sp Is there anyway to run the mailpasswds cron jobs for just one sp list as opposed for all lists on my mailman server? cron/mailpasswds -l onelist See -h for details. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] misfeature/bug in MM 2.1
JAE == Jeff A Earickson [EMAIL PROTECTED] writes: JAE In my study of my mailing lists today (both new in MM 2.1, JAE and upgraded from 2.0.13), I made the sad discovery that JAE generic_nonmember_action = 0 JAE for **all** of my lists. The bend over and take spam JAE setting. I noticed that DEFAULT_GENERIC_NONMEMBER_ACTION is JAE set to one in Mailman/Defaults.py, but I don't think this JAE setting works properly. If it did work properly, I would JAE argue that the default should be 2 (reject), not 1 (hold for JAE administrator). Why should the list administrator be JAE bothered with having to tend admin requests from spammers and JAE other idiots? Mailman isn't an anti-spam program, although it has some modest anti-spam defenses. Since there are lots of anti-spam programs out there, it should be pretty easy to install a good anti-spam program upstream of Mailman. I just gave a talk at the MIT spam conference about our approach and will be putting our slides up on the web somewhere soon (probably on spamconference.org -- not sure yet). BTW, on the train to said conference, I got working a prototype integration of Mailman and spambayes, and I'll probably be checking this into cvs when I get back wink. I'd label it as an interesting experiment, but whether it'll be useful remains to be seen. I doubt it will eliminate the need for other upstream spam catching tools. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: [Mailman-Developers] spam filter
KW == Kory Wheatley [EMAIL PROTECTED] writes: KW I would like to discard any email that comes from the from KW address [EMAIL PROTECTED]. In MM2.1, this is easy. Add [EMAIL PROTECTED] to your Privacy-Sender filters-discard_these_nonmembers. In MM2.0 the best you can do is catch From: [EMAIL PROTECTED] and manually discard them. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] What's wrong with the mailman-users archive?
We had some problems with mail delivery on python.org/zope.org. We now believe it was a SpamAssassin process that was hanging Exim delivery. We've got a stop gap measure in place which is getting mail flowing again. Looks like the hosage affected the archives. I'll attempt to rebuild them. -Barry -- 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/
Re: [Mailman-Users] mm2.1 cookie problem?
BF == Bryan Fullerton [EMAIL PROTECTED] writes:
I had the same problem initially. I manually deleted all the
old cookies set by mailman and it worked fine. Deleting just
the cookie from that list didn't help.
BF Unfortunately, in this case both of the lists are active, so
BF they're setting cookies all the time. Telling my list-owner
BF that he has to delete all his cookies for his other 10 mm2.0
BF lists on my server every time he wants to admin his mm2.1 list
BF isn't really a good solution IMHO. :/
BTW, for the hacker inclined, an possibly useful way to debug this is
to edit SecurityManager.py, the __checkone() method. Stick something
like this before the first try: line (untested):
syslog('debug', 'key: %s, c[key]: %s, val: %s', key, c[key], c[key].value)
then tail logs/debug until you see the problem. Maybe something
interesting will show up.
-Barry
--
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: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members UPDATE
SR == Steve Rifkin [EMAIL PROTECTED] writes: SR OK, I upgraded to MM2.1. After having to run check_perms with SR -f to fix permissions, I finally got the web pages up. SR When I go in as site admin and change the list admin's SR password for a list, I *still* cannot log in as the list SR admin. (I still receive the authentication error). SR And if I go back into the password change page for the list as SR the site admin, and if I put in a new list admin password and SR have a *different* verified password, I receive no errors when SR I click submit. SR However, if I run change_pw from the command line, changing SR the password for the list admin for the specific list, them, I SR CAN log in! :) SR So, it's the web interface that's screwing up. We're SR narrowing this one down now... I hope! Any suggestions? Do you have any cookie blockers or other proxies between your browser and the web server? That's about the only thing I can think of. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] MM 2.1 -- another qrunner crash
DG == David Gibbs [EMAIL PROTECTED] writes:
DG Any thoughts on this?
| IOError: [Errno 4] Interrupted system call
Just that something's wrong with your mail server, or the connection
between it and Mailman, or something sent the qrunner process a signal
while it was in the middle of talking to your mail server.
Try this patch; it won't avoid the interrupted system call, but it
ought to handle the situation more gracefully (assuming it's a
transient problem).
Untested, but let me know if it works for you.
-Barry
snip snip
Index: SMTPDirect.py
===
RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/SMTPDirect.py,v
retrieving revision 2.25
diff -u -r2.25 SMTPDirect.py
--- SMTPDirect.py 6 Nov 2002 04:43:54 - 2.25
+++ SMTPDirect.py 7 Jan 2003 05:35:24 -
@@ -337,7 +337,7 @@
refused = e.recipients
# MTA not responding, or other socket problems, or any other kind of
# SMTPException. In that case, nothing got delivered
-except (socket.error, smtplib.SMTPException), e:
+except (socket.error, smtplib.SMTPException, IOError), e:
# BAW: should this be configurable?
syslog('smtp', 'All recipients refused: %s', e)
# If the exception had an associated error code, use it, otherwise,
--
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: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] problems with different chatsets (footer getsattached if different)
ST == Sebastian Talmon [EMAIL PROTECTED] writes: ST I'm sorry, but with this path the headers are set correct, but ST MS Outlook still shows the footer as a pseudo-Attachement ST (giving it the name ATT00010.txt or so) Sigh. -Barry -- 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/
[Mailman-Users] Re: [Mailman-Developers] Qmail Doc patch for 2.1
EL This is a documentation patch for the README.QMAIL file. EL There's not much testing here, but Barry would you consider EL applying it? Sure, if other qmailers like it. Can you upload it as a patch to SF? Thanks, -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] MM2.1 Footer user variable.
MD == Matthew Davis [EMAIL PROTECTED] writes: MD From the 'verify.txt' it looks like %(email) will work. verify.txt doesn't enter into it. Go to Non-Digest Options - personalize and read the details. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] MM2.1 Footer user variable.
JS == John Swartzentruber [EMAIL PROTECTED] writes: JS On Wed, 8 Jan 2003 07:59:01 -0500, Barry A. Warsaw wrote: Go to Non-Digest Options - personalize and read the details. JS It would be helpful if these personalized footer fields were JS also listed in the Details for msg_footer. Or at least a JS mention that they are listed in the Details for personalize. I agree, it's hard to find. Please submit a bug report on this. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mm2.1 cookie problem?
BF == Bryan Fullerton [EMAIL PROTECTED] writes: BF Yup, I have no doubt that it's because I'm mixing 2.0 and BF 2.1. And yup, I've been upgrading individual lists as per the BF UPGRADING instructions. Here's the rewrite rule I used for the BF 2.1 list: | RewriteRule ^/mailman/(.*)/(trawler-world-list-help.*) \ | /home/mailman-2.1/cgi-bin/$1/$2 \ | [T=application/x-httpd-cgi] Very interesting. I wonder if this could be some Apache bug or other? We're running 1.3.27 on python.org so I don't have direct experience with this bug on Apache 2.0 BF It's only been a problem so far with this one set of lists, BF where the list names are all very similar (and also rather BF long). And the 2.0 lists are fine, it's only been affecting BF the one I moved to 2.1. (I did move about a dozen other lists, BF which are all working perfectly, but they have no sibling BF lists with similar names still in 2.0) That's an interesting clue! BF Did something change with the cookie handling between 2.0 and BF 2.1? (besides yes, everything :). Other than everything, no nothing. :) BF I note that the list/login delimiter in the cookie name is now BF + instead of : - is that somehow throwing off the new parser? BF I briefly looked at SecurityManager.py and Cgi/admin.py, but I BF haven't yet been able to figure out if the cookie parsing BF stuff is entirely Mailman code, or if it's using cookie stuff BF from Python too (though my Python version is the same for both BF - hrm). The colons did cause problems with Python's Cookie.py, as that module stood back in Oct 2001. I think the change was made when we zapped Mailman's own copy of Cookie.py for the one in Python's standard library. Sure, there could be a bug there, although I haven't seen any other reports of problems. Mailman crafts the key used to look up the cookie data (essentially a dictionary), by using the list's internal name, `+', and an authcontext, which for the admin screens is `admin'. BF I suspect that my list-owner using IE on WinME didn't really BF need to reboot LOL! BF - I'll get him to try deleting the cookie BF manually for his 2.0 list and see if that helps. Okay. Also, what version of Python are you using? I've seen the problem with Python 2.1.3, but I don't recall seeing it since I've upgraded python.org's Mailman 2.1 to run on Python 2.2.2. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mm2.1 cookie problem?
BF == Bryan Fullerton [EMAIL PROTECTED] writes: BF Is there any limit to the length of the list-name variables or BF the comparisons? None except limits on directory names in your OS's file system. I doubt you're even close. :) BF Is there any other way a cookie request for BF trawler-world-list-help would return the cookie for BF trawler-world-list? Not that I can think of. BF Is -help a 'reserved' extension like BF -request or -admin? Nope. BF I'm using Python 2.2.2, compiled from the FreeBSD port (port BF version python-2.2.2_2, installed December 1st). I'm still putting my money on Apache. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] problems with different chatsets (footer getsattached if different)
BG == Ben Gertzfield [EMAIL PROTECTED] writes: BG I haven't tested this at all, but this patch to BG Mailman/Handlers/Decorate.py to add Content-Disposition: BG inline to any MIME'd headers and footers may make MS Outlook BG show the footer in the message. Can you test it and see if BG this fixes the problem? At worst, I can't see how this would hurt, so I think I'll add it anyway. (But please do let us know if this helps.) Thanks! -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Login Persistence and Cookies
PAR == Paul Allen Rice [EMAIL PROTECTED] writes: PAR I've noticed that when I log out of the admin page for one PAR list, go to another and login there, then come back to the PAR first list, all without shutting down my browser, Mailman PAR allows me back into the first list admin area without PAR requesting a login. I cannot reproduce this with NS, Moz, or Konq on Linux. I don't have OSX booted at the moment, but I don't recall ever seeing any such problems with NS, Moz, Chimera, or IE on OSX (haven't tried Safari yet :). PAR There's obviously some sort of persistence thing going on PAR here, since we all have cookies enabled, but some cookies go PAR stale quicker than others. Mailman's admin cookies are session cookies. They go away when you quit your browser. PAR Does anyone have a definitive answer for this, other than to PAR tell me to turn my cookies on, because they already are. Is PAR there some sort of setting that can be tweaked in PAR Mailman/Python to adjust the lifespan of the cookies it PAR creates? No, but you could try playing with MakeCookie() in SecurityManager.py. The only cookie problems I've seen so far, and that have been confirmed, are those related to the Apache rewrite rules given in UPGRADING. Folks use these to migrate lists one at a time. I'm still not sure why this is, but I strongly suspect an Apache problem or misconfiguration. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Changing URL
RSR == Roy S Rapoport [EMAIL PROTECTED] writes: Did you run the fix_url.py script? RSR Nope. Didn't see that mentioned in the directions. It's buried in the UPGRADING INDIVIDUAL LISTS section of the UPGRADING file. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mm2.1 cookie problem?
BF == Bryan Fullerton [EMAIL PROTECTED] writes: BF If python's Cookie code (or at least SimpleCookie) doesn't BF like cookies with :'s in them that'd explain it. Great sleuthing, Bryan! I don't have time tonight to work out a fix, but this is an excellent clue, and I'm hopeful there's a workaround. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] problems with different chatsets (footer getsattached if different)
BG == Ben Gertzfield [EMAIL PROTECTED] writes: BG It's theoretically possible to search through the whole BG header/footer of each list to see if it is completely BG us-ascii, but this seems like a hack to me. Unless we do BG that, we have to assume that the footer is in the list charset BG (iso-8859-1) which means that us-ascii messages will get the BG footer attached as a MIME part. I can envision something in Mailman 3 where you'd be able to create headers and footers for different languages and/or charsets, or at least be able to specify the language and/or charset of the header and footer. ST == Sebastian Talmon [EMAIL PROTECTED] writes: ST I see, internationalisation is not such an easy thing... *g* It's early yet, but I've nominated you for the Understatement of the Year award. :) BG This is a possibility, but I'm a little scared of changing BG something so major as the Content-Type of the whole message BG just to avoid using separate MIME parts for the body and BG footer. Me too. I really don't want to do that. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mm2.1 cookie problem?
BF == Bryan Fullerton [EMAIL PROTECTED] writes: BF From time to time (ah, the best kind of bug), the cookie set BF when logging into a list seems to go bad - after BF authenticating, any other admin operation (admin pages, BF admindb, list archives) results in prompting again for the BF password every time a link is clicked or a form submitted. I've only ever seen this with lists on python.org that we upgraded from MM2.0 according to the instructions in the UPGRADING file (see UPGRADING INDIVIDUAL LISTS). I've never seen this for brand new MM2.1 lists. I've suspect it's some wacky interaction with Apache so I've tended to ignore it, so I'd like to know if the lists you're having problems with are using these rewrite rules. Indeed since Mailman's cookies are session cookies, restarting your browser should take care of the problem. I've also had success doing a Logout (with a couple of authentications :/ ) followed by using Mozilla's cookie manager to manually delete the cookies. Doing just one or the other never seemed to do the trick. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 2.1 Install Issues
DL == David LeVine [EMAIL PROTECTED] writes: DL I think the Solaris make does support wildcarding, perhaps DL with slightly different syntax...:^) Maybe you can help figure out the right syntax for Solaris make? -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] VERP_CONFIRMATIONS in 2.1?
DG == David Gibbs [EMAIL PROTECTED] writes: DG Anyone know if VERP_CONFIRMATIONS ever got expanded to support DG more than just invitation confirmations? Nope. And with the vacation program issue we'll have to discuss whether it's generally a good idea or not. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Converting 2.0 to 2.1
KR == Kyle Rhorer [EMAIL PROTECTED] writes:
KR This might be a good opportunity to remind folks that prudent
KR system administration practice dictates one make not only
KR frequent, scheduled backups, but also a one-off backup before
KR upgrading software. I'm sure we all know that already, but
KR it's easy to become complacent.
Good reminder Kyle.
BTW, for those of you upgrading a list at a time, what I do first is
create a tarball in 2.0.13 before moving the directories over to 2.1.
E.g.
% cd /usr/local/mailman20
% tar zcvf SAFETIES/mylist.tgz lists/mylist archives/private/mylist{.mbox,}
-Barry
--
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: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Question about fixing an install..
GS == Glenn Sieb [EMAIL PROTECTED] writes: GS I am still running 2.1b5, and would like to upgrade to GS 2.1RC1... but I'd like to resolve this one eetsy problem. GS I had failed to create the mailman list as the first list in GS my install. I have since done so--but I still get the cron GS error: GS Site list is missing: mailman It would be worth investigating why you still get this. You shouldn't! You cd to /usr/local/mailman and type bin/list_lists. Does the mailman list show up there? It should. GS So I figure, hey.. I want to upgrade to RC1... is there a way GS I can make this a smooth transition and fix this error? Can I GS back up my old lists, then back up my mailman directory, GS install the new version, create the mailman list, and finally GS import all the settings and such into the new install? Will GS this cause any of my list owners grief? The databases for 2.1b5, 2.1rc1, and 2.1final are completely identical so your files should work just fine in any of those versions, although of course I'll recommend moving to 2.1 final instead of messing with betas or release candidates. I don't think any of those will have any effect on your site-list problem. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] upgrade: 2.0.13 to 2.1, searchable archives?
JAE == Jeff A Earickson [EMAIL PROTECTED] writes: JAE I successfully upgraded from 2.0.13 to 2.1 today, with JAE minimal fuss and pain. Some comments: JAE a) I can no longer get sync_members to work. It always gives JAE the following error: Yep, known bug. I posted a patch for this a few days ago. Alternatively, you can grab the whole file from: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/bin/sync_members?rev=HEADcontent-type=text/vnd.viewcvs-markup Drop this in your source directory, run config.status, and re-install. JAE b) The ability to turn off RFC2369 mail headers on a per-list JAE basis is a huge win for me, for a few cranky list-owners that JAE hated seeing the list management stuff in Eudora. Thank you, JAE thank you. You're welcome! JAE c) The ability to turn off subscribe/unsubscribe passwords JAE and/or list-owner confirmation on a per-list basis would also JAE be a help. After converting from majordomo to Mailman, some JAE of my old list-owners hate the password thing, and so are JAE less than happy with Mailman (I am however). You know that you don't really /need/ the passwords much for subscribes and unsubscribes. Mailman will use mailback confirmations for these actions if no password is given. If users never want to modify their options, they don't need to know their password. I'm not sure what list-owner confirmation means. Do you mean the Approve option under the Privacy category for subscribe_policy? JAE Question: How to I get searchable archives? Like JAE http://www.mail-archive.com/mailman-users%40python.org/ JAE for my own mailing-list archives? You can try the htdig patches on SourceForge. This is not officially supported right now. JAE How come this doesn't come as a part of Mailman? I'd prefer a Pythonic solution integrated with Pipermail. Lacking that, eventually some kind of third party hook for external indexers will likely become official. I don't have any plans to distribute or bundle something like htdig. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 2.1 Install Issues
DL On most directories, each file to be installed is enumerated DL and installed within a loop, however, for the icons directory, DL the Makefile seems to rely on wildcard matching. That may not DL be a valid assumption. Could be a GNU Make-ism. Maybe Solaris's make doesn't do wildcarding? (It's been too long since I've been on Solaris and I'm too tired right now to look it up. ;). DL On the line that installs the template subdirectories, the DL 'install-sh -c' line has '-m 644 instead of '-m 664', so that DL may also be a Makefile issue. That's correct for the files inside the template subdirs. DL As for the messages subdirectories, those appear to be created DL with simple calls to mkdir rather than install and they don't DL appear to have permissions being set at all. Actually, both should be created by the mkinstalldirs script in the top level source directory. I'll have to try to find some time to build Mailman on the Solaris box in the SF compile farm. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Race condition with summary moderation screen?
DS == David Shaw [EMAIL PROTECTED] writes: DS I just upgraded to 2.1 and noticed an interesting race DS condition with the summary version of the moderation page. DS Take this timeline: DS 1) [EMAIL PROTECTED] sends 3 messages to the list 2) moderator DS visits summary moderation page and sees the 3 messages 3) DS [EMAIL PROTECTED] sends another message to the list 4) DS moderator clicks discard and submits DS The end result is that Mailman discards 4 messages, including DS the latest one that the moderator did not get to see. DS This does not happen with the old-style details version of DS the moderation page. Please submit a SourceForge bug report so this one doesn't get lost. I haven't verified it, but it seems reasonable. I don't have a fix readily available, but if you submit the bug report, I'll fix this one for 2.1.1. Thanks, -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] problems with MM 2.1
l == ljacobs [EMAIL PROTECTED] writes: l I had been running MM 2.0.13 for some time now. I upgraded to l 2.1 on my test system, RH 8 running Postfix 2 and had no l problems. SO I upgraded my production system, RH 7.1 with l Postfix 1.1.11 and am now unable to send messages to the lists. l I have tried running configure with -prefixes that I thought l made sense, and have included the most recent config right l here: ./configure --with-python=/usr/local/bin/python l --exec-prefix=/usr/local/bin/ --with-cgi-gid=apache l --prefix=/home/mailman --with-mail-gid=postfix You probably don't want to have a separate --prefix and --exec-prefix. That just makes your life more complicated and should only be used in special circumstances (if you don't know what those are, you probably don't need it. ;). Try building w/o the --exec-prefix option. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members UPDATE
The ownership issue is a red-herring. As long as it's group owned by
mailman and it's g+rw you should be fine.
I'm guessing somewhere along the way Python got upgraded and the
status of the crypt libraries changed (either they were there before
and not now, or vice versa). Try setting USE_CRYPT=0 in your
mm_cfg.py file.
A better solution would be to upgrade to MM2.1. It uses sha1 hashing,
which will always be available.
BTW, a debugging tool I use quite often (or the Python literate here),
is to sprinkle the code with lines like:
syslog('debug', 'some value: %s', somevalue)
which puts the output in errors/debug. You may need to add
from Mailman.Logging.Syslog import syslog
at the top of the file, if it isn't already there.
-Barry
--
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: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] No module named korean
chaim == [EMAIL PROTECTED] writes: chaim Thank you for your help so far on this issue. Have you chaim found anything new since your last email? This was resolved in 2.1 final. You must have the python -devel package installed, but the test for this was broken in the pre-2.1 final configure script. -Barry -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
