? 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
Last night I had to change all subscribers to one of my lists to a digest
version. I used bin/withlist -l in interactive mode and gave the following
all = m.GetMembers()
for member in all:
m.SetUserDigest(member, 1, force=1)
This took a really long time (1635 regular subscribers) and after about 20
minutes I decided to press Ctrl-C cause I was afraid it hung somewhow...
this means I wasn't able to do a m.Save() but after checking the number of
subscriber was reduced to about 60 so appearantly it did work out...
After that I decided to rerun the commands again and this time I waited
untill it was finished and did a m.Save()
Anyway my point is that now I'm getting some complaints from members about
receiving empty digests (it only says the number of posts which should be in
there) I'm not sure yet what they are missing but I was wondering if I
could have messed things about by interrupting the process w/o a m.Save()?
When I look up the subscription options for one of the members who
complained I don't see anything weird in there...
We have been running Mailman on Windows for about two weeks now and most
things seem to work very well.
To make it run I had to make some changes - all of them minor - and most of
them related to opening files ('b').
Mailmanwin (as I have named it) is probably not useful for anyone but me
(and my company) right now; some things do not work at all (web interface,
e-mail archive, usenet gateway, all the bin scripts) and some things are
changed to make them better fit my needs.
I have made an "install" script doing all the work and describing all the
changes, so it's fairly easy getting started.
I hope to get a webpage up with these things soon.
I don't expect the mailman developers to take account of any of these changes.
I fully understand and respect that this is a Linux project and would hate
if cross platform issues in any way affected the future direction of Mailman.
Having said that, it would be nice if no module names conflicted with
modules in the standard Python distribution (mailbox) ;)
On to the questions.
1. Delivering messages to scripts/post
I could not find any MTA for Windows (I didn't look much, though) that was
able to get the toaddr and deliver the message to scripts/post.
Instead we are using L-soft LSMTP (we used L-soft LISTSERV before changing
LSMTP is told to save all messages (complete with all envelope header
information) and I have made a Python script that parses each message and
calls Enqueu with the correct parameters.
This works well, except that we have had a couple of mail loops because of
auto-responders replying directly to the list.
So my question is, what information does a MTA look for before passing the
message to post?
I found out that filtering out all messages with daemon and/or postmaster
in the fromaddr is a good idea.
Are there any other "keywords" that i should know of?
2. Empty envelope fromaddr
In some messages the envelope fromaddr is empty.
Is it safe to never deliver a message with an empty envelope fromaddr to a
3. Using the envelope fromaddr or the message fromaddr
I can see that this is a Mailman setting.
What are the consequences of using only the envelope fromaddr?
Just for the record.
L-soft LISTSERV is a great product - the most solid/stable I have ever used.
We chaned to Mailman because we needed some things LISTSERV didn't have.
All the best,
On Tue, 01 May 2001 00:54:39 +0200
Jesper Jensen <jj-list(a)mail.dk> wrote:
> I fully understand and respect that this is a Linux project...
Actually its a GNU project, which is not at all Linux specific.
Mailman in its current incarnation is Unix-centric in a number of
ways (which subtley different from Linux-centric), but that is
mainly due to the majority of the developers (and thus the users)
having Unix as their preferred (server) platform.
> We chaned to Mailman because we needed some things LISTSERV didn't
Like what? (might as well pump up our strengths)
J C Lawrence claw(a)kanga.nu
--=| A man is as sane as he is dangerous to his environment |=--
Bill Bumgarner <bbum(a)CODEFAB.COM> writes:
> This appears to be a fairly common problem; I suspect that
> MailMan is using a header to set the date and some folks have
> their client set to preposterous dates. See:
That's why under "archival options" you'll find:
"Set date in archive to when the mail is claimed to have been
sent, or to the time we resend it?"
If you leave it on 'when sent', you deserve the mess you'll get
in your archives.
I've finally moved mimelib development to SourceForge, and uploaded
mimelib is yet another MIME and RFC 2822 <wink> message handling
library for Python. It differs from older modules and packages by
providing an abstract MIME object model separate from parsing and
generating the plain text representations. There is a parser class to
convert from plain text to the model, and a generator class to output
plain text from the model. Along the way, the object model can be
manipulated in very Pythonic ways (or you can generate an entire model
from scratch using the provided message classes).
mimelib is compatible with Python 2.x. My goal is to solidify the API
and implementation enough for inclusion of mimelib in Python 2.2.
mimelib 0.3 is required for the current CVS snapshot of Mailman 2.1
For online documentation, see
For project information, see
For downloading mimelib-0.3.tar.gz, see
And of course, there's a mailing list for developers
This appears to be a fairly common problem; I suspect that MailMan is
using a header to set the date and some folks have their client set to
preposterous dates. See:
The above is from a mailing list managed with 2.0b3.
On Monday, April 30, 2001, at 12:02 PM, mailman-developers-
> Date: Sun, 29 Apr 2001 19:12:29 +0000 (GMT)
> From: Ousmane Wilane <wilane(a)MINT.SN>
> To: <mailman-developers(a)python.org>
> Subject: [Mailman-Developers] 2006 archives already online!
> Take a look at the Mailman-dev archives page, we have a 2006-April
> line there with only one message. Perhaps I'm missing sth!
> Kind regars.
> W. O.
It seems like admindb.py doesn't escape the body of html emails
properly, which can make it impossible to do anything to the post.
This patch should fix it.
--- mailman/Mailman/Cgi/admindb.py~ Mon Apr 30 17:53:15 2001
+++ mailman/Mailman/Cgi/admindb.py Mon Apr 30 17:56:09 2001
@@ -228,7 +228,7 @@
row, col = t.GetCurrentRowIndex(), t.GetCurrentCellIndex()
t.AddCellInfo(row, col-1, align='right')
- TextArea('fulltext-%d' % id, text, rows=10, cols=80)])
+ TextArea('fulltext-%d' % id, cgi.escape(text), rows=10, cols=80)])
t.AddCellInfo(row+1, col-1, align='right')
Tollef Fog Heen
Unix _IS_ user friendly... It's just selective about who its friends are.
[ I am not on the list so please leave me in the CC on this thread ]
After doing this 'patch' you can specify a single %d anywhere in
subject_prefix (ie the 'Prefix for subject line of list postings') and it
will be magically replaced to the post_id (ie the message index).
BTW, where is the post_id stored? Can I updated it from the command line
with some (less)? standard tool?
I have tested with formats of type '[LIST (%d)]' for subject_prefix.
I would not be surprised if some strange formats may screw up my regular
expresions... today is my first day writing Python :)
Ex: Say you have a list with subject_prefix set to '[LIST (%d)]'
The first post will have a subject of:
Subject: [LIST (1)] the real subject line
The reply to this will hold:
Subject: Re: [LIST (2)] the real subject line
The reply to that will hold:
Subject: Re: [LIST (3)] the real subject line
And so on.
Just a simple but useful patch:
If someone sends an administrative request to the -request address, he
or she may leave the subject line empty, writing the commands(s) in the
body of the message.
Netscape and other mailers suggest a default subject "(no subject)", and
the sender will get an error report because (no subject) is no valid
< # ignoring (no subject) in the subject line of a administrative
< if subject == "(no subject)" or subject == "(No Subject)"
< subject = ""