This is one thing I am confused about. The explanations in the settings about No Munging, etc. are not completely clear.
What I want to make sure, since this is a discussion list, is that most messages go to the mailing list, not to individuals. I plan to put something in one of the templates to remind people that a reply goes to the discussion list. If they do not want to send it to everyone, they should send to the original poster.
1) I understand there are plusses and minuses but I am not sure I understand the explanation given. If it IS preferable to use NO MUNGING, how do I make sure that this is easy to accomplish?
2) I can put something in the footer of every message to remind people, but first I need confirmation of what I should choose in this section. Thanks in advance.
I have read documentation, but still have stupid questions, could You please help, because I can't make it working. I do not understand something important. I have no experience with python at all. I have mailman 3, python 3.5 in my debian OS system, and additional packages like uwsgi and ect. using https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman… about till chapter 6. I understand mailman suite has hyperkitty already. But I am not sure about:
1. Does mailman-suite have hyper-kitty inside? Because if I run $python manage.py runserver - it runs. In installed it under dedicated OS user home and fonfigured to run.
I can create lists, event add lists to hyperkitty page using: $django-admin runjob new_lists_from_mailman list server sends messages to list members as well. But nothing happens more. No emails come to hyperkitty, arciver log 0 size.
$ python manage.py runjobs -l shows the lists of the jobs, so seems nothing to add.
Except uwsgi.ini, I have only 2 configuration files in mailman-suite project directory: settings.py and mailman.cfg So I do not understand what did I configured badly.
2. If I (using Postorius web interface) add footer template to my list under regular message, something strange happens. Mailman stops to send messages for list members. No any entries in the logs. Just Mailman log writes: "unable to connect localhost port 25" and no more explanation. If I delete list's footer template (web interface), mailman starts working again. What is bad here? How to add custom footer? In mailman 2 if was working so good and was easy to setup.
Could You please confirm that this parameter should be placed in
I have checked mailman/postorius/hyperkitty owner user can write files
there and web user group
has privileges to write and to read, but *no any files appear there*.
Mailman works, it is possible to download
attachments from hyperkitty. Mailman restarted, uwsgi restarted, runjobs
restarted. No files in
File looks like:
HYPERKITTY_ATTACHMENT_FOLDER = /full/path/to/folder/
2019-09-11, tr, 21:21 Ugnius S <ugniusviln(a)gmail.com> rašė:
> Thank You so much.
> 1) https://hyperkitty.readthedocs.io/en/latest/install.html
> Close to the end before the "UPDATE" topic, chapter "Customization".
> Page 10, chapter 2.8 "Customization"
> 2019-09-11, tr, 20:16 Abhilash Raj <maxking(a)asynchronous.in> rašė:
>> On Wed, Sep 11, 2019, at 9:52 AM, Ugnius S wrote:
>> > Hi.
>> > Can anybody send example how to set it? It is mentioned in
>> > but very vaguely.
>> If you can point out where did you find it in docs, I can update it.
>> Information is kind of duplicated in a few places.
>> > HYPERKITTY_ATTACHMENT_FOLDER = /full/unix/path
>> This is the right value.
>> It is a path on the filesystem, where the user running Hyperkitty is
>> allowed to write.
>> > HYPERKITTY_ATTACHMENT_FOLDER = http://localhost:8000/something
>> > HYPERKITTY_ATTACHMENT_FOLDER = ./var/data/something/
>> > Has anybody experience of using this, maybe have recommendations of
>> > it? Better under project user or better under web content owner where
>> > static content is. I would like to store attachments separately to avoid
>> > growing database.
>> > Hyperkitty documentation:
>> > By default, HyperKitty stores the email attachments in the database.
>> > you would rather have them stored on the filesystem, you can set the
>> > HYPERKITTY_ATTACHMENT_FOLDER configuration value to a directory.
>> > Make sure that the user running the Django process (for example, apache
>> > www-data) has the permissions to write in this directory.
>> > -------------
>> > _______________________________________________
>> > Mailman-users mailing list -- mailman-users(a)mailman3.org
>> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org
>> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>> Abhilash Raj (maxking)
>> Mailman-users mailing list -- mailman-users(a)mailman3.org
>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
Can anybody send example how to set it? It is mentioned in documentation,
but very vaguely.
HYPERKITTY_ATTACHMENT_FOLDER = /full/unix/path
HYPERKITTY_ATTACHMENT_FOLDER = http://localhost:8000/something
HYPERKITTY_ATTACHMENT_FOLDER = ./var/data/something/
Has anybody experience of using this, maybe have recommendations of using
it? Better under project user or better under web content owner where the
static content is. I would like to store attachments separately to avoid
By default, HyperKitty stores the email attachments in the database. If
you would rather have them stored on the filesystem, you can set the
HYPERKITTY_ATTACHMENT_FOLDER configuration value to a directory.
Make sure that the user running the Django process (for example, apache or
www-data) has the permissions to write in this directory.
My server uses https connection. According this error seems that
certificate of course has not localhost written in it:
port=443): Max retries exceeded with url: /mailman3/api/
templates/list/example.com/list:user:notice:welcome (Caused by
SSLError(CertificateError("hostname 'localhost' doesn't
match either of 'listserv.example.com', 'example.com', 'www.example.com
Second question, is archiver template example:
$hyperkitty_url: Permalink to archived message in Hyperkitty
If to set as in the example, then it add " : " to the end of the line, and
link does not work. I would recommend to update it.
My question is: My server's address is listserv.example.com, but mailman
to email message variable $hyperkitty replaces like https://example.com/....
What does then happen? https://example.com does not point to my web
interface address. I have resolved it with the Apache2 redirection tools,
but is it possible to set it correct in mailman's configuration?
On Debian, in the process of setting up Mailman 3.3.0 I'm getting:
$ pip3 install postorius
django-mailman3 1.3.0 has requirement Django<2.2,>=1.11, but you'll have
django 2.2.5 which is incompatible.
Successfully installed Django-2.2.5 ...
Which may or may not be causing a later error when creating superuser:
ImportError: No module named django.core.management
Am I missing the obvious somewhere?
New question about configuration, maybe somebody has experience and know
what I should change it. I have tried to implement Google authorisation.
I have created Google credentials keys and successfully added using Django
I use UWSGI proxy for apache setup like "ProxyPass / http://127.0.0.1:8002",
UWSGI runs on 0.0.0.0:8002. (So Appache from external address redirects to
internal) What happens when I try Google auth...
If I set Authorised redirect URIs:
http://lists.example.com/accounts/google/login/callback/ , Google gives me
error 400 Error: redirect_uri_mismatch and requests for:
If I set that requested address to Google, then Google authorises me,
but and after authorisation redirects to
http://127.0.0.1:8002/accounts/google....../.... (very long line) Of
course this internal address does not open, but...
If I just manually replace part of address just: http://127.0.0.1:8002
replace to https://lists.example.com/.../...(long line) this makes me get
in as authorised user to the page.
How to make django to send external request to Google? Because
Google should not point back to internal address... This seems simple, but
I do not find what I should change in the configuration: Apache or Django
or uwsgi.ini I hope anybody of You have experience and made it to run.
Latest upgrade version has not improved matters. When I download, the file is generated but it is ten bytes long and obviously therefore corrupt.
Why am I the only one seeing this error?
What can I do to diagnose it?