I just installed Mailman 2.1, and somebody noticed that for
Word file attachments, the attachment link in the archives
showed up as ".dot" rather than ".doc".
When I tested it out, my attachment was just a string of
I did some research and found Bug 669081. So I took the
latest Scrubber.py from CVS (2.24), and swapped it into
the 2.1 sources, rebuilt Mailman, and installed it.
Now my attachment isn't gibberish anymore, but it has
an ".obj" extension.
I realize updating just Scrubber.py is not necessarily kosher.
Are there other files I need to update?
David Eisner | E-mail: cradle(a)umd.edu |
CALCE EPSC | Phone: 301-405-5341 |
University of Maryland | Fax: 301-314-9269 |
I am having problems getting Mailman 2.1 installed on LM 8.2 using the
Stock Python distributions. Here is the Error I am encountering:
/usr/bin/python -S /home/mailman/cron/qrunner
Traceback (most recent call last):
File "/home/mailman/cron/qrunner", line 89, in ?
from Mailman.Handlers import HandlerAPI
File "/home/mailman/Mailman/Handlers/HandlerAPI.py", line 26, in ?
from Mailman.pythonlib.StringIO import StringIO
ImportError: No module named pythonlib.StringIO
Does this follow with the missing Python 2.2 Development RPM (Note that
LM 8.2 does not have a Python-development rpm).
Do these errors shed any additional light on the matter?
Albert E. Whale - CISSP
ABS Computer Technology, Inc. - ESM, Computer & Networking Specialists
Sr. Security, Network, and Systems Consultant
Board of Directors - InfraGard - Pittsburgh, PA
There seem to be some other threads capturing people's attention, but Barry
has logged in and sent mail a couple of times :), so I'm assuming this fell
through the cracks.
I have some lists on a host running MM1.1, and a new host running MM2.1. I
need to move the 1.1 lists over to the new host. Is there a robust way to
I've read several of the posts about changing the footers. I've made changes
to the footer in the non-digest and digest options, but they do not get
applied. I've also emabled personalization, but did not see any other
options. Is there somewhere else I should look?
we have a mailing list of customers that we use to send out
announcements about service problems, bad lines and general
information. Nobody should be able to send e-mail to that list except
the people allowed to do so. Since e-mail senders are easily forged,
we have currently set all list members to moderated (including the
people allowed to send to the list, who are also moderators).
When a message goes out to the list, the author sends it, gets back
the approval request and approves her own message. People have started
to complain that this is uncomfortable. Before we switched to Mailman
(2.1, if that matters), that list was managed with a patched majordomo
that would only forward a message to this list if the correct password
was found in the message's first line (which was then removed from the
message before actually sending it out to the list).
Is there a possibility to allow Mailman 2.1 to immedately forward a
message from a moderator to the list if and only if the correct
moderator password is given in the message? If the message doesn't
have an "Approved: <listpassword>" header or first line, it should be
held for moderation just as any other message coming in to the list
Any hints will be appreciated.
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Karlsruhe, Germany | Beginning of Wisdom " | Fon: *49 721 966 32 15
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fax: *49 721 966 31 29
I have closely followed install instructions for mailman.
But when I try to send something I get this error:
<mailman(a)medsyn.org>: Command died with status 8:
"/usr/local/mailman/mail/mailman post mailman". Command output: Failure
to find group name mailman
Try adding this group to your system, or re-run
configure, providing an existing group name with the command line option
... but the 'mailman' group is really existing!! Mailman was created under
Du I need to configure --with-mail-gid=mailman?
I cannot find anything in the FAQ, or the bugtracking.
My system: RedHat 8, Postfix 1.1.11, last release of Mailman, Apache 2.0,
I've got a problem with some of my subscribers that are using the gmane.org
news server to read mailing lists. I run my lists with Mailman 2.1.
These subscribers (myself included) post messages to the list via the news
server, and the messages go out to the regular subscribers, and gmane.org,
without a problem ... however, when the message is included in a digest, it
just shows up as "--- non-text attachment removed ---" (or something to that
I do have Mailman 2.1's content filtering enabled so that only text portions
of a message are sent through (and HTML is *SUPPOSED* to be converted to
text, but that's another issue).
I have Mailman's "pass_mime_types" set to:
Again, the "non-text attachments removed" message is only showing up in the
Any idea what is going on?
I was going to add this FAQ entry, but I realize that I don't have a
password to do that and I have to leave for a meeting right now.
If someone wants to add this, feel free to do it. I just discovered
this issue this morning, when I noticed that some of my lists took a
long time to deliver mail.
PS/ feel free to reformat, rewrite, delete, ... :)
Samuel Tardieu -- sam(a)rfc1149.net -- http://www.rfc1149.net/sam
4.20 Who should deal with DNS errors?
Sometimes, Mailman tries to send mail to domains which exist but do
not have a MX (mail exchanger) or an A (address) record. This may
happen for example when a spam comes from a newly reserved domain, who
has not been setup to receive mail.
Most MTA are configured to reject mail for such a domain with a
temporary failure exit code (such as 450), because the absence of
those records may be caused by a transient network outage. If your
local MTA has been configured this way, it will reject mail from
Mailman with this temporary failure exit code, and Mailman will try to
resent the mail every minute. Considering that the DNS lookup may
easily take up to 30 seconds in case of a network problem, this may
slow down Mailman mail delivery by a huge factor.
One solution is to let your MTA deal with this situation instead of
Mailman. Configure your MTA so that it always accepts mail coming from
Mailman. In Postfix for example, this is done by using a
"client_access" restriction (allowing mail from localhost if Mailman
is running on the same machine as Postfix) before the
If you have an old cookie from Mailman 2.0.x, you'll have to re-login
for every page until you manually clear the cookie from your browser
(after upgrading to 2.1).
Is there any way to fix this in the future? With some browsers, it's not
simple to remove an individual cookie.
"Since when is skepticism un-American?
Dissent's not treason but they talk like it's the same..."
(Sleater-Kinney - "Combat Rock")