The mailman process for <armedbear-devel@…> seems to be stuck, as my message from Thu Nov 14 14:20:35 2019 is still in the file://common-lisp.net/var/lib/mailman/qfiles/in/ folder as
If this in indeed the outstanding incoming queue for mailman, it contains 1729 messages that haven’t been processed since Oct 27 19:30.
I am now looking for how mailman processes this queue, slowly working through how to fix as I get the time, but if someone (Erik?) could step in to take a look to save me the unknown amount of time to figure this out, I would appreciate it.
We’ll see if this message gets delivered…
On Nov 15, 2019, at 16:39, Mark Evenson evenson@panix.com wrote:
The mailman process for <armedbear-devel@…> seems to be stuck, as my message from Thu Nov 14 14:20:35 2019 is still in the file://common-lisp.net/var/lib/mailman/qfiles/in/ folder as
The mailing lists hosted @common-lisp.net had not been delivering messages since October 26th. We restarted the service, and the backlog of messages has been injected into SMTP over the last hour. We apologize for the inconvenience.
On Nov 15, 2019, at 18:43, Mark Evenson evenson@panix.com wrote:
The mailing lists hosted @common-lisp.net had not been delivering messages since October 26th. We restarted the service, and the backlog of messages has been injected into SMTP over the last hour. We apologize for the inconvenience.
Once again, he mailing lists hosted @common-lisp.net have not been delivering messages since March 4th. We restarted the service, and the backlog of messages has been injected into SMTP over the last hour. We apologize for the inconvenience.
-
Mark Evenson