Mailman 3 June 1999 - Mailman-Users

Permissions problems
by Richard B. Pyne 15 Jun '99

15 Jun '99

Unless the permissions settings are simplified and explained clearly, they are an absolute waste of time and serve only to reduce security. >From reading the past postings on the list, I'm sure I'm not alone in this frustration. Every time I have installed a new update, I have had to spend litterally hours fighting with permissions issues. Several times I have ended up just setting everything to world writable in order to keep the system running. If I fix one part of it, it breaks another. PLEASE if the install scripts can't be made to set permissions and ownership correctly then at least document CLEARLY who needs to own what and what permissions are necessary. ------------------------------ Richard B. Pyne, KB7RMU rpyne(a)kinfolk.org http://pyne.kinfolk.org/rbp2

1 0

Problem with ALIASES
by Usuario para TESTE 15 Jun '99

15 Jun '99

I Having some problem with mailman, i've followed the instructions and installed 1.0rc1, but when i try to send an E-mail to the list i receive: ----------------------------------------------------------------------- ----- The following addresses had permanent fatal errors ----- "|/home/mailman/mail/wrapper mailowner alunos" (expanded from: alunos-admin) ----- Transcript of session follows ----- 554 "|/home/mailman/mail/wrapper mailowner alunos"... unknown mailer error 2 Reporting-MTA: dns; venom.comp.ufscar.br Received-From-MTA: DNS; oxford.comp.ufscar.br Arrival-Date: Mon, 14 Jun 1999 17:52:04 -0400 Final-Recipient: RFC822; alunos-admin(a)venom.comp.ufscar.br X-Actual-Recipient: RFC822; |/home/mailman/mail/wrapper mailowner alunos(a)venom.comp.ufscar.br Action: failed Status: 5.0.0 Last-Attempt-Date: Mon, 14 Jun 1999 17:52:04 -0400 ----------------------------------------------------------------------- any idea ????

2 1

Re: [Mailman-Users] Lack of RFC822 compliant date header
by Matthew Darwin 14 Jun '99

14 Jun '99

>From http://www.ornl.gov/its/archives/mailing-lists/qmail/1997/03/msg00576.html << qmail doesn't munge messages. If the messages arrive over SMTP, they are assumed to be RFC-compliant (if they aren't RFC-compliant, why is the SMTP client sending them??). >> So either mailman needs to deliver locally (via qmail-inject) or generate RFC 822 Date: headers. I also notice that pipermail is broken. My original message is archived in two pieces: http://www.python.org/pipermail/mailman-users/1999-June/001436.html http://www.python.org/pipermail/mailman-users/1999-June/001437.html On Sat, 12 Jun 1999, Dan Busarow wrote: > On Sat, 12 Jun 1999, Matthew Darwin wrote: > > The newlist program generates an e-mail as follows. I notice a lack of a > > "Date: " line in the header: (I'm using qmail 1.03) > > That's qmail's job. MUA's, which list software is a variant of, can > supply date and message-id headers but they don't need to. MTA's > *must* make sure that those headers exist. > > Since we don't run qmail I can't tell you how to get this fixed > but you really should. Missing message-id's cause email to go > to /dev/null here and lots of other places cause it's a great > way to trap spam from the "make your pc a mail server" spam > software. > > Dan > > > ------------------------------------------------------------------- > > > > >From mailman-owner(a)lists.davin.ottawa.on.ca Sat Jun 12 00:32:28 1999 > > Return-Path: <mailman-owner(a)lists.davin.ottawa.on.ca> > > Delivered-To: matthew(a)davin.ottawa.on.ca > > Received: (qmail 3154 invoked by uid 2); 12 Jun 1999 00:30:43 -0400 > > Received: from localhost (HELO HSE-OTT-ppp33376.sympatico.ca) (127.0.0.1) > > by localhost with SMTP; 12 Jun 1999 00:30:43 -0400 > > From: mailman-owner(a)lists.davin.ottawa.on.ca > > Subject: Your new mailing list > > To: matthew(a)davin.ottawa.on.ca > > X-Mailman-Version: 1.0rc1 > > Precedence: bulk > > List-Id: <test.lists.davin.ottawa.on.ca> > > > > The mailing list `test' has just been created for you. The following > > is some basic information about your mailing list. > > > > Your mailing list password is: > > > > test > > > > You need this password to configure your mailing list. You also need > > it to handle administrative requests, such as approving mail if you > > choose to run a moderated list. > > > > You can configure your mailing list at the following web page: > > > > http://lists.davin.ottawa.on.ca/mailman/admin/test > > > > The web page for users of your mailing list is: > > > > http://lists.davin.ottawa.on.ca/mailman/listinfo/test > > > > You can even customize these web pages from the list configuration > > page. However, you do need to know HTML to be able to do this. > > > > There is also an email-based interface for users (not administrators) > > of your list; you can get info about using it by sending a message > > with just the word `help' as subject or in the body, to: > > > > test-request(a)lists.davin.ottawa.on.ca > > > > To unsubscribe a user: from the mailing list 'listinfo' web page, > > click on or enter the user's email address as if you were that user. > > Where that user would put in their password to unsubscribe, put in > > your admin password. You can also use your password to change > > member's options, including digestification, delivery disabling, etc. > > > > Please address all questions to > > mailman-owner(a)lists.davin.ottawa.on.ca. > > > > > > > > ------------------------------------------------------ > > Mailman-Users maillist - Mailman-Users(a)python.org > > http://www.python.org/mailman/listinfo/mailman-users > > > > -- > Dan Busarow 949 443 4172 > Dana Point Communications, Inc. dan(a)dpcsys.com > Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 > > -- Matthew Darwin Westend Family Cinema Community Volunteer The home of great family movies! matthew(a)davin.ottawa.on.ca cinema(a)flora.org http://www.davin.ottawa.on.ca/~matthew/ http://www.flora.org/cinema/

