Mailman 3 April 2007 - Mailman-Users

script
by felixtp＠webmail.co.za April 23, 2007

April 23, 2007

Hi Can someone help, i need a script to check all user accounts last login against dormancy period and be able to delete users who haven't updated their in 30 days detail then send an email to them. Thank you ------------------------------------------- South Africas premier free email service - www.webmail.co.za ------------------------------------------------------------------ For super low premiums, click here http://www.webmail.co.za/dd.pwm

3 2

Making "Your Name" Mandatory?
by David Devereaux-Weber, P.E. April 23, 2007

April 23, 2007

Is there a way to make "Your Name" a mandatory part of the subscription process? This is a great help to list operators trying to troubleshoot email problems. Dave -- David Devereaux-Weber, P.E. DDW Services <http://ddwsvcs.com> dave(a)ddwsvcs.com (608)576-2599

2 1

Mail problems
by shacky April 23, 2007

April 23, 2007

Hi. I'm trying to install Mailman 2.1.9 on a system running Debian Stable (Etch 4.0) and Qmail+Vpopmail. I installed Mailman with apt-get, I added a new virtual domain ( lists.mydomain.com) in Vpopmail and I configured the web interface. I created a new test list, but if I try to subscribe myself by the web interface I don't receive any confirmation message. The /usr/sbin/sendmail executable is correct and points to the Qmail installation. In the Qmail logs I dont' see anything special, it … [View More]

2 1

Re: [Mailman-Users] [Mailman-i18n] Hebrew Mailman Support
by Dov Zamir April 23, 2007

April 23, 2007

Hi all, I am resending this email, as well as to the other mailing lists, since I have received zero feedback since sending the original over two weeks ago. Should I assume there is no interest in this translation, and just keep it for my own sites? ציטוט Dov Zamir: > ציטוט Barry Warsaw: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> It's probably best to open a patch issue on SourceForge and attach >> your .po file to the … [View More]

2 1

Re: [Mailman-Users] Integrating mailman with joomla/mambo
by David Southwell April 23, 2007

April 23, 2007

On Monday 23 April 2007 06:06:32 David Ravetti wrote: > On Apr 23, 2007, at 06:51 , David Southwell wrote: > > Hi > > > > Has anyone done this? > > If so how successful? > > How about username/password integration? > > It would be really great to have mailman as a joomla/mambo module > > If not does anyone have any ideas how to go about this? > > I am posting a similar question in the joomla forum > > > > David > > -----------… [View More]------------------------------------------- > > Mailman-Users mailing list > > Mailman-Users(a)python.org > > 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/ > > Unsubscribe: http://mail.python.org/mailman/options/mailman-users/ > > david.ravetti%40us.army.mil > > > > Security Policy: http://www.python.org/cgi-bin/faqw-mm.py? > > req=show&file=faq01.027.htp > David, > > We have a site that uses Joomla and also produces a newsletter > through Mailman. There is no integration between the two in the way > that you're thinking of - they're on separate servers in fact - but > from a user perspective it all appears to be a single site. > > They have the newsletter signup form within the Joomla site. They > simply copied the form commands that would be used from within the > Mailman subscription page. The subscription confirmation page was > then customized within Mailman to reflect the site's look and feel > (it could also have been customized to redirect to a page within the > site to keep everything within Joomla). > > Another site has done a similar setup within Moveable Type. > > I wouldn't feel comfortable with doing username/password integration, > at least not with our setup, since Mailman's password system is less > rigorous than Joomla's. It could probably be done with some > customization and proxying if you own the server, but since Mailman > sends passwords in the clear it would reduce the security of the > Joomla site. > > Respectfully, > > David Ravetti > > ---------------------------------------------------------- > Technical Manager, Army Homepage > ---------------------------------------------------------- > Thanks very much for your interesting comment which I have forwarded to the list along with my reply.. I hope you don't mind but I have changed this round to the standard bottom post because top posting tends to confuse. I have received one encouraging reply from Brian on the Joomla Integration forum who says: >>The only thing I have seen is this module for subscribing >>http://forge.joomla.org/sf/frs/do/viewRelease/projects.gesellix/frs.mailman_ >>subscripe.2_4 I think this could provide an interesting basis for building further extension modules. For my part, as I use my own server, I would prefer to shift away from sending passwords in the clear (apart possibly an initial use one time use for mass subscriptions followed by logon verfication). Thanks for your input, it is apprecaited david [View Less]

1 0

