? This very message came to me with the following header:
All my bounces come to the list admin address, set in
the admin webpage, in the second field of General Options.
Do you have that set to something, and bounces still come to root?
> 2. Bounces are sent to the poor postmaster instead of a -admin address.
> I'm not entirely certain, but I think an Errors-To: header or something
> like that in all Mailman messages might allow one to distribute that load
I've got a bit of a dilemma that I'd like to get your opinion on. In
MM2.1, I can be more sane about adding headers and footers to messages
that flow through a list, especially when it comes to MIME messages.
Here are the cases I've identified:
1. A message comes in that is either text/plain or has no
Content-Type. In that case, I can just textually prepend any
header and append any footer. This is essentially what MM2.0.x
does for all messages.
2. A message comes in that's multipart/mixed. That's easy too, since
we can just add the header and footers as additional text/plain
3. A message comes in that has some other main Content-Type than
"multipart", e.g. image/gif. This is a little tricker, but what I
think you can do is transform the container message into a
multipart/mixed, add the header and footers as subparts, and create
a new subpart for the original message payload. You'd need to copy
the body of the original message, plus any Content-* headers, into
the subpart, but I think you leave all other headers in the
4. A message comes in that is multipart/* but not multipart/mixed.
What to do here? I suppose we could play the same trick as
#3, but it seems like an awful lot of work and potentially error
prone. Maybe not though. Alternatively, we could add the header
and footer to any existing preamble and epilogue, although they'll
get hidden by most MIME-aware MUAs.
Or we could simply not add headers and footers for #3 and/or #4.
Let's assume for the moment <wink> that MM2.1 will have facilities to
hold, discard, chop apart, etc. MIME messages and that we're talking
about messages that are allowed to go though the list untouched.
Any other suggestions? Any preferences?
This is the error I get when I try to do a ./configure of mailman-2.1a1:
Compiling /home/mailm21/Mailman/versions.py ...
File "bin/update", line 81
print >> sys.stderr, 'Fixing language templates:', mlist.internal_name()
SyntaxError: invalid syntax
File "bin/check_perms", line 96
arg.ERRORS += 1
SyntaxError: invalid syntax
I tried with python 2.0 and python 2.1b1 and same result.
Here is how I made python 2.0:
I installed mimelib 0.2 downloaded over the weekend:
python2.0 setup.py install
And verified the install as per the doc
I tried to install mailman-2.1a1 (downloaded today) with:
./configure --prefix=/home/mailm21 --with-username=mailm21 --with-groupname=mailm21 --with-python=/usr/local/bin/python2.0 --with-mail-gid=daemon
I tried with and without PYTHONPATH=/usr/local/lib/python2.0
I'm on Linux.
Patrick Timmons, service informatique
i think a great feature for mailman would be some indication of how busy a
list on the web page showing all the lists. (e.g. this
e.g. 15 messages a day, or 3 messages a week, or 2 messages a month
(averaged over the past month)
this would listed as a new column between the name of the list and the
i don't know anything about the internals of mailman, but i think it would
be really useful info for people to know.
I am applying the following patch to the debian package of mailman
unless somebody screams loudly. It will close debian bug #59359
( http://www.debian.org/59359 ).
--- bin/digest_arch~ Tue Mar 21 07:26:18 2000
+++ bin/digest_arch Sat Mar 24 01:14:51 2001
@@ -90,7 +90,7 @@
last_dow = days_of_week.index(dow)
if len(year) == 2:
- year = '19' + year
+ year = 1900 + year # some MUAs are stupid
outfile.write("From %s %s %s %s %s %s\n" % (From, dow, mon, day, time, year))
# print "From %s %s %s %s %s %s" % (From, dow, mon, day, time, year)
Tollef Fog Heen
Unix _IS_ user friendly... It's just selective about who its friends are.
Well, never mind. :) I have solved my problem with just about 2 hours work -
For those who are interested on how to fix this problem:
1. Read suggestions at list.org
2. Uninstall sendmail
3. Read instructions for postfix
4. Download and install postfix
5. Migrate virtual hosts
6. Have a restful night.
I have been fighting sendmail for 2 weeks now...and in 2 hours, I'm happy
RTFM for sure....
Hello all -
I have tried to do everything I can think of to fix this one, so I throw it
out to you all...
I have a machine running RH7 and sendmail (default install). I have 2
domain names assoc. with the box:
foo.com and bar.comfoo.com is the hostname I used to setup the box - and there are users with
email accounts on foo.com that can use the system no problem, POP and
locally - all mail is delivered fine, and all headers are correct.
bar.com is a virtual host - the machine responds to it, apache is setup to
listen to it, and sendmail responds just fine as well. I have a list on
bar.com, setup in its own directory, and the list(a)bar.com list delivers
mail to its recipients with no problem.
BUT: list(a)bar.com sends mail that has headers saying the sender is
list-admin(a)foo.com. If an admin request goes thru, the from is
list-request(a)foo.com. If I look into the headers, I see that the sendmail
requests were initiated by mailman (which is correct) but at foo.com, not
at bar.com. I think this may have something to do with those headers
getting written incorrectly.
I had a VERY similar setup on a RH6 system (actually the same box before
the catastrophic HD crash) and it delivered mail with no incorrect headers.
I just can't seem to remember what was different about my setup.
In summation: 2 domains, list mail gets delivered as wrong domain sender -
right user alias, wrong domain.
Thanks in advance.
On Tue, 20 Mar 2001 00:38:35 -0500
Jay R Ashworth <jra(a)baylink.com> wrote:
> On Mon, Mar 19, 2001 at 08:36:26PM -0800, J C Lawrence wrote:
>> > Typical djb mistake.
>> While he reinvented common practice (a definite DJB-ism) he
>> hardly violated any standard -- +-addressing is still mostly
> Really? I've seen it for *years*.
Similarly. Its penetration in terms of actual use has been damned
small to near non-existant up until about 15 months ago however.
Thus, on account of lacking critical mass, I account it larval.
>> Every MTA I'm aware of that supports +-addressing mandates having
>> the extension character set as part of the feature configuration.
> Do that again? I fell off.
1) There are MTAs which either directly or through patch support
what I'll loosely call +-addressing.
2) For each of those MTAs configuring +-addressing requires that you
explicitly define the character to be used in segmenting the
3) None of these MTAs per se has a default +-addressing character
from which the config may specify a deviation. Instead, the
+-addressing character must be explicitly stated as part of the
>> I've seen both '-' and '+' commonly used over tha last decade ro
>> so outside of DJB circles. IIRC the early Sendmail patches for
>> +-addressing used '-' by default until enough people yelled at
>> Eric that it was too confusing and tended to screw up their other
> I see.
>>> Tampa Bay, Florida http://baylink.pitas.com +1 727 804 5015
>> Do Tim et al still do the Weds night/Sunday brunch meets?
> Oh. Hey, Carnage. I wouldn't begin to know. I've seen Tim once
> in the last 6 years, at a SLUG meeting. He saw me, and hasn't
> been going to those meetings since.
I heard rumours for a while (semi-regularly exchange mail with
Wilson and a couple old messages with Beach). I ran into Tim via
email a few years back ('98?) who AIR wrote something quite
ambiguous and then didn't reply further. I haven't been back to FL
since 97 -- am a little curious.
J C Lawrence claw(a)kanga.nu
--=| A man is as sane as he is dangerous to his environment |=--