1 0

My mailman-users digests have bad MIME formatting
by Bob Glickstein 14 Jun '99

14 Jun '99

(I've already reported this to the Mailman jitterbug database.) The daily digest of mailman-users messages I receive has broken MIME multipart structure. One of the multipart boundaries is not correctly nested. Here's the structure of yesterday's digest, for example: --132.151.1.90.9001.6311.929163771.576.10662 --132.151.1.90.9001.6311.929163771.576.10662 --132.151.1.90.9001.6311.929163771.576.10662 --__--__-- --__--__-- --__--__-- --__--__-- --__--__-- --__--__-- --__--__-- --__--__-- --__--__-- --__--__-- --132.151.1.90.9001.6311.929163771.576.10662 --__--__---- --132.151.1.90.9001.6311.929163771.576.10662-- Note that the closing "--__--__----" boundary appears outside the subpart in which it's valid. I'm happy to help diagnose or correct this problem in the code, but first I'd like to know whether this is a known problem for which a fix may already exist. Cheers, - Bob

2 1

Re: [Mailman-Users] Get rid of Apparently To?
by J C Lawrence 14 Jun '99

14 Jun '99

On Tue, 1 Jun 1999 20:13:57 -0600 John-David Childs <jdc(a)nterprise.net> wrote: > My boss just sent out a notice to our customer list using mailman > 1.0rc1 and wrote "this new list software sucks" because it > included an "apparently-to:" line for each of our customers in the > header. Your MTA is doing this, not MailMan. -- J C Lawrence Home: claw(a)kanga.nu ---------(*) Linux/IA64 - Work: claw(a)varesearch.com ... Beware of cromagnons wearing chewing gum and palm pilots ...

3 2

Newbie can't get everything to work.
by Tomas Halvarsson 14 Jun '99

14 Jun '99

Good afternoon. I have some problems setting up Mailman on our system. One of the problems is that the mail server is an AIX machine, and the www server is a Linux machine. Installing from the Linux machine _seem_ to work, but... I can't get the locks to work. The www server is running Linux 2.2.9, Apache, and Python 1.5.1 (maybe we will have to upgrade to Python 1.5.2?). The mail server have Python 1.5.2. Anyway, here's what it looks like when I try to create a new list (on the Linux machine): Enter the name of the list: mailman-test Enter the email of the person running the list: psycho(a)acc.umu.se Initial mailman-test password: Traceback (innermost last): File "/home/special/mailman/bin/newlist", line 141, in ? raise SystemExit(main(sys.argv)) File "/home/special/mailman/bin/newlist", line 91, in main newlist.Create(list_name, owner_mail, pw) File "/home/special/mailman/Mailman/MailList.py", line 719, in Create self.Lock() File "/home/special/mailman/Mailman/MailList.py", line 1274, in Lock self._lock_file.lock('w|', 1) File "/usr/lib/python1.5/posixfile.py", line 190, in lock flock = fcntl.fcntl(self._file_.fileno(), cmd, flock) IOError: (37, 'No locks available') Creating the list on the AIX machine works, but then I get errors when trying to do stuff (like subscribing) via www. So the question is: is this a Mailman or a Python problem? I'd guess it's a Linux/Python problem, but I'm not sure. Other Linux users, have you experienced the same problem? If so, how have you fixed them? Thanks in advance. (And if this have already been discussed (although I can't find anything in the archives) I apologize, and would appreciate a pointer to the posts discussing it.) /Tomas

