On 6/23/26 8:48 PM, Thomas Ward via Mailman-Developers wrote:
The 'message' in question is processed by an archiver class that is already written. However, to debug an issue we were encountering, I wanted to see the object as it was a Message object as internally the archiver process sees it.
I don't understand. If you have implemented your archiver using the archiver interface, the thing passed to the archiver is exactly Mailman's mailman.email.message.Message object.
What I wanted to do was see the object *exactly* as Mailman3 sees it internally.
Why do you think the message object you get is not Mailman's internal message object.
-- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-Developers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
