Mailman 3 December 1999 - Mailman-Users

Re: [Mailman-Users] Question Regarding admindb
by claw＠kanga.nu Dec. 1, 1999

Dec. 1, 1999

On Wed, 01 Dec 1999 16:37:51 +1100 Gonzalo Servat <speedy(a)WebBios.com.au> wrote: > It would be quite easy for anyone to send spam to the list, then > guess the URL of the approval page (since its usually > www.domain.com/admindb/<listname> and approve it themselves since > no password is required. A password is required unless you already have a cookie from a previous authentication (which hasn't timed out yet). -- 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 |=--

2 1

Cron <mailman@saturn> /usr/bin/python /home/mailman/cron/nightly_gzip (fwd)
by Pete Holsberg Dec. 1, 1999

Dec. 1, 1999

Huh? What do I do about these messages? Do they occur because "make update" failed with Updating mailing list: et124 Traceback (innermost last): File "bin/update", line 214, in ? dolist(list) File "bin/update", line 22, in dolist l = MailList(list) File "/home/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 810, in Load raise Errors.MMBadListError, 'Failed to access config info' MMBadListError: Failed to access config info Thanks, Pete ---------- Forwarded message ---------- Date: Wed, 1 Dec 1999 03:27:04 -0500 From: Cron Daemon <root(a)saturn.mccc.edu> To: mailman(a)listserv.mccc.edu Subject: Cron <mailman@saturn> /usr/bin/python /home/mailman/cron/nightly_gzip List et124 has a bogus archive_directory: /home/mailman/archives/private/et124 List hiltonia has a bogus archive_directory: /home/mailman/archives/private/hiltonia List mcp has a bogus archive_directory: /home/mailman/archives/private/mcp List njccasst has a bogus archive_directory: /home/mailman/archives/private/njccasst List njccpres has a bogus archive_directory: /home/mailman/archives/private/njccpres List epo has a bogus archive_directory: /home/mailman/archives/private/epo List aoagene has a bogus archive_directory: /home/mailman/archives/private/aoagene List eli97 has a bogus archive_directory: /home/mailman/archives/private/eli97 List njcfs has a bogus archive_directory: /home/mailman/archives/private/njcfs List aoadl has a bogus archive_directory: /home/mailman/archives/private/aoadl List vision has a bogus archive_directory: /home/mailman/archives/private/vision List jpc has a bogus archive_directory: /home/mailman/archives/private/jpc List tvc has a bogus archive_directory: /home/mailman/archives/private/tvc List account-list has a bogus archive_directory: /home/mailman/archives/private/account-list List nynjpaeta has a bogus archive_directory: /home/mailman/archives/private/nynjpaeta

1 0

backup mailman machine
by Kory Wheatley Dec. 1, 1999

Dec. 1, 1999

Most of you probably backup up your Mailman machine and save the archive on tape or on some other related machine. What I have attempted to do is create two mailman machines, identical hardware and software with the same lists on both keeping them in sync. When one goes down I can use the other, of course both machine have a different host name, but I use a CNAME (configured in the bind tables) to keep the same address for users to use their mailing list without having to switch to a different SMTP Host Name if the primary Mailman machine goes down. Only problem when I send out messages to the lists, the To: header field always displays the SMTP host name not the CNAME when the message is received. I have tryed using Masqurading rules in Red Hat 6.0 Sendmail configuration, but it does not work, which is below. Has everyone tried this sort of thing, or does anyone know a solution to this problem? Why my masquerade rules will not work? # Masquerading rules S1 R$*<@mm1.isu.edu> $@ $1 < @ maillist.isu.edu> R$*<@mm1.isu.edu.> $@ $1 < @ maillist.isu.edu.> -- Kory Wheatley Office Phone 236-3874 Computing & Communication Academic Computing Analyst sr. Everything you do must point to him.

1 0

Re: [Mailman-Users] Mailer
by Richard Ellerbrock Dec. 1, 1999

Dec. 1, 1999

>On Tue, 30 Nov 1999 15:45:45 -0700 >Kory Wheatley <wheakory(a)isu.edu> wrote: > >> What is the best Mailer agent to use with Mailman. Right now I am >> using sendmail and it seems to be fine. > >Sendmail works, but does not perform well. It is a very >(unnecessarily) complex piece of software which has a long history >of security problem which encourage me to avoid it. Other possible >choices for an MTA enclude Exim, Postfix, and QMail. I have been lurking and listening to this advocacy debate for a while now and have stayed clear of the debate up till now. Just some hard facts to set the record straight: I run around 150000 e-mail messages a day through a single mail spool machine. This machine is configured with 3 virtual interfaces (each running a different configuration). I handle around 15 domains on this machine. Spam filters and blackhole lists are configured to the max. At any one time there are around 300 mail processes on this machine with the machine never going under 95% idle! Another machine (P133!) handles all my mailing lists on mailman. This machine has around 30 lists, with around 10 with over 3000 members each. Many of the lists are automagically generated each evening using sync_members from our HR database system. I have never had a performance problem or a security violation in the last 5 years this setup has been running. It also never falls over and never needs maintenance. BTW, it is all running on sendmail 8.9.3 I have looked at the other offerings and have not found any other mailer that even comes close to what sendmail can do for you. My suggestion to those that moan about complexity is to stay away from UNIX and go to NT. Also, it must be noted that every UNIX that I have ever worked with comes standard with sendmail, so you are bound to discover security problems if 90% of the mailers run your software. The others are just lucky as their mailers only have a small number of users compared to sendmail. My 2c worth, and no mail will be answered. Thanks. -- Richard Ellerbrock richarde(a)eskom.co.za

1 0

Re: [Mailman-Users] editing the html
by RC Compaan Dec. 1, 1999

Dec. 1, 1999

This is a bit problematic if you want a Enlish and a translated list on the same server. If <MM-variable-name> holds essential mailman functionality and you translate these <MM-..> tags in the source this will reflect on all lists. Shouldn't one make these tags more list specific? Roché Compaan > Message: 3 > Date: Mon, 29 Nov 1999 12:34:03 -0800 > To: Mailman-Users(a)python.org > From: Michael Sweeney <sweeney(a)projectcool.com> > Subject: Re: [Mailman-Users] editing the html > du> > > Depends on what modifications you want to make. The basic template files > are in the MAILMAN-DIR/templates directory if you want to change the > interface pages for all new lists. You can edit them and use the > <MM-variable-name> tags that will keep the essential mailman > functionality. > For existing lists, or changes specific to a particular list, you can use > the "Edit the HTML for the public list pages" link from the admin pages. > > If you are wanting to change the content and/or formatting of what is > expanded from the <MM-...> tags, you have to get into the Python source > code. Depending on which tag you want to change, you have to look through > the source to find the specific tag. But remember that if you change the > sources, the changes are likely to be lost on upgrade or re-installation. > > Michael > >

1 0