I want all mails sent to the list to come from the list's email address...
But, in this case, if the user forgets to sign their name at the
bottom of their mail body, effectively the mail to the list is
Is there a way to add the user name (or email address) to the top of
each mail so that the mails have the name of the sender, while the
mail itself comes from the list address?
I have looked high and low for an answer, but noone seems to have the solution.
Hi - I have searched FAQ and archives to find an answer. Hoping you can
I have a new list (with previously imported addresses) for announcements
only, and wish these announcements to be received immediately.
I set the defaults to allow non-digest and to not allow digest.
I wish to send out announcements in html, and so wish to make the
default for new subscribers be MIME. While I see a setting under Digest
Options (MIME_is_Default_Digest), I don't see any equivalent option
under Non-Digest Options... and new subscribers continue to come in as
In order to avoid having to manually change this option for each
existing subscriber, is there a way to force all existing subscribers to
receive MIME in Non-Digest mode?
If not, is there a way to force all NEW subscribers to be enrolled with
MIME as their default?
Also, is there a way to "lock" the MIME switch on, so that users who try
to change their option to plain text will be prevented from doing so?
When authorizing a moderated list posting is it possible to change the
date/time on the outgoing authorized list message to the time it was
approved instead of the message showing the time it was first received
Where can I find the template for the monthly password reminder email?
I'd like to modify it so that it doesn't contain the password (our members
object to this being sent unbidden in plain text), and so that it reminds
users to make sure their subscription address matches the address from which
they currently send email (ideally with a link to their personal options
page so they can update).
Michael R. Boudreau
Senior Publishing Technology Analyst
The University of Chicago Press
1427 E. 60th Street
Chicago, IL 60637
(773) 753-3298 fax: (773) 753-3383
I've followed the FAQ to move some lists across to a new server, but now
on the new machine any message posted to a list gets passed to Mailman
and then disappears. The Mailman error log says this:
Sep 24 10:34:18 2009 (5311) Uncaught runner exception: regular_exclude_lists
Sep 24 10:34:18 2009 (5311) Traceback (most recent call last):
File "/usr/lib64/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop
File "/usr/lib64/mailman/Mailman/Queue/Runner.py", line 191, in _onefile
File "/usr/lib64/mailman/Mailman/Queue/IncomingRunner.py", line 130,
File "/usr/lib64/mailman/Mailman/Queue/IncomingRunner.py", line 153,
File "/usr/lib64/mailman/Mailman/Handlers/CalcRecips.py", line 99, in
File "/usr/lib64/mailman/Mailman/Handlers/CalcRecips.py", line 157, in
File "/usr/lib64/mailman/Mailman/MailList.py", line 146, in __getattr__
Sep 24 10:34:18 2009 (5311) SHUNTING:
I can't find any reference to this exception, so I'm a bit stuck where
to look next. Any ideas?
The new server is running a fresh install of Mailman (it didn't have any
lists before I moved these ones across) and the move went from Slackware
to Gentoo so many of the paths have changed, just in case these are
saved in the list data. (I have run the fixurl script as per the FAQ,
and the lists do appear in the Mailman web UI.)
I found this E-Mail address on the MailMan homepage and decided to
contact you as I don't seem to be able to locate the information I
To explain my circumstance. I am a visually impaired person, trying
to get to grips with administrating a mail server under Apple Mac OS X
10.5.7 (Leopard) server.
I need to host mailing lists under virtual domains hosted on our
server but can't see quite how this is accomplished.
Is there anywhere I can obtain this information as Apple's
documentation on this subject seems poor from what I've seen.
I really do apologise for any inconvenience I may cause you by
contacting you - but if you could point me to the relevant information
pages as to how to accomplish virtual domain list configuration under
Apple's server platform I'd be very grateful.
As a blind person this information is not always easy for me to
locate. Thank you in advance for any help.
Mailman 2.1.5 on RedHat Linux -
How can I set up a new list that sends to multiple existing lists - but
only sends one message to each person - even if the person is a member
of multiple lists?
a. LSOFT calls this a "superlist"
b. Can "Mailman" do this?
c. In this case, we have a system newsletter that will be sent to
multiple lists. I'd like people to receive the message only once, even
if they are on more than one of the lists included in the mailing.
Unix system administrator
Center for Information Services
Bellevue, WA 98004
I am a list administrator for a number of mailing lists hosted on
lists.sonic.net. The folks at sonic are great, except they really
don't fully understand Mailman, so I am hoping to get a few of my
issues resolved here.
All my lists are pretty standard (aka, I don't need any help for
them), except for one. One of the lists was recently migrated from
Autoshare (finally got to say goodbye to Mac OS 9, the only OS
Autoshare runs on). There are certain features of Autoshare that are
awesome, but I cannot figure out how to configure Mailman to support
In a nutshell, this list is a combination announcement list and tech
support list, and the list contributions are modified by the list
administrator on a regular basis (either to remove excessive text
from previous posts, add signatures, remove profane or rude language,
and/or remove sensitive data that is commonly posted in error on our
list). The way it worked on Autoshare, and they way I want it to
work on Mailman, is like this:
All posts go directly to the moderator (not the mailman "list
moderator", because that puts a bunch of extraneous pre-text in the
email that I don't want to have to wade through on every post). Upon
acceptance of the post, modified or not, I then redirect the post to
the actual mailing list. Redirect means the "TO:" header remains in
tact as the original poster, and the moderator email is the
"envelope" sender. Autoshare recognized the envelope sender and
passed the post through to the list immediately.
I have been unable to recreate this configuration on Mailman, but I'm
hoping that there is a way to do it. I have successfully set up the
list such that the Reply-To goes to the moderator. This sends the
post, in tact, with no extraneous pre-text, directly to the
moderator. The problems I'm having are as follows:
1. The reply-to does not seem to work for digest members. Digest
members are reporting that the reply-to of the digests goes to the
list (which then creates the moderator email text before sending to
the moderator). How do I get the reply-to for digest members to work
the same as non-digest?
2. For members whose email clients use buttons based upon email
headers - specifically, list-id - they click on Reply to List and it
goes to the wrong place. I would either like to change the list-id
value, or remove it entirely. Is there a way to do that?
3. When I redirect the modified/approved post to the list, I want the
TO field to maintain the original poster's email, and the moderator's
email will be the envelope sender. I would like the Mailman list to
recognize the envelope sender to authorize immediate distribution of
the post. Currently, however, it holds the post for moderator
approval. Is there a way to do this?
4. Lastly, the web archives created by Autoshare automatically
created clickable HTML links for all HTML URL's in posts. The
Mailman archives are all unclickable plain text URL's. Note, I want
the list to remain a plain text list, as it was on Autoshare, but I'd
still like Mailman to build HTML code to make the links active in the
web archive. Is there a way to do this?
I really appreciate any help in this matter.
describes a bug I'm suffering from: MIME encoded headers are re-
encoded by mailman and spaces are added around each encoded
The affected mailman installation is 2.1.5 and maintained by a
hoster, not myself. Therefore I would like to know what to tell the
I couldn't find the bug in the mailman (Launchpad) bug tracker so I
wonder whether this bug is known to the developers and whether it's
Oliver Betz, Muenchen