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
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've got another problem with Qmail/Plesk/Mailman (same customer,
rebuilt server). Plesk is 7.5.4 reloaded.
Mail delivered fails with "need GID 110 got 101" error. I set up the
brute-force wrapper to deliver with GID 110, and set the permissions
correctly for it to work. Now, I'm getting the following (broken up
into multiple lines for courtesy):
qmail: 1157518628.995172 delivery 726: success:
I'm about ready to pull my hair out. I even added the popuser user to
the mailman group in /etc/passwd.
So, that being said, are there any ideas out there? I have been
messing with this for a week, and have not come up with anything else
Douglas G. Phillips
Simple Business Solutions
This message was sent using IMP, the Internet Messaging Program.
-----BEGIN PGP SIGNED MESSAGE-----
I am happy to announce the first beta release of Mailman 2.1.10.
This is a security and bug fix release and it is highly recommended
that all sites upgrade to this version. Mailman 2.1.10 also adds support
for two new language translations, Hebrew and Slovak and a few new features.
Mailman is free software for managing email mailing lists and e-
newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.
For more information, including download links, please see:
Special thanks are due to Barry Warsaw and Tokio Kikuchi for much coding
and support, Moritz Naumann for help with security issues and Jim Tittsler
for a significant patch.
Here's a list of the major changes.
- The 2.1.9 fixes for CVE-2006-3636 have been enhanced. In particular,
many potential cross-site scripting attacks have are now detected in
editing templates and updating the list's info attribute via the web
admin interface. Thanks again to Moritz Naumann for assistance with
- Changed cmd_who.py to list all members if authorization is with the
list's admin or moderator password and to accept the password if the
roster is public. Also changed the web roster to show hidden members
when authorization is by site or list's admin or moderator password
- Added the ability to put a list name in accept_these_nonmembers
to accept posts from members of that list (1220144).
- Added a new 'sibling list' feature to exclude members of another list
from receiving a post from this list if the other list is in the To: or
Cc: of the post or to include members of the other list if that list is
not in the To: or Cc: of the post (Patch ID 1347962).
- Added the admin_member_chunksize attribute to the admin General Options
interface (Bug 1072002, Partial RFE 782436).
- Added the Hebrew translation from Dov Zamir. This includes addition of
a direction ('ltr', 'rtl') to the LC_DESCRIPTIONS table. The
add_language() function defaults direction to 'ltr' to not break
existing mm_cfg.py files.
- Added the Slovak translation from Martin Matuska.
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
-----END PGP SIGNATURE-----
I'm using Mailman for lists management, in a collaboration
I configured Mailman so that an external archiver is used, but I
hesitate to run this archiver in background or foreground.
More concretely, in mm_cfg.py conf file, should I put:
PUBLIC_EXTERNAL_ARCHIVER = 'cat > /var/run/mailman/mail_tmp;
PUBLIC_EXTERNAL_ARCHIVER = 'cat > /var/run/mailman/mail_tmp;
/usr/local/bin/external_arch %(listname)s &'
What do you recommend ? is there a difference, in terms of performance ?
Is there a risk of system overload, for one of the 2 solutions, when
dealing with too big archives ? (I have some archives exceeding 50 M)
--Mohamed CHAARI (mailto : mohamed.chaari(a)st.com)
I have two smtp servers that we use dns round robin for load
balancing. I can run it one server at a time, but I am running into
some pid lock file issues when I try to run them simultaneously.
Ok, maybe this is an issue with my understanding, but...
I am on a gentoo system, trying to clean up some things (inherited) -
duplicates, etc. I had an old version of Mailman (2.1.7) and 2.1.9
I removed the 2.1.7 version with no apparent problems, but then updated
2.1.9 to the latest rev - 2.1.9-r2 (this is in the testing/unstable repo
on gentoo, so maybe this is a bug with this package)...
They aren't supposed to make major changes between minor rev bumps like
this, but they did this time:
1. The install directory was changed from /usr/local/mailman to
2. They also split up some of the stuff... if I'm not mistaken, the
following directories used to be in the main /usr/local/mailman:
but they all got moved to /var/lib/mailman...
I got all of this sorted (fixed the paths in the aliases files and in
main.cf for postfix), and mailman seems to be working fine - I send a
message to a list, I see it processed in the log, and the message is
delivered to all list members... but...
If I try to 'start' mailman, it won't start - I get the (!!) error. If I
try to stop it, it says it isn't started.
What am I missing?
I set up a mailman mailinglist (everything preinstalled on a plesk-based
hosting) and have a strange effect.
When I subscribe a user from my address by using the email-command with the
optional "address=<user-address>", the user receives the
confirmation-message without problems. BUT if the user replies to the
message (to confirm), he gets a welcome-message with the variable-codes
instead of the real values.
When the user himself does the same procedure (obviously without the
address= option, that is not needed in this case), the welcome-message looks
I tried the same with the mailman-users-list itself and it worked, so I
think this is not a bug - at least not in the actual version. I am using
Can anybody help me with this one?