[Mailman-Users] Re: Apache: allow which dirs?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 22 Sep 2004 11:58:11 -0600 Anthony Chavez [EMAIL PROTECTED] wrote: On Tue, 21 Sep 2004 23:32:25 -0600 Anthony Chavez [EMAIL PROTECTED] wrote: However, Apache 2 still 403s when attempting to access /pipermail/listname/, using either hostname My question at this point is this: what Mailman directories should Apache allow access to? Section 4 of the INSTALL document says to allow access from all for /usr/local/mailman/cgi-bin, but in order to access my public archives I also must enable it for /usr/local/mailman/archives/public. Never did get a response to this. Can anyone point me in the right direction? Naturally, I'd like to only allow access to those parts of Mailman that are *absolutely* necessary to be accessed by subscribers. I'm interested to know if anyone has already distilled these paths before I start experimenting. Thanks! - -- Anthony Chavez http://anthonychavez.org/ mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (Darwin) iD8DBQFBnvQbbZTbIaRBRXERAhooAJ9tSM7En5kewhux/O8s/YL3nqmXbgCeJNIi Ib5qxk75zgLfci8q6xLYjqc= =fPlW -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Re: Apache: allow which dirs?
On Sat, Nov 20, 2004 at 12:36:53AM -0700, Anthony Chavez wrote: On Wed, 22 Sep 2004 11:58:11 -0600 Anthony Chavez [EMAIL PROTECTED] wrote: My question at this point is this: what Mailman directories should Apache allow access to? Section 4 of the INSTALL document says to allow access from all for /usr/local/mailman/cgi-bin, but in order to access my public archives I also must enable it for /usr/local/mailman/archives/public. You will need to allow access to the scripts in /usr/local/mailman/cgi-bin, and the files in the /usr/local/mailman/archives directory tree. (You will also want to allow Apache to follow symbolic links from /usr/local/mailman/archives/public into the private directory.) -- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/ Ringo MUG Tokyo http://www.ringo.net/rss.html -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Help: PTR record and ISP blocking...
At 9:31 PM -0700 2004-11-19, Rodd Ahrenstorff wrote: Should I have my ISP drop the host name portion in my PTR? Could the other ISP be attempting to verify my actual server host name against the existing PTR record before accepting email? Any other suggestions to keep the ISP's on my good side? (.beyond the obvious) Before I can provide any advice, I would need to have more details about precisely what it is that your ISP is complaining about. It may be that they're talking a complete load of bollocks, and that you should simply go get another ISP. Or, they may have legitimate issues which you need to be concerned about. Once we see that, I imagine we might also be able to come up with some additional advice. -- 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 [EMAIL PROTECTED] 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/
RE: [Mailman-Users] Has anyone successfully installed Mailman
On Sat, 20 Nov 2004, Brad Knowles wrote: At 9:45 AM -0800 2004-11-19, Greg Deputy wrote: I didn't see anything in the INSTALL file about that besides having python installed, and being a linux newbie I didn't realize I needed that in addition to the standard python installation. Seems like something the configure script would check for, no? Maybe for the RedHat RPM version, that is something they should do. For the version we provide, we assume that you have a complete installation of a recent version of Python. If you don't have that, you're likely to have problems. If you can show us a cross-platform way to check for all the appropriate and necessary Python headers that would be required by Mailman, and would work regardless of where Python was installed, where Mailman was installed, etc..., I'm sure we'd love to see your patch. The Red Hat RPM versions have the dependencies built into the package. That's what RPM is for. $ rpm -qp --requires mailman-2.1.5-26.src.rpm rpmlib(VersionedDependencies) = 3.0.3-1 python-devel = 2.2 rpmlib(CompressedFileNames) = 3.0.4-1 $ rpm -qp --requires mailman-2.1.5-26.i386.rpm /bin/sh /bin/sh /bin/sh /bin/sh /bin/sh /sbin/chkconfig /sbin/service /usr/bin/env /usr/bin/python config(mailman) = 3:2.1.5-26 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1.3) mktemp python = 2.2 rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 shadow-utils vixie-cron = 4.1-9 webserver So you can't install the precompiled RPM without Python 2.2 runtime support and you can't install the source RPM for rebuilding without the python-devel 2.2 package. If you have enough Python support to build the RPM, you should have enough to build Mailman from scratch. Note that in Red Hat distros, many development tools are split into pkgname for runtime support and pkgname-devel for developers. Greg Deputy probably doesn't have the python-devel RPM, which he needs to build Mailman, although he has the python RPM, which is enough to run Mailman. But I'm not quite clear on why one would want to build Mailman from scratch, when there are perfectly good Mailman RPMs already available for Fedora Core. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
[Mailman-Users] Generic non-members rejection notice
I see this question asked, but haven't seen a reply. Is there any way to change the response message that non-members receive when rejection is the chosen action? I managed to modify my admin gui to allow adding an attribute nonmember_rejection_notice (had to fake a getattr out as well), but I can't seem to make this message appear in rejections. In fact the code in Moderate.py doesn't seem to get used during rejections. I cchecked and it seems as though the .pck does contain the new attribute. What am I missing/doing wrong? -- Robin Becker -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
[Mailman-Users] Unable to get Mailman up and running with qmail/vpopmail
Hi there, I've been trying now for almost 3 days and I am about to give up :-( I tried to install using those tutorials http://nav.bandersnatch.org/clues/qmail-vpopmail-mailman.html and http://www.nerdworks.org/modules.php?name=Contentpa=showpagepid=12 The second link doesn't seem to work today, so I will paste the tutorial at the end of this mail as I kept a local copy. Everything seems to run fine. I am able to create lists, I can sign lists, etc. What doesn't work and this is of course the most important part, is any mail to mailman. Let's say I have a list [EMAIL PROTECTED] and I send an email to this address as a list user, the mail gets stuck in the qmail queue. So I am not even sure if those mails ever reach mailman in order to process the mails? Any help is highly appreciated. Best regards, Alex PS: Below you'll find the tutorial mentioned above.. Whatsoever I used mailman-2-1.5 not 2.1.3! How to set up the Mailman mailing list manager to work with the Qmail MTA http://www.nerdworks.org/modules.php?name=Contentpa=showpagepid=12 How to set up the Mailman (http://mailman.sourceforge.net/) mailing list manager (MLM) to work with the Qmail (http://cr.yp.to/) MTA using vpopmail to handle virtual users, and Apache with dynamically configured mass virtual hosting. The default install-prefix for Mailman is /usr/local. Personally I really don't like to put things that grows in to /usr. You can of course split the installation by using ./configure options. In this HOWTO I change the install-prefix to /var. This document assumes you have already set up a DNS A record for lists.your.domain. It also assumes a fairly good knowledge about using the shell. 1. Mailman requires the mailman user, the mailman group and the mailman install-directory to be present. The following commands will accomplish this. groupadd mailman useradd -d /var/mailman -g mailman mailman cd /var mkdir mailman chown mailman:mailman mailman chmod a+rx mailman chmod g+ws mailman 2. With the user, group and directory in place, we can start working with the sourcecode for Mailman. Download the source from http://mailman.sourceforge.net/ I downloaded it to /usr/src. Untar and enter the Mailman source directory. cd /usr/src tar zxvpf mailman-2.1.3.tgz cd mailman-2.1.3 Read the documentation, but do not take the Qmail part of it too seriously, some of it is dated, and it is a true mess of solutions for different environments. The mailman user is not a virtual user, so mail to Mailman should be delivered as mailman. The cgi-gid is the user that Apache run as. Check in your httpd.conf for the right user. ./configure --prefix=/var/mailman --with-mail-gid=mailman --with-cgi-gid=nobody --with-cgi-ext=.cgi make install cd /var/mailman ./bin/check_perms ./bin/check_perms -f ./bin/check_perms After running check_perms with the -f switch, it should return no problems. Edit /var/mailman/Mailman/Defaults.py At he top of the file set: MailmanHome = /var/mailman; MailmanVar = /var/mailman; MailmanOwner = postmaster; in the Qrunner defaults section DEFAULT_EMAiL_HOST = 'lists.your.domain' DEFAULT_URL_HOST = 'lists.your.domain' 3. This howto assumes you are running Apache with dynamically configured mass virtual hosting. If you are not using dynamically configured mass virtual hosting, just skip this section. Read more about dynamically configured mass virtual hosting at: http://httpd.apache.org/docs/vhosts/mass.html It is areally nice feature. mkdir -p /path/to/domain/lists/htdocs 4. Configuring Apache for Mailman. cp /var/mailman/icons/* /var/www/icons edit /etc/apache/httpd.conf Add the following inside the IfModule mod_alias.c section: ScriptAlias /mailman/ /var/mailman/cgi-bin Directory /var/mailman/cgi-bin/ Options Indexes FollowSymLinks MultiViews AllowOverride None Order allow,deny Allow from all /Directory Alias /pipermail/ /var/mailman/archives/public Directory /var/mailman/archives/public/ Options Indexes FollowSymLinks MultiViews AllowOverride None Order allow,deny Allow from all /Directory 5. Set up the cronjobs neccesary for Mailman. The needed cronjobs are located in /var/mailman/cron/crontab.in Set them up as the user mailman with this command. crontab /var/mailman/cron/crontab.in -u mailman 6. Configuring qmail to handle mail for lists.your.domain Make mailman handle all mail to lists.your.domain by inserting the following line to /var/qmail/control/virtualdomains. lists.your.domain:mailman Put the following line in /var/qmail/control/rcpthosts. lists.your.domain Copy /usr/src/mailman-2.1.3/contrib/qmail-to-mailman.py to /var/mailman/ Edit /var/mailman/.qmail-default and add the following line. |/usr/bin/python /var/mailman/qmail-to-mailman.py 7. Now we can create the Mailman site-wide list. This is the list that password reminders and so on appears to come from. cd /var/mailman ./bin/newlist mailman passwd A fairly good default configuration for the site-wide list is
[Mailman-Users] setting a list for no daily reminders?
I am running a list set to immediately send administrative requests (admin_immed_notify set to yes), but I am getting daily notices as well. I don't want to receive daily notices. The immediate notices are sufficient. Nor do I see the logic in filling my inbox with daily notices when I'm not around or haven't had a chance to process the immediate notices that are already sitting there. Is there any way to change this?? THANX!! -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Unable to get Mailman up and running withqmail/vpopmail
Alexander Schwethelm wrote: What doesn't work and this is of course the most important part, is any mail to mailman. Let's say I have a list [EMAIL PROTECTED] and I send an email to this address as a list user, the mail gets stuck in the qmail queue. So I am not even sure if those mails ever reach mailman in order to process the mails? Have you read the README.QMAIL file that comes with the Mailman source distribution? Also see Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Article 3.14. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
[Mailman-Users] Anywhere for novices?
Is there ANYWHERE a novice can get hand-holding step-by-step tutorials on all this stuff? Python, scripts, configs, mailman, MTAs, what the hell does it all mean? Is there ANYWHERE this is in plain English - where it isn't written as if to be read by people with years of programming experience. I need: you do this... and then you do that... and this is what should happen... etc! Sorry. PeteBell. UK -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
AW: [Mailman-Users] Unable to get Mailman up and running withqmail/vpopmail
Hi Mark, hi List, Yes I've read both sources. What I am wondering about is the issue that mails stay in the qmailqueue. I really believe that until now MailMan didn't have the chance to do anything wrong. I am using the qmail-to-mailman.py file provided by MailMan. Reading e.g. Article 3.14 from the FAQ talks about /etc/aliases, but I don't use this file at all. It seems to me that all the documentation regarding qmail AND vpopmail is totally mixed up, with different solutions for different environments. Does any of this help, to direct me somewhere? Thanks and best regards, Alex -Ursprüngliche Nachricht- Von: Mark Sapiro [mailto:[EMAIL PROTECTED] Gesendet: Samstag, 20. November 2004 18:02 An: DIGITAL FOR YOU - Alexander Schwethelm; [EMAIL PROTECTED] Betreff: Re: [Mailman-Users] Unable to get Mailman up and running withqmail/vpopmail Alexander Schwethelm wrote: What doesn't work and this is of course the most important part, is any mail to mailman. Let's say I have a list [EMAIL PROTECTED] and I send an email to this address as a list user, the mail gets stuck in the qmail queue. So I am not even sure if those mails ever reach mailman in order to process the mails? Have you read the README.QMAIL file that comes with the Mailman source distribution? Also see Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Article 3.14. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] setting a list for no daily reminders?
Mark wrote: I am running a list set to immediately send administrative requests (admin_immed_notify set to yes), but I am getting daily notices as well. I don't want to receive daily notices. The immediate notices are sufficient. Nor do I see the logic in filling my inbox with daily notices when I'm not around or haven't had a chance to process the immediate notices that are already sitting there. Is there any way to change this?? You could delete the checkdbs entry from crontab, but this would affect all lists and also would have the side effect of never clearing stale entries from hold_and_cmd_autoresponses[] (I don't think this is serious because I don't think there is ever more than one entry per user - stale entries get reused). The only other way and the only way to do it per list is to change the code in checkdbs. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
RE: [Mailman-Users] Has anyone successfully installed Mailman
So you can't install the precompiled RPM without Python 2.2 runtime support and you can't install the source RPM for rebuilding without the python-devel 2.2 package. If you have enough Python support to build the RPM, you should have enough to build Mailman from scratch. Note that in Red Hat distros, many development tools are split into pkgname for runtime support and pkgname-devel for developers. Greg Deputy probably doesn't have the python-devel RPM, which he needs to build Mailman, although he has the python RPM, which is enough to run Mailman. But I'm not quite clear on why one would want to build Mailman from scratch, when there are perfectly good Mailman RPMs already available for Fedora Core. Yup, I was missing the python-devel package. Dropped that in and mailman is now built and happy. I'm relatively new to linux, and I've found some things are easier installed as a package and others from source. This is just my personal perception, of course. I generally try to install from source first, I feel like I get more control over how it ends up working that way. Thanks for the help. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Anywhere for novices?
Pete, There may be a web-based tutoral out there, but I found the README and INSTALL text files from the installation the best instruction set available. Some software has very tech oriented instructions, assuming you are an expirienced user, Mailman's instructions are some of the best I have used in open source. If you are fairly comfortable in command line, and can get Mailman downloaded and untarred, you will find the install very straight-forward. Some tips: Take your time. Have both the README and INSTALL files printed or available for reference. Have a browser open to Google for answers for things you may not understand. Use this list when stumped. Best of luck, Jon - Original Message - From: PeteBell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, November 20, 2004 12:23 PM Subject: [Mailman-Users] Anywhere for novices? : Is there ANYWHERE a novice can get hand-holding step-by-step tutorials : on all this stuff? : : Python, scripts, configs, mailman, MTAs, what the hell does it all mean? : : Is there ANYWHERE this is in plain English - where it isn't written as : if to be read by people with years of programming experience. I need: : you do this... and then you do that... and this is what should : happen... etc! : : Sorry. : : PeteBell. UK : : -- : Mailman-Users mailing list : [EMAIL PROTECTED] : 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/ -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
RE: [Mailman-Users] Has anyone successfully installed Mailman
--On Saturday, November 20, 2004 7:11 AM -0500 Matthew Saltzman [EMAIL PROTECTED] wrote: you can't install the source RPM for rebuilding without the python-devel 2.2 package. Quibble: You can't *build* the source RPM without the devel package. You can install it, which basically amounts to unpacking it into spec file, tarball, and patches. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
RE: [Mailman-Users] Has anyone successfully installed Mailman
--On Saturday, November 20, 2004 10:08 AM -0800 greg deputy [EMAIL PROTECTED] wrote: I'm relatively new to linux, and I've found some things are easier installed as a package and others from source. This is just my personal perception, of course. I generally try to install from source first, I feel like I get more control over how it ends up working that way. Building from source and installing from RPM are not mutually exclusive. If you want to maintain the integrity of your packaging database, you should endeavor to locate RPM's, either binary from the distro vendor or source from a third party. You get just as much control installing from a source RPM as you would from a source tarball. Usually that means changing the configure options, and you can easily do that by unpacking the source RPM and editing the configure command in the spec file before rebuilding it. If you use any kind of automatic update system (like yum or up2date) to keep your system secure, manual installation of packages will interfere with that and will likely eventually cause things to break because the packaging system isn't aware of all the packages on the system. Note that this applies not just to RPM but to any package database system. It's there to help you, but you have to keep it informed about what you've installed if it's to make correct decisions. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
RE: [Mailman-Users] Anywhere for novices?
Just to add to Jon's comments. I used two sets of Mailman install manuals. Combined, the instructions were clearer. Another tip is to get the prerequisites going before installing Mailman. Get your mail system working and make sure Python and the C compiler are installed. Pay attention to the ./configure section, this is important to get right. Finally, it is not as hard as it looks :). Best, Robert Toronto -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Krause Sent: Saturday, November 20, 2004 1:11 PM To: [EMAIL PROTECTED]; PeteBell Subject: Re: [Mailman-Users] Anywhere for novices? Pete, There may be a web-based tutoral out there, but I found the README and INSTALL text files from the installation the best instruction set available. Some software has very tech oriented instructions, assuming you are an expirienced user, Mailman's instructions are some of the best I have used in open source. If you are fairly comfortable in command line, and can get Mailman downloaded and untarred, you will find the install very straight-forward. Some tips: Take your time. Have both the README and INSTALL files printed or available for reference. Have a browser open to Google for answers for things you may not understand. Use this list when stumped. Best of luck, Jon - Original Message - From: PeteBell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, November 20, 2004 12:23 PM Subject: [Mailman-Users] Anywhere for novices? : Is there ANYWHERE a novice can get hand-holding step-by-step tutorials : on all this stuff? : : Python, scripts, configs, mailman, MTAs, what the hell does it all mean? : : Is there ANYWHERE this is in plain English - where it isn't written as : if to be read by people with years of programming experience. I need: : you do this... and then you do that... and this is what should : happen... etc! : : Sorry. : : PeteBell. UK : : -- : Mailman-Users mailing list : [EMAIL PROTECTED] : 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/ -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
RE: [Mailman-Users] Has anyone successfully installed Mailman
On Sat, 20 Nov 2004, greg deputy wrote: So you can't install the precompiled RPM without Python 2.2 runtime support and you can't install the source RPM for rebuilding without the python-devel 2.2 package. If you have enough Python support to build the RPM, you should have enough to build Mailman from scratch. Note that in Red Hat distros, many development tools are split into pkgname for runtime support and pkgname-devel for developers. Greg Deputy probably doesn't have the python-devel RPM, which he needs to build Mailman, although he has the python RPM, which is enough to run Mailman. But I'm not quite clear on why one would want to build Mailman from scratch, when there are perfectly good Mailman RPMs already available for Fedora Core. Yup, I was missing the python-devel package. Dropped that in and mailman is now built and happy. I'm relatively new to linux, and I've found some things are easier installed as a package and others from source. This is just my personal perception, of course. I generally try to install from source first, I feel like I get more control over how it ends up working that way. Some people with many years of experience maintain that attitude too, and it's OK. But I've come to believe that for most things, RPMs (or working with whatever packaging system the distro uses--.debs for Debian, etc) are the way to go. For one thing, all the Red Hat/Fedora automated update services rely on it. It records where files are installed so they can be located and/or removed when necessary, and it manages dependency issues such as the one you just ran into. Up2date, Yum, and Synaptic package amnagers even find and install missing dependencies automatically. You can always customize stuff post-install if it's not a feature that needs to be compiled in, and you can always grab the SRPM and rebuild if necessary while reaping all the other benefits. Thanks for the help. You're welcome. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Help: PTR record and ISP blocking...
On 11/19/2004 20:31, Rodd Ahrenstorff [EMAIL PROTECTED] wrote: Could the other ISP be attempting to verify my actual server host name against the existing PTR record before accepting email? Yes, they could be. Forward and reverse lookups really should match. (Whether to reject based on a non-match is a policy issue over which there are endless arguments which don't matter to you...what matters is the end result...a block.) The MTA we use here doesn't log the sending host's name unless, among all the names it gets back from a reverse lookup there is at least one name which contains among its list of IP addresses a match to the actual IP address used. (That's the logging...accept or reject is a matter of policy which is easily configured in that MTA thanks to a variable it makes available. We accept, but allow individual users to block mail from servers with no reverse name at all.) --John -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] setting a list for no daily reminders?
On 11/20/2004 9:30, Mark Sapiro [EMAIL PROTECTED] wrote: Mark wrote: I am running a list set to immediately send administrative requests (admin_immed_notify set to yes), but I am getting daily notices as well. I don't want to receive daily notices. The immediate notices are sufficient. Nor do I see the logic in filling my inbox with daily notices when I'm not around or haven't had a chance to process the immediate notices that are already sitting there. Is there any way to change this?? You could delete the checkdbs entry from crontab, but this would affect all lists and also would have the side effect of never clearing stale entries from hold_and_cmd_autoresponses[] (I don't think this is serious because I don't think there is ever more than one entry per user - stale entries get reused). The only other way and the only way to do it per list is to change the code in checkdbs. The easy thing to do would be to use your mail program's filters to get rid of the daily notices for you. You appear to be using Eudora 6, so the filters are quite capable of doing that. --John -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
[Mailman-Users] Second attempt at posting
Hi there, I tried earlier to post to this list but was bounced for some unknown reason. In installing on Mac OSX 10.3.6, I have encountered the following errors: [server:~mailman/bin] root# ./check_perms -f Traceback (most recent call last): File ./check_perms, line 46, in ? from Mailman import mm_cfg File /usr/local/mailman/Mailman/mm_cfg.py, line 45, in ? add_virtualhost (heard.com.au, heard.com.au) NameError: name 'heard' is not defined The line which begins add_virtualhost is exactly as it appears in mm_cfg.py Could anyone point me in the right direction to try to get this installation up running please. -- Bye for now, Terry Allen ___ hEARd Postal Address: hEARd, 26B Glenning Rd, Glenning Valley, NSW 2261, Australia Internet - WWW: http://heard.com.au http://itavservices.com EMAIL: [EMAIL PROTECTED] Phone: Australia - 02 4388 1400 / International - + 61 2 43881400 Mobile: Australia - 04 28881400 / International - 61 4 28881400 --- Non profit promotion for new music - since 1994 --- -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
[Mailman-Users] Installation problems
Hi all, I have been trying to get Mailman installed have been attempting to post to the users list without success. I have an error installing Mailman after running check_perms -f which is as follows: Traceback (most recent call last): File ./check_perms, line 46, in ? from Mailman import mm_cfg File /usr/local/mailman/Mailman/mm_cfg.py, line 45, in ? add_virtualhost (heard.com.au, heard.com.au) NameError: name 'heard' is not defined I have looked in the FAQ, but nothing relates specifically to that error - I see entries relating to globalname, but not what I have listed. My system details are as follows: Mac OSX 10.3.6 (client version) Python 2.3 Mailman 2.1.5 Postfix 2.1.5 Apache 2.0.50 Can anyone point me in the right directiopn please. -- Bye for now, Terry Allen ___ hEARd Postal Address: hEARd, 26B Glenning Rd, Glenning Valley, NSW 2261, Australia Internet - WWW: http://heard.com.au http://itavservices.com EMAIL: [EMAIL PROTECTED] Phone: Australia - 02 4388 1400 / International - + 61 2 43881400 Mobile: Australia - 04 28881400 / International - 61 4 28881400 --- Non profit promotion for new music - since 1994 --- -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] setting a list for no daily reminders?
At 11:58 AM -0500 2004-11-20, Mark wrote: I am running a list set to immediately send administrative requests (admin_immed_notify set to yes), but I am getting daily notices as well. I don't want to receive daily notices. The immediate notices are sufficient. Hmm. Good question. I know you can turn off the immediate notices and arrange to have only the daily ones, but I don't know if you can go the other way around. Please let me know what you find out. Thanks! -- 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 [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Unable to get Mailman up and running with qmail/vpopmail
At 5:16 PM +0100 2004-11-20, DIGITAL FOR YOU - Alexander Schwethelm wrote: What doesn't work and this is of course the most important part, is any mail to mailman. Let's say I have a list [EMAIL PROTECTED] and I send an email to this address as a list user, the mail gets stuck in the qmail queue. This sounds like a problem with the aliases definitions on the MTA. Personally, I had never heard of either of the URLs you mentioned. With regards to getting Mailman to work with qmail, the best reference I know of is found within the Mailman tarball, in the README.QMAIL file. -- 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 [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Second attempt at posting
Terry Allen wrote:
I tried earlier to post to this list but was bounced for some
unknown reason.
This post and a subsequent one were just approved by the moderator and
delivered to the list. So far there's no sign of the earlier one.
These later two may have been held because you are not a list member
if that is in fact the case.
In installing on Mac OSX 10.3.6, I have encountered the
following errors:
[server:~mailman/bin] root# ./check_perms -f
Traceback (most recent call last):
File ./check_perms, line 46, in ?
from Mailman import mm_cfg
File /usr/local/mailman/Mailman/mm_cfg.py, line 45, in ?
add_virtualhost (heard.com.au, heard.com.au)
NameError: name 'heard' is not defined
The line which begins add_virtualhost is exactly as it
appears in mm_cfg.py
Could anyone point me in the right direction to try to get
this installation up running please.
It should be
add_virtualhost ('heard.com.au', 'heard.com.au')
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
RE: [Mailman-Users] Has anyone successfully installed Mailman
On Sat, 20 Nov 2004, Kenneth Porter wrote: --On Saturday, November 20, 2004 7:11 AM -0500 Matthew Saltzman [EMAIL PROTECTED] wrote: you can't install the source RPM for rebuilding without the python-devel 2.2 package. Quibble: You can't *build* the source RPM without the devel package. You can install it, which basically amounts to unpacking it into spec file, tarball, and patches. Haven't actually tried it, but won't rpm complain about the missing python-devel package when you attempt to install the SRPM? Seems like that would be what dependencies in SRPMs are for. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
RE: [Mailman-Users] Has anyone successfully installed Mailman
--On Saturday, November 20, 2004 9:45 PM -0500 Matthew Saltzman [EMAIL PROTECTED] wrote: Haven't actually tried it, but won't rpm complain about the missing python-devel package when you attempt to install the SRPM? Seems like that would be what dependencies in SRPMs are for. No, build prerequisites are checked at build time, not unpacking time. Note that you can do both with one command, rpmbuild --rebuild xxx.src.rpm. But if you just want to unpack it, use rpm -i xxx.src.rpm and it won't check the build prereqs. You can then unpack the tarball or inspect the spec file and patches and other support files included in the SRPM. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
[Mailman-Users] Email to list rejected
For some reason email to my list is being rejected. I've set up a list with my email address as the only member. When I send email to the list I get: - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 [EMAIL PROTECTED]: Recipient address rejected: User unknown in local recipient table) I'm using: foo:trb $ rpm -aq|grep mailman mailman-2.1.4-83.4 foo:trb $ rpm -aq|grep postfix postfix-2.1.1-1.4 foo:trb $ uname -a Linux foo 2.6.5-7.104-default #1 Wed Jul 28 16:42:13 UTC 2004 i686 i686 i386 GNU/Linux Mailman and postfix were installed via rpm. There are no entries in /etc/postfix/access. Should there be? Where/how is access to sending email to a list managed? How particular is it in regard to address matching? In other words, does every part of an address have to match the address in the list, or does it just look at the user id? The machine is accepting email from the same address when it is sent to a user on the machine, but it is rejected when sent to a Mailman list. I thought this would be in the FAQ, but I can't find it. If you can help me figure this out, I'll add it. -- Tom Barton email: [EMAIL PROTECTED] _ SGI Systems Engineer _| ~~. MCSE, RHCE phone: 972-380-1590 \, _} Dallas fax: 972-692-5194 \( -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Email to list rejected
Tom Barton wrote: For some reason email to my list is being rejected. I've set up a list with my email address as the only member. When I send email to the list I get: - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 [EMAIL PROTECTED]: Recipient address rejected: User unknown in local recipient table) This looks like an alias problem. I'm using: foo:trb $ rpm -aq|grep mailman mailman-2.1.4-83.4 foo:trb $ rpm -aq|grep postfix postfix-2.1.1-1.4 foo:trb $ uname -a Linux foo 2.6.5-7.104-default #1 Wed Jul 28 16:42:13 UTC 2004 i686 i686 i386 GNU/Linux Mailman and postfix were installed via rpm. There are no entries in /etc/postfix/access. Should there be? Where/how is access to sending email to a list managed? How particular is it in regard to address matching? In other words, does every part of an address have to match the address in the list, or does it just look at the user id? It is done through aliases that match the user id and pipe the message to mailman. The machine is accepting email from the same address when it is sent to a user on the machine, but it is rejected when sent to a Mailman list. I thought this would be in the FAQ, but I can't find it. If you can help me figure this out, I'll add it. Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Did you look at FAQ articles 1.7 and 3.14? They both mention aliases. Have you read the INSTALL and README.POSTFIX documents that are in the standard Mailman distribution? Are these or equivalents in your mailman rpm? If you don't have them, you can find them at http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/ -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
