dkim failing
by Abhijith PA
Hello.
I am seeing dkim fail in mail that people send to lists
/dkim=fail reason="signature verification failed"/
but it is not happening when the list solely sending mail to subscribers
(like digest, or subscribe/unsubscribe messages etc). I recently added a
new domain to the mailman3. After this I started noticing this issue.
Any help ?
15 hours, 23 minutes
dkim failing
by Abhijith PA
Hello.
I am seeing dkim fail in mail that people send to lists
/dkim=fail reason="signature verification failed"/
but it is not happening when the list solely sending mail to subscribers
(like digest, or subscribe/unsubscribe messages etc). I recently added a
new domain to the mailman3. After this I started noticing this issue.
Any help ?
Thanks
Abhijith PA
17 hours, 29 minutes
Change digest frequency and default threshold
by Henrik Rasmussen
When creating a new list in Mailman 3, the Digest Size Threshold is set to 30KB, which is not much in my opnion.
1) How do I set another default for Digest Size Threshold for new lists.
2) How do I change the default for existing lists
When Digest Size Threshold is not reached, mails seems to be sent according to digest_volume_frequency': which is set to 'monthly'. The web interface doesn't seem to have a setting for this.
How do I change this setting, both on a single list and the default for new lists?
Henrik Rasmussen
4 days, 15 hours
Archiving error
by Enrique Terrazas
Hello,
I'm hoping someone can help me configure hyperkitty correctly. I've got mailman3 installed and working. I created a test list and can send/receive, moderate message. However, archiving does not seem to be working. Below is a copy of my (sanitized) hyperkitty.cfg file and settings.py file(edited) along with the errors being logged to mailman.log
hyperkitty.cfg
-----
# Mailman-Hyperkitty Archiver plugin
[general]
base_url: http://localhost:8002/
api_key:
-----
settings.py
# Mailman API credentials
MAILMAN_REST_API_URL = 'http://localhost:8001'
MAILMAN_REST_API_USER = ''
MAILMAN_REST_API_PASS = ''
MAILMAN_ARCHIVER_KEY = ''
MAILMAN_ARCHIVER_FROM = ('my.host.name', 'myIPaddress', '127.0.0.1', '::1')
------
This is the error being sent to maillog.log
------
Oct 05 01:54:59 2018 (15127) Exception in "hyperkitty" archiver
Traceback (most recent call last):
File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 171, in _new_
conn
(self._dns_host, self.port), self.timeout, **extra_kw)
File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/connection.py", line 79, in c
reate_connection
raise err
File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/connection.py", line 69, in c
reate_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 600, in urlopen
chunked=chunked)
File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 354, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1239, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1285, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1234, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1026, in _send_output
self.send(msg)
File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 964, in send
self.connect()
File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 196, in connect
conn = self._new_conn()
File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 180, in _new_conn
self, "Failed to establish a new connection: %s" % e)
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f0ba1c22048>: Failed to establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
------
Thanks in advance,
Enrique J. Terrazas
1 week, 4 days
Hyperkitty 1.1.1 to HyperKitty 1.2.1
by Thomas G
Hi,
I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh
install in Mailman3.2.
I didn't found how migrate the archives.
From : HyperKitty - Version: 1.1.1 - Python2.7
To : HyperKitty - Version: 1.2.1 - Python3.5
I exported a mbox from hyperkitty (web interface) and tried to re-import
it, without result.
""""""""""""""""""""""""""""""""""""""""
xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l
listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz
Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to
listedetests(a)hatlab.fr
Computing thread structure
Synchronizing properties with Mailman
Warming up cache
The full-text search index is not updated for this list. It will not be
updated by the 'minutely' incremental update job. To update the index
for this list, run the 'manage.py update_index_one_list
listedetests(a)hatlab.fr' command.
""""""""""""""""""""""""""""""""""""""
The database stay empty (and web interface):
""""""""""""""""""""""""""""""""""""""
mailmandbnameprod=# select * from hyperkitty_email;
id | message_id | message_id_hash | subject | content | date | timezone
| in_reply_to | archived_date | thread_depth | thread_order |
mailinglist_id | parent_id | sender_id | thread_id | sender_name
----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+-------------
(0 rows)
""""""""""""""""""""""""""""""""""""""
Any idea to do this importation ?
Thanks !
1 week, 5 days
Proper permissions for mailman installation under home directory, with layout: local
by Eric Abrahamsen
I recently upgraded my server from Ubuntu 16.04 to 18.04, and have hit
some snags in the process.
I've had my mailman3 installation under my home directory, running as my
own user, without too many problems. var_dir was set to something in my
home directory. Recently, while tracking down some weird behavior, I
realized that with this sort of setup I'm supposed to use "layout:
local", and that previously I'd had a sort of weird half-way
installation where some things were kept in my /home/<me>/sites/mailman
directory, and other bits (pids and whatnot) were scattered around the
filesystem.
Now that I'm using "layout: local", mailman really is trying to keep
everything under that main directory, and now everything's breaking. The
hyperkitty search indexer is saying it has no permissions to write into
that directory, postfix won't deliver mail, saying the mailbox is
unavailable, and in the web UI postorius shows no configured list
domains (though hyperkitty still displays the archives correctly).
So obviously I've got quite a big problem with permissions, but I don't
know how to resolve it. My webserver is nginx, running as www-data. I'm
starting mailman in a systemd script, with User and Group set to my
user -- though maybe that should be set to root? I guess postfix runs as
root, I'm not sure, but obviously it's not able to read the files in
var/data/*, which appear all correct to me.
What's the recommended solution here? I'd still like to keep this whole
directory under my home directory, if possible...
Thanks,
Eric
2 weeks
