Hi,
since migration from mailman2 to mailman3 I had twice the following, last time today:
When sending a mail to a list I get the following reply from postfix after a while:
connect to 127.0.0.1[127.0.0.1]:8024: Connection refused
Searched on that and found some posts, where the following shell command is named to check what is running:
ps -fwwu mailman
And I get this as output:
UID PID PPID C STIME TTY TIME CMD
mailman 1166 1 0 Jan07 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/master -C /opt/mailman/core/mailman.cfg
mailman 1180 1166 0 Jan07 ? 00:03:09 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1
mailman 1212 1180 0 Jan07 ? 00:01:10 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1
mailman 11039 11036 0 06:25 ? 00:00:03 /usr/bin/uwsgi-core --ini mailman3.ini
mailman 11064 11039 0 06:25 ? 00:00:00 /usr/bin/uwsgi-core --ini mailman3.ini
mailman 11065 11039 0 06:25 ? 00:00:01 /usr/bin/uwsgi-core --ini mailman3.ini
mailman 17257 1180 0 Jan12 ? 00:00:37 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1
Lots of expected runners are missing. After restarting the service the output of the same command is:
UID PID PPID C STIME TTY TIME CMD
mailman 11039 11036 0 06:25 ? 00:00:03 /usr/bin/uwsgi-core --ini mailman3.ini
mailman 11064 11039 0 06:25 ? 00:00:00 /usr/bin/uwsgi-core --ini mailman3.ini
mailman 11065 11039 0 06:25 ? 00:00:01 /usr/bin/uwsgi-core --ini mailman3.ini
mailman 14430 1 13 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/master -C /opt/mailman/core/mailman.cfg
mailman 14434 14430 18 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=archive:0:1
mailman 14435 14430 20 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=bounces:0:1
mailman 14436 14430 18 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=command:0:1
mailman 14437 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=in:0:1
mailman 14438 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=lmtp:0:1
mailman 14439 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=nntp:0:1
mailman 14440 14430 19 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=out:0:1
mailman 14441 14430 20 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=pipeline:0:1
mailman 14442 14430 20 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1
mailman 14443 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=retry:0:1
mailman 14444 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=virgin:0:1
mailman 14445 14430 18 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=digest:0:1
So now back to good. I checked all the logs prior to restarting the service in directory /opt/mailman/var/log, but I do not see any errors. And the master was still running, I would expect that the master will start / restart a runner in case it died?
Fun fact: First time of this problem was two weeks from now, which was two weeks after migration to mailman3. I'm excited if it will happen in two weeks again.
Installed packages for core:
mailman (3.3.0)
mailman-hyperkitty (1.1.0)
Any suggestions where I should have a deeper look and maybe find the root cause of this problem?
Thanks in advance
Torge
Hi,
we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, here is the first, second comes in a separate post:
The list moderator currently receives a copy of the original mail in the info mail he gets for moderation. This is bad in case it was a SPAM mail, cause we have seen that such an info mail is detected also as SPAM. That might rise problems cause other mail servers might block the info mail as SPAM and if this happens too often blocking the whole server. I fear. At least I see that my rspamd starts learning the info mail as SPAM. I don't want that to happen.
I searched mailman web interface for a setting to disable adding a copy to the info mail. But have not found it. Is it missing or where do I have to look?
Best regards
Torge
Hi,
we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, this is the second question:
Such SPAM mails are currently hold for moderation with reason "not from a list member". Is there no check for the "X-Spam: Yes" header or is this check done later? I would prefer that a check for such a header is done first and is reported as the reason. Which is IMHO a very important information. Or maybe show "This is detected as SPAM" in big bold red letters in a new column in the list of mails to moderate for such a mail. Maybe there is more eye-candy solution for it.
Sometimes mail accounts of allowed users are hacked and we do not want spread SPAM accidently. On my setup all mails are checked by rspamd before local delivery and I see that the "X-Spam" header is set for such mails. So even mails from allowed members with header "X-Spam: Yes" should be hold for moderation. Maybe this is already the case, did not gave it a try yet.
Best regards
Torge
Hi Everyone,
Hope everyone had a great weekend!
I am pleased to announce new set of releases:
- Postorius 1.3.2
- Django-mailman3 1.3.2
- Hyperkitty 1.3.2
This release was required as it turned out 1.3.1 releases did not includes translations in the tarballs that I created and uploaded to PyPI. They do include a couple of bugfixes and more translations.
- Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1)
- Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1)
All three of these releases also officially drop support for Django 1.11. Although, there hasn't been any code change that breaks compatibility with 1.11. It has just been dropped form our CI machinery since our dependencies no longer support 1.11.
All the releases are available on PyPI, as usual!
--
Thanks
Abhilash Raj
Our MailMan3 server is extremely slow and when trying to list or export members for a larger list it is throwing 'Mailman REST API not available. Please start Mailman core'. In Mailman core logs I am seeing
[27] [CRITICAL] WORKER TIMEOUT (pid:40)
[43] [INFO] Booting worker with pid: 43
Has anyone seen this issue? Is there any way to increase 'timeouts'?
Thanks for any help!
Tom
Mailman Novice
16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com/roster/owner HTTP/1.1" 200 634 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/list.somelist.com/roster/moderator HTTP/1.1" 200 638 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/somelist(a)somelist.com/config HTTP/1.1" 200 2257 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:05 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:10 +0000] "GET /3.1/lists/list.somelist.com/member/somelist@somelist HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:16 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:19 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:26 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0"
[2020-01-16 16:56:58 +0000] [27] [CRITICAL] WORKER TIMEOUT (pid:40)
[2020-01-16 16:57:00 +0000] [43] [INFO] Booting worker with pid: 43
DISCLAIMER: The information contained in this message is privileged and confidential. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the message and delete/destroy any copy of this message. Information in this message that does not relate to the official business of the firm shall be understood as neither given nor endorsed by it.
Hi,
I configured Postorius (via Apache2) to use https, which looks fine. But
the connection to hyperkitty failed with "code 400, message Bad request
syntax". I tried serveral settings....without success. Could you give me
an example, which settings are to configure?
Thanks for your help!
--
Dieter
is there a tutorial or some examples for using the mailman shell? Is there detailed documentation on it?
Anything I try to do such as the following fails:
$ mailman shell
Welcome to the GNU Mailman shell
>>> command('mailman shell --details')
Traceback (most recent call last):
File "<console>", line 1, in <module>
NameError: name 'command' is not defined
>>>
I execute the shell as user mailman and from within the same venv that all the programs run under.
Hi all,
I’m still working on setting up my lists in a domain that was added after MM3 installation.
It’s mostly working but the Postorius page and the ‘noreply’ emails still sport the old domain name. I hav looked at all the py and cfg files where the old name appeared, and they no longer hold the old name. My coadmin now tells me that the database has a table with the old name. Any suggestion as to whether that can cause the issue and if it’s safe to change the table.
Yours,
Allan Hansen
P.O. Box 2423
Cypress, CA 90630
Ubuntu 20.04
mailman3 3.2.2-1
mailman3-web 0+20180916-10
python3-django 2:2.2.9-2ubuntu1
In ```/etc/mailman3/uwsgi.ini``` (example.org is defined in the local /etc/hosts as 10.0.0.1):
```
[uwsgi]
# Port on which uwsgi will be listening.
### suwsgi: uwsgi protocol over TLS
uwsgi-socket = example.org:8430
# https://uwsgi-docs.readthedocs.io/en/latest/HTTPS.html?highlight=ssl
https = /etc/ssl/example.org.crt,/etc/ssl/example.org_rsakey.pem.decrypted,HIGH
...
# Drop privileges and don't run as root.
uid = www-data
gid = www-data
...
```
I suppose that uwsgi reads the certificate & its private key before dropping root privileges. Right now, uwsgi cannot access them as ```www-data```.
In ```/etc/mailman3/mailman-web.py``` (symlinked to django settings.py) :
```
...
SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_SCHEME', 'https')
# Other security settings
# SECURE_SSL_REDIRECT = True
# If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT
# contains at least this line:
# SECURE_REDIRECT_EXEMPT = [
# "archives/api/mailman/.*", # Request from Mailman.
# ]
# SESSION_COOKIE_SECURE = True
# SECURE_CONTENT_TYPE_NOSNIFF = True
# SECURE_BROWSER_XSS_FILTER = True
# CSRF_COOKIE_SECURE = True
# CSRF_COOKIE_HTTPONLY = True
# X_FRAME_OPTIONS = 'DENY'
...
POSTORIUS_TEMPLATE_BASE_URL = 'https://example.org:8430'
```
In ```/etc/nginx/sites-enabled/example.org.conf```
```
...
location /
{
include /etc/nginx/uwsgi_params;
# upstream app server
uwsgi_pass suwsgi://example.org:8430;
}
```
uwsgi is listening on the right address/port:
```
# networks-list-connections.sh | grep :8430
tcp 0 0 10.0.0.1:8430 0.0.0.0:* LISTEN 33 54336045 1768187/uwsgi
```
Despite those settings and all the relevant systemd services restarted, I get ```502 Bad Gateway``` while browsing to ```https://example.org/postorius/lists/?all-lists``` (or any other page) with the following error nginx message:
```
*1 peer closed connection in SSL handshake while SSL handshaking to upstream, client: 10.0.0.1, server: example.org, request: "GET /postorius/lists/?all-lists HTTP/2.0", upstream: "suwsgi://10.0.0.1:8430", host: "example.org", referrer: "https://example.org/postorius/lists/"
```
Of course, without those specific https/suwsgi settings, everything works fine.
What am I missing/doing incorrectly? Does uwsgi need access to the certificate/private key while running as non-root for instance?
Hi
I haven't found out where I could choose or edit default list values
(when creating new list).
For example I would like that all new lists would be with *private
archive* (and change this when it is needed).
This is great that I can choose not to advertise list in Index (which I
can choose from list creation interface) but I would like to choose
other options too.
Right now only solution is to create list and then choose Archiving and
then select "private archives".
Another thing is that I would like to choose default subscription policy
to "Moderate".
If anyone has encountered this problem, let me know!
All the best
Sten
