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.
After several researches with Google and archives of mailinglists please
allow me to contact you via this mailinglist.
Our postfix-mailserver hosts several domains (virtual mailhosting,
postfix/mysql) and "mailman".
The "primary domain" myserver.de is a virtualized domain also. So this
domain is not listed in mydestination:
myhostname = mail.myserver.de
mydomain = myserver.de
myorigin = $mydomain
mydestination = $myhostname, localhost
As far as I understand mailman forwards all emails to the "primary
domain" (mydomain) and mailman is only working if I add $mydomain to
But when doing this there are warnings from postfix that it is not
allowed to list the domain in the virtual aliases (mysql-database) and
Is there any possiblity to configure mailman to forward the emails in
./data/virtual-mailman not to "testliste2(a)myserver.de" but to
My actual config is:
DEFAULT_EMAIL_HOST = 'mail.myserver.de'
DEFAULT_URL_HOST = 'lists.myserver.de'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.myserver.de']
Or am I missing an important point?
On 18 Jun 2008, at 20:59, adsarebad-at-......... wrote:
>> Have you seen <http://www.gurulabs.com/downloads/postfix-to-mailman-2.1.py
> I think I may have ran into that file in my travels, can`t remember
> for sure through because I ran into so many. Is that the one where
> I need to have mylist(a)list.domain.com? I was hoping to be able to
> use mylist(a)domain.com.
At least the advantage of this solution is that you set the transport
for an entire domain to be this script, and then don’t need to have
the Mailman email addresses explicitly stated in your Postfix config.
If you want to have both regular and Mailman addresses for the same
domain, then I am afraid you will have to explicitly have the Mailman
addresses in your Postfix config. Just, they should go in the
appropriate section (addresses for virtual domains instead of aliases).
I am unsure what you actually wanted help with in your original
letter, i.e. was it a convenient way to do “newlist” after you setup
the multiple Mailman installs? Was it routing the different addresses
to the proper installs? etc.
Hi, i'm performing some tests with Mailman and Postfix over Centos5.
Does some body know how many messages per hour can be sent?
I´ll appreciate if some one could tell me what hardware and bandwith
are using and your stats?
What do I need to improve it?
Thanks in advance.
Jesus Alonso Rivas
Hi, I am observing periods of qfiles/in backlogs in the 400-600 message
count range that take 1-2hours to clear with the standard Mailman 2.1.9 +
Spamassassin (the vette log shows these messages process in an avg of ~10
Is there an easy way to parallelize what looks like a single serialized
I see some posts re: multi-slice but nothing definitive
I would also like the option of working this into an overall loadbalancing
scheme where I have multiple smtp nodes behind an F5 loadbalancer and the
nodes share an NFS backend...
Many thanks for pointers to any HOWTO docs or wiki notes on this
-----BEGIN PGP SIGNED MESSAGE-----
I am happy to announce the final release of the Mailman 2.1.11.
Mailman 2.1.11 is a cleanup of a few problems found since the release of
Mailman 2.1.10. It fixes the issue of shunted email subscribe requests
and a few minor issues. It updates the contrib/mmdsr script for some
2.1.10 and 2.1.11 log and error messages, and it adds a new cron to cull
and optionally archive old entries in the 'bad' and 'shunt' queues.
Mailman 2.1.11 has updates to several i18n translations.
A few bounce log messages now have the list name prepended.
There is a new Defaults.py|mm_cfg.py setting
ACCEPTABLE_LISTNAME_CHARACTERS with default value '[-+_.=a-z0-9]'. This
Python regular expression character class specifies the characters
allowed in list names. The motivation for this is the fact that
previously, a list named, e.g., xxx&yyy could be created and MTA aliases
generated that would cause the MTA to execute yyy as a command. There
is a possible security issue here, but it is not believed to be
exploitable in any meaningful way.
If anyone is concerned about the security issue and not ready to
upgrade, the mailman-2.1.11-listname-patch file contains a patch that
can be applied to Mailman 2.1.9 or 2.1.10 to add this feature.
See the release notes at
for more details.
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:
Files in this release are:
mailman-2.1.11.tgz <- The full release tarball
mailman-2.1.11.tgz.sig <- GPG signature for the tarball
mailman-2.1.11-listname.patch <- Patch to add new listname
~ validation to 2.1.9 or 2.1.10.
~ This patch is only applicable to
~ the older releases.
mailman-2.1.11-listname.patch.sig <- GPG signature for the patch
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-----