I want to whitelist an email address on all lists to bypass moderation.
The email address is not a subscriber. On google I
found accept_these_nonmembers but I do not know how to use it.
Please show me some examples how to whitelist someone(a)example.org.
Thanks in advance.
I saw in the docs:
> We have it! We just don’t have proper documentation here yet.
Could you please be more specific - can I switch Mailman 3 installation to
Hello all ,
I configured mailman3 following this contributer guide http://docs.mailman3.org/en/latest/devsetup.html but i'am still getting problem with the configuration of MySQL and postfix . Is this section is enough for MySQL configurations ?
url: mysql+pymysql://myuser:mypassword@mymysqlhost/mailman?charset=utf8&use_unicode=1htmlI will appreciated if there are some documents to provide to cotinue the intergration of mailman3 .
Is there any tuto for postfix config ?
Thanks in advance
#129 says that private lists are visible in the archive overview only
but "archives aren't displayed".
However, I can browse a private list's archives and read the mail text
while not logged in. Shouldn't the private archive be hidden from
I have an active list for which I am trying to debug some deliverability
issues. When a user tells me that folks aren't getting their postings, I
check the archives first. In this case, I am getting a traceback saying
"thread matching query does not exist" when I try to go to the HyperKitty
page for the list. How can I debug this?
I am using Mailman 3 via the Docker containers documented here:
The container versions appear to be 0.1.
I currently run MM3.0 based on the old bundle installation. It seems
to work just fine although with a number of minor and major annoyances
that probably have been fixed now.
What is the rekommended way to upgrade to the newest version? (newest
_usable_ version, of course)? Is it docker-only with a migration from
the current solution to a docker based? If so, any ideas or pointers
on how to go about this?
* Docker-mail 0.1.1
* Mailman 3.1
* Postorius 1.1.1
* Hyperkitty 1.1.1
Settings -> Message Acceptance -> Acceptable aliases has a default of  resulting in "An error occured: [u'']" when saving. This fiend should be empty by default or at least accept the default when saving.
To me the description right under the Acceptable aliases field is not user friendly. It doesn't explain the purpose of the field, but is meant for the Mailman sysadmin, not the list admin who can't be expected to understand this. A much better description would be the ones used for MM2:
On a second note: Where I can change the field and message descriptions in MM3, like the /usr/lib/mailman/messages/[sprog]/LC_MESSAGES/mailman.po in MM2?
Henrik Rasmussen <her(a)adm.ku.dk<mailto:firstname.lastname@example.org>>
(With the hope that someone on the list can help me diagnose this problem, I’m posting a copy of the HyperKitty issue that I opened a few days ago: https://gitlab.com/mailman/hyperkitty/issues/151.)
Testing MailMan3, installed using the Docker containers 0.1.1 (with HyperKitty 1.1.1):
I have two lists with several discussions in each. The participants/comments stats for all discussions show multiple participants and multiple comments. (Note that the numbers are wrong, as discussed in #149.)
However, when I open a discussion, some of them only display the first message. Others display all messages, one displays only some, but not all, of the messages. In one case, the discussion showed the top two messages, but when a new message was added, it briefly showed and then it and the second message suddenly disappeared, leaving only the first message. In another case, the discussion only showed the top message, but then, for no apparent reason, the rest of the messages appeared.
I decided to start all over, removing the Docker containers and images, as well as the existing database... all gone.
With the newly created system and database, I created two new lists and three member-subscribers. I then created new threads and added several messages to the new threads. The messages came from all three of the members and were entered via email and HyperKitty. One thread was created from within HyperKitty.
All of the newly created threads are displaying the same behaviour: all of the subscribers received, via email, all of the messages, but only the first message of each thread is displayed in HyperKitty.
Suggestions for how to trace/diagnose the problem would be appreciated.