I am seeing the error below and wondering what's the cause:
Jul 25 13:35:05 2025 (944) Could not archive the message with id < CO1PR06MB798076961F096CAA4DB9A2FCBB59A@CO1PR06MB7980.namprd06.prod.outlook.com
Jul 25 13:35:05 2025 (944) archiving failed, re-queuing (mailing-list testlist.my.domain, message < CO1PR06MB798076961F096CAA4DB9A2FCBB59A@CO1PR06MB7980.namprd06.prod.outlook.com
) Jul 25 13:35:05 2025 (944) Exception in the HyperKitty archiver:
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css">
</head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Jul 25 13:35:05 2025 (944) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError:
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
On 7/26/25 1:23 AM, Odhiambo Washington via Mailman-users wrote:
I am seeing the error below and wondering what's the cause:
The message has some issue which is causing HyperKitty to not be able to
archive the message. The message will be queued in Mailman's
var/archives/hyperkitty/spool/ directory and can be examined with
mailman qfile. If you do that and the cause is not clear, you can post
the message, and we will investigate. If the message is unwanted, you
can just remove the file from Mailman's var/archives/hyperkitty/spool/
directory.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, Jul 26, 2025 at 8:28 PM Mark Sapiro <mark@msapiro.net> wrote:
On 7/26/25 1:23 AM, Odhiambo Washington via Mailman-users wrote:
I am seeing the error below and wondering what's the cause:
The message has some issue which is causing HyperKitty to not be able to archive the message. The message will be queued in Mailman's var/archives/hyperkitty/spool/ directory and can be examined with
mailman qfile. If you do that and the cause is not clear, you can post the message, and we will investigate. If the message is unwanted, you can just remove the file from Mailman's var/archives/hyperkitty/spool/ directory.
I had examined the message using 'mailman qfile', but did not see anything obvious. There were 3 files inside the spool/ directory. I have just checked again and they are no longer there.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
On 7/26/25 10:35 AM, Odhiambo Washington via Mailman-users wrote:
I had examined the message using 'mailman qfile', but did not see anything obvious. There were 3 files inside the spool/ directory. I have just checked again and they are no longer there.
If the files disappeared, they were eventually successfully delivered
to HyperKitty. If you made no changes to mailman-hyperkitty.cfg, there
was probably some transient network issue that caused the initial error.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, Jul 26, 2025 at 8:49 PM Mark Sapiro <mark@msapiro.net> wrote:
On 7/26/25 10:35 AM, Odhiambo Washington via Mailman-users wrote:
I had examined the message using 'mailman qfile', but did not see
anything
obvious. There were 3 files inside the spool/ directory. I have just checked again and they are no longer there.
If the files
disappeared, they were eventually successfully delivered to HyperKitty. If you made no changes to mailman-hyperkitty.cfg, there was probably some transient network issue that caused the initial error.
Most likely. Another thing I have seen, inside /etc/mailman3/ root@list:/etc/mailman3# ls -al total 40 drwxr-xr-x 3 mailman mailman 4096 Jul 26 10:52 . drwxr-xr-x 110 root root 12288 Jul 26 07:17 .. -rw-r--r-- 1 mailman mailman 948 Jul 25 02:48 mailman.cfg -rw-r--r-- 1 mailman mailman 352 Oct 25 2023 mailman-hyperkitty.cfg drwxr-xr-x 2 mailman mailman 4096 Jul 26 03:11 __pycache__ <===== Is the presence of this directory expected? -rw-r--r-- 1 mailman mailman 4971 Jul 26 03:10 settings.py -rw-r--r-- 1 mailman mailman 863 Jul 25 04:14 uwsgi.ini
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
On 7/26/25 10:55 AM, Odhiambo Washington via Mailman-users wrote:
Another thing I have seen, inside /etc/mailman3/ root@list:/etc/mailman3# ls -al total 40 drwxr-xr-x 3 mailman mailman 4096 Jul 26 10:52 . drwxr-xr-x 110 root root 12288 Jul 26 07:17 .. -rw-r--r-- 1 mailman mailman 948 Jul 25 02:48 mailman.cfg -rw-r--r-- 1 mailman mailman 352 Oct 25 2023 mailman-hyperkitty.cfg drwxr-xr-x 2 mailman mailman 4096 Jul 26 03:11 __pycache__ <===== Is the presence of this directory expected? -rw-r--r-- 1 mailman mailman 4971 Jul 26 03:10 settings.py -rw-r--r-- 1 mailman mailman 863 Jul 25 04:14 uwsgi.ini
Yes, in any directory that contains .py files, when those files are imported, a corresponding compiled byte code .pyc file is placed in a __pycache__ directory. This is normal Python 3 behavior.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Odhiambo Washington