After upgrading to HyperKitty 1.3.x I get the following error for
File ".../lib/python3.7/site-packages/django_q/cluster.py", line 300,
task = SignedPackage.loads(task)
File ".../lib/python3.7/site-packages/django_q/signing.py", line 31,
File ".../lib/python3.7/site-packages/django_q/core_signing.py", line
38, in loads
File ".../lib/python3.7/site-packages/django_q/signing.py", line 44,
AttributeError: Can't get attribute 'process_task_result' on <module
How do I recover from that? It seems like there are still persisted
tasks in the qcluster queue using the old code from 1.2.x with the old
I have a Mailman 3 server up and running but I'm terrified to migrate to it from my existing Mailman 2 provider for fear that services like Gmail will randomly start blacklisting my IP with little I can do about it. I have SPF records set up so I'm hoping I'll be Ok but I'd like to have a backup plan.
Has anyone ever tried using an external service like Mailgun or Sendgrid as a relay? I tried both but couldn't get either to work due to their sender authentication mechanism. They want all 'From:' headers to be from domains that are pre-authenticated as senders. But Mailman keeps the 'From' header from the original sender so it won't match any authenticated domains. Right?
Is there anything to be done here or do I just have to migrate and pray?
Does anyone have any usable Logrotate files for Mailman3 (especially for the web stuff)?
Will look to create my own if no one comes forward but if anyone has anything they are willing to share it would be fab.
I'm new to Mailman and after some failed attempts to install from git on CentOS8, I have just installed it on Ubuntu 20.04 using mostly aptitude. But it's not quite working and I want to increase the log level to better understand the problem. I did see another post that suggested that I add to /etc/mailman3/mailman.cfg
But that doesn't work for me. For example, after using that `mailman conf` doesn't list and debug values and as far as I can tell, the service, even after restarting, is not logging any more than it was. On the other hand, if I add
Invoking `mailman conf` will reflect that new loglevel. This started me down the path of trying to figure out the configuration system of mailman in hope that that will save me time down the road. I have read
https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html but that doesn't seem to agree with what I'm seeing.
For an additional example, my mailman.cfg file has a "logging.debian" section, but I don't see that section listed in the `mailman conf` output. Why would that be?
I don't see in the documentation if `mailman conf` only sees values after the service is restarted. Nevertheless, restarting mailman hasn't helped.
What guidance can you give?
Context: `mailman info` produces:
GNU Mailman 3.2.2 (La Villa Strangiato)
Python 3.8.2 (default, Apr 27 2020, 15:53:34)
config file: /etc/mailman3/mailman.cfg
db url: sqlite:////var/lib/mailman3/data/mailman.db
REST root url: http://localhost:8001/3.1/
REST credentials: restadmin:KI5TuWE/v.....
In mailman 2, few of my users used to approve the held messages
through the mail by writing Approved: header and the password of the list
in the first line of the reply mail to the "confirm" attachment in the mail
notification of the held messages.
But after I started migrating my distribution lists from mailman
2 to mailman 3, my users are complaining that they could not approve the
posts or the held messages through the mail as they usually do while they
were browsing their lists in mailman 2.
Is there any bug or limitation in mailman 3 or if I am doing
any wrong at the server side? Please suggest.
Thanks & Regards,
I am having a curious problem with just ONE list management page for ONE list on my server. Every other list I've checked, and every other management page for this affected list, seem fine. But when I go to the Subscribers page for this one list I get a Server 500 error, and I can't find anything in the apache or mailman logs to give me a clue (granted I'm not sure I know for sure where all the different logs are).
So specifically this page: https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org…
For a list called "alarms-all" obviously. Any ideas? I'm able to review the list, it's members, etc in the PostsgreSQL tables and I'm not seeing any members with funky characters in their address - the one thing I could think of to check.
Does Mailman generally send email with a null sender?
This is what I see in the log:
Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) handling connection
Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'LHLO mail.example.coop'
Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'MAIL FROM:<>'
Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) sender: <>
Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'RCPT TO:<techque-bounces(a)example.org>'
Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) recip: techque-bounces(a)example.org
Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'DATA'
Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'QUIT'
Notice the empty MAIL FROM.
Sendgrid seems to be choking on that because it needs to check if sending domain has been validated. If there is no sending domain it seems to reject.
Why does Mailman do this? Can it be changed? I've been trying to find the relevant section of the code to no avail.
I'm trying to set up mailman3 on two hosts, one of which runs core +
exim, the other runs postorius (&possibly hyperkitty).
I have I think got core set up correctly, and postorius is sort of
usable, but anything in the web ui that talks to core ends up with a
I think what is happening is a postorius URL ends up with the core (or
perhaps no) hostname, and as there's nothing there to answer it fails.
I've checked the settings and I don't think I have misconfigured
postorius. Is it possible that the bad url is being passed from core to
postorius in some way and reused without changing the host?
In the config at present, both hosts are visible to the browser, and
each host can communicate with the other.
Any ideas on how to pin down the problem better?