Re: [Mailman-Users] separate web server
At 15:13 08/02/2002 +0800, you wrote: Hi All, I have two servers that work as http and mail, I already have mailman already working on my mail server and right now its also running apache. How am I going to reconfigure my mailman to run on a different web server and mail server? I have read mailman documentations but there is no detailed explanation on how to do it. Any reference you may give or is there anyone on the list kind enough to give me instruction on how to do it? Mailman's INSTALL document contains a hint as to how to split mail distribution and web GUI on different machines. It has a couple of comments that relate: quote Make sure that you have write permissions to the target installation directory, and permission to create a setgid file in the file system where it resides (NFS and other mounts can be configured to inhibit setgid settings). ... - If you plan on running your MTA and web server on different machines, sharing Mailman installations via NFS, be sure that the clocks on those two machines are synchronized closely. You might take a look at the file Mailman/LockFile.py; the constant CLOCK_SLOP helps the locking mechanism compensate for clock skew in this type of environment. /quote In other words you need to use some file sharing mechanism so that both the mail server and web server can access the Mailman files. At a basic level all you have to do is: 1. ensure both servers can access the mailman install directory using NFS. 2. ensure the uids and gids are common to both systems. 3. get Mailman working on your mail server. 4. ensure the information in the httpd.conf used by the Apache server refers to the mailman file path as it sees it through NFS. 5. adjust as necessary to get it working. Most of this is straight UNIX admin stuff and what you do in detail depends on how your local network is run. For instance: 1. have you already got NFS in use for file sharing on your LAN. 2. are you are using NIS for distributing passwd, group and automount maps. 3. are you using something else for distributing information, LDAP for instance I'm not trying to palm you off but there are so many variations on how networks and sharing/distribution can be set up that a single, simple step-by-step guide is more difficult to write than you might imagine. If you have UNIX guru then I'd discuss the problem with him. Otherwise you will need collect the information about how your network is setup and ask again if you are still having problems doing it yourself . Thank you very much in advance. -- Lito A. Lampitoc Foundation for Communication Initiativesphone:+63(2)8941345 CodeWAN Project http://www.codewan.com.phhttp://www.codewan.com.ph -- Things which matter most must not be in the mercy of things which matter least - Goethe. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Log Files
How can i suppress Alert messages from log files? My logs are getting waaay to big because of an error i know about
Re: [Mailman-Users] HTML formatting in digests
At 12:32 AM -0500 8/2/02 [dmy], you wrote about [Subject] Re: [Mailman-Users] HTML formatting in digests: I think this may have something to do with HTML posts to the lists. I've heard filtering for this will be an option in 2.1. In the interim, www.exim.org (the MTA I'm using w/OpenBSD 2.9) uses Mailman 2.08 and manages to ship decent digests. Maybe they'd be willing to give up the secret... As soon as I get a round-to-it, I'll ask ;) Thanks Delpy. Yes, it is related to users who do not turn off their HTML or RTF or other fancy formatting options. I for one hate and damn the day when somebody thought of adding this feature to e-mail. Unfortunately, it's now common practice on the Internet and we must live with it. As my example demonstrated, even people on this mailing list (inadvertently or not) post their messages in HTML format, and even the Mailman distribution used by [Mailman-Users] doesn't use any of the patches we cannot use (even if we wanted to). As you point out, I too have heard rumours that 2.1 may include this fix. That would indeed be wonderful news we could convey to our many disgruntles members. Does anybody know for sure, is this true or not. Many thanks, marina http://www.soapnaturally.org -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Log Files
What is the error? Is it a Python error/warning, an MTA warning, or one directly from Mailman? When I've had problems like this - mainly warnings about routines being deprecated - I've either upgraded to remove the deprecated routines, or gone into Python's source code and removed the warning statement (then do a make and make install). I really love OpenSource! Jon Carnes === On Friday 08 February 2002 06:08, Joe Mizzi wrote: How can i suppress Alert messages from log files? My logs are getting waaay to big because of an error i know about Content-Type: text/html; charset=iso-8859-1; name=Attachment: 1 Content-Transfer-Encoding: quoted-printable Content-Description: -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] HTML formatting in digests
On Fri, 2002-02-08 at 11:27, marina wrote: At 12:32 AM -0500 8/2/02 [dmy], you wrote about [Subject] Re: [Mailman-Users] HTML formatting in digests: I think this may have something to do with HTML posts to the lists. I've heard filtering for this will be an option in 2.1. In the interim, www.exim.org (the MTA I'm using w/OpenBSD 2.9) uses Mailman 2.08 and manages to ship decent digests. Maybe they'd be willing to give up the secret... As soon as I get a round-to-it, I'll ask ;) We use the patches to coerce postings to plain text on exim.org. See Mailman patch #413752 URL (which will probably break in transit) is:- http://sourceforge.net/tracker/index.php?func=detailaid=413752group_id=103atid=300103 Nigel. -- [ Nigel Metheringham [EMAIL PROTECTED] ] [ Phone: +44 1423 85 Fax +44 1423 858866 ] [ - Comments in this message are my own and not ITO opinion/policy - ] -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Web only
At 06:39 AM 2/7/02 -0500, you wrote: Subject: Re: [Mailman-Users] What do you think of this idea to keep external people from subscribing? Date: Wed, 6 Feb 2002 17:55:20 -0500 Organization: HAHT Commerce Try it, it should work fine. Your users will be stuck using the web, but that's not so bad. The web interface is usable but less desirable for persons with limited/no vision who use a screen reader, so accessibility could be an issue if it is an issue for any of your internal subscribers. -- Lynn Calvin [EMAIL PROTECTED] [EMAIL PROTECTED] (as part of the list management volunteer team). Co-Moderator UU-Community Mailing List -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] /etc/aliases and new lists?
Michael Styer [EMAIL PROTECTED] writes: If so, can anyone explain what I would need to add to /etc/aliases for each list in order to make them function correctly? My MTA ist Postfix. I have added in main.cf , | alias_database = hash:/etc/aliases, hash:/etc/aliases.mailman | alias_maps = hash:/etc/aliases, hash:/etc/aliases.mailman ` and /etc/aliases.mailman is , | -rw-rw-r-- 1 root mailman 11227 Feb 8 15:24 /etc/aliases.mailman ` When i create a new list, i use , | newlist -o /etc/aliases.mailman ... ` This apped the listaliases to the file /etc/aliases.mailman. The last step ist to rebuild the aliases database with the command newaliases. Normaly only root can execute newaliases. But with sudo, mailman also can execute this. ,[ /etc/sudoers ] | mailman mailman=NOPASSWD:/usr/bin/newaliases ` Thats my way. Mit freundlichen Grüßen Detlef Neubauer -- .oO GnuPG Key auf http://www.keyserver.net/ Oo. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Announce only list?
Molly Cliborne [EMAIL PROTECTED] writes: I'm new to Mailman and would like to know if it's possible to create read-only announcement type list using this software. Yes. Privacy Options - Must post be approved by an administrator? [ ] No [X] Yes Mit freundlichen Grüßen Detlef Neubauer -- .oO GnuPG Key auf http://www.keyserver.net/ Oo. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Setting up a 'read-only' list
Proffitt, David [EMAIL PROTECTED] writes: I need to set up an 'announcement' type list I need to guarantee (if this is possible) that *only* the list admin can post Is there a standard way of doing this? I've flagged the list as moderated and restricted access to the admin pages to the local network (in the apache config) Privacy Options Must post be approved ... [ ] No [X] Yes Addresses of members accepted for posting to this list without [EMAIL PROTECTED] implicit approval requirement. Mit freundlichen Grüßen Detlef Neubauer -- .oO GnuPG Key auf http://www.keyserver.net/ Oo. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Behind a firewall help
I can get sendmail to work behind firewall, I can get mailman to work behind firewall, but not them both. It all works fine out from behind it. The part that is not happening behind the firewall is sending the messages to the list members, they are all staying in the qfiles. Any ideas, thanks
[Mailman-Users] digests wouldn'd send
First time I've ever seen this message.. Anyone know what might cause it? -- Forwarded Message -- From: root (Cron Daemon) To: mailman Traceback (innermost last): File /var/www/mailman/cron/senddigests, line 65, in ? main() File /var/www/mailman/cron/senddigests, line 42, in main send_list_digest(mlist) File /var/www/mailman/cron/senddigests, line 46, in send_list_digest mlist.Lock() File /var/www/mailman/Mailman/MailList.py, line 1339, in Lock self.__lock.lock(timeout) File /var/www/mailman/Mailman/LockFile.py, line 224, in lock self.__touch() File /var/www/mailman/Mailman/LockFile.py, line 370, in __touch os.utime(filename or self.__tmpfname, (t, t)) OSError: [Errno 1] Operation not permitted: '/var/www/mailman/locks/camelid.lock.camel.lrllamas.com.3602' --- -- Jay S. Curtis -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] backing up pending administrative requests
I finally have a solution to my fried config.db problem. While I could copy the config.dbs relevant files to another machine make it work, I copying them to a new install on the same machine didn't buy me anything. So the solution is basically: foreach list in old install, make a new list with the new install, feed config_list -o from old install into config_list -i for new install, and copy archives/private/list_name* over. Out of the current ~500 or so lists, I have around 6 that have pending administrative requests. I can get info out of a dump of request.db, but I'm not sure what it means, and what will break if I don't treat them differently from the ones without pending requests. Where is the info mentioned from the request.db kept what do I need to do with it? Since htdig is compiling without too much pain, I also plan to integrate Richard Barrett's mailman-htdig patch into the new install. Any heads ups before I roll this whole thing next weekend? --)) --)) Mark T. Valites Unix Systems Analyst 1 College Circle - 124b1 South Hall SUNY Geneseo Geneseo, NY 14454 716-245-5577 716-259-3471(Cell) -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] backing up pending administrative requests
Out of the current ~500 or so lists, I have around 6 that have pending administrative requests. I can get info out of a dump of request.db, but I'm not sure what it means, and what will break if I don't treat them differently from the ones without pending requests. Where is the info mentioned from the request.db kept what do I need to do with it? You can ignore the pending requests if you like, but you will have to copy a blank one into the new lists (or use the blank one that is already there). The pending requests are either folks wanting to subscribe to the list or messages waiting to be approved. If they are messages waiting to be approved, you will find copies in the old ~mailman/data directory. Read the files in there, and if something is worth passing on, simply drop a note to the sender of the message telling them to re-submit as the mail was not delivered properly. Good Luck with the setup. Jon Carnes -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] having specific email addresses in the To: field
Hi guys. Anybody know if any of the future releases will be able to put the actual email address of the recipient in the To: field instead of just having the lists email address. I don't believe this is possible in the current stable version. Jas -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] removing message headers
No doubt a common newbie question, but is there a way to remove some of the headers from each message sent from my list? I refer to the stuff like this: At 2:33 PM -0500 2/8/02, [EMAIL PROTECTED] wrote: X-No-Archive: yes X-Ack: no Sender: [EMAIL PROTECTED] X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.0.8 (101270) List-Help: mailto:[EMAIL PROTECTED]?subject=help List-Post: mailto:[EMAIL PROTECTED] List-Subscribe: http://mail.python.org/mailman/listinfo/mailman-users, mailto:[EMAIL PROTECTED]?subject=subscribe List-Id: Mailman mailing list management users mailman-users.python.org List-Unsubscribe: http://mail.python.org/mailman/listinfo/mailman-users, mailto:[EMAIL PROTECTED]?subject=unsubscribe List-Archive: http://mail.python.org/pipermail/mailman-users/ I realize some of this may be necessary to proper function (X-BeenThere?) but some is clearly not. -Andrew -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] removing message headers
On Friday 08 February 2002 15:05, Andrew Watson wrote:
No doubt a common newbie question, but is there a way to remove some
of the headers from each message sent from my list? I refer to the
stuff like this:
At 2:33 PM -0500 2/8/02, [EMAIL PROTECTED] wrote:
X-No-Archive: yes
X-Ack: no
Sender: [EMAIL PROTECTED]
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.0.8 (101270)
List-Help: mailto:[EMAIL PROTECTED]?subject=help
List-Post: mailto:[EMAIL PROTECTED]
List-Subscribe: http://mail.python.org/mailman/listinfo/mailman-users,
mailto:[EMAIL PROTECTED]?subject=subscribe
List-Id: Mailman mailing list management users
mailman-users.python.org List-Unsubscribe:
http://mail.python.org/mailman/listinfo/mailman-users,
mailto:[EMAIL PROTECTED]?subject=unsubscribe
List-Archive: http://mail.python.org/pipermail/mailman-users/
I realize some of this may be necessary to proper function
(X-BeenThere?) but some is clearly not.
-Andrew
Its quite easy to do. You edit one file - please backup the file before
you edit it!:
~mailman/Mailman/Handlers/CookHeaders.py
headers = {
'List-Id' : listid,
'List-Help' : 'mailto:%s?subject=help' % requestaddr,
'List-Unsubscribe': subfieldfmt % (listinfo, requestaddr, 'un'),
'List-Subscribe' : subfieldfmt % (listinfo, requestaddr, ''),
'List-Post' : 'mailto:%s' % mlist.GetListEmail(),
}
Feel free to delete any of the lines inside the headers clause, but I
would recommend that you leave 'List-Id'.
BTW: I strongly feel that this should be in the FAQ, even though I fully
agree that the problem is with the Mail client (the MUA) and not with
Mailman.
Jon Carnes
--
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] goodbye_msg problem?
When one of our lists has the following as goodbye_msg, it breaks the unsubscribe message. Some of the headers are inserted _after_ the goodbye message. Any ideas? Running Debian's Mailman 2.0.8 from woody. This is from the list config: goodbye_msg =Goodbye, sorry to see you leave! NOTE: If you have unsubscribed in order to change your e-mail address please go to: http://lists.lcms.org/cgi-bin/mailman/listinfo/this-list and enter your new e-mail address. Thank you And this is what the message looks like: X-From-Line: [EMAIL PROTECTED] Fri Feb 08 14:48:02 2002 Return-path: [EMAIL PROTECTED] Received: from CONVERSION-DAEMON by lcms.org (PMDF V5.2-32 #40908) id [EMAIL PROTECTED] for [EMAIL PROTECTED] (ORCPT rfc822;[EMAIL PROTECTED]); Fri, 8 Feb 2002 14:52:02 CST Received: from rf4.cuis.edu ([66.99.8.16]) by lcms.org (PMDF V5.2-32 #40908) with ESMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED] (ORCPT rfc822;[EMAIL PROTECTED]); Fri, 08 Feb 2002 14:52:01 -0600 (CST) Received: from CONVERSION-DAEMON.crf.cuis.edu by crf.cuis.edu (PMDF V6.1 #40908) id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Fri, 08 Feb 2002 14:51:18 -0600 (CST) Received: from stlux3 (lists.lcms.org [208.167.160.9]) by crf.cuis.edu (PMDF V6.1 #40908) with ESMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Fri, 08 Feb 2002 14:51:17 -0600 (CST) Received: from stlux3 ([127.0.0.1] ident=www-data) by stlux3 with esmtp (Exim 3.33 #1 (Debian)) id 16ZHwA-0001Vy-00for [EMAIL PROTECTED]; Fri, 08 Feb 2002 14:48:02 -0600 Date: Fri, 08 Feb 2002 14:48:02 -0600 From: [EMAIL PROTECTED] Bcc: X-Gnus-Mail-Source: pop:[EMAIL PROTECTED] Message-id: E16ZHwA-0001Vy-00@stlux3 MIME-version: 1.0 Content-type: TEXT/PLAIN Original-recipient: rfc822;[EMAIL PROTECTED] X-Content-Length: 1024 Lines: 23 Xref: sebold.lcms.org LCMS.OIS:2080 Goodbye, sorry to see you leave! NOTE: If you have unsubscribed in order to change your e-mail address please go to: http://lists.lcms.org/cgi-bin/mailman/listinfo/this-list and Subject: Unsubscribed from this-list mailing list From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Ack: no Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: mailto:[EMAIL PROTECTED]?subject=help List-Post: mailto:[EMAIL PROTECTED] List-Subscribe: http://lists.lcms.org/cgi-bin/mailman/listinfo/this-list, mailto:[EMAIL PROTECTED]?subject=subscribe List-Id: For Family Ministry this-list.lists.lcms.org List-Unsubscribe: http://lists.lcms.org/cgi-bin/mailman/listinfo/this-list, mailto:[EMAIL PROTECTED]?subject=unsubscribe enter your new e-mail address. Thank you -- Charles SeboldShabbat Shalom26th of Shevat, 5762 LCMS - Office of Information Systemshttp://unix.ois.org/ *** Opinions expressed herein are not necessarily *** *** those of the Lutheran Church - Missouri Synod *** -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] What do you think of this idea to keep external people from subscribing?
On Wed, Feb 06, 2002 at 05:55:20PM -0500, Jon Carnes wrote: Try it, it should work fine. Your users will be stuck using the web, but that's not so bad. Just for info, that's what I've done at my company for the last 2.5Y :-) I want them to use the authenticated web interface to be *really* sure it's them. Marc -- Microsoft is to operating systems security what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger [EMAIL PROTECTED] for PGP key -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] digests wouldn'd send
On Fri, Feb 08, 2002 at 12:07:38PM -0500, Jay S Curtis wrote: First time I've ever seen this message.. Anyone know what might cause it? -- Forwarded Message -- From: root (Cron Daemon) To: mailman Traceback (innermost last): File /var/www/mailman/cron/senddigests, line 65, in ? main() File /var/www/mailman/cron/senddigests, line 42, in main send_list_digest(mlist) File /var/www/mailman/cron/senddigests, line 46, in send_list_digest mlist.Lock() File /var/www/mailman/Mailman/MailList.py, line 1339, in Lock self.__lock.lock(timeout) File /var/www/mailman/Mailman/LockFile.py, line 224, in lock self.__touch() File /var/www/mailman/Mailman/LockFile.py, line 370, in __touch os.utime(filename or self.__tmpfname, (t, t)) OSError: [Errno 1] Operation not permitted: '/var/www/mailman/locks/camelid.lock.camel.lrllamas.com.3602' 1) Make sure your permissions are right (~mailman/check_perms -f 2) If you run linux with restricted hardlinks and/or grsecurity, check the README.linux file Marc -- Microsoft is to operating systems security what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger [EMAIL PROTECTED] for PGP key -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Enforcing ASCII in a list
I'm switching a 1700-person mailing list from majordomo to mailman. I like mailman a lot, so far, so does the list admin. But there's one thing missing: The ability to differentiate between and filter out HTML/RTF messages and MIME attachments. Our list's policy is: no HTML, no attachments. With majordomo we had long taboo_body and taboo_headers lists containing things like this: /Content-Type: text\/html/ Is there a way with Mailman 2.0.8 to filter out HTML and attachments, per-list? The closest thing I could find to it was this patch, which washes all messages to ASCII text, as far as I can tell. http://sourceforge.net/tracker/?group_id=103atid=300103func=detailaid=413752 Is this patch the only solution? Any caveats that I should know about, WRT the patch? Thanks, Morgan -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Enforcing ASCII in a list
On Fri, 8 Feb 2002, Morgan Fletcher wrote: With majordomo we had long taboo_body and taboo_headers lists containing things like this: /Content-Type: text\/html/ Is there a way with Mailman 2.0.8 to filter out HTML and attachments, per-list? Look at the privacy page (under list admin) for Hold posts with... The closest thing I could find to it was this patch, which washes all messages to ASCII text, as far as I can tell. http://sourceforge.net/tracker/?group_id=103atid=300103func=detailaid=413752 There are also two perl-based solutions that can be installed in front of Mailman or Majordomo. I wrote one of them (http://www.phred.org/~alex/stripmime.html -- it also links to DEMIME, the other option) and have been using it for almost two years on my lists. alex -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Can't Add Lists After Upgrade
I was running Red Hat 7.0, Postfix, and Mailman 2.0.6, and have been running with that setup since 2.0.6 was released. I upgraded the server to Red Hat 7.2, but did not change anything else. After the upgrade, all of the exists lists continued to work. However, I could no longer add new lists. If I issue a /home/mailmain/bin/newlist command, it accepts the new list name, e-mail address, and password, and then hangs while attempting to create the list. After a period of time waiting, if I abort the creation process and check the status, I find that it created the directory for the list under /home/mailman/lists but did not create any files in the directory. I downloaded Mailman 2.0.8 and ran make install. After the install I ran the check_perms and it did not report any errors. All of the existing lists continue to function, including allowing me to access the admin pages with the web browser. But, I still cannot create a new list. Are there other configuration changes I need to make with this install? Thanks! Larry -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
