Mailman 3 December 1999 - Mailman-Users

Preventing binaries
by Deirdre Saoirse 21 Dec '99

21 Dec '99

I haven't upgraded from one of the betas to the official 1.1, but I was wondering if anyone had done any patches that allowed one to set whether or not to strip binaries from the list (including vcards and so on). This is fairly common on commercial lists. I am now hosting a pretty large list of spinning fiends and, as the average spinner isn't especially technical, I'd rather NOT see, say, the latest virus going to the list. -- _Deirdre * http://www.linuxcabal.net * http://www.deirdre.net "Mars has been a tough target" -- Peter G. Neumann, Risks Digest Moderator "That's because the Martians keep shooting things down." -- Harlan Rosenthal <Harlan.Rosenthal(a)Dialogic.com>, retorting in Risks Digest 20.60

2 1

Re: [Mailman-Users] Preventing binaries
by Dan Mick 21 Dec '99

21 Dec '99

> Quoting Dan Mick (Dan.Mick(a)West.Sun.COM): > > > I've posted detailed instructions on this before, but I got the original idea > > > from this mailing list before that. > > > > Yup, and if it didn't involve procmail, I'd probably do it too. > > I despise having two tools for the same job, especially when one > > Well, then you probably shouldn't be using Unix - that's the whole Unix > philosphy: use an existing tool for a job it's good at, rather than trying to > reinvent the same functionality. No, no, no, you missed the "same job" part of the sentence. IMO, attachment rejection is just as much a part of mailing-list management as any other function of Mailman. > > of them is a chainsaw with no blade guard or handle. ;) > > You *definitely* shouldn't be using Unix. Yeah, yeah, yeah. Not everything is so user-brutal as Procmail.

1 0

digest error
by Kory Wheatley 21 Dec '99

21 Dec '99

When the cron process for the Send digest runs. I get the following error below. What problem am I having. I recently upgraded to mailman 1.1 and upgraded to python 1.5.2 . The digest has been working fine for a week and all of a sudden I get this error below. Traceback (innermost last): File "/home/mailman/scripts/contact_transport", line 66, in ? Utils.TrySMTPDelivery(to_addrs, from_addr, text, queue_id) File "/home/mailman/Mailman/Utils.py", line 222, in TrySMTPDelivery from Mailman.pythonlib import smtplib ValueError: bad marshal data /home/mailman->Traceback (innermost last): File "/home/mailman/scripts/contact_transport", line 66, in ? Utils.TrySMTPDelivery(to_addrs, from_addr, text, queue_id) File "/home/mailman/Mailman/Utils.py", line 222, in TrySMTPDelivery from Mailman.pythonlib import smtplib ValueError: bad marshal data -- Kory Wheatley Office Phone 236-3874 Computing & Communication Academic Computing Analyst sr. Everything you do must point to him.

2 1

Never mind, fixed it
by Paul Tomblin 21 Dec '99

21 Dec '99

All the archive files belonged to mailman.mailman instead of nobody.mailman. I fixed that and archiving seems to have fixed itself again. -- Paul Tomblin, not speaking for anybody. SETI@Home: Finally a *good* way to impress Jodie Foster http://www.setiathome.ssl.berkeley.edu/

1 0

Mailing lists don't archive any more
by Paul Tomblin 21 Dec '99

21 Dec '99

I had a system crash, and when I restored some of the older files weren't there. I eventually got the mailing lists working again, but it seems the mailing lists don't archive new posts. Old posts are still in the archive, but new ones don't show up. Any suggestions? -- Paul Tomblin, not speaking for anybody. SETI@Home: Finally a *good* way to impress Jodie Foster http://www.setiathome.ssl.berkeley.edu/

1 0

Re: [Mailman-Developers] Bad/Invalid email address
by Marco Budde 20 Dec '99

20 Dec '99

