I am making a serious attempt at installing Mailman 3 using docker. I have a CentOS 7 server setup via Linode. I am using the following documentation to setup a Mailman 3 server:
I have Docker, Postfix, and Nginx installed and working fine. The installation of the Mailman 3 container went fine. However I am getting the following error when I go to test Posterius via shell:
curl: (7) Failed connect to 172.19.199.3:8000; Connection refused
I assume this has something to do with uwsgi which I have no experience with.
Appreciate any assistance with getting Mailman 3 up and running. Thanks!
How can one do this? Raw database access gets you involved in all the usual foreign key constraints.
I don't know how to make use of this information:
After a very large import of decades of data, I need to delete just one wrong mail that is corrupt. I think it is a valid case. I could run the import again after fixing the import mbox, but it takes many hours to load.
I have been recently working on adding rich text support through markdown in Hyperkitty so that emails can be made easier to read. The core design idea in my mind when working on this was building something that doesn't bother writers of plain text emails too much, but allows people to write emails in markdown.
The supported syntax is limited Markdown, for example:
Hyperkitty's Markdown Syntax
- List items are supported
- Even nested ones
- Headers with `#` aren't supported, mostly due to their widespread use as comments in code shared on mailing lists.
- You can **emphasize** text and _itcalize_ them too
- Block code and `inline code` works.
- URLs work like they usually do.
- Images _do work_, but are disabled by default because of their potential for tracking users. They need to be enabled by administrators through a configuration flag.
While text intentionally written for Markdown rending looks pretty good, plain text sometimes isn't as good. I have applied my branch on both the Mailman installations for these two lists (mail.python.org & lists.mailman3.org).
Any feedback or bug reports on weird looking stuff is welcome here or directly [on my PR]
Abhilash Raj (maxking)
I see discussion about this topic here in July. My immediate interest is that I had hoped to move from an antique plain-text only list to modern list software that will support content such as inline images (partly to staunch the flow of subscribers to facebook, simply to be able to post pictures.)
Does hyperkitty support this, and where can one read about that?
Now I am seeing this in the log every few seconds:
12:12:29 [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes]
12:12:29 [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. : Traceback (most recent call last):
File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_q-1.0.1-py3.7.egg/django_q/cluster.py", line 377, in worker
res = f(*task['args'], **task['kwargs'])
File "/opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.2.3-py3.7.egg/hyperkitty/tasks.py", line 189, in _rebuild_thread_cache_votes
thread = Thread.objects.get(id=thread_id)
File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-2.1.9-py3.7.egg/django/db/models/manager.py", line 82, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-2.1.9-py3.7.egg/django/db/models/query.py", line 399, in get
hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist.
Any help? How do I identify the thread in question?
I imported an archive from a Listserv list, processed into something resembling mbox format (which I now understand not to be a standard at all) and have about 100,000 messages there. I am having a lot of trouble with these sort of errors, as you will see from my flurry of posts recently.
Yes, I am running all the jobs.
Would there be a way to show the number of subscribers to a list in the web UI?
The number of participants per message is great, but this would be good too. My users seem very interested in this number. I guess they want to know how big the audience is that is reading their posts.