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.
I received the following error this morning. So I rerun configure again with the following command: ./configure --with-cgi-id=apache --prefix=/var/mailman. I'm still getting the same error. Is there any place that I can look for so that I can debug this problem better? Perhaps, looking at the config history file or something. Any other places that I can check the cause of this error?
"Mailman CGI error!!!
The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog:
Group mismatch error. Mailman expected the CGI
wrapper script to be executed as group "nobody", but
the system's web server executed the CGI script as
group "apache". Try tweaking the web server to run the
script as group "nobody", or re-run configure,
providing the command line option `--with-cgi-gid=apache'."
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?
I've just set up my first Mailman mailing list in OS X Server. It sends mail
as welcome notifications were received by several different members
subscribed to the mailing list. However, it doesn't seem to be receiving
e-mail. All attempts I've made have resulted in Delivery Failure
This is the text returned with this Delivery Failure Notifications:
> Delivery to the following recipient failed permanently:
> Technical details of permanent failure:
> Google tried to deliver your message, but it was rejected by the recipient
> domain. We recommend contacting the other email provider for further
> information about the cause of this error. The error that the other server
> returned was: 550 550 5.1.1 <list(a)domain.com>: Recipient address rejected:
> User unknown in virtual alias table (state 14).
What could be the cause ?
In order for a Mailman list to work properly do I need to create an account
for it in Workgroup Manager with its e-mail address ?
Sorry if this is a simple question but I am not an IT specialist and don't
have any experience with Mailman.
Thank you in advance,
I find it convenient to have a Google Groups interface for Mailman
lists. This adds search, thread monitoring at no cost, and makes
communication for people who don't like email a lot easier (look at
PySide list as an example). There is one problem though:
- if a mirrored list requires subscription, you need to subscribe both
to mailing list and to groups -
This takes a lot of fun out of using Groups, but the worst thing that
your message may be delivered and will be available in Groups and not
in Mailman. So, my question is:
- how can I setup Mailman, so it can accept mails sent through Google
Groups proxy automatically? -
Please, CC. Thanks.
Hi Mark (Sapiro) and other members,
While discussing some possible DNS set-up issues I might need to resolve on
my server a certain IT professional mentioned to me that Mailman shouldn't
be run using a virtual domain. I am not sure if this professional was
referring to virtual domains in general or only those running on Mac OS X
Do you know if this is true ? Do you see any problems with Mailman running
from a Virtual domain ? Let me make this a little clearer. I have a Mac
server on a single IP address and host several domains. The primary domain
name (the one returned when you do a search on my IP address) is domain1.com
and the Mailman list is being run on domain2.com (one of several virtual
domains hosted on the same server).
Any Mac specialists on the list that know the answer to this question ?
Thank you in advance,
Although I have a few years of experience as a list administrator of lists
hosted on other sites, so far I never managed a mailman server on my own.
In our institute we manage small list via /etc/aliases :include:s
Recently I decided to make an experiment, so I installed mailman 2.1.11
via the suse 11.3 distribution on my machine. I read carefully the PDF
"GNU Mailman Installation Manual release 2.1" by Barry Warsaw, and other
stuff on the wiki, including those concerning sendmail (we are a sendmail
I say "experiment" since I am testing it on my personal machine, although
the target system will be one of the institute servers (in process of
being upgraded). I thought to gain experience first in a simpler
I followed the manual except that at step 6 (6.3) I followed
and related links.
The suse installation via yast2 installs mailman partly in
/usr/lib/mailman, partly in /var/lib/mailman/ (and also
/usr/share/man/man8 and /usr/share/doc/packages/mailman/), it also creates
the user and group.
It does not provide any automatic configuration for apache, so I did it
manually (I actually like this better). I had to place in
default-server.conf also this block
Options +ExecCGI -Includes
Allow from all
in order to be able to execute the CGIs.
I note that the startup script /etc/init.d/mailman gives a message
"Starting mailman (Warning: the Apache2 webinterface for Mailman has not
been activated!)" which seems to imply a flag missing in line
APACHE_SERVER_FLAGS in /etc/sysconfig/apache2, but I have no documentation
for it, and it seems that the site can be accessed ok
Any Suse user can confirm this is unnecessary ?
Concerning sendmail, I followed the "method 2" (WITHOUT mm_handler)
because it seems to apply better to our institute arrangements. So I have
a sudo wrapper script with the two lines
/bin/cp /var/lib/mailman/data/aliases /etc/mail/mailman.aliases
a sendmail.cf with O AliasFile=/etc/mail/aliases,/etc/mail/mailman.aliases
and the fake arrangement in mm_cfg.py
POSTFIX_ALIAS_CMD = '/usr/bin/sudo /usr/sbin/mailman.aliases'
POSTFIX_STYLE_VIRTUAL_DOMAINS = 
I have verified the command /usr/lib/mailman/bin/genaliases works and
touches the right files.
I have also run "/usr/lib/mailman/bin/newlist mailman" to create the top
list and it works (it said to have sent a mail, but actually it was just
queued, and it was sent as soon as I started the qrunner from /etc/init.d
I set my own e-mail as list owner, and set a password (incidentally the
same test password used by /usr/lib/mailman/bin/mmsitepass)
I hope the fact I always use the same test password is not a problem
At this point I entered the admin web page of such a list (for which I
received the "Your new mailing list" message). It seems I can browse it
Then I wanted to subscribe myself to the list.
If I do it via the Membership Management -> Mass Subscription, and I enter
my e-mail address in the form, I get no errors but nothing happens.
If I try to subscribe via the mailman/listinfo/mailman page, I get instead
an error "you must supply a valid e-mail address"
Why does that happen ? see also question 4
I tried also to create a new mailing list via the web interface (this
requires supplying the site password as well)
this gives me instead an error
"Unknown virtual host: sax.iasf-milano.inaf.it "
This may have to do with our institute standard arrangement, and will
apply also to the real arrangement on our target server. Unfortunately I
cannot find the documentation for the keywords in mm_cfg.py so I am not
sure what shall be tuned.
This is the content of mm_cfg.py. The first 9-10 lines were added
automatically by the suse yast installation, the rest was edited/added by
me to suite our apache config and the "sendmail method 2"
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
DEFAULT_NNTP_HOST = 'poseidon.lambrate.inaf.it'
DEFAULT_EMAIL_HOST = 'poseidon.lambrate.inaf.it'
DEFAULT_URL_HOST = 'poseidon.lambrate.inaf.it'
MTA = 'Postfix'
DELIVERY_MODULE = 'SMTPDirect'
SMTPHOST = 'localhost'
SMTPPORT = '25'
#IMAGE_LOGOS = '/mailmanicons/'
IMAGE_LOGOS = '/icons/'
# changed lines above manually
# inserted this stuff for sendmail
POSTFIX_ALIAS_CMD = '/usr/bin/sudo /usr/sbin/mailman.aliases'
I have to explain our configuration:
- we have two domains.
lambrate.inaf.it is the one where all A and PTR records are,
and also a number of CNAMEs for various services.
iasf-milano.inaf.it is a more formal domain alias, which contains
just CNAMEs for the main services visible from outside
- poseidon(.lambrate.inaf.it) is my machine FQDN
- sax.iasf-milano.inaf.it is the CNAME for the web server on it.
It is also the ServerName in default-server.conf (so one can get
to the server as sax or poseidon or localhost but is shown just
This will apply not only to my test configuration, but also to the
target configuration (the institute web server will be
www.iasf-milano.inaf.it, which is a CNAME for a server [let us say
server3] ... actually that server runs different virtual servers)
- all our e-mail address are FULLY MASQUERADED, i.e. they are of the
form "user(a)lambrate.inaf.it" or "user(a)iasf-milano.inaf.it" (our
MXs accept both in entrance, and each user selects which form to
use on exit).
The message from mailman when I created the initial list did have
(obviously masqueraded by sendmail)
It did contain URLs like http://poseidon.lambrate.inaf.it
(reachable but translated as sax.iasf-milano.inaf.it)
It did contain e-mail like mailman-request(a)poseidon.lambrate.inaf.it
(so far I haven't tested them)
I am not sure how much of the above applies to QUESTION 4 (i.e. to run on
my local machine)
The arrangement on the target system will be more complicated.
As I said the www server is "server3", but the MX servers are instead
"server1" and "server2". They are also NIS master and slave server, and
all our e-mail aliases are NIS aliases (so
I am not expecting a solution to question 5 now, I guess that if I can
have a running solution on my local machine, and an understanding of the
inner working of mailman, some creative user of crontab scripts or NFS
mounts could make the mailman aliases available to all NIS clients and
visible to the outside world.
But any hint will be gratefully acknowledged.
Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy)
For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html
I have been having a rather queer problem. I am running several lists
on my list server but having a problem with only one list. I have gone
through my server and tried to compare configs and have done check_perms
but have found no clue as to why it is failing to deliver to list
members and yet it is archiving properly. Looking through the logs i
have seen that the messages are being shunted. Being a newbie would
someone please point me in the right direction. Below is my list server
and an extract from the error log:
Mar 30 16:56:41 2011 (31246) SHUNTING:
Mar 30 17:01:08 2011 (31246) Uncaught runner exception: msg_footer
Mar 30 17:01:08 2011 (31246) Traceback (most recent call last):
File "/usr/local/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop
File "/usr/local/mailman/Mailman/Queue/Runner.py", line 191, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 74,
self._func(mlist, msg, msgdata)
File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 132,
Decorate.process(mlist, msg, msgdata)
File "/usr/local/mailman/Mailman/Handlers/Decorate.py", line 70, in
footer = decorate(mlist, mlist.msg_footer, 'non-digest footer', d)
File "/usr/local/mailman/Mailman/MailList.py", line 146, in __getattr__
raise AttributeError, name
I'm a new here on this list and new on the Linux world. :-)
Using for a web project a virtual server with Ubuntu 10.04.2 LTS, and
installed is from the Ubuntu package sources Mailman version 2.1.13.
In one of a short news of the upcoming Ubuntu 11.04 is the latest
Mailman version available then. My provider don't accept any Kernel
My question: It's possible with a bash script to update largely and to
minimize the administration process automatically?
For the beginners in this area, it seems the English documentation is
not really easy to use it manually.
Thanks for tips and tricks.
I have 2 problems at the same time.
1. A massive electrical storm took out computer/router/phone lines. I'm left with Blackberry for next few days.
2. A member is spamming my list and I want to boot him off.
My question: can I boot him off via an email command? If so, what is it? I can't connect to get to the FAQ.