On 5/11/19 7:43 AM, Web Analysts via Mailman-Users wrote:
> I'm now getting an error when I start Mailman:
>
> root@primeo:~# /etc/init.d/mailman start
> Traceback (most recent call last):
> File "/usr/local/mailman/bin/mailmanctl", line 106, in
> from Mailman import mm_cfg
> File
On 5/10/19 12:37 PM, Jason Morrill wrote:
> Since the beginning of May I've had a problem with all messages going through
> Mailman. They are being delivered to the lists properly but copies are
> staying in qfiles/shunt
>
> The errors appearing in the Mailman error.1 log file indicate
> "
>
On 5/10/19 12:46 PM, Jason Morrill wrote:
> I have messages accumulating in the qfiles/shunt folder.
>
> Running unshunt does nothing. Literally.
>
> No error message, no progress message. The only change I see is the timestamp
> on the shunted messages is updated to when I ran the unshunt
I have messages accumulating in the qfiles/shunt folder.
Running unshunt does nothing. Literally.
No error message, no progress message. The only change I see is the timestamp
on the shunted messages is updated to when I ran the unshunt command.
This is on Debian 9.6 with Python 2.7.13 and
Since the beginning of May I've had a problem with all messages going through
Mailman. They are being delivered to the lists properly but copies are staying
in qfiles/shunt
The errors appearing in the Mailman error.1 log file indicate
"
May 05 10:16:29 2019 (1167) Uncaught runner exception:
I'm now getting an error when I start Mailman:
root@primeo:~# /etc/init.d/mailman start
Traceback (most recent call last):
File "/usr/local/mailman/bin/mailmanctl", line 106, in
from Mailman import mm_cfg
File "/usr/local/mailman/Mailman/mm_cfg.py", line 54, in
