I created a list, did migration from 2.1 and run update_index_one_list. Then I posted a test mail to the list and it got distributed and was seen in the archive. Now 2 days later it does no longer show up in the archive.
What is going on here? May this have to do with HYPERKITTY_RENDER_INLINE_IMAGE which I have turned on meanwhile.
Clueless, Axel
PGP-Key: CDE74120 ☀ computing @ chaos claudius
On 1/21/22 3:06 PM, Axel Rau wrote:
I created a list, did migration from 2.1 and run update_index_one_list. Then I posted a test mail to the list and it got distributed and was seen in the archive. Now 2 days later it does no longer show up in the archive.
What is going on here? May this have to do with HYPERKITTY_RENDER_INLINE_IMAGE which I have turned on meanwhile.
It may. Is there anything in Django's log about this? If you have the original message from the list, can you go to the URL in the Archived-At: header? is the message in the hyperkitty_email table in the database? E.g.,
SELECT * FROM hyperkitty_email WHERE message_id_hash ='xxx';
(xxx is the value of the Message-ID-Hash: header from the message)
If the prototype archiver is enabled for the list, the message should be in Mailman's var/archives/prototype/list@example.com/new directory and that message will have the Archived-At: and Message-ID-Hash: headers.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Am 22.01.2022 um 02:39 schrieb Mark Sapiro <mark@msapiro.net <mailto:mark@msapiro.net>>:
On 1/21/22 3:06 PM, Axel Rau wrote:
I created a list, did migration from 2.1 and run update_index_one_list. Then I posted a test mail to the list and it got distributed and was seen in the archive. Now 2 days later it does no longer show up in the archive. What is going on here? May this have to do with HYPERKITTY_RENDER_INLINE_IMAGE which I have turned on meanwhile.
It may. Is there anything in Django's log about this? Yes:
Jan 19 16:46:59 2022 (1997) HyperKitty failure on https://lists.framail.de/hyperkitty/api/mailman/urls: <https://lists.framail.de/hyperkitty/api/mailman/urls:> <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403)
I have:
MAILMAN_ARCHIVER_FROM = ('{{ fqdn }}')
Should I put localhost here?
If you have the original message from the list, can you go to the URL in the Archived-At: header? Is empty:
Archived-At: <>
is the message in the hyperkitty_email table in the database? E.g.,
SELECT * FROM hyperkitty_email WHERE message_id_hash ='xxx';
(xxx is the value of the Message-ID-Hash: header from the message) No.
If the prototype archiver is enabled for the list, the message should be in Mailman's var/archives/prototype/list@example.com <mailto:var/archives/prototype/list@example.com>/new directory and that message will have the Archived-At: and Message-ID-Hash: headers.
No. How can it be enabled? That’s all I have:
(mailman_33) [root@lists5 /usr/local/mailman3]# ls -lR var/archives total 1 drwxrwx--- 3 mailman mailman 3 18 Jan. 18:05 hyperkitty
var/archives/hyperkitty: total 25 drwxrwx--- 2 mailman mailman 6 19 Jan. 16:46 spool
var/archives/hyperkitty/spool: total 1310 -rw-rw---- 1 mailman mailman 838274 19 Jan. 16:46 1642610819.7180374+05663686ecac2e85272bac93299d8469aa299a6d.pck -rw-rw---- 1 mailman mailman 8888 19 Jan. 16:46 1642610819.7836225+51d3aa9170bfb408821d5d05bd50acb687f23c19.pck -rw-rw---- 1 mailman mailman 13215 19 Jan. 16:46 1642610819.846788+bdfe7825a5a718d081683cf9cfa53cc1f36e64f2.pck -rw-rw---- 1 mailman mailman 469150 19 Jan. 16:46 1642610819.9367082+6c8adeae7d43ec9f721959a57bc1d1415c0b4857.pck
Thanks for your time, Axel
PGP-Key: CDE74120 ☀ computing @ chaos claudius
Am 22.01.2022 um 11:23 schrieb Axel Rau <Axel.Rau@chaos1.de>:
It may. Is there anything in Django's log about this?
Yes:
Jan 19 16:46:59 2022 (1997) HyperKitty failure on https://lists.framail.de/hyperkitty/api/mailman/urls: <https://lists.framail.de/hyperkitty/api/mailman/urls:><https://lists.framail.de/hyperkitty/api/mailman/urls: <https://lists.framail.de/hyperkitty/api/mailman/urls:>> <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403)
I have:
MAILMAN_ARCHIVER_FROM = ('{{ fqdn }}')
Changed this to IP (stupid Django, can’t resolve). Posts appear now in the archive view.
If the prototype archiver is enabled for the list, I haven’t. Should I ?
Thanks, Axel
PGP-Key: CDE74120 ☀ computing @ chaos claudius
Mailman's content filtering has removed the following MIME parts from this message.
Replaced multipart/alternative part with first alternative.
On 1/22/22 11:11 AM, Axel Rau wrote:
If the prototype archiver is enabled for the list, I haven’t. Should I ?
It's entirely up to you. You can disable it entirely with
[archiver.prototype] enabled: no
If it is enabled, you can then enable/disable it list by list in Postorius Settings -> Archiving
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Axel Rau -
Mark Sapiro