I have of course activated password login as it was not possible to get the
provider based logins to work (might be but not worth the time for me right
now). Is there any way for an user to request a new password when it is
I presume that the Persona login is removed now. I cannot hide it in my
version or at least I do not know how.
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:email@example.com>>