Wow! I'm impressed. Once past the initial hurdle of the vsnprintf
problem and Solaris 2.5, I had mailman installed and working in less that
an hour. Beautiful!
In case this hasn't been discussed already, I have a suggestion for
handling the mailman aliases.
The INSTALL file says:
- Add aliases for `mailman' and `owner-mailman' to the system's
mail alias database. These aliases should point to whoever is
ultimately responsible for the Mailman installation. Here are
instructions for those running sendmail:
1. su to root.
2. Assuming your email is fred(a)flintstone.com, add the following
lines to the file /etc/aliases:
3. Some versions of sendmail require you to run the program
I did this a little differently:
1) add to /etc/mail/sendmail.cf
2) create the /home/mailman/aliases dbm files
- edit aliases and add mailman and mailman-owner alias entries as above
touch aliases.dir aliases.pag
chown root aliases*
chgrp mailman aliases*
3) run newaliases and restart sendmail
When adding a new list:
/home/mailman/bin/newlist list-name list-admin-address admin-password 1 >>
then you just have to edit the aliases file to remove the extra junk
output by newlist (but this could be suppressed when the immediate flag
is used) and run newaliases.
Todd Pfaff \ Email: pfaff(a)mcmaster.ca
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University \
Hamilton, Ontario, Canada L8S 4M1 \
Mailman has been working great for several months until I made a couple
of changes on the server.
I had been getting tons of mail errors because the hostname was actually
an ALIAS according to DNS, so I changed the hostname to the CNAME and
stopped getting the errors. Around that same time, I upgraded to RedHat
6.0. Somewhere along the line, I started getting this error everytime
anyone tries to post to any of our lists:
----- The following addresses had permanent fatal errors -----
"|/home/mailman/mail/wrapper post be-install"
(expanded from: <be-install(a)techops.rfa.org>)
----- Transcript of session follows -----
sh: wrapper not available for sendmail programs
554 "|/home/mailman/mail/wrapper post be-install"... Service unavailable
Reading between the lines :), it appears that for some reason sendmail
is no longer allowing wrappers. Any ideas?
Lead Technical Engineer
Radio Free Asia
2025 M St. NW Suite 300
I can't seem to add a space after the [listname] prefix, so
things come out like this:
Subject: [listname]foo bar baz
instead of this
Subject: [listname] foo bar baz
Is this an inherent weakness, or what? Adding a space after it
on the admin webpage and it seems to get stripped off again.
: gossamer(a)tertius.net.au http://www.tertius.net.au/~gossamer/
: And then he thought: Is this how idiots rationalize their
: stupidity to themselves? -- Orson Scott Card, Ender's Shadow
Is it possible to subscribe a huge (20000) number of members with
password (migration to mailman) using either mass subscribe on the
web-interface or add_members script ???
PS: Specified password is important.
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com
I just switched our internal lists over to Mailman (yay!!!!) without
making an announcement on the list. The switch went smoothly, once I
figured out how to get the old archives into mbox format!
There are now a lot of messages on the list, however, objecting to the
[listname] prefix taking up "valuable subject line space". I suspect
all of these people are using Microsoft products... anyway, has anyone
else had this experience? Has anyone explicitly commended the use of the
[listname] prefix? I personally like it, and don't want to change
anything. The list has ~500 subscribers, and 5 have so far complained.
I could just ignore them... any thoughts?
I just installed mailman on solaris 2.6 box yesterday and everything till now seems
to be working smoothly. The only problem I have is with the headers, I donot know
if sendmail is doing it or mailman has some influence in it. This box which is running
mailman has a very stripped down version of sendmail.cf which basically tells the
sendmail to masquerade as login(a)dnrc.bell-labs.com instead of login(a)box.dnrc.bell-labs.com
and it sends the mail to one of our mailhosts for routing.
The following is the header generated from one the mail from a list called test123.
>From test123-admin(a)maya.dnrc.bell-labs.com Thu Jul 29 19:07 EDT 1999
Date: Thu, 29 Jul 1999 19:06:40 -0400 (EDT)
From: Bhavnesh Makin <makin(a)dnrc.bell-labs.com>
Subject: [Test123] rrrr
Test123 mailing list - Test123@maya
I wondering if there is a way to change "From" field from test123-admin(a)maya.dnrc.bell-labs.com to
Also how do I change Test123@maya to Test123(a)dnrc.bell-labs.com in the footer.
I have a big problem -- I cann't send mail to list more then 16K size.
We use Mailman-1.0rc2 and ZMailer-2.99.50s11 on FreeBSD-3.2 and error
97634# connection from postman.lipetsk.ru ipcnt 2 ident:
97634w 220 postman.lipetsk.ru ZMailer Server 2.99.50-s11 #1 ESMTP+IDENT
ready at Tue, 27 Jul 1999 14:01:55 +0400
97634# remote from [220.127.116.11]:53516
97634r ehlo postman.lipetsk.ru
97634w 250-postman.lipetsk.ru Hello postman.lipetsk.ru
97634w 250-SIZE 20000000
97634w 250-X-RCPTLIMIT 10000
97634w 250 HELP
97634r mail FROM:<consultant-base-admin(a)lipetsk.ru> size=543124
97634w 250 2.1.0 Sender syntax Ok
97634r rcpt TO:<cons(a)chousing.lipetsk.su> NOTIFY=failure
97634w 250 2.1.5 Ok; can accomodate 543124 byte message
97634r rcpt TO:<root(a)prom.lipetsk.su> NOTIFY=failure
97634w 250 2.1.5 Ok; can accomodate 543124 byte message
97634w 354 Start mail input; end with <CRLF>.<CRLF>
97634- aborted (17459 bytes): SMTP protocol timed out
CU, Victor Gamov
For the record, I did some hunting and came across a page
which contains modified source files for Python which
enable Japanese to be handled nicely by the string and
token handlers. After re-compiling Python 1.52 using the
substitute source files (stringobject.c, compile.c, tokenizer.c)
I found that Python readily accepts Japanese characters.
Upon sending a test message or three to my temporary mailing
lists, I found that Mailman also processes the characters perfectly
I am now a happy camper. ;-)
The page is listed below, though I warn you it is entirely in