Mailman 3 November 2002 - Mailman-Users

What to backup
by Brian Read 29 Nov '02

29 Nov '02

Please could someone confirm that if I backup /opt/mailman and all below, then I am backing up the complete mailman installation including the address lists and actual messages? Thanks Brian Brian J Read www.abandonmicrosoft.co.uk www.theonlineorganiser.com www.thepersonalknowledgebase.com Mitel SMEserver Contributions and Howtos: www.abandonmicrosoft.co.uk/abandon/links.html +44 1695 723723

3 2

help with a semi-complex filtering scheme
by douglas repetto 29 Nov '02

29 Nov '02

hi, i'm getting ready to move a largish (~1400 subscribers) from majordomo to mailman. i've been running a bunch of mailman lists for a while now, and they're all fine. but this particular list has a funny setup, and i'm not sure if it can be duplicated under mailman. the list has two modes, regular and digest. however, any mail that is sent to the list with [ot] in the subject line only gets sent to the regular list, and does NOT get added to the digest. i accomplished this in majordomo via lots of headaches and whining and finally a couple of dummy lists that redirect mail hither and thither. i'm hoping that there's some simpler way to do this with mailman, but having looked through the docs and config quite a bit i don't see it. i know that i can just bounce things with [ot] in the subject, but that's not at all what i need... any ideas? thanks, douglas -- ................................................http://artbots.org .....douglas.....irving.........................http://dorkbot.org .................................http://shoko.calarts.edu/musicdsp .......... repetto..............http://music.columbia.edu/organism ................................http://music.columbia.edu/~douglas

1 0

Strings in headers/footers
by Chris 29 Nov '02

29 Nov '02

I see that you can insert the following strings into the headers/footers of outgoing messages: real_name _internal_name host_name web_page_url description But at the bottom of this list, there is a footer that contains the sender's email address in a hyperlink that takes the sender to their options page. What string is used for that? It's not 'email' or 'user_email'... Chris

2 1

headers
by Felix F. 29 Nov '02

29 Nov '02

Hello, Can anyone tell me how to remove the headers Mailman places into a sent out e-mail? I'm specifically talking about headers such as: List-Unsubscribe: <http://domain.com/mailman/listinfo/g_domain.com>, <mailto:G-request@domain.com?subject=unsubscribe> List-Id: <g_domain.com.domain.com> List-Post: <mailto:G@domain.com> List-Help: <mailto:G-request@domain.com?subject=help> List-Subscribe: <http://domain.com/mailman/listinfo/g_domain.com>, <mailto:G-request@domain.com?subject=subscribe> List-Archive: <http://domain.com/pipermail/g_domain.com/>

2 1

how do I uninstall
by David Gordon 29 Nov '02

29 Nov '02

What do I have to do to uninstall Mailman so I can start again with a 'clean' server? I have removed the $prefix directory but the must be something else as I am getting mail to admin >/usr/bin/python: can't open file '/home/mailman/cron/gate_news' Using Mailman 2.0.13 with Sendmail... Thanks -- DG

3 2

Re: [Mailman-Users] how do I uninstall
by David Gordon 29 Nov '02

29 Nov '02

Matthew Davis bigdog(a)dogpound.vnet.net wrote on Fri 29 Nov 2002 at 10:54 -0500 >If the user that you created the mailman program for is still created, Mmmmm. I deleted the user "mailman" and created a new user "mailman" before reinstalling.... ># crontab -u mailman -l Gets the result - "must be privileged to use -u" >check /var/spool/cron if your running vixie-cron. a file for each user >that has a crontab entry will be in that dir. I have an entry for mailman -rw------- 1 root mailman 1218 Nov 29 09:41 mailman which appears to be the current milman user's but I can't read it even as mailman... What I'd really like is a complete list of files to remove so I can start again... __ DG

1 0

Re: [Mailman-Users] how do I uninstall
by David Gordon 29 Nov '02

29 Nov '02

Danny Terweij danny(a)terweij.nl wrote on Fri 29 Nov 2002 at 12:13 +0100 >You must also delete the cronjob's from user mailman. Can you give me a further clue about that? >And cleanup the aliases file. I don't want to do that as I want to try and re-install? -- DG

2 1

mailman & postfix problem
by Rob Hudson 29 Nov '02

29 Nov '02

