Mailman 3 February 2007 - Mailman-Users

Mailman with sendmail smtp-failure (solved)
by Curt Siffert Feb. 18, 2007

Feb. 18, 2007

Hi, I am setting up Mailman with sendmail and apache2, and when I try to subscribe an address to the list with "send notifications to subscriber" turned on, I never receive the email. logs/smtp says: Feb 18 01:08:17 2007 (77993) <mailman. 0.1171789696.78619.mailman(a)sub.domain.net> smtp to mailman for 1 recips, completed in 0.018 seconds logs/smtp-failure says: Feb 18 01:08:17 2007 (77993) SMTP session failure: 553, 5.3.0 <mailman-bounces(a)sub.domain.net>... User … [View More]

1 0

Problem with archive URL
by Julia Frizzell Feb. 16, 2007

Feb. 16, 2007

My mailman is configured to have as its default_email_host alliance.brown.edu, but the default_url_host to be list.alliance.brown.edu. However, our list information pages list the archive link as alliance.brown.edu instead of the proper list.a.b.e link as it should be. We host other virtual hosts at this site, all of them using list.name and they have no problem with the archive, it's just this one domain. How can we ensure the info pages go to the right URL without manually … [View More]

3 5

Re: [Mailman-Users] Mailman-Users Digest, Vol 36, Issue 24
by Glen Page Feb. 16, 2007

Feb. 16, 2007

Not sure if this is related by I got an odd message from one of my moderators. At least one list subscriber is getting messages but the top half of the messages is gone. This is puzzling as it is not happening to everyone on the list. I do NOT know what client is displaying the partial messages. I do know that the moderator sending the messages is using OS X Mail Client. Moderator has found that adding a few carriage returns to the top of the original post makes it show up fine. … [View More]

2 4

Re: [Mailman-Users] Group mismatch error
by Barry Finkel Feb. 16, 2007

Feb. 16, 2007

Mark Sapiro replied to my posting about group-id mismatches, in part: >>My questions are these: >> >>1) Where is this group test being made? >In the wrapper /usr/lib/mailman/mail/mailman. > >... > >In a 'package' installation, the expected group is determined by what >ever magic the packager has resorted to to avoid having to recompile >the wrapper. I was looking at this wrapper executable and how it is compiled. I needed to determine the "magic" … [View More]involved. I have the "script" output of my installations on Solaris and Ubuntu. I found this Debian/Ubuntu patch 10_wrapper_uid.dpatch that contains, in part, this change to mail-wrapper.c: ===================================================================== --- mailman-2.1.4.orig/src/mail-wrapper.c +++ mailman-2.1.4/src/mail-wrapper.c @@ -74,7 +74,7 @@ fatal(logident, MAIL_ILLEGAL_COMMAND, "Illegal command: %s", argv[1]); - check_caller(logident, parentgroup); + if (getgid() >= 100 && getgid() != 65534) check_caller(logident, LEGAL_PARENT_GROUP); /* If we got here, everything must be OK */ status = run_script(argv[1], argc, argv, env); ===================================================================== The patch contains a similar patch to cgi-wrapper.c . >From the debian/changelog, with the oldest patch first: ------------------------------------------- mailman (1.0b7-1) unstable; urgency=low * Don't check caller gid in mail-wrapper -- Gergely Madarasz <gorgo(a)caesar.elte.hu> Fri, 8 Jan 1999 02:24:00 +0100 ------------------------------------------- mailman (2.0.3-2) unstable; urgency=low * Applied some old patches which had got lost, including allowing the calling of the wrapper scripts if GID == nobody or < 100. (Closes: #36010, #89564, #89848, 89818) -- Tollef Fog Heen <tfheen(a)debian.org> Wed, 14 Mar 2001 13:40:16 +0100 ------------------------------------------- >From the Debian web site: mailman (2.0.3-3) unstable; urgency=low * Mailman has supported having nobody as the CGI user for some time (closes: #36010) - Tollef Fog Heen <tfheen(a)debian.org> Fri, 16 Mar 2001 11:06:44 +0100 ------------------------------------------- There was no additional information on patches #89564, #89848, 89818. The patch appears to be calling check_caller only if the group is over 99 and not 65534, and it is calling that routine with a different parent group. But the mail-wrapper.c code has #define LEGAL_PARENT_GROUP MAIL_GROUP const char* parentgroup = LEGAL_PARENT_GROUP; I have no idea for the reasoning behind "Don't check caller gid in mail-wrapper", nor do I understand the reasoning for the "nobody" and "< 100" GID checks. I do not know if the change to the second parameter of check_caller is significant. When I built my 2.1.9 package, I did not include any of the Debian patches except for one that changes two parameters in Defaults.py.in: IMAGE_LOGOS DEFAULT_URL_PATTERN What I have on my Ubuntu test system in /etc/group is: daemon:x:1: list:x:38: I have to conclude that the straight Ubuntu/Debian package installation was not checking the group-id because the daemon and list groups have ID below 100. When I built and installed the 2.1.9 Ubuntu package without this patch, the Mailman code began checking the group-id and found a mismatch. I would appreciate it if someone would confirm my conclusions. Thanks. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel(a)anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 [View Less]

3 3

Mailman not seeing mails with postfix
by Rauch Christian Feb. 16, 2007

Feb. 16, 2007

