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,
http://wiki.list.org/pages/viewpage.action?pageId=4030545 seems to
suggest that it's possible to enable personalization (for headers /
footers of messages), without enabling VERP itself (for the
envelope-sender of messages).
Is that correct? Some of the mailing list messages I have seen seem to
imply that you have to also
Also, is it possible to toggle personalization under the hood (using
withlist / config_list to set 'mlist.personalize = 2') /without/
enabling OWNERS_CAN_ENABLE_PERSONALIZATION globally? I have a case where
I'd like to enable personalization for a couple of lists without
allowing any other list owners to enable this feature.
I am very happy to announce the release of the seventh alpha for Mailman 3.0,
code named "Mission". Here are some of the highlights of a release with lots
of new stuff (a more detailed NEWS.txt file excerpt is below).
* Significant improvements to the subscription model. Users can now subscribe
to mailing lists with either an explicit address or a "preferred" address.
When a user changes her preferred address, all of her subscriptions
automatically track this change. All this and more have also all been
exposed to the REST API.
* New rules for member and non-member moderation. This effectively ports and
updates Mailman 2's moderation rules to the Mailman 3 framework.
* Support for SMTP AUTH added.
* The default password encryption scheme can be defined in the configuration
file, and all passwords are by default encrypted (using SSHA1).
* 'bin/mailman status' command added to provide command line status of the
master queue runner process.
* 'bin/mailman info' now prints the REST API root url and credentials.
* Basic Auth support for the REST API was added. (thanks Jimmy Bergman)
* Python 2.7 is supported.
I'm really excited about this release because it will provide a great baseline
for our Google Summer of Code students. If you've been putting off taking a
look at Mailman 3, I encourage you to download it and play with it. My goal
is for a final release on 11.11.11 so there will not be too many more alphas.
Now is the best time to influence our design decisions.
The tarball can be downloaded from Launchpad or the Cheeseshop:
The full documentation is also online:
3.0 alpha 7 -- "Mission"
* Significant updates to the subscription model. Members can now subscribe
with a preferred address, and changes to that will be immediately reflected
in mailing list subscriptions. Users who subscribe with an explicit
address can easily change to a different address, as long as that address
is verified. (LP: #643949)
* IUsers and IMembers are now assigned a unique, random, immutable id.
* IUsers now have created_on and .preferred_address properties.
* IMembers now have a .user attribute for easy access to the subscribed user.
* When created with add_member(), passwords are always stored encrypted.
* In all interfaces, "email" refers to the textual email address while
"address" refers to the `IAddress` object.
* mailman.chains.base.Chain no longer self registers.
* New member and nonmember moderation rules and chains. This effectively
ports moderation rules from Mailman 2 and replaces attributes such as
member_moderation_action, default_member_moderation, and
generic_nonmember_action. Now, nonmembers exist as subscriptions on a
mailing list and members have a moderation_action attribute which describes
the disposition for postings from that address.
* Member.is_moderated was removed because of the above change.
* default_member_action and default_nonmember_action were added to mailing
* All sender addresses are registered (unverified) with the user manager by
the incoming queue runner. This way, nonmember moderation rules will
always have an IAddress that they can subscribe to the list (as
* Support for SMTP AUTH added via smtp_user and smtp_pass configuration
variables in the [mta] section. (LP: #490044)
* IEmailValidator interface for pluggable validation of email addresses.
* .subscribe() is moved from the IAddress to the IMailingList
* IAddresses get their registered_on attribute set when the object is created.
* [devmode] section gets a new 'testing' variable.
* Added password_scheme and password_length settings for defining the
default password encryption scheme.
* creator_pw_file and site_pw_file are removed.
* 'bin/mailman start' does a better job of producing an error when Mailman is
* 'bin/mailman status' added for providing command line status on the master
queue runner watcher process.
* 'bin/mailman info' now prints the REST root url and credentials.
* mmsitepass removed; there is no more site password.
* Add Basic Auth support for REST API security. (Jimmy Bergman)
* Include the fqdn_listname and email address in the member JSON
* Added reply_goes_to_list, send_welcome_msg, welcome_msg,
default_member_moderation to the mailing list's writable attributes in the
REST service. (Jimmy Bergman)
* Expose the new membership model to the REST API. Canonical member resource
URLs are now much shorter and live in their own top-level namespace instead
of within the mailing list's namespace.
* /addresses/<email>/memberships gets all the memberships for a given email
* /users is a new top-level URL under which user information can be
accessed. Posting to this creates new users.
* Users can subscribe to mailing lists through the REST API.
* Domains can be deleted via the REST API.
* PUT and PATCH to a list configuration now returns a 204 (No Content).
* Support Python 2.7. (LP: #667472)
* Disable site-packages in buildout.cfg because of LP: #659231.
* Don't include eggs/ or parts/ in the source tarball. (LP: #656946)
* flufl.lock is now required instead of locknix.
* Typo in scan_message(). (LP: #645897)
* Typo in add_member(). (LP: #710182) (Florian Fuchs)
* Re-enable bounce detectors. (LP: #756943)
* Clean up many pyflakes problems; ditching pylint.
For many years, Atlassian has provided the GNU Mailman project with free (as
in beer) wiki hosting on their proprietary platform. This has included a free
license, free hosting, and free support. We are very grateful to them for
this, as our wiki contains lots of useful information that help you, the
members of our Mailman community.
The current wiki was offered to us at a time when we didn't really have any
other options. However, GNU Mailman is free software and a GNU project, so it
is not appropriate for us to be hosting our wiki on non-free software. We
have offers for hosting a new wiki on Moin <http://moinmo.in/> a very
excellent free wiki engine written in Python.
The major hurdle is actually finding the resources to do a high-fidelity
conversion from the current wiki to Moin, retaining as much of the current
feature set, layout, and history as possible during the migration. None of
the core Mailman developers has time to do this, though we will support the
effort. We tried, but were unable to get a slot in this year's Google Summer
of Code for the conversion work.
Now the FSF has put out a call for volunteers:
If you'd like to help GNU Mailman in this way, please contact the FSF at
We will provide as full a data dump from the current wiki as possible, and
guidance for requirements, etc., and the Moin developers have graciously made
themselves available to help with the technical details. Your conversion work
will of course be free software itself, so it will help Moin and other free
software projects wanting to do similar conversions. I hope you'll consider
help us out with this.
I administrate two Mailman mailing lists at ScienceByEmailHTML and ScienceByEmailPlain. We have approximately 39 000 addresses in the former list, and about 1000 in the latter. I have a question about the bounces we receive.
We have the lists set so after five bounces, the address is automatically disabled. An notification is sent alerting us to the disabled account, where we then delete the address from our own records as well as Mailman.
Depending on the week, we can get over a hundred of these notifications which come in batches, arriving typically on Friday (although we also get waves coming in on Monday as well).
However, we can also go a week without receiving a single one. Given the spread of excessive bounces is often in excess of a hundred, and rarely fewer than 60 or 70, I'm wondering if you know why this might be the case. Also, why do they arrive in waves? Is it collated and sent periodically through Mailman, or is it a result of batches of bounces being sent back from servers?
Note, running Debian Stable on the server.
I'm attempting to update Mailman through aptitude, but it warns me that
all files in the qfiles tree will be wiped out. This includes files that
have been bouncing back and forth between qfiles/out and qfiles/retry.
It's not quite clear as to when these messages have landed there.
Moreover, I noted that I have a good sized stack of messages in
qfiles/bad - which I'm not too worried about, since the dates are pretty
In short, what is the best way to proceed, given the circumstances?
I am trying to set up the aliases for qmail.
I used the Skript (manually) from the FAQ for 2.1 version of mailman.
But after executing it I stillt get this error:
"Sorry, no mailbox here by that name. (#5.1.1)"
A few things I am not sure about:
I wrote in my virtualdomains:
1. Is the list user correct? I used list because mailman doesn't exist
and list is the only one, that is linked some how to mailman
2. Where am I supposed to execute the script from the FAQ?
I executed it in /var/qmail/alias
Was that correct?