I recently set up mailman on a debian machine with postfix as the MTA. It appears to be working to a point. I've set up a list via the web interface. When I send a request to the list, postfix receives the mail and sends it to another domain (?). I'll try to include as much information as I can... We're hosting these two domains for our linux group: euglug.org and euglug.com. We're also hosting euglug.net, but only the web pages. Currently, euglug.net mail and it's mailing lists are hosted on another machine, which we'll eventually transfer to euglug.org. I've set up one test list called 'beer'. When I send an email to beer-request(a)euglug.org, the following shows up in my maillogs. Note the euglug.net domain... May 2 21:07:35 tux postfix/smtpd[2261]: connect from cogit8.org[207.189.137.44] May 2 21:07:36 tux postfix/smtpd[2261]: 0621398: client=cogit8.org[207.189.137.44] May 2 21:07:36 tux postfix/cleanup[2262]: 0621398: message-id=<1020398591.6046.2.camel@fuggles> May 2 21:07:36 tux postfix/smtpd[2261]: disconnect from cogit8.org[207.189.137.44] May 2 21:07:36 tux postfix/qmgr[27174]: 0621398: from=<rob(a)euglug.net>, size=698, nrcpt=1 (queue active) May 2 21:07:36 tux postfix/smtp[2264]: 0621398: to=<"|/var/lib/mailman/mail/wrapper mailcmd beer"@euglug.net>, relay=mail.euglug.net[207.189.131.4], delay=0, status=sent (250 ok 1020398444 qp 11289) Here are some various configs: ---------------- postfix virtuals ---------------- # What domains do we accept for: # euglug.org virtual euglug.com virtual # # Mailing Lists: needed here b/c not local users? # # Beer beer(a)euglug.org "|/var/lib/mailman/mail/wrapper post beer" beer-admin(a)euglug.org "|/var/lib/mailman/mail/wrapper mailowner beer" beer-request(a)euglug.org "|/var/lib/mailman/mail/wrapper mailcmd beer" beer-owner(a)euglug.org beer-admin ------------ /etc/aliases ------------ # See man 5 aliases for format postmaster: root mailman: rob(a)euglug.net mailman-owner: mailman I've grepped all the mailman directories I could find as to where the euglug.net domain is coming from, but can't find any reference to it. Any help is appreciated. And any config tips are appreciated also. Thanks, Rob

2 1

Qrunner problems - new edition
by fish 28 Nov '02

28 Nov '02