Re: [Mailman-Users] Personalization [was: mailman post mail to list error]
by Mark Sapiro April 22, 2007

April 22, 2007

Calvin Muller wrote: >Thank you very much, I did actually manage to get it to work. :) Thanks >again very much. If I am sending out a newsletter to people I create the >HTML newsletter in Outlook and then I send it to mailman(a)hostname.blah it >sends and is archived but how do I add unsubscribe links and personalize the >emails? Set OWNERS_CAN_ENABLE_PERSONALIZATION = Yes in mm_cfg.py. Then go to the admin Non-digest options page and set personalize to Yes or Full as … [View More]

5 7

customizing list info pages!
by Dennis Morgan April 22, 2007

April 22, 2007

Thanks to Mark, we now have a very spiffy looking (well I like it!) Mailman site. For an example see here: http://lists.eaachat.org/mailman/listinfo/nb There is one page left - this one: http://lists.eaachat.org/mailman/listinfo Is there someway to edit that one? BTW - everyone here is very impressed with Mailman's ease and speed. Thanks in advance! Dennis

2 1

Troubles with mailman+postfix
by Andrea S. Gozzi April 21, 2007

April 21, 2007

I'm currently running Postfix with SQL backend for virtual domains. One of the domain owners wants to set up a mailing list and I decided to go with Mailman (great web administration). I installed Mailman and configured it (along with Postfix) following the instructions here: http://workaround.org/moin/PostfixTutorialContributions and everything seems to work. I can create/delete/manage mailing lists but now postfix is unable to delivery any message. Postfix is 'mail.vp44.net' and I added an … [View More]

4 5

Re: [Mailman-Users] Mailman GID problem
by Jeffrey Goldberg April 21, 2007

April 21, 2007