1 0

help with "http://list.scansoft.com/mailman/listinfo" (2nd request) request)
by Joshua S. Freeman 14 Jun '99

14 Jun '99

I am trying, in vain, to find out where I can edit the text template that is used to build this page... any help appreciated. Thanks, J. ----------------------------------------------------- Joshua S. Freeman | jfreeman(a)scansoft.com Internet Program Mgr. | voice: 978.977.2114 ScanSoft, Inc. | fax: 978.977.2412 pager: 6172336422(a)messaging.sprintpcs.com

1 0

Envelope from, sender, from, etc.
by Per Starback 14 Jun '99

14 Jun '99

In 1.0rc1 USE_ENVELOPE_SENDER = 0 by default, but still it didn't work for me. After investigating it turned out that the documentation misled me. I think the documentation or the function should be changed, preferrably the latter. According to the section in NEWS where USE_ENVELOPE_SENDER is added: # With this variable set to true, the envelope sender (e.g. Unix # "From_" header) is used to match addresses, otherwise the From: # header is used. The FAQ also speaks about the difference being between using envelope from and From:. The comments in Defaults.py indicate that this is perhaps not the whole truth as they say # The envelope sender is set by the SMTP delivery and is thus less easily # spoofed than the sender, which is typically just taken from the From: header "Typically" is the key word here. The actual code uses GetSender which prefers to use Sender: but uses From: if there is no Sender:. So my messages which said From: starback(a)ling.uu.se Sender: starback(a)objekt.ling.uu.se where rejected when only "starback(a)ling.uu.se" was a subscriber. Am I missing something here? It seems to me that the point of USE_ENVELOPE_SENDER=0 is that we are willing to accept the lesser security we get when we just accept who the sender says they are and don't insist that the "technical stuff" (envelope from) has to match. Why then refuse because of a Sender: header that probably echoes what was in envelope from? -- Per Starback <starback(a)ling.uu.se> <http://stp.ling.uu.se/~starback/me.html> "Life is but a gamble! Let flipism chart your ramble!"

2 1

Re: [Mailman-Users] Privay options.
by Harald Meland 13 Jun '99

13 Jun '99

[David Sean McNicholl] > hi, > I have a password protected list. I use administrator confirmation > of posts. Last night someone was able to modify my pages to remove this > option. Could they have done this without the password ? Unfortunately, there is a security flaw in all Mailman versions up to and including 1.0rc1. The security flaw has been fixed in CVS, and I'm hoping there will be a new release shortly. > How can I check ? If the security flaw is what's been used to get in, the breakin is neither easily traceable -- as the flaw is due to a misdesign in Mailman's cookie authentication. Your web server access logs might contain some hints. -- Harald

3 2

Re: [Mailman-Users] `Password reminder' message lacks some helpful properties
by Harald Meland 13 Jun '99

13 Jun '99

[Ian Jackson] > Observe the attached bounce message. Unfortunately, I can't easily do > anything about it because the original message doesn't tell me which > list(s) it relates to. Well, it used to -- before the bouncer chopped off the bottom of the original message. > (b) Change the envelope from for these messages to be the listowner > of at least one of the relevant lists. This will probably be feasible with the global member database, planned for post-1.0. -- Harald

1 0