Sean Reifschneider wrote: > I presume if you use "mbudde(a)domain.com", where "domain.com" is your > domain, that it works fine? Yes, that is right. > Mailman is simply being canonical, which > IMHO is better than relying on magic to happen behind the scenes. > For example, if you specified "mbudde", and then later changed the > SMTP server, or moved the mailman installation to another host, the > behavior may change. Well, maybe somebody wants to use your program in an intranet, which does not have a official domain name. I understand your problem with the account name only, but what is wrong with mbudde@ovid. ovid could be a top level domain like com. Does the mailman source support messages/pages in different languages? If you´re interested, I could create German translations of your messages. cu, Marco -- -- Linux HOWTOs: Die besten Lösungen der Linuxgemeinde -- ISBN 3-8266-0498-9 Uni: Budde(a)tu-harburg.de Fido: 2:240/6298.5 Mailbox: mbudde(a)sms.antar.com http://www.tu-harburg.de/~semb2204/ Return-Path: <owner-mailman-users(a)python.org> Delivered-To: mailman-users(a)dinsdale.python.org Received: from python.org (parrot.python.org [132.151.1.90]) by dinsdale.python.org (Postfix) with ESMTP id 0853B1CE6B for <mailman-users(a)dinsdale.python.org>; Tue, 21 Dec 1999 16:45:54 -0500 (EST) Received: from allhats.xcski.com (d185d1cd8.rochester.rr.com [24.93.28.216]) by python.org (8.9.1a/8.9.1) with ESMTP id QAA15085 for <mailman-users(a)python.org>; Tue, 21 Dec 1999 16:45:53 -0500 (EST) Resent-From: ptomblin(a)xcski.com Received: by allhats.xcski.com (Postfix, from userid 406) id ED397AB; Tue, 21 Dec 1999 16:46:32 -0500 (EST) Date: Tue, 21 Dec 1999 16:45:52 -0500 From: Paul Tomblin <ptomblin(a)xcski.com> To: Mailman user account <mailman(a)xcski.com> Message-ID: <19991221164552.A16840(a)xcski.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us Resent-Date: Tue, 21 Dec 1999 16:46:32 -0500 Resent-To: mailman <mailman-users(a)python.org> Resent-Message-Id: <19991221214632.ED397AB(a)allhats.xcski.com> Subject: [Mailman-Users] Can't subscribe from BeOS Sender: mailman-users-admin(a)python.org Errors-To: mailman-users-admin(a)python.org X-BeenThere: mailman-users(a)python.org X-Mailman-Version: 1.2 (experimental) Precedence: bulk List-Id: Mailman mailing list management users <mailman-users.python.org> One of my mailing list users can't subscribe from BeOS using Opera, even though he has no problem using Netscape from Linux or IE from Windows. Here is the message he gets: Bug in Mailman version 1.1 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (innermost last): File "/usr/home/mailman/scripts/driver", line 112, in run_main main() File "/usr/home/mailman/Mailman/Cgi/subscribe.py", line 157, in main if digest: NameError: digest Environment variables: Variable Value DOCUMENT_ROOT /usr/home/httpd/html CONTENT_LENGTH 71 CONTENT_TYPE application/x-www-form-urlencoded PATH_TRANSLATED /usr/home/httpd/html/allhats GATEWAY_INTERFACE CGI/1.1 HTTP_USER_AGENT Mozilla/4.0 (BeOS R4.5;US) Opera 3.60 [en] REMOTE_ADDR 216.39.151.89 SERVER_PORT 80 SCRIPT_FILENAME /usr/home/mailman/cgi-bin/subscribe HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/png, */* REQUEST_URI /mailman/subscribe/allhats PATH /sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin QUERY_STRING SERVER_PROTOCOL HTTP/1.0 PATH_INFO /allhats HTTP_HOST xcski.com REQUEST_METHOD POST SERVER_SIGNATURE SCRIPT_NAME /mailman/subscribe SERVER_ADMIN ptomblin(a)xcski.com SERVER_SOFTWARE Apache/1.3.6 (Unix) (Red Hat/Linux) mod_perl/1.19 PHP/3.0.9 PYTHONPATH /usr/home/mailman HTTP_REFERER http://xcski.com/mailman/listinfo/allhats SERVER_NAME xcski.com REMOTE_PORT 62505 Is this an Opera problem? -- Paul Tomblin, not speaking for anybody. SETI@Home: Finally a *good* way to impress Jodie Foster http://www.setiathome.ssl.berkeley.edu/

1 0

Re: Welcome to the "Mailman-Users" mailing list
by Nico Wimmer 20 Dec '99

20 Dec '99

