Mihai Moldovan writes:
> The imported messages, do have a Message-ID-Hash, but the
> Archived-At and List-Archive headers are empty (literally <>).
[...]
> What are the proper header values for this module?
Empty or omitted. See site-packages/mailman/archiving/prototype.py.
If they're produced at all, I suppose that's a bug. Mailman core get
the contents of those from the 'list_url' and 'permalink' callbacks
defined by the archiver, which in the case of the prototype archiver
return None. So Mailman should omit those headers and log an error
message IMO.
I believe your web-facing archive is HyperKitty. I suppose you should
import those callbacks from HyperKitty (I think they're actually in
the mailman_hyperkitty Python package) in order for your backup to
reflect "archived message plus headers omitted by HyperKitty", (I
haven't checked to see if you can actually just
from mailman.archiving.prototype import Prototype
from mailman_hyperkitty import Archiver
class Backup(Prototype):
list_url = Archiver.list_url
permalink = Archiver.permalink
but it that doesn't work cargo-culting the code should be
straightforward.
I forget if your goal was to reproduce the incoming message or the
outgoing message. If the incoming message, archiving happens pretty
late in the pipeline so banned attachments have been stripped and
HTML-to-text conversion and the like have already been done.
--
GNU Mailman consultant (installation, migration, customization)
Sirus Open Source https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/NIK5WUWWH67WBAILK77LZ6K4S73BNKGP/
This message sent to arch...@mail-archive.com
