Hello. How might one configure Mailman (version 2.1.6) list settings
using PHP scripts? The goal is to configure Mailman list settings such as
domain name of list, non-digest footer, set welcome/goodbye messages, etc.
An approach that comes to mind is to use bin/config_list. This would
require writing/reading files and using bin/config_list to process them.
Is there another recommended or preferred way to accomplish this?
There was a post about "PHP Wrappers" which suggested, "...just use a
setuid mailman wrapper script that does caller-checking to see if it's
called correctly, by the right user, and with 'safe' values"
This was recommended over simply adding the www user to the mailman group.
I do not completely understand how one creates a setuid mailman wrapper
script. Is this a matter of creating something similar to mail-wrapper.c?
If someone has written a wrapper script or has some good resources further
explaining this to share and is willing to do so, I would appreciate it.
I have recently installed mailman.
As a result of customising the user interface, I have noticed that
the HTML of both the administrative and user interface is quite
incorrect. In particular the user interface, which shows many layers
of intervention (tags appear with too many case changes!).
I am attempting to clean up the code (as HTML 4.01 Transitional), but
I wonder if there is already an ongoing tidying up or redesign that
would make my work a waste of time.
One change in Mailman that would make correction and editing of HTML
templates easier would be to have all Mailman inner tags written
without using <> or other strange characters. For instance <MM-Form-
End> could be simply MMFormEnd. This way a template could validate as
valid HTML without being parsed first, as long as these Mailman tags
are not required in strange places.
Clearly the documents could loose its validity once parsed, but this
too can be avoided with careful design of the tags. For instance the
footer tag (I think <MM-Mailman-Footer>) generates at the moment
incorrect HTML all by itself and so cannot be corrected by a list
I see now that there is a General Web UI item in the TODO. Let me add
a plea: please do not use php for the future UI!
I just upgraded from 2.1.5 to 2.1.7, using a Fedora beta rpm.
has been applied.
Now I see crashes in Archiver like shown below. My problem is similar to
but different from
It turns out to be because both 8-bit ascii and unicode strings appears
as first element in key tuples in the 2006-February-author marshal. When
sort tries to compare these unrelated encodings python don't know what
to do. Neither do I...
How should the problem be solved? Should keys be stored as 8-bit ascii
or as unicode?
If anybody can give a hint I'll try to come up with a solution ;-)
Feb 18 17:57:44 2006 (29051) Uncaught runner exception: 'ascii' codec
can't decode byte 0xe5 in position 1: ordinal not in range(128)
Feb 18 17:57:44 2006 (29051) Traceback (most recent call last):
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose
File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 217, in
File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 327, in close
File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 543, in
File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 1125, in
File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 447, in
self._update_simple_index(hdr, archive, arcdir)
File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 460, in
msgid = self.database.first(archive, hdr)
File "/usr/lib/mailman/Mailman/Archiver/HyperDatabase.py", line 296,
key, msgid = index.first()
File "/usr/lib/mailman/Mailman/Archiver/HyperDatabase.py", line 113,
self.__sort() # guarantee that the list is sorted
File "/usr/lib/mailman/Mailman/Archiver/HyperDatabase.py", line 73,
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe5 in position 1:
ordinal not in range(128)
Feb 18 17:57:44 2006 (29051) SHUNTING:
I'm developing a patch to add an XMLRPC-based management interface to
Mailman. Would this be something that you would be interested in trying
to incorporate in the 2.1.x branch? Thanks!
Joshua Ginsberg <jag(a)fsf.org>
Free Software Foundation - Senior Systems Administrator
> I noted that in the source of mailman 2.1.7 there are 2 lines in
> # Clear our file mode creation umask
> Is this intended? Is it the reason why data/bounce-events-?????.pck
It looks like you're right. I don't know if there is/was a good reason
or not. I'm cross posting this reply to Mailman-Developers. Maybe
someone there knows the reason for this.
Note that many places in the Mailman code, umask is saved and set for a
particular purpose and then restored, but BounceRunner doesn't do this
when creating the bounce-events-*.pck. I don't know why.
Mark Sapiro <msapiro(a)value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan