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
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.
I will move a few lists to mailman, from ecartis.
I want to retain message numbers, and continue current
sequence. So I need to start message number from a
How can I do that ?
I am new to mailman. I can undump, config.pck, I can chnage
post-id. I do not know, how to put that fiile in pck format.
Secondly, I manage to change post-id, will it break anything
I've just installed Mailman version 2.1.11.
I was surprised to find that the standard distribution had no support
for the Postfix VERP feature, which can create VERP return paths much
more efficiently than when Mailman does it itself.
I did find a patch for the FreeBSD port of an earlier Mailman version
and changed it to match the standard 2.1.11 distribution.
It seems to work fine.
If anybody should be interested, I've placed the modified patch,
directly usable for 2.1.11, at
Note that even with the patch, this feature is disabled by default; it
is turned on by setting VERP_STYLE = 'Postfix'. It also needs to be
allowed explicitly in the Postfix configuration (e.g.,
I have tested the patch only with the feature turned on.
Jesper Dybdal, Denmark.
http://www.dybdal.dk (in Danish).
Is there a preferred flavor of Linux that Mailman seems to work and install the best with? I'm trying Ubuntu, but the apt-get feature is getting hung up on trying to find the repositories and can't, so, until I get that fixed I just thought I'd ask.
Thanks for any ideas and suggestions,
Director of Technology
Centralia City Schools
Centralia, Illinois 62801
618-532-1907, Ext. 1030
I continue to get these messages when some cron jobs are running. I can see
that it is a permissions problems. But I have tried everything by changing
permissions and it still is having problems. This particular file that is
mentioned is not there. Someone please help me figure this out. There has
to be some little thing I am missing. I have compared files with others
that are not getting the message and the permissions are the same.
Your "cron" job on lists
/usr/local/bin/python -S /usr/local/mailman/cron/nightly_gzip
produced the following output:
Traceback (most recent call last):
File "/usr/local/mailman/cron/nightly_gzip", line 154, in ?
File "/usr/local/mailman/cron/nightly_gzip", line 140, in main
File "/usr/local/mailman/cron/nightly_gzip", line 81, in compress
outfp = gzip.open(txtfile+'.gz', 'wb', 6)
File "/usr/local/lib/python2.3/gzip.py", line 49, in open
return GzipFile(filename, mode, compresslevel)
File "/usr/local/lib/python2.3/gzip.py", line 94, in __init__
fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
IOError: [Errno 13] Permission denied: