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?
In a long thread I asked this but have not gotten a clear enough explanation.
Presumably, to insure fewer problems with users of Yahoo etc,, there seem to be two settings:
1) Alter messages
2) Dmarc mitigations
I don’t understand how my choice in one affect the other, if they do even,
Two experts have tried to help, but I think I need a little hand holding.
I understand there is no consumer ready manual and all I have found us this:
REPLY GOES TO LIST (alter messages)--current settings
REPLACE FROM: with list (DMARC mitigations) -> current settings
DMARCH Mitigation YES OR NO (DMARC mitigations)--> currently NO
I was told that Dmarc mitigations YES might prevent people from not getting mail
How about Replace from with list?
How about reply goes to list?
In other words, what is the relationship between these two different menu items and the effect of the settings in one on the settings of the other?
Can anyone help a confused would be happy user?
If so, what about the Alter Messages settings:
In the annoucement mail, the new version is
- Mailman Core 3.3.0 (Tom Swayer)
but on my webpage I see:
Mailman Core Version GNU Mailman 3.3.0 (La Villa Strangiato)
Mailman Core API Version 3.0
Mailman Core Python Version 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC 8.3.0]
Why is the version name from the previous release?
is my setup wrong?
[There are so many issues I keep reporting here about Mailman that get no response that I wonder if there is something fundamentally wrong with my site.]
Hi. All the project installation is under the same user / path and
it works. Archiving working as well, (just one remark: no matter what to set in postorius, hyperkitty shows list as public)
I have found work around - it is possible to change list as private in "admin" page.
I started to get issues with runjobs after I have created couple of new lists with "no archive" option.
If as owner user from project home I run:
Traceback (most recent call last):
line 84, in _execute
return self.cursor.execute(sql, params)
line 383, in execute
return Database.Cursor.execute(self, query, params)
sqlite3.OperationalError: attempt to write a readonly database
"django-admin runjob sync_mailman " - makes read only errors as well.
"django-admin runjob new_lists_from_mailman"
django.db.utils.OperationalError: attempt to write a readonly database
I did not find information how to fix this. It was worked without errors
I noticed, that if I stop mailman, "django-admin mailman_sync" starts to work.
If I start "mailman start", then "django-admin mailman_sync" failing again.
I did not check other jobs, but I think what is related to database, will get errors.
Seems mailman locking the database. It is not a file permissions issue.
Mailman db location is: /project_directory/var/data/mailman.db
if to rename /project_directory/var/data/mailman.db to something, mailman creates database file size 0, django-admin runjobs start working, but of course postorius stops working. I did it for testing. I have returned this database file back, postorius started to work again, but django-admin runjobs does not work, error: "database read only".
Please help me how to fix this issue.