As a web hosting provider I have searched and searched for a way to limit the total size of messages posted to all lists. We have moderators who just can't get it through their heads to limit the size of attachments. One list today distributed a 6 mb pdf to over 700 recipients. I have found information on creating a custom handler and some old and brief logic on limiting max_message_size from Mr. Sapiro.
Would anyone who has developed a custom handler to reject messages based on total size, mind sharing the full file? If so, could you also state where the handler was positioned in the chain of handlers.
Thank you for your time.
I have a problem with my Mailman 3-setup. The symptom is that postfix
rejects non-existing addresses for my list domains with
<adr(a)example.com>: mail for example.com loops back to myself
What I guess happens happens is that postfix for some reason accepts
the mail as it is for a relay domain and finds that it is not
deliverable locally as the address does not exist locally and then
tries to relay it on to the appropriate MX server, which is itself and
then fails and generates a bounce message.
This is a bit annoying as I have set up postfix to only accept valid
addresses. I have set the transport_maps, local_recipient_maps and
relay_domains to the files generated by MM3. I run an older version of
MM3 (3.0) but prefer to fix this without upgrading as upgrading is a
relatively big undertaking.
This is mostly a backscatter problem for spam I guess.
Any ideas of very simple and easy to forget things that I've probably missed?
we've migrated a list from another domain and would like to keep the
archives. Hyperkitty doesn't recognize the emails in the mbox archive
during import due to the other domain name.
As a workaround we thought of creating a placeholder list with the
original and than import the mbox. But actually I don't like to have
dysfunctional lists in the domain list. Is it possible to set domains
Or is there a switch to import a list from another domain?
Hi to all,
even after a lot of google search I could not find a way to disable the
Confirmation Mails like
The results of your email command are provided below.
- Original message details:
Is there a way to do this? I have users who would be irritated and I
dont want them to recieve this
it seems like the way mailman3 processes header filters is a bit
With a header filter (HeaderMatch) like the following:
header => from
pattern => .*(a)freesources.org
chain => accept
I expect mails from *(a)freesources.org to be accepted regardless of the
default message acceptance settings.
Apparently, that's not the case. If the default message acceptance
setting for members is set to "reject", then mails from
*(a)freesources.org get rejected even though the header filter says
"accept". In other words, the default message acceptance action seems to
overrule any header filters.
Is this expected behaviour?
Our group of 30 plus people have the perennial problem in MM II of not checking previous messages before replying.
A second problem is starting a new topic rather than responding to a message in the same topic, which makes searching even harder.
I previously suggested a forum or something like Stack or Flock. People had no interest in a Word Press forum yet moan about the inefficiency of a list, also it is something new and involves leaving email. Stack and Flock make it hard to require all to be a member of all topics in their free versions.
Then it occurred to me, the threaded view in Mailman III looks good and could help us nudge people back on topic.
Am I being too optimistic.
It is a closed group only open to people we approve.
I would like to migrate to MM III but lack the technical skills to fo this? Anyone who could do this for a fee?
We probably do not need to bring in the old topics. (I guess there us no way like a forum to limit the topics but at least we could keep things on track).
Japan Association for Language Teaching
Sent from my iPhone
Hi to all,
I am trying to setup mailman3 with the Docker Image. Everythings works
relative nicely but I am blocked by the Postfix integration part.
I have a small postfix server that is delivering mails to known domains
and an alias map. The standard use case assumes that the external
postfix is only routing mails to the mailman lmtp. If I do this all my
old users are recected.
I am looking for an example(s) to integrate mailman into a Postfix
configuration as an additional target for postfix.
We're currently piloting Mailman3 to replace a failing Ecartis installation. We've had to push back our go live date several times due to stability issues with our Mailman 3 installation. We currently have Mailman core 3.2.0 running on Red Hat Enterprise Linux 7.5 with 2 vCPUs, 8GB RAM and 25GB swap space. Occasionally, we see mailman become unresponsive both via the REST API and the web UI. We haven't seen anything glaring in the logs but would be happy to check further. I know Mailman 3 powers many large lists and would appreciate any performance, stability and tuning information that can be provided.
I've been using mailman2 for quite some time and I am considering upgrading
to mailman3. In a test setup I noticed that mailman3 with just a basic
setup (Debian with mailman3 package and sqlite as backend using exim4)
uses over 700MB RAM (RSS):
| USER VSZ RSS COMMAND
| list 73072 54568 /usr/bin/python3 /usr/lib/mailman3/bin/master
| list 73100 54500 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=archive:0:1
| list 73100 54572 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=bounces:0:1
| list 73100 54560 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=command:0:1
| list 73100 54600 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=in:0:1
| list 146832 54700 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=lmtp:0:1
| list 73100 54808 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=nntp:0:1
| list 73100 54652 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=out:0:1
| list 73100 54504 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=pipeline:0:1
| list 150516 58228 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=rest:0:1
| list 73100 54508 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=retry:0:1
| list 73100 54500 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=virgin:0:1
| list 73100 54608 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=digest:0:1
This is with only one test list configured that just has one member.
Compared to a mailman2 setup with many lists with up to 300 members that
only uses around 70MB RAM:
| USER VSZ RSS COMMAND
| list 63724 1396 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -q start
| list 62896 10660 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
| list 61156 1792 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
| list 58148 1808 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
| list 73116 23316 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
| list 55464 1672 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
| list 65840 11868 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
| list 62036 10840 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
| list 58716 5712 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
This is without hyperkitty or a management interface, just mailman3 core
that uses 10 times as much ram as mailman2. Did I do something wrong
here? Is there probably a bug in my python environment? Are there any
config options that I should set to avoid this huge memory footprint?
I found one thread on this mailing list where a user asked a question
similar to mine with comparable numbers.