Hi List, I am having a problem with mailman/postfix and hope, someone can help me :) I configured Postfix and dovecot with virtual mailboxes and this just works fine. Then I installed and configured mailman, well, the result is, I can send mail _from_ mailman (e.g. invitations from the web interface), but mailman never receives any responses here. But postfix receives and saves them! I saved my output of postconf -n here: http://rauchs-home.de/tmp/postconf.txt and configured mailman as … [View More]

2 2

Best version of Python to use with Mailman 2.1.9?
by vancleef＠lostwells.net Feb. 15, 2007

Feb. 15, 2007

Now that I've got Mailman up and running relatively smoothly in "production" mode, I've taken some time to revisit questions primarily involving Python. The Mailman installation I am running has several non-standard lashups and workarounds that really need some cleanup, and Mark Sapiro has convinced me that using Python resources for that work, plus some extensions, is something I ought to consider seriously. I was aware, when I downloaded the Mailman 2.1.9 sources, that the recommended … [View More]Python is given as 2.4.3. A trip to the Python site showed that 2.4.4 was the latest in that chain, and strongly suggested the current version, 2.5. Since I was under severe time pressure to get my site up and running, I did fairly simple ./configure, make, make test, and make install runs, which produced a usable installation, ending up with the Python 2.5 version. However, I was aware that the Python 2.5 build was not particularly complete, and there were a few regression tests that failed. Accordingly, I've audited the Python build situation for both 2.4.4 and 2.5 on Sun Sparc Solaris 9 and 10, using various versions of gcc and Studio 11 (the Sun Solaris devsys, formerly "Forte"). The situtation turned out to be far worse than I had thought, and turned into something of a porting effort. I'm left with a nagging impression that perhaps I should fall back to Python 2.4.4. I tried to weave my way through the Sourceforge bug tracker to find out whether I was reinventing the wheel and was unable to pull up some bug reports listed in the README's in the Python 2.5 distribution that pertained to problems I was seeing on my builds. Do the Mailman developers have strong feelings about Python 2.4.4 vs. 2.5? Getting both versions of Python to find needed libraries and include files for such things as Tcl/Tk turned out to be a small matter of reworking the distribution setup.py. Once I realized that Makefiles and environment arguments didn't seem to influence the Python modules invoked during the build process, adding the needed code to the Python modules got results. There were also some minor corrections to existing Python code. It leaves me with a strong impression that I'm sailing in uncharted water. I'm a bit dismayed to discover that Python 2.5 includes a ctypes extension with a very GNU-specific libfbbi implementation. The only thing I could find to compile it was a local build of gcc 4.1.1. Other versions of gcc, including the gcc 3.4.3 that is included with the Solaris 10 O/S, failed to build this library properly. My preference is for a build using the Studio 11 devsys. I can live without a working ctypes in 2.5. But considering the basic changes needed to get either 2.4.4 or 2.5 to do something resembling a complete build, I'm concerned about reliability and robustness. Python is a new language to me, and while I'm beginning to get my arms around it, I think that learning it by getting the distribution to build is a strange way to go about this learning. In short, should I fall back to 2.4.4? Hank [View Less]

3 4

Install Issue -- Qmail/Mailman Interaction
by Greg Sims Feb. 15, 2007

Feb. 15, 2007

Hi There, I installed mailman on a system that is running Qmail and virtual domains. The Mailman GUIs from the web and the command line seem to be working correctly. I created a list "testing" and performed a mass subscribe of a single email address -- mine. Membership management from the web shows one person subscribed. This all seems to be working. I sent an email to testing(a)dom.ain which was rejected with the following: <testing(a)dom.ain>: xx.xx.xx.xx does not like … [View More]

2 1

Mailman archive -small problem
by Joe Comeau Feb. 14, 2007

Feb. 14, 2007

I have mailman 2.19 installed with postfix and apache2. Almost everything is perfect except for the archives. I have 3 test list, only one with a couple messages. If you click on the link to go look at the archives for a list, instead of getting the archive list, you get a files listing (ie no index file for apache) of the public folder instead of the public/(list name). If you type in the list name in the url it takes you to the archives and you can browse them. This happens to any of the … [View More]

3 2

Install Issue -- Qmail/Mailman Interaction
by Greg Sims Feb. 14, 2007

Feb. 14, 2007

Hi There, I installed mailman on a system that is running Qmail and virtual domains. The Mailman GUIs from the web and the command line seem to be working correctly. I created a list "testing" and performed a mass subscribe of a single email address -- mine. Membership management from the web shows one person subscribed. This all seems to be working. I sent an email to testing(a)dom.ain which was rejected with the following: <testing(a)dom.ain>: xx.xx.xx.xx does not like … [View More]

1 0

mails stuck in shunt folder
by kamalakannan Feb. 14, 2007

Feb. 14, 2007

I have mailman 2.1.9, some of the mails stuck in shunt folder. these mails are not delivered even after using unshunt command. Below are the errors in mailman log. Feb 14 13:36:46 2007 (1196) SHUNTING: 1171438347.6975739+4557e8bc5545704d99fed8f512cd2de377b05e2e Feb 14 13:36:47 2007 (1196) Uncaught runner exception: unpickling stack underflow Feb 14 13:36:47 2007 (1196) Traceback (most recent call last): File "/list/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop self._onefile(… [View More]

2 1