Well, I fixed (with Richard's help) the problem with the qrunner authentication, but now that it is authenticating, I am receiving multitudes of messages from my CronDaemon which I have included one such below. In reading the archives, the only suggestions that I have found is to try running check_perms from the mailman/bin directory as root, but this reports no problems found. Are there any other suggestions about how to fix this problem that I might have missed? Again, I am using Mailman, Exim, Debian, Apache Robert Lydiate icon(a)accesscomm.ca > -----Original Message----- > From: CronDaemon [mailto:mailman@livingsky.net]On Behalf Of Cron Daemon > Sent: Thursday, November 28, 2002 10:45 PM > To: mailman(a)livingsky.net > Subject: Cron <mailman@fish> /usr/bin/python -S > /usr/lib/mailman/cron/gate_news > > > Traceback (most recent call last): > File "/usr/lib/mailman/cron/gate_news", line 222, in ? > main() > File "/usr/lib/mailman/cron/gate_news", line 198, in main > lock.lock(timeout=0.5) > File "/usr/lib/mailman/Mailman/LockFile.py", line 219, in lock > self.__write() > File "/usr/lib/mailman/Mailman/LockFile.py", line 350, in __write > fp = open(self.__tmpfname, 'w') > IOError: [Errno 13] Permission denied: > '/usr/lib/mailman/locks/gate_news.lock.fish.13366'

1 0

2.1b5 make syntax error?
by j2 28 Nov '02

28 Nov '02

See end of enclosed dump for details.. Hints please? [root@waldorf mailman-2.1b5]# ./configure --prefix=/home/mailman --with-username=exim --with-groupname=exi m --with-mail-gid=501 creating cache ./config.cache checking for --with-python... no checking for python... /usr/bin/python checking Python interpreter... /usr/bin/python checking Python version... 2.2a1 checking that Python has distutils... yes checking for a BSD compatible install... /usr/bin/install -c checking whether make sets ${MAKE}... yes checking for true... /bin/true checking for --without-gcc... no checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking whether #! works in shell scripts... yes checking for --with-var-prefix... no checking for --with-permcheck... yes checking for --with-username... exim checking for user name "exim"... okay checking for --with-groupname... exim checking for group name "exim"... okay checking permissions on /home/mailman... okay checking for mail wrapper group; i.e. --with-mail-gid... exim checking for CGI wrapper group; i.e. --with-cgi-gid... nobody checking for CGI extensions... no checking for --with-mailhost... no checking for --with-urlhost... no checking for default mail host name... www.skyddsrummet.net checking for default URL host component... www.skyddsrummet.net checking for strerror... yes checking for setregid... yes checking for syslog... yes checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for syslog.h... yes checking for uid_t in sys/types.h... yes checking type of array argument to getgroups... gid_t checking for vsnprintf... yes updating cache ./config.cache creating ./config.status creating misc/paths.py creating Mailman/Defaults.py creating Mailman/mm_cfg.py.dist creating src/Makefile creating misc/Makefile creating bin/Makefile creating Mailman/Makefile creating Mailman/Cgi/Makefile creating Mailman/Logging/Makefile creating Mailman/Archiver/Makefile creating Mailman/Commands/Makefile creating Mailman/Handlers/Makefile creating Mailman/Bouncers/Makefile creating Mailman/Queue/Makefile creating Mailman/MTA/Makefile creating Mailman/Gui/Makefile creating templates/Makefile creating cron/Makefile creating scripts/Makefile creating messages/Makefile creating cron/crontab.in creating misc/mailman creating Makefile creating tests/Makefile creating tests/bounces/Makefile creating tests/msgs/Makefile creating build/bin/add_members creating build/bin/arch creating build/bin/change_pw creating build/bin/check_db creating build/bin/check_perms creating build/bin/cleanarch creating build/bin/clone_member creating build/bin/config_list creating build/bin/convert.py creating build/bin/dumpdb creating build/bin/find_member creating build/bin/fix_url.py creating build/bin/genaliases creating build/bin/inject creating build/bin/list_admins creating build/bin/list_lists creating build/bin/list_members creating build/bin/mailmanctl creating build/bin/mmsitepass creating build/bin/newlist creating build/bin/pygettext.py creating build/bin/qrunner creating build/bin/remove_members creating build/bin/rmlist creating build/bin/sync_members creating build/bin/transcheck creating build/bin/unshunt creating build/bin/update creating build/bin/version creating build/bin/withlist creating build/bin/b4b5-archfix creating build/contrib/check_perms_grsecurity.py creating build/contrib/qmail-to-mailman.py creating build/contrib/rotatelogs.py creating build/cron/bumpdigests creating build/cron/checkdbs creating build/cron/disabled creating build/cron/gate_news creating build/cron/mailpasswds creating build/cron/nightly_gzip creating build/cron/senddigests [root@waldorf mailman-2.1b5]# make install Creating architecture independent directories... chmod o-r /home/mailman/archives/private Creating architecture dependent directories... make[1]: Entering directory `/home/root/download/mailman/mailman-2.1b5/bin' for f in mmsitepass newlist rmlist add_members list_members remove_members clone_member update arch sync_members check_db withlist check_perms find_member version config_list list_lists dumpdb cleanarch list_admins genaliases change_pw mailmanctl qrunner inject unshunt fix_url.py convert.py transcheck b4b5-archfix; \ do \ /usr/bin/install -c -m 755 ../build/bin/$f /home/mailman/bin; \ done make[1]: Leaving directory `/home/root/download/mailman/mailman-2.1b5/bin' make[1]: Entering directory `/home/root/download/mailman/mailman-2.1b5/cron' for f in crontab.in; \ do \ /usr/bin/install -c -m 644 $f /home/mailman/cron; \ done for f in checkdbs mailpasswds senddigests gate_news nightly_gzip bumpdigests disabled; \ do \ /usr/bin/install -c -m 755 ../build/cron/$f /home/mailman/cron; \ done make[1]: Leaving directory `/home/root/download/mailman/mailman-2.1b5/cron' make[1]: Entering directory `/home/root/download/mailman/mailman-2.1b5/misc' /usr/bin/install -c -m 644 *.jpg *.png /home/mailman/icons for d in bin cron scripts; \ do \ dir=/home/mailman/$d; \ /usr/bin/install -c -m 644 paths.py $dir; \ done /usr/bin/install -c -m 755 mailman /home/mailman/scripts for p in email-2.4.3 JapaneseCodecs-1.4.9 KoreanCodecs-2.0.5; \ do \ gunzip -c $p.tar.gz | tar xf -; \ (cd $p ; umask 02 ; PYTHONPATH=/home/mailman/pythonlib /usr/bin/python setup.py --quiet install --install-lib /home/mailman/pythonlib --install-purelib /home/mailman/pythonlib --install-data /home/mailman/pythonlib); \ done File "/home/mailman/pythonlib/email/_compat22.py", line 31 return i // j ^ SyntaxError: invalid syntax --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.422 / Virus Database: 237 - Release Date: 2002-11-25

2 1

Mailman-Users November 2002