[Mailman-Users] Mailman under Debian -- Icons aren't showing up.
Hello, I am using Debian Linux and I have mailman up and running, but I'm running into a few problems. When I connect to the admin page, I get there, but I get three blue boxed question marks at the bottom of the page as if something or some images aren't loading. I read the help sheet on copying over icons to the apache/icons directly, and putting PythonPowered.png, mailman-large.png, and mailman.jpg into the /usr/share/apache/icons directory has done nothing for me. Also, when I attempt to go to the mail archives, I get: The requested URL /pipermail/mailman/ was not found on this server. Do I have to install Pipermail? Thanks for any and all help. Aaron ~ -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Exim and Mailman, address_pipe and never_users
I didn't see this come through the list since yesterday, so I figured I'd send it again... --- I'm running Gentoo with Exim 4.43-r2 and Mailman 2.1.5-r4. When I send a message to my list rbc, it never gets sent. The logs have some entries that look like this: Apr 6 00:42:21 [exim] 2005-04-06 00:42:21 no host name found for IP address 10.10.10.69 Apr 6 00:42:21 [exim] 2005-04-06 00:42:21 1DJ5B7-0006dd-Cc = [EMAIL PROTECTED] H=(locutus) [10.10.10.69] P=esmtpsa X=TLSv1:RC4-MD5:128 A=login:dae51d S=569 Apr 6 00:42:21 [exim] 2005-04-06 00:42:21 1DJ5B7-0006dd-Cc User 0 set for address_pipe transport is on the never_users list - Last output repeated twice - Apr 6 00:42:21 [exim] 2005-04-06 00:42:21 1DJ5B7-0006dd-Cc == |/usr/local/mailman/mail/mailman post rbc [EMAIL PROTECTED] R=system_aliases T=address_pipe defer (-29): User 0 set for address_pipe transport is on the never_users list I've googled for address_pipe and never_users and it seems to be Exim related, but I really don't know what to change to fix this. I used to run mailman 2.0 with sendmail on an old RH8 box. Exim is all new to me too. Sorry if this is off topic. I tried to follow the instructions here, but still no joy. http://www.exim.org/howto/mailman21.html#exconf Something isn't right: daevid bin # exim -bt [EMAIL PROTECTED] [EMAIL PROTECTED] - |/usr/local/mailman/mail/mailman post rbc transport = address_pipe When it should say: router = mailman_router, transport = mailman_transport -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;fileúq01.027.htp
Re: [Mailman-Users] How to rebuild html archives from plaintext ?
On Thursday 07 April 2005 06:17, you wrote: helen wrote: Thank you ! It appeared even easier than in the FAQ - just bin/arch list_name (it figured out by itself to use the archived text files instead of the mbox file) Actually, the normal archiving process creates the cuumulative archives/private/listname.mbox/listname.mbox file as well as the monthly text files and that's what bin/arch used, but the bottom line is it worked. *feels stupid* Indeed, the mbox contained the posts back to 2001 ! for some reason I had decided that the file is too small to contain all the postings - but apparently the list in question is very low-traffic. BTW, if you didn't use --wipe with bin/arch, you might want to check carefully in the monthly files for duplicates. If you have duplicates, you can just make a new, clean archive with the --wipe option. Thank you ! -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- ^.^ || ~~~ -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] In it possible to have Accept ticked by default?
Thank you Mark for your reply. I've submitted a feature request for this. Here's my reasoning: One particular user from our organization regularly sends several emails to several moderated mailman lists. It is sufficient to simply see who the message is from and then Accept it. We have to approve each one separately and we have to change the Defer tick each time. It's becoming a pain and it would be nice not to make those extra mouse movements. -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] In it possible to have Accept ticked by default?
At 7:46 AM -0500 2005-04-07, Rodger Copp wrote: One particular user from our organization regularly sends several emails to several moderated mailman lists. It is sufficient to simply see who the message is from and then Accept it. Then put their address on the whitelist, so that their messages are automatically accepted and you don't have to manually moderate them. This is a much better solution than taking the serious risk of accidentally approving a whole raft of spam messages. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] getting uncaught bounce notification but not always !
Hi. I have been getting uncaught bounce notifications from messages which look like they should have worked. Now the one thing you should know is that I had to change the verp stuff to go along with qmail which uses a - instead of + for its verp processing. I changed the regular expressions and the formats (I hope) correctly and some bounces were processed correctly, but not ones like the one below. So, if you could assist me in this, I would appreciate it. P.S. Is there a way to get qmail to do the right thing and use a + rathar than a - for its verp? Here is one of the messages I got. From [EMAIL PROTECTED] Wed Apr 6 23:41:33 2005 X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] [3348 Wednesday 6 April 2005 22:31:11 -0500 [EMAIL PROTECTED] [EMAIL PROTECTED] nil 89 Uncaught bounce notification ^From: [EMAIL PROTECTED] [EMAIL PROTECTED] 4 nil nil nil nil nil nil nil nil nil] nil) Received: from fwd1a.spamh.com (fwd1a.spamh.com [207.44.136.106]) by ccs.covici.com (8.13.1/8.13.1) with ESMTP id j373fU9O013682 for [EMAIL PROTECTED]; Wed, 6 Apr 2005 23:41:33 -0400 Received: from m5.spamh.com (m5.spamh.com [70.84.233.170]) by fwd1a.spamh.com (8.12.11/8.12.11) with ESMTP id j373fTCt031700 for [EMAIL PROTECTED]; Wed, 6 Apr 2005 23:41:29 -0400 Received: from main.wlym.com (lb1d.spamh.com [67.18.240.242]) by m5.spamh.com (8.13.1/8.13.1) with ESMTP id j373fSAl004157 for [EMAIL PROTECTED]; Wed, 6 Apr 2005 23:41:28 -0400 Received: (qmail 27157 invoked from network); 7 Apr 2005 03:41:10 - Received: from localhost (HELO main.wlym.com) (?09g8yZEbNPaG6vGgauAu8L8QL/[EMAIL PROTECTED]) by localhost with SMTP; 7 Apr 2005 03:41:10 - MIME-Version: 1.0 Content-Type: multipart/mixed; boundary1447001146== Message-ID: [EMAIL PROTECTED] Precedence: bulk X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.5 Errors-To: [EMAIL PROTECTED] X-SpamH-CheckIP: 69.57.138.70 X-SpamH-Recipient: [EMAIL PROTECTED] X-SpamH-ID: j373fSAl004157 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on ccs.covici.com X-Spam-Level: X-Spam-Status: No, score=-11.0 required=8.0 tests=BAYES_00,NO_REAL_NAME, USER_IN_WHITELIST autolearn=no version=3.0.2 From: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Uncaught bounce notification Date: Wed, 06 Apr 2005 22:31:11 -0500 --===1447001146== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s). For more information see: http://lists.wlym.com/mailman/admin/lalist/bounce --===1447001146== Content-Type: message/rfc822 MIME-Version: 1.0 Return-Path: Delivered-To: [EMAIL PROTECTED] Received: (qmail 10290 invoked from network); 7 Apr 2005 03:31:11 - Received: from smtp.ucla.edu (169.232.47.138) by wlym.com with SMTP; 7 Apr 2005 03:31:11 - Received: from localhost (localhost) by smtp.ucla.edu (8.13.1/8.13.1) id j373VTeW004601; Wed, 6 Apr 2005 20:31:29 -0700 Date: Wed, 6 Apr 2005 20:31:29 -0700 From: Mail Delivery Subsystem [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Returned mail: see transcript for details Auto-Submitted: auto-generated (failure) The original message was received at Wed, 6 Apr 2005 20:31:28 -0700 from wlym.com [69.57.138.70] - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 5.0.0 [EMAIL PROTECTED]... User unknown) - Transcript of session follows - ... while talking to mail.ucla.edu.: DATA 550 5.0.0 [EMAIL PROTECTED]... User unknown 550 5.1.1 [EMAIL PROTECTED]... User unknown 503 5.0.0 Need RCPT (recipient) - Message header follows - Received: from main.wlym.com (wlym.com [69.57.138.70]) by smtp.ucla.edu (8.13.1/8.13.1) with ESMTP id j373VSeW004588 for [EMAIL PROTECTED]; Wed, 6 Apr 2005 20:31:28 -0700 Received: (qmail 9607 invoked from network); 7 Apr 2005 03:30:40 - Received: from unknown (HELO main.wlym.com) ([EMAIL PROTECTED]) by 127.0.0.1 with SMTP; 7 Apr 2005 03:30:40 - Delivered-To: [EMAIL PROTECTED] Received: (qmail 8395 invoked from network); 7 Apr 2005 03:29:40 - Received: from bay13-f6.bay13.hotmail.com (HELO hotmail.com) (64.4.31.6) by wlym.com with SMTP; 7 Apr 2005 03:29:40 - Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 6 Apr 2005 20:29:24 -0700 Message-ID: [EMAIL PROTECTED] Received: from 64.30.208.48 by by13fd.bay13.hotmail.msn.com with HTTP; Thu, 07 Apr 2005 03:29:24 GMT X-Originating-IP: [64.30.208.48] X-Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wed, 06 Apr 2005 20:29:24
[Mailman-Users] brainstorming sending options (approval of moderated messages)
I have a script that monthly removes the members of a list and then updates it from another file. The default for all members is 'moderated',including the only person who will send messages, so as to prevent spammers from spoofing list owners email and sending to the 40,000 member list. I just need to clarify a couple of things about posting to lists. My tests show that if a subscriber is moderated and also is listed as a non-member who has permission to post, a post from that person is considered a post from a moderated member. So, assuming the above, the only way to allow this person to post without having to go through the approval process would be to send a message with the Approved: password as the first line. Could someone verify that this is correct? Are there any other configuration options that would make this work without the sender having to intervene or send the Approved:password line? -- Christopher Adams -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Exim and Mailman, address_pipe and never_users
Daevid Vincent wrote: I didn't see this come through the list since yesterday, so I figured I'd send it again... It was on the list yesterday and Brad's reply is at http://mail.python.org/pipermail/mailman-users/2005-April/043964.html Brad's reply is that this is an Exim question and Exim lists, etc are much more likely to provide a useful response than this list. In order to prove Brad correct, I'll point out what I (not an Exim guy) see, but I can't tell you what to do about it because I don't know. --- I'm running Gentoo with Exim 4.43-r2 and Mailman 2.1.5-r4. When I send a message to my list rbc, it never gets sent. The logs have some entries that look like this: Apr 6 00:42:21 [exim] 2005-04-06 00:42:21 no host name found for IP address 10.10.10.69 Apr 6 00:42:21 [exim] 2005-04-06 00:42:21 1DJ5B7-0006dd-Cc = [EMAIL PROTECTED] H=(locutus) [10.10.10.69] P=esmtpsa X=TLSv1:RC4-MD5:128 A=login:dae51d S=569 Apr 6 00:42:21 [exim] 2005-04-06 00:42:21 1DJ5B7-0006dd-Cc User 0 set for address_pipe transport is on the never_users list - Last output repeated twice - Apr 6 00:42:21 [exim] 2005-04-06 00:42:21 1DJ5B7-0006dd-Cc == |/usr/local/mailman/mail/mailman post rbc [EMAIL PROTECTED] R=system_aliases T=address_pipe defer (-29): User 0 set for address_pipe transport is on the never_users list This seems to me to be saying that Exim is trying to pipe the message (presumably to the mailman wrapper), but it is running as User 0 (root) which is on some Exim configured list (never-users) of users not allowed to do this. I've googled for address_pipe and never_users and it seems to be Exim related, but I really don't know what to change to fix this. I used to run mailman 2.0 with sendmail on an old RH8 box. Exim is all new to me too. Sorry if this is off topic. I don't know what to change either. I tried to follow the instructions here, but still no joy. http://www.exim.org/howto/mailman21.html#exconf Something isn't right: daevid bin # exim -bt [EMAIL PROTECTED] [EMAIL PROTECTED] - |/usr/local/mailman/mail/mailman post rbc transport = address_pipe When it should say: router = mailman_router, transport = mailman_transport Actually, I think the above is right. Mail to the list post address ([EMAIL PROTECTED]) should be piped to the mailman wrapper exactly as shown in the response. The router = and transport = stuff is an Exim incantation that tells Exim to do its Mailman magic which results in the pipe as shown. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman under Debian -- Icons aren't showing up.
Aaron The Young wrote: When I connect to the admin page, I get there, but I get three blue boxed question marks at the bottom of the page as if something or some images aren't loading. I read the help sheet on copying over icons to the apache/icons directly, and putting PythonPowered.png, mailman-large.png, and mailman.jpg into the /usr/share/apache/icons directory has done nothing for me. Have you set IMAGE_LOGOS in mm_cfg.py? Also, when I attempt to go to the mail archives, I get: The requested URL /pipermail/mailman/ was not found on this server. Do I have to install Pipermail? No, but you have to configure the pipermail alias in your web server. See http://www.list.org/mailman-install/node10.html for more on both of these things. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] UnicodeDecodeError: 'ascii' codec can't decode byte
I'm seeing a problem where messages get in to mailman, and into the archives, but never get sent. When this happens I see this in the error log: Apr 07 22:14:30 2005 (2477) Uncaught runner exception: 'ascii' codec can't decode byte 0x92 in position 291: ordinal not in range(128) Apr 07 22:14:30 2005 (2477) Traceback (most recent call last): File /usr/local/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop self._onefile(msg, msgdata) File /usr/local/mailman/Mailman/Queue/Runner.py, line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/local/mailman/Mailman/Queue/OutgoingRunner.py, line 73, in _dispose self._func(mlist, msg, msgdata) File /usr/local/mailman/Mailman/Handlers/SMTPDirect.py, line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File /usr/local/mailman/Mailman/Handlers/SMTPDirect.py, line 285, in verpdeliver Decorate.process(mlist, msgcopy, msgdata) File /usr/local/mailman/Mailman/Handlers/Decorate.py, line 95, in process payload = header + frontsep + oldpayload + endsep + footer UnicodeDecodeError: 'ascii' codec can't decode byte 0x92 in position 291: ordinal not in range(128) Apr 07 22:14:32 2005 (2477) SHUNTING: 1112933669.117754+96c37c2b0a5227c2d9e33ff582f5651df360473d Any help in solving this will be greatly appreciated. --Richard -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] UnicodeDecodeError: 'ascii' codec can't decode byte
Richard Pyne wrote:
I'm seeing a problem where messages get in to mailman, and into
the archives, but never get sent. When this happens I see this
in the error log:
snip
File /usr/local/mailman/Mailman/Handlers/Decorate.py, line
95, in process
payload = header + frontsep + oldpayload + endsep + footer
UnicodeDecodeError: 'ascii' codec can't decode byte 0x92 in
position 291: ordinal not in range(128)
The list language is English (USA) ('en') which has character set
us-ascii and the posted message contains a non-us-ascii character (hex
92).
Apr 07 22:14:32 2005 (2477) SHUNTING:
1112933669.117754+96c37c2b0a5227c2d9e33ff582f5651df360473d
This error caused the message to be shunted (placed in the shunt
queue). You can run bin/unshunt to reprocess the message, but unless
you change the character set of the list language first, the error
will occur again and the message will be shunted again.
To change the character set to e.g. western european, you can put
add_language('en','English (USA)', 'iso-8859-1')
in mm_cfg.py and then do
bin/mailmanctl restart
followed by
bin/unshunt
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
