Dear all,
this may be of course related to Debian version of Mailman3 (currently 3.3.3,
Debian 11 Bullseye), but I hope someone may point me towards a direction in
which i should start digging in order to resolve this issue.
I have recently migrated two lists from perfectly working MM2 to MM3
On 10/13/22 13:33, gr...@mm.st wrote:
What is however important, is that for both lists mailman3 generates
approximately every minute a message that it tries to send to the list and the
message is catched by the mailman and requires moderation. As a result, I have
some 1000 moderation request
Now I will start over ...
First of all: do you recommend the debian package install or the manual one?
```
Package mailman3:
p 3.3.3-1
stable
On 10/14/22 09:56, Martin Lorenz wrote:
Now I will start over ...
First of all: do you recommend the debian package install or the manual one?
```
Package mailman3:
p 3.3.3-1
OK
thanks for the advice.
I started installing following the path ...
the first error I hit is:
```
(venv) mailman@arda:/etc/mailman3$ mailman-web migrate
Traceback (most recent call last):
File
"/opt/mailman/venv/lib/python3.9/site-packages/django/template/utils.py", line
66, in __getitem__
On 10/14/22 13:59, Martin Lorenz wrote:
OK
thanks for the advice.
I started installing following the path ...
the first error I hit is:
```
...
File "/opt/mailman/venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py",
line 6, in
from mistune.plugins.extra import plugin_url
Mo
thanks, that one did the trick
I think I kint of got ist up and running now.
this ist how the site looks:
https://list.poc.im/mailman3/lists/
I don't think, it should be like that.
I already added
```
location /static/ {
alias /opt/mailman/web/static;
}
```
to my nginx config, b
heureka!
added two lines to the nginx config and now it seems up and running ...
_location_ now looks like this:
```
location / {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
prox
i think, I hit a bug
I had mailman up and running, sent testmails to a testlist, used the
webinterface ...
but than I played around with the domains.
I had added one of my domains for the test list but in the archive interface I
still had "example.com" as a header. so I switched over to the
everything is nice and silky again ...
that's what I finally did to the database:
```
sudo -u postgres psql
postgres=# \connect mailmanweb
mailmanweb=# insert into django_site(id, domain, name) values (1,
'example.com', '');
INSERT 0 1
mailmanweb=# insert into django_mailman3_maildomain(id, mail
On 10/14/22 16:42, Martin Lorenz wrote:
everything is nice and silky again ...
And your site looks good to me.
If you have further questions about this, please join the
mailman-us...@mailman3.org list at
https://lists.mailman3.org/mailman3/lists/mailman-us...@mailman3.org/
and post there.
11 matches
Mail list logo