Hi .. When I send the confirm mail back to jokes-request(a)kurios.dhs.org i get the error: ----- The following addresses had permanent fatal errors ----- "|/home/mailman/mail/wrapper mailcmd jokes" (expanded from: <jokes-request(a)kiddies.dhs.org>) ----- Transcript of session follows ----- sh: wrapper not available for sendmail programs 554 "|/home/mailman/mail/wrapper mailcmd jokes"... Service unavailable in the maillist archive i found many answers (symboliclinks from wrapper to smrsh .. i have this: in /etc/smrsh/ lrwxrwxrwx 1 root root 27 Dec 20 02:14 wrapper -> /home/mailman/mail/wrapper/ sendmail functins without probs ... only wrapper have a error.. i hope anybody can help me.. Cheers, Nico PS: I use Redhat 6.1 on intel and Sendmail 8.9.3

2 2

Re: [Mailman-Users] Announcement lists and Moderated Lists...
by J C Lawrence 20 Dec '99

20 Dec '99

On Mon, 20 Dec 1999 15:29:38 +0800 (CST) Maren S Leizaola <maren(a)leizaola.com> wrote: > On Sun, 19 Dec 1999, J C Lawrence wrote: >> On Mon, 20 Dec 1999 14:32:10 +0800 (CST) Maren S Leizaola >> <maren(a)leizaola.com> wrote: >> 1) You can tell MailMan to deliver via SMTP to your ISP's mail >> server (this is part of the normal configs when you define what >> mail server for MailMan to use) > Can you point me to the right file/parameter where this is > stored. I hope I did not miss it on the web interface. :) You specify this when you build MailMan, or put it in Defaults.py. >> 2) You configure your MTA to use your ISP's mail server as a >> smarthost. MailMan then delivers mail to your local MTA which >> then immediately bounces it to your ISP's mail server for >> delivery. >> >> I would recommend #2. > I thought of this but the problem is that it will spawn each > individaul message and deliver it to the ISP and what I am trying > to avoid is using bandwidth. This is only true with unintelligent MTA's. Exim, as a case in point, will deliver to the smarthostonly as many messages as MailMan delivered to it -- which is typically <num_of_subscribers>/100. I believe, but have not checked, that Postfix behaves similarly. > This does not solve my problem. Actually it does, modulo your choice of MTA. -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

1 0

Re: [Mailman-Users] mailman and exim
by Nigel Metheringham 20 Dec '99

20 Dec '99

prudek(a)nembv.cz said: > 554 Too many hops 27 (25 max): from <prudek(a)nembv.cz> via So the message is looping, and from the log extract you gave its a simple loop where you are passing mail to your smarthost hp-bv.nembv.cz and its passing it back to you for delivery. Thats a simple configuration fault, and the question is *who* should be taking responsibility for finally delivering that address - looks like mailman is not involved at all. prudek(a)nembv.cz said: > Well, I have relay_domains = hp-bv.nembv.cz. > I tried the following: > relay_domains = hp-bv.nembv.cz:127.0.0.1 you should be adding that entry to host_accept_relay (for version 3.00 and above) not relay_domains. Obsolete 2.x versions use a different variable. Running a mail system is not a suck it and see process. Exim is exceptionally well documented, I suggest you read some of that documentation. Finally you could try asking on the exim list, but you will need to post the directors/routers config for people to make sense of it. Exim information, including the (mailman run) mailing list, is at http://www.exim.org/ Nigel. -- [ - Opinions expressed are personal and may not be shared by VData - ] [ Nigel Metheringham Nigel.Metheringham(a)VData.co.uk ] [ Phone: +44 1423 850000 Fax +44 1423 858866 ]

2 1

Re: [Mailman-Users] mailman and exim
by Nigel Metheringham 20 Dec '99

20 Dec '99

As J C Lawrence said there is a lot of logging data from exim - that should certainly let you pin down the problem. Also there is the log data from mailman itself in its logs directory. Your most likely problem is that exim is not set to allow relaying from 127.0.0.1. Nigel. -- [ - Opinions expressed are personal and may not be shared by VData - ] [ Nigel Metheringham Nigel.Metheringham(a)VData.co.uk ] [ Phone: +44 1423 850000 Fax +44 1423 858866 ]

2 1