On Apr 20, 2007, at 9:26 PM, Paul Schmehl wrote: > --On April 20, 2007 7:54:45 PM -0500 Jeffrey Goldberg > <jeffrey(a)goldmark.org> wrote: >> So the first fix (modifying the owner of data/aliases{,.db}) is the >> right way to go, but instead of making those files owned by "nobody" >> (which does seem dangerous because than anything running as "nobody" >> could change those file) they should be owned by root with mailman as >> the group and … [View More]permissions like 664. >> > Nobody is an unprivileged user. Thank you. I forgot about that. I was treating "nobody" like "www" or "mail". It entirely slipped my mind that "nobody" really is different. >> it would break to ownership of the aliases file so that we would have >> the mismatch between what the uid postfix gives the the wrapper >> ("mailman") and what the wrapper demands ("nobody"). >> > Nope. I've been running mailman for years now, and it works > perfectly fine. The owner of the data directory is mailman, and > the group is mailman. > ls -lsa /usr/local/mailman/data/ > total 132 > 2 drwxrwsr-x 2 mailman mailman 512 Apr 7 19:47 . > 2 drwxrwsr-x 20 mailman mailman 512 Nov 28 17:48 .. > 48 -rw-r--r-- 1 mailman mailman 65536 Sep 6 2005 .db > 2 -rw-r----- 1 mailman mailman 41 Sep 6 2005 adm.pw > 6 -rw-r--r-- 1 root mailman 4383 Oct 14 2005 aliases > 4 -rw-r----- 1 mailman mailman 3984 Sep 8 2005 aliases.bak > 48 -rw-r----- 1 mailman mailman 49152 May 5 2006 aliases.db > 0 -rw-rw-rw- 1 mailman mailman 0 Sep 9 2005 bounce- > events-00446.pck > 0 -rw-rw-rw- 1 mailman mailman 0 Sep 9 2005 bounce- > events-00449.pck > 0 -rw-rw-rw- 1 mailman mailman 0 Sep 9 2005 bounce- > events-00467.pck > 0 -rw-rw-rw- 1 mailman mailman 0 Jan 27 2006 bounce- > events-00567.pck > 0 -rw-rw-rw- 1 mailman mailman 0 Oct 13 2005 bounce- > events-38840.pck > 2 -rw-r----- 1 mailman mailman 41 Sep 6 2005 creator.pw > 2 -rw-r--r-- 1 root mailman 10 Nov 28 17:48 > last_mailman_version > 2 -rw-rw---- 1 mailman mailman 4 Apr 1 08:31 master- > qrunner.pid > 14 -rw-r--r-- 1 root mailman 14114 Nov 28 17:48 sitelist.cfg I am fairly confident that if that is working for you, than you are not running with /usr/local/mailman/mail/mailman that was compiled with the current port with the postfix option set. The binary mailman has a gid compiled into it. Given the current port WITH_POSTFIX. Installing the current port WITH_POSTFIX will produce a mailman binary which will only allow itself to be run by "nobody". Yours must have "mailman" compiled in where "nobody" is in what I (and David) get. [jeffrey@dobby /usr/local/mailman/mail]$ strings mailman | tail leave post owner request unsubscribe Mailman mail-wrapper nobody Illegal command: %s Usage: %s program [args...] $FreeBSD: src/lib/csu/i386-elf/crtn.S,v 1.6 2005/05/19 07:31:06 dfr Exp $ What is your result on your system? If you get "mailman" where I have "nobody" then one of my earlier suggestions (change MAIL_GID for the postfix setting from "nobody" to "mailman" in the port Makefile) may be the right thing. That is what is most consistent with the mailman install instructions. From /usr/local/share/doc/mailman/mailman-install.txt In section 6.1.1 Integrating Postfix and Mailman * When you configure Mailman, use the --with-mail-gid=mailman switch; However, the current ports Makefile compiles mailman --with-mail- gid=nobody The same section also says Make sure that the owner of the data/aliases and data/aliases.db file is mailman, that the group owner for those files is mailman, or whatever user and group you used in the configure command, and that both files are group writable: % su % chown mailman:mailman data/aliases* % chmod g+w data/aliases* > > It is the *group* that matters to postfix, *not* the owner. Per > the pkg-message file: > Mailman has been installed, but requires further configuration > before use! > > You will have to configure both your MTA (mail server) and web > server to > integrate with Mailman. If the port's documentation has been > installed, > extensive post-installation instructions may be found in: > > %%DOCSDIR%%/FreeBSD-post-install-notes > > Note (1): If you use an alternate (non-Sendmail) MTA, you MUST be > sure > that the correct value of MAIL_GID was used when this port or package > was built. Performing a "make options" in the Mailman port directory > will list required values for various mail servers. > > Note that MAIL_GID is what matters. That is the *group* not the > owner of the files. Note also that the group only has read writes > to the aliases file, although it does have read/write access to the > bounce-events files. However it is the owner of the file containing the pipe alias that matters to postfix local deliveries. See local(8). >> So maybe the problem is with check_perms and not with the port at all >> (well the port would still need to get the aliases files owned by >> root). >> > There's nothing at all wrong with the check_perms script. I am coming to that conclusion. I now think that my second suggestion of changing the ports Makefile to set MAIL_GID to mailman instead of nobody when configuring for postfix is the correct direction to go. > mailman owns the aliases db for mailman: > ls -lsa /usr/local/mailman/data/aliases* > 6 -rw-r--r-- 1 root mailman 4383 Oct 14 2005 /usr/local/ > mailman/data/aliases > 4 -rw-r----- 1 mailman mailman 3984 Sep 8 2005 /usr/local/ > mailman/data/aliases.bak > 48 -rw-r----- 1 mailman mailman 49152 May 5 2006 /usr/local/ > mailman/data/aliases.db > > And this is a working setup of mailman and postfix that's been > running for years. But I don't believe that that set-up will work with the configure options that get passed for compiling mailman with the current port. PORTNAME= mailman DISTVERSION= 2.1.9 PORTREVISION= 1 CATEGORIES?= mail Thus, with a bit more confidence that before I present the same Makefile diff I recommend: --- Makefile.orig Fri Apr 20 14:17:08 2007 +++ Makefile Fri Apr 20 23:57:22 2007 @@ -7,7 +7,7 @@ PORTNAME= mailman DISTVERSION= 2.1.9 -PORTREVISION= 1 +PORTREVISION= 2 CATEGORIES?= mail MASTER_SITES= ${MASTER_SITE_SOURCEFORGE} \ http://www.list.org/ @@ -88,7 +88,7 @@ .if defined(WITH_SENDMAIL) || defined(WITH_EXIM3) || defined(WITH_EXIM4) BROKEN= choose only one MTA integration .endif -MAIL_GID?= nobody +MAIL_GID?= mailman .endif .if defined(WITH_CHINESE) Cheers, -j -- Jeffrey Goldberg http://www.goldmark.org/jeff/ [View Less]

1 0

Re: [Mailman-Users] Mailman GID problem
by Jeffrey Goldberg April 20, 2007

April 20, 2007

On Apr 20, 2007, at 4:31 PM, Paul Schmehl wrote: > --On Friday, April 20, 2007 14:23:14 -0500 Jeffrey Goldberg > <jeffrey(a)goldmark.org> wrote: > >> Can you tell me where to find the unprocessed version of pkg-install? >> What is in work/ has already been processed by sed, and I didn't see >> anything obvious in files/ > /usr/ports/mail/mailman/pkg-install Ah. It was right under my nose. >> I'm beginning to think that the fix will be as simple … [View More]as >> >> --- Makefile.orig Fri Apr 20 14:17:08 2007 >> +++ Makefile Fri Apr 20 14:18:14 2007 >> @@ -88,7 +88,7 @@ >> .if defined(WITH_SENDMAIL) || defined(WITH_EXIM3) || defined >> (WITH_EXIM4) >> BROKEN= choose only one MTA integration >> .endif >> -MAIL_GID?= nobody >> +MAIL_GID?= mailman >> .endif >> .if defined(WITH_CHINESE) >> > No, that's *absolutely* the wrong fix. The group required for > mailman to work depends on the mail server you are using. > Sendmail, postfix, qmail, etc. all require different groups. So > using a fixed group might work for you, but it would break it for a > lot of other people's setups. I think I'm beginning to understand where that "nobody" comes from and why you are right about that. Here is an excerpt from the postfix aliases(5) In the absence of a user context, the local(8) daemon uses the owner rights of the :include: file or alias database. When those files are owned by the superuser, delivery is made with the rights specified with the default_privs configuration parameter. I had been looking at the first half of that (which I was already aware of). So I thought that if the wrapper were compiled to only run as "nobody" than the relevant alias files had to be owned by "nobody". I wasn't, until looking this up, aware of what happens when the aliases file is owned by root. In the postfix out of ports on FreeBSD, default_privs is set to "nobody". So the first fix (modifying the owner of data/aliases{,.db}) is the right way to go, but instead of making those files owned by "nobody" (which does seem dangerous because than anything running as "nobody" could change those file) they should be owned by root with mailman as the group and permissions like 664. Let me just test that now... Yes. Mail delivery seems to work with [jeffrey@dobby /usr/local/mailman/data]$ ls -la . total 78 drwxrwsr-x 2 root mailman 1024 Apr 19 16:03 . drwxrwsr-x 20 mailman mailman 512 Mar 30 13:57 .. -rw-r----- 1 root mailman 41 Sep 11 2006 adm.pw -rw-rw---- 1 root mailman 3523 Mar 31 16:10 aliases -rw-rw-r-- 1 root mailman 16384 Mar 31 16:10 aliases.db -rw-rw-r-- 1 root mailman 12288 Sep 13 2006 aliases.db.rpmsave -rw-r----- 1 root mailman 41 Sep 11 2006 creator.pw -rw-r--r-- 1 root mailman 10 Mar 30 13:57 last_mailman_version -rw-rw---- 1 root mailman 4 Apr 17 14:34 master-qrunner.pid -rw-r--r-- 1 root mailman 14114 Mar 30 13:57 sitelist.cfg -rw-rw---- 1 root mailman 3334 Mar 31 16:10 virtual-mailman -rw-rw-r-- 1 root mailman 16384 Mar 31 16:10 virtual-mailman.db I haven't yet tested list creation, but the permissions look fine to me. All of the relevant files (as well as the data directory itself) are writable by members of the mailman group. But I think I now see the problem $ ../bin/check_perms /usr/local/mailman/data/aliases.db owned by root (must be owned by mailman /usr/local/mailman/data/virtual-mailman.db owned by root (must be owned by mailman Problems found: 2 Re-run as mailman (or root) with -f flag to fix Somehow check_perms doesn't seem to know how postfix does things. If I were to actually run check_perms -f it would break to ownership of the aliases file so that we would have the mismatch between what the uid postfix gives the the wrapper ("mailman") and what the wrapper demands ("nobody"). So maybe the problem is with check_perms and not with the port at all (well the port would still need to get the aliases files owned by root). While setting the aliases files to be owned by "nobody" or by making the wrapper want "mailman" instead of "nobody" would be work-arounds, both of those lose out on the security achieved by having the aliases files owned by root. Of course my two previous "understandings" of how things were supposed to work were wrong. So please take my current analysis with a large grain of salt. And thank you all for your patience in putting up with my half-baked postings. Cheers, -j -- Jeffrey Goldberg http://www.goldmark.org/jeff/ [View Less]

1 0