[Mailman-Users] Ownership problems in admindb.py
Hi, I have setup Mailman and have the following problems with it: I have a list called priv where only memebers are allowed to post. When a non-member posts to the list, it goes for admin approval. The administratior rejects the posting thru web interface. At this point the ownership of /var/lists/priv/configdb and /var/lists/priv/configdb.last changes. It changes from uid=mailman, gid=nofiles to uid=nobody, gid=nofiles. Also, the permission of the files become -rw-rw This happens because apache is running with uid=nobody and gid=nofiles. I have configured mailman with uid=mailman and gid=nofiles. The refusal intimation from the admin never goes ou to the poster because the qrunner runs with uid=mailman and gid=nofiles and it has no read access to the files /var/lists/priv/configdb*. The moment I do "chmod a+r /var/lists/priv/configdb*" the queue is cleared and the refusal message reaches the external user. Can anyone please help me out ? I can not run apache with any other uid. I am thinking of patching the admindb.py to force the ownership to uid=mailman and gis=nofiles. This I want to do as a last resort if I dont find any responses. Regards. --ajit |-| | Ajit K. Jena Phone : (Office) +91-22-5767751 | | Computer Centre+91-22-5722545 x8750 | | Indian Institute of Technology(Home) +91-22-5722545 x8068 | | (Mobile) | | POWAI, Bombay Fax : +91-22-5723894 | | PIN 400076, India Email : [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
Re: [Mailman-Users] Mailman subscription limit?
On Fri, 19 Apr 2002 12:38:21 -0400 Stephen A Dale <[EMAIL PROTECTED]> wrote: > Is there a limit to the number of users you can have on a mailman > list? I am running mailman 2.0.5 on RedHat 7.0.91 with sendmail. Please see the FAQ: http://www.python.org/cgi-bin/faqw-mm.py -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- 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
Re: [Mailman-Users] mailman 2.0.9 attachment questions
On Fri, 19 Apr 2002 17:45:47 +0300 Egemen Ergel <[EMAIL PROTECTED]> wrote: > Is it possible to prevent people sending attachments to the mailing > list? Please see the FAQ: http://www.python.org/cgi-bin/faqw-mm.py -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- 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
[Mailman-Users] Re: mailman 2.0.9 attachment questions
Egemen Ergel wrote: > Is it possible to prevent people sending attachments to the mailing list? use demime or stripmime (see the faq) -- Will Yardley input: william < @ hq . newdream . net . > -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
[Mailman-Users] error 126
I am still stuck at the smrsh. I am getting error 126 send back to the email? - The following addresses had permanent fatal errors - "|/home/mailman/mail/wrapper mailcmd test" (reason: 126) - Transcript of session follows - /bin/sh: /usr/adm/sm.bin/wrapper: is a directory 554 5.3.0 "|/home/mailman/mail/wrapper mailcmd test"... unknown mailer error 126 strange isn't it? Erik -- 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
Re: [Mailman-Users] Topic Filters in 2.1b1
> "SKM" == Sarah K Miller <[EMAIL PROTECTED]> writes: SKM> However, right now, I can't get topics to work. I had 'em SKM> working, but now they're not. No matter what I do, I seem to SKM> get every post from a list that has topics, whether I've SKM> selected them or not. One of my many projects for the weekend SKM> is to try to at least isolate when/why it happens and go from SKM> there. Hmm, please try cvs or (if I get it out) beta2. I just tried some simple experiments and it seems to be working as documented. -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
Re: [Mailman-Users] missing db files for messages
> "MP" == Mark Peglow <[EMAIL PROTECTED]> writes: MP> 1) Is there a way to regenerate the db files so these stuck MP> messages can be delivered? If so, how? Not easily, although you can attempt to resend the messages through the system to get them unstuck. MP> 2) Is there a way to keep this from happening in the future? Upgrade to MM2.0.10. This is exactly the situation the last two patch releases fixed. -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
[Mailman-Users] Error.
Title: Message Hello I have configured all the tghings that exim tells me to: And configured the Mail man also. I have the following errors on the exim_mainlog: 2002-04-19 11:01:58 16yaph-00047B-00 <= [EMAIL PROTECTED] H=clueponbook.nasc.inter.net (app4.nasc.inter.net) [203.176.60.253] P=esmtp S=1327 id=004a01c0c8e0$9d9a79b0$890a0ac0@hubble2002-04-19 11:01:59 16yaph-00047B-00 ** [EMAIL PROTECTED] D=list_director T=list_transport: Child process of list_transport transport returned 2 from command: /home/mailman/mail/wrapper2002-04-19 11:02:01 16yapj-00047G-00 <= <> R=16yaph-00047B-00 U=root P=local S=21832002-04-19 11:02:01 16yaph-00047B-00 Error message sent to [EMAIL PROTECTED]2002-04-19 11:02:02 16yaph-00047B-00 Completed2002-04-19 11:02:04 16yapj-00047G-00 => [EMAIL PROTECTED] R=lookuphost T=remote_smtp H=bm.nasc.inter.net [203.176.60.83]2002-04-19 11:02:05 16yapj-00047G-00 Completed Can you please help on this.
[Mailman-Users] Mailman Footer
Is it possible to change the footer information to include some company specific logos and information? Noah Swint Pathways Community Network 1908 Cliff Valley Way NE Ste 250 Atlanta, GA 30329 404-584-6591, ext 303 404-584-9006 (fax) www.pathways-usa.org Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -- 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
[Mailman-Users] mailman 2.0.9 attachment questions
Is it possible to prevent people sending attachments to the mailing list? thnx -- 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
[Mailman-Users] Mailman subscription limit?
Is there a limit to the number of users you can have on a mailman list? I am running mailman 2.0.5 on RedHat 7.0.91 with sendmail. Thanks, Steve -- 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
Re: [Mailman-Users] problems up through 2.1b1
Message to self: RTFM. More appropriately: Read the Fine NEWS File The bounce problem was due to not having switched "wrapper" to "mailman" in my aliases. Now, the problem is somewhat different. Mail to all of the various mailman-managed addresses goes through. I get many lines of the following format in my error log: Apr 19 16:30:51 2002 (8765) lost data files for filebase: 1019248249.5778871+551c9167abc87d8d6b151ba2dcaccfdc818fee30 Also, I continue to get the same tracebacks on the membership management pages, which look like a bug. Did I miss something else in the docs? I think I've read them more thoroughly now... Thanks. -Justin > - > Traceback (most recent call last): > File "/home/mailman/scripts/driver", line 82, in run_main > main() > File "/home/mailman/Mailman/Cgi/admin.py", line 193, in main > show_results(mlist, doc, category, subcat, cgidata) > File "/home/mailman/Mailman/Cgi/admin.py", line 496, in show_results > form.AddItem(membership_options(mlist, subcat, cgidata, doc, form)) > File "/home/mailman/Mailman/Cgi/admin.py", line 823, in membership_options > qs = cgi.parse_qs(os.environ['QUERY_STRING']) > File "/usr/local/stow/Python-2.2/lib/python2.2/UserDict.py", line 14, in >__getitem__ > def __getitem__(self, key): return self.data[key] > KeyError: QUERY_STRING > - -- 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
Re: [Mailman-Users] Topic Filters in 2.1b1
- Original Message - From: "Barry A. Warsaw" <[EMAIL PROTECTED]> > > "S" == Spam <[EMAIL PROTECTED]> writes: > > S> I need help though. When subscribing new members to a list that > S> uses topic filters, I want the default to be that people > S> receive only those messages that have a topic and that they not > S> receive the rest. Right now, the default is that they not > S> receive any of the topics and not receive any of the > S> non-topics, meaning they get nothing at all! > > Ah, this is because by default, no user is subscribed to a topic, and > there's no way for the admin to auto-subscribe users to a topic. To > further complicate things, the default is for users to not receive > messages that match no topics. > > I've re-examined the topic stuff and I'm not entirely sure that we've > got the semantics right for the defaults. Would it help if, by > default, a user were to receive all messages that don't match a topic? I poked around a bit too. I think that in truth, by default everybody gets every message, unless they choose some topics, in which case they get only the topics. That works ok in theory. However, right now, I can't get topics to work. I had 'em working, but now they're not. No matter what I do, I seem to get every post from a list that has topics, whether I've selected them or not. One of my many projects for the weekend is to try to at least isolate when/why it happens and go from there. -- Sarah -- 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
[Mailman-Users] missing db files for messages
Hello, I am running Mailman 2.0.8 on FreeBSD 4.5-STABLE with Python 2.0.1 and Sendmail 8.11.6. I have several message file (.msg) with no corresponding .db files. From the logs, it seems that qrunner determined that the db files were orphaned and removed them. Most messages are delivered without a problem. The log entry: Apr 19 17:08:06 2002 (80652) Unlinking orphaned .db file: /usr/local/mailman/qfiles/9ce5400cd779c86b3ae5adc4a73790d618d0163f.db There are no error messages around this (except that qrunner cannot open the db file it just removed). The message file: -rw-rw-r-- 1 mailnull mailman - 7735 Apr 19 17:08 9ce5400cd779c86b3ae5adc4a73790d618d0163f.msg The system does get busy from time to time (although I cannot correlate the failures to system load), so I am guessing that the message starts to get queued up (the database file is written) then gets held up writing the message file, during which time qrunner starts, finds the .db file and no .msg file, so it removes it. My questions: 1) Is there a way to regenerate the db files so these stuck messages can be delivered? If so, how? 2) Is there a way to keep this from happening in the future? Thank you in advance for you help with this. Mark. -- 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
[Mailman-Users] problems up through 2.1b1
I was having some problems with one of the cgis under 2.1a2, but that sort of thing is to be expected with an alpha release. I figured that I'd upgrade to 2.1b1 to see if it helped. Well, it changed the problem. All mail to any mailman/wrapper managed addresses now bounce like so: - <[EMAIL PROTECTED]>: Command died with status 1: "/home/mailman/mail/wrapper post loopback" Reporting-MTA: dns; ra.iago.org Arrival-Date: Fri, 19 Apr 2002 13:29:41 -0400 (EDT) Final-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; Command died with status 1: "/home/mailman/mail/wrapper post loopback" - Some of the web page CGI scripts throw tracebacks. For instance, the admin membership management page: - Traceback (most recent call last): File "/home/mailman/scripts/driver", line 82, in run_main main() File "/home/mailman/Mailman/Cgi/admin.py", line 193, in main show_results(mlist, doc, category, subcat, cgidata) File "/home/mailman/Mailman/Cgi/admin.py", line 496, in show_results form.AddItem(membership_options(mlist, subcat, cgidata, doc, form)) File "/home/mailman/Mailman/Cgi/admin.py", line 823, in membership_options qs = cgi.parse_qs(os.environ['QUERY_STRING']) File "/usr/local/stow/Python-2.2/lib/python2.2/UserDict.py", line 14, in __getitem__ def __getitem__(self, key): return self.data[key] KeyError: QUERY_STRING Python information: Variable Value sys.version 2.2 (#1, Dec 28 2001, 09:54:53) [GCC 2.96 2306 (experimental)] sys.executable /usr/local/bin/python sys.prefix /usr/local/bin/../stow/Python-2.2 sys.exec_prefix /usr/local/bin/../stow/Python-2.2 sys.path /usr/local/bin/../stow/Python-2.2 sys.platform sunos5 Environment variables: Variable Value HTTP_ACCEPT text/html, image/png, image/jpeg, image/gif, image/x-xbitmap, */* AUTH_TYPE Basic HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.0; Linux 2.2.12 i386) Opera 5.0 [en] TZ US/Eastern HTTP_REFERER http://www.iago.org/mailman/admin/in-the-wings SERVER_NAME ra GATEWAY_INTERFACE CGI/1.1 PYTHONPATH /home/mailman REMOTE_ADDR 65.202.32.10 SERVER_SOFTWARE thttpd/2.21b 23apr2001 SCRIPT_NAME /mailman/admin CGI_PATTERN mailman/**|mailman/*/* REQUEST_METHOD GET HTTP_HOST www.iago.org PATH_TRANSLATED /export/home/thttpd/data/in-the-wings/members SERVER_PORT 80 SERVER_PROTOCOL HTTP/1.1 HTTP_ACCEPT_ENCODING deflate, gzip, x-gzip, identity, *;q=0 HTTP_COOKIE in-the-wings+admin=28020069803dc03c73280037363130656131663133376434323732313431363033306233366437343037353830353666303238 PATH_INFO /in-the-wings/members (sorry for the formatting, it didn't survive cut/paste very well) - Did I miss some documentation necessary for the upgrade? Mailman is useless on this host at this time. Thanks for any help. Please let me know if there is any more info that I can provide. -Justin -- 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
[Mailman-Users] OT: Projects need Money. You can help!
Apologies in advance if this feels spammy. I showed it to Barry first and he thought the concept was interesting. We both would like to see what you think of the idea. I have been working with a few folks on a grassroots way for people to donate money to various non-profits & projects such as Apache, Hurd, EFF, or even to a given developer. This donation might be in response to some helpful feedback given by that developer in response to a question on a mailing list; it might be because their name and URL were in some software they used. To be upfront: Affero adds 10% on top of the donation for our expenses. We hope this is reasonable given the costs involved in credit card auth and the like. There are other sites out there that don't charge you anything like justgive.org The problem is justgive.org and other sites like it, are limited to 501c3 charities and you have to go to the site to donate. Affero is viral network, where the donation happens after an event. The event being the support givin on mailing lists. For example: Jon wants to get his employer to change their privacy policy but runs into a brick wall. Jon goes to some discussion list and pleads for help. Jane, and EFF supporter, responds to Jon's plea and give him some specific ideas and resources about how to turn his employer around. Jon uses the approach and is successfull. Jon wants to say thanks to Jane, so he clicks on a URL in her email message. The URL takes Jon to a webpage where he can give public praise to Jane as well as donate $50 to her favorite foundations (which includes the GNU and the ACLU). The software used to deliver the service is open source. You can click on the "(0)" any page in our service and download the source. For example, take a look at a link I created below. http://svcs.affero.net/rm.php?r=creed&p=Projects People can go to that URL and donate money, 35% of which goes to the Squid, 35% to XFree86 and 30% to FSF Gen Fund-GCC. We're very interested in any comments and feedback on the site/service. Sign up and raise some cash for your favorite project! You can check it out at http://www.affero.net to see some demos. BTW, we have been told that we should lower the current $15.00 minimum. What do you think? Thanks Reed How valuable is my contribution? Share your feedback at Affero: http://svcs.affero.net/rm.php?r=creed&p=Projects Office: 415 371 9900 [EMAIL PROTECTED] http://www.affero.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
[Mailman-Users] pending subscription problem in 2.0.9
I am having a problem with 2.0.9 I have not been able to get the web interface to work for subscriptions. When I attempt to subscribe on the general user web page. I get an acknowledgement of the subscription with the note that I will have to respond to the email message to confirm my subscription. The email message never comes. If I look in the subscription log I see the standard entry for a pending subscription. Apr 15 10:45:53 2002 (9697) help: pending [EMAIL PROTECTED] 129.186.254.254 However, I never get an email message to confirm the subscription. I see no errors or abnormalities on the web server side. I am running Apache 1.3.22 on RedHat Linux 7.1. This happens if I set it to confirm for the subscription verification. If I change it to require approval, it works and I can approve subscriptions. I do not want to get all the approve and disapprove email on most of my lists I just want the user to subscribe and confirm. Any ideas on how to fix this or where to look next? -- --Tom /- | Tom Hillson Computer Services Manager | [EMAIL PROTECTED] College of Agriculture | http://www.ag.iastate.edu Iowa State University | (515) 294-1543 phoneB2 Curtiss Hall | (515) 294-1349 fax Ames, IA 50011 - |"The only thing I have too much of is too little time" -- 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
[Mailman-Users] Wrapper and SMRSH???
Hi there! I'm a total newbie, the newest kind... I installed Mailman under Netmax-linux (Based on RH6) and got the follwing problem, which I even found in the FAQ: Problem: I send mail to the list, and get back mail saying, sh: wrapper not available for sendmail programs Solution: Your system uses sendmail restricted shell (smrsh). You need to configure smrsh by creating a symbolic link from the mail wrapper ($prefix/mail/wrapper) to the directory identifying executables allowed to run under smrsh. Some common names for this directory are /var/admin/sm.bin, /usr/admin/sm.bin or /etc/smrsh. Note that on Debian Linux, the system makes /usr/lib/sm.bin, which is wrong, you will need to create the directory /usr/admin/sm.bin and add the link there. Note further that any aliases newaliases spits out will need to be adjusted to point to the secure link to the wrapper. So: What do I type in to fix this ? My SMRSH directory is /usr/sbin Help!? Erik -- 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
Re: [Mailman-Users] Any method to set alias for each member?
hey, the only way i see of accomplishing the second task is to forget the first. Granted that will expose the email addresses of the people sending to the list but it will also take their specified from name insted of their email address. for example as i type this now according to outlook i am replying to lewis lau insted of your email address. Matt Lavergne Tech Support Interlynx Internet 905-524-5969 x229 1-888-658-5969 x229 - Original Message - From: "Lewis Lau" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 19, 2002 12:33 AM Subject: [Mailman-Users] Any method to set alias for each member? > > >Hi, > > > >Now I have Mailman 2.0.9 up and run on my Mandrake box. I've created a > >small list (about 20 members) for my students to take group discussion. > >What I exactly wanted is: > > 1. Hidden the "real email address" of the senders when they posting > > message on the list. > > 2. Each of them should have an alias (different names) showing in > > the email header, so that others are still able to realise who is who. > > > >I done the first part by set the "Hide the sender of a message, replacing > >it with the list address (Removes From, Sender and Reply-To fields)" > >option in the "Privacy Option" page to "Yes", now everybody have a fake > >"From address": [EMAIL PROTECTED], but unfortunately everybody > >have the same "From" alias, "Member-admin" as well! =( > > > >Can somebody tell me how to setup the second part? I sincerely appreciate > >for your kindly help! > > > >Best Regards, > >Lewis > > > > > -- > 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 > -- 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
Re: [Mailman-Users] Headers and why they suck
On 4/19/02 8:53 AM, "Jon Carnes" <[EMAIL PROTECTED]> wrote: > Makes you kind of want to create a "Meta" admin page with some standard > setups like Announce-only list, etc. Or write up faqs/howtos on how to configure specific standard list styles? Maybe an operators manual of some sort? -- Chuq Von Rospach, Architech [EMAIL PROTECTED] -- http://www.chuqui.com/ Very funny, Scotty. Now beam my clothes down here, will you? -- 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
Re: [Mailman-Users] Headers and why they suck
> "JC" == Jon Carnes <[EMAIL PROTECTED]> writes: JC> Makes you kind of want to create a "Meta" admin page with some JC> standard setups like Announce-only list, etc. What I have in mind for MM-after-2.1 is to allow the creation of "list styles" which can be easily applied to any particular list. Probably exactly what you're thinking about. -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
Re: [Mailman-Users] regexes in bounce_matching_headers
On Wed, 2002-04-17 at 03:41, Joern Nettingsmeier wrote: > a number of questions about regexes in mailman: > i'm desperately looking for a python-specific regex documentation. > i'm using a php manual (whose regexes are said to be > perl-compatible), but i seem to run into subtle problems. any > pointers ? Joern, Here are a couple of links that may help. Also, take a look in the list archive for a thread named "Regular Expressions". http://www.python.org/doc/current/lib/re-syntax.html http://py-howto.sourceforge.net/regex/regex.html -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ -- 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
Re: [Mailman-Users] Headers and why they suck
Makes you kind of want to create a "Meta" admin page with some standard setups like Announce-only list, etc. -- 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
Re: [Mailman-Users] Re: Editability of messages
> "DM" == Dan Mick <[EMAIL PROTECTED]> writes: DM> Umbrella lists have always confused me, so it wouldn't DM> surprise me if the List- headers are wrong there. (Not that DM> I'm responsible for them, but that I have no experience with DM> umbrella lists.) FWIW, they've always confused me too (there were there long before I took over ;). I believe I know how it Ought To Be Done so it's likely that they will go away in MM3. The feature I have in mind will be so much more flexible. It's been discussed in mailman-developers, so I won't go into details here. -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
Re: [Mailman-Users] RELEASED Mailman 2.0.10
> "MTV" == Mark T Valites <[EMAIL PROTECTED]> writes: MTV> When did the race condition occour? Mailman uses a clever naming scheme to make sure that a partially written incoming message isn't processed by the qrunner. It has to do this because two separate processes are writing the incoming messages and reading the same messages for processing. Pretty typical system design stuff. The race condition in 2.0.8 occurred because of a disagreement in which file name extension between the reader and the writer. The race could -- very occasionally -- cause email to get lost. Chuq gave a very nice explanation of why this happens, and why it's so rare; see the mailman-developers archives for details. So 2.0.9 fixes this race condition by making sure the reader and writer agree on the naming convention being used. But it had a small bug in the name lookup routine which would cause spurious error messages in the log file. 2.0.9 won't lose email because of this bug, which is why the upgrade to 2.0.10 isn't a critical patch. You'll just get some useless errors in the error log, with about the same (in)frequency as the race condition in 2.0.8. -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
Re: [Mailman-Users] Topic Filters in 2.1b1
> "S" == Spam <[EMAIL PROTECTED]> writes: S> First, I have to say that 2.1b1 is a beautiful thing! It does S> all things I've always thought Mailman should. :) Great! S> I need help though. When subscribing new members to a list that S> uses topic filters, I want the default to be that people S> receive only those messages that have a topic and that they not S> receive the rest. Right now, the default is that they not S> receive any of the topics and not receive any of the S> non-topics, meaning they get nothing at all! Ah, this is because by default, no user is subscribed to a topic, and there's no way for the admin to auto-subscribe users to a topic. To further complicate things, the default is for users to not receive messages that match no topics. I've re-examined the topic stuff and I'm not entirely sure that we've got the semantics right for the defaults. Would it help if, by default, a user were to receive all messages that don't match a topic? -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
Re: [Mailman-Users] Re: Removing those extra List-* headers
> "TN" == Tom Neff <[EMAIL PROTECTED]> writes: TN> Look, I completely agree with you about this major gotcha with TN> Mailman, that its otherwise terrifically brilliant coders TN> happen to have some ideological hobbyhorses they ride - there TN> is no use arguing with them about it. I wouldn't say that. Read my other response to this thread. -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
Re: [Mailman-Users] Keeping HTML in pipermail
> "AD" == Allen Day <[EMAIL PROTECTED]> writes: AD> I asked about this a while ago, and never received a response. AD> Here we go again. AD> How can I prevent pipermail from escaping out the tags in HTML AD> email? I want the archived messages to be in HTML form, as AD> they were sent out. In MM2.1, you'd want to set ARCHIVE_HTML_SANITIZER = 3 -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
Re: [Mailman-Users] Mailman
> "carmine" == <[EMAIL PROTECTED]> writes: carmine> When member_posting_only is set to yes, is there a carmine> setting to DUMP un-authorized email rather than send it carmine> to list admin for review? There will be 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
Re: [Mailman-Users] Headers and why they suck
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: CVR> On 4/8/02 9:59 AM, "Dave Sherohman" <[EMAIL PROTECTED]> CVR> wrote: >> OK, I'll give you that List-Post: isn't applicable to your >> list. CVR> And I believe in 2.1, mailman won't include headers that CVR> aren't relevant to a list, so an announce-only list won't get CVR> list-post. Barry? Is that true? I know we talked about it. Sort of. There's actually no concrete notion of an "announce-only" list; IOW, there's no switch to pull to say this is or isn't an announce-only list. In MM2.1, the way to do that is to - turn on the moderation flag for all members - set the default moderation action to discard (or hold if you don't want to be so strict/nasty). - turn off the moderation flag for the members who are allowed to post - add any non-members who are allowed to post to the "accept these non-members" list. That having been said, MM2.1beta2 will have the following controls on the List-* headers: - if the site administrator allows it, you can suppress all the List-* headers for all messages. For MM2.1beta2, I'm going to change the default to allow list owners to override the headers (the default used to be to not allow overrides). - there will be a separate config option to include the List-Post: header. Set this to No if you're running an announce-only list - List-Archive: will only be added if your list actually has archives enabled. - List-Id: will always be added for all messages (unless suppression of all rfc2369 headers is enabled). - for non-administrivia messages (i.e. postings), List-Help:, List-Unsubscribe:, and List-Subscribe: will be added (unless suppression of all rfc2369 headers is enabled). - for administrivia messages, those three headers will not be included, but an X-List-Administrivia: header will be added instead (again, unless all are suppressed). I think that about covers all the bases, and should make everyone happy (FLW). -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
Re: [Mailman-Users] moving from yahoo
In article <[EMAIL PROTECTED]>, Charles Sebold <[EMAIL PROTECTED]> writes >On 7 Iyyar 5762, Robin Becker wrote: > >> Some people have kept private partial archives eg gnu nnml and suggest >> that this should be easy to convert to mbox form. I know little about >> the internals of Mailman, nnml or mbox can anyone suggest a plan? > >[this part of the answer is off-topic to Mailman technically, sorry to >other readers] thx mucho. I hope my correspondent can do this, but your info looks OK to me (as a non-gnus user). > >As far as Gnus and nnml goes, the easiest thing to do would be to ask >the users with nnml archives to copy them to an nnmbox archive and send >that to you. That is standard mbox format. Then you don't have to do >any massaging of data. > >In Gnus: > >* Enter the mail folder using C-u RET >* M P b >* B c nnmbox:mbox > >That (or something close to that, I didn't test it) should generate an >mbox archive, probably in the user's ~/mbox file. Then they can just >gzip that and send it to you. Note that you may have to strip >extraneous headers that Gnus added (not sure about that), but I'm >guessing you can accomplish that with a grep -v or something like that. -- Robin Becker -- 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
Re: [Mailman-Users] force existing users to reautherticate ?
Available in the beta 2.1.x series, but not the current 2.0.x series. You could dump the list to a file and then try: for i in `cat file`; do mail -s "subscibe $i" [EMAIL PROTECTED] \ Hi all, > > I have resurrecting a stale list from another server > and was wondering if it is possible to force the > current subscribers (i added them from a flat file > using the utility) to re-authenticate ? > > I am using mailman 2.0.8/Linux RH 7.2. > > Thanks, > Moshe > www.bgaddict.com > > > > __ > Do You Yahoo!? > Yahoo! Tax Center - online filing with TurboTax > http://taxes.yahoo.com/ > > > -- > Mailman-Users mailing list > [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py -- 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
[Mailman-Users] force existing users to reautherticate ?
Hi all, I have resurrecting a stale list from another server and was wondering if it is possible to force the current subscribers (i added them from a flat file using the utility) to re-authenticate ? I am using mailman 2.0.8/Linux RH 7.2. Thanks, Moshe www.bgaddict.com __ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Re: [Mailman-Users] Urgent! Guys, I need help!
Charles Sebold <[EMAIL PROTECTED]> writes: > On 7 Iyyar 5762, Detlef Neubauer wrote: > > > Sorry Guys, > > > > why did you send all the messages as Cc: to me? I read the list. > > Because you didn't have a header that said something like > "Mail-Copies-To: never" or "nobody" in your headers? Right! I solve this problem. Mit freundlichen Grüßen Detlef Neubauer -- .oO GnuPG Key auf http://www.keyserver.net/ Oo. -- 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
Re: [Mailman-Users] Urgent! Guys, I need help!
On 7 Iyyar 5762, Detlef Neubauer wrote: > Sorry Guys, > > why did you send all the messages as Cc: to me? I read the list. Because you didn't have a header that said something like "Mail-Copies-To: never" or "nobody" in your headers? -- Charles Sebold Shabbat Shalom 7th of Iyyar, 5762 LCMS - Office of Information Systemshttp://unix.ois.org/ *** Opinions expressed herein are not necessarily *** *** those of the Lutheran Church - Missouri Synod *** -- 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
Re: [Mailman-Users] moving from yahoo
On 7 Iyyar 5762, Robin Becker wrote: > Some people have kept private partial archives eg gnu nnml and suggest > that this should be easy to convert to mbox form. I know little about > the internals of Mailman, nnml or mbox can anyone suggest a plan? [this part of the answer is off-topic to Mailman technically, sorry to other readers] As far as Gnus and nnml goes, the easiest thing to do would be to ask the users with nnml archives to copy them to an nnmbox archive and send that to you. That is standard mbox format. Then you don't have to do any massaging of data. In Gnus: * Enter the mail folder using C-u RET * M P b * B c nnmbox:mbox That (or something close to that, I didn't test it) should generate an mbox archive, probably in the user's ~/mbox file. Then they can just gzip that and send it to you. Note that you may have to strip extraneous headers that Gnus added (not sure about that), but I'm guessing you can accomplish that with a grep -v or something like that. -- Charles Sebold Shabbat Shalom 7th of Iyyar, 5762 LCMS - Office of Information Systemshttp://unix.ois.org/ *** Opinions expressed herein are not necessarily *** *** those of the Lutheran Church - Missouri Synod *** -- 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
Re: [Mailman-Users] Urgent! Guys, I need help!
Lewis Lau <[EMAIL PROTECTED]> writes: > Dear guys, > > I got it!! It works!! I love you all!! Haha... > So happy now! Thanks for all of your kindly help! Sorry Guys, why did you send all the messages as Cc: to me? I read the list. Mit freundlichen Grüßen Detlef Neubauer -- .oO GnuPG Key auf http://www.keyserver.net/ Oo. -- 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
[Mailman-Users] moving from yahoo
I am trying to move two lists from yahoogroups/egroups to mailman. We would like to preserve and transfer the archive. has anyone else attempted this? Some people have kept private partial archives eg gnu nnml and suggest that this should be easy to convert to mbox form. I know little about the internals of Mailman, nnml or mbox can anyone suggest a plan? -- Robin Becker -- 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
[Mailman-Users] Mailman 2.0.10 compatible Mailman/htdig integration patchesposted
I have just posted on soureforge revised versions of one of the patches needed for the Mailman htdig integration. The other patch needed no revision from its MM 2.0.9 version. You will now need to apply the following files in the order they are listed to the vanilla MM 2.0.10 build directory: 1. from http://sourceforge.net/tracker/index.php?func=detail&aid=444879&group_id=103&atid=300103 file indexing-2.0.9-0.1.patch 2. from http://sourceforge.net/tracker/index.php?func=detail&aid=444884&group_id=103&atid=300103 file htdig-2.0.10-0.1.patch Any problems with these then let me know -- 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
