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'."
Is there an efficient way to change the domain name that mailman is
I have two mailing lists that were created for an organization before
that organization had their own domain. At the time the organization was
sure they did not want their own domain and would not be getting a
Since then, they have chosen to get a domain and set up a web site.
I would like to move their mailing lists onto their domain. It looks
like the process for this is:
1) get the list of subscribers
2) delete the mailing list from the one domain (losing the archives)
3) create the mailing list on the new domain
4) subscribe the list of subscribers
This process doesn't seem too difficult, but I would prefer to keep the
archives, if possible.
Both domains are on the same server, running CentOS7 and PLESK 12.5, if
that makes a difference.
I have waited almost a year for AOL and Yahoo to admit that they messed up and to remove their DMARC policy. My AOL and Yahoo subscribers are pretty upset at me because I won’t let them post. A number now have two subscriptions, one for posting (from GMail) and another for receiving the messages.
So against my better judgement, I included this hack in Cleanse.py;
< from email.Utils import formataddr, parseaddr
>from email.Utils import formataddr
< # Added to deal with DMARC issuej
< name, addrs = parseaddr(msg.get('from'))
< addrs += '.invalid'
< del msg['from']
< msg['from'] = formataddr((name, addrs))
\ No newline at end of file
I found it in the discussion list.
I don’t get compile errors, but Cleanse.pyc is not being updated. I have stopped and restarted Mailman and I have also rebooted, but same non-action. I have not tried ‘compileall’ and am not eager to, either (permissions, where to invoke, etc). Any suggestions?
The host OS is Mac OS X Server 10.5.8 with Mailman 2.1.14
one question. If the Sender-field exist and mailman create a new
Sender-field-line, then he have to delete the old one, or not?
And maybe, this is true also for all other header fields, what mailman
many greetings, willi
St. Elena de Uairen, Venezuela
Because of centralized administration of mailman server used by many
campus units, and other general inertia, we still use 2.1.12 (a couple
of local mods; I know of one for sure for recognizing alternative email
So I am wondering if later versions of Mailman 2 have added something
which seems to me to be obviously missing.
In (showing a representative, not necessarily real, URL)
you can choose to "discard" most messages and check "forward
discarded messages to the moderator".
you can only Dicard or Hold.
(Complete list Defer, Hold, Reject, Discard, Accept).
It would be nice if for each filter rule individually you
could choose "discard and forward to moderator".
Has that actually been implemented in subsequent versions of Mailman 2,
i.e. between 2.1.12 and 2.1.21 ?
I assume in Version 3 the filter capabilities have been completely
redone and probably regularized.
It began to seem prudent for us to hold "slightly spammy" mail for
inspection. A problem is that the majority of those would have been
rejected by the sender filters anyway (though we're interested in
those that wouldn't), so this has resulted in a lot of extra moderator
Now certainly we wouldn't want [or would appreciate the choice
not] to "forward to moderator" all discards on the /spam page.
And, really, the "does this fail the membership (filter) requirements"
is something you'd like to be able to determine in the spam filters.
(And simply discard those, perhaps forwarding if they are not too
spammy). (Because really really we'd like to "hold" slightly spammy
messages which meet membership requirements, but discard-and-forward
the others, but discarding-and-forwarding-to-moderator all would be
I wondered too about combined expressions (and negation).
Those don't look easy to do.
header_filter_rules (privacy): Filter rules to match against the
headers of a message.
Each header filter rule has two parts, a list of regular
expressions, one per line, and an action to take. Mailman matches
the message's headers against every regular expression in the rule
and if any match, the message is rejected, held, or discarded
based on the action you specify. Use Defer to temporarily disable
a rule. You can have more than one filter rule for your list. In
that case, each rule is matched in turn, with processing stopped
after the first match. Note that headers are collected from all
the attachments (except for the mailman administrivia message) and
matched against the regular expressions. With this feature, you
can effectively sort out messages with dangerous file types or
file name extensions.
Since you can always add multiple rules to achieve "or", it seems
unfortunate (but past history now) that multiple expressions don't "and".
Anyway, my simple question is "did Mailman 2 sometime after 2.1.12 gain
the ability to 'dicard and forward to moderator'" as an option for each
spam filter rule?
(Along with the implicit suggestion that that would be a useful option).
(And the longer-term suggestion for AND and negation).
The Service-Assistant of my hosting tried to solve, but did not found both of the default entries in mm_cfg.py.
SMTPHOST = 'localhost'
SMTPPORT = 0
So he's asking for accurate steps to handle SMTP Host Override (Plesk 12.5.x.).
Also he wants to know, how to prevent overriding that values during next server-update.
Antwort auf Nachricht vom 2016-03-13 - 23:44:12 :
>On 03/13/2016 01:44 PM, kapuzino(a)web.de wrote:
>> The new operator of my hosting decided to remove localhost from whitelist in plesk outbound filter to prevent spam and blacklisting.
>> Anybody knows any chance to use mailman another way ?
>There are a couple of possibilities.
>> MM is still installed (v2.1.18), but recently only woks delivering to server-internal adresses.
>> The service guy said, there might by a chance using smtp auth.
>> I have no access to mm_cfg.py of my own, but perheaps the service assistant will do the job, if I give him information.
>> (have a low price hosting)
>Mailman has two settings for the outgoing mail server that can be
>overridden in mm_cfg.py. The default settings are
>SMTPHOST = 'localhost'
>SMTPPORT = 0 # 0 means use the smtplib default which is 25
>These are for outgoing mail from Mailman only. They have nothing to do
>with delivery of mail TO mailman. You can tell Mailman to connect to any
>SMTP server and port by setting SMTPHOST to the fully qualified name of
>the server and/or SMTPPORT to the port.
>If the host operator will perhaps set up and allow an alternative port
>for you to use without authentication, then Mailman can simply be
>configured to use that port.
>If that isn't an option, but you can use an alternate port such as 465
>or 587 that may require TLS and/or authentication, you can set SMTPPORT
>to that value, but you (or the host admin) will have to patch Mailman's
>SMTPDirect.py module to provide the authentication. You can find a patch
>for this at <https://bugs.launchpad.net/mailman/+bug/558281>.
We have come up a few times where a list was created incorrectly.
Normally, we catch the mistake, delete the list, and recreate it
properly. However, there are times when the mistake is caught after
having been in use. So, the delete and recreate is not available to use.
I have a copy of Mark's clone_list command and it will allow us to
rename lists. Which is great and not a problem for me. However, I am
not the person normally involved with list creation, etc. Another group
does it. Normally through the web interface which works well for them.
Unless a mistake is made then they have to use the command line tools.
Again, not a problem for me but that group has very limited knowledge of
linux/unix and Mailman.
I can easily train them to use the Mailman tools, however, ensuring they
do the appropriate checks to avoid other problems is more difficult.
Specifically, they can run the clone_list command but rebuilding the
archives requires checking if the scrub_nondigest settings is No (this
is explained in the clone_list help).
What I have done is modify the clone_list command to combine the
renaming/cloning of a list and include an option to rebuild the
archives. However, the archives will not be rebuilt if the
scrub_nondigest setting is Yes.
Below my message is a diff of my changes to clone_list. While I try
testing my changes on a test system, I would appreciate it if someone
could take a look at my changes to ensure I am not off-base with my process.
--------------- My diff of clone_list -----------
--- clone_list 2016-03-18 10:28:14.000000000 -0700
+++ clone_list_scu 2016-03-22 10:19:43.000000000 -0700
@@ -109,6 +109,10 @@
Clone the archives of the old list. The default is an empty archive.""")
+ parser.add_argument('-b', '--rebuild_archives',
+ dest='rebuild_archives', action='store_true',
+Rebuild the archives of the new list. Requires -a/--archives.""")
@@ -186,6 +190,8 @@
abort("%s doesn't appear to be a valid email address" %
if ns.extra and not ns.clone_members:
abort('-e/--extra_files requires -m/--members.')
+ if ns.rebuild_archives and not ns.archives:
+ abort('-b/--rebuild_archives requires -a/--archives.')
print 'Getting %s list...' % ns.old_list
ol = MailList(old_list, lock=False)
@@ -268,5 +274,29 @@
+ if ns.rebuild_archives:
+ if ns.verbose:
+ print 'Rebuilding %s archives...' % ns.new_list
+ if ol.scrub_nondigest:
+ abort('Scrub_nondigest is YES for %s. WILL NOT REBUILD
ARCHIVES.' % ns.old_list)
+ archcmd = os.path.join(os.path.dirname(sys.argv), 'arch')
+ if not os.path.isfile(archcmd):
+ abort("""%s doesn't exist.
+Am I installed in Mailman's bin/ directory?""" % archcmd)
+ rbld = subprocess.Popen([archcmd,
+ so, se = rbld.communicate()
+ if rbld.returncode:
+ abort('unable to rebuild archives for %s\n%s' %
+ # If there was stdout output, print it. It is probably aliases.
+ if so:
+ print so
if __name__ == '__main__':
I've got a mailman-2.1.15 list which is BCC'ed by an original e-mail
message. Is it possible to get/view the original recipient at WEBUI
(along with Subject and Sender)?
Any help is appreciated. Thank you.
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
I am receiving spam to my list-owner address that appears to be sent
from the same list-owner address. Here are some of the headers,
anonymized a bit (google is there because my email is forwarded to my
Received-SPF: pass (google.com: domain of
mailman-bounces(a)my.server.com designates MY.IP.ADDR.ESS as permitted
spf=pass (google.com: domain of mailman-bounces(a)my.server.com
designates MY.IP.ADDR.ESS as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
Received: from localhost ([127.0.0.1] helo=www.my.server.com)
by my.server.com with esmtp (Exim 4.84)
for listmaster(a)my.server.com; Fri, 25 Mar 2016 08:23:06 -0500
Received: from [SPAM.IP.ADDR.ESS] (helo=spammer.domain.com)
by my.server.com with esmtp (Exim 4.84)
(envelope-from <mylist-owner(a)my.server.com>) id 1ajRhW-0006b2-Jk
for mylist-owner(a)my.server.com; Fri, 25 Mar 2016 08:23:00 -0500
From: A. Spammer <mylist-owner(a)my.server.com>
To: mylist-owner <mylist-owner(a)my.server.com>
Sender: "Mylist" <mailman-bounces(a)my.server.com>
The SPF and DKIM passes make it seem like this spam is actually being
sent from my server, not just from somewhere else with a spoofed
sender. Is there some way that my mailman may be misconfigured that
could be allowing the spammer to spam through it in this way? Or has
my